delcowizzid wrote:elmscan 5 should work charles can you take a car battery inside and power the cable LOL
so where too now LOL.ive had a bit of a read up and some of the chineese cables have resistors across the can bus +/- and maybe other k line and j1850 can cause issues and requires removal of resistor just have to see how we go.no .net 4 on the lappy is going to be an issue ill work on it so i can test incar
Where to now? Hmm.. think ill quickly add the voltage input as well "ATRV" (RV = Read Voltage input).
From what Iv seen in most applications, they seem to turn headers on, turn off echo, check the protocol or set protocol annnnnnnd also sent off AT@1 which gives cable ID ("USB to Serial Converter") or something like that.
Since now we have a working connection between the cable and software. Just a matter of putting in the correct PID's or Modes to read engine data and faults. Then convert that data into useful information.
If all of the above then works. I can hopefully feed any data I want to the tech2, to extract any "Holden specific" codes and errors. Will need access to a OBD2 PCM though.. or just get a willing participant to send off the messages I log from the tech2
Ill attempt to change the target framework. Have to mess with the advance compiler options or something like that. Will chuck it up once done.. hopefully still works the same.
Any idea what .net framework you have installed? 2,3,3.5?
