Datalogging
Thread Starter
Supreme Member
Joined: Aug 2003
Posts: 1,644
Likes: 4
From: Long Island New York
Car: 89 Formula 350
Engine: Forged 385 H/C/I
Transmission: 700R4-4300 Stall-lockup
Axle/Gears: BW 9 Bolt 3:70
Datalogging
trying to get TunerPro RT to see the ALDL cable. When try to get to it to initialize I get- Hardware not found-not ready-connection failed. In the "tools">"preference">"ALDL/Emulation" I have the interface set to MAX232-Com4(cables in 4)-10HZ with the ALDL able set to 10HZ as well. In the ALDL Setup the Datastream definition is set to 1227165_6E.ads..any ideas why it wont see the cable and connect the laptop to the aldl cable to the ECM?
Joined: Sep 2003
Posts: 25,895
Likes: 429
From: Pittsburgh PA
Car: 89 Iroc-z
Engine: 555 BBC Turbo
Transmission: TH400
Axle/Gears: MWC 9” 3.00
Re: Datalogging
Could be a communication port problem. I have had this happen many times in the past where tunerpro wouldnt recognize the aldl being attached. I had to make sure my usb ports on the laptop were configured right. Sometimes, com4 isnt what the usb connection is using.
Then sometimes, it will say ALDL not found but if i try to connect to the ecm it will! Just need to keep trying different ports.
Then sometimes, it will say ALDL not found but if i try to connect to the ecm it will! Just need to keep trying different ports.
Re: Datalogging
Yup, what Orr89Rocz said. it happens to me all the time I think because I have so many other periphrials that my Comm ports are changing. If you open TunerPro go to tools, then preferences then Data aqa.Emulation and use plug in then configure the plug in set to Comm3 is always the best for me, test it then you can set the other tings where you need them. Restart the program, if it doesn't work leave only your cable plugged in and restart the computer then restart the program. This is usually what I have to do to get all hardwae found and it will stay that way all day until you unplug your cable, plug in a printer or something and restart computer... HTH!
Thread Starter
Supreme Member
Joined: Aug 2003
Posts: 1,644
Likes: 4
From: Long Island New York
Car: 89 Formula 350
Engine: Forged 385 H/C/I
Transmission: 700R4-4300 Stall-lockup
Axle/Gears: BW 9 Bolt 3:70
Re: Datalogging
Tried to get TunerPro RT to connect the aldl cable again with no luck. I have the computer setup for Com4 and its also setup under Tools>Preferences>Com4....If I open TunerPro>Tools>Preferences>Test for valid cable using settings, I get cable found and functioning....... Then if I go into setup>Connect to ECM, or I click on the double blue arrows its says Not Ready-Connection Failed...Then the strange thing is if I go bac to Tools>Preference>Test for valid cable using settings...I get Cable not found or not operational(test 8192 baud)..even though it saw the cable doing the same things before I tried to connect to ECM???? The only way to get it to see the cable again is to close out TP RT and reopen it. Then if I goto Tools>Preferences>Test for cable it sees it again till I try to connect???? Any idea what I'm doing wrong??? Thanks
Moderator
iTrader: (1)
Joined: Mar 2002
Posts: 18,432
Likes: 231
From: Chasing Electrons
Car: check
Engine: check
Transmission: check
Re: Datalogging
Check that there is a 10K resistor between A & B on the ALDL port. That is the only way to connect at 8192 on the '86 - '89 TPI ECMs. Once connected the 10K should be removed (opened via a switch).
With no 10K the 160 baud mode is the only one available.
RBob.
With no 10K the 160 baud mode is the only one available.
RBob.
Thread Starter
Supreme Member
Joined: Aug 2003
Posts: 1,644
Likes: 4
From: Long Island New York
Car: 89 Formula 350
Engine: Forged 385 H/C/I
Transmission: 700R4-4300 Stall-lockup
Axle/Gears: BW 9 Bolt 3:70
Re: Datalogging
I'm using a Moates Xtreme ALDL cable set to 10k ohms. Car is an 89 with 1227165. As for definations I'm using 1227165_6E.ads... Not sure why its saying Cable not found or functioning(test 8192 baud)
Trending Topics
Thread Starter
Supreme Member
Joined: Aug 2003
Posts: 1,644
Likes: 4
From: Long Island New York
Car: 89 Formula 350
Engine: Forged 385 H/C/I
Transmission: 700R4-4300 Stall-lockup
Axle/Gears: BW 9 Bolt 3:70
Re: Datalogging
My AutoProm is almost always found first shot. But if I use my cable it is never found! Even with settings changed to cable instead of AutoProm?
Thread Starter
Supreme Member
Joined: Aug 2003
Posts: 1,644
Likes: 4
From: Long Island New York
Car: 89 Formula 350
Engine: Forged 385 H/C/I
Transmission: 700R4-4300 Stall-lockup
Axle/Gears: BW 9 Bolt 3:70
Re: Datalogging
Sorry, yes it works now but I don't know how he fixed it. You should contact Craig Moates on his site,Moates.net
Supreme Member
Joined: Jan 2001
Posts: 1,047
Likes: 2
From: Lincoln, Nebraska
Car: 1988 Firebird, 2000 GTP
Engine: 327
Transmission: 700R4
Axle/Gears: 9" posi, 4.11
Re: Datalogging
If any of the posters are watching this thread anymore...
After a year of off/on working on this I resorted to TunerPro TR V.4 So far that has got me to this point:
I tried connecting without the 10K resistor so I definately need that added again. It looks like I might just need to look for programs attempting to use the Serial Port which my DIY cable is in.
The difference is that I'm running a '6395 PCM out of a TBI '94 S10. I wanted this so I coudl run an electronic transmission one day as well as have faster ECM speeds for better fuel/spark control.
It appears the issue lies within the PC->PCM link. So either the cable is not working or I am not getting the PC to start the communication.
After a year of off/on working on this I resorted to TunerPro TR V.4 So far that has got me to this point:
Tried to get TunerPro RT to connect the aldl cable again with no luck. I have the computer setup for Com4 and its also setup under Tools>Preferences>Com4....If I open TunerPro>Tools>Preferences>Test for valid cable using settings, I get cable found and functioning....... Then if I go into setup>Connect to ECM, or I click on the double blue arrows its says Not Ready-Connection Failed...Then the strange thing is if I go bac to Tools>Preference>Test for valid cable using settings...I get Cable not found or not operational(test 8192 baud)..even though it saw the cable doing the same things before I tried to connect to ECM???? The only way to get it to see the cable again is to close out TP RT and reopen it. Then if I goto Tools>Preferences>Test for cable it sees it again till I try to connect???? Any idea what I'm doing wrong??? Thanks
The difference is that I'm running a '6395 PCM out of a TBI '94 S10. I wanted this so I coudl run an electronic transmission one day as well as have faster ECM speeds for better fuel/spark control.
It appears the issue lies within the PC->PCM link. So either the cable is not working or I am not getting the PC to start the communication.
Member
iTrader: (3)
Joined: Jul 2009
Posts: 409
Likes: 0
From: Ontario, Canada
Car: 86 IROC
Engine: 350 Vortec TPI
Transmission: 700R4
Axle/Gears: BW 3.27
Re: Datalogging
Those are almost the same issues that I had....it would find the cable, then a second later it would say that there is nothing there......
I was able to finally figure it out. For some reason it was the ecm. I was able to get my hands on a spare and I tested that one out. Sure enough within 2 seconds of me plugging my laptop into the car it started to log. I read around that some people had issues with the '165 ecms, but didn't think that was my issue. Sure enough it was.
Now that may not be your issue, but if you can get your hands on another unit for cheap or free.....then I would test it.
I was able to finally figure it out. For some reason it was the ecm. I was able to get my hands on a spare and I tested that one out. Sure enough within 2 seconds of me plugging my laptop into the car it started to log. I read around that some people had issues with the '165 ecms, but didn't think that was my issue. Sure enough it was.
Now that may not be your issue, but if you can get your hands on another unit for cheap or free.....then I would test it.
Supreme Member
Joined: Jan 2001
Posts: 1,047
Likes: 2
From: Lincoln, Nebraska
Car: 1988 Firebird, 2000 GTP
Engine: 327
Transmission: 700R4
Axle/Gears: 9" posi, 4.11
Re: Datalogging
I'm talking to a guy that runs a Dyno. I think I'm going to try to stop by there since he has just about everything for tuning. I at least want to see if he can connect with it. So, hopeully that doesn't take me months to do but I'm going to keep plugging away at it in my free time.
I'm thinking tomorrow will be a nice day to pull the distributor and prime the oil so it's ready to go for the spring.
That really sucks that the ECM was the issue you found. That doesn't really seem like something that should go wrong with one, but anything is possible. Maybe that's why the truck was in the salvage yard in the first place. It wasn't wrecked.
I'm thinking tomorrow will be a nice day to pull the distributor and prime the oil so it's ready to go for the spring.
That really sucks that the ECM was the issue you found. That doesn't really seem like something that should go wrong with one, but anything is possible. Maybe that's why the truck was in the salvage yard in the first place. It wasn't wrecked.
Member
iTrader: (3)
Joined: Jul 2009
Posts: 409
Likes: 0
From: Ontario, Canada
Car: 86 IROC
Engine: 350 Vortec TPI
Transmission: 700R4
Axle/Gears: BW 3.27
Re: Datalogging
I was lucky, I was able to get an ecm out of a junk s10 with the same ecm number....Other than logging, the ecm ran perfect.
Re: Datalogging
I've been plagued with comms issues.
I will say pictures (screencaps) are worth a thousand words, even if they take 1/2 hour at assemble.
I've got it down to a science:
<Alt-PRINTSCREEN> will only capture the active window...
Start:Run: mspaint<enter>
<Ctrl-V> <ctrl-S> filename<enter>
However I did have some very wonky stuff going on. I had to pull my chip&memcal and replace it to get datalogging to work after it went wonky. And by wonky I mean it only updated MAP and o2 voltage.
I will say pictures (screencaps) are worth a thousand words, even if they take 1/2 hour at assemble.
I've got it down to a science:
<Alt-PRINTSCREEN> will only capture the active window...
Start:Run: mspaint<enter>
<Ctrl-V> <ctrl-S> filename<enter>
However I did have some very wonky stuff going on. I had to pull my chip&memcal and replace it to get datalogging to work after it went wonky. And by wonky I mean it only updated MAP and o2 voltage.
Thread
Thread Starter
Forum
Replies
Last Post









