Bill

Try ticking the auto connect, set the ISO support to the same as what I have & then close FORScan completely & reopen it. Maybe try a reboot & if unsuccessful, get in touch with TiPerformance as advised.

If the OpenPort 2.0 drivers have installed correctly, have you setup the "Connection Type" - J2534 & selected the Openport 2.0 as the J2534 Adapter? When changes are made to the connection type, you will need to close FORScan & reopen it for it to connect successfully.

Can you see OpenPort 2.0 when you click on the start menu?

Below is the link to "FORScan", it's the software that Roland has suggested installing to help you work out if your issue is hardware related. If it connects, it's not a hardware issue. If it won't connect, you likely have a hardware issue and need to contact the supplier for further advise. https://forscan.org/download.html

Did you search via Tear Tag "BBME"??? I can see it in the calibration list & it's available as a stock file

Is the dead pcm from an XR8 auto sedan? I had to replace a dead one a few years back but couldn't get one with an identical code. I'm sure it was A3JA & we used an A3JC or A3JD. It worked fine. I was told the last letter represented a later calibration version. Roland or someone else with more experience may be able to confirm if that's right.

Thanks for the confirming the procedure works 👍

Unless you fitted the tcm from the vehicle you got the pcm from I'd expect that you would be getting transmission faults. You would need to know the TEAR TAG or strategy info as a minimum if you plan on trying to reprogram the tcm to match. There are several topics on ZF's if you search. If you get stuck, search for Whiteford & contact Jack. He may not give away info but he is a go to when it comes to ZF programming & can reprogram TCM's on the bench.

I've only tried this with a BF XR6T & am getting an error for the BEM.....incorrect number of blocks so I can only assume it includes the BEM data & data for other modules. I haven't tried other modules yet. Further investigation shows it's been fitted with the wrong BEM at some point. The current BEM has faults for seat memory module etc that are not fitted. From your edit, it looks like you might already have 2.4.2. If not, let me know if you want a copy

If it's a FG MK1, I think it might be able to be changed the same way as it's done in BF. I believe FG MK2 is done via central configuration but haven't had access to an FG1 or FG2 to confirm. Select the tab for - Configuration & Programming. Don't select ABS Module Configuration (As-Built)....you need to select the second option - ABS Module Configuration, if available & press the play button at the bottom left. If you have access to the car the pcm came from, there will be an ABS value on the TEAR Tag that should match one of the values below. Select the correct value and write it. If you don't have access to the TEAR Tag info on the car the pcm came from, you could try the XR6 Turbo or G Turbo options to see if one works. Start with the one that the you believe the pcm came from ie if XR6T, then use the XR6T value. The pcm will be looking for a match in calibration. I have corrected BF swaps this way without changing the as-built data. Remember, as with all programming, there are risks. Don't try making changes unless you are confident in what you are doing and you have the correct equipment & a stable connection. Disregard the highlighted blue option below. I borrowed the image from an earlier post.

FORScan 2.4.2 Beta has the functionality to use the pcm VIN to check the Ford as-built database & download the as-built data file if it's available. It can also check the firmware of some OBDII interfaces & update the interface firmware. There has been a few problems reported & 2.4.2 version has currently been removed from the downloads area. Depending on what you were going to use 2.4.2 for, it may work fine. I believe most of the issues were around programming APIM. When it becomes available again, you will need an internet connection to check & download the as-built data. Don't forget to save your current configuration for all modules before doing any programming so you have data to revert back to should something not be right.

VID block in the original PCM file should have been correct but stock PCMtec files need to have the VID block merged from the original PCM file either using the merge function or manually.

I just read you're response & thought....Shouldn't it have been either ABS CAN or TCS CAN already? I then had to read from your initial post again & saw the reference to VRS Via Wire....that should have also been a trigger for issues. Good to hear you've got it sorted

I can't remember the exact reason but i have read somewhere that BA sensor won't work in FG & visa versa. Might have been something to do with the pattern of the signal ie one uses square wave, the other doesn't

This screenshot is using FORScan to reprogram an ABS module on a BFII XR6T ute but shows the variants that can be programmed. The same ABS module can be programmed for several different models & options. The errors don’t affect the final programming & are shown due to incorrect variants being programmed previously as the correct calibration is now selected

Happy to share information. Screenshots of FORScan ABS programming. Errors were present when I bought the BFII Craig Lowndes XR6T manual ute....really cheap after the faulty PCM was replaced with a second hand F6 PCM. It had ABS & oil pressure fault codes & lights on. 2 different Ford dealers tried reprogramming the ABS module & even replaced the ABS module & tried again with no success. They were trying to calibrate the ABS with the XR6T calibration. They both were aware that the PCM had been replaced as it was documented on their receipts for work carried out but they didn’t check the PCM calibration. One also did an oil pressure check & replaced the sensor with both a genuine & aftermarket oil pressure sensor trying to work out why the oil light was on. From the VIN stored in the PCM I determined it was from a F6 manual ute. I was able to write the ABS calibration 09 03 04 for the FPV ute & cleared the ABS fault. It’s now been reflashed with the XR6T 09 02 04 ABS calibration using FORScan & the correct XR6T PCM Calibration using the PCMtec “Create Stock File From Strategy or Catchcode” & “Manually Merge VID/Serial”. I used the Tear Tag B7BA to find the right calibration. The PCM still has the F6 VIN which doesn’t worry because everything else is right. Very simple with PCMtec. I wish I didn’t buy HP a few years ago when I was watching the development of this in the pcmhacking forum, lol

BF MKII F6 Manual ute strategy is HACCKC6. As per Rolls comments, you will get the low oil pressure light on that can be switched & ABS fault. Forscan will allow you to switch the ABS calibration from XR6T ute to F6 ute etc. I believe the differences between the XR6T & F6 was a larger intercooler, airbox If they were swapped with F6 parts then it might be safe to run the F6 tune at your own risk of course

I recently purchased a BFII XR6T manual ute that had a PCM (ASU-224) replaced & had issues that Ford couldn’t fix ie ABS light on & fault code C1991 - Module Calibration Failure. Oil pressure light on & fault codes P0520 - Engine Oil Pressure Sensor or Switch Circuit & P0524 - Engine Oil Pressure Too Low. After reading the PCM to obtain the fault codes I have the VIN to put into FORD Etis & confirmed the replacement PCM was from a BFII F6 manual ute. Same hardware different software/strategy. I was able to change the ABS calibration to the F6 ABS calibration & the ABS fault was gone which also confirmed the PCM had the F6 strategy. I compared the XR6T strategy vs F6 strategy after reading another forum post & could see the oil pressure switches were inverted as suggested in that post. I decide to reprogram the correct XR6T ABS calibration & return the PCM to the factory XR6T calibration because the engine has no modifications. If I had the correct F6 intercooler & airbox I would hav just flipped the oil pressure switch settings. If you are trying to swap tunes between the 2 cars you are likely going to experience similar issues. Are you getting any fault codes? ie C1991 Transferring the tunes will possibly have each car looking for the ABS calibration of the other ie MKI F6 looking for MKII XR6T ABS calibration & MKII XR6T looking for the MKI F6 calibration. Have a look at the Tear Tag on both cars & see what the ABS calibration should be. You will have to see if the ABS calibration for the MKI is available in the MKII & visa versa & hope that works. No guarantee. In order to achieve this with the car tuned using SCT, you may need to use the controller to return to stock, change the ABS calibration & then flash the tune back in. Again, no guarantee it’ll work Post Tear Tag photos of both cars