Bill

That’s ok if the hardware isn’t ABU-212 or ABU-242. They don’t have the IO for the clutch switch so cruise will never work.

From memory, enthusiast level doesn't allow for you to use the return to stock feature. I missed the bit about it not recognising the cal id. When it can't read VIN & Cal ID, it's tuner locked as per what hjtrbo has said. FORScan usually has no problems returning it to stock but you need to be a paying customer, have a particular version of FORScan & the factory files. If the VIN is missing from the VID, FORScan won't show the VIN section for you to write it & takes some knowledge on how to trick it to re-add it. If you want to retain the tune, Custom Machine Works is your best option.....if it's not locked using PCMTEC.

Unlike tuning applications, FORScan doesn't care if the VIN is programmed into the VID block & will connect regardless of it being there or not. I can see the VIN isn't displayed in any of your FORScan screenshots. This is often seen in stock PCM's that have had the VID block programmed incorrectly using IDS or FJDS. I've lost count of the number of times I've seen it.

I may have a new DLP + AEM X-SERIES 30-0310 all wired up ready to go. I put it together for a bloke, he lost his job & I haven't heard from him for a few months. If you're interested, send me a PM & i'll check if he still wants it.

No, the Tatrix doesn't support MS CAN & you should avoid the cheap ELMs with a manual switch, they're usually cheap crap. The VGATE vLinker FS cable is a cheap auto switching cable with regular firmware updates to keep up with FORScan development.

Here's download link for Xspurt Injector data for their different size injectors, if anyone needs a starting point https://www.racerindustries.com.au/injector-data-files/

Update on the bricked TCM. The TCM is now recovered. It arrived & FORScan would find the TCM but would only recognise the OS calibration, not the 7J105 calibration. Identifying the TCM with other software, confirmed the same thing. It's been re-flashed with a full OS & calibration write, tested & will be posted back tomorrow.

https://support.pcmtec.com/kb/article/34--critical-resources-not-available-happens-when-upgrade-between-different-edtions/

That's great mate. You need the paid licence to get access to the beta area of the forum to get the download link for 2.4.8beta but yes, recovery mode works well. It took a few emails, sending debug data to the FORScan team in 2.4.7.test builds to get it working properly with the vLinker FS & J2534 devices. There were a few service procedure interrupted errors, resulting in no communication with the PCM, but they got there in the end. I had another tool I could use to recover the PCM, so it was ready to try again when another test build was provided. So far, I've only had 1 PCM sent to me that I haven't been able to properly recover using FORScan or return to stock. The PCM wouldn't communicate in car with any scan tools, HP or read using PCMtec recovery mode. I wasn't going to licence it to try writing to it. It was an ABU-244 BA turbo PCM, that would recover using FORScan over & over. Once recovered, it would then read with HP, PCMtec & FORScan. Give it half hour to an hour of being connected on the bench & it wouldn't communicate again. Leave it disconnected for a few hours & it could be recovered again using FORScan but kept losing COMMS over time. Not a FORScan issue but a hardware issue. It'd been sent for repairs twice & sent back after being supposedly being repaired, prior to being sent to me. A replacement PCM was installed & that solved the problem. There's a few other things you can do with FORScan PCM programming, that are pretty handy, if you have the Ford calibration files & spend a bit of time to work out a few workarounds.

I've seen a couple of bricked TCM's & it's usually been the result of trying to flash with low voltage or high temp. I'd ask what codes you have but you have no COMMS. If you think you may have bricked it because of one of these problems or others, send me a PM & we can discuss possible recovery options.

BF has fully independent VCT

Thanks for the update. The PSPS & wiring are often overlooked but are known to cause weird issues.

Did you make all the other changes you listed in your previous post or just auF1716? Do you remember what the codes were?

Yes, use the calibration merge function & just copy the VIN from the na file to the turbo file

Make use of the factory turbo PCM. Get onto Hootens Harnesses on FaceBook & get a patch loom to add the factory boost control. FYI, Hootens (Bill) is taking some time off but if you're lucky, he might still be at work & might just have a patch loom on the shelf. Update the PCM VIN to what the car is, if it's FG1, do step 2 of PATS programming...."Module initialisation" & it should be right to start & tune. Don't do step 1 as this will delete the keys. Not a problem if you have 2 keys but unnecessary. You may need to change strategies depending on if it's currently tuned for auto or manual to suit the setup. This may also include having a matching TCM calibration if ZF6 & an ABS variant change. IF it's FG2, you're going to need someone with IDS or FJDS to carry out PATS programming.

Open a stock file & then start the datalogger

Unplugging the noise suppressor will stop it from doing its intended job. Noise suppression. I haven’t seen a faulty TCM that hasn’t produced fault codes but yours could be the first. Let us know how it goes.

auF16449 & auF16489

Yes, power steering pressure switch. Usually due to it causing VREF or SIGRTN to open circuit or ground. I've had one where spinning the top section of the switch & flipping the wiring over itself whilst doing this would influence the fault.

Is the noise suppressor under the intake manifold connected & wiring ok, good earth? Not sure if it also reduces noise on the bus, but it's connected directly to coil wiring & back to the PCM via the A connector & meant to suppress radio noise. A faulty PSP switch & wiring will at times cause very weird issues but not cause a fault code. Have you checked if there's a consistent pattern ie when trans TOT reaches a set temp, rpm & load?

Good to see you've got it sorted & that the info we now have on auF12105 is providing a simple fix for people.

TCM failure happens but isn't common unless the gearbox has suffered the dreaded milkshake or it's been incorrectly handled. SAS fault C1956 is present at the time of request. Everything else appears to have cleared, so it's an issue that needs to be looked at. I'll attach an image of the ABS/DCS wiring circuit. Check power & earth circuits. Follow the CANbus circuits, noting the modules the data all passes through as there may be an issue somewhere in between. Also make sure the SAS is correctly located & not loose. I've seen one that wasn't right that caused intermittent issues. For the ABS section of the workshop manual, go to https://fordforums.com.au/wsmpub/bf/206-09.html There's very good information for diagnostic & testing, including pinpoint tests. Do these tests to rule out a SAS & ABS module fault. Speedo dropping out, gearbox not knowing what to do & having a heap of comms fault codes is very common when coils fail....even new coils. Anything that causes noise on the bus will do it. Usually, faulty coils will also cause a P0500 no speed source fault code, resulting in loss of speedo & ZF issues. If you need additional wiring diagrams, they can also be found here https://fordforums.com.au/vbportal/viewarticle.php?articleid=1818 If you need something a bit better quality, let me know.

@Kirby@PCMTec an update for auF12105 The values for auF12105, shown at the far right for (Ford/FPV Switch) 130=FG XR6T, BF & FG V8 FPV. 138=BF, F6X & FG 4.0 FPV. The auF12105 values I've found for other variants are as per below which isn't correctly reflected in the parameter description auF12105 isn't found when searched in FGX Sprint UEAA or UEAB. I wasn't able to find a BF manual 3V file but could have missed one when filtering.

UPDATE on this due to incorrect info. A5ME is actually a BF V8 FPV Tear Tag, not XR8 as I previously said. The VIN is however XR8. The values for auF12105, shown at the far right for (Ford/FPV Switch)130=FG XR6T, BF & FG V8 FPV.138=BF, F6X & FG 4.0 FPV. The auF12105 values I've found for other variants are as per below

No worries, you're not the first to have problems when they've had gauges or clusters plugged in at the same time.