Originally Posted by Livnitup

After you did the pairing procedure by pushing the button on the front of the OBDLink MX BT, does windows show it under bluetooth devices as "OBDlink MX"? If not, FORScan won't see it.

Originally Posted by Nimrod

Im an idiot. So there is a black button... LOL I'm linked now. Somehow I missed that on the Quick start guide, Thanks!

It listed a lot of modules so Im good I think.

Originally Posted by AllGoNShow

This one is super handy! Appears to work as well;

SecureIdle (Police Option):
Note: Doesn't Allow Vehicle To Shift From Park To Drive Without Passive Key Inside Vehicle (Shifter Locked w/No Key Detected Message)
726-42-01 (2014+ MY) xXxx xxxx xxxx
(BdyCM) 0 (Disabled - Default)
1 (Enabled)

Originally Posted by AllGoNShow

Small update on 'Remember High or Fog settings';
In Auto Mode it will remember the fogs or highs on, If it is still dark out when you restart the truck. If you restart in the day time, the auto light sensor turns your fogs and highs off as it senses light and doesn't need the fogs on. Not a big deal but for guys expecting it to remember 100% of the time, don't use Auto setting.

Originally Posted by Livnitup

Hey guys, just made an account here and am interested in what you find for the 2017s. Some of you may know me from the FORScan thread on the F150 forums but if not, I was given this link by ZooDad. Anyways, just wanted to introduce myself and I'll be keeping up with what you guys find

Originally Posted by Rebelz

New here. First off wanted to thank livnitup for an amazing job on the f150. With that being said I have started testing to see how many of the f150 codes match up to the f250. Looks like livnitup and the others have pretty much paved the way for us. So far I have confirmed that the different boot up screens and global open and close do work. I will keep posting back here as I get more confirmed.

Originally Posted by KubotaOrange76

the info in line 26 & 27 in this spreadsheet https://docs.google.com/spreadsheets...#gid=815852466
is what changed me back from hyper flash. I do not have leds. I tried every fog light/high beam setting on your spreadsheet and they all worked but still with hyper flash, and it was because as a newbie one of the first things i did with forscan was entered the 0001 in the first set of digits based off line 4 of your spreadsheet.

--------------------------------------------------------------------

On another note i was able to get my speedometer within 1/4 mph so far.

factory tires were 275-70-18, i am running 285-75-18 which produced just under 5% off, factory speedo vs gps was dead on with factory tires.

I changed the setting yesterday 6 times to get it corrected.

First try i used this https://docs.google.com/spreadsheets...EqU/edit#gid=0

put my tire size in the top and entered the hex code that it produced. After a few miles at 65-75 mph i noted speedo was about 1.2 mph slow

i entered 70 & 71.2 with my current hex code into the lower table and loaded that produced code into my truck.

Back on the highway now speedo was reading about 1.75 mph fast.

Entered 65 & 67 into the lower table and loaded that hex code into the truck, now my speedo is reading 3 mph fast so i knew for sure i needed to go the other direction, unless i am using the calculator incorrectly.

i went back to the top table and tried 285/78/18 and put that hex code in,
I finally figured out what changed moved it what direction and subsequently used 285/72.5/18 then 285/72/18 to get it very close. I have driven about 35 miles with the last two settings with no DTC's.

The setting that had my speedo 3 mph off immediately produced a DTC related to axle ratio within a few miles.
I am wondering if smaller changes do not produce dtc's, time will tell!

I hope this is helpful to you guys and not too confusing..

Sorry for the long post