Page 1 of 1

Ranger PX2/TKE 3.2 Issue with Pre-Collision-warner

Posted: Tue Nov 05, 2019 7:08 am
by robinkrumm
Hello Gents,

I am Robin, 38 years old from Germany, PLC engineer and I ended up in your Forum as I spent some time researching my own stupidity. :-)

I did some changes to the BCM and other other modules- but to be honest, I was so stupid to not back up the factory data.

My ranger is MY2016, Wildtrak edition with Offroad and technology package and now having around 75000km on the counter.


One result is that I get an error that my pre-collision-assistant is not working any more after switching the ignition on.
I have a little menu showing up for a second of two to offer the ability to switch pre-collision on or off.

The red dots are lighting when starting and it seems that it is working partially (not giving sound but flashing) .

I can't see any option I might have changed related to pre collision, maybe the error is caused because any incompatible programming?
Unfortunately Ford in Germany tells that they are not able to send me the OEM data / original factory data.

Re: Ranger PX2/TKE 3.2 Issue with Pre-Collision-warner

Posted: Tue Nov 05, 2019 7:53 am
by todorakiggg
You can check this thread for more information: https://saeb.net/viewtopic.php?f=12&t=1 ... 7121ae4061

Re: Ranger PX2/TKE 3.2 Issue with Pre-Collision-warner

Posted: Wed Nov 06, 2019 6:18 am
by robinkrumm
Thanks toddarskigg,

I solved it yesterday night, maybe someone else needs this information:

If you come from the german or european market there are some forums leading you to fordserviceinfo.com .
If you are a newby and register yourself with a profile in australia or china or US you will never see the ASBuild-Download-section.

But they are available - you just need to change your country code to (working in November 2019) canadian - there you find all you need to get your original *.ab file that you could load back with forscan.
You might use the link below to change your country.

https://www.motorcraftservice.com/Home/ ... %3A1402%2F


I went through the data and got back to zero errors and much less checksum errors.

Thank you folks - will stay with you