[Jeller]

Anyone know what this represents in the logging? I can't seem to find it written anywhere?

Thanks

Jeller

[OpenFlash]

IIRC, it is just an unimportant debugging parameter used in the development of some boost control function. Nothing valuable to the end user. Many of these un-labelled debug channels represent different things from one firmware version to the next.

Shiv

[Jeller]

Originally Posted by shiv@vishnu

IIRC, it is just an unimportant debugging parameter used in the development of some boost control function. Nothing valuable to the end user. Many of these un-labelled debug channels represent different things from one firmware version to the next.

Shiv

Thanks for your prompt response. Much appreciated

[TenshiWingusu]

Originally Posted by shiv@vishnu

IIRC, it is just an unimportant debugging parameter used in the development of some boost control function. Nothing valuable to the end user. Many of these un-labelled debug channels represent different things from one firmware version to the next.

Shiv

On a similar note, Debug byte 4 which is low pressure fuel sensor on the V5 2.5se hardware is not the same for the V4 Rev 2 hardware. Is there a way for me to see the low pressure fuel sensor data with the V4.R2 hardware?

Thanks

[Jeller]

Originally Posted by TenshiWingusu

On a similar note, Debug byte 4 which is low pressure fuel sensor on the V5 2.5se hardware is not the same for the V4 Rev 2 hardware. Is there a way for me to see the low pressure fuel sensor data with the V4.R2 hardware?

Thanks

Some of the "read me" files have info in them if a particular data set has changed or been reassigned.
I am not sure the answer to your question though... Shiv?