# NR_UNKNOWN_SCOPE (0x000F)

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

- **Code:** 0x000F
- **Decimal:** 15
- **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_UNKNOWN_SCOPE` is NACK reason `0x000F` (15): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the component is not part of that RDMnet scope (NR_UNKNOWN_SCOPE)*.

## At the bench

An RDMnet term: the device is not in the scope the request named. It matters only on an RDMnet network, never on a DMX cable.

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