# SHEHDS

> What RDMBench's fixture library knows about SHEHDS fixtures: 1 profiled model, each with its source.

- **Manufacturer ID:** 0x024A
- **Parameters named:** 0
- **Models profiled:** 1
- **Registered to:** No one
- **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

What the [rdmbench-pids](https://github.com/darinpope/rdmbench-pids) fixture library holds for SHEHDS, whose ESTA manufacturer ID is `0x024A`: the models profiled from a unit on a bench, and the names of the parameters the maker added to RDM.

## Models

- [GlamoPar07A (SL7RGBWAUV)](/fixtures/shehds/glamopar-07a/): Fixture (other), firmware V1.0 13-07-2021 05:20, 2 personalities, 2 known quirks

## Manufacturer parameters

No table names SHEHDS's parameters yet. A fixture that describes its own still shows them by name in the report.

## Manufacturer ID

`0x024A` is **registered to no one**: ESTA's [manufacturer ID registry](https://tsp.esta.org/tsp/working_groups/CP/mfctrIDs.php) (© ESTA) had no entry for it when read on 2026-09-18.

For a tech, that means the ID cannot say who made the unit, and a tool that names the maker from the UID has no name to give. Nothing reserves it, so another maker's units may send it too. Go by the label the unit sends, the markings on it and where it was bought.

What units under `0x024A` called themselves on the bench, in their own replies (MANUFACTURER_LABEL, DEVICE_MODEL_DESCRIPTION and DEVICE_INFO's model ID), from RDMBench's recordings:

| Manufacturer label | Model description | Model ID |
| --- | --- | --- |
| `Canara` | `LED 2 color` | `0x0000` |

The unit calls itself `Canara`, over an ID that is nobody's, and this library files it under SHEHDS, from the order, the manual and the maker's own files (each model's source says which). The label is only what the firmware says.

Model ID `0x0000` is a placeholder: any product on the same firmware sends it, so it does not identify the model.
