Controller and Communication Faults: When the Scrubber's Electronics Report on Themselves
Floor scrubber controller and communication faults explained: CAN bus loss, display link errors, contactor and internal faults, ranked causes and tests.
Key takeaways
- Communication faults mean one module stopped hearing another, which is usually a wiring or power problem, not a dead board.
- Check supply voltage and ground at each module before suspecting the electronics.
- CAN bus wiring can be checked with the battery disconnected by measuring resistance between the two data lines.
- Main contactor faults often come from low coil voltage or welded contacts.
- Replace controllers only after wiring, power and grounds are proven good.
A controller or communication fault means a module in the scrubber's electronics has reported a problem with itself or has lost contact with another module. Typical examples are loss of communication between the display and the main board, a drive controller that stopped responding, a main contactor that did not close or did not open, a memory or configuration error, or an internal self-test failure.
These codes sound expensive, and occasionally they are. But in practice the large majority trace back to something simpler: low supply voltage to a module, a poor ground, a corroded or loose connector, or a harness chafed at a hinge. A board that loses power for a fraction of a second during a voltage dip will report a communication fault on its neighbors. The rule is to prove power, ground and wiring before replacing any controller.
What the controller is detecting
| Condition | What is detected | Common meaning |
|---|---|---|
| Communication loss or timeout | Expected messages from another module stopped arriving | Wiring, connector, power or ground to that module, or module failure |
| Bus error | Corrupted or missing messages on a shared data bus | Damaged data wire, missing terminating resistor, moisture in a connector |
| Main contactor fault | Contactor did not close when commanded, or contacts appear welded | Low coil voltage, failed coil, burned or welded contacts |
| Precharge fault | Capacitors in a motor controller did not charge as expected at power-up | Wiring, precharge resistor or controller problem |
| Supply out of range | Controller's internal supply voltage too high or low | Battery or wiring problem, or internal failure |
| Memory or configuration error | Stored settings are corrupt or missing | Firmware or parameter issue; may need dealer tool |
| Watchdog or internal fault | Processor reset or self-test failed | Often power-related; sometimes a real board failure |
| Output driver fault | A power output transistor failed or is stuck | Usually follows a shorted motor, coil or wire |
Many machines use a CAN bus (a two-wire data network) between the main board, display, drive controller and, on lithium machines, the battery management system. Others use simpler serial links. Robotic scrubbers add computers, sensors and network connections, and their fault messages are more numerous but follow the same logic. For how to find stored faults and service menus, see how to read scrubber error codes.
Typical display wording
Look for wording about communication error, no communication, CAN fault, bus error, display link, controller fault, internal error, EEPROM or memory, configuration, contactor fault, main relay, precharge, or system fault. A blank display or a display stuck on a startup screen is often part of this family even without a code. Look up the exact meaning in the service manual for your serial range, because these codes are among those most often revised with firmware updates.
Common triggers, ranked by likelihood
- Low or dipping battery voltage, especially at startup or under heavy load. See battery and low voltage faults.
- Loose, corroded or wet connectors, often after the machine was washed with a hose or pressure washer. Interlock inputs suffer the same way; see sensor and switch faults.
- Poor ground connection between modules and the battery negative.
- Harness damage at tank hinges, steering columns or deck lift points.
- Main contactor problems: worn contacts, weak coil, or contacts welded after a short.
- Aftermarket or incorrect batteries or chargers that confuse a lithium BMS link, a common issue after a lithium conversion or when the wrong charger is used (see charger fault codes).
- Firmware or configuration mismatch after a module is replaced.
- Actual module failure, often secondary to a short elsewhere.
Step-by-step diagnosis
Safety: key off and disconnect the battery before unplugging modules. Static can damage electronics; touch the frame before handling boards and avoid touching connector pins.
- Check battery voltage at rest and during key-on. Watch the meter at the main terminals while turning the key. A large dip at key-on points to the battery or main cables.
- Check supply and ground at the module that is reported missing. Back-probe its power and ground pins with the key on. Supply should be near battery voltage (or the regulated value in the manual). Measure from the module ground pin to battery negative: it should read near 0 V, typically well under 0.2 V even with loads running.
- Inspect every connector between the modules. Look for green corrosion, water, bent or pushed-back pins. Clean with electrical contact cleaner, dry fully, and reseat.
- Check the data wiring. With the battery disconnected, measure continuity of each data wire end to end. On a typical CAN bus with a terminating resistor at each end, resistance measured between the two data lines is commonly around 60 ohms; around 120 ohms suggests one terminator is missing or a wire is open, and near zero suggests the lines are shorted together. Confirm the expected value in your service manual, since not every machine uses this layout.
- Check for shorts to frame on data and power wires, especially where the harness passes metal edges.
- Test the main contactor. Key on: the coil should receive voltage and the contactor should click. Under load, measure voltage across the main contacts: more than a few tenths of a volt means burned contacts. With the key off, the output side should drop to zero; if it does not, the contacts may be welded.
- Note firmware and part numbers of any recently replaced module. Replacement boards may need configuration by a dealer tool before they communicate correctly.
Fixes
| Finding | Fix |
|---|---|
| Voltage dip at key-on | Fix battery or main cable problem first |
| Poor ground | Clean and tighten ground points; add or replace ground strap |
| Corroded or wet connector | Clean, dry, replace terminals if needed, apply dielectric grease to seals per manual |
| Data line open or shorted | Repair harness; replace chafed sections and add protection |
| Missing terminator | Reconnect or replace terminator or the module that contains it |
| Contactor worn or welded | Replace contactor; find any short that caused welding |
| Configuration mismatch | Have the dealer configure the module or update firmware |
| Confirmed module failure | Replace module, then check what may have caused it to fail |
If the machine does nothing at all when the key is turned, start with scrubber won't start. For robots, many faults also involve sensors and mapping; see robotic floor scrubbers.
Reset behavior
Communication faults usually clear when contact is restored, sometimes only after a key cycle so all modules restart together. Contactor and precharge faults normally latch until key cycle. Memory, configuration and internal faults may not clear without a dealer tool, and some are deliberately non-resettable because the controller can no longer trust its own data. A communication fault that clears and returns at random is almost always a connection, not a board.
Fault record worksheet
- Exact code or message, plus which module reported it if the display shows it
- Hour meter reading and the firmware version shown in the service menu, if available
- When it occurred: key-on, mid-run, on bumps, after washing, after charging
- Battery voltage at rest and the lowest reading during key-on
- Supply and ground voltage at the affected module
- CAN or data line resistance measured with the battery disconnected
- Connectors inspected and their condition
- Any recent repairs, part replacements, battery changes or software updates
- Whether the machine was washed or exposed to water before the fault
Robotic and connected machines may also keep a remote fault log that the manufacturer or dealer can read; ask for it when you report the problem.
Frequently asked questions
What does a communication error mean on a floor scrubber?
It means one electronic module stopped receiving messages from another, such as the display from the main board. The usual causes are low voltage, a poor ground, a loose or wet connector or a damaged data wire, not necessarily a failed board.
Does a controller fault mean I need a new controller?
Not usually. Prove battery voltage, grounds and wiring first. Many controller faults are triggered by power dips or connector problems, and a new board will fault the same way if the cause is elsewhere.
Can washing a scrubber cause error codes?
Yes. Water in connectors can cause communication and sensor faults that come and go for days. Wipe electrical areas rather than hosing them, and dry any wet connectors thoroughly.
What is a main contactor fault?
The main contactor is a heavy-duty relay that connects the battery to the motor controllers. A fault means it did not close when commanded, or the controller detected that it stayed closed when it should have opened, often from worn or welded contacts.
Why did my scrubber show a fault after a new board was installed?
Replacement modules often need configuration or a firmware update to match the machine. If it was not done, the modules may not communicate correctly. Ask the dealer to configure it with their service tool.