Forscan applications
06-06-2016, 07:06 AM
#281
Turbo --> :-)
http://www.amazon.com/Factory-Remote...=1&*entries*=0
Sounds like they are using one similar to this that hooks up to the can bus then they are just enabling remote start so it will show in the instrument panel
Sounds like they are using one similar to this that hooks up to the can bus then they are just enabling remote start so it will show in the instrument panel
Nowhere in the video or their website they show a picture of the physical unit, that's why I was thinking it was only a software mod.
The price is attractive at $112.
I called my dealer to see if he could install the Ford remote start later, and he quoted me $599cnd including labor!
If I compare: $112usd + $20 shipping?? X 1.3 = $171cnd... a saving of $430! and I have only one key FOB, not 2. (shorter distance, but it's ok with me)
06-06-2016, 09:32 AM
#282
Not sure if it's in the nav or travel link.. But it gives warning of accidents and lane closures on your route and will direct you around them.. At least I know something is up even if I can't read what it is.. I just hit the middle button to ignore and go see for myself what the problem is.. Most of the time it's gone when I get there. Note I have the factory installed nav
06-06-2016, 10:13 AM
#283
The FORScan Guy
So yesterday I took the as built data for a 2016 Plat FX4 that had all the features as mine but mine is a 4x4 and compared the BdyCM data. I noticed there were only two different values in the whole module so I tried them on mine and noticed errors on my productivity screen about AdvanceTrac & Hill Descent Assist (which my 4x4 doesn't have.) So this only took a few mins and at least allowed me to cross off 2 addresses in the huge BdyCM list of addresses for which we haven't discovered the functions. If my vehicle was an FX4 and I tried the 4x4 values, I may not have seen any errors for this function.
Anyways, this got me thinking to ask if any of you guys testing can think of subtle differences between your own build and another vehicle on the dealer lot you can pull the VIN data from. I think this is the only way we're gonna narrow down the huge # of undocumented addresses in the BdyCM because changing a random address/value is the easy part, finding what is different after the change can be a needle in a haystack. Once we find the function of an address, we can then play with values to achieve a result we're after.
Anyways, this got me thinking to ask if any of you guys testing can think of subtle differences between your own build and another vehicle on the dealer lot you can pull the VIN data from. I think this is the only way we're gonna narrow down the huge # of undocumented addresses in the BdyCM because changing a random address/value is the easy part, finding what is different after the change can be a needle in a haystack. Once we find the function of an address, we can then play with values to achieve a result we're after.
Last edited by Livnitup; 06-06-2016 at 11:07 AM.
The following users liked this post:
k.b. (06-06-2016)
06-06-2016, 11:25 AM
#284
Old Fart
So yesterday I took the as built data for a 2016 Plat FX4 that had all the features as mine but mine is a 4x4 and compared the BdyCM data. I noticed there were only two different values in the whole module so I tried them on mine and noticed errors on my productivity screen about AdvanceTrac & Hill Descent Assist (which my 4x4 doesn't have.) So this only took a few mins and at least allowed me to cross off 2 addresses in the huge BdyCM list of addresses for which we haven't discovered the functions. If my vehicle was an FX4 and I tried the 4x4 values, I may not have seen any errors for this function.
Anyways, this got me thinking to ask if any of you guys testing can think of subtle differences between your own build and another vehicle on the dealer lot you can pull the VIN data from. I think this is the only way we're gonna narrow down the huge # of undocumented addresses in the BdyCM because changing a random address/value is the easy part, finding what is different after the change can be a needle in a haystack. Once we find the function of an address, we can then play with values to achieve a result we're after.
Anyways, this got me thinking to ask if any of you guys testing can think of subtle differences between your own build and another vehicle on the dealer lot you can pull the VIN data from. I think this is the only way we're gonna narrow down the huge # of undocumented addresses in the BdyCM because changing a random address/value is the easy part, finding what is different after the change can be a needle in a haystack. Once we find the function of an address, we can then play with values to achieve a result we're after.
I suggest that those that have the day off today go to your local dealer and start grabbing vin#'s from vehicles, both 2015 and 2016 models, all trim levels. Just tell the dealer you are researching your next purchase.
06-06-2016, 11:35 AM
#285
The FORScan Guy
Last edited by Livnitup; 06-06-2016 at 11:46 AM.
06-06-2016, 11:43 AM
#286
Senior Member
You don't even have to do that. All you have to do is go to any dealer website and browse the models. Most dealers list the VIN # right on the webpage and have links to the window sticker. I use http://www.galpinford.com/ because they are huge and have tons of inventory. Then input that VIN # at https://www.motorcraftservice.com/AsBuilt/Details and you get the as-built data.
The game may be over..
Sure wish they worried this much about the dam seats!
Last edited by Livoniabob; 06-06-2016 at 11:46 AM.
The following users liked this post:
Livnitup (06-06-2016)
06-06-2016, 11:46 AM
#287
The FORScan Guy
I'll edit that previous post with the correct link
06-06-2016, 11:52 AM
#288
Can someone with a Canadian F150 with DRL forced on try the following:
Set the DRL Cluster Control 1 in BCM to enable with FORScan PID or do manually (726-16-02 0101 0101 0049)
AND
Set the following in IPC: 720-02-01 4DE0 3C31 1CE0
This should now give you the option in productivity screen under Settings, Advanced Settings, Vehicle, Lighting for "Daytime Lights"
I'm curious if this is what's needed to be able to disable DRL. I noticed on a Canadian VIN build data this value was 720-02-01 4DA0 3C51 1CC0 and that value made my option for Daytime Lights disappear.
Set the DRL Cluster Control 1 in BCM to enable with FORScan PID or do manually (726-16-02 0101 0101 0049)
AND
Set the following in IPC: 720-02-01 4DE0 3C31 1CE0
This should now give you the option in productivity screen under Settings, Advanced Settings, Vehicle, Lighting for "Daytime Lights"
I'm curious if this is what's needed to be able to disable DRL. I noticed on a Canadian VIN build data this value was 720-02-01 4DA0 3C51 1CC0 and that value made my option for Daytime Lights disappear.
This absolutely works! TVM Livnitup! Previously I managed to turn off my DRL manually through the Forscan program. Now you got it on screen for me! Awesome!
The following users liked this post:
V8-Coyote (06-06-2016)
06-06-2016, 11:59 AM
#289
The FORScan Guy
06-06-2016, 04:19 PM
#290
The 500A package trucks do not. The most common Lariat configuration is 501A rather than the base 500A truck. I think it's because of the price gap between it and the XLT 302A's being so small. I think people who want most of what the Lariat has to offer will get at least the 501A equipment group. The people that don't necessarily want leather will probably opt for the XLT 301A or 302A and save a bit of cash. Similarly, XLT 300A's are probably not that popular either.