Can't connect TunerPro RT V5

[Turbo]

Good morning gents: Can someone help please? I have been trying to get my Windows 7 SP1 to connect to a 1227730 ECM for months now, with no success. I have found a Device Driver that worked previously but Windows won't allow it to be installed, now, on my replacement computer. The driver #2.01.0 is windows signed, but not Certified. The driver comes with my GQ USB Programmer and is the only one out of all of the drivers that I have tried that worked. I tried at least a dozen different drivers. All I want to do is some Data Logging on my registered TunerPro RT V5. Windows Service Pack 1 refuses to recognize this driver. When I used it previously, on the original computer, service pack 1 was not installed. By eliminating all of the drivers, windows gave me the option of installing the un-certified driver along with all of the "are you sure" warnings. All I wanted to do was change my 19# injectors for 30# injectors and do a new tune on my Hot rod. Please help me solve the problem. Turbo
NOTE: all my cables and connections pass all of the tests (Realterm, ALDL test, TunerPro, Data Master, etc.) It gets to "Connecting" but never connects. Data Master dosen't see the ecm.

[Six_Shooter]

What hardware are you using?

Connecting via the ALDL connector will not allow you to change any settings in the bin, you need to program a new E/EPROM to do that.

[Turbo]

I'm sorry if I misled you. I am able to burn chips and change data, I just can't connect and gather new data due to the lack of a connection. I have been able to reduce the idle from 3,000 RPM to 2,000 by removing all of the add'l fuel being added from the current chip that was programmed 20 years ago. I really don't want to make more changes without
new data. I'm concerned that with the over fueling I may be washing down the cylinders. My block is already at .060" over and will not handle another boaring.
My equipment list is as follows:
- 1227730 ECM
- Flash and burn from Moates
- Extreme ALDL1 cable1 and usb adapter
- Un-named Add'l USB cable and adapter
- DataMaster 3.3 and 4.1
- TunerPro RT V5
- GQ USB Programmer
- Prolific #2303 USB to Serial adapter
- SST27SF512 Chips from Moates
- Several flash chips - #FM27C256
- HP EliteBook - windows 7 SP1
- HP Windows 10
All of the cables check out OK after running all of the tests available. But the ECM is not seen?
Thank you for your help.
Turbo (Tom)

[Six_Shooter]

What code are you using/what's the application?

What ADX are you using?

[dave w]

My experience with USB adapters has not been good, actually horrible!

I now use a USB ALDL cable from http://www.aldlcable.com/products/aldlobd1u.asp

dave w

[Turbo]

My cables did all work with my Device Driver 2.01 that came with the QC Programmer. The programmer is awesome by the way. It is flawless and seems to be intuitive. Turbo (Tom)

[Turbo]

Looks just like my second cable. It works also. Tom

[dave w]

What .adx file are you using?

dave w

[Turbo]

Hi Dave, I am using 1227730_8D.adx. Tom

[dave w]

See attached pics for my TunerPro RT settings.

Maybe you can post screen shots of your settings?

dave w

[Six_Shooter]

So is the code in the ECM $8D? If not that ADX won't work. What is the application?

Dave W, the ALDU1 doesn't require a USB adapter. ;) It will require the FTDI drivers though, your programmer drivers have no effect on the function of the ALDU1. IIRC the drivers are different.

[uncabob]

So is the code in the ECM $8D? If not that ADX won't work. What is the application?

Dave W, the ALDU1 doesn't require a USB adapter. ;) It will require the FTDI drivers though, your programmer drivers have no effect on the function of the ALDU1. IIRC the drivers are different.
7 needs the FTDI drivers. Get them free from Moates.

[Turbo]

Thank you Dave W, with all of the reading and research I've done, I didn't know there was a code inside the ECM. Where can I find it? Do I feel pretty stupid about now? I have never had any problem getting drivers, I just couldn't get them to work. So I am on my way over to the car to see if I can see that code. By the way I am assuming the code is the problem, which driver have you found to be the most reliable - 2.08.14? Thank you all for your responses, Turbo Tom.

[dave w]

When I setup a new ALDL cable, an ALDL cable exactly like the one I posted a picture of, I plug in the new cable into my laptop USB port. I then "Run" the CMD20824 Setup.exe directly from the Moates.net website http://www.moates.net/usb-driver-p-215.html?cPath=78

Then I check which com port is needed from the Device Manager.

dave w (http://www.moates.net/zips/CDM20824_Setup.exe) (http://www.moates.net/zips/CDM20824_Setup.exe)

[Turbo]

Update: Well gents, I think I may have found the problem, but not the answer. After jumping terminal's 'A' & 'B' together and turning the key to the ON position - NO flashing, no codes just a light that stays on. I checked all of the associated wires for conductivity and position in the harness and connectors. Everything appears to be correct. No broken connections. etc. The engine still starts and runs but no data logging. I was able to get the original laptop computer (XP), chips, programmer, cables, etc. from the friend that programmed the engine, when it was first built. I hooked everything up, ran it with DataMaster 4.0 and got the same results. I figure it must be the wiring or the ECM. I do have a second ECM and get the same results; I can't vouch for the second one, as I bought it over the internet???? That is where things stand at the present. I have a list of things to do yet, including finding a known GOOD ECM. Thanks and I will keep you posted. Turbo

[Six_Shooter]

Ok...

So under normal operation (when you're not trying to datalog or anything like that), when you turn the key on, what does the CEL do? Does it just turn on and stay on solid or does it turn on, flash off once and then stay solid until the engine is started?

[Turbo]

Well, it appears that my chip is corrupted. I am now in search of a new chip that would be a starting point for my engine specs. I will get to the details later, but with another ECM and working chip, all appears to be normal. I will get back to you shortly. Turbo.

[Turbo]

Good evening. I have a further update to this thread and it is to do with programming chips. I have two chip burners, one being a Burn two (Flash and burn). This thread was started because I couldn't connect to any data logging no matter what I tried. What I have discovered is that any chips that I have burned lately are being (invisibly) altered when they are burned, (to my eye at lest). When verifying the burn the new file doesn't match, so it fails to verify? I have been using Win 10 and most other things seem to be OK. If I use older chips I have no problems with logging on to TunerPro RT. I have tried a second computer running Win 7 and the same thing is occurring. I was was wondering if anyone else is having similar issues. By the way, the new chip burned does run, with the changes, but you can't data log anything, so you are flying blind. I tried the comparison tool but nothing shows up there either. I am more than frustrated with all of this nonsense and would love to get on with learning the program instead of wasting everyone's time. I appreciate any and all of the help. Turbo

[Six_Shooter]

Are you erasing the EEPROM before programming the new BIN file to it? I often, maybe every time have chip verify fail when I haven't first erased it.

If you don't get a verification of true, stop, do not use the EPROM, first get it to verify THEN use it.

[Turbo]

Well guys - Good news. I have my wheels back in the garage. Fixed a few issues, found a good 'BIN' file from my past, that works real well. The car pulls like crazy and "you just want to keep your foot in it". After I have a chance to go over the file I would like to share it, if anyone is interested? I would like some of you Experienced guys to critique it and make suggestions, if you be so kind?
I haven't had time to sort out the chip programming issues yet, but I will keep you posted. I sorted out why "I Couldn't connect with T.P.". I needed a BIN that was working as a reference only and then you can log any good BIN. I have no problem and I'm using Win 10.
To answer Six Shooter about erasing the chip, Yes I can see myself forgetting to erase it first, but in this case I tried 2 and 3 times erasing and then doing "the blank check" thing. I even used the Comparison tool and it thought the bins were the same. ???????? I will publish the file and a copy of the Programmed file and see what you think (when I have some time). By the way, I am using Moates Cable 1 with extreme ALDL and Driver 2.12.16 installed by Windows and it works fine.

[Turbo]

The problem with the programming was caused by a bad connection in the ZIF socket. When I programmed the chip part of the code was missing, when it tried to verify, of course that part of the code wasn't there. So the result is that all is good and working. I will attach my BIN file if someone can tell me how to do that. Thanks all, Turbo