Trouble Datalogging
#1
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Trouble Datalogging
Hi there,
I'm not getting any data flow using either WinALDL or Tunerpro RT. I'm using a ALDU1 and CABL1 from Moates, and have been using the 10k ohm setting. I tried switching to "open" but without success. I'm trying to connect with a '7747 ecm in an 89 K1500.
In Tunerpro RT I've used a 42.ads and converted it to .adx then edited the file to have 67 as the body size. When I test the cable, it shows up as good and when I hit "Aquire Data" I get that box at the bottom that says "DA:Connecting" that could go for eternity.
In WinALDL I have set in configurations for the '7747 ecm, Com 6 which checks out as ok and 4800 as my baud. I click START under datalogger with all boxes or just one checked, but nothing happens besides the START button turning to STOP.
Under port settings latency timer has been turned down to 1 for Com 6, transfer sizes are 4096 bytes, and time outs are set to 0.
I have tried connecting KOEO and while the vehicle is running, but it doesn't seem to make a difference.
Am I missing anything? Help would be appreciated, thank you in advance.
I'm not getting any data flow using either WinALDL or Tunerpro RT. I'm using a ALDU1 and CABL1 from Moates, and have been using the 10k ohm setting. I tried switching to "open" but without success. I'm trying to connect with a '7747 ecm in an 89 K1500.
In Tunerpro RT I've used a 42.ads and converted it to .adx then edited the file to have 67 as the body size. When I test the cable, it shows up as good and when I hit "Aquire Data" I get that box at the bottom that says "DA:Connecting" that could go for eternity.
In WinALDL I have set in configurations for the '7747 ecm, Com 6 which checks out as ok and 4800 as my baud. I click START under datalogger with all boxes or just one checked, but nothing happens besides the START button turning to STOP.
Under port settings latency timer has been turned down to 1 for Com 6, transfer sizes are 4096 bytes, and time outs are set to 0.
I have tried connecting KOEO and while the vehicle is running, but it doesn't seem to make a difference.
Am I missing anything? Help would be appreciated, thank you in advance.
#3
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
Where do I need to make sure I have that? In Tunerpro, under data transfer, packet type is set at 160 baud. Directly above that it says Baud 0 (0 = default apparently?)
EDIT: changed baud to 160 and packet type to static and now I get "DA: connected" which is good, but I'm still not getting any data.
EDIT: changed baud to 160 and packet type to static and now I get "DA: connected" which is good, but I'm still not getting any data.
Last edited by chevyracingrox; 01-26-2013 at 08:19 PM.
#4
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
Now noticing I can replicate my results of being connected, but I'm sitting in my house with the cable plugged in to my laptop. Anyone know if that's normal?
#5
Moderator
iTrader: (2)
Re: Trouble Datalogging
Go to gearhead-efi.com and look for the '7747 $42 thread, in there there are known good ADS and ADX files. I use the "7747-Sort" (Or some name that is similar) when I tune '7747 ECMs.
The '7747 does NOT use the 10K ohm resistor to connect, that is used only with the '7165 (early TPI) ECM. Though in some ECMs it will put them into an "ALDL mode" when using the 10K ohm resistor, but it's not a datalogging property, but a way for tech years ago to make sure that the device was connected to the vehicle. Using the 10K ohm resistor will in some ECMs cause the idle RPM to raise to 1200 RPM.
#8
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
I thought TTS was only for 91-94ish trucks?
I tried using a $42-1227747-V5.0.adx and $42-1227747-V3T.adx (I'm using the latest version of TP RT) but still getting the same results, just a different looking dash and monitor.
What else should I check?
I tried using a $42-1227747-V5.0.adx and $42-1227747-V3T.adx (I'm using the latest version of TP RT) but still getting the same results, just a different looking dash and monitor.
What else should I check?
#9
Sponsor
iTrader: (92)
Re: Trouble Datalogging
have you checked the driver installation and device status ?
http://support.moates.net/troublesho...-installation/
http://support.moates.net/troublesho...-installation/
#12
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
Just got done going through checking the drivers and all seems well. Is there a way to check if the pcm signal is getting to the aldl connector? Using my cable on the 10k ohm setting hasn't done anything with the idle.
#14
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
weird, I'm getting 5v testing on E and grounded to A. tried grounding to other nearby screws and such and I get the same results.
#15
Sponsor
iTrader: (92)
Re: Trouble Datalogging
sorry, I guess my eyes didn't focus right. Engine running 2.5v koeo 2-5v.
http://www.gearhead-efi.com/Fuel-Inj...0&d=1331599730
http://www.gearhead-efi.com/Fuel-Inj...0&d=1331599730
#16
Moderator
iTrader: (1)
Join Date: Mar 2002
Location: Chasing Electrons
Posts: 18,409
Likes: 0
Received 217 Likes
on
203 Posts
Car: check
Engine: check
Transmission: check
Re: Trouble Datalogging
Re you getting the SES blink at key-on, engine-off. If not the ECM is likely in limp mode and wont xmit any data.
RBob.
RBob.
#17
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
I'm getting the light on when I turn the key to the "on" position. Kind of hard to see because the SES light and shift lights are very dim.
Still getting 5v with the engine running. This truck uses a 12 pin connector.
Still getting 5v with the engine running. This truck uses a 12 pin connector.
#18
Moderator
iTrader: (1)
Join Date: Mar 2002
Location: Chasing Electrons
Posts: 18,409
Likes: 0
Received 217 Likes
on
203 Posts
Car: check
Engine: check
Transmission: check
Re: Trouble Datalogging
OK, but does it give a 'blink?' And the SES/CEL should not be dim.
At key-on, engine-off the SES/CEL should turn on briefly, blink off, then turn on solid. Can repeat the test after a minimum of 10 seconds of key-off.
No blink-off, the ECM isn't running from the PROM.
RBob.
At key-on, engine-off the SES/CEL should turn on briefly, blink off, then turn on solid. Can repeat the test after a minimum of 10 seconds of key-off.
No blink-off, the ECM isn't running from the PROM.
RBob.
#19
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
Ok looks like I have some electrical troubleshooting to do then. I found out the non-functioning cruise control probably wasn't OE. Found a wire that was haphazardly spliced into a grayish brown wire with a red stripe with a trailer wire connector near the pcm. http://www.etrailer.com/Merchant2/gr...64_tab_500.jpg
Interested as I was to find this, I'm still not getting the SES to blink, turn off, then come on and it's still so dim I can barely see it. I'll try posting some electrical diagrams to help check my work along with what I've tested and where.
Interested as I was to find this, I'm still not getting the SES to blink, turn off, then come on and it's still so dim I can barely see it. I'll try posting some electrical diagrams to help check my work along with what I've tested and where.
#21
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
I believe at one point satan owned this truck then because I traced down a bad brake light issue a few months ago and found one of them to be the culprit.
#23
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
A5 is the terminal for the SES light, A7 is the shift night (not important, but not working), and A10 is the VSS that was spliced.
A5 has no voltage KOEO, but A7 has battery voltage.
I'll put the pcm back in and jumper a and b. IIRC I'm looking for a code 12 right?
A5 has no voltage KOEO, but A7 has battery voltage.
I'll put the pcm back in and jumper a and b. IIRC I'm looking for a code 12 right?
#24
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
Jumper the terminals and got a code 12 and code 51. Its getting dark here in illlinois so the SES and shift lights are easier to see, though still not very bright. Maybe the bulbs are just dim from age or something? Also doesn't make sense that the SES light would work at all if I couldn't get B+ from the harness connector for the pcm. Hmm....
#26
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
51 is a code for a malfunctioning prom, if I remember right. Ok, now that the problem is narrowed down what do I need to look at?
#29
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
it's a 27SF512, I have the solder in adapter from moates.net (G2?) installed with notch toward handle of zif socket
#30
Moderator
iTrader: (2)
Re: Trouble Datalogging
Do you have a non modified ECM you can plug into test?
It's very possible that the EEPROM is not programmed correctly, or the soldered in socket is not making good contact, causing the code 51.
Do you have an EPROM programmer?
#33
Moderator
iTrader: (2)
Re: Trouble Datalogging
I will also suggest removing the ZIF socket, and placing the EEPROM directly in the adapter. It's possible that the ZIF socket is causing issues, or it's not plugged in quite right, which is easy to do with the components you have.
Also, telling us the notch is toward the ZIF handle means SQUAT to us, since the ZIF socket can be plugged in either way.
#37
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
I don't have another pcm, but I have a Burn 2, I use moates guide on burning chips with offsets for 4k file sizes http://support.moates.net/programmin...using-offsets/
#38
Moderator
iTrader: (2)
Re: Trouble Datalogging
I don't have another pcm, but I have a Burn 2, I use moates guide on burning chips with offsets for 4k file sizes http://support.moates.net/programmin...using-offsets/
Do you have the original EPROM? If you do, you can install this in the adapter as well, just move it to the "lower" 24 pins, where there are 4 exposed pin holes at the end of the EPROM where the notch is. The notch should be pointing towards the CALPAK. This will help determine if it is a hardware problem or a programming issue.
#39
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
EEPROM and adapter are oriented with the handle and notch facing like the directions
https://static.moates.net/gmecm/g2/g2-g.jpg
https://static.moates.net/gmecm/g2/g2-g.jpg
#41
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
Got the old EPROM out and installed it without the zif socket. Still getting a code 51. Shall I break out the solder yet?
#44
Moderator
iTrader: (2)
Re: Trouble Datalogging
From the (slightly blurry) picture it looks right.
I think it's time to grab a DMM and check continuity between the DIP socket pins and daughter board itself.
Did you install the 24 pin DIP socket then plug the G2 into it, or did you solder the G2 directly to the daughter board?
I think it's time to grab a DMM and check continuity between the DIP socket pins and daughter board itself.
Did you install the 24 pin DIP socket then plug the G2 into it, or did you solder the G2 directly to the daughter board?
#45
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
The adapter is soldered directly to the daughter board to save space. It's a pretty close fit behind the glove box.
Edit: Seems like I get continuity from the pins to the board.
Edit: Seems like I get continuity from the pins to the board.
Last edited by chevyracingrox; 01-27-2013 at 09:44 PM.
#47
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
hard to say if it ever worked because I've never pulled codes or datalogged this truck. Even the chips I've burned have just been a stock tune until now. Touched up the solder joints and checked my grounds, put the zif socket in and a chip. Still nothing, going to keep looking for stuff to check.
#48
Supreme Member
iTrader: (2)
Join Date: May 2009
Location: Delaware
Posts: 3,371
Likes: 0
Received 1 Like
on
1 Post
Car: 91' Firebird SOLD
Engine: 350 TPI +bolt-ons
Transmission: 700r4
Axle/Gears: 3:42
Re: Trouble Datalogging
hard to say if it ever worked because I've never pulled codes or datalogged this truck. Even the chips I've burned have just been a stock tune until now. Touched up the solder joints and checked my grounds, put the zif socket in and a chip. Still nothing, going to keep looking for stuff to check.
#49
Supreme Member
Thread Starter
Join Date: Nov 2007
Location: IL
Posts: 1,092
Likes: 0
Received 1 Like
on
1 Post
Car: 88 IROC, 76 Malibu Classic
Engine: 350 TPI, 350
Transmission: 700R4, 4-speed
Axle/Gears: 10 bolt ????
Re: Trouble Datalogging
yea this morning I've been experimenting, tried a different bin and a couple other chips. still getting that code 51.