+86-18050089566（WhatsApp/wechat）
+86-18050089566（WhatsApp/wechat）
Time：2026-10-04 Views：0
Most "the printer is broken" calls are not broken printers. They are paper in the wrong way round, a queue on a shared PC that fell asleep, an address that changed over the weekend, or a job too big for the buffer. Work it in order: cheapest check first, one branch decision at a time.
Ask whoever noticed it three things. One printer or all of them? More than one machine gone quiet at the same time in one building is a network or POS-server fault, not a printer fault. What changed? A new roll, a power cut, an OS update on the till, a new starter on the pass — printers rarely fail without a preceding event, people just do not report it. What comes out? Nothing, blank paper, paper half cut, or garbage characters.
Power off. Hold the feed button down, power on, keep holding a second or two, release. On the ESC/POS class that prints a self-test and a settings page: interface, address, baud rate, firmware. This one test splits the whole fault tree and needs no tools, no laptop and no driver.
If the self-test prints cleanly, the printer is healthy. Mechanism, head, paper, supply and cover sensor all work, so the fault is the link, the settings, the queue or the software — go to steps 5, 6 and 7 and do not dismantle the machine. If it does not print at all, the unit is the problem — steps 2 and 3, and keep the cutter shut until step 4.
Two results sit in the middle: garbled characters mean the mechanism is fine and the data or serial settings are not, and a crisp page with a vertical white line down it is dead head elements, which no setting recovers.
Names vary, states do not, broadly across the class. Online steady means ready — if nothing prints, the job is not arriving, so step 6. Online flashing means the printer is being told to print and cannot: paused at the driver, a jam it has detected, or a job it is still swallowing. Pause means somebody paused it, and usually not at the printer: a driver-side pause, or a queue held on a shared PC. Error or blinking red means a condition it will not print through — no paper, cover unlatched, jam, cutter blockage, overheated head. Steps 3 and 4, then power-cycle.
Thermal paper works on one face only. There is no ink and no ribbon: the printer burns the image into a coating, so a roll loaded reversed gives a perfect feed, a normal-looking ticket and no text at all. That one mistake accounts for an unreasonable share of "printer dead" reports.
Prove the coated side in five seconds. Tear off a short strip and scratch it firmly across the width with a fingernail: the coated face shows a dark grey-to-black mark where you pressed, the back does nothing. If neither face marks, it is not thermal paper, which happens when a supplier ships plain or transfer stock in the same wrapper. Then load it so the coated face meets the head. Conventions differ between top-loaders and front-loaders, so make it repeatable once: mark the end of a known-good roll with a pen, photograph the open door with the roll sitting right, and tape the photo inside the paper cupboard.
Power off first. Open the cover and look: the usual cause is a torn strip from a hand-tear wrapped round the roller, or an offcut held in the cutter from an earlier partial cut. Do not pull paper backwards against a guillotine blade — you will shred it into the mechanism and cut your hand. Most cutters have a release, a lever or a knurled wheel under the mechanism, that retracts the blade; use it, then ease the paper out in one piece. Get every fragment out, because dust left near the platen is why the same machine jams three times in a week. Close the cover on both latches and run the self-test before handing the station back.
Once the self-test passes, the fault lives between the printer and the application, and the symptoms depend entirely on the cable or the radio.
Boring order: a port on the back of the PC rather than a front panel or a monitor hub; a different cable, because printer USB leads get pulled daily; no hub in the path. Windows listing "Unknown USB Device (Device Descriptor Request Failed)" means enumeration failed, which is usually cable, port or supply rather than the printer — remove the device in Device Manager, unplug, reboot, replug, let it reinstall.
Typical symptom: the printer had an address, the network was touched, and now nobody can reach it — or it works until Monday. A printer given a manual address inside the DHCP pool will have that same address handed to a laptop by the server, and a re-scoped subnet, a switch moved to a new VLAN or a batch of leases renewed over the weekend all produce the same Monday outage. The discipline: a DHCP reservation keyed to the printer's MAC, inside the pool and written down, or a static address deliberately outside it, with mask and gateway labelled on the chassis. No link light at all is physical — the patch panel, or the switch that rebooted.
Paired and connected are different states and only the second prints. A tablet holding a bond to a printer currently connected to something else queues tickets into nowhere, because these mechanisms serve one host at a time: remove the bond at both ends and re-pair. After an OS update, expect the bond or profile to have been dropped and the printer entry your app used to point at a re-added device with a different handle. If the platform is iOS and the printer is a plain Bluetooth SPP mechanism, no number of re-pairings helps.
Baud rate, parity, data bits and stop bits have to be identical at both ends, and the self-test settings page is the only place you can read what the printer thinks it is set to. Flow control is the subtler half: with none selected, a ticket carrying a logo outruns the buffer.
Restart the print spooler on whatever machine owns the queue, then clear the stuck jobs: one corrupted job at the head of the queue holds an entire printer's worth of tickets. Check the driver for a pause or "offline" state the printer never asked for. A queue hosted on a PC that sleeps, gets renamed or leaves the domain leaves every other till pushing tickets into a machine nobody can reach, which is why kitchen and bar printers should be reached directly by address and shared by nobody.
Two faults that look like hardware and are really layout. The print stops partway, online lamp flashing, a partial ticket in the jaws: the job exceeded the buffer — a loyalty poster, a whole report sent as one giant bitmap. These machines take data into a buffer of tens of kilobytes and an image must be dithered and streamed line by line, so send shorter jobs and have the app commit per ticket rather than per report. The right-hand column of every receipt is missing: the driver's page width does not match the paper, an application laid out for 80 mm columns printing to a 58 mm machine. Make the driver's paper size and the app's template agree with each other, not with the datasheet.
Recoverable means the machine is intact and something around it is in a state: paused, out of paper, jammed, wrong address, stuck queue, oversized job, reversed paper — fixed by a person taking an action, with no part needed. Hardware means the unit has changed: no self-test on a known-good supply, vertical streaks through the print, motor noise with the roller not turning, a head that stays cold, a cutter that stalls every third ticket. Faults that appear only after half an hour of service belong with hardware too — that is heat, and it is the head or driver board wearing, not the network.
Set a timebox and honour it. On a Saturday evening the arithmetic is not the price of the printer; it is an hour of technician time plus the tickets the venue cannot turn away. If the machine passed its self-test and you have not found the fault inside the box, the fault is in the shop's software or network — stop dismantling the printer and escalate that instead. Swap when the head is streaking and the supplier will not sell the head alone, when the cutter stalls repeatedly on known-good paper, or when faults return within weeks of a repair. Head and cutter are consumables, and a unit that has eaten both is not temperamental, it is finished.
Why is my receipt printer on but not printing? A printer with a steady online lamp and no output is nearly always in one of three states — paused at the driver rather than at the machine, addressed on a network the till cannot reach, or holding a job too large for its buffer — and the self-test separates all three from a real printer fault in twenty seconds.
What does a blinking red light on a thermal printer mean? A blinking red or error lamp means the printer has detected a condition it will not print through — normally out of paper, a cover that has not latched, a jam or cutter blockage, or an overheated head — and it clears when that condition does, not when the power is cycled.
How do I tell which side of the receipt roll is the thermal side? Scratch the surface firmly with a fingernail: the coated face shows a dark grey or black streak where you pressed and the backing shows nothing, so a reversed roll that feeds normally and prints blank is identified in five seconds.
Why does our printer only stop working on Mondays? A manual address inside the DHCP pool gets handed to someone's laptop by the server, and renewed leases, a re-scoped subnet or a switch moved to another VLAN over the weekend all break it — put printers on a documented DHCP reservation keyed to MAC, or a static address outside the pool.
When should I replace a receipt printer instead of repairing it? Replace it when the head streaks and the head is not sold separately, when the cutter stalls repeatedly on good paper, or when faults return within weeks of a repair — past that point the machine consumes more in labour and lost tickets than it is worth.
services · FAQ · Receipt and label printers · technical-recognition · Product documentation and SDKs · Android PDA and POS terminals · CashRegister · Contact EDOO
About
Products
Solutions
Support
News
