How to program Central Configuration using FORScan

[FORScan]

Yes, this sounds like adapter problem.

FORScan makes a test of adapter and tries to estimate it's ability to perform complex operations like writing to ECU. If test is not successful, FORScan runs cruical procedures in read only mode (or refuses to run them at all). Most likely, your adapter passes the check but not always (roughly in 50% of cases). For Fiesta familty it is not critical, because if FORScan is unable to write the block, nothing will happen (except that configuration will not be changed).

It would be great if you sent us logs from this session for analysis. It seems we need better adapter tests.

[FrancYescO]

Yes, this sounds like adapter problem.

FORScan makes a test of adapter and tries to estimate it's ability to perform complex operations like writing to ECU. If test is not successful, FORScan runs cruical procedures in read only mode (or refuses to run them at all). Most likely, your adapter passes the check but not always (roughly in 50% of cases). For Fiesta familty it is not critical, because if FORScan is unable to write the block, nothing will happen (except that configuration will not be changed).

It would be great if you sent us logs from this session for analysis. It seems we need better adapter tests.

what log are you searching for? Haven't find nothing in the logs more than what i posted...

So basically there is no risk if comunication get interrupted during write on fiesta? (Could you explain more? fallback memory? Waiting for the final "verify-OK"?)

EDIT: this is probably the log you was searching for: http://pastebin.com/raw/fXHzJCiQ let me know if you need more

[FORScan]

So basically there is no risk if comunication get interrupted during write on fiesta? (Could you explain more? fallback memory? Waiting for the final "verify-OK"?)

Hard to explain, it is so just by design,

EDIT: this is probably the log you was searching for:

yes, but we also need the second file, instruction is sent via PM

[FORScan]

Thanks for the logs.

As you know, ELM327 is some kind of amateur level adapter, designed for simple OBDII operations. In order to perform some complex service operations, FORScan has uses special "emulation" mode. For such mode of work adapter's minimal response time is critical. Minimal response time is a bottleneck of BT adapters, china ones have 20-40ms avg. That's ok, but main problem with BT adapter is stability. You can see minimal response time in FORScan.log. Sometimes it is fine:

Code: Select all

11:52:46.802 [ELM327 Adapter] Profiling: 32 ms
11:52:49.835 [ELM327 Adapter] Profiling: 33 ms
11:52:52.868 [ELM327 Adapter] Profiling: 33 ms
11:52:55.901 [ELM327 Adapter] Profiling: 32 ms
11:52:58.933 [ELM327 Adapter] Profiling: 32 ms
11:53:01.970 [ELM327 Adapter] Profiling: 36 ms
11:53:05.009 [ELM327 Adapter] Profiling: 39 ms
11:53:08.043 [ELM327 Adapter] Profiling: 33 ms
11:53:11.077 [ELM327 Adapter] Profiling: 33 ms
11:53:14.110 [ELM327 Adapter] Profiling: 33 ms
11:53:17.146 [ELM327 Adapter] Profiling: 36 ms
11:53:20.181 [ELM327 Adapter] Profiling: 33 ms
11:53:23.213 [ELM327 Adapter] Profiling: 32 ms
11:53:26.249 [ELM327 Adapter] Profiling: 36 ms
11:53:29.283 [ELM327 Adapter] Profiling: 33 ms
11:53:32.315 [ELM327 Adapter] Profiling: 33 ms
11:53:35.355 [ELM327 Adapter] Profiling: 40 ms
11:53:38.390 [ELM327 Adapter] Profiling: 33 ms
11:53:41.422 [ELM327 Adapter] Profiling: 32 ms
11:53:44.459 [ELM327 Adapter] Profiling: 38 ms
11:53:47.498 [ELM327 Adapter] Profiling: 38 ms
11:53:50.532 [ELM327 Adapter] Profiling: 33 ms
11:53:53.567 [ELM327 Adapter] Profiling: 34 ms
11:53:56.600 [ELM327 Adapter] Profiling: 32 ms
11:53:59.633 [ELM327 Adapter] Profiling: 32 ms
11:54:02.666 [ELM327 Adapter] Profiling: 33 ms
11:54:05.701 [ELM327 Adapter] Profiling: 34 ms
11:54:08.735 [ELM327 Adapter] Profiling: 33 ms
11:54:11.775 [ELM327 Adapter] Profiling: 41 ms
11:54:14.825 [ELM327 Adapter] Profiling: 49 ms
11:54:17.859 [ELM327 Adapter] Profiling: 32 ms
11:54:20.891 [ELM327 Adapter] Profiling: 33 ms
11:54:23.927 [ELM327 Adapter] Profiling: 34 ms
11:54:26.960 [ELM327 Adapter] Profiling: 34 ms
11:54:29.996 [ELM327 Adapter] Profiling: 34 ms
11:54:33.039 [ELM327 Adapter] Profiling: 43 ms

But sometimes it is not:

Code: Select all

11:54:34.672 [ELM327 Adapter] Profiling: 103 ms
11:54:34.773 [ELM327 Adapter] Profiling: 101 ms
11:54:34.942 [ELM327 Adapter] Profiling: 169 ms
11:54:35.070 [ELM327 Adapter] Profiling: 129 ms
11:54:35.133 [ELM327 Adapter] Profiling: 63 ms
11:54:35.187 [ELM327 Adapter] Profiling: 54 ms
11:54:35.343 [ELM327 Adapter] Profiling: 156 ms
11:54:35.434 [ELM327 Adapter] Profiling: 91 ms
11:54:35.544 [ELM327 Adapter] Profiling: 109 ms
11:54:35.647 [ELM327 Adapter] Profiling: 103 ms
11:54:35.694 [ELM327 Adapter] Profiling: 47 ms
11:54:35.740 [ELM327 Adapter] Profiling: 47 ms
11:54:35.853 [ELM327 Adapter] Profiling: 113 ms
11:54:35.943 [ELM327 Adapter] Profiling: 90 ms
11:54:36.006 [ELM327 Adapter] Profiling: 62 ms
11:54:36.105 [ELM327 Adapter] Profiling: 99 ms
11:54:36.211 [ELM327 Adapter] Profiling: 106 ms
11:54:36.312 [ELM327 Adapter] Profiling: 102 ms
11:54:36.453 [ELM327 Adapter] Profiling: 140 ms
11:54:36.516 [ELM327 Adapter] Profiling: 63 ms
11:54:36.619 [ELM327 Adapter] Profiling: 103 ms
11:54:36.723 [ELM327 Adapter] Profiling: 104 ms

Delays before 30-40ms are fine, should cause no problem. Delays up to 60 ms is something that should work about ok. Delays over 90-100 ms are a problem, service requests will most likely fail. Lines above are taken from the logs you sent.

[Chelious]

hey what is the funktion bhind the option at german forscan for a ford mondeo mk3 telling like " seitliche blinkleuchten" at the configuration from the gem (bcm) ?

best regards Steve

[Kethav]

Is the Central Configuration already avaiable on Forscan with the Focus MK3.5 ?

For the Focus MK3 there were the FoCCCus software which had a lot of parameters, but for MK3,5 Forscan is the only possible way...

[FORScan]

CC procedure for Focus Mk3/3.5, Mondeo Mk4, Galaxy/SMax, Transit , Kuga and few other models is still in work/testing.

[radkor]

Hello,
thanks for adding configuration programming option!
Now i Can configure my GEM and IC on Mondeo MkIII (2006r, gasoline).
I succesfully added "instant. fuel consumption" to average consuption, and succesfully disabled audible snow/frost warning with orange/red snowflake.
ACM (audio) configuration works too.

Unfortunately RCM (SRS airbag) configuration isn't working.
My SRS module informations:
Part number: 4S7T-14B056-AC
Software version: v3 2002-06-26

BTW. If RCM configuration works, is it possible to clear "crash data" on SRS module like IDS can (up to 5 times)?

BTW. What's "ESPIVD" on IC configuration?

[FORScan]

Unfortunately RCM (SRS airbag) configuration isn't working.

We are aware about this issue. RCM module requires special procedure to get access to the configuration, it is not implemented yet.

BTW. If RCM configuration works, is it possible to clear "crash data" on SRS module like IDS can (up to 5 times)?

We are not aware about existence of this function for Mondeo 3.

BTW. What's "ESPIVD" on IC configuration?

As far as we know, this flag means ESP availability (ESP light on IC).

[radkor]

BTW. If RCM configuration works, is it possible to clear "crash data" on SRS module like IDS can (up to 5 times)?

We are not aware about existence of this function for Mondeo 3.

Hi, thanks for your response. Ford Etis says that resetting crash data in Mondeo 3 is possible:
"The air bag control module can be reset, using WDS, and used for up to five collisions in which the air bags deployed."
Could you please look further in this option eventually in the future?