OBD-II Code

P1380

Severity

Not yet reviewed

Nobody on our side has assessed this code yet, so we are not going to guess at how serious it is.

Can you drive it

We cannot say

Treat it as unknown until a shop reads it with live data. If the check-engine light is FLASHING, stop driving as soon as it is safe to — that means an active misfire, whatever the code.

Indicative cost (USD)

$120–$700

From this code's diagnostic notes. Varies by vehicle, diagnosis, parts, and local labor. This is not a repair quote.

How a shop works this

Work from evidence to part, not the other way round. A code names a circuit or a symptom; it does not name the part that failed.

Note every code that is set, not just this one.
Codes that appear together usually narrow the cause faster than any one of them read alone.
Read the freeze frame — the conditions the fault was recorded under.
Cold or warm, idle or load, road speed and engine speed. A fault that only appears cold is a different fault from one that only appears under load, even with the same code on the scanner.
Confirm the fault is current rather than history.
Clear the code and see whether it returns under those same conditions. A code that does not come back may have been logged during a repair, a flat battery, or a bad connection that has since been disturbed.
Then follow the diagnostic notes further down this page, in the order they are written.
They are written in the order a shop works this code, cheapest checks first. Where they name a component, inspect its wiring and connector before replacing it.

If the code comes back after a repair, the underlying fault is still there. That is the point to bring in a scanner with live data and freeze-frame, or a shop that has one.

Common symptoms

Check engine light

Read the full diagnostic procedureP1380 means the PCM's misfire monitor cannot access rough-road data from the ABS/EBCM module over the GMLAN or Class 2 serial data bus, so it cannot…+

P1380 means the PCM's misfire monitor cannot access rough-road data from the ABS/EBCM module over the GMLAN or Class 2 serial data bus, so it cannot suppress false misfire detections caused by wheel-speed jitter on broken pavement. The misfire monitor still runs, but without rough-road compensation it will throw false P0300/P030x codes whenever the truck hits a frost heave or washboard surface. Diagnose by first checking for ABS/EBCM communication codes — if the EBCM is offline (U-codes pointing to U0121 or similar), fix the bus problem first because P1380 is the symptom, not the cause.

With a scan tool, verify rough-road data is being broadcast

the EBCM should publish a rough-road status PID that toggles between Smooth and Rough as you drive across rumble strips at 30 mph. If the EBCM is awake and the rest of the network is healthy, suspect a calibration mismatch — a flashed PCM or EBCM from a salvage yard with a non-matching part number will set P1380. The expensive misdiagnosis is chasing misfire ghosts on a truck that runs fine — recognize P1380 as a communications/calibration code, not an ignition problem.

Vehicle-specific patterns1999-2007 Silverado/Sierra/Tahoe/Yukon/Suburban 4.8L/5.3L/6.0L sets P1380 most commonly when the EBCM module is replaced with a unit from a different…+

1999-2007Silverado/Sierra/Tahoe/Yukon/Suburban 4.8L/5.3L/6.0L sets P1380 most commonly when the EBCM module is replaced with a unit from a different RPO or model year — the message structure doesn't match.
2003-2007Trailblazer/Envoy 4.2L I6 sees P1380 from the EBCM wakeup circuit failing intermittently.
2004-2008Colorado/Canyon 2.8L/3.5L/3.7L throws P1380 after wheel-speed-sensor harness damage, which knocks the EBCM offline.
2005-2009Equinox/Torrent 3.4L sets P1380 from a corroded under-seat body-control connector that carries the Class 2 bus segment.

Estimated repair$120 to $700.

Look up another code

← All OBD-II codes

More free tools

See all 9 tools