Syvecs Forums

I looked in the manual and at the videos, and could not find an explanation on how to convert the error flag number that is produced by the log to the actual error specified by the "error flag items bit assignments".

I do understand how to set the severity by group, but not how to determine what error flag = which fault.

Thanks!

Open you error flag channel in SView, highlight this channel. On the bottom of the screen will be the decode for the channel. In my case it is the channel syncFault See below bottom screenshot.
In brackets is the hex value of each fault, get your trusty Programmer calculator and from there you can see what bits are active for each fault. In this case Tooth Timeout(6) will be bits 1 and 2 active or 0x06h

That should work..

@littlefella thank you for looking.

I've attached a screenshot with the cursor on limp mode; error flag is 1024 (lambda 2 in my case) and limp mode shows "sensor warning level".

I'm not seeing the decode like yours, maybe I'm missing where to look. Thanks again for the help.

Seems some channels are not in ENUM Can't help sorry, need to ask directly I think, you need a decode document.

EOG wrote: ↑Mon Jun 05, 2023 6:06 pm I looked in the manual and at the videos, and could not find an explanation on how to convert the error flag number that is produced by the log to the actual error specified by the "error flag items bit assignments".

I do understand how to set the severity by group, but not how to determine what error flag = which fault.

Thanks!Sprunki

You're right, it can be confusing at first. To convert the error flag number, you essentially need to perform a bitwise check against the defined 'bit assignments' for each error type. The manual should list out the specific bits (e.g., bit 0 might indicate one error, bit 1 another, etc.). When you see the flag in the log, it’s usually a decimal representation of a binary number. From there, you can use a simple mask to extract which bits are set to ‘1’ and match that to the fault code. You’ll want to be familiar with some bitwise operations here to decode them properly. Good luck!

The individual sensor errors can be extracted from “errorFlagsL” and “errorFlagsH” by using the maths circled in red in the screen shot below.

For the EOP sensor fault example shown the “5” in the maths refers to the 5th bit in “errorFlagsH” which in the “Error Flags Items Bit Assignments” in the ECU calibration is assigned as EOP.

Note that “errorFlagsL” refers to Bits 0 to 15 in “Error Flags Items Bit Assignments” and that the 1st bit is “0” and the 16th bit is “15”.

And for “errorFlagsH” refers to Bits 16 to 31 in “Error Flags Items Bit Assignments” and that the 1st bit is bit 16 and the 16th bit is bit 31.

Once the maths is set up it is a great way to instantly spot any sensor problems in the logging.