By iCarsoft Official Store Technical Team, Automotive Diagnostics Editors · Updated October 15, 2026 · Technical sources checked
Quick Answer
The U0142 code means lost communication with body control module b. It does not prove a failed Body Control Module B, a failed actuator, or safe system operation. Save the scan, identify the exact architecture, and test the physical and electrical paths before selecting a repair.
What Does the U0142 Code Mean?
U0142 is listed as lost communication with body control module b in the Autel code-reference table. The full fault record determines the test branch.
The diagnostic opportunity is the pattern around the body-message fault. When starting, gauge, shifting or network symptoms occur together, ask whether the same physical path could affect more than one circuit. A list of many codes is not a list of failed modules. Map the observed unavailable senders and the circuits that share a connector, supply or harness route.
Use the complete OEM label to identify BCM B; the letter does not specify the left side, rear location or a particular fuse. Photograph visible damage before disturbing it, but do not assume a clean exterior proves the copper or terminal contact is sound. Inspection and a measured failed path must agree before repair authorization.
Keep the sender, reporting receiver and physical function separate. A component name on a scan is not a replacement instruction.
GM PIT6192C, published May 12, 2025, includes U0142 in a broad fault cluster on its listed 2022–2025 Silverado/Sierra 1500 2.7L L3B applications. It points technicians toward engine-harness contact areas, including the left-front compartment and cam-cover region. This is a bounded shared-harness example. It does not identify BCM B universally or establish that an isolated U0142 on another vehicle has the same cause.
Use the documented case to choose a question, then prove the branch on the actual vehicle.
Save the full module wording and suffix before clearing; they can change the test path.
Separate U0142 from adjacent fault families
| Code | General description | Key distinction |
|---|---|---|
| U0142 | Lost Communication With Body Control Module B | Confirm the complete OEM wording, receiver and installed sender. |
| U0073 | Control Module Communication Bus A Off | Bus state differs from one sender missing at a receiver. |
| U0100 | Lost Communication With ECM/PCM | A different message source; do not combine replacement decisions. |
| P0562 | System Voltage Low | A voltage record requires its own measured confirmation. |
Record the complete U0142 description. The suffix, reporting module and companion faults can change the diagnostic path. Use the manufacturer's full wording and test procedure for the exact vehicle.
U0142 Symptoms and Likely Causes
Record U0142 symptoms and fault status; symptoms alone cannot identify a failed part.
Check whether companion faults share a proven cause.
Record what changed in the body control module b system, the exact warning and when it appeared. Absence of a warning does not prove all messages arrived.
A history event needs its original conditions preserved. A current missing sender requires diagnosis in the prescribed wake and power state.
Review the actual record of engine-bay, harness, body-module or accessory service. Timing narrows inspection but does not prove the new component is defective.
Save the vehicle-wide report. Several missing messages may share a prerequisite; one receiving module may also have a separate software or configuration issue.
Practical cause-checking order
- Incorrect identity or equipment assumption: Save the complete code cluster and symptoms, then map shared wiring routes. Use the GM harness locations only after the listed truck, engine and model-year restrictions are confirmed.
- Unstable feed, ground or wake state: Verify the sender’s permitted supplies, grounds and wake conditions. Record the actual operating state and OEM test limits; a sleeping sender cannot be judged from the wrong state.
- Connector or network-path interruption: Inspect the missing-message branch, including disturbed connectors and routing. Prove terminal contact and the electrical path with the prescribed checks; no universal CAN value or connector pin is assumed.
- Applicable configuration or software issue: Compare the identified BCM B feed and message path with the companion faults. A proven chafed circuit is useful evidence; a bulletin mentioning the code is not proof that its illustrated location is damaged.
- Internal sender or receiver fault: Consider controller failure after the required external paths pass. Request the failed-test evidence and distinguish a genuine offline ECU from scan-tool coverage or access limitations.
Did U0142 appear after recent engine-bay, harness, body-module or accessory service? Recheck the documented connections, parts and setup steps affected by that work. Record battery and software history; a post-repair code does not prove the new part is defective.
How Serious Is U0142, and Can You Drive?
A no-start, stalling event or multiple safety warnings overrides a routine driving plan. Arrange qualified inspection or towing when vehicle behavior is abnormal; do not road-test a suspected intermittent stall for convenience. The DTC alone cannot establish a safe driving distance.
Record warning messages, operating conditions and service history. Do not induce wheel slip, emergency braking or a handling event on public roads. A red stop warning or abnormal control overrides any verification plan.
Stop and arrange a tow if required lighting, braking, steering, propulsion or another safety function is abnormal.
A no-start, stalling event or multiple safety warnings overrides a routine driving plan. Arrange qualified inspection or towing when vehicle behavior is abnormal; do not road-test a suspected intermittent stall for convenience.
How to Diagnose U0142 in the Right Order
-
Preserve the original event
Save U0142, its complete suffix, reporting ECU, current/history status, available event data and companion faults before clearing anything. Record the symptom timeline and the current vehicle warnings.
-
Identify equipment, sender and receiver
Save the complete code cluster and symptoms, then map shared wiring routes. Use the GM harness locations only after the listed truck, engine and model-year restrictions are confirmed. Obtain the VIN diagram and current OEM definition. Compare the installed equipment with the scan report, and note any mismatch explicitly.
-
Check electrical prerequisites
Use the permitted feed, ground and wake checks for the identified message source. Secure the vehicle and respect its electrical safety state before access. Record loaded or static test conditions as required by the OEM procedure; do not borrow another model's pin assignments, thresholds or isolation sequence.
-
Test the relevant communication branch
Compare the identified BCM B feed and message path with the companion faults. A proven chafed circuit is useful evidence; a bulletin mentioning the code is not proof that its illustrated location is damaged. Keep physical measurements separate from ECU-reported data. If the diagnostic tool cannot access the ECU, establish its coverage and authorization before concluding that the ECU is offline. Avoid arbitrary module disconnection that can create new faults and obscure the baseline.
-
Choose a proven correction
A harness quote should state the failed location, circuit proof, repair method and restored protection. It should not silently add every module named by the original scan. Use the failed path to choose wiring, terminal, supply, software, setup or controller work.
-
Verify communication and function
After a demonstrated harness repair, verify its routing and protection as well as communication. Recheck all modules that shared the event so that a remaining companion fault is not hidden by fixing only one label. Save a final multi-module report and compare it with the original record. Confirm required setup and the actual function under the manufacturer's safe conditions.
Specifications are vehicle-specific. Use the exact VIN specifications, approved test points and required operating state. No generic value or drive cycle can replace the applicable procedure. Manufacturer examples here do not establish specifications for other applications.
U0142 Repairs and Cost Planning
A U0142 repair must address the demonstrated failure. Do not replace an assembly from the code alone.
Recheck installation and required setup after repair. A harness quote should state the failed location, circuit proof, repair method and restored protection. It should not silently add every module named by the original scan.
Ask the shop to name the failed branch and the measurement supporting each proposed repair.
Authorize diagnosis before parts while the cause remains uncertain.
| Possible path | Quote basis |
|---|---|
| Restore a demonstrated feed, ground, connector or network path | VIN-specific quote |
| Apply matching OEM configuration/software instructions when required | VIN-specific quote |
| Replace an isolated controller only after the approved diagnostic decision | VIN-specific quote |
These are alternative repair paths, not prices to add together. Request a VIN-specific quote separating diagnosis, parts, labor, fluids, taxes, required setup and verification. Ask which failed test supports the proposed repair and whether warranty coverage applies.
Using iCarsoft CR Max P for U0142
On a supported vehicle, iCarsoft CR Max P can save accessible faults, available freeze frame, live data and diagnostic reports. Preserve the U0142 evidence before clearing.
Compare the saved and final module records. Scan data supports diagnosis but does not replace the OEM reference, physical measurement or safety-system functional check.
Preserve the BCM B messages and shared harness evidence evidence
iCarsoft CR Max P
Review supported codes and relevant live data together. Confirm the exact VIN, controller access, PIDs and any requested active test with iCarsoft before purchase; generic product capabilities do not guarantee a U0142-specific function.
Check current CR Max P price and availabilityCheck CR Max P compatibility by VINThe official product page describes supported full-system diagnostics, available live data, freeze frame and diagnostic reports; exact controller coverage and active tests depend on the VIN and software. Confirm the requested function by VIN before purchase. Follow OEM prerequisites and stop for abnormal operation.
Know the measurement boundary. Scan data describes ECU-provided information; it does not directly prove the physical condition of the BCM B messages and shared harness evidence. Where required, use approved system scan access, the VIN wiring diagram and the specified electrical test equipment and compare reported values with the relevant measured evidence.
Verify the U0142 Repair
After repair, verify installation, clearance and required setup. Save the final findings and clear only erasable records as instructed. Battery disconnection is not a repair.
Run the manufacturer's applicable verification conditions in a safe workshop or route. Compare the original operating state with current data for the BCM B messages and shared harness evidence, and check current and pending faults in related modules. A clean start or idle period does not prove the repair; use the OEM functional check for the affected system.
Compare the original and final fault status. Record the functional-check result and whether the original event returned.
If U0142 returns, compare its suffix, status, failure order and operating conditions with the saved baseline before replacing another part. Revisit the failed branch and inspect anything disturbed. Confirm the prescribed affected-system functional verification separately from code clearing.
Verification follows the system involved. After saving the original evidence, use the OEM procedure to clear erasable records, complete any required calibration or functional check, and compare the final module status with the original warning and fault conditions.
Related BCM B Messages And Shared Harness Evidence Code Guides
Compare the related monitor families below. Shared symptoms or components do not make their repair procedures interchangeable.
U0142 Frequently Asked Questions
Does a group of U-codes mean several modules need replacing?
No. A shared physical or electrical path can affect multiple messages. Use the fault pattern to choose a tested branch; preserve the complete scan and do not turn a list of codes into a parts order.
What should I check first for U0142?
Save every module's codes and freeze frame before clearing. Confirm the full definition, suffix and VIN architecture. Then inspect recent engine-bay, harness, body-module or accessory service, connectors and shared supplies. Those facts determine whether the next test needs approved system scan access, the VIN wiring diagram and the specified electrical test equipment or a manufacturer-specific functional procedure.
Can I drive with the U0142 code?
A no-start, stalling event or multiple safety warnings overrides a routine driving plan. Arrange qualified inspection or towing when vehicle behavior is abnormal; do not road-test a suspected intermittent stall for convenience. The DTC alone cannot establish a safe driving distance.
Why did U0142 return after a part was replaced?
A returned U0142 needs its suffix, reporting module and operating state compared with the baseline. After a demonstrated harness repair, verify its routing and protection as well as communication. Recheck all modules that shared the event so that a remaining companion fault is not hidden by fixing only one label.
What should a U0142 repair estimate include?
Ask for the failed-test evidence and a VIN-specific breakdown of diagnosis, parts, labor, taxes, required setup and verification. A code alone cannot establish the repair price.
Can CR Max P diagnose and clear U0142?
On a supported vehicle, CR Max P can organize available faults, freeze frame, live data and reports, and can clear erasable records after repair. Confirm exact ECU coverage. It cannot replace the OEM functional procedure or physical measurements for the BCM B messages and shared harness evidence.
The iCarsoft Official Store Technical Team maintains the store's fault-code library. This guide organizes published technical references and verified product information; it does not document a hands-on test of a particular vehicle or claim an individual engineer's review.
Technical and cost references
- Autel AL519 DTC definitions — communication-code terminology. Definition table only; no universal test limits or failed-part conclusion.
- GM PIT6192C — specific 2.7L truck harness condition. Bounded OEM application example; scope and exceptions explained in the meaning section.
Product information: Official iCarsoft CR Max P page.
Editorial note: General diagnostic education, not a substitute for the owner's manual, current VIN-specific service information or professional inspection. Test limits, procedures, coverage and costs vary. Related articles provide context; apply only the specifications and repair procedures that match the vehicle. No universal failure rate, repair price or outcome is implied.
