So a new to me 17 MKC just got a TCU upgrade to the JL3T-14G087-CF with the official antenna NLIZ-19A390-A I was able to successfully update the firmware of the TCU to the latest version and was able to successfully authorize. I can see current fuel level, location, and odometer. My issue is when I try to lock, unlock, remote start it always fails. When doing any of those functions I can hear a relay under the hood energize and something in the fan area buzz but nothing happens and receive the failed message. I’ve updated the APIM to HB5T-14G371-CCA but still behaving the same.
Is there something I’m missing? Do i need to buy another antenna for the other port on the TCU? Do i need to use a different firmware on the TCU or APIM? Completely stumped at this point.
What did you use for the final AB in the TCU?
The config is platform specific, so if you left it as it was from the F150 donor you’ll have issues.
I’d look for the VIN for a 2018/2019 Escape since they are the same platform and use that to download the config from Ford and either use it directly or run your config vs that one in AB Explorer and find the deltas.
I have the VIN from the donor and the AB data from the Ford site. Should I be updating my current AB to match the donor? For example my 754-01-01 defaulted to B132-0000-0050 but the AB on the Escape was B142-0000-0050
The 2018 MKC came from the factory with a JL3T, try loading this AB into the unit.
Typically the issue isn’t with the B132 0000 0050 setting unless you’re dealing with a HEV/PHEV.
The problems come with the platform specific items 754-03-0x through 754-06-02. 2018 MKC FWD.ab (34.5 KB)
That would be B132 for CGEA 1.3, it didn’t work right with that and then he tried B142 which would be C1CMA?
What kept it from working when he had it set to B132 previously?
No, the file he used was the donor from the Escape, which is C1CMA, which is coded B142. The file you supplied is CGEA 1.3, which is coded B132. The MKC started life as CGEA 1.3.
No the original AB I was using was B132 0000 0050 and it would communicate but not carry out the functions. I’ve never used B142, rather was asking if that is what it was looking for. After I corrected it with warlock file I notice the only changes was in line 754-01-01 B132-0000-0050 to B132 -0000-0040 and line 754-02-01 from 03E0 to 03A0 After writing it everything worked.
The only issue I’m left with now is a DTC for an error with the checksum in the APIM. I was reading somewhere before getting help here that the APIM may need the firmware updated. When doing that it errored out during ECU calibration file and screen stayed black. Took several attempts but was able to get it working again just with a checksum error. Not sure what firmware it really wants and left good enough alone.
From an earlier post here and the FORScan forum, “Strategy file GB5T-14G374-CB may brick the module. Solution is to upload GB5T-14G374-CD instead of GB5T-14G374-CB.”
