# NR_HARDWARE_FAULT (0x0002)

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

- **Code:** 0x0002
- **Decimal:** 2
- **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_HARDWARE_FAULT` is NACK reason `0x0002` (2): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *an internal hardware fault stopped the device complying (NR_HARDWARE_FAULT)*.

## At the bench

The unit understood the request, but something inside it kept it from acting. The one refusal about the fixture's hardware rather than the conversation: read its status messages and sensors, and try the same change from its own panel to see whether that fails too.

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/).
