MLU-1 documentation › Documentation desk
Documentation desk
This library is maintained by the people who install and repair the units, which is why it is blunt about what does not work. If something here is wrong, out of date, or missing the one step that would have saved you an hour, tell us — that is how every quirk on these pages got written down.
We reply by email. Corrections are published with the next revision and the page date changes.
✉️
docs@printdoc.digital
Documentation corrections and missing procedures.
Documentation corrections and missing procedures.
🧰
Diagnostic bundles
Attach the file from mluctl diag bundle and say what you were doing when it went wrong.
Attach the file from mluctl diag bundle and say what you were doing when it went wrong.
📦
Hardware faults
A unit with a fast red status LED is a replacement, not a support case. Raise it through the usual service channel.
A unit with a fast red status LED is a replacement, not a support case. Raise it through the usual service channel.
Before you write about a device that will not answer:
run mluctl net test <address> and paste the output. It settles the
first three questions we would otherwise have to ask.
Please do not send held job files. They are encrypted, we cannot read
them, and they may contain the customer’s documents. The job metadata from
mluctl queue show is what we need.
Useful first
Most questions that reach us are already answered in the symptom table or in what each closed port costs. Neither takes long to read, and both were written from the questions people sent.
PreviousRelease notes