Sponsored
Ford360 - Front Camera - When Parking
- Thread starter Sasquatch2ez
- Start date
- Watchers 10
- First Name
- Jim
- Joined
- Dec 13, 2025
- Threads
- 9
- Messages
- 77
- Reaction score
- 178
- Location
- 20 miles south of the Twin Cities
- Vehicle(s)
- 2023 Bronco Outer Banks
- Your Bronco Model
- Outer Banks
Mine is just to the left of the ASS button.
- First Name
- Kevin
- Joined
- Oct 18, 2025
- Threads
- 15
- Messages
- 338
- Reaction score
- 381
- Location
- Bay area California
- Vehicle(s)
- 2026 Badland 4-dr Manual
- Your Bronco Model
- Badlands
I use the 360 camera a lot when parking, I need to make sure I am not sticking out too far or running over a potted plant. I wish it would come on at say below 5mph and I also wish it would show me where my tires are going, like when I am in 4L where it shows tire tracks.
OP
OP
- Thread starter
- #19
One day, maybe? My friend has a machE mustang and it does it… maybe if I add a few Duracells underneath, it might active it?
- First Name
- Dennis
- Joined
- Mar 10, 2023
- Threads
- 5
- Messages
- 655
- Reaction score
- 1,170
- Location
- Southern LLano Estacado
- Vehicle(s)
- Bronco, Lincoln
- Your Bronco Model
- Wildtrak
The wife's Lincoln turns the cameras on automatically when parking. The Bronco makes you do it manually - a shame, really, but it's only a minor annoyance. After all, I spent most of my life parking without benefit of cameras.
Sponsored
Spent a little time with this today and I'm finding an anomaly. I know some modules have an A and B side to them for data updates so that in case it goes wrong it won't lose its function. I pulled my IPMB As-Built from the cloud before starting to mess with everything, verified my target bits to change and hooked up. Well once I booted in to change the setting, the data presented to me wasn't what I just reviewed. I made what I'm positive is the correct changes but no dice. It's as if Forscan isn't seeing what is actually there, almost like it's getting the dummy side of the IPMB. @rugedraw any thoughts on this? In case anyone else wanted to try, the changes I attempted to make are below.
7B1-02-01-xxxx-*xxx-xx--
Stock value from the cloud As-Built is 4 which means Obstacle Detect Cam View (ODCV) is on in Reverse. There are several options that may work, I tried all three. When viewed in Forscan my initial value was 0 so I feel like my changes weren't actually doing anything.
8 =ODCVSITC PAM_RADAR
A =ODCVSITC CAM_RADAR
C =ODCVSITC PAM_CAM_RADAR
7B1-02-01-xxxx-*xxx-xx--
Stock value from the cloud As-Built is 4 which means Obstacle Detect Cam View (ODCV) is on in Reverse. There are several options that may work, I tried all three. When viewed in Forscan my initial value was 0 so I feel like my changes weren't actually doing anything.
8 =ODCVSITC PAM_RADAR
A =ODCVSITC CAM_RADAR
C =ODCVSITC PAM_CAM_RADAR
Are you saying the ab data you pulled from motorcraft didn't line up with what your IPMB actually shows when you plugged into FORScan?
First thing I would try is when you connect FORScan and it asks if you want to load the exisiting profile, select no so it does a fresh scan and then compare again. As far as the dummy side and AFAIK, that is only used when firmware is being flashed since it uses a write and replace method. I am not a software engineer, so I am not saying that with certainty, but the "b" side should be empty unless firmware is being flashes which is not the case when makign config changes.
Also, the bits to flip to enable ODCV are in this line on the Bronco. 02-01 is on the Explorer and maybe some other Ford platforms. The Bronco spreadsheet is clear on what should be there to change the behavior.
I remember this now. I went through all the spreadsheets for the Maverick, Super Duty and other vehicles and there is no tab for the IPMB at all to compare it to.
The enable disable of ODCV is in that bit, however it’s already enabled. The configuration of the ODCV trigger parameters are what I’m changing ie going from reverse gear ODCV to radar signal. I used the Explorer as a baseline since that’s the module essentially that’s in the Bronco give or take a slight difference. I used to do a little supplier work for ADAS units. I’ll check again though another time. I didn’t know someone decompiled the Bronco into a spreadsheet so that’s good to know.Are you saying the ab data you pulled from motorcraft didn't line up with what your IPMB actually shows when you plugged into FORScan?
First thing I would try is when you connect FORScan and it asks if you want to load the exisiting profile, select no so it does a fresh scan and then compare again. As far as the dummy side and AFAIK, that is only used when firmware is being flashed since it uses a write and replace method. I am not a software engineer, so I am not saying that with certainty, but the "b" side should be empty unless firmware is being flashes which is not the case when makign config changes.
Also, the bits to flip to enable ODCV are in this line on the Bronco. 02-01 is on the Explorer and maybe some other Ford platforms. The Bronco spreadsheet is clear on what should be there to change the behavior.
I remember this now. I went through all the spreadsheets for the Maverick, Super Duty and other vehicles and there is no tab for the IPMB at all to compare it to.
Also yes I remembered to not select any existing profile and load as new and still getting the same results.
Yea, Livnitup made one a few years back using a 2022. Fortunately, he did pull the data from the IPMB for these trucks, so there is something solid to go by.
Do you know where to find it I’m having trouble locating it.
Nvm I found it. Interesting. The LROS data doesn’t seem to correlate for me. I might have to dig up the software and try my own data.
Sponsored
Last edited:
Similar threads
