Software On ELM Street - OBD2 Software Development

[Tazzi]

Jayme: yes you can on the AVT

Thats pretty damn cool..
*kicks ELM again*

Now up to 1400lines for the DPID routine. A tonne of checks have been added to prevent any significant problems arising. Also checks that the DPID setups were accepted.
So far.. this is only for the CAN setup. The VPW setup should hopefully be a tonne easier and most of the subfunctions can be applied.

Im still stuck on how many bytes each PID uses.. will need to work out what each are.. or somehow get the ECU to tell me. theres only 7bytes in the "spam" message from the ecu so Im thinking if I load up a DPID with a message that requires 8bytes to be returned the ecu will recognize this and will error back. Possibly load up known PIDs and then try a new one.. if it accepts it, its 1bytes in return size, if it returns an error, then the PID is 2bytes in return size. (well.. I hope that works!)

Also need to add a "PIDs supported" button or check. I think If I check each PID by applying it to a DPID.. any invalid PIDS will result in an invalid DPID setup message.

[Tazzi]

Bit of a redesign for the main screen. Appeals alot more to me.
Can get a quick brief overview of the car status on initial startup (once its all implemented )

Still got a bit of room for extra settings, not sure what to fit in there. Was thinking maybe just a simple user choice for "basic", "amateur" and "professional" settings. So things like header changes (automatic now), CAN error formatting, pid lists?

Am also looking to remove the "Dev" tab, as Im spending more time modifying the code for each use rather than a "one size fits all" solution. Eh.. dunnoo.. the alternative is to apply a simply plugin system so all settings can be modified systematically and user customizable.

Will definitely keep the seed/key searcher. Will greatly appreciate anyone/everyone testing when I get the next version out.

guiupdate.PNG (62.51 KiB) Viewed 4173 times

[vlad01]

cool interface!

the 'holden diagnostic" logo at the top does my eyes in though lol. red and blue together are really hard to focus the eyes.

[Holden202T]

yeah screen looking good

[Tazzi]

cool interface!

the 'holden diagnostic" logo at the top does my eyes in though lol. red and blue together are really hard to focus the eyes.

Yeah agreed, Ill try another color

[VL400]

Looks really good tazzi, will be a very handy tool

[delcowizzid]

im gonna get a loan of the vt during the week so i can just walk outside and play with it.ive been looking for a nicer way to log and check error codes liking the look of this very much

[Jayme]

Awwwww dont like my dpid adx for vpw hey. It does do error codes just 4 at a time lol

[delcowizzid]

i find tunerpro and LS1 a bit clunky and have connection issues and shit sometimes.i need to make multiple adx's instead of changing the commands to suit would make it easier i spose just havnt had an LS1 powerplant to play with for more than an hour or so at a time every now and then doesnt help

[Tazzi]

logo is still using red writing.. but much darker. Is there still conflicts? Can dull the blue if that might help.
I tried orange.. and felt that I had burnt holes into my eyes staring at that. All black was..plain and dull. A mellow green was ok, but Im preferring the red

gui2.PNG (66.1 KiB) Viewed 4100 times

On successful connection with elm, it will automatically (by default) grab some basic information including VIN, current protocol, last logged in. And then will do a quick fault code scan, freeze frame scan and PID search.

The PID search is still only pseudo code.. Im yet to full test out my theory. But GM docos explain that a DPID that is loaded up wit PIDS that requires a return frame greater then the allowed 7bytes will result in an error. Soooo Im counting on this to determine valid PIDS for CAN protocol. VPW is piss easy to determine this.

Will also have to add some sort of progressbar at the bottom to show setup progress.. as all of the above actions will take a little time (mainly just the PID search)