Member No. 1

Ok so I took the plunge and decided I wanted to be one of the "cool" kids and adjust some of the module values to enable some features. However, while mostly
successful, I have observed some unwanted side effects. As recommended, I did back up all the As Built modules. I started out with a few of the more
popular easy ones, so here is a list of what I changed and the side effects.
Thoughts, insite or help as to why I might be getting the unwanted side effects would be much appreciated. If all else fails, I will restore the As Built settings and start
from scratch.

Temp above gages - Worked, no issues

I restored BCM to As Built before I tried these mods again.

Bambi Mode - Worked but now I have a indicator that looks like a headlight with and A in it that is left of the headlight on indicator. If I turn the Hi Beams on with the
lever, the indicator goes out, and the auto hi beam doesn't work. Turn them off with the lever, they return to being auto hi beams. Is this how they are supposed to operate?
BCM 726-27-01 xxxx xxx0 xxxx Bambi mode without high beam/fogs remembered after ignition off/on - Loaded this and my issue is corrected.
BCM 726-27-01 xxxx xxx0 01xx Bambi mode with high beam/fogs remembered after ignition off/on - This cause my issue

Auto fold mirrors Lincoln style - Worked, no issues

Auto tilt in reverse - Does not work, need to investigate
Tried setting this up several more times, seems to be working now. However, they still do not auto fold when you put the truck in R.
I had to press a mirror button for them to fold.

Double honk on exit - Does not work. Note: Before mod, it only beeped sometimes, and when I locked the doors with the remove, the horn never beeped.
After the reset and reprogram, this seems to be working

When I auto started the truck this morning, it started ok, but none of the outside lights (tail, front marker, puddle, etc..) were on. I unlocked the truck with the remote
and the lights did turn on. When I got to work, I stopped the truck and got out and locked it. I restarted it with the remote, no lights. Unlock with the remote, lights came
on. Relocked with the remote, lights go out. Stopped the truck with the remote. Any ides why?
Working correctly - See Bambi Mode for notes.

TIA for your time.

Dutchrudder7

Hey guys,

I upgraded to Sync 3.4 in my 2017 XLT 301A using a second hand 4d tech harness.

I have one small but annoying issue I think is programming related and I’m hoping someone can point me in the right direction. When I make a phone call through CarPlay or sync the radio or Sirius begins playing instead of the audio from my phone. As it stands I have to use my phone speaker to make phone calls.

Thanks in advance!

Sven150

This just changes the time it takes for the lamp to fade/dim from full bright to dark or vice versa.

fullyford

Haven’t messed with it for a bit. But has anyone figured out the Canadian DRL. How to shut the low beam off. I got the amber halo turned on. And that’s all that I would like turned on.
also is there any way to turn off this notification of my cell reconnecting every time I get back in the truck.

Livnitup

As an example of this see the picture below....a firmware flash gone wrong

Mlarv

I don't know I sort of like the look(-;

C17chief

Can you blind flash any of these modules with failed flash but still get power like that IPC...like you can with some failed pc bios’s? I’ve already flashed the few modules I wanted updated in mine and all turned out well, but as I was doing them, wondered if it decided to fail midway thru if it was 100% the end of that module or if there would be at least some chance of bringing it back to life.

Livnitup

It would depend on whether the software you're using for the flash could communicate with the module and determine the h/w part # of the module or if that was messed up when the flash failed as is often the case - IDS/FDRS & FORScan doesn't give any advanced methods for recovering a dead module. Some software will have a Hail Mary attempt to deal with dead modules where you can give the hardware p/n of the module and try to see if the module will respond to the SEED keys sent by the software but this often doesn't work and the module would be basically declared dead at this point.

jamie75

UCDS can. I used it on a failed door module. You load the sbl and vbf files do forced programming, enter the HW ID. Start and it tell you to remove power from the device and reconnect within 15 seconds. Worked for me

urbino

Okay, guys, I'm sitting in the truck with everything hooked up. I'm trying make my backups. I'm in the APIM module, but when I click save all and name the file, it says "Unable to save log".

What gives?