Programming PATS for Australian models 1998-2006

[f-wolf]

Hi,

I'm trying to program new keys in a 2006 BF Falcon and a 2008 SY Territory. I've got a BF Falcon ignition with 2 keys plugged into the vehicle. When I press the PATS Programming start button in Forscan it says to turn the ignition to On but dont have the engine running. I've got the ignition on with the engine off but it won't let me proceed.

They keys I've got are chipped keys and are genuine Ford but don't have a blue chip i the end as the chip is embedded into the keys. Is this part of my issue?

Thanks

Try this version ... And see if it works


2.2.6 beta, 2015-09-16 (download) at https://forscan.org/changes_history.html

[adami]

I have tried the different version of Forscan but I have the same issue. I have tried to initiate a Pats reprogram on a 2001 AU2 Falcon which is running and has keys working but still the same result. Is there a step I'm missing before selecting Pats program?

[f-wolf]

I have tried the different version of Forscan but I have the same issue. I have tried to initiate a Pats reprogram on a 2001 AU2 Falcon which is running and has keys working but still the same result. Is there a step I'm missing before selecting Pats program?

Also ... Did you have a read here:

We have implemented PATS programming functions for the following models:

Falcon/Fairmont/Fairlane AU/AU2/AU3/BA, 1998-2006
Territory 4.0 2004-2006

https://www.forscan.org/forum/viewtopi ... 3&t=1485

[AFR]

I have tried the different version of Forscan but I have the same issue. I have tried to initiate a Pats reprogram on a 2001 AU2 Falcon which is running and has keys working but still the same result. Is there a step I'm missing before selecting Pats program?

Make sure you doors are closed and boot is closed

[kartaphilos]

I'm trying programme keys for a 1999 Falcon AU(1.5) 5.0 Ute but the process fails at the key erase stage. I'm using Forscan 2.3.38 beta on a trial extended license.

Here's what I do:
1. Clear DTC's (have a persistant traction control(?) DTC P1221 - I'm guessing as its not on the Ute).
2. Start PATS programming - 2 Stored keys are detected.
3. Select 'Erase & Program keys'. Turn ignition OFF when prompted. Doors are closed (no boot, just the two doors).
4. Confirm I have 2 PATS keys on the pop-up
5. Confirm yes on the pop-up explaining the door lock cycle on successful erase.
6. Pop-up appears stating "Ignition key code erase was unsuccessful"

Should there be a 10min delay in the process somewhere to enter key erase/learn mode (or is not required on Oz models)?

Forscan detects the Ute as "Ford Falcon Forte S/Futura/XR/XT 5.0L" - Is this the correct profile?

I've attached the Forscan Log file.

Any thoughts?

Thanks,
Matt

FORScan-1999_Falcon_AU_PATS_fail.log

(15.09 KiB) Downloaded 328 times

[AFR]

What adapter you using?

[kartaphilos]

What adapter you using?

Good pick. It was an older one (>10yrs old). Got a newer one and successfully programmed keys today.

[CleanAgain]

Trying to do PATS reset on my 01 AU Ute and having similar problems. It has erased the known keys but now I cant store any in to the system. It will cycle the doors to say it has entered learning mode, i turn the key to on within a few seconds and it does not cycle the locks again. Im using both the original key and a new blank key. Any suggestions?

[Ecmbuster]

Much of these faults are because of the adapter. FORScan will recognize and likely fail with poor quality adapters.
The best for any type of programming are high quality Bluetooth and USB connections.
A personal choice are the OBDLink devices with firmware and the general duty BAFX.
The chinese clones are garbage. The tools that have been tested sucessfuly are versions 1.4 to 1.5.
These so called 2.1 versions are quite questionable.
Just because those are cheap to purchase, doesn't mean it was a smart purchase.

The J2534 device are very stable and much faster. The issue being the cost of such a device.
Again, chinese close are questionalble and the best will be from high end manufacturers like Bosch, DrewTech, Actia etc.

When it comes to keys, the best solution are OEM keys, not some cloned fleaBay or amazonia POS from wherever they are created.

At least one key should start the vehicle. If no keys are available, a minimum of two OEM keys are required.

Get a wiring schematic and follow the connection from the PATS module to the controller that "Authorizes" the key and sends authorization to the PCM to enable a start sequence. In many cases, the Instrument Panel addresses the Tx and Rx lines. (Tx = Transmit, Rx = Recieve)

1) A power supply is a must and attached at the battery.
2) A complete scan must be performed first and saved.
3) Have the OEM keys ready. Make sure the DLC fits the device snug and ALL the connecting pins are clean and tight.
4) Look at the controller and save the image of where the keys are stored. View the changes later.
5) Perform the function and wait for the the complete allotted time.
6) Follow the instructions for your model exactly as described.

One last piece of advice, if for any reason As-Built data was changed for any controller that is associated with PATS, you've been warned.

As with any immobilizer, the As-Built should be the factory version.

[Farlig]

Big shout out to the FORScan crew!

I bought a Ford 2004 SX Territory and it only had one key. Purchased a couple of eBay flip keys, but only 1 of them gave me a P1601 code unfortunately (I don't expect a reply from the seller going by their feedback history, I requested they send out a replacement transponder chip for that key) but I might purchase another transponder from another eBay store instead if I end up needing a third key. Having the original key and one working blank I ran the gauntlet and erased and programmed the 2 keys. It was a stressful 12min wait while it did the timed program but it all worked in the end!