Epson firmware blocks the network reset, but a USB cable still reaches the ink counter

An Epson printer can reject a maintenance command over Wi-Fi and accept the same command through a USB cable, apparently because it needed to hear the request in person.

The independent epson_print_conf project documents that split between the two connections. Its network route uses SNMP. Its USB route reaches the printer’s EPSON-CTRL service through the IEEE 1284.4 protocol, also called D4. The tool can carry status checks, EEPROM reads and writes, counter resets and access-key detection through that wired connection.

The README says affected firmware disables network EEPROM access for security reasons. That includes some recent models and older printers with updated firmware. A network refusal therefore doesn’t, by itself, establish that the maintenance operation is unavailable through a cable. The firmware has closed one connection, with the owner still standing beside a perfectly reachable USB port.

Waste ink is the catch worth keeping in the headline’s shadow. Cleaning cycles discard ink, and the printer uses counters to track the waste system. At the limit, printing stops to help prevent overflow. Resetting a stored number cannot remove a drop of that ink, however reassuring a zero looks on screen (lovely little number).

The project calls a reset “just removing a lock.” Its documentation warns that an unserviced tank can spill and affect print quality. A useful repair path pairs the physical maintenance with the correct counter operation for that printer. An owner who has replaced the waste tank still needs the counter operation, while an owner who has only changed the number still has a full waste tank.

The software also separates temporary relief from a permanent counter reset. A temporary reset can bypass a full-maintenance-box warning, but the setting disappears when the printer reboots and does not change the EEPROM. The permanent operation changes stored values. Confusing those two could turn a successful afternoon into the same warning tomorrow morning.

Verification deserves as much attention as the reset button. The README describes firmware that replies successfully while discarding writes. By default, the tool reads EEPROM values back after changing them. During key detection, it checks that a byte actually changed, then restores and verifies the original value. A cheerful acknowledgment from a printer has apparently joined the list of things that require receipts.

The connection also changes the setup burden. On Windows, the project says it uses the interface exposed by the existing Epson driver without replacing that driver. Linux and macOS use libusb to claim the relevant interface, then return it when the connection closes. The README is the authority for those requirements; this is the project’s documented behavior, not a hands-on printer test.

A repair utility becomes more useful when it admits where models differ. The README describes an ET-2814 case where reset bytes survived a restart but the overflow status remained. That printer family needed an additional completion step. The project explicitly warns against applying its address to arbitrary models.

That makes a universal reset recipe a poor shortcut. If independent maintenance tools keep adding model-specific checks, the helpful improvement will be fewer false success messages and clearer supported paths. The remaining work depends on the exact printer, firmware and physical waste system, not merely finding a cable in a drawer.

USB still can’t wring out a sponge.