Unable to detect vehicle type

Discussion about adapters and connections - usage, problems, solutions
Post Reply
Andrew Saunders
Posts: 2
Joined: Sat Aug 31, 2019 5:57 pm
Vehicle: Ford Ranger Wildtrak 3.2 Auto 2017

Unable to detect vehicle type

Post by Andrew Saunders » Sun Sep 01, 2019 1:47 pm

Hi
I have a Usb Elm327 which I can connect to using the Android app of Forscan
software connects to the device but then when connecting to Ranger 2017 Wildtrak an error message is shown

saying:-
unable to connect to vehicle ------ if PCM has a custom tune installed please enter the strategy/calabration name or part number of factory PCM (ex.5l3a-12a650-ayh)
if i cancel still no connection

any ideas
thanks
Andrew

kzimmerm
Posts: 2
Joined: Wed Jun 26, 2019 1:31 am
Vehicle: fusion gas 1.5 2016

Re: Unable to detect vehicle type

Post by kzimmerm » Wed Sep 18, 2019 12:18 am

I have a 2000 7.3 diesel with the same issue. It will not connect to the pcm but obd appears to be working. I have two other vehicles that I have had great results with. Did you find a fix for this?

Andrew Saunders
Posts: 2
Joined: Sat Aug 31, 2019 5:57 pm
Vehicle: Ford Ranger Wildtrak 3.2 Auto 2017

Re: Unable to detect vehicle type

Post by Andrew Saunders » Tue Dec 03, 2019 2:37 pm

Hi
Just picked up your message

interestingly one of the support programmers suggested trying the adapter on the windows version , i have recently resurrected an old laptop on windows xp and downloaded ForScan for windows , this worked straight away so it has to be the driver being used in the android version

my Android tablet is a Samsung Tab a 6 running android 8.1.0 kernel 3.18.14.1295872

will go back to the forum and post an up date

Andrew

barfan
Posts: 1
Joined: Sat Jul 28, 2018 3:40 pm
Vehicle: Mazda3, 1.6 MZCD, 109hp, 2010

Re: Unable to detect vehicle type

Post by barfan » Wed Jan 01, 2020 4:23 pm

Hi,

Got the same problem with a 2019 Mazda3, using 2.3.28 and a OBDlink MX.

I tried with a laptop and with my phone, no difference, unable to detect vehicule type. But I think it's because the vehicule is too "new" and the Forscan database is not up-to-date...

Post Reply