# NR_ACTION_NOT_SUPPORTED (0x000B)

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

- **Code:** 0x000B
- **Decimal:** 11
- **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_ACTION_NOT_SUPPORTED` is NACK reason `0x000B` (11): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the device does not support that action (NR_ACTION_NOT_SUPPORTED)*.

## At the bench

The value was acceptable, but the unit cannot make the change as it is set up now. Look for another setting that has to change first, such as a mode the requested one depends on.

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