Desired options for a scantool?

[Tazzi]

Currently, the main options for diagnostic (Or even tuning) tools currently are ELMs, Scantool.net cables or AVT's.
Really, the AVT is in a whole different league since it covers so many protocols, and allows reading/writing using raw bytes. But, it is crazy expensive.

Have looked into designing and making a cable based on the STN1110 chip, which handles alot of protocols but still, communicates just like the ELM which is the down fall of that device. After using the AVT... I feel its a giant leap backwards to use the ASCII<->Byte standard again.

Iv been tinkering.. alot...actually.. its been all day everyday .. and have been playing around with some micro-controllers. Slowly but surely Im nutting together a device that so far communicates over:
-HS CAN (11bit)
-MS CAN (11bit.. Fords use this)
-GMLAN
-VPW
-ALDL
It communicates using raw bytes just like the AVT, and its own communication protocol is similar but has been adjusted to suit different needs. Communication can be performed over USB or bluetooth (Bring on the apps!).

In saying that, what sort of other options in a tool would people desire? I like the idea of having all the commands documented so apps can be made, or it can be implemented into existing programs like tunerpro.

The AVT has the choice of analogue ports, I guess that would be a good start?
What about onboard logging, designate specific PIDs and this gets saved to a SDCard when initiated?

Can anyone think of anything else? Within reason of course, I cant think of anything other then the two above?

[Dylan]

I like the above. Analogue inputs would be great for wideband integration fuel pressure monitoring for logging. SD card recording would be great. One of the big 2 (HPT or EFI live) offer this as does VL400's logger.

Read and write LS1 bin's would be fantastic and XDL logs would be great for tuner pro. Maybe you could make a program to read LS1 (maybe even LS2) ECU's into a .bin format. Edit it in tuner pro from the logs saved on your guru tool's SD card and then write back to the ECU with your program. The more integration for tuner pro the better!

I'm looking into LS tuning only recently and for something so popular and getting old now I cant believe the limited options and the prices.
There's a good market for you Tazzi.

[Gareth]

From a workshop point of view, we need a tool that -

that 'does it all'

that doesn't become redundant

that doesn't cost the earth

that has a great set of make and model specific instructions

that is fast and easy to use

that is reliable


The drew tech cardaqM is the closest to that, that we use.

hope that helps

[Tazzi]

I like the above. Analogue inputs would be great for wideband integration fuel pressure monitoring for logging. SD card recording would be great. One of the big 2 (HPT or EFI live) offer this as does VL400's logger.

Read and write LS1 bin's would be fantastic and XDL logs would be great for tuner pro. Maybe you could make a program to read LS1 (maybe even LS2) ECU's into a .bin format. Edit it in tuner pro from the logs saved on your guru tool's SD card and then write back to the ECU with your program. The more integration for tuner pro the better!

I'm looking into LS tuning only recently and for something so popular and getting old now I cant believe the limited options and the prices.
There's a good market for you Tazzi.

Unfortunately, creating to tool for communicating with the vehicle, and creating the bootloader read/write to ecus are completely different things

Although Id assume people like dimented24x7 might be able to use the tool as a cheaper alternative to use with his LS1 tuning tool?
As for LS2, well.. the E38 is powerPC.. so least we know that, but as for a bootloader to read/write to that, so far no-one has made one for public use for those.. or pretty much any OBD2 ECU.

Im looking at making a diagnostic cable that supports multiple protocols and it easy for developers (And newbies) to get up and running and making custom stuff. First on the agenda would be integrating it into my own current software and also TunerPro.

A tool like the AVT is required, and I do still recommend the AVT it highly! its just the costs are very high for the average joe.

From a workshop point of view, we need a tool that -
that 'does it all'
that doesn't become redundant
that doesn't cost the earth
that has a great set of make and model specific instructions
that is fast and easy to use
that is reliable

The drew tech cardaqM is the closest to that, that we use.
hope that helps

Wow.. cardaqM... Sheeeeezzzz! Doesnt cost the Earth... its close to it!

The complete alternative here.. it use open source J2134 (whatever its called) and take use of the protocol that the mongoose utilizes, and mdi, VCM ect.. pretty much all scantools.

[ejukated]

Analogue & Digital inputs. K-Type input optional and RS232 input for serial logging WB, Dyno input etc. If you want to get really fancy an additional CAN input could be used for adding aux data similar to the RS232 input.

[Tazzi]

Analogue & Digital inputs. K-Type input optional and RS232 input for serial logging WB, Dyno input etc. If you want to get really fancy an additional CAN input could be used for adding aux data similar to the RS232 input.

Wow.
That right there puts me out of pins I think.... would need to upgrade to a bigger chip with more pins.

[ejukated]

Analogue & Digital inputs. K-Type input optional and RS232 input for serial logging WB, Dyno input etc. If you want to get really fancy an additional CAN input could be used for adding aux data similar to the RS232 input.

Wow.
That right there puts me out of pins I think.... would need to upgrade to a bigger chip with more pins.

lol sorry I should prioritise them.

Std:
[*]Analogue, say 4
[*]Digital, Say 2. (these can be used for marking the log file for an event of interest
[*]RS232, WB input - this leaves 2 Analogue inputs free if you use a dual ch. wb

Optional:
[*]K-Type
[*]CAN

[VL400]

What about custom firmware for a tactrix interface? Has most of what you want but they dont support VPW in the firmware even though the hardware is apparently capable.

Its only the aux inputs that are not on board, but that can be overcome with a module that sits on the bus that the interface could see. Easily upgradable hardware then.

[Tazzi]

lol sorry I should prioritise them.

Std:
[*]Analogue, say 4
[*]Digital, Say 2. (these can be used for marking the log file for an event of interest
[*]RS232, WB input - this leaves 2 Analogue inputs free if you use a dual ch. wb

Optional:
[*]K-Type
[*]CAN

For the digital, how would you implement something to "mark" an event? If that makes sense.
Its easy enough to chuck a couple digital inputs there which can 'mark' an event, but what will be used to mark the event?.

From what I understand, the WB input can go straight into the analogue ports? Do some use a RS232 connector?... now thats an interesting one.. size of the rs232 plugs is annoying.

I like the idea of being able to expand the device later on if need be. So Iv purposely left a set of SPI pins available for expansion ideas.. or even connecting up some sort of expansion module.

Hmmm.. what if... maybe.. the RS232 is a plug-n-play expansion module?
Next, what is fed form the dyno.. and what connection does it use? Id assume a simple serial connection?

As for the additional CAN connection, theres already two CAN chips on board
But.. actually.. using the CAN network as a way to expand and add modules is not a bad idea! A third CAN module (If I can fit it in!) could link directly to expansion pins along with power and ground. Then a 4way connectory attaches and the new module is instantly supported. Hmmmm... the possibilities...

What about custom firmware for a tactrix interface? Has most of what you want but they dont support VPW in the firmware even though the hardware is apparently capable.

Its only the aux inputs that are not on board, but that can be overcome with a module that sits on the bus that the interface could see. Easily upgradable hardware then.

Thats true.. hmmm.. Ill have to look up some more details on the chip.
Current bluetooth setup on this can be used to flash upgrade the firmware over bluetooth

[Gareth]

Wow.. cardaqM... Sheeeeezzzz! Doesnt cost the Earth... its close to it!

compared to buying a new scan tool every year, its waaaayyyy cheaper and doesn't look like it will be redundant any time soon, the training and instructions are what are worth the money, in a workshop environment we don't have unlimited time to spend on each job just to work out how to complete a task, in the past this has been done by me, after hours... I now have a young family - the really late nights are over... plus I have better things to do with my life, like racing cars what does suck is the cost of subscriptions, if there is another way of replacing ecu's, I would like to know how

please consider that most jobs that require a replacement module come in on the back of a tow truck and are usually bricked...

I should also add that most of what you guys are talking about is way over my head