03-02-2023, 05:34 PM
Hey TweakedNL
I had found since DID reading added to OrBit, the HCMs have some data fields that might be helpful here:
43E0 and E103, the "config parameters used" and "config parameter errors"
Read those from your car and post back here! I've found it's not obvious what exactly is going on. But so far I have learned: 43E0 will tell you what the current parameters the HCML or R is using, should be item 8 (LHD or RHD) and 106 (headlight type) and the current values (in decimal not hex) so you can be sure the values have taken.
E103 is not so obvious...it will tell the "invalid" parameters, but it appears to be a "history" that is not cleared, for example my car below, you can see that the invalid parameters reported are item 106 being "7" (which I set once mistakenly and caused lots of codes) and item 8 being "255" (which is probably a bad flash long ago, FF/255 is an erased memory byte). So it doesn't really show the "current issues" UNLESS those "invalid values" MATCH the current values from 43E0.
From my car:
Anyways I thought it might be interesting to check those values on your car...
I had found since DID reading added to OrBit, the HCMs have some data fields that might be helpful here:
43E0 and E103, the "config parameters used" and "config parameter errors"
Read those from your car and post back here! I've found it's not obvious what exactly is going on. But so far I have learned: 43E0 will tell you what the current parameters the HCML or R is using, should be item 8 (LHD or RHD) and 106 (headlight type) and the current values (in decimal not hex) so you can be sure the values have taken.
E103 is not so obvious...it will tell the "invalid" parameters, but it appears to be a "history" that is not cleared, for example my car below, you can see that the invalid parameters reported are item 106 being "7" (which I set once mistakenly and caused lots of codes) and item 8 being "255" (which is probably a bad flash long ago, FF/255 is an erased memory byte). So it doesn't really show the "current issues" UNLESS those "invalid values" MATCH the current values from 43E0.
From my car:
Anyways I thought it might be interesting to check those values on your car...