CarCodes
Home cases › gm ultium isolation and thermal priority codes specialist escalation before parts

GM Ultium isolation and thermal-priority codes: specialist escalation before parts: Source-Scope Research

GM Ultium isolation and thermal-priority codes: specialist escalation before parts. See the manufacturer document, vehicle conditions, exclusions and questions for a qualified shop before assuming a repair.

DOCUMENT-SCOPED CASE

This is a research summary of a manufacturer communication, not a diagnosis for your car, a DIY repair procedure or confirmation of warranty or recall eligibility. No qualified technician has approved a repair for your individual vehicle here.

Source check and limits

This historical communication is conditional. The current revision, VIN/build eligibility, measured diagnosis and any warranty or recall decision are not established here. Ask the manufacturer or a qualified shop to check the complete current document.

Read the General Motors original: EV battery isolation and coolant-loss data collection · Check open recalls by VIN at NHTSA Source date: document date not recorded; research checked: 2026-11-01.

What prompted this manufacturer document

  • High-priority battery DTCs
  • Possible no-start, abnormal noises or loss of propulsion
  • This bulletin is a specialist handling/data-collection protocol, not a list of guaranteed bad battery parts or universal definitions for its U-codes.
Advertisement

Which vehicle conditions must be checked

Each row below retains its own conditions. Do not combine engines, years or models across rows to create new applications. A listed model is not proof that a particular VIN is affected.

  • BrightDrop Zevo 600 · 2022, 2023, 2024 · BEV
  • BrightDrop Zevo 400 · 2024 · BEV
  • Cadillac LYRIQ · 2023, 2024 · BEV
  • Chevrolet Blazer EV · 2024 · BEV
  • Chevrolet Equinox EV · 2024 · BEV
  • Chevrolet Silverado EV · 2024 · BEV
  • GMC HUMMER EV · 2022, 2023, 2024 · BEV
  • GMC HUMMER EV SUV · 2024 · BEV

Codes recorded in this document

A root listed only as an appearance has no separately verified meaning here. Preserve every suffix and module name; a shared root does not transfer a repair branch to another vehicle.

Document code forms and evidence status
RootRaw formMeaning in this source, if established
P0AA6P0AA6Appears in the document; individual meaning not verified
P0AA7P0AA7Appears in the document; individual meaning not verified
U359EU359EAppears in the document; individual meaning not verified
U2220U2220Appears in the document; individual meaning not verified
U2221U2221Appears in the document; individual meaning not verified
U2222U2222Appears in the document; individual meaning not verified
U2223U2223Appears in the document; individual meaning not verified
U2224U2224Appears in the document; individual meaning not verified
U2225U2225Appears in the document; individual meaning not verified
U2226U2226Appears in the document; individual meaning not verified
U2227U2227Appears in the document; individual meaning not verified
U2228U2228Appears in the document; individual meaning not verified
U2229U2229Appears in the document; individual meaning not verified
U222AU222AAppears in the document; individual meaning not verified
U222BU222BAppears in the document; individual meaning not verified
U222CU222CAppears in the document; individual meaning not verified
U222DU222DAppears in the document; individual meaning not verified
U222EU222EAppears in the document; individual meaning not verified
U222FU222FAppears in the document; individual meaning not verified
U2230U2230Appears in the document; individual meaning not verified
U2231U2231Appears in the document; individual meaning not verified
U2232U2232Appears in the document; individual meaning not verified
U2233U2233Appears in the document; individual meaning not verified
U2234U2234Appears in the document; individual meaning not verified
U2235U2235Appears in the document; individual meaning not verified
U2236U2236Appears in the document; individual meaning not verified
U2237U2237Appears in the document; individual meaning not verified
U1666U1666Appears in the document; individual meaning not verified
U1667U1667Appears in the document; individual meaning not verified
U2426U2426Appears in the document; individual meaning not verified
U2427U2427Appears in the document; individual meaning not verified
U2BFCU2BFCAppears in the document; individual meaning not verified
P1C34P1C34Appears in the document; individual meaning not verified
U35B5U35B5Appears in the document; individual meaning not verified

What an owner can record safely

  • Whether propulsion was lost or unusual sounds occurred
  • Photos of dashboard messages from a safe location
  • Previous coolant addition or battery work

Editorial safety boundary for this system

Do not continue driving with loss-of-propulsion, isolation or serious battery warnings; obtain model-specific roadside guidance.

  • Use current model-specific service information, calibrated equipment and a qualified technician for the selected diagnostic branch.
  • Do not open the traction pack, touch orange cables or damaged connectors, bypass interlocks, or perform home insulation testing.

This is a conservative editorial policy, not a manufacturer safe-to-drive decision for a specific vehicle.

Advertisement

What the source does not prove

  • Do not open the pack, perform owner-level insulation testing, or describe every listed communication code as a proven coolant leak.
  • A code or message alone does not establish a failed part, a safe-to-drive decision or an approved repair for this VIN.
  • A service bulletin is not automatically a recall or free warranty repair. Confirm current eligibility directly.

Questions for the repair shop

  • Which current manufacturer procedure, VIN/RPO/build gate and test result determine the diagnostic branch?
  • Does a later revision or a current recall change the source's original advice?
  • What measurement or inspection confirms the cause, and how will the repair be verified?

Open source-review issue

  • Q3-08: Many U-codes are listed as escalation triggers, without individual definitions. Index as appearance-only. Do not label each as a particular component failure or coolant leak.

The uncertain field is not used here to claim a current fitment, repair or market-wide failure.

Read the original record

The linked communication may be revised after the research date. Compare its document number, exact vehicle table, diagnostic preconditions and exclusions with a qualified technician. This page paraphrases selected facts and does not reproduce the manufacturer procedure.

Advertisement

Sources and scope

  1. General Motors — EV battery isolation and coolant-loss data collection (23-NA-151) Document: date not recorded · Research checked: 2026-11-01

Research snapshot: 2026-11-01. Source documents may have newer revisions. Verify current instructions and VIN eligibility with the manufacturer.

Advertisement