AutoLogicTools

OBD-II trouble code

U0112: Lost Communication with Battery Energy Control Module B

Before chasing a wire, establish that a second battery controller exists on this vehicle at all — plenty do not, and on those the code is a configuration error. Where B does exist it is a monitoring unit rather than the contactor authority, so the car usually still moves, just worse.

High severityNetworkNetwork CommunicationDo not drive

Quick facts

System
Network
Category
Network Communication
Severity
High severity
Drivable
No — stop driving until repaired
Repair cost range
$150$2,200
DIY difficulty
Shop recommended

What does U0112 mean?

The first question on this code is not electrical. It is whether the vehicle in front of you actually has a second battery energy control module. A great many hybrids and EVs are built with only one, and on those the correct interpretation of a U0112 is that some module has been told to expect hardware that was never fitted. That happens for ordinary reasons: a replacement controller flashed with the wrong variant, a module configured for a larger battery option than the vehicle was built with, or a used part transplanted from a higher-specification car and never reconfigured. Checking the build and option content before opening a harness is free, and on a single-controller vehicle it is the whole diagnosis.

Where B genuinely exists, the architecture tells you what to expect. Multi-controller battery systems come in two broad shapes. In a master-and-satellite arrangement, the primary controller owns the contactors and the state-of-charge calculation while the satellites do nothing but measure a group of cells and report upward. In a twin-pack arrangement — found on some plug-in hybrids and on a number of commercial and light-truck hybrids — there is a physically separate second battery with its own controller. Either way, module B is a reporter rather than an authority. It does not decide whether the pack may be connected.

That distinction changes the entire complaint. Losing the primary controller leaves an inert vehicle. Losing B usually leaves a vehicle that still moves and still charges but does noticeably less of both, because a battery management system will not use cells it cannot see. Owners describe it as range falling off a cliff, as acceleration going soft, or as charging that stops well short of full. It is a derate, not a shutdown. The vehicle should still not be relied on in that state — running a pack with a section unmonitored means temperature and cell voltage limits are being enforced on incomplete information — but understanding that the car still drives prevents a lot of misdirected diagnosis.

How these satellites are connected is the other thing worth knowing, because it is unlike ordinary vehicle networking. Cell-monitoring units are frequently linked to each other in a daisy chain — a serial interconnect that runs from board to board through the pack — rather than each hanging independently off the vehicle bus. A daisy chain has one important property: a single broken link silently removes everything downstream of it. So the module the code names may be in perfect condition, with the actual fault one connection earlier in the string. That is why on this code you check the interconnect in order from the master outward rather than going straight to the module that was reported missing.

One further pattern is worth acting on. Those interconnect ribbons run inches from cell tabs sitting at full pack potential, so if the pack has taken in moisture or a board has been contaminated, isolation problems tend to surface on this circuit first. A U0112 arriving alongside an isolation or leakage code should be treated as a pack integrity concern rather than a networking one, and handled accordingly.

Finally, if U0111 is stored with it, stop treating this as a B problem. Two controllers going quiet at once points at the shared supply, the shared ground or the trunk they both report through, not at two independent failures.

Common causes

  • Vehicle has only one battery controller and a module has been configured or flashed for a variant that has two
  • Replacement or used control module never configured to the vehicle's actual battery option content
  • Broken link earlier in the cell-monitoring daisy chain, which removes every unit downstream of it including this one
  • Interconnect ribbon or board-to-board connector inside the pack unseated, corroded or damaged during service
  • Moisture inside the pack enclosure contaminating a monitoring board
  • Second battery pack's harness damaged where it runs between enclosures on twin-pack vehicles
  • Satellite monitoring board failed internally
  • Shared low-voltage supply or ground fault affecting more than one controller, which normally sets U0111 alongside
  • Connector disturbed during previous pack, seat, floor or cargo-area work on vehicles where the second unit lives under trim

Symptoms

  • Usable range or electric-only distance noticeably reduced while the vehicle still drives
  • Acceleration softer than normal, with the system limiting available power
  • Charging stopping short of full, or a lower-than-expected state of charge reported at the end of a session
  • State of charge that jumps or behaves inconsistently between journeys
  • Hybrid or EV system warning illuminated without the vehicle refusing to start
  • Scan tool reaching the primary battery controller normally but not the second unit
  • Isolation or leakage codes stored alongside, which changes this from a network concern to a pack integrity one
  • Symptoms that appeared shortly after work involving the pack, the rear seat, the floor or the cargo area

Diagnostic steps

  1. 1.Confirm from the vehicle's build and option content that a second battery controller is actually fitted. On a single-controller vehicle this code is a configuration fault and no wiring exists to chase.
  2. 2.If a module was recently replaced, reprogrammed or transplanted from another vehicle, check its configuration against the pack that is really installed. A controller expecting a larger battery option will report a unit that was never there.
  3. 3.Establish which architecture this is — a master with satellite monitoring boards, or two physically separate packs. The two are diagnosed in completely different places.
  4. 4.Check whether U0111 is also stored. Both controllers silent at once points at a shared supply, ground or trunk rather than at two separate failures.
  5. 5.Follow the manufacturer's de-energising procedure in full before opening any enclosure or probing inside the pack.
  6. 6.On a daisy-chained monitoring system, work outward from the master and check each link in order. The named module is often healthy and the break is one connection upstream of it.
  7. 7.Inspect interconnect ribbons and board-to-board connectors for unseating, corrosion, chafe and heat damage, paying attention to anything disturbed by previous service.
  8. 8.Look for moisture inside the enclosure and check the case drains. Contamination on a monitoring board shows up on this circuit before it shows up anywhere else.
  9. 9.On twin-pack vehicles, follow the harness between the two enclosures, especially where it crosses the floor, a subframe or a mounting bracket.
  10. 10.Check for stored isolation or leakage codes before continuing. If they are present, treat the vehicle as a pack integrity issue rather than a communication one.
  11. 11.Replace the satellite module only once the chain ahead of it, the supply, the ground and the configuration have all been proven, and configure the new unit to the pack after fitting.

Repair cost

$150$2,200

The cheapest outcome here has no parts in it at all: correcting a module's configuration on a vehicle that never had a second controller is $150 to $400, and it is a real and reasonably common result. An interconnect or connector repair inside the pack is $400 to $1,100, driven almost entirely by the labour to de-energise, open and reseal the enclosure. A harness repair between enclosures on a twin-pack vehicle is $300 to $900. A satellite monitoring board or second-pack controller is $600 to $2,200 including configuration. Where moisture has got into the enclosure, price the case seal and drain work separately, because an electrical repair inside a pack that still lets water in will not last.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with control module replacement & programming preselected. Adjust labor rate and vehicle category to fit your situation.

DIY vs shop

Leave this one to a qualified shop. It typically involves emissions-critical components, refrigerant handling, or other work that requires manufacturer-grade tooling, training, or certification. DIY attempts often produce a more expensive problem than the original code.

Related codes

Frequently asked questions

How do I know whether my car even has a battery control module B?

Check the build sheet, the option content or the manufacturer's service data for the specific battery configuration your vehicle left the factory with. Many hybrids and EVs have only one battery controller. If yours is one of them, this code means some module has been told to expect hardware that does not exist — usually after a replacement or used control unit was fitted without being configured properly. That is a programming fix, not a wiring one, and finding it out first saves a great deal of wasted work.

Why does the car still drive when this code is set, but not with U0111?

Because the two modules do different jobs. The primary controller is the only thing authorised to close the contactors, so losing it leaves the pack disconnected and the vehicle inert. Module B is a monitoring unit — it measures a group of cells and reports upward. Losing it means the system is missing information about part of the pack, so it refuses to use what it cannot see. The result is reduced range, reduced power and charging that stops early, rather than a car that will not move.

Could the module named in the code actually be fine?

Very possibly. Cell-monitoring units are often linked in a daisy chain rather than each hanging separately off the vehicle bus, and a daisy chain fails in a particular way: one broken link takes out everything downstream of it. So the unit reported missing may be perfectly healthy while the real break sits one connection earlier in the string. That is why the chain should be checked in order from the master outward instead of going straight to the module the code names.

Is it safe to keep driving while I get it looked at?

It will usually still drive, but that is not the same as it being a good idea. With part of the pack unmonitored, the system is enforcing its temperature and voltage limits on incomplete information, and the protection those limits provide is weaker than it appears. Short, local journeys while you arrange a proper inspection are reasonable; extended use is not. If isolation or leakage codes are stored alongside this one, stop driving and have the vehicle assessed before anything else.

Editorial context

About This Diagnostic Information

AutoLogicTools diagnostic guides explain OBD-II trouble codes using recognized code definitions, standard automotive diagnostic principles, and practical automotive context. A trouble code records a condition detected by a control module. It does not automatically identify a failed part, and the right diagnostic procedure can vary by vehicle.

Manufacturer service information, technical service bulletins, wiring diagrams, and vehicle-specific procedures should take precedence when available.

AutoLogicTools was founded by Vincent Fisk, an automotive locksmith and shop owner in San Diego with hands-on experience in vehicle keys, immobilizer systems, electrical issues, modules, programming, and diagnostics.