I should explain what has occurred. Firstly I was not expecting to find any codes in the ecu as I never once saw the cell light come on. It was only the following day that I wanted to extract the learn block to see how the fueling was in cruise mode. I used our own DST to do this and discovered Code33 set. The DST is reading a different ALDL string to what TP is looking at. DST command is F4 8E 01 vs TP F4 57 01.VL400 wrote:Is code 33 still active or are you viewing the fault history? The logged data in the engine data message is the fault history. The CEL/MIL will only be lit while the fault is active, same operation as a factory bin. It may have been a very well timed fault, long enough to set the code but not long enough to enable the CEL for a length of time that you would see it?
To answer your question VL400 "Is code 33 still active" I will have to ask you how are you determining when a code is active or history.
Again are these stored code active. How would one know if they have been cleared when using using TP or flashing them out.VL400 wrote:Flashing codes via the CEL/MIL is also the stored faults, so code 33 has likely been set and since cleared.
Finally went through all the Logger V2 XDL files and found when code 33 was set. It was when I spun the car but the cell light never came on from that point on. I did have to re-start the engine as it had stalled. Do you think this is why the cell lamp did not come on?
Edit: Sorry I did not read your most recent post before posting this. Your explanation makes a lot of sense. Thanks