pcmhacking.net

yeah cell tracing is cool waiting for the new tunerpro V5 so i can use my ADX cause i dont have an ADS and im too lasy to make one

my attempts at making an ADS failed miserably cause it wouldn't connect to the ecm!

haha i had been thinking in bed the last few nights about blm tables and cell tracing like winaldl well scannerpro has this function you just need to build the tables so i now have a blm table and O2 volts table based on rpm vs map even fills when playing back a log and has data averaging and the amount ofd hits the cells taken and a nice coloured bubble floating over the cells as you use them

Holden202 wrote:my attempts at making an ADS failed miserably cause it wouldn't connect to the ecm!

I had this problem too, the problem was that our ECUs have 2 wire serial, so there is no echo. Tunerpro RT4 does not support no echo, so I faked the echo in antusprom. If you connect via antusprom you should be able to get it to work. You have to configure the offsets slightly differently, but it does work

PS Ive got winxp + vc++ as a virtual machine under linux now. This will make rebooting to work on antusprom a thing of the past so I should be able find more time to work on it.

The latest version of Tuner Pro RT V4.14 build 0381 allows for com ports higher than 10.

I can verify that TP RT V5 will also have the same capability.

Does the antusprom require a patch to the bin, like the NVSRAM requires?

Thats some good news six_shooter, will be handy.

It needs the same code in the bin as the NVRAM, the OSE $12S code works with it.

Just FYI, the latest V4 build is available for download to the public.

Since the code needs a patch, I'll stick with my Ostrich 2.0 for now. I would love to only need one cable though, or better yet go wireless. I have a Bluetooth module in my Ostrich installed in my Datsun, but hardly ever use that because I still need to plug in my ALDL connection.

I would love to figure out how to datalog through Bluetooth, I have tried a serial to BT adaptor, with no luck, which I'm starting to think is because of the baud rate of the ECM, since it is an odd rate.

The biggest thing about not wanting to use a patched bin is because I use $59, which has new versions coming out, hopefully soon, and since I don't know enlough about dis/assembly, I'm not comfortable with the change, yet.

Yeah if you were using an open source code base could add the code, but code 59 the only way is to patch the necessary code - which is not the most ideal way to do it.

First post...great site! I have a newb question as well. I'm currently using $A1, does a version of it with the "real time" patch added exist? If not, is there a general description of the changes needed to make this work available? I searched but couldn't seem to find anything.

Thank you!

-- Scott

Sorry one does not exist yet. To add it is a task that needs some specialist knowledge. You need to dissassemble the code in the ecu, find the aldl code from the serial interupt handler and splice in the write code, then re-assemble. The banked memory access makes this harder but not impossible. We will try to work on the VS/VT and later codes after after we've finished with the OSE $11 and $12 versions. (supporting VN/VP/VR/VSV8)