CAN signal error either means wiring (a short somewhere) or the camera is not giving good signal. the error coming on right away when you plug in the camera doesn't right away confirm that it's the camera.

i don'tk know where the wiring goes to under the dash, and i'm expecting it to be hard to get to just to verify the wiring from the camera, but that should be the easiest/cheapest thing to verify first. other than getting another camera and just connecting it without mounting it to see if the CAN error goes away. if so, then it will need to be mounted and re-calibrated.

 

I have ordered a used camera from another vehicle- a 2017 Sorento. It's returnable so if it's not the right one or doesn't resolve the issue, I am only out some waiting time, and not any appreciable sum of money.

l will update here with the progress.

In the interim, I am open to suggestions and inputs from the members here.

@ecanderson, any thoughts on these codes and likely culprit?

 

C160646
Means the module didn't provide a 'watchdog' indication that it was still alive, or that information never made it across the bus. To the 'outside world', it looks like the module is locked up. So a faulty ECU for the LDWS or a bad connection or loss of power somewhere.

C180508
Further reinforces the failure above. This one is a declaration of an outright C-CAN failure. Again, we're talking defective LDWS ECU or a problem with the CAN bus wiring.

Neither point to a camera issue. Both will shut down the AEB (autonomous braking) system.

 

What is the best method to troubleshooting this issue? Or am I likely stuck needing a Kia dealership to fully diagnose and resolve this issue?

As I already have a camera from another Sorento on the way, do i need to perform any additional steps, besides calibration of ADAS? My intent was to plug in the camera and see if one or both issues would move to History from Active.

 

I guess we could consider where more likely points of failure could be. Like a doctor who is asked about pain, we first ask about trauma to suss out any obvious origins of the problem.

You say "For some time now..."
For how long, and were there any 'events' that preceded the onset of these failures?

Had you had any major work done anywhere on the vehicle?

 

LDWS and AEB started in May 2025. It was randomly occurring whereby it would illuminate then it would go away. Within a few days of the first occurrence it persisted until it was consistently “on” and has remained this way since.

no repairs. No trauma. No windshield replacements. Camera is secure.

 

The camera itself uses CAN (not a regular video signal) to communicate the video data, so one can hope that something about the camera has got the bus tied up.

 

Update:

• Plugged in the used MFC.
• Cleared the history of codes.
• Did not mount the MFC as I know it requires calibration.
• Scanned for codes.
• No codes found.

I drove around for a bit and turned LDWS “on” and while it can’t see my lane due to lack of calibration, I no longer have either code C1606:46 or C1805:08

Does this confirm a hardware issue with the original MFC? Any steps I can or should take for any additional troubleshooting and diagnosing?

 

Your bus problem is beyond simple online diagnosis, I'm afraid. It now requires the correct tools to be applied in person by someone who knows how to use them.