I don't know where to turn at this point, but to this board in hopes someone can look at the code and maybe find what's wrong.

Backstory: Last year, my backup camera stopped working. Dealer replaced the camera twice to no luck. Then they replaced some other part, which also didn't fix the issue. They ordered the APIM and that didn't fix the issue either. Truck has been in the shop for the last 2 months almost where they tested wiring, replaced wires, some cables to no avail. Now they're ordering another APIM, but I'm sure that when the second APIM gets here, it won't fix the issue.

Last year, I tweaked a couple settings in FORSCAN pertaining to door locks, but nothing to do with the camera. Then a few days later the camera went out. I used the non-hex editing mode in forscan (the drop down menu one or whatever) for the setting I changed. Perhaps that changed something in the hex code? Its unlikely, but I'm not sure. I'll post all the hex configs of every module below in hopes maybe something did mess up. The modules are listed at the top of each screenshot.

Any help will be greatly appreciated and I'll even donate to whoever will help me fix the issue.

Thanks a lot for any help.

 

Load your as built data back in from Forscan.

 

Doesn't that pull data from Ford servers? From my understanding that data gets updated from the data on the truck so it will be essentially the same data that's there already.

 

As build data should be just that. At this point you have that or the option of finding someone else with the same build that has never modified to compare there as built data.

 

Correct, the name itself implies it was the settings when the truck was built. I provided the AsBuilt for another member on here that was having headlight issues after a collision shop repair and that resolved their issue.

So as caperJ and others have said, review the AsBuilt data for the module you changed. I don't believe it will fix the camera, but at this point it wont hurt anything either.

 

The truck uploads as built data periodically to Ford's servers, so any Forscan changes will eventually propagate. This is why it's critical to make backups in Forscan before making changes. No one knows exactly what triggers the data upload, but it can be as quick as a few days or as long as a month. It won't hurt to do a comparison, but based on the original post, it sounds like his changes are very likely already in the cloud.