larryo108

iTrader: (1)

You are better off checking this thread. That's where you will find info about the 2014 trucks.

Bugle104

Is there a way to forscan and delete the backup noise on a 24 f150 yet. I had the forscan for my 22 don’t know if the new truck is the same being it’s a power boost

Airborne_Ape

@Bugle104

You mean this? I posted it years ago.
Also as a disclaimer it doesn't cause any errors. Forscan will just show an error for the one connected session when the module is initially deactivated. Afterwards everything is fine. Mine been deactivated since I made this.

Airborne_Ape

I drove a 2014 work. ForScan works fine and you can modify your DRLs but keep in mind your platinum would have had the unique projector head lamps for that model year and the circuit logic is controlled by a different strategy unique to 2014 specifically. You will find the most relevant circuit logic references from old 3rd gen Super Duty forms which had the same BCM. Nothing in this thread really applies to your truck, which is why your lights flash an error sequence.

DCM

Might work if he did the "easy" mode?

efwunfiddy

So...I screwed something up. Haven't been in Forscan in a long while, but did use it without issue to do a bunch of things when I first got the truck (chime/honk delete, Lincoln auto-fold mirrors, extend turn blinks for lane change, kill fake engine noise, DRL mods, etc.). I'm pretty tech savvy and had no issues doing this.

I have a 2015 502A with OEM LEDs and initially set DRLs to parking lights only, but found the halos way too dim. So I changed them to turns+parks, which has been working as expected ever since. Today I tried to revert back to parks only, in addition to increasing the brightness (super duty style), which I didn't realize was possible. Results? DRLs are completely dead, and if I manually set the light switch to parking only I still get headlights. Light switch is in the auto position, DRLs enabled in vehicle settings, truck running, in gear with the parking brake set.

I have the original as-built data saved and also looked up the relevant locations in the Ford as-built database, and they agree...so that's good. And I checked my changes against these references and I think it's all good, but apparently not. I don't want to do a complete BCM as-built restore, because as I said, there are lots of changes I don't want to re-do.

I have gone so far as to compare Ford vs backup vs current using "As-Built Compare", and for the four locations in question, everything looks right (Ford matches backup, neither matching current...but current showing appropriate spreadsheet values). I punted for today (awaiting your helpful replies), but I guess my next move is to put all four locations back to as-built and hope it works per OEM spec, then maybe re-edit.

Getting a little cross-eyed here...what am I missing? Here's my numbers (cs = irrelevant checksum):

726-26-02
As-built: 0000 0000 00cs
Current: 0100 0000 00cs

726-29-02
As-built: 0000 0001 00cs
Current: 0100 0001 00cs

726-45-01
As-built: 0A00 1101 01cs
Current: same (reset from 0A00 7F01 01cs)

726-50-01
As-built: 10cs
Current: 01cs

breakers28

Maybe I don't quite understand.... but look at the possible values in 726-50-01 from Livnitup's spreadsheet.... it appears your current values in 726-50-01 are set to 01xx (or as you put it 01cs). Based on the spreadsheet, that is set to DRLs disabled.
Note: Italics are from Livnitup's spreadsheet

726-50-01 108E Dedicated DRL Lights (LED Light Bars/Strips) - Enables BCM DRL Outputs - C2280F (F-150) Pins 36 (Right) and 40 (Left) <-- this is default value for trucks with stock LEDs
726-50-01 017F DRL disabled
726-50-01 0280 DRL - low beams (default value for trucks with stock halogens) You need to enable all DRL choices at 726-45-01 for these to work
726-50-01 0482 DRL - front fog lamps
726-50-01 0886 DRL - front turn lamps
726-50-01 209E DRL - high beams
726-50-01 40BE DRL - Low Beams and Dedicated DRL (this may get rid of flickering for LED conversions)

Also, it appears you have 726-45-01 set to 0A00 1101 01cs Again, per Livnitup's spreadsheet, you should have 0A00 7F01 01cs The 7F allows all DRL choices.
726-45-01 xxxx **xx xxxx DRL Lamp Mask Cfg *allow all DRL choices=7F

I'd try the 7F values in 726-45-01, and then I'd select one of the options in 726-50-01 other than disabled. It looks like you have the park lamps enabled correctly in 726-26-02
726-26-02 x*xx xxxx xxxx DRL Include Park Lamps: 1=enable, 0=disable

Anyway, that is my 2 cents and what I'd try. Good luck!

efwunfiddy

These are the spreadsheet values I was referencing...screen shot straight from the Google sheet. The 50-01 setting matches the park+turn settings that were working previously.

breakers28

That information you posted is from the common tab of the spreadsheet. If that worked before, you might try re-writing the values to ensure they took correctly. I don't think you'll have any DRLs with 726-50-01 set to DRL Disabled, but that is just my opinion. The values I posted above are from the BCM tab in the spreadsheet. I don't know what else to suggest, other than try what was posted in the previous post. You can always revert back to what you have now, but it might be worth a try. Maybe someone else has some ideas for you. Good luck.

reinharm1959

So I'm was attempting to enable Pre-collision w/eab and employing a CCD (cruise control distance sensor) which I have installed and calibrated successfully however the distance sensor enable in the IPC is not responding and I get the following DTC in the IPMA:

Code: U2300 - Central Configuration

Additional Fault Symptom (:64):
- Signal Plausibility Failure

Status (-6C):
- DTC Maturing - Intermittent at Time of Request
- Malfunction Indicator Lamp is Off for this DTC
- Test not complete

Module: Image Processing Module A

So I was just looking for any expertise/advise on what to try next. I'm trying to figure out if this is a address change/setting or requires and different IMPA altogether.

Thanks for any help in advance