Datalog for ACT and ECT reading zero

[Diabolic]

My ACT and ECT show zero when trying to datlog my 93 Lightning. I have the Qtr Horse 1.6 with the BE software. I have been talking to Adam Marrer about this, but instead of resting the burden on him only I'm asking publicly. I was datlogging fine and then it froze on ACT of 82º and ECT of 132. Now when I start to datalog they both read zero. I have tried:
1) a new strategy file,
2) new C3P2 calibration,
3) a new datalog payload.
4) I have tried clearing all the tunes in Pos 2 and relaoding 8 new ones.
5)running a degbug file
6)Verified that both sensors are getting a 5 volt refrence signal
7)Verified that both sensors are functioning correctly with a multimeter
verified that the ECT is sending a signal all the way back to the ECM with my multimeter

Truck pulls up no codes except for 511 Prom failure
The truck runs perfect otherwise and will datalog everyrthing else I command it to. I am really stumped. Anyone have other ideas?

[Chucko]

Just a SWAG... have you tried pulling the battery off the QH to let it reset? Good luck.

[Diabolic]

I have not tried that. What all will that effect with my tunes and other things. Will I need to reinstall the qtr horse or anything like that? Anyone ever had to do this before?

[EDS50]

You can try to check your payload to make sure you have them enabled in you datalogging screen and to make sure the levels are selected under the settings tab.

[Diabolic]

Yes, they are selected on my payload. I've created a couple test payloads as well and the same occours. I go into levels and hit unselect all and then reselect all on both pages. Than save agin, and still get a "0" reading for both ACT and ECT. Stumped

[cgrey8]

The only thing I can think of is make sure you are actually downloading/writing the tune each time you make payload changes. For the QH, a majority of the payload items have nothing to do with the tune, but for a select few like MAF, RPM, ACT, ECT, TPS, and a few others, the values must be acquired by having the EEC actively relay those values to the QH, and that required modification of the tune, which BE does for you in the background. But for those modifications to get into the QH, you must write the tune.

[Diabolic]

I'm certain I'm doing this right. I'm doing the same thing I have been doing all along, and it was working perfectly. It just stopped working all of a sudden in the middle of a datalog and hasn't worked since.