jezzab wrote:Re: programming via an ELM. I have attempted to program a module in 11bit with an ELM. I could 1/2 do it. The problem was timing. See the ECU has to write the blocks as you upload them and while its thinking it will send a 0x78 response which means "Im hearing you but im working, shutup and give me a minute and then send again when i tell you im ready", the problem is there is no IRQ on the ELM so you can only put in a set delay and if the timing goes out then it will fail with a GPF (General Programming Fault)
Jez
hahahahaha, that made my day.
Sounds like the ecu is a grumpy bugger.
What exactly is "IRQ"?
Doesnt sound..tooooo bad.. just have to monitor for the 78 response each time. I guess Im also assuming that the elm is capable of doing this since its limited by a 8byte write buffer. Would require some know how to develop ya own.
ZerOne wrote:If it helps Tazzi, Mace (and Trifecta performance) in the states) offer a remote tuning service using this little beastie.
http://store.mp3car.com/OBDLink_SX_2_0_ ... om-145.htmhttp://www.trifectaperformance.com/It looks like trifecta have made their own software for High Speed Can, which they use in combination with the above dongle to email tunes to customers.
(MACE has either licensed the software, or is sending the log files to trifecta in the States to create the tune file, making Trifecta a provider of wholesale priced tunes for Mace).
Uploading Tune files (Engine and transmission) took around 15 minutes or so
So it definitely can be done using some cheap hardware.
Are you saying that the OBDlink cable and trifectaperformance cables are the same? Since thres a massive price difference! $250 for the cable from Trifecta, Id assume that cable would be similar to the AVT cables.
But at 15mins, that sounds fairly long since though it normally takes about 4-5mins to tune with AVT or tuner cables ect. The cables look similar although wouldnt think they are.
A few of the boys at delco seem to be having trouble connecting their cable in car. But the software works on bench with power supplied to pin 16. After a little bit of research, looks like its actually a common problem, I even found a few mentioning that they had it communicating on bench to software although failing once connected in car.
Immediate thoughts are the obd port has a dodgy connection, but turns out most sorted the issue by uninstalling the drivers, downloading the newest FTDI drivers directly from their site and then manually clicking on the driver install for the cable and navigating to the FTDI folder downloaded.
I dont see how this affects the cable when in car, but seems to have sorted it for those having issues.