# NR_INVALID_ENDPOINT_MODE (0x000D)

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

- **Code:** 0x000D
- **Decimal:** 13
- **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_INVALID_ENDPOINT_MODE` is NACK reason `0x000D` (13): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the endpoint is in a mode that does not allow this (NR_INVALID_ENDPOINT_MODE)*.

## At the bench

A gateway term: the port is in a mode that does not allow the request, such as an input where the request needs an output. Change the port's direction or mode on the gateway 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/).
