mraz72

Didn't want to create a new thread...

I was trying FORscan out today (for the first time) and I am getting an error on the one thing I tried to change.

I wanted to add climate to the sync screen, so i backed up the APIM module, attempted to change the 2 numbers needed to change and when I click write, I get the following error

This adapter has CAN bus compatibility issues and cannot be used in some functions. I haven't checked the other modules.

I do have the extended license, the software shows me the extended license is applied and valid

I am going to try to run the software as administrator and see if that produces different results.

I purchased the OBDlink MX (referenced in the beginning of this thread) and I am running a win 10 laptop (Microsoft Surface 3 pro)

Livnitup

Did you have anything else in the truck drawing current during the write process such as fan blowing, etc.? In FORScan settings, connection tab, try putting "Connection Type" to "Bluetooth" if it's on Auto.

mraz72

I did have the stereo on, or a more accurate statement, I didn't turn it off after turning the ignition to on.

I'll try it again with the stereo off (everything off) and also the options you mentioned and report back.

Airborne_Ape

Edit: I made two posts for you, this one and the one under it.

First:
Which OBD link MX? Wifi or Bluetooth?


I have surface pro 4 and have noticed a pile of forced windows 10 updates recently. The only ForScan related issue I've had was on a 2017 Super Duty IPC.

I made a youtube post on how to check and update your adapter firmware. I recall it has been an issue for some people in the past, which may be applicable if you bought a refurb.

Also, sometimes my surface pro 4 will act up like that too and just needs a full shutdown and reboot. Highly doubt your issue is user/admin privilege related.

Airborne_Ape

Oddly enough, Windows 10 will often assign my OBD MX BT to a Comm port and thus selecting Bluetooth in ForScan will make troubleshooting more difficult. I advise selecting AUTO in this case.

Still, I don't think that's even part of the problem considering this user can see the modules and only runs into issues upon trying to write the data. I've hit this issue a few times which I think is a driver fault in the Surface pro, it's probably just a timeout condition.

Whenever I've had this, a full shutdown and restart (of laptop and F150) typically resolves this.

In 2 cases I've had to delete the paired OBD link from Windows 10 and repair the device.

All of us Windows 10 users have had a barrage of forced updates this week from Redmond. Even today on my Surface Pro 4, the very laptop I'm typing this on now, decided to remove its own network wifi adapter after it updated itself while in sleep mode.

So... actually... now that I think about it, that would be my best advice for MARZ72.


Make sure WIndows 10 has installed the updates if any are stuck in que, do a full restart afterwards, forget and re-pair the ODB link MX.

Livnitup

The FORScan developers themselves suggest to people with Bluetooth adapters to change this to Bluetooth from Auto when having issues so I would assume they have a reason why this should be tried.

Livnitup

Unfortunately I haven't found how to turn that high beam indicator off, just the normal headlamp indicator with this value:
720-03-01 4xxx xxxx Headlamp indicator light disabled on cluster

cwcb08

Nothing super exciting today, I'm working my way across 720-04-02 on my '16 4.2 today I did x*xx xxxx &
xx*x xx & xxx* xx
results below

cwcb08

cwcb08