Software On ELM Street - OBD2 Software Development

[III ROMEO III]

Perfect work Tazzi

thank you

[Tazzi]

Attempt number 3 for modified ELM device for VE commodore... Success!!.
Unfortunately takes almost an hour per board to retro fit. The opening of the old case it oddly the hardest part as I dont want to damage the internals. I might be about time to pull out the dremel and see if I cant cut straight around it.
The next frustrating part is the replacement cases I have do not have the rear holes.. even though they say they do. Have purchased from 8 different sellers to be hit with the same thing!. Will need to work out a suitable bit size to drill a hole so the cable stopper/protection fits nicely and does its job.

Ive had a VE BCM, IPC, Radio, SDM and HVAC all power up together, and can happily communicate between all devices and request diagnostic data. Whats even better is they handle all that communication happily! Whereas the MX WIFI will have "buffer overflow" issues. You would think the WIFI connection would easily be able to keep up, but it seems the bottle neck is within the device somewhere.
The devices are stable and work 100%, I have been able to update the IPC and radio no worries with an ELM (yes.. I did say ELM!).

The only perk that the MX has over these modified ELMs, if that the MX can do both normal CAN and the gmlan. Whereas the modified ELM is now only capable of gmlan.
A quick work around for this, is having a simple little switch on the side which can be used to transfer between Standard and gmlan, I will give that a go on the next revision.

[Tazzi]

Completed a full software update on a VE radio twice using two different modified ELMs. I am more then happy with the results. Looks like they are rock solid once kicked into the right mode.

Plugged into my VE SS, also did a full update. And could successfully negotiate faults/data from various modules. Veeerrrryyyy happy!

[antus]

Nice work!

[yoda69]

Great work tazzi, sounds like it's all coming along really well.

[Tazzi]

Yeeep, will probably drain the VE battery a few times over the next week with testing haha.
Only other alternative is an MX which isnt cheap at $161.68 not including shipping!!!

The major modules Ill be hitting will be IPC,Radio,SDM,BCM (Unsure if only CAN high for this).

Once Iv got something together, will get any pcmhacking locals interesting in testing setup with a modded cable

[Tazzi]

With sending 02 1A 9A to the listed pcm's I got the following response....

E38 YRPS (serv. no. 12619077) = 7E8 04 5A 9A 81 17 AA AA AA

E38 YPMT (serv. no. 12617568) = 7E8 04 5A 9A 81 11 AA AA AA

E55 = 7E8 03 7F 1A 78 00 00 00 00

E69 SIDI AALT(Serv. no. 12617230) = 7E8 03 7F 1A 78 00 00 00 00

E77 non SIDI LHBP(Serv. no. 92193637) = 7E8 03 7F 1A 78 00 00 00 00


Seems very weird that the E55 hd the exact same response to the E69 & E77 whether there SIDI or not.

With that PCM you had a link to it's definitely a VE SIDI at a guess probably late 2008 as I have the same PCM here that's a brick ATM & is exactly the same service no's & prefix but teh serial on mine starts with 4919 as that 1 is 4917, so guessing it's a bit older than my brick!

I hope all that helps!

Spareecm on ebay usa can be cheaper than local. The guy specialises and has heaps of thrm. Post is the gotcha but its still worth it. He can 'probably' program a bin on if the service no is correct but you want a particular aussie os and vin. Efilive have a compatability matrix for e38 of what os works with what service number. All e38s are not exactly the same (although you would think that is what the e38 designator meant!)

Just quoting some posts from previous that will come in handy soon!. Literally just when through the entire 102 pages.... Im impressed if anyone goes to that effort and follows that!
Looks like I will try contact spareecm for some e38's/ls1 ecus. Tried 3 local wreckers.. and they wanted $350+ for each, Literally walked out laughing
Also been trying to pickup VZ E55 V6 ecus, and about to fly kick the next wrecker that tells me I cannot reprogram it and must be sold with key/bcm and pim. Telling me they know from first hand it cannot be done. You would think they would just get on with the sale and sell the ecu!

I honestly must have the worse luck with wreckers, never get a fair price. Its not like Im not polite! Maybe I need to go roll in dirt, put on a FIFO outfit and try again?

Snug as a bug in a rug
(Excuse the shanks into the case on the bottom... it was an effort to open up a sealed case)

014.JPG

Also had a few asking what happened to the STN development. I made up one proto. The good news is it works (with a couple little green wire changes)
But, took me literally forever to get solder up and the costs on my behalf are quite high for it.

[ralcool]

Riddle me this, I am trying to work out why this SOE and AED are separate programs.. Its probably really obvious, like ELM327 support, and later models covered.

But couldn't they be merged into one? I'm looking at the website and gosh they look similar.

Am I missing something.. I can be daft at times.

Edit, I am seeing the light now.. Its OBD2 specific, for VZ and later effectively. Still, aren't they otherwise similar, logging, pids, gauges.

[Tazzi]

Riddle me this, I am trying to work out why this SOE and AED are separate programs.. Its probably really obvious, like ELM327 support, and later models covered.

But couldn't they be merged into one? I'm looking at the website and gosh they look similar.

Am I missing something.. I can be daft at times.

Edit, I am seeing the light now.. Its OBD2 specific, for VZ and later effectively. Still, aren't they otherwise similar, logging, pids, gauges.

Yes,exactly that. They utilize different diagnostic cables to be able to communicate over different 'languages" (Protocols).
AED is soley designed for ALDL communication using an ALDL cable and only supports those commodores that use the ALDL line. It works similar to that of tunerpro/efilive v4 in the fact each vehicle has a set "definition" that it follows to display in the gauges.
SOE is soley designed for OBD2 communication, specifically over VPW (LS1's) and CAN500 11bit, using an ELM327 cable. The later protocol is used in all commodores from VZ upwards.

They look similar because they are built on the same foundations/platform. Its easy enough to change the layout and colour scheme to make them look different but I havent looked any further into gui redesign as Iv been focused on adding features rather then attempting to redesign GUI. I do intend on differentiating the two applications later to make them more distinguished but this is not on the high priority list.

Those two applciations have not been merged into one, as they utilize two completely separate diagnostic cables/interfaces to read the required data. Both these cables also communicate different and support different vehicles. This causes ALOT of confusion to what cable is needed for what vehicle, and results in a large amount of my time spent on answering back emails in regards to which vehicle needs what. Basically I will be utterly swamped with messages saying "it doesnt work on this vehicle" because they are using the wrong interface! This is why I found splitting ALDL applications away from OBD2 applications and having definately set "Supported vehicles" helps distinguish what is exactly needed.

If there was a diagnostic cable that supported ALDL and the OBD2 cables, then yes I would have combined the two softwares instead of two separate interfaces.

[Chuff]

OMG!!

I have just upgraded to the latest version and things have definitely advanced since the version I last saw.

I look forward to running all the additional functionality you have now so graciously provided us all with.

Excellent work to yourself and all concerned.

Chuff