pcmhacking.net

Moates has a header adapter to read the chip with a chip burner like the Gq-4x
https://www.moates.net/hdr1-memcal-head ... l?cPath=64

Also a G1 adapter to use a 27F2512 chip which will erase and write without UV light. This chip will burn and erase with Moates Burn 2 and program is built into TunerPRo RT.
https://www.moates.net/g1-memory-adapte ... l?cPath=64

If you can read the chip? We can find the mask ID and know what or if an XDF is available? I have a ton of them for USA stuff along with all GM .ds files converted to TP .ads

Have you looked on the TunerPRo files page?
http://www.tunerpro.net/downloadBinDefs.htm

What Datamaster did you use that worked?

I'll have to g et the version number for you but it had the definition s for the Lotus elan m100 with it. I'll post the bin file later tonight.

Sorry about the horrible post from earlier I was on my Phone at work. I have attached the BIN file that I was able to pull down from my computer today.

EagleMark, I have been through that list multiple times and somehow still missed that ADX file! Thanks! It should help in trying to get tunerpro to work. I will let you know on my success.

I want to take it one step at a time and start with monitoring and data logging and work my way up to eventually tuning but no hurry as I have alot to learn first. Not to mention no one else is trying to do this with this car, So I am kind of a lone ranger.

I will also try sending a few commands to the ECM with the OSE Flash Tool Tomorrow and post the results.

I REALLY appreciate your help through this!

Thanks

Brandon

Ive got some bad news about that bin. It does not look like a good read, or its a very different system to the delcos we know. I suspect its not a good read though. The contents appear random, and any regular bin would have some kind of order to it and that file does not.

antus wrote:Ive got some bad news about that bin. It does not look like a good read, or its a very different system to the delcos we know. I suspect its not a good read though. The contents appear random, and any regular bin would have some kind of order to it and that file does not.

perhaps the software on this ECM has a different memory map to that of the elan and as such downloaded the wrong data.
Best bet is to pull the memcal and read it externally

Here is the first code I entered and the response that I got.

16:25:39.716 Tx'd Frame = F4, 56, 1, B5,
16:25:39.803 Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, AB, 6C, FF, 1B, 0, 0, 1, 0, 0, 0, 0, 0, 5, 0, 80, 50, 48, 74, 76, 0, 7B, 2, 3C, 80, 20, 0, 0, 56, 12, 26, 23, 37, 0, 0, 0, 0, 0, 48, 0, 0, 0, 4C, 0, 0, 1B, 0, 0, 0, 0, 0, 0, 0, 1, 0, A, 0, 1F, 40, CC,


Here is the second ommand that I entered and the response that I got.

16:26:27.293 Tx'd Frame = F4, 58, 2, 0, 0, B2,
16:26:27.384 Rx'd Frame = F4, 95, 2, FF, FF, FF, FF, 7F, 0, 0, 0, 0, 0, 0, 12, 26, 20, 15, 0, 1, 0, 0, 0, 70, 70, 50, 0, F0, 74, 23, 1B, 13, 0, A, 0, 0, 1, 0, 0, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 40, 20, 1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 15, BC, 0, 0, 21,



IM trying to get tunerpro to connect with the ELAN ADX, it keeps saying Connected and Flashing to Error

Still working on it though

are the echo settings right in TP5 ?

I have looked and havent seen any kind of setting to change the Echo. I am also getting an error in TP trying to connect to my ecm. It flashes between DA:Connected and DA:Error. I have read around the net and seen that you have to edit the adx file which I cant do because it is password Locked. This File came from the TunerPro site, anyone know the password?

Also I got this out of Datamaster although I dont know if its really any help or not:

Thanks

Brandon

never seen a locked adx

They are lockable, its the 'encrypt file' option on the main adx config page, with optional open and/or edit passwords. But which file is it, and is it for the right car?

We can confirm from the above that the pcm does speak ALDL and is device ID F4. And it responds normally to mode 1 and mode 2 commands. So far, so good. Also I think your interface is an echo type interface, because in the datamaster response you can see the request command has been echoed back. "F4 56 01 B5" echo then reply "F4 95...." That is normal for regular aldl interface to a factory aldl port.

I think you will be able to read the bin over the aldl bus with the flashtool, but VL400 might need to give you the settings for the custom memory map.