What's new
CK5
Register an account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members.

Can't seem to log data... WTF? Point me in the right direction?

scouthead

scouthead

1/2 ton status
 Premium
Joined
Feb 24, 2007
Posts
3,466
Reaction score
4,548
Location
Long Beach / Joshua Tree
Can't seem to get WINALDL to work. Have tried a bunch of things off and on over the last couple months and still not working. I bought a cable premade. Has the resistor built into it. Does not seem to make a difference with or without the resistor jumped.

When trying to data log...
I can see some sort of data streaming across the first few rows of the "raw data" tab. "WM2", "PROMIDA", and, "PROMIDB" always seem to show something going on, but that's about it. Once I saw a few numbers in another row or two...

The little box next to the "configuration" button always flashes red and has some sort of number in it - mostly a 1, or a 3. From what I've read, this means that the info coming into the program is "incomplete"... hmmm... What?

All the saved files I have logged contain only zeros... ??

And should the "DASH" actually show something when I click the button? I see values for speed, rpm,tps, o2, and kpa. I have never seen them move from zero.

I have tried two different laptops, and the program has done the same damn thing every time...

There is either something wrong or I don't have the program set up right.
??????????????????????????????????????????????????????????????????????????????
 
The most common problem is a bad serial to USB converter. These converters are flaky at best, I've had the best luck with finding an older laptop with a serial port. If you have to run a converter then the Belkins seem to be the most reliable, but that's not saying much.

If that's not your problem make sure you're using the correct definition file for the computer you're running in your truck. I.E. using $42 definition for a 1227747 computer etc.
 
My laptop is an older dell with a serial port. I bought it just for datalogging. My Cable is a usb though. Uses com port 4 on my computer, but the program goes up to com 14...
Maybe I'll have to scrounge up another cable...

I have the 1227747, 1228062 selected in the "ecm type" window in the configuration section. Is there another way to change the defnition on the program?

My computer is a 1227747, but... not the origional out of my truck...
It's an '88 blazer - 5.7L/sm465. The stock computer got F'd up somehow when I put a TBI chips chip into it... I Put my stock chip back into a 1227747 from an '89 with a 700r4 auto. Hope the year and tranny difference aren't an issue. I was under the impression the computer was the same except for the prom.
 
Have you tried using another program, like tunerpro RT for instance?

Doesn't sound like a software issue, however tunerpro is a lot newer than winALDL and perhaps has some "fixes" in it that might help the USB issue?

I too have seen lots of posts with issues re: the USB adapters, but it seems a waste to get a new cable on the assumption it's the USB issue.
 
Sounds like you're having the same type of problems I am with my setup. (regular Dell laptop, and a premade USB to ALDL cable) Please post up if you find a solution!
Thanks!
Chad
 
I bought my USB/ALDL cable a while back and i'm about to see if it works tomorrow. I have a Dell inspiron 1525 laptop so we'll see what happens. It's been a long time since i've played with the winALDL program so if any of you guys can give me any tips on what i need to have the settings on would be a help. Do i want US or Metric (assuming US) and do i want to set the LOG data on RAW Data, Flag Data, Sensor Data, or Error codes? Again i'm assuming either Sensor Data or RAW Data. How about on the configuration do i want 2400 or 4800 Baud? Again assuming 2400.
 
Ok, i played with winALDL today and at first i couldn't get anything to show up, as it turns out if you have a serial cable you need to have the setting on 2400 baud but if you use a USB cable it needs to be set for 4800 baud.

The dash should have numbers in all places and if you choose US then it will read correct speed otherwise it is measuring in metric form. At first i did not get any readings either and unfortunately i don't remember what i did to fix that problem. I was having a problem where when i saved my data it actually wasn't being saved to my computer so i uninstalled winALDL and then reinstalled it and it works perfect now.
 
Just got my usb cable today and am having the same problems :confused: Tried a ton of different things and setting but no help :mad:
 
Go into the configuration and change the baud to 4800 and it should start working. The 2400 baud is for a serial cable.
 
Well I changed all my settings to 4X4HIGH's recomondations and everything appears to be working now. How about that. The DASH even works now. THanks!
I'll have to do some reading because all the numbers I have now don't make much sense to me. I'll have to post up a couple stored logging sessions when I get the chance.
 
Glad it worked for you. I will now be burning my own chips come tuesday when my hardware arrives. :D
 
DO you have any expeirience burning chips or are jumping in blind? A friend offered to lend me his hardware to start burnung chips, but then I would have to burn chips for him when he's got projects in need... sounds like fun, but more time than I have to burn right now.
 
I'm jumping in blind. I have been playing with the tunerpro software for a few weeks and i borrowed a reader/writer from a friend so that i could at least read some chips and look at all the different areas of the chip that can be adjusted or altered. I really need to find someone who knows what all the acronyms mean and is willing to help me understand them. I think once the meanings are understood it will be a piece of cake.
 
Perhaps start a thread?

Going to have to learn MAP TBI for my dads 454 TBI swap, and at this point I know very little about it.

Don't really know much about MAF TPI in the grand scheme of things either compared to many lol. :)
 
Scott,

Send me a PM or start a thread and I'll be more than happy to walk you through most (there are a few that I still can't figure out) of what you need to know, and show you where to start to correct certain problems etc.
 
Well my first discovery is that winADLD only reads pin E on the 160 baud. My ECM is pinned for the M 8192 baud so I downloaded TunerPro RT.

I guess I start logging my old motor when the cable gets here to get an idea of what I'm looking at.
 
Is that an 8192 baud ECM, or simply putting 160 out on that pin?

I know on my TPI setup, pins E and M are spliced together, so I can get 8192 on either one. But the important part is that 8192 is better than 160.
 
You must log in or register to reply here.

Latest Posts

Top Bottom