HEX-NET Issue Changing Adaptation

Chimuel · May 5, 2019

I am getting this message when inputting 0 as a value. Note that 0 is a valid and in my case the default value from factory:

Auto-scan and Channel 09 Admap available in the Retrofit thread I started here: https://forums.ross-tech.com/showthread.php?18447-MK7-Foglight-Check-Bulb

EDIT:

I have now updated to VCDS Beta 19.4.0
HEX-NET firmware updated to:
CB: 04504
FW: 0.256
CFB: 0.10
BL: 0.28
DS: 60000057

Eric · May 6, 2019

Just enter 00 for now. I'll see why VCDS is complaining about needing the totality of the channel size (16 bytes) instead of just the required user input (1 byte).

Eric · May 6, 2019

Fixed the error message in source.

Chimuel · May 6, 2019

Thanks for the quick response --is 00 the same as 0 for the CECM? The reason I am setting 0 is to disable the fog light bulb check warning/error checking by setting that adaptation channel to 0 (as recommended by DV52 in my Retrofits thread).

I set it to 00 but I still get the notification pop up on my instrument cluster and in the infotainment car status screen.

Eric · May 6, 2019

Can't speak to what 0/00 is supposed to do inside the CECM firmware, but since it's a numeric, they're both the same as far as the CECM is concerned. VCDS is just being extra-cautious validating your input: it wants to see a double "digit" number even if it's less than 10.

Chimuel · May 6, 2019

Are there plans to fix this so that it can accept a single 0?

DV52 · May 6, 2019

Chimuel said:
Thanks for the quick response --is 00 the same as 0 for the CECM? The reason I am setting 0 is to disable the fog light bulb check warning/error checking by setting that adaptation channel to 0 (as recommended by DV52 in my Retrofits thread).

I set it to 00 but I still get the notification pop up on my instrument cluster and in the infotainment car status screen.

hmm......... odd indeed. As I have said, I was able to stop lamp monitoring on individual Leuchte-sets by changing the "DTC-DFCC" channel setting on my test-bench.

Last suggestion is to also turn-off the Lampendefektbitposition channel (again, by setting the value to "0" ) in each of the Leuchte-sets. Perhaps Uw's point about different firmware versions in our two hex09 modules enforces this additional requirement for your BCM- long shot, I admit

Don

Chimuel · May 9, 2019

DV52 said:
hmm......... odd indeed. As I have said, I was able to stop lamp monitoring on individual Leuchte-sets by changing the "DTC-DFCC" channel setting on my test-bench.

Last suggestion is to also turn-off the channel (again, by setting the value to "0" ) in each of the Leuchte-sets. Perhaps Uw's point about different firmware versions in our two hex09 modules enforces this additional requirement for your BCM- long shot, I admit

Don

No luck with that one... I now have:

IDE04924-ENG115860-Driving light and parking light-Zahl der aktiven Scheinwerfer auf 2 limitieren > in Betrieb lassen
ENG116948-ENG116102-Leuchte12NL LB45-Fehlerort mittleres Byte DTC-DFCC 12 > 00
ENG116949-ENG116121-Leuchte13NL RB5-Fehlerort mittleres Byte DTC-DFCC 13 > 00
Lampendefektbitposition (both LB45 and RB5) > 00

Maybe in the CECM 00 =/= 0?

Eric · May 9, 2019

Chimuel said:
Maybe in the CECM 00 =/= 0?

Ugh, no. Again, we're not sending text, we're sending numbers. The CECM has no interest in how you as a human choose to represent that number.

Chimuel · May 10, 2019

Eric said:
Ugh, no. Again, we're not sending text, we're sending numbers. The CECM has no interest in how you as a human choose to represent that number.

Thanks. In my work, programming large scale energy SCADA systems, a 00 and a 0 do not represent the same thing which is why I kept going down that thought process.

I appreciate the responses! --cheers

HEX-NET Issue Changing Adaptation

Chimuel

Verified VCDS User

Eric

Active Member

Eric

Active Member

Chimuel

Verified VCDS User

Eric

Active Member

Chimuel

Verified VCDS User

DV52

Verified VCDS User

Chimuel

Verified VCDS User

Eric

Active Member

Chimuel

Verified VCDS User