# NR_INVALID_PORT (0x0013)

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

- **Code:** 0x0013
- **Decimal:** 19
- **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_PORT` is NACK reason `0x0013` (19): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the port number is invalid (NR_INVALID_PORT)*.

## At the bench

Network setup: the device would not take the port number in the request. Port 0, and ports the device keeps for itself, are the usual cause.

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