# NR_FORMAT_ERROR (0x0001)

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

- **Code:** 0x0001
- **Decimal:** 1
- **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_FORMAT_ERROR` is NACK reason `0x0001` (1): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the device could not make sense of the request data (NR_FORMAT_ERROR)*.

## At the bench

The unit heard the request but its data was the wrong length or shape for this parameter. From a well-tested controller it points at the unit's firmware reading the parameter another way, often an older revision of the standard; from a hand-built request, check the data length first.

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