# NR_ENDPOINT_NUMBER_INVALID (0x000C)

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

- **Code:** 0x000C
- **Decimal:** 12
- **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_ENDPOINT_NUMBER_INVALID` is NACK reason `0x000C` (12): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *no such endpoint (NR_ENDPOINT_NUMBER_INVALID)*.

## At the bench

A gateway term: the request named an endpoint, one of a gateway's ports or universes, that it does not have. A fixture on a DMX cable sends this only through a gateway; check the port number asked for.

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