# NR_INVALID_STATIC_CONFIG_TYPE (0x0010)

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

- **Code:** 0x0010
- **Decimal:** 16
- **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_STATIC_CONFIG_TYPE` is NACK reason `0x0010` (16): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the static configuration type is invalid (NR_INVALID_STATIC_CONFIG_TYPE)*.

## At the bench

An RDMnet term: the device does not take the configuration type in the request. 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/).
