# NR_PROXY_BUFFER_FULL (0x000A)

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

- **Code:** 0x000A
- **Decimal:** 10
- **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_BUFFER_FULL` is NACK reason `0x000A` (10): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the proxy's buffer is full and cannot hold more queued or status messages (NR_PROXY_BUFFER_FULL)*.

## At the bench

A proxy between the controller and the units has no room left for the replies and status messages it holds for them. The units behind it may be fine: ask more slowly, or take the unit off the proxy.

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