# NR_DEVICE_ABSENT (0x0014)

> What NACK reason 0x0014, NR_DEVICE_ABSENT, means when a fixture sends it, and what to do about it at the bench.

- **Code:** 0x0014
- **Decimal:** 20
- **Kind:** NACK reason
- **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

`NR_DEVICE_ABSENT` is NACK reason `0x0014` (20): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the sub-device or sensor addressed is absent (NR_DEVICE_ABSENT)*.

## At the bench

The sub-device or sensor is in the unit's numbering but is not there now: a module unplugged, a sensor board missing or not detected. Worth chasing at the bench, since it can be a loose connector inside the unit.

Numbered in [E1.20](https://tsp.esta.org/tsp/documents/published_docs.php), Table A-17. Every NACK reason is listed in [NACK reasons](/codes/nack/).
