test to see if eec is bad?

[tiresmoke69]

I have been converting over to speed density on my 88 tc. After I got the conversion done I hooked up the laptop to start tuning and my datalogging was not working. I have BE 2010, and QH 1.6, I also have datalogging enabled and a payload saved. When I turn the key on and hit the start button all of the fields that I have selected show up, but they all read zero except for pw1 and hego. Im leaning toward it being an eec problem, it seems that BE is working properly, but there is no output from the eec to datalog from. I am sure that the QH is working properly also, because I can write a tune to the eec and it does make the changes ( I changed the rev limit to test this and it worked ). Any ideas on what I can check to figure out this problem would be much appreciated.

Thanks, Joseph T.

[tiresmoke69]

Also the car does crank up, but immediatly goes dead. If I try to keep it running by pushing the pedal ( in neutral ) it will just surge badly and pop and sputter.

[Stinger]

Are you sure it's writing to the correct location?

[tiresmoke69]

Yes, I have been using BE to datalog/tune when I was using the VAM and it worked fine. Its only after swapping over to SD this happened.

[Stinger]

Typically a bad ecu will not give codes (just a constant buzz), you should try to scan codes.