GM Volt Forum banner

2017 P0AC4 code after using preconditioning

7.1K views 11 replies 6 participants last post by  glasspilot  
#1 ·
Recently it's been cold (for N.E. North Carolina), temps in the mid 20's at night and low 30's in the mid day.

I use the remote to precondition and it's cold enough to start the ICE normally. But 2 times in the last week I push "lock" then "precon" and the car lights don't come on so I know it's failed. I get in the car and push start and the check engine light is on. The car operates normally. I use my ODB2 bluetooth gadget to erase the code and I'm good for a few days. The precon even works. Then I get P0AC4 again, can drive with no symptoms.

Any ideas?
 
#6 ·
Thanks Jbaker, My FOB batteries are fairly new. In my OP I mentioned car lights when using the FOB. When I hit "Lock" the lights flash. (So FOB batteries are working). Then I hit the "Precondition" button normally the running lights come on and stay on. In my case the second lights didn't come on. A precondition failure that sets the engine light. This has only happened twice so far, and only when it's cold.
 
#5 ·
old post answer from WOT

"Well there MUST have been another DTC. P0AC4 isnt really even considered a "fault" code, as it will automatically set in the Engine Control Module (ECM) whenever some other system significant fault s detected within either of the Hybrid Powertrain Control Modules (HPCM1/2). Since the ECM is really the only module permitted to turn "ON" the Check Engine/ Malfunction Indicator Light due to OBD2 regulations. When the HPCM detects a system problem it essentially "tells" the ECM to set the P0AC4, basically JUST to turn on the MIL. So this code is always set in combination with some other DTC.
Did Onstar even mention another code? Did you write them down? "
 
#7 ·
Thanks Cord, yes there were other codes. P1AEE and P1AEF.

Not using Onstar. I have a OBD2 bluetooth reader to get the codes and delete them. Whatever is causing this does not affect the operation of the car at all.