More messages but no more actual info,
I see a lot more actual info. Lots of stuff which wasn't tested before.
if not intermittent is not it.
Sorry, I dont't understand.
First acqProcThermistor is tested without an answer.
Since diag continues there can be a Thermistor error with same result.
A broken thermistor will probably not stop the communication between
the two CPUs. It might come back with 0x00 or 0xFF (or whatever the
ADC range is) but not with nothing.
Next trigGtlRegisterDiag is tested with the same no answer result.
Now diag can assume it's something else since Thermistor and GtlRegister are too different.
It of course can also be just a counter.
Yes, that's possible. It might say: When the first two tests (where the acq cpu
is involved) fail so miserably, there must be something seriously wrong and
decides to not go on. It also might have kicked off trigGtlRegisterDiag before
acqProcThermistor had come back.
Honestly, I don't care ;-) Fact is, that console adapter and these error messages
helped me to find and fix the error within 30 minutes. Before I was too heavily
focussed on that 7-segment display and that took me more than 30 minutes...