Use this path when the charger powers up normally but current never reaches the battery.
Run these quick checks before you assume the charger has a deeper hardware fault.
AC socket is energised. Test it with another appliance.
AC plug is fully inserted, undamaged, and its pins are clean and straight.
DC output connector is fully locked into the vehicle inlet, not just inserted.
Both AC and DC cables are free of cuts, kinks, crushing damage, or severe bending.
Charger vents are unobstructed and have at least 10 cm clearance on all sides.
Ambient temperature is below 45 C.
No extension cord is being used, or the cord is correctly rated and within the allowed length.
Universal reset has been tried: AC off for 30 seconds, then reconnect.
Follow the steps in order. Stop and escalate as soon as a step says the issue is not field-serviceable.
Solid green means the battery is already fully charged. If the charger is showing a yellow-first fault sequence, move to the fault-pattern guide instead of treating it like a no-charge case.
Disconnect and firmly reconnect the DC output connector. You should feel or hear a positive lock into the vehicle inlet.
If pack voltage is below 15 V on a 48 V pack, or below about 2.0 V per cell, the charger is dealing with a deep-discharge case rather than a normal charge start.
Check that the BMS is powered, CAN_H and CAN_L are not swapped, termination is about 60 ohm across H and L with the bus de-energised, and there is no CANbus baudrate mismatch.
Disconnect AC for 30 seconds, reconnect the DC side, then reconnect AC. This clears many startup-state and handshake issues.
If the charger still powers up but will not charge after 3 correct restarts, the issue likely needs pack-side or charger-side service work.
Keep moving between the support guides below to narrow the issue faster.
Pick a symptom and follow the correct field checks before escalating to service.
See how Solterra chargers wake deeply discharged batteries and what risks apply during activation.
Follow the charger-BMS handshake flow, message types, and CAN fault diagnosis guidance.
