When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Sounds like you should go take an F150 for a test drive / uHaul rental (pull around back, plug in your TCU, program it quickly, drive back lol). I'm going to make the same suggestion I did earlier fro i8iridium, did you delete all saved ForScan profiles before starting?
It seems like what was mentioned earlier, that if Forscan doesn't think a module is in a particular year/model it won't even scan for it. My work around thus far has been to use the 2017 Explorer profile in Forscan that I saved when I had the TCU connected there. When I hook up to the F150, I leave the key off and click connect in Forscan. Since it can't detect a vehicle, it'll prompt me to pick one of the saved profiles. I pick the Explorer one, then turn the vehicle on real fast. It'll do it's normal checks and once it's ready, I just select the TCU and do the programming. I sent that saved explorer profile to another guy on here that was in the same situation I was. I'm waiting to see if it worked for him.
So when the TCU is connected to the vehicle, does the DTC on the APIM go away?
No. But there are a lot of variables that I'm unsure of. My wiring to the OBD port was a little janky, as was my power supply. I was using a USB cord and a 5v power bank and butt connectors in lieu of more reliable connections.
Originally Posted by i8iridium
It seems like what was mentioned earlier, that if Forscan doesn't think a module is in a particular year/model it won't even scan for it. My work around thus far has been to use the 2017 Explorer profile in Forscan that I saved when I had the TCU connected there. When I hook up to the F150, I leave the key off and click connect in Forscan. Since it can't detect a vehicle, it'll prompt me to pick one of the saved profiles. I pick the Explorer one, then turn the vehicle on real fast. It'll do it's normal checks and once it's ready, I just select the TCU and do the programming. I sent that saved explorer profile to another guy on here that was in the same situation I was. I'm waiting to see if it worked for him.
I ruled out the gateway module as well.
I would think it would be an expected module on a 2018.
I have a buddy with a 2019 XLT 302a. I might see if he'll let me test on his truck but he's not the type to mess with his stuff. I might at least do what you did a create a profile with the TCU.
No. But there are a lot of variables that I'm unsure of. My wiring to the OBD port was a little janky, as was my power supply. I was using a USB cord and a 5v power bank and butt connectors in lieu of more reliable connections.
I would think it would be an expected module on a 2018.
I have a buddy with a 2019 XLT 302a. I might see if he'll let me test on his truck but he's not the type to mess with his stuff. I might at least do what you did a create a profile with the TCU.
Oh shoot, the 5v won’t cut it. It needs 12v from the vehicle. And how are you wiring it the ODB port? It has to be connected to the HS3 network which will be off the back of the gateway module/odbII port.
Oh shoot, the 5v won’t cut it. It needs 12v from the vehicle. And how are you wiring it the ODB port? It has to be connected to the HS3 network which will be off the back of the gateway module/odbII port.
I swear the diagram I posted said 5v to the BCM.
I'm using pins 6 and 14, which I believe is the HS network. I also tried the back of the gateway module plug. I think it was.pins 2 and 3. Green/Blue and White/Green.
I'm using pins 6 and 14, which I believe is the HS network. I also tried the back of the gateway module plug. I think it was.pins 2 and 3. Green/Blue and White/Green.
Its definitely 12v. C2280C pin #15 is the same location that the intrusion sensor is pinned with on The Lariat and higher trims. I know that the intrusion sensor operates on 12V for the power supply. The LIN data line might be a different voltage..
All the donor TCU's I connected showed up right away without any extra effort involved.
My 2017 F150 Gateway Module is:
Gateway Module A
Part number: GL3T-14F642-AA (latest known HL3T-14F642-AC)
Strategy: HL3T-14F530-AC
754-01 B132 40 (same data on every module I've seen).
754-02-01 x*xx xxxx I think is related to brand (Lincoln / Ford) or vehicle model.
754-03 appears to be Sync connect related
754-04 appears to be LTE hotspot related
754-05 ? (Ford only)
754-06 ? (Lincoln only)
The data looks very similar; fastest way to look for differences is to compare the checksum in each line.
I tried copying 1:1 all the data from the wrecked Lincon APIM onto mine and then followed the same procedure with as built data from a 2019 Limited F150. No matter what I try I am also not able to get the hotspot setup screen to show up in Sync 3 V3.0. I know the hotspot is broadcasting because my phones pick up the new SSID when the donor TCU has power.
This is my stock TCU As Built:
This is from the donor Canadian 2017 302a XLT:
This is from the donor Canadian 2017 Platinum:
Here is what i8iridum used on his US donor TCU:
This is from the US Lincoln MKZ TCU:
After testing, my Ford Pass app simply prompted me to pair my truck again. Which is probably more related to the fact I master reset Sync 3 more than once while testing some things. As far as I can tell, there appears to be no adverse effects from playing around with different donor modules on the vehicle side.
Last edited by Airborne_Ape; 08-10-2019 at 09:55 PM.
While is was out there I did run my antenna cable and mounted the antenna. There appears to be a backing or nut of some kind for the screw which I don't have. I just used some 3m emblem tape and a zip tie.
The antenna needs to be bolted down (it should have mounting hole). It has a built in ground that needs to be connected to the vehicle.
Possible important information for those wanting the HotSpot feature: I have been going back and forth with @i8iridium trying to figure out why he can't control his HotSpot with the APIM even though his programming is correct. I finally tested a theory on the bench. I took the same APIM programming and put it in both a GEN1 (2016) and GEN3 (2018) APIM. The GEN1 would not bring up the hotspot menu. The GEN3 did. I believe it is firmware or hardware (leaning towards firmware) related and the GEN1 can't have the its firmware updated that I am aware of. I then tested a GEN2 (2017) APIM that is running the latest firmware as those can be upgraded and programmed it and it also comes up working with the hotspot menu. I can't say whether or not a GEN2 with original firmware works as I don't have one to test (I always update the firmware).
I'm using pins 6 and 14, which I believe is the HS network. I also tried the back of the gateway module plug. I think it was.pins 2 and 3. Green/Blue and White/Green.
If you're going to test off the back of the Gateway module, you'll use pins 16 GN/BU and 15 WH/GR which will go to the TCU pins 8 and 16 respectively. You can find 12v anywhere, but the back of the Gateway module has 12 on Pin 13 WH-RD and Ground on pin 1.
08-10-2019, 06:59 PM
