data logging problem

[reuben]

I borrowed a cable to log data and something is not right.
I installed winaldl but when all hooked up it only reads the top 3 lines. I only see numbers when in the raw data setting, none of the other tables show anything.
Any ideas? I am about ready to give up on this and go back to a quadrajunk and hei

by the way it is a sbc400 with all parts and pieces from a 91 5.7 pu

 

[Bill USN-1]

My first thought is if you get that frustrated that you are willing to go back to a carb then it May be better that you do.
Most seem to blame every issue they have on efi simply because they don't understand it and don't take the time to learn. So it's just easier to blame it for the problem.

Here's my common speach...
I have never seen a bad efi system, only bad installations.

So now we can move on to your problem.......

you did not provide me with really any info so from the data logging FAQ...

to log data you will need software. For the basic 88-91 GM 1227747 we use winaldl and the associated cable like the one shown at that link.
when you first open it make sure you set the configuration to the 1227747 ECM and your com port selection shows ok.

The important things to look for are;
1. Do you have a 1227747 ECM? If so, what is the 4 letter code on the chip? Could it be a 1228747?
2. Is the correct ECM selected on the configuration page? Do you have the 1227747, 1228062 ecms selected at the top? (assuming you have a 1227747)
3. Did you verify the port assigned in your computers control panel for the usb cable you connected? Under computer hardware/devices it will show ports near the bottom. Then you can click on that and see what port was assigned. If unsure then unplug the cable and plug it back in and the list will refresh.
4. Does that port match the port selected on the configuration page of winaldl?
5. Have you tried to switch between 2400 and 4800 baud to see if it makes a difference?
6. Are you sure your buddies cable is correct for your system?
7. Are you sure your buddies cable is good?
8. The system doesn't care what engine it is bolted to. I think I have proved that with all the projects I have bolted it to.

Good thing for you I will be at the sfr!!!

 

[reuben]

1: yes
2:yes
3:yes
4:yes
5: no
6:yes
7:no
8: I just want to drive

the cable belongs to r290, when I picked it up from him he was having the same problem with only a couple lines being read. I just heard from him that he has a new cable on the way. My truck is finally so close to being drivable I am getting frustrated with little things.

I'll wait for the new cable and try it all again

 

[reuben]

This is the most that ever popped up

 

[Bill USN-1]

the cable belongs to r290

Found the problem...

have you used a led or light to check for fault codes? Just connect to 12v and the ses wire then jumoer pins a and b on the aldl. Turn on the key and count the flashes. Doesn't work if you disconnect the battery or unplug the ECM tho.

Why is logging data keeping you from driving it?
It sounds more like you have other issues if you can't drive it.

Something to keep in mind is that I also sell a direct usb cable for $30. No adapter needed.

 

[reuben]

The check engine light never comes on after I installed the esc and knock. I am still having off idle stumbling issues.

 

[Bill USN-1]

You have a 400 running 350 injectors so did you perform the regulator mod to make it adjustable and increase the fuel pressure to compensate for the difference?
Run it up to the top of the slot and the pressure will be about 15psi.

 

[reuben]

No I have not done that, I will this weekend.

 

[BScoutII]

I started out the same way as rueben. Wasn't getting good/any data. Followed the 8 steps you outlined above and now I'm getting data. You might want to add that to the sticky of data logging.

I had to update the software so I could use com port 5 on my eeepc (the original software I was using only went to 4) and switch to the 4800 baud rate. Working fine now.

My problem is the engine dies at idle. I have some text files of the data, how should I get them to you bill? As the engine starts to die, my tach is acting wild, going from 0 to 5500 in spikes.

Ps you May remember me, you worked on my Scout during the 2011 Sierra Fall Rallye.

 

[Bill USN-1]

What part of the Scout were we working on?

I'll see about updating the data logging FAQ.
Something to keep in mind is you can actually change the assigned port in windows.
Even if it says port 19 you can go into the properties/settings in device manager and change it.
In your case port 2, 3, or 4. I don't use port 1 and normally skip 3. They seem to get used by the computer for printers and such.

You can start a thread here and just attach the files to the post or email them to me.
May be best to attach so everyone else can follow along.

I uploaded a sample log by just hitting manage attachemnts and then uploading the file.

Make sure you have your logger setup properly to get the right data and save the blm table also.
I need both at a min.

 

[BScoutII]

Hi bill, you worked on my fuel injection. Here's what I have logged so far. I ran the engine at around 1800 rpms for a few minutes and then let it go to idle and die.