# Status messages

> Every standard RDM status message ID by number, a fixture's report of a fault or warning in itself, with what each means at the bench.

- **Status IDs:** 34
- **Numbered in:** E1.20, Appendix B
- **Version:** 0.12.0
- **Runs on:** macOS 15 Sequoia or later, Apple silicon or Intel
- **Needs:** An Enttec DMX USB Pro with its DMX/RDM firmware (major version 2), or, on a rig, an Art-Net 4 node with RDM on at its ports
- **Price:** Free

A fixture reports its own faults and warnings as status messages, each with an ID. The standard ones are numbered in [E1.20](https://tsp.esta.org/tsp/documents/published_docs.php)'s Appendix B; a maker may add its own, which only the fixture can describe. RDMBench's [report](/help/report/#status-messages) and [monitor](/help/monitor/) show them in words. Here is every standard ID by number, with what it means at the bench, in RDMBench's words rather than the standard's.

- [`0x0001` STS_CAL_FAIL](/codes/status/0x0001/): A moving part, named in the message by its slot (pan, tilt, a wheel), did not finish calibrating at power-up or reset. Look at that part's motor, belt and home sensor, and anything blocking its travel, and watch it reset.
- [`0x0002` STS_SENS_NOT_FOUND](/codes/status/0x0002/): The unit could not find the home or position sensor for the part the message names. Usually the sensor, its cable or connector, or a magnet or flag that has moved; less often the part never reached the sensor at all.
- [`0x0003` STS_SENS_ALWAYS_ON](/codes/status/0x0003/): The position sensor for the part the message names reads as triggered all the time: shorted, stuck, or with something parked in front of it. The unit cannot find home while it does.
- [`0x0004` STS_FEEDBACK_ERROR](/codes/status/0x0004/): By its own position feedback, the part the message names is not where the unit sent it. Lost steps, a slipping belt, a stiff bearing, or a feedback sensor that cannot be trusted.
- [`0x0005` STS_INDEX_ERROR](/codes/status/0x0005/): The part the message names lost its reference position, such as a wheel that skipped. A reset may clear it; if it comes back, look at the index sensor and anything that lets the part slip.
- [`0x0011` STS_LAMP_DOUSED](/codes/status/0x0011/): The lamp has been turned off, by a controller, the panel or the unit itself. Not a fault by itself; if no one turned it off, look at the unit's lamp settings (off on DMX loss, say) and its temperatures.
- [`0x0012` STS_LAMP_STRIKE](/codes/status/0x0012/): The unit tried to light the lamp and it did not come on. A lamp at the end of its life, the igniter or ballast, or a lamp still too hot to restrike.
- [`0x0013` STS_LAMP_ACCESS_OPEN](/codes/status/0x0013/): The unit reads the lamp cover or its interlock switch as open and will not run the lamp. Check that the cover is shut and the switch makes contact.
- [`0x0014` STS_LAMP_ALWAYS_ON](/codes/status/0x0014/): The lamp is on when the unit expects it off: a relay or ballast stuck on. Treat it as a safety problem until it is found.
- [`0x0021` STS_OVERTEMP](/codes/status/0x0021/): A sensor, numbered in the message, reads above its limit, and the message carries the temperature. Fans, filters and dust first; then the sensor itself, if the reading does not match how warm the unit really is.
- [`0x0022` STS_UNDERTEMP](/codes/status/0x0022/): A sensor, numbered in the message, reads below its limit, and the message carries the temperature. A unit fresh from a cold truck may say this until it warms; in a warm room, suspect the sensor.
- [`0x0023` STS_SENS_OUT_RANGE](/codes/status/0x0023/): A sensor, numbered in the message, reads outside what it can measure. More often a sensor open or shorted, or its connector off, than a real extreme.
- [`0x0031` STS_OVERVOLTAGE_PHASE](/codes/status/0x0031/): The supply on the phase the message numbers is above the unit's limit, and the message carries the voltage. Check the supply before the unit: a wrong voltage setting, or a lost neutral on a three-phase feed.
- [`0x0032` STS_UNDERVOLTAGE_PHASE](/codes/status/0x0032/): The supply on the phase the message numbers is below the unit's limit, and the message carries the voltage. A long or thin cable, a weak generator, or a voltage setting wrong for the supply.
- [`0x0033` STS_OVERCURRENT](/codes/status/0x0033/): The current on the phase the message numbers is over the unit's limit, and the message carries the current. A shorted load or output stage, or more load than the circuit is rated for.
- [`0x0034` STS_UNDERCURRENT](/codes/status/0x0034/): The current on the phase the message numbers is below what the unit expects, and the message carries the current. On a dimmer, a lamp out or a load not connected.
- [`0x0035` STS_PHASE](/codes/status/0x0035/): The phase angle of the supply phase the message numbers, in degrees. A reading, not a fault.
- [`0x0036` STS_PHASE_ERROR](/codes/status/0x0036/): Something is wrong with the supply phase the message numbers: missing, or out of order on a multi-phase feed. Check the feed before the unit.
- [`0x0037` STS_AMPS](/codes/status/0x0037/): A current, carried in the message. A reading, not a fault.
- [`0x0038` STS_VOLTS](/codes/status/0x0038/): A voltage, carried in the message. A reading, not a fault.
- [`0x0041` STS_DIMSLOT_OCCUPIED](/codes/status/0x0041/): From a dimmer rack: that position holds no dimmer the rack can drive, empty or filled with something else. Check what is seated there against the rack's own setup.
- [`0x0042` STS_BREAKER_TRIP](/codes/status/0x0042/): A circuit breaker in the unit or rack has tripped. Find out why before resetting it: a shorted lamp or cable on that circuit, or more load than it carries.
- [`0x0043` STS_WATTS](/codes/status/0x0043/): A power, carried in the message. A reading, not a fault.
- [`0x0044` STS_DIM_FAILURE](/codes/status/0x0044/): A dimmer has failed. Look at its output stage and its fuse, or swap the module to see whether the fault follows it.
- [`0x0045` STS_DIM_PANIC](/codes/status/0x0045/): The rack or dimmer is in panic mode, running fixed levels whatever DMX says, usually turned on by a panic or emergency input. Check that input and the rack's panel before chasing DMX.
- [`0x0046` STS_LOAD_FAILURE](/codes/status/0x0046/): The unit sees no load, or a failed one, on an output: a lamp burned out, or a cable or connector open between the unit and the lamp.
- [`0x0050` STS_READY](/codes/status/0x0050/): The part the message names is ready. A reading, not a fault: it usually follows a not-ready message once that part has warmed up or calibrated.
- [`0x0051` STS_NOT_READY](/codes/status/0x0051/): The part the message names is not ready yet: warming, filling or calibrating. Wait for its ready message; if it never comes, the part is stuck there.
- [`0x0052` STS_LOW_FLUID](/codes/status/0x0052/): The part the message names is low on fluid, typically a hazer's or smoke machine's supply. Refill it; if the message stays, check the level sensor.
- [`0x0060` STS_EEPROM_ERROR](/codes/status/0x0060/): The unit's settings memory failed a check. Settings may not survive a power cycle, or may have gone back to defaults. A factory reset or a firmware reload sometimes clears it; if it returns, it is the board.
- [`0x0061` STS_RAM_ERROR](/codes/status/0x0061/): The unit's working memory failed a check. A board fault: note the firmware version and whether it comes back after a power cycle.
- [`0x0062` STS_FPGA_ERROR](/codes/status/0x0062/): A programmable chip in the unit did not load its configuration. A firmware reload may cure it; if not, it is the board.
- [`0x0070` STS_PROXY_BROADCAST_DROPPED](/codes/status/0x0070/): A proxy could not pass a broadcast, a request to every unit, on to the units behind it, and the message names the parameter. Those units may not have had it: send it again, or address them one at a time.
- [`0x0071` STS_ASC_RX_OK](/codes/status/0x0071/): The unit received DMX with an alternate start code and took it, and the message carries the code. A reading, not a fault, from units that report what arrives on their DMX input.
