[olddog]

I just getting started with QH using TunerPro RT. I downloaded a definition A9L bin file when I downloaded TunerPro. I think it was from the TunerPro web site, but it may have been Moates. It has a 2010 date on the file. I later found on Moates site there latest definition and A9L bin file that were dated 2013. Once I got TunerPro and my drivers working I decided to use the compare utility to compare the two bins. I did it more to start learning the software, and was expecting to find no or very little differences. To my shock almost every memory location is different. It is displayed in hex, which I am familiar with hex. The differences are not small like 03 verses DA, other areas one bin has everything zeroed out. The MAF transfer area are totally different.

This has me a bit spooked. I think I just want to read my stock A9L EEC4 and make a bin from that, but not too sure how to actually do that. I believe I should be able to use the QH and TunerPro RT to do that. Any words of wisdom would be greatly appreciated. It's a bit like drinking out of a fire hose for me at the moment.

TunerPro is connecting to the QH, but I'm not sure which steps I should take next.

[SRI3850341]

It's a bit like drinking out of a fire hose for me at the moment.

great analogy!!

[olddog]

I have this option on selecting a Bin file:
Import Bin from S-Record (S19,PTP,etc)

I fail to understand abbreviations and acronyms quite often. I do not know what S in S-record means nor S19 or PTP.

I am trying to figure out how to download the Bin file from my EEC4 A9L ECU.

I have spent hours reading the help files, and there is a lot of good info here that I needed to learn. However I do see a pattern of explaining in an overview style, but little specifics, especially when it comes to Ford issues.

Can anyone offer advise here?

PS:
The WOT spark advance vs RPM table makes absolutely no sense to me.
RPM ______ deg adv
108.75 _____ 889.00
3328.25 ____1013.75
287.50 ____ -6579.00
4483.25 ____ -275.25
12753.0 ___ -1535.75
245.75 ______ 164.25
9741.00 ____ 3341.25
12623.75 ___ 1154.50
13868.75 __ -3767.00

This is using the most recent XDF and Bin from Moates.net
I think something is very wrong, but don't know if the mistake is mine or not.

[xd41efisc]

It looks like the offset is wrong.
I cant remember of the top of my head but there are some settings that need changing.
I will have a look and let you know.

[xd41efisc]

Go into XDF.
Then go down to XDF Header Editor.
And check that the:
Bin Size (Hex) = E000.
Base Offset = 2000 and the subtract box is ticked.

See if that helps.

[olddog]

Go into XDF.
Then go down to XDF Header Editor.
And check that the:
Bin Size (Hex) = E000.
Base Offset = 2000 and the subtract box is ticked.

See if that helps.

After my last post, I opened the other older A9L.bin file and it looks like all the functions and tables have realistic values.

After reading your post I opened the XDF Header Editor and everything is set as you instructed. So I opened the newer A9L.bin and rechecked the XDF Header Editor. The header is set the same when either A9L.bin is open, but the new .bin appears to be shifted. Perhaps is was not correct on Moates web site, but I doubt that. Maybe it got corrupted when I unzipped it or during the download.

Thanks for the help

I think since I have what looks like a good .bin, I'm ok to proceed.

I did find XDF\Import\from ECU. I assume this is how you upload from the CPU to make your own .bin file. Does that sound right?

[cgrey8]

It sounds like both are A9L but one is a 56k unbuffered file and the other is a 64k buffered file.

[decipha]

x2, download this gufb def and you wont have any issues

http://www.efidynotuning.com

>>downloads

[olddog]

Thanks for the link. I just downloaded them. Do you think these files may act differently (see below my problem)?

The older version I had previously downloaded all seemed to work. I downloaded the Bin to the QH. It verified good. Turned the key on and started the data acquisition (DA), with the dashboard open. I can move the throttle a see voltage change. I can read battery voltage, etc. Everything appears to work fine. As soon as I start the engine, the DA goes into error and the dashboard freezes. A couple times TunerPro stopped responding and would not shut down until the USB was unplugged. The engine runs normally, so I assume the Bin is the same as the ECU tune.

I added the two ferrite (SP?) beads to the USB cable. I could never find any information on where to locate them. I put one a few inches from the QH chip (outside the ecu case. The other is a few inches from my PC USB Port. Is this correct?

My other thought was setting the USB serial Port driver latency to 1 mil-sec as Moates instructions said. I am running vista. The com port drive is not where the documentation says it is. I did install the drivers as the instructions said, and it appeared that they installed correctly. Any thoughts?

I have read for hours and cannot find anything else to look at. Moates is taking the rest of the week off until after the holiday. I do not blame them. I do want to get this all working this long week end, so I can get started.

[olddog]

I think I started the data acquisition before starting the engine every time. Could the solution be as simple as starting the engine before starting the data acquisition?

[olddog]

Tonight I loaded the bin and definition files that decipha provided the link 2. Result the same.

Next I tried leaving emulation and data acquisition off until after the engine was started. Then I turned on only data acquisition. It works for about 5-10 seconds, and then get the error. So it is a little better this way.

This is an AC Shelby Cobra replica. The firewall is fiberglass ~1/4" - no metal. The ECU is inside the passenger compartment mounted above the passengers feet. The USB cable off the QH is only about 6" from the rear cylinder spark plug. It has high quality new Taylor plug wires. I tried putting a piece of aluminum sheet between the plug wire and ECU area. No change.

I'm still thinking the USB to Serial Driver may be the issue.

[olddog]

I downloaded from Moates a USB Serial driver CDM20824_Setup from an area that said it was there newest driver. Installed it and set the latency to 1ms as instructed. It worked better but still got the communication error.

Then I found another area on Moates site that specifically stated the driver was proven to work on Vista. It is CDM_Setup Auto-Installer. I installed it and set the latency to 1ms. It worked for 35-45 seconds before the communication error.

Any ideas?

[olddog]

First I do not know if no one has replied because they do not have any ideas or if I have offended or did something wrong. If I did something wrong tell me, so I can make amends and not repeat it. If others are stumped too, that's fine.

Tonight I unbolted the ECU and set it on the drivers side seat, which got the USB Serial cable a good 3.5 feet from the nearest spark plug wire. No improvement at all.

I moved the ferrite beads to the opposite ends of the cable. No improvement.

I tried playing around with the advanced driver setting by reducing the number of bites it transfers. No improvement. Put it back