Ok, I had to set tuner pro aside for a while because of issues with it not being compatible with my logger setup, but today I've downloaded the latest version, and if it does what it says (baud, parity, etc..) it should work fine.
Since my last visit, I've found a compatible writable chip to place in the ECU in replacement of the prom chip, and am working on writing to the chip via the logger interface to edit the map tables, instead of needing an emu. (the ECU is designed for this and the code is in the prom, even though the ECU has a prom instead of a writable chip)
Is TP capable of loading a bin/XDF/ADX, and after editing parts of the bin sending commands via the ALDL interface to the logger to write the changes to the chip?
I get that I can do single commands just via the interface, but can they be tied to the map tables to write, like via using an emulator?
Capability of witing via the ALDL?
Moderators: Mangus, robertisaar, dex
- Six_Shooter
- Posts: 590
- Joined: Sun May 06, 2007 7:32 am
-
- Author of Defs
- Posts: 962
- Joined: Sat Feb 21, 2009 3:18 pm
- Location: Camden, MI
The ECU is a bastard child, from a sled..
Some of the stuff is similar to Subaru (select monitor hardware interface), some is similar to Nissan (added port for write enable), and something similar to the nistune add on is what I'm using.
Unfortunately, although the select monitor hardware is compatible, none of the commands nor the baud rate is the same. And although I'm using something like the nistune, nothing else commands or otherwise is compatible with the nistune or any nissan stuff.
So, I wrote a vb script that I can run in a shell to communicate with the ECU and can pull up the error codes and sensor values, dump parts of the chip, etc. And now that Mark has added the ability to do oddball baud rates, I've been tinkering with the ALDL features for an hour or so to try to get it log from the interface I have, but having not used TP is almost a year I'm a little rusty, and the logging part is totally new.
I made 3 identical boards to replace the prom's with, and managed to get one to work out of the 3. (can't figure out why the other 2 won't work yet) And I haven't worked out the write routines yet.
I am hoping that with a more stable interface like tunerpro, it'll work better than a VB script, which is about the extent of my coding ability. So if tunerpro is capable, I'll put the effort into making it work, but if it won't I'll stick to using TP with the emu and logging.
Some of the stuff is similar to Subaru (select monitor hardware interface), some is similar to Nissan (added port for write enable), and something similar to the nistune add on is what I'm using.
Unfortunately, although the select monitor hardware is compatible, none of the commands nor the baud rate is the same. And although I'm using something like the nistune, nothing else commands or otherwise is compatible with the nistune or any nissan stuff.
So, I wrote a vb script that I can run in a shell to communicate with the ECU and can pull up the error codes and sensor values, dump parts of the chip, etc. And now that Mark has added the ability to do oddball baud rates, I've been tinkering with the ALDL features for an hour or so to try to get it log from the interface I have, but having not used TP is almost a year I'm a little rusty, and the logging part is totally new.
I made 3 identical boards to replace the prom's with, and managed to get one to work out of the 3. (can't figure out why the other 2 won't work yet) And I haven't worked out the write routines yet.
I am hoping that with a more stable interface like tunerpro, it'll work better than a VB script, which is about the extent of my coding ability. So if tunerpro is capable, I'll put the effort into making it work, but if it won't I'll stick to using TP with the emu and logging.