# NR_UNKNOWN_PID (0x0000)

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

- **Code:** 0x0000
- **Decimal:** 0
- **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_UNKNOWN_PID` is NACK reason `0x0000` (0): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the device does not implement this parameter (NR_UNKNOWN_PID)*.

## At the bench

The unit does not have this parameter. The most common refusal and usually harmless: a unit lists what it supports, and anything else should get this answer. It is a fault only for a parameter every responder must answer, and some units say nothing at all instead, which reads as a timeout rather than a refusal.

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