Error code reference
These are the fault indications we see on TopBrewer systems: the TopBrewer Pro and Compact coffee taps, plus the TopWater and TopJuicer companion units. For each one: what the machine is telling you, the usual causes, what's safe to try yourself, and when it's time to call.
We'll get back to you today with what it likely is.
Thanks. We received your request.
A Grajqevci technician will get back to you today to confirm your machine and book the visit. If it's urgent, call us directly at (289) 217-3796.
Something went wrong sending your request.
Please try again, or call us directly at (289) 217-3796 and we'll book your service over the phone. You can also email [email protected].
About these codes. Compiled from Scanomat product research and our own GTA service logs. Entries follow the fault names the machine and app report rather than numbered codes. Updated July 2026
The brew boiler didn't reach its set temperature inside the allowed warm-up window, so brewing is locked out.
Most heating timeouts come down to element scale or a tripped cutout. We descale, test the element and relay, and replace what the readings condemn.
The controller told a solenoid to open, and the feedback or current draw says it didn't.
If the fault survives a restart, the coil or the driver circuit has failed. We test both and replace the one that's actually at fault.
The brew unit hasn't made it back to its home position within the allowed cycle time, so the controller locks out brewing until it can verify the unit is home.
If the fault returns after a power cycle, the usual finding is seal wear plus a drifting home switch. We slide the unit out, fit new seals, clean the cam paths, and verify the switch actuates cleanly.
The brew-unit drive motor is drawing current but the unit's position isn't advancing, so the controller cuts power to protect the motor.
A motor timeout is a mechanical fault and won't clear itself for long. We service the brew unit end to end and replace the motor or gear if it's worn.
The bean-detect sensor reads no beans, or beans have bridged above the grinder throat. The machine prompts for a refill and holds brewing until it sees beans again.
If the alert persists with a full hopper, the sensor needs a proper clean or a replacement. Quick work once the unit is out.
The grinder ran past its maximum dose time without hitting the target, so the controller stopped it to protect the motor.
If beans are flowing and the timeout keeps coming back, the burrs are worn or the motor is down on torque. We measure the dose by weight and replace whichever part the numbers point to.
The milk pump isn't drawing, or the flow meter isn't registering milk movement, so the machine aborts milk drinks rather than serve them wrong.
Most of these resolve to a worn impeller or a clogged pathway, both straightforward at the machine. A daily clean cycle that actually runs keeps it from coming back.
The milk heat exchanger isn't reaching the programmed temperature, so milk drinks pour cold or lukewarm instead of at spec.
If the test drink still pours cold, the sensor or the exchanger needs attention. We test the sensor, descale the milk circuit, and replace whichever part is failing.
The milk-system clean cycle hasn't run within its configured window, so milk drinks may be locked out until one completes. It's a hygiene safeguard rather than a machine fault.
A clean cycle that won't complete is stalling somewhere in the pathway. We find the blockage or the failed sensor and put the routine back on schedule.
The filter cartridge counter has reached its configured limit. Left alone, water taste drifts first and boiler scale follows.
A counter that won't reset after a valid replacement points at the controller's memory retention, which we verify and fix.
On TopWater installs the filter cartridge has reached capacity, or on sparkling-capable models the CO2 supply has dropped below its threshold.
Fresh consumables plus a persisting alert means the regulator or the counter retention needs diagnosing. Both are quick once we're at the cabinet.
The controller is signalling a fault through the tap's status LED or display. Which fault it is gets read through the Scanomat service interface, not guessed from the light.
We connect through the service interface, read the full log, and fix the actual fault rather than the symptom at the tap.
The Scanomat cloud has flagged a firmware update for this unit, or a previous update stopped partway through.
Failed updates are almost typically recoverable. We reflash from the service interface and restore the drink profiles afterwards.
The brew flow meter isn't sending pulses during dispense, so the controller can't measure volume and aborts the cycle.
Cleaning a flow meter is routine work. We clear the turbine, verify the pulses, and chase the pump or valve if the meter turns out to be innocent.
The descale counter has reached its interval, calculated from the water-hardness setting and brew volume. Brewing continues through a grace period, but the clock is running.
If the alert survives a completed descale, the counter or the hardness configuration needs checking. We verify both and confirm the boiler is genuinely clean while we're in there.
The boiler's NTC temperature sensor is reading open or shorted, and the controller won't regulate heating on a sensor it can't trust.
An open or shorted NTC doesn't recover on its own. We test the resistance and fit a new sensor.
The spent-puck counter has hit its programmed limit, and the machine won't dispense until the bin is emptied and the counter resets.
If the alert keeps returning after a clean empty, the microswitch is misreading and needs replacement.
The drip-tray float or presence sensor is reporting a full or missing tray, and the app prompts whoever is nearest to deal with it.
Persistent alerts after a clean, empty, properly seated tray mean the float or switch needs servicing.
The cabinet door or service panel microswitch reads open while the machine is running, so the unit halts its moving parts as a safety lockout.
A door fault that persists with the door properly shut means the switch needs cleaning or replacement. Five minutes of work once the unit is slid out.
The under-counter unit can't reach the Scanomat cloud. The app shows the machine offline, and remote diagnostics and order routing stop until the link returns.
If the building's network is healthy and the unit still shows offline, the network module or the cloud-side registration needs work. We sort it alongside your IT contact.
The user app can't complete pairing with the TopBrewer unit, so orders won't route until pairing succeeds.
Pairing faults that don't trace back to the phone need the Bluetooth module or the app account put right. We handle both ends.
No codes match your filters.
Try a different search term, clear the filters, or call us and we'll diagnose from your display.
Code you can't find?
Trusted by Toronto's most demanding teams
FAQ
9 answers about resetting codes, recurring faults, firmware versions, and when DIY ends.
Updated July 2026
Every documented TopBrewer fault we see is listed above, with its meaning, common causes, and what to try before calling a technician. If the code on your machine isn't on this page, call us with the exact display string and we'll work it out by phone.
Sometimes. Many TopBrewer codes clear after a power cycle, a completed descale, or a counter reset through the service menu. Codes tied to a hardware fault (failed sensor, blown element, board issue) will return immediately and need a technician. Each code above lists what's safe to try first.
A code that returns after a power cycle is signalling a real fault, not a glitch. The underlying part (sensor, heating element, valve, motor, board) needs replacement. Repeat codes are diagnostic gold for us, so call with the exact code and any timing or symptom pattern you've noticed.
TopBrewer updates fault tables across firmware revisions and model generations, and not every code is documented publicly. We see codes in the field that aren't in any published list. Call us with the exact display string and the model and we'll work it out from our service log.
Most calls in Toronto and the immediate GTA get same-day on-site response when scheduling allows. Tell us the code and the model when you book and we'll bring the right parts on the first visit so the repair finishes the same day in most cases.
No. We're an independent service provider, not affiliated with TopBrewer, and we work on machines outside the manufacturer's authorized network routinely. That independence lets us service older or out-of-warranty machines authorized networks may decline, and quote transparently every time.
Depends on the machine, the code, and the cost. We give you honest math on this. If repairs are starting to exceed roughly 50% of a refurbished replacement and multiple major systems are throwing codes, we'll tell you it's time to look at replacing rather than running up the repair bill.
If your machine is under the manufacturer's warranty, independent service may affect coverage depending on TopBrewer's specific terms. Try the manufacturer's authorized network first. If their response is slow or they decline coverage for your code, call us and we'll service it on standard terms.
21 codes are documented above, organized by the system they affect. The list is compiled from manufacturer service literature, technician forums, and our own service log. We update it as new codes appear or firmware adds new states.
By the numbers
Our franchise machine has been quietly degrading for months. Their tech rebuilt the brew unit, recalibrated the grinder, and the espresso quality came back instantly.
We diagnose TopBrewer codes by phone routinely. Same-day on-site dispatch if it needs hands on the machine.
Call (289) 217-3796 now →