# NR_PROXY_DROP (0x0019)

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

- **Code:** 0x0019
- **Decimal:** 25
- **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_PROXY_DROP` is NACK reason `0x0019` (25): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the proxy lost the device's reply (NR_PROXY_DROP)*.

## At the bench

A proxy passed the request on and lost the unit's reply. The unit may have acted on it: read the setting back directly before assuming either way.

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