Model and documentation reference
Exact model: LumenRadio Stardust, SKU 800-2281. The reference is the 31-page English manual dated April 9, 2026, for firmware 1.5.0 or later. Record installed version and each receiver model separately. Luna, Aurora or MoonLite connectors and functions are not transferred to Stardust.
LumenRadio · Stardust · SKU 800-2281
Event application
For a zoned lighting proposal, define which areas share content and which need independent control. Two physically separated groups do not automatically need another universe, but their addresses and personalities must match the agreed patch. Keep a row for each critical route and assign an owner to compare console, received data and fixture response. Catalog capacity establishes no coverage or continuity promise.
Capacity depends on mode and receiver
| Element | Documented limit | Event information |
|---|---|---|
| CRMX² | Up to 8 universes with compatible receivers | Confirmed receiver model and firmware |
| CRMX Classic | 4 universes | Available outputs and zone patch |
| W-DMX G3 / G4S | 4 universes in each mode | Exact receiver compatibility and selected mode |
| 4-universe mode | Every second output is disabled | Distinguish disabled output from missing network data |
| Art-Net / sACN | Network data input, distinct from radio mode | Source, actual universe, output and receiver |
Stardust User Manual · 2026-04-09 · firmware 1.5.0+ · selected pages
Compare actual universe and output states
Record protocol and destination emitted by the console rather than its visible number alone. Art-Net uses Net/SubNet/Universe; sACN is set by universe. A label starting at one does not authorize automatic conversion to zero. The manual menu distinguishes unconfigured output, configured output without Ethernet data and output receiving Ethernet data. These states guide the next check: interface access or a linked receiver does not establish arrival of the correct universe.
Stardust User Manual · 2026-04-09 · firmware 1.5.0+ · selected pages
When intensity stays up or another source appears
The manual tracks up to four sources per output and combines equal-priority sources by HTP, retaining the highest value on each channel. Art-Net source identity uses IP and no priority; sACN uses CID. Before changing the patch, the proposed test should therefore compare one intended source and then the additional sources the design actually requires. Do not add another console or application as a backup without documenting its effect on those channels.
Stardust User Manual · 2026-04-09 · firmware 1.5.0+ · selected pages
Proposed map and test for each zone
- Record Stardust, firmware, receivers and compatibility before selecting capacity. Preserve original configuration and patch; no update is performed here.
- Prepare rows with source/IP or CID, protocol, network destination, enabled output, radio mode, receiver, address and personality. Keep linking keys outside the shared worksheet.
- Agree on a recognizable intensity sample and another required attribute, with a defined fixture and owners off-program. Compare input data, link and response separately.
- For a multi-source design, compare priorities and HTP with an agreed return plan. The manual requires receiver relinking after changing transmission protocol; do not use that as an improvised live-show test.
- Define a wired alternative and changeover decision owners. Document power throughout the chain and pending or measured results; this candidate operates no link, console, network or firmware.
Stardust User Manual · 2026-04-09 · firmware 1.5.0+ · selected pages
Frequently asked questions
Do eight universes work with every CRMX receiver?
CRMX² capacity requires compatible receiver support. Classic and the listed W-DMX modes have different capacity; actual identity and version must precede the map.
Does a visible interface establish DMX arrival?
It establishes control access only. Check output data state and emitted universe before attributing a missing response to radio or fixture addressing.
Does zero on one console always turn a light off?
Another equal-priority source can hold a higher value under HTP. Preserve source-arrival evidence and plan an off-program comparison without assuming every attribute should mix alike.
Is a cloned Linking Key an automatic backup?
No. The manual warns of undefined behavior if cloned transmitters are not separated. Cloned credentials establish no rehearsed changeover or recovery.
Does the battery ensure continuity of the entire installation?
Transmitter backup does not power fixtures, external receivers or switches. No runtime is promised; unit conditions and documentation must be confirmed before electrical design.
Follow the lighting control path
Official edition-specific documentation
Stardust manual 2026-04-09: p. 8 version; pp. 10–12 modes, compatibility and clones; p. 13 connections, visually inspected; pp. 17–18 states; pp. 20–23 protocol, mapping and merging; pp. 26 and 30 conditions and specifications. Existing original SHA verified without copying. Conflicting electrical and runtime values between references are not recommended here. Consultation and a proposed test are distinct from performed operation.
