Having nothing but trouble connecting to my 1227165 ECM (actually it's the 8259 direct replacement) and was wondering if there is a different stream file I should be using just to data log since I have a Jet stage 2 chip installed? This is an '89 Iroc 350 and am trying to use the 1227165_6E.adx file. It just will not connect and continuously gives the red flashing data read errors.

I've tried playing with the cables and ports and rest of the ideas i've found so I was curious now if the Jet chip makes a difference?

Thank you!

 

You might try a different ecm. Or a different adx ?

 

Yeah I may buy one or just leave well enough alone and not bother worrying about reading any codes on my own

So that jet chip is irrelevant and it should be reading with the setup i have?

 

Should be a $6e mask and work ok. I think the connection issue is just the infamous 165 ecm.

 

More adx files to try
http://www.gearhead-efi.com/Fuel-Inj...Information-6E

 

Thank you, will try them all

 

same problem I have. I was able to get rid of the flashing error by going into my usb port settings, advanced settings, and raising the minimum read/write timeout period to 900 milliseconds. Now the flashing is gone, it says I'm connected, but I get junk data. Still trying to figure this out. Let me know if you figure this out.


Kent

 

Hey Kent, will do! I gave up on it last week as nothing worked but will test it out again tonight with adjusting the usb port as you describe.

 

I started going up from 0 (it should only let you do this in 100 millisecond increments)... when I got to 900... the DA dataerror message stopped flashing. Like I said I still can't get good data but I think I'm in the right direction.

 

If you can't get good data, then something is wrong with the ECM, or there's a wiring issue, or a major setup issue with the software/port settings/definition file, etc.

The 165 disconnecting issue is not an issue that will cause you to get bad data, or not connect in the first place. They will randomly stop transmitting data. It will appear that you are still connected and the engine keeps running just fine. This happens with a high degree of randomness. Typically I see this happen within about 10 minutes of connecting. It requires a 15 second key cycle and it will go right back to data-logging again. After that sometimes I can log for 45 minutes. Sometimes 45 seconds. It's completely random. It does not cause bad data or failure to connect in my experience.

GD

 

Yes I am just getting bad data. I am going to look for possible electrical interference, screw around more with the com ports.... I know my ECM is fine. But eventually I think I will try to get a replacement just to test and see my particular ECM is just finicky.

 

I had a similar problem when I first tried to stream data to my bluetooth adapter. The adx file I was using was not correct. I was getting data but it made no sense. Switching to the correct adx file got it going for me.

Have you tried all the different versions in the gearhead-efi link above?

Pretty sure I'm just using the one that came with TunerPro RT though. Try a different computer? I'm using an old Windows XP netbook I picked up for $100. These little Lenovo netbooks can accept a huge battery that lasts for like 6 hours of tuning. They are super cheap and so are the batteries.

GD

 

I have not tried ALL... but will... I also just ordered a spare ECM from Hawks. I am also going to try switching com ports. I have to figure this out. I'm too emotionally invested now.


My computer is a Surface pro3.

 

LOL, I feel the same way!

 

I use one of these. Cheap and small. 6 hour extended batteries are available for like $25:

http://m.ebay.com/itm/Lenovo-IdeaPad...%257Ciid%253A4

GD

 

Lol...yep me too. Some cheap a$$ old Dell i picked up on eBay for 40 bucks a couple of years ago.

For interfacing with a 26 year old ECM, it does very well.

 

So what are u guys saying? These simple, cheap laptops might work better?

 

It's possible. Your trying to interface with 30 year old tech. There's no technical reason you should have a problem but they don't exactly test the newest hardware with 30 year old peripherals.... it wouldn't be the first time I've seen something like that. While the hardware is for sure capable of the interface, it doesn't mean there isn't some kind of driver issue..... trying a second PC as well as a second ECM can be part of the troubleshooting.

GD