Has anyone gotten WINALDL to work with the ECM in an 88 Camaro 305 TBI. It is the only year that got that ECM and I am having trouble getting it to read data. It reads some data, but not rpms or anything useful. Just the first two rows of the main chart.

I got it to work in winaldl, for the ecm type just use the 8746. My only problem that I have is that when it records the data, half of it like below Map, RPM, TPS doesn't log into the .txt file and thats just Raw data. It doesn't even record sensor data. kinda sucks...

I have it on 8746 and its not showing RPM, TPS, MPH, or anything. Just the first 2 lines where it says MW2 and then PROMIDA. Could the cable possibly be bad??

are you talking about the live data or when you record it?

The 8063 xmit list is the same as the 8746 and will datalog as an '8746' in winaldl fine, assuming everything else is working.

In winaldl, there is a flashing counter that shows the bytes recieved for that frame. If its red and some number other then 20 then the pc/cable/ecm is dumping data.

Just viewing live data. It flashes but the number is always 1,2, or maybe 3 nothing higher than that. I got my cable from customefis, do you think I should send it back for a replacement?

im using a usb-serial adapter with my cable. i get all the live data it just doesn't record most of it.

Yea I am using an adapter as well, I am only getting 1 or 2 parts of the info and I don't even think it is correct cuz the PROMIDA keeps changing.

i made a .ads file for TunerPro RT for this ECM and uploaded it to the moates server: 1228063_4D_88_L03.ads

with that you can try it with TunerPro

I tried using TunerPro RT and I am having the same problems. The data that comes up in the tables is completely bogus, like it would say I was doing 194mph and then 4mph all while I just have the key on and not even moving. I have the black wire going to the upper right terminal and the red wire going to the one 4 to the left of it. This is correct right???

i don't know your cable, but if black is ground its correct in pin A

but the 4th from pin A i think is Pin D (which is for reading the Brake module), put it in the 5th, Pin E

Nope, I have it in A and E. Still getting stupid readings. Think the cable itself could be bad?? Is the USB adapter throwing things off?

try it in WinALDL and set the Baud rate to 4800

how many lines in the RAW Data table you get?

I have the rate set to 4800. It mostly gets 1 or 2 lines but every once and a while will jump up to 7 or so. The thing is all the data is completely false. I am gonna try it on my friend's Camaro with an 89 TBI ECU. If it doesn't work on that I may try to exchange the cable for a new one.

thats a good idea - let me know what happens

Nope, doesn't work on my friends car ethier and he has the newer and more common ECU. His is doing the same thing, only reading 1 or 2 lines of data, and that data is wrong. I think the cable may be bad and I am gonna try to get a different one.

the ALDU1 in combination with the CABL1 from moates is a nice one

but yes, like you discribe it, it should be the cable

Customefis is going to swap the cable out for me so in a couple days I should be able to try it again. I'll let you know how it goes.

I tried the new cable from Customefis and that still didn't work with the Radioshack USB adapter so I bought a new USB adapter from Comp USA but that is not pulling any data at all. This is really pissing me off. I am thinking about returning it all and maybe getting that Moates setup. Does that thing work really well?? It would eliminate the need of a USB adapter, but it is kinda pricy.

the moates cable works very well - it's worth the money

Alright, sounds like I am going to return all this stuff and try the moates setup. If that doesn't work I am going to shoot myself, or my car.

Recieved the Moates stuff yesterday and it works great. It is a much cleaner looking setup as well and I love it.

Thanks for all your help guys.