Everything an administrator needs for the PrintDoc MLU-1 meter and logging unit: where to put it, what it needs from the network, how it finds printers, what it reads from them, and what to do on the morning it stops answering.
One fanless unit on the customer network, four jobs. Nothing on it is a print driver, and it never becomes a print server for anything except the secure release queue.
Page counters, by colour and by paper size, polled over SNMP on a schedule and kept for three years so a billing dispute has something behind it.
Toner, drums, waste containers and maintenance kits, with per-model thresholds. A cartridge is ordered because the unit saw it coming, not because someone called.
Traps and polled status turned into a short list of things that matter, deduplicated, with quiet hours, so a jam at 02:00 does not page anyone.
One queue for the whole floor. The job waits on the unit until the person is standing at a device and enters a PIN or taps a card.
In order. The three setup pages take about forty minutes on a site that is already cabled.
Dimensions, power, ports, mounting and environmental limits for MLU-1 and MLU-1P.
step 1 · before you orderMounting, the service port, the setup wizard, and the checks that prove it worked.
step 2 · on siteEvery port the unit uses, in which direction, and what breaks when one of them is closed.
step 3 · with the network teamWhat you set up once per site, in the order the console presents it.
Scan ranges, SNMP credentials, how a device is matched to a profile, and what to do with the ones that answer but refuse to identify themselves.
Poll schedule, which counters are read on which platforms, retention, and the three export formats the billing desk accepts.
Thresholds, per-model overrides, the difference between a percentage and a page estimate, and why a brand-new cartridge sometimes reports 40 %.
The single hold queue, PIN and card identification, retention and printing limits, and how a job is moved to another device when the first one is broken.
Look-up material. Nobody reads these front to back, and they are not written to be read that way.
Every page of the console, what it changes, and which role can see it.
All commands with real examples, exit codes and the four that need a maintenance window.
Every code the unit can raise, its severity, and the action that clears it.
LED patterns, symptom table, and how to collect a diagnostic bundle.
What changed in each 3.x release, and the two upgrades that need a step in between.
Corrections, gaps, and questions this library does not answer yet.
Figures are for a standard MLU-1 with the stock configuration described in these pages.
Restore the configuration backup first and let discovery run afterwards. The order matters: a fresh scan on an empty database will invent new device records and your meter history will not follow them.