A car that will not enter READY may produce a long list of communication faults. The useful question is which controllers disappeared first, and under what conditions. Photograph the warning and preserve the complete scan before anyone clears the codes.
What these code families point towards
HELLA’s generic reference associates U0110 with missing communication from the drive-motor controller, and U0111/U0112 with battery-energy controllers A/B. The letters do not identify a physical battery location across every vehicle. Use the manufacturer’s full description and any suffix. Generic reference.
Build a timeline, not a replacement list
Tell the workshop whether the car drove normally before charging, whether it woke up after storage and whether the warning followed a flat 12-volt battery. Separate an old stored code from a fault that returns immediately. An engine-only reader may not show the battery, gateway or charger information needed for this investigation.
- Send make, model, year and powertrain details.
- Include every reporting controller, complete code and recorded status.
- Describe whether AC charging, DC charging or both are affected, where supported.
- Record recent battery, collision, water-ingress or programming work.
- Keep any earlier scan so the workshop can compare the sequence.
Vehicle diagnosis or a posted module?
A communication problem may depend on wiring, supply, wake-up conditions or another controller in the vehicle. Posting the named module without that context can leave the original fault unresolved. Ask AXION to review the information before removal or delivery. Do not open a high-voltage enclosure or bridge an interlock to see whether communication returns.
Prepare an enquiry or identify your vehicle. These codes are starting points for diagnosis, not proof of a failed traction battery or inverter.
Reviewed September 2026. Use the complete manufacturer-specific fault description and vehicle repair information.