22+ Expedition FORSCAN - Warning

[m3olsen]

.... I use an OBDLink MX+ most of the time.

I meant to ask: how are you liking the MX+? Would you spend the money for it if you had to do it all over again? I'll start with the OBDLink EX corded for programming. MX+ only runs with Forscan Lite, correct?

 

[LokiWolf]

I meant to ask: how are you liking the MX+? Would you spend the money for it if you had to do it all over again? I'll start with the OBDLink EX corded for programming. MX+ only runs with Forscan Lite, correct?

You can do all the coding you want with the MX+. I attach it to my Windows Tablet and do 95% of my coding with it. Works great. If I am really poking around or when I was messing with the APIM Firmware I used the EX. The MX+ stays attached to our Expedition pretty much 24/7. I use it with the FORSCAN app on my iPhone for monitoring, and then pair with laptop for coding.

 

[m3olsen]

You can do all the coding you want with the MX+. I attach it to my Windows Tablet and do 95% of my coding with it. Works great. If I am really poking around or when I was messing with the APIM Firmware I used the EX. The MX+ stays attached to our Expedition pretty much 24/7. I use it with the FORSCAN app on my iPhone for monitoring, and then pair with laptop for coding.

@LokiWolf that's awesome! I was guessing that Lite only let you monitor settings and not make any adjustments.

 

[Andy B]

The big thing that EVERYBODY needs to remember. Ford is NOT keeping the programming and module config the same in a generation or even a model year anymore. That is proven by the fact that the 18/19's programming is different than the 2020's, and the 2021's even have a few small tweaks. With the chip shortage, Ford is making more changes even more often. On the 21+ 150's we are seeing changes after updates. Not only does the module matter, but the version will too. I haven't seen the modules on a 22 Expy yet, but I expect them to more closely match the 21+ 150 than the 21 Expedition. You change a bit based on previous coding, and if you did not back up, you could be REALLY sad. There is nobody that I am aware of mapping differences between the versions in this community, like there is in the 150's. With Russia and Ukraine and the FORSCAN developers being in Russia, there is risk of less and less support(They can't get paid). If you are on a 22, be very careful of the changes you make, and BACKUP before every change.

Thank you so much for this warning.

 

[kenny1629]

They can! Assuming you are talking about the Instrument cluster, and not Sync. You might need to contact FORSCAN support and get a Beta link. We can do it on the 21+ 150's and it is in the drop downs for the IPC. I am currently using a Beta, an older one, but it works on my 150, and is still a newer version than the current release version. If you are talking the Sync Screen it should be doable also...just haven't done it, but the 22 150's lost the knob display and have the zone temps on Sync.

What can.beta fordscan do more then regular fordscan?

 

[LokiWolf]

What can.beta fordscan do more then regular fordscan?

You would have to look at the release notes. If you pay for a FORSCAN license you have the option of logging into the Forums and downloading the Beta installer.

I typically always run the Beta's, but I have been using FORSCAN a LONG time. Also, FYI the product is FORSCAN not forDscan, no D.

 

[rugedraw]

What can.beta fordscan do more then regular fordscan?

The beta version allows you to flash firmware. This is NOT to be used to update modules......FORScan themselves warns you against doing so. You cannot trust FORScan to pull all the files or even the correct files from Ford's servers. This should only be used if absulotely necessary and it is always good to source the files from someone who may have them instead of relying on FORScan to get them. However, with the cybersecutiry changes that Ford made last year, it is very difficult to source files anymore. If you need to program modules, the right way to do it is with FDRS if you want to avoid bricking the node.