|
|
|
|
|
|
Welcome to the Australian Ford Forums forum. You are currently viewing our boards as a guest which gives you limited access to view most discussions and inserts advertising. By joining our free community you will have access to post topics, communicate privately with other members, respond to polls, upload content and access many other special features without post based advertising banners. Registration is simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact us. Please Note: All new registrations go through a manual approval queue to keep spammers out. This is checked twice each day so there will be a delay before your registration is activated. |
|
|||||||
 |
|
|
Thread Tools | Display Modes |
18-05-2021, 08:22 AM
|
#31 | ||
|
FF.Com.Au Hardcore
Join Date: Oct 2005
Location: Auckland, NZ
Posts: 1,266
|
Checked a few things in Forscan. The delay is 16 ms, which the app says is good. Forscan IDs it as V2.2, confirmed by the ELM Identifier app. I have also setup Forscan to connect automatically.
__________________
MB Mondeo TDCi wagon, sea grey, on MAK Invidia 16" wheels. |
||
|
|
| 2 users like this post: |
|
18-05-2021, 09:33 AM
|
#32 | ||
|
FF.Com.Au Hardcore
Join Date: Jul 2005
Location: Melbourne
Posts: 6,928
|
Brilliant! Thanks! Think I'll get myself one.
Forscan takes a bit longer to sync than others, because Forscan will scan all trouble codes at the start. If you read the logs as it connects at the start, it will go through the DTCs for PCM, BEM etc. Thats why it takes a bit longer. |
||
|
|
|
| This user likes this post: |
Re: OBD2 adapter to use with Forscan
Linear Mode
