Why am I getting "Unable to Identify the Vehicle, Contact Developers"

Can you help me get by this roadblock please?

2018 F250 6.2

 

I wonder if your OBD adapter is the issue?

 

Got the bluetooth OBDLink MX . . . . I think that is the preferred adaptor.

ForScan connects to the vehicle but claims it can't identify it . . .

 

Keep rebooting your BlueTooth MX by unplugging and clicking the little yellow switch, you should see a rapid blinking of the blue light. then also restart your bluetooth on the device your connecting too at the same time. they will connect. HAve you entered your licence code in Forscan? If not, or even try re-entering. It took me a few tries but once connected its easy peasy.

 

Yup, that's the adapter that many of us have and are using. Very strange.

 

The computer and adapter are connected. It finds the vehicle and connects to it. Then it says it cannot identify the vehicle. I looked in the log. It knows that it found a Ford vehicle. It identifies the truck computer module. Then says that it can't identify it.

 

I don't have a 2018 so I am not sure what the exact problem was, but just to confirm - you do have the latest version of Forscan they released that fixed some issue with 2018's - right?

 

I downloaded from their site today. 2.3.13

Is there another version?

 

latest one i know of:

Download FORScan

February 2, 2018 - FORScan for Windows version 2.3.13 beta is released
Vehicle database update. New functions, fixes, improvements.

maybe there is some info on their forums:
http://forscan.org/forum/viewforum.php

 

Thanks. I finally sent my log to Forscan. We'll see what happens. They did respond and wanted the dump.bin file also.

 

I had the same issue and did what mhoefer suggested, but I also turned the truck off and stated over with the BT sync.

 

Just got a response that my vehicle is too new. They said it will be fixed in about 3 days. They've been VERY responsive!! Hope the fix will work.

 

 

Try posting in the Forscan support forum itself. I did a quick Google search, several topics come up.

 

I don't see that forscan has released a new update yet. Are you still waiting to get this issue resolved?