FORScan release notes

[FORScan]

This release contains quite significant volume of changes, here is the full list:

- added support for USB adapters with FTDI and Prolific USB-UART bridges (see Release Notes for additional information)
- migration to core 2.3.0
- added 2 new sizes for gauges ("very big" and "huge")
- added option to change gauge view in Dashboard mode (Text, Dial or Combined), for PIDs that can be displayed in any of these formats
- added Auto-connect option
- added Polish language
- Action Bar is now hidded when parameters are read in Dashboard, Table or Graph modes
- fixes and improvements in gauges and graphs displaying, zoom in/out
- fixed bug of periodic incorrect recognition STN chip based adapters

Some comments:

- added support for USB adapters with FTDI and Prolific USB-UART bridges

- It will work only for devices that have USB host function, also OTG cable is necessary.

- only FTDI and Prolific bridges are supported (we guess these are majority of adapters users have).

- In order to use USB adapter, user has to select USB FTDI or USB Prolific from the connection type list in Settings.

- FORScan is able to detect FTDI baud rate in automated way, but for Prolific everything is not so easy because of limitations of the Prolific USB driver for Android. So user has to select not only type of connection, but also baud rate (USB Prolific 38400, USB Prolific 115200 or USB Prolific 9600). All ELM327 adapters with Prolific chip use 38400, so one should select USB Prolific 38400. Situation is even more complicated for users who has adapters with STN chips and high baud rates (like ELS27). Prolific 2Mbps, 5Mbps and 8Mbps are not supported by Android driver. So these users have to switch their adapter to 115200 (or 38400/9600) in order to use it with FORScan Lite for Android. It would be possible to use 3Mbps or 6Mbps, but these baud rates is not supported by STN.

- Action Bar is now hidded when parameters are read in Dashboard, Table or Graph modes

When data logger is started, the Action bar is hidden. In order to get it back, user has to tap on the screen, and tap once again to hide it.

[FranMex]

Sorry if this was answered before, but I have just bought the Forscan for my Iphone and only realized after that it work only for with WiFi. Will it work with BT in future release ?

[fred08155]

AFAIK the problem is not FORScan - it´s the iPhone that doesn´t work with BT adapters.
See https://discussions.apple.com/thread/3900772?tstart=0
or
http://cartech.about.com/od/Connected-C ... iPhone.htm

[FranMex]

Indeed Fred, I was not aware of this issue. But I'm not surprised, another more reason to get rid of this Iphone.

Tx for the info.

[ng275]

Service function "Read Fuel Injector correction factors" is missing on my Ford Mondeo MK3 2.0 TDCi - 2002. Is this normal (this car does not support this function)?
Only "Change Fuel Injector correction factors" and "PATS programming" is present.
I'm using FORScan 2.3.0

[fred08155]

Service function "Read Fuel Injector correction factors" is missing on my Ford Mondeo MK3 2.0 TDCi - 2002. Is this normal (this car does not support this function)?

Yes this is absolutely normal. On this old model the C2I codes cannot be read out. It is even impossible using original Ford service equipment!
This is no restriction of the software it´s a restriction of the hardware.
Beginning with the facelift models built from september 2003 on there are other components used in the car and reading C2I codes became possible.
Also see http://forscan.org/forum/viewtopic.php?f=6&t=2 where the programming for both versions is explained.

You can read the values from a sticker on the motor if they have never been exchanged or get a dental stick mirror and read it from the back of the injector itself if needed.

[Stesa1]

Hi,
I use the full version Version 1.2.1, i'm happy that works fine with me.
But I miss one PID, REG-DIS, this was no more selectable.
It was a very helpfull PID for me to check the DPF Regeneration interval.
Is somebody here, how has the same problem?

[FORScan]

We have checked v1.2.1 with Mazda CX5 2.2 Skyactive and REG_DIS PID is still there. Please try to clear vehicle cache: Vehicle->Service->Clear Cache.

[Stesa1]

Hi and thank's for the replay.
I clear the cache, nothing was changed, only my before selected PIDs are gone
Could you show me a screenshot from your Android device?
What's next? Any Idea?

[FORScan]

Please check your PM, request for debug info is sent.