It was not advertised as used but being an ebay item - I am a bit suspect, also the fact that it is reporting as the wrong part number is not encouraging.

Yes sir - did not load any saved profile

Im attempting to return the part, and looking to source another sensor.

In reading some of the writeups from @mbrick im hoping it is possible to get just the ACC running on a 2018MY without enabling stop and go, adding the IPMI camera, windshield etc. Interestingly enough, the actual distance sensor module identified in his writeup do not appear to be the correct one at least for the raptor.

 

Hi @kevinkk - got your PM and have been reading through.
The 2018 Raptor is equal to a 2015-2017 F-150 with non stop and go based on what I am reading. You can't pick which you want, but instead have to install for what the truck was designed for and I thought the Raptor is on a different refresh cycle.

My work is all with a 2018 and stop and go, so it requires the windshield camera as part of the system.
I think you have the earlier non IMPA (camera) system in the top graphic here? So we'll need help from the folks who pioneered it on the 2015-2017's. Unfortunately I don't have any experience on the 2015-2017 generation hardware/software.

I really don't think it is a Forscan profile issue as others suggested because the CCM shows up and you have ran the calibration. I think you would have been stuck before that, but it doesn't help to check.

I'm wondering if you have a bad or incorrect year CCM. Are you able to verify from a 2015-2017 or same year raptor what engineering P/N you need?
I first mistakenly used a 2019 CCM on my 2018 and it did not work but the DTCs were different than you (but also the system design is differnent for stop and go).

Did you re-try the CCM calibration procedure? I think I had to perform it twice because I didn't understand the process correctly the first time.
Share all of the as built values you used incase you have overlooked something?
Check the VIN hex on the CCM.

I found another forum for an older Ford Edge and the U2100 was solved by entering the correct values in the CCM (in that case it was a new module that was not programmed with as built) even though the calibration was already performed before that. Long shot?

I read another post here that is a tad generic but may help, to reset the GWM? Or re write the CCM.

Post your DTC so we can see which module it is for?

The part number you bought does seem to match the parts list, but I am not familiar enough to know if what Forscan reported is correct.

It's really close... don't give up yet.

 

Really appreciate everyone's suggestions - I have sourced another CCM, and will update the post once it arrives!

 

I agree. Pretty sure your '18 Raptor is same as my '17F150. The CCM I first installed gave me fits, was from F250 and I thought it should work but it didn't. As @mbrick said above 2 important needs right now: patience and show us your error code screen. I'll have to reread my steps and notes but it's worth the work IMO.

 

Happy to report that the new, genuine Ford distance sensor calibrated instantly and works flawlessly. Another happy mod made!

For other MY 2018 Raptor owners, this guide contained all of the correct Forscan modifications, with the following changes to the parts list:

• No Sensor bracket was required as it was already installed from the factory
• No Sensor mounting studs were required as they were already installed from the factory
• The correct sensor for my application 802a package was FL3Z-9E731-D
• The harness that I used was fl3z15k867b, though it came with fog lamp connectors which are not applicable to the Raptor, a more appropriate harness may exist

 

Awesome, welcome to the club! Thanks for keeping us updated.

Did you have any reason to believe the first purchase was not a genuine part? Were any markings different between the two?

 

The first one was definitely an ebay special, had no manufacturer markings whatsoever. Second one was bought from tasca, and was actually motorcraft branded - cost more for sure but worked pretty much right out of the box.

 

Oh, yeah, total junk. I looked at the listing: Brand - Unbranded.
That alone is enough reason not to touch it!

For future reference I have bought the more expensive parts from Superfordparts. When I compared, they were the lowest combined part and shipping cost. Tasca serems to have gone off the deep end on their pricing these last few years.

 

Hi everyone, I’m running into a calibration issue I hope someone can help with.



I retrofitted Adaptive Cruise Control (ACC) into my 2022 Ford Bronco 2-door, and while everything seems connected correctly, I’m stuck on a persistent error. Every time I run the CCM calibration (Calibrate Cruise Control Sensor) in FORScan, it gets to 99% and then stalls indefinitely. Eventually, I cancel it because it never completes.



Here are the only DTCs I’m getting:

• B1433 – Forward-Looking Sensor Alignment: Missing Calibration
  
• C1001 – Vision System Camera: Alignment or Adjustment Incorrect
  

The front cluster screen is stuck on “Front Sensor Not Aligned” and that message never clears. When I activate cruise control, the system menu appears and the ACC bars show up, but it won’t let me set the distance or engage cruise. It just sits there.



What’s working:

• Lane Keep Assist works perfectly
  
• Collision Assist is functional
  
• 360 cameras work great
  
• No other DTCs are showing
  

A few important notes:

• The donor vehicle was a 4-door Bronco, but this retrofit is in a 2-door model
  
• I changed the VIN in FORScan across all relevant modules, including IPMA and CCM
  
• I updated all required as-built data for ACC and related features
  
• The bracket is intact, properly mounted, and the sensor is plugged in securely
  
• I saw some folks mention the wheelbase setting (SWB/MWB) affecting calibration, but I’m unsure if that applies here or how to confirm it
  

Does anyone know what causes CCM calibration to fail right at 99%? Is this a wheelbase mismatch? Or something else blocking alignment? Could the C1001 camera code be unrelated since Lane Keep and cameras work fine?



Any help or insight would be massively appreciated. I feel like I’m close, but something’s off and I just can’t get past this last hurdle.



Thanks in advance!

 

Your system is newer and more complicated than mine w/lane-keep and 360 cameras. However, function of CCM is essentially the same. So my (and many other's) experience is alignment/level of CCM is super important as is the CCM itself.

1. Double check CCM alignment/level as per this thread. If this checks out correct then
2. Purchase new correct p/n CCM.

Most, including myself, couldn't get used or incorrect p/n CCM to work so we had to purchase a new correct CCM to achieve success.