Car dead after tried to Scan with ForScan

Any issues related to FORScan application
Post Reply
surfix
Posts: 2
Joined: Sat Feb 17, 2018 2:36 pm
Vehicle: Ford Kuga TDCI 140 - 2009

Car dead after tried to Scan with ForScan

Post by surfix » Sat Feb 17, 2018 3:32 pm

Hello everybody,

I come asking for help as i am a little desperate now.
I bought a cheap ELM327 clone, supposed to be an FTDI chip wich finally is not as the FTDI drivers were not recognized when i tried to install them.
Finally it seems to embed a Silicon Labs chip as Windows shows a device named "CP2102 USB to UART Bridge Controller"
So with the Silicon Labs Drivers, the "ELM327" was correctly recognized by ForScan as "ELM327 1.4"

The real big problem came when i tried to plug it in my car (Ford Kuga 2.0 TDCI 140 - 2009)
ForScan told me that the interface seems to be shit (wich is true) and asked me if i wanted to increase speed anyway. I clicked "yes" and the car started to make some strange noises then shutted down. really. The lcd screen behind the wheel shutted down.
When i tried to push the "Start" button of the car, nothing happens !
I plugged down the battery of the car but no changes...
The obd screen just briefly says "key not recognized" and then turns off
I don't know what to do.
If someone could help...

Thanx in advance
Surfix (from France)

surfix
Posts: 2
Joined: Sat Feb 17, 2018 2:36 pm
Vehicle: Ford Kuga TDCI 140 - 2009

Re: Car dead after tried to Scan with ForScan

Post by surfix » Sat Feb 17, 2018 5:33 pm

so i reply to myself :

my car lives again !
thanks to this post http://forscan.org/forum/viewtopic.php? ... 37&p=13755 i checked the battery and.. it was critically low... :mrgreen:
sorry for the unnecessary post but maybe it can be helpfull to someone else.

Before trying to scan : check your battery level !

thanks anyway
seeya soon i think
cheers
SurfiX

denbo
Posts: 191
Joined: Mon Feb 06, 2017 3:00 pm
Vehicle: ford focus 16 zetec

Re: Car dead after tried to Scan with ForScan

Post by denbo » Sun Feb 18, 2018 11:16 am

I tell people all the time to use battery support. By the way no such word as "shuttered" its just "shut". Glad you got it sorted.

andysobdtool
Posts: 1
Joined: Tue Mar 13, 2018 1:00 am
Vehicle: 2005 Mercury Mountaineer , 4.6L

Re: Car dead after tried to Scan with ForScan

Post by andysobdtool » Fri May 18, 2018 2:17 pm

BTW , just an FYI..

The CP2102 is a USB to TTL UART bridge chip , as opposed to the CP2104 , which is FTDI.

I know this post is a few months old..

Glad ya got it running though without too much trouble.

martin123
Posts: 29
Joined: Wed Jul 15, 2015 5:24 pm
Vehicle: transit connect 2003 1.8 tddi

Re: Car dead after tried to Scan with ForScan

Post by martin123 » Fri May 18, 2018 7:23 pm

I asked admin to make a sticky as regards to this issue IE non genuine ftdi chip/driver etc. I think a lot of folk including myself have made mistakes thru this

reachasiri
Posts: 2
Joined: Thu May 24, 2018 4:06 am
Vehicle: Escape 2014 Titanium

Re: Car dead after tried to Scan with ForScan

Post by reachasiri » Fri Jun 01, 2018 3:22 pm

That's scary,
I was expecting something like this but didn't happen fortunately.
Thanks for the post.
Could you get done what you were trying to do?

Post Reply