Are you able to do this within forscan? I have switchback led's for my turn signal and they are pretty bright at night.

 

I removed the Nav in motion block from sync and noticed I lost the option to call 911 if there is a crash, I left it like that for a day or so. Today I noticed the cross is back and I have an option to create 2 emergency contacts for sync to call. So, I added a new contact in my phone called cops and put 911 for its phone number and used that as the emergency contact #1 for sync to call if there is a crash. If anyone wants to do this its in the "phone" section of sync.

 

Turn signals should only come on when the turn signal is activated. For the running lights, the front and rear are most likely wired to the same circuit, so if you could kill the power the front, you wouldn't have any taillights. If you can find a wiring diagram, you should be able to confirm. It could, however, be done with a relay and some wiring, but I doubt it would be worth the trouble.

 

 

Sounds to me like an issue with the aftermarket bulb. The turn signal portion of the bulb does not get power with the headlights. Turn signal is only powered when the switch is activated (unless you have turn signals set as DRL).

Edit: if your turn signals come on with the headlights, then what happens when you activate the turn signal?

 

I recently used Forscan to activate the backup camera and the factory brake controller. It worked perfectly. This morning I tried to connect Forscan to disable the car finder feature (installing remote start) and I keep getting the error ... Unable to connect to vehicle. Please make sure the ignition key is ON and try again.

This is odd since I'm using the exact laptop and ELM327 adapter that I used to activate the camera and brake controller. Any ideas on how to fix this? Everything is connected and ignition is ON.

 

They are switchback LEDs that I have for the turn signal bulbs. When the headlights come on and the turn singles come on with the headlights it's glowing white. When the turn signals are activated it turns amber. I believe that's how all 2013/2014 F150's operate. I do have the OEM HID's so I'm not sure if that make a difference in how it works.

 

That has happened to me a couple times, and if I shut down Forscan and restart it it usually connects. For me, it seems that sometimes when starting Forscan before the OBD is connected to the computer, Forscan doesn't recognize it when it does connect. Not sure if this is your issue or not.

Ok, I'm not trying to split hairs with the terminology, but the white light that comes on with the headlights isn't the turn signal. It's the running light/parking light. I know it's the same "bulb", but it's 2 separate circuits (and for the OEM bulbs, it's 2 separate filaments). On a the regular bulb, the running light filament is a dimmer than the turn signal filament. When you activate the turn signals, the running light stay on, but the brighter turn signal overpowers it (from a lighting standpoint, not electrical). If you really want to, you can do some wiring to get just the front running lights to turn off with the headlights, but I don't know what the legal implications may be. I think your best options would be to look for a set of switchback LEDs that have a dimmer running light.

 

Thanks, I'll assume you're right. But that thread does not have a clear answer, that's what I referenced in my question. I read a post that was heralded as a clear answer by several people, but it did not actually say anything. I'm assuming lots of beer was involved.

 

That is far from how ALL F150s operate, because only a select few people have added aftermarket switchbacks.