Jump to content

2023 with P0562 error and Service transmission Now, unable to shift soon

kickass audio
 Share

Recommended Posts

kickass audio Enthusiast

kickass audio

Posted
Posted

I went to hop in my truck this afternoon and immediately on the Drivers Information Center it read the message "Service Transmission Now, unable to shift soon" after I started it up. The truck let me move forward and back in the parking lot just fine and I immediately restarted the truck and the message came back on the screen. When I got home which is about a 20 minute drive, I shut the truck down and immediately restarted it and the message was no longer displayed at startup. 

 

I pulled my OBD2 reader and it gave the code P0562 - Powertrain System Voltage Low as a pending fault. I unfortunately only have a basic OBD2 adapter through the torque app so I can't check body codes and things of the such.

 

I let the truck sit for about an hour in the driveway and restarted it a few times with no error on the drivers instrument cluster but this time the P0562 code was listed as active through the torque app.

 

Not once did a check engine light come on nor did I have any difference in shift pattern on my truck.

 

Leading up to this I put my truck into 4WD HI mode (I only have a single speed transfer case) on my way into work since it was snowy and a bit icy on the streets and had no issue on my drive in. I forgot to switch the truck back to 2WD mode when I shut it down and worked my shift. When I came back out it was still in 4WD HI and gave that error about not being able to shift soon.

 

Has anyone had a similar experience? I found a service bulletin https://static.nhtsa.gov/odi/tsbs/2022/MC-10212919-0001.pdf for the 2022 that indicates a potential rub on the wire harness between the PCM wires that run along the driver side of the engine just above the valve cover. I visually looked at them and don't see anything at quick glance that looks worn and it was totally dry in the engine bay. I did have service done a year ago where the data line between the PCM and the transfercase control module was giving high resistance and needed to be soldered and taped back up but had no issues all year with it. I also have a upgraded alternator and brand new battery that's only a few months old so power issues from that are not a concern.

kickass audio Enthusiast

kickass audio

Posted
  • Author
Posted

Does anyone have the exact parameter range for the P0562 code? What voltage range is acceptable?

jlivy Enthusiast

jlivy

Posted
Posted

clear codes first

12.4v - 12.8 v at the battery with everything off.

13v - 15 v running with no accessories on. 

 

read codes after. pay attention if its current/not current. and if there is any systoms codes with it

 

kickass audio Enthusiast

kickass audio

Posted
  • Author
Posted
13 hours ago, jlivy said:

clear codes first

12.4v - 12.8 v at the battery with everything off.

13v - 15 v running with no accessories on. 

 

read codes after. pay attention if its current/not current. and if there is any systoms codes with it

 

thank you! The battery was holding great voltage at rest, never lower than 12.7V, with the engine running and being cold outside the high output alternator would maintain a voltage around 15.2-15.6v. The only voltage issue I noticed is when the truck would shut the engine off with auto stop enabled and my voltage would get to 11.9v with the engine off and would drop to 8.6V for a millisecond when it would crank the engine to get me going again then would go back to 14.8-15.6v of power.

  • 1 year later...
Jeff5 New Member

Jeff5

Posted
Posted

Hello,

 

I have the exact same issue on my 2023 Chevy Silverado 1500. It happened about 3 months ago and the dealership changed the gear shift control module. Now throwing the same error, no check engine light, and OB2 showing a P0562 code. Anyone found a root cause for this scenario?

 

 

  • 4 months later...
Frankielozano214 Senior Enthusiast

Frankielozano214

Posted
Posted

Mines done this few times. I heard it happens if  it something to do with shifter not sure what but mine hasn’t said it in while (seen the msg like 4 different times) usually goes away quick wasn’t sure if it had something to do with my truck being super lifted on big tires or not

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...