Page 1 of 1

Should I reload px1 as builts

Posted: Wed Jan 12, 2022 12:25 am
by Tommo654331
Hi all,
With great anticipation and some stupidity, I finally got my FORScan to work, which turned out to be an issue with my laptop. After getting the driver to download for my connector I plugged it into the car, jumped into the bcm area (not as builts) and started ‘playing’ with a couple of areas

Few things I did. Mainly going through and selecting what my ranger had and writing it over what displayed.

Also, I installed a new cluster and it doesn’t display the mileage. I jumped into rewrite mileage and changed it to what it was ( increased mileage). After writing all of that i got a number of dtcs, now I can’t for the life of all things good get ride off them, even though I Houghton I reverted back all the ones I changed. I have a power train light on the dash now and the dtc code is U2101-00-2f. So I have changed something.

The stupidity comes where I was that excited to jump into it, I didn’t save the original.

I have read a few posts on here and Stewart keeps saying px1 as builts only lead to tears. Is updating the as builts the best way to get everything right again?

Someone on the forscan Facebook page has said to download the as builts from the website and update it all on fire scan and that will fix it.

Now I’m worried I will screw it it even more

Also is there a way to get the mileage back on the cluster after a cluster change?

Help would be very much appreciated

Re: Should I reload px1 as builts

Posted: Wed Jan 12, 2022 9:53 am
by RossPat
You will need to wait for Stewart to answer, way out of my league.

Re: Should I reload px1 as builts

Posted: Wed Jan 19, 2022 2:53 pm
by saeb
Generally a PMI will be done when changing modules including the cluster across. This will ensure correct data is moved from the old module to the new one.

Unless you have access to Ford IDS then you are not going to be able to do this.

I can only suggest to plug in the old cluster and save asbuilt then write it to the new cluster else try writing the factory data.