# NR_WRITE_PROTECT (0x0004)

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

- **Code:** 0x0004
- **Decimal:** 4
- **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_WRITE_PROTECT` is NACK reason `0x0004` (4): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the setting is normally writable but is blocked at the moment (NR_WRITE_PROTECT)*.

## At the bench

The setting can normally be changed, but not right now. At the bench this is usually a lock you can see: a panel or menu lock, a password, or a setting held by the current mode or by a standalone program the unit is running. Unlock it on the fixture and try again.

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