Spare FPCM (Fuel Pump Control Module) WISE IDEA!!!!

[DocDoug]

Its not if the module will fail, but when IMHO. Either due to component failure, solder joint problems or water intrusion into the connector.

I cannot say 100% that the module needs to be programmed, there was all sorts of info that my 2024 needed to be programmed, but it did not need to be programmed.

I think your FPCM is clearly a different part number from the current models and may be around $100 depending on where you find it.

There are 2 problems when the unit fails.

1. Finding the correct FPCM quickly and easily. Late and night, weekends in the wild, who knows. Buy one and have it in the truck.

2. Programming, does it need it?? Buy it and try it. It will either work or need programming. If it needs programming, you at least have it on hand and can shop around and find someone to program it for a spare, or if you get stranded and have the part, then you just need to find a shop with a more advanced scan tool that can program the module.

In my area, this would be less than a cost of a tow job, plus you would likely need to pay list price for the part, labor to install and programming. Quickly adds up to a $500-$750 job and at least a day or more. Can't even put a value on the PIXXed Off wife!!! If mine fails, it will likely be in the midst of a 2.5-6 hour trip as we take these pretty often.

Gateway came through! Arrived two days ago! I plan to test it on the truck to confirm that it works. Once confirmed, it will be placed in the rear jack area for standby! Thanks again. Cheap insurance.

 

[DontTaseMeBro]

Just got mine from Shea Chevy.

It is a 13554821. Looked underneath my Yukon and it has the 13537053 module.

 

[DontTaseMeBro]

Just did a test replacement on mine. It fired right up. That being said, it triggered a CEL code - P0627 “Fuel Pump “A” control circuit/open. I could not clear it with the Carbyte module that I have plugged in. Put the old module back, vehicle fired back up as well. Still could not clear the DTC. Drove the vehicle for about 10 miles. Turned it off. Turned it back and CEL was gone. Something to keep in mind. Also, I found out that remote start gets disabled when a CEL is triggered.

 

[jfoj]

CEL is not really an issue. Depending on the state of the vehicle when the module is changed, it could possibly trigger a code. When I originally swapped the replacement module in, the vehicle had been parked overnight and I purposefully left the keyfob in the house rather than have it in my pocket so when I approached the vehicle it would not "wake" up. once the module was swapped, I walked out with the keyfob and pressed the unlock button on the keyfob while standing next to the left rear of the vehicle. I heard the fuel pump cycle when I unlocked the door so I knew things would likely be fine, no programming vs what was all over the Internet.

After starting and allowing the vehicle to run for about 10 minutes, I fully shut down the vehicle so the dash and electronics were shut down, swapped module, no issue.

If for some reason the vehicle was not in a full shut down state, there may be polling of some modules and this may have been what triggered the CEL/code.

As for CarByte, I believe the OBDII App that works with it is OBDFusion or an OE version of OBDFusion. I know this App quite well, one thing that OBDFusion tends to limit is being able to clear codes while the engine is running, even if prompted to clear codes with the engine running, it may not clear them. Also with the newer CAN vehicles, it is possible that the CAN system limits under what conditions the code can be cleared.

In any case, OBDII standard is designed to clear codes automatically after a specified number of Start/Run cycles, depending on the code, this could be a few Start/Run cycles up to 10-20 Start/Run cycles if the code does not reappear the CEL will go out if the fault has not been seen again but there may be History trouble codes stored.

 

[StephenPT]

Just did a test replacement on mine. It fired right up. That being said, it triggered a CEL code - P0627 “Fuel Pump “A” control circuit/open. I could not clear it with the Carbyte module that I have plugged in. Put the old module back, vehicle fired back up as well. Still could not clear the DTC. Drove the vehicle for about 10 miles. Turned it off. Turned it back and CEL was gone. Something to keep in mind. Also, I found out that remote start gets disabled when a CEL is triggered.

Did you replace it with the battery still connected? As @jfoj mentioned the vehicle will be in an “awake” state for about 10min if you unlock a door, open a door, etc.

Likely the ECM saw the disconnected fuel pump because it was “awake” and after completing a drive cycle and not seeing the fault anymore, it reset the light.

Yes, a CEL for any reason automatically disables remote start.

 

[DontTaseMeBro]

Did you replace it with the battery still connected? As @jfoj mentioned the vehicle will be in an “awake” state for about 10min if you unlock a door, open a door, etc.

Likely the ECM saw the disconnected fuel pump because it was “awake” and after completing a drive cycle and not seeing the fault anymore, it reset the light.

Yes, a CEL for any reason automatically disables remote start.

Yup sure did. OP stated that he replaced his without touching the battery but didn’t say whether or not it popped a code. Also, I did not wait 10 minutes for all of the electronics to power down.

Either way, no harm no fowl. Just wanted to point out that if someone were to experience an unexpected FPCM failure, they should expect a CEL if they don’t wait 10 minutes first before replacing the module. Under normal circumstances I would have disconnected the battery(as I usually do for these types of things), but I wanted to do a dry run emergency replacement.

As far as remote start, it was kind of interesting cause I’ve never had a CEL on a remote start equipped vehicle so I was caught off guard for a second.

 

[DontTaseMeBro]

CEL is not really an issue. Depending on the state of the vehicle when the module is changed, it could possibly trigger a code. When I originally swapped the replacement module in, the vehicle had been parked overnight and I purposefully left the keyfob in the house rather than have it in my pocket so when I approached the vehicle it would not "wake" up. once the module was swapped, I walked out with the keyfob and pressed the unlock button on the keyfob while standing next to the left rear of the vehicle. I heard the fuel pump cycle when I unlocked the door so I knew things would likely be fine, no programming vs what was all over the Internet.

After starting and allowing the vehicle to run for about 10 minutes, I fully shut down the vehicle so the dash and electronics were shut down, swapped module, no issue.

If for some reason the vehicle was not in a full shut down state, there may be polling of some modules and this may have been what triggered the CEL/code.

As for CarByte, I believe the OBDII App that works with it is OBDFusion or an OE version of OBDFusion. I know this App quite well, one thing that OBDFusion tends to limit is being able to clear codes while the engine is running, even if prompted to clear codes with the engine running, it may not clear them. Also with the newer CAN vehicles, it is possible that the CAN system limits under what conditions the code can be cleared.

In any case, OBDII standard is designed to clear codes automatically after a specified number of Start/Run cycles, depending on the code, this could be a few Start/Run cycles up to 10-20 Start/Run cycles if the code does not reappear the CEL will go out if the fault has not been seen again but there may be History trouble codes stored.

Carbyte displays a warning saying not to clear codes while the engine is running. Personally, I’ve never done code clearing this way with any OBDII scan tool. I tried to clear the code with accessories on only. I heard the relay clicks and the chime but the code stayed. So ya, the CAN system prevents it from being erased.

 

[jfoj]

DontTaseMeBro pretty much took the same approach as me, did not want to worry about disconnecting the battery because if I was on the side of the road, I would not bother. So as you found, clearly in some instances it may trigger the CEL/code. But triggering the CEL/code should not impact the way the engine runs, possibly some other codes might, but not likely for the FCPM.

Interesting about the Remote Start, will need to test this to see if I can replicate the Remote Start being inhibited due to a CEL.