Pre. Collision not available

[Dtuck2]

I have pre. Collision assist not available error on dash. I have dtc codes C1A67 (08) forward looking sensor and also code U0405 (64) invalid data from ccm. Using forscan i successfully recalibrated the ccm, i get the green lines and it hits 100% and indicates calibration is completed. Ive attempted to calibration the ipma, following the prompts i lt goes to 100% however never indicates completed just continues to say something along the lines of radar scan in progress. Doesnt seem to matter how far i drive after. Once i click stop it then says completed but i still have these 2 codes. I did adjust the wheel arch values to reflect correctly. Im at a loss does anyone have any pointers? When I bought the vehicle it had an error front sensor not aligned and had 2 ccm codes and 4 or 5 ipma codes. Ccm had the wrong vin number and also for a max lwb i corrected it and got it mounted properly within the 5 degree window and mine is not a max so changed it to swb. In the ipma it was listed as a right hand drive, i corrected that as well. This is a 2018 expedition platinum with adaptive cruise control. Maybe the previous owner replaced the ccm with one incompatible? My thoughts were maybe a model that didn't have adaptive cruise control, I don't know if the ccm s are different. The ipma camera is secured in place. Maybe if I had oem as built blocks i could verify they are correct. It's obvious someone had been in there messing around. Also curious of the the ccm horizontal parameters.

Thanks

 

[rugedraw]

Check this in the IPMA in FORScan:

706-26-19

xxxx 0xxx xx--

If you have a 0 there, try changing it to an 8 and then reboot the IPMA. This will tell the IPMA it is calibrated. If it does not get rid of the code, then change it back to a zero.

I am not sure where the calibration values are on your IPMA, but on the F150, they are stored in blocks 27 and 28 of the IPMA. You may have to pull the a/b data for a comparable vehicle that has everything working and check the data in those blocks and compare then to yours.

 

[SGM B]

Holy crap - sounds like you are working on the space shuttle. I’m 77 years old and no one (and I do mean no one) has been able to explain to me why my new 2024 Expo has all this garbage installed with the propensity to not work. In 8,000 miles this low grade junk has worked a total of 700 miles. Below are my notices.

 

[OpticonBill]

This response may not be related to your issue with the pre-collision not available error.

I get this error when backing out of my long straight driveway over 7 MPH. If I stay below that speed I don't get the error. The pre-collision seems to be still working as I get the proper warning collision lights when approaching a vehicle making a sudden slow-down to make a right-hand turn. As a system analyst (albeit retired) and software application developer, this appears to be a fault in how the pre-collision module handles and processes input from the sensors and speed module.

 

[Left Coast Geek]

heh, I think I counted 45 separate computer modules on the diagnostic buses of my 2019 Limited Stealth. there's 3 or 4 different data buses interconnecting this stuff.