Hello,
I have a problem with a Fiesta 1.4 with Siemens SID 22 ECU and accelerator problem. It shows errors P2100-C, P2176-P, P0562-60, P2100-F0 etc tha show either Throttle or ECU.
Before I start paying for replacing these expensive parts i want to do a recalibration of the Throttle body. I could not find how to do it.
Am i doing something wrong or FORScan can not do this function?
B.R
Fiesta 1.4 Gasoline accelerator pedal
Re: Fiesta 1.4 Gasoline accelerator pedal
If the Service section doesn't contain the function you are looking for, it is most likely not implemented in FORScan for your model. FORScan still has a lot of functions not implemented, as there are a lot of versions for different model. We add them one by one by users' requests. If you want us to look into this issue (if the functions is available for your engine and if it can be implemented in FORScan and when), please send us internal FORScan logs to email as described on Contact Us page.
Re: Fiesta 1.4 Gasoline accelerator pedal
OK thanks for the reply. I will email the DTC LOG
Best Regards
Best Regards
Re: Fiesta 1.4 Gasoline accelerator pedal
Status update:
For this vehicle the ETB/EGR initialization function performing during the Reset All Adaptations service functions. But the user was unable to execute this function (FORScan returned error). It was found out that FORScan has a bug in workflow for Siemens ECU, that appeared in many cases (not always but quite often). The bug is fixed, the fix will be available in nearest release. Also, here is the direct link to the test version that has this bug fixed:
http://forscan.org/download/FORScanSetu ... 190914.exe
For this vehicle the ETB/EGR initialization function performing during the Reset All Adaptations service functions. But the user was unable to execute this function (FORScan returned error). It was found out that FORScan has a bug in workflow for Siemens ECU, that appeared in many cases (not always but quite often). The bug is fixed, the fix will be available in nearest release. Also, here is the direct link to the test version that has this bug fixed:
http://forscan.org/download/FORScanSetu ... 190914.exe