Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Multiple errors in xc40 after autopilot and adaptive headlight mods
#1
Hi All,

Thanks in advance for looking at this!

Trying to troubleshoot an annoying problem with my xc40 recharge (Android, my22). Ever since upgrading the software to 3.3.16 (which I did according to the instructions, first restoring to OEM and then upgrading), I have been receiving two warning errors when I add autopilot and adaptive high beams with Orbit. 


 The first error is "the collision avoidance system is unavailable" and the second is "headlight system is malfunctioning." See attached photos of the errors and the dash. 

At first, I thought this might be a sensor or hardware issue, so in preparation to bring the vehicle into the dealer for service, I again restored the software to OEM. Initially the errors persisted, but by the end of the 20-minute drive to the dealer they had all cleared up. The mechanic spent all day looking for errors and could find none, not even anything recorded in the computer. He went ahead and wiped the computer and reloaded all the software, and the car was working fine when I got it back. 

After a week of driving it OEM, error-free, I again uploaded the autopilot and adaptive high beams mods through orbit. Once again the errors popped up almost immediately. 

Anyone else have this issue? Any ideas on what could be causing the problem? 

Many thanks to everyone for their insights!


Attached Files Thumbnail(s)
           
Reply
#2
Hello, 

I went ahead and pulled the DTC codes from the computer. Perhaps these are of use? 

Thanks everyone!
**OrBit DTC Report for ********** (last read: 2025/02/04 22:29:07)**

ASDM-U2127292 - 2025/02/02
  Invalid Data Received in SteerServoSts- Component Failures- Performance or incorrect operation

ASDM-U261792 - 2025/02/02
  Invalid Data Received in CamFrntFaulty- Component Failures- Performance or incorrect operation

ASDM-U261B82 - 2025/02/02
  Invalid Data Received in CamFrntBlkd- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

CEM-U110082 - 2025/02/03
  Interrupted Communication with Active Safety Domain Master (ASDM)- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

HCMR-U2150078 - 2025/02/02
  Headlamp Control Module swivelling motor Alignment or adjustment incorrect- Mechanical Failures- Alignment or adjustment incorrect

PSCM-U112B87 - 2025/02/01
  Interrupted Communication with Central Electronic Module (CEM)- Bus Signal / Message Failures- Missing message

VGM-U105E00 - 2025/02/03
  IHU Not Connected On Ethernet- -


Reply
#3
Which settings exactly did you change, from what to what?
Reply
#4
(02-05-2025, 07:36 PM)IMAY2023 Wrote: Which settings exactly did you change, from what to what?
Hi!

I used the configurator tab, and enabled level 1 cruise (from the stock OEM setting) and adaptive beams (also from the stock OEM setting) 

I didn't mess with any of the settings individually, as the configurator tab seemed most straightforward.
Reply
#5
I am assuming you have reverted back to OEM after those DTCs and errors. If you have not reverted back to OEM, please do so. 
Then in the configuration TAB. what OEM settings you see in.. 
023 CRUISE CONTROL
238 TOP DAMPING, BRAKES
106 HEADLIGHTS, TYPE
109 ACTIVE HIGH BEAM
Reply
#6
(02-06-2025, 05:22 AM)IMAY2023 Wrote: I am assuming you have reverted back to OEM after those DTCs and errors. If you have not reverted back to OEM, please do so. 
Then in the configuration TAB. what OEM settings you see in.. 
023 CRUISE CONTROL
238 TOP DAMPING, BRAKES
106 HEADLIGHTS, TYPE
109 ACTIVE HIGH BEAM

Hi! Thanks so much for helping me out. Yes, I reverted back to OEM as soon as I saw these errors. They having continued since my initial post.

I finally got a chance to check this today:

023 - 02 With cruise control
238 - 01 Friction brake actuator without top damping
106 - 0B Bending, Type A, w/HCM US/CND High Range
109 - 03 With AHB1 (On/Off), US/Canada Sensitivity

Thx again

I also pulled all the DTCs (including the unconfirmed ones):

**OrBit DTC Report for ************  (last read: 2025/02/09 11:05:42)**

ASDM-U261792 - 2025/02/09
Invalid Data Received in CamFrntFaulty- Component Failures- Performance or incorrect operation

ASDM-U261B82 - 2025/02/09
Invalid Data Received in CamFrntBlkd- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

CEM-U110082 - 2025/02/09
Interrupted Communication with Active Safety Domain Master (ASDM)- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

FLC2-U108B49 - 2025/02/09
Internal device communication- System Internal Failures- Internal electronic failure

HCML-U2133E82 - 2025/02/09
Corrupted Data Received in VehSpdLgtSafe- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

HCML-U2135A82 - 2025/02/09
Corrupted Data Received in VehModMngtGlbSafe1- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

HCML-U2138B82 - 2025/02/09
Corrupted Data Recieved In IndcrOutSafe- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

HCML-U2138C82 - 2025/02/09
Corrupted Data Received In HdlampRiReq/HdlampLeReq- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

HCMR-U2133E82 - 2025/02/09
Corrupted Data Received in VehSpdLgtSafe- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

HCMR-U2135A82 - 2025/02/09
Corrupted Data Received in VehModMngtGlbSafe1- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

HCMR-U2138B82 - 2025/02/09
Corrupted Data Recieved In IndcrOutSafe- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

HCMR-U2138C82 - 2025/02/09
Corrupted Data Received In HdlampRiReq/HdlampLeReq- Bus Signal / Message Failures- Alive / sequence counter incorrect / not updated

PSCM-U112B87 - 2025/02/09
Interrupted Communication with Central Electronic Module (CEM)- Bus Signal / Message Failures- Missing message
Reply
#7
According to messages, you might be low on battery or there is something connected to car messing up the system. 
First thing, we need to get rid of the DTCs. 
Revert to OEM if you have not done so then clear all the DTCs.  Lock the car for about 10 to 15 minutes. 
Get back to car, drive about 10 to 15 minutes then rescan the car, you should not have any DTCs. 

Then, 
Step by step. 
Connect the CAR to orbit and update the profile.  It might ask you to enter CEM and VGM pins after that. So, please make sure you have them handy. 
Let's do the light first. 
Make sure your OEM setting is  106 - 0B Bending, Type A, w/HCM US/CND High Range. 
Change setting 
256 - BENDING LIGHT > with bending High and low beam. 
109 - ACTIVE HIGH BEAM > 05 with AHB2 (adaptive) High beam in Small village. 

write the config to car. Lock the car for couple of minutes then test. Check for the DTCs after driving. 

For the Pilot Assist. 


Check these again. 
238 - TOP DAMPING, BRAKES > 01 Friction brake actuator without top damping. 
314 - ADAPTIVE CRUISE CONTROL VERSION > ?
145 - TRAFFIC JAM ASSIST > ? 
382 = CREEP SETTING > ?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)