Bill

Do you have any datalogs?

If I'd have known about the other issues with dropping cylinders or injector drivers, you'd read the ecu in recovery mode, licenced the ecu & then not being able to connect with FORScan, I'd have suggested to try writing it again with PCMtec & if you still had the issue, don't bother with it being a BA ecu. The other issues prior to having PATS issues is vital info when asking for help trying to diagnose a problem. At the end of the day, you have it going again. That's what matters most.

Try reading your old ecu using PCMtec. If it won't read, tick recovery mode & see if it will read. You don't need to licence it if it does & it might just confirm if there was an issue with the SCT tune.

I've just re-read some of your previous info. Your problems likely started with the SCT tune. I've come across several instances where a pcm hasn't been readable using FORScan, HPtuners, Ford IDS & scan tools in general. It doesn't explain why keys were forgotten. PCMtec will usually still connect to these ecu's in recovery mode. Sometimes the calibration & strategy don't match, the VIN isn't in the correct format or incorrect VID programming. Sometimes, when this is an issue & they can't be read, they will still accept being flashed PATS programming on a BA will take about 10-12 minutes

Great to hear. I've seen a lot of failed BA pcm's where hot or cold temperature stops them from starting or causes stalling, failed coil or injector drivers, auto transmission issues, but haven't seen any where PATS has been an issue. I'll be adding it to the list of known problems.

If the 2 spare keys are cloned off the original key, it will see all 3 keys as 1 single key which is why when it fails to see one key, it fails to see all keys. You need 2 individual keys (transponders) for programming, not 3 keys which essentially have the same transponder chip due to cloning. When using the wrong colour BEM, you'll have to look at the additional fault codes that you'll get & say to yourself, that's a false code when you get them for seat memory module etc

Looks like the BEM has forgotten the keys for some reason. Hopefully, the keys are not cloned. If they are cloned, if it forgets 1 key, it forgets them all. Try reprogramming PATS (keys). If it's only finding one key when you try programming 3, it may be due to cloned keys. If it's not finding any keys to program & has no other codes after programming, it might be a BEM issue.

Check the courtesy lamp fuse. It's what supplies power to the OBDII connector. Your OBDII interface won't power up without it

It could be a faulty key reader, pcm, bem, transponder chip, cloned keys, ignition switch, wiring etc Check the ignition electrical switch at the back of the barrel hasn't started falling apart. It's common for this to happen but usually cases other issues too. Having fault codes would help steer you in the right direction & should have been enough to give your mechanic somewhere to start. If you know someone with FORScan, they could scan it for you.

Without fault codes, all anyone can do is guess

Sounds like PATS has kicked in. What have you changed since it was running? Have you flashed a different strategy, changed pcm, icc, bem? What are the fault codes ie P1260? any other codes?

Depending on what pcm you're starting off with, you might be better off flashing a manual strategy onto your pcm. If you use the "Create Stock File/Calibration Merge" function, you'll be able to download a stock file HACCKBC (manual BF na) that doesn't have the VID details programmed & use it as a comparison file or to create a stock file to flash to your ecu. I have got a file from a vehicle if needed but it hasn't been licenced so it won't load as a compare file.

Thanks Roland, I've saved the file. Mine doesn't copy it back when the datalogger is launched 🤷‍♂️ even after an uninstall & reinstall. Not an issue though. Looking forward to the 2.1 release.

Hi Roland, Any chance you can pin the logging template here or add them to a Logging Layouts post? I'm not sure if I've modified & renamed the original. The only logging templates I have are ones I've created or modified.

Being able to connect to the pcm & have it show the VIN & strategy in the correct format is a good start. It may not be locked. You'll just have to read it with PCMtec now to confirm. If you find it's locked after reading & you can't access the file to view, it can be returned to stock

That's a good start. Some tuners recommend knock ears & some don't & it's something else to consider. Here's a link to data logging & setting up your wide band Having limited or no access to a pcm that's been locked isn't unusual. SCT can cause some issues too from what I've seen. FORScan won't display as-built data for the pcm. Are you seeing the pcm in FORScan connection log or config tab? Any changes made to a tune, can result in engine damage which is why it's important to data log before you start & understand what's going on. You can then make small changes, data log & see what effect it had & make adjustments from there.

Are you working with a manual strategy now or are you converting an auto strategy to manual? If you've started with a manual strategy, you already have the stock values to compare as it will show current & stock values. You can verify it's stock, what's been changed or setup by Ford in the VID block before you start

I completely understand the original workshop protecting their work. Even unlocking the tune for another PCMtec Workshop who hasn't done the hard yards, could potentially be giving away hundreds of hours & thousands of $$ in R&D. Did you pay for the original tune & was remote support part of the deal or did you buy the car with the tune?

I haven't used the function but reading the information above & highlighted below, It appears you, the original tuner would be given the option to unlock, whereas if I were to read it, I would get "This file has been tuner locked by another user" as shown above. PCMtec Editor records the licenced serial number & OSID of the pcm, it would recognise the pcm when reading & allow the original tuner access to unlock it

You haven't mentioned if your PCM has a custom OS. This procedure is for replacement of a PCM with a custom OS. If you have a custom OS, you need to follow this guide & program PATS. If your current PCM is a stock or tuned HAAN9N2 strategy, you need to follow You won't avoid having to program PATS when you replace the PCM even if the VIN is correct. It's a simple process using FORScan & can be done with the Tatrix cable if that's what your using with PCMtec. It's just slow on BA's.

I've just finished saying in PM that you'd be the person to speak to haha

Have you got a photo of your Tear Tag for a direct comparison of strategies?

If you can get a tear tag from one that's got the 6HP26, that would be good. I've got a mate wanting to swap his 21 to a 26 because it's failing again.

Thanks for that. Sometimes, the information on ETIS isn't 100% correct but I hope it is. I'll have to have a look at FGX ute Tear Tags when I spot one.

Would you mind posting the Tear Tags for both vehicles? It would be interesting to have a look at both files when time permits.