Model and documentation reference
Reference: Aputure Sidus One APR0316A31 with Sidus One 2-Way Splitter Cable APR0316A34, three-pin push-pull to five-pin DMX XLR. The chosen path is CRMX into Sidus One RX and wired DMX out to a compatible fixture. The originating transmitter is a separate component to identify. A single unit is not both TX/RX ends simultaneously and does not equal Sidus Four.
Sidus One · one-sheet · PDF 1–2
Event application
For an Argentine presentation, theater or recording, prepare a zone row with console, universe, transmitter, receiver and fixture input. Mark intended positions, obstacles, people paths and final cable run. If the entire route cannot be cabled, document which segment needs radio and which remains wired. Include an agreed recovery alternative and rehearsal window; proximity alone establishes no stable link.
Sidus One · one-sheet · PDF 1–2 · Sidus One · EN v1.0 · PDF 11/12/29 visual · RDM hardware note · Aputure Sidus One · FAQ · universe and FW conditions
Separate roles and conditions
| Path element | Documented reference | Required confirmation |
|---|---|---|
| CRMX transmitter · TX | One transmitted CRMX universe per unit | Source hardware/data/universe; Wi-Fi 1–4 selector does not create four outputs |
| Sidus One receiver · RX | Receives CRMX and outputs DMX through adapter | Intended unit, output branch and fixture DMX input |
| Wi-Fi input · another route | Art-Net/sACN by version; universe selection 1–4 | Firmware, source and console numbering; do not assume Universe 0 support |
| RDM · hardware scope | Manual p. 29 separates RDM/non-RDM versions | Identify actual variant before assigning TX/RX RDM functionality |
Sidus One · one-sheet · PDF 1–2 · Sidus One · EN v1.0 · PDF 11/12/29 visual · RDM hardware note · Aputure Sidus One · FAQ · universe and FW conditions
Describe inputs and outputs before touching controls
For the selected path, record compatible CRMX transmitter, intended Sidus One RX and APR0316A34 adapter output to fixture DMX IN. Document fixture address/personality from its own manual; transporting a universe does not replace that identification. Sidus One USB-C handles charging/maintenance, not DMX. The manual separates Wi-Fi, CRMX and Sidus BT antenna ports: Bluetooth/Sidus Mesh is another function and proves no CRMX reception.
Sidus One · one-sheet · PDF 1–2 · Sidus One · EN v1.0 · PDF 11/12/29 visual · RDM hardware note · Aputure Sidus One · FAQ · universe and FW conditions
Preserve version, variant and state before rehearsal
The consulted EN v1.0 manual distinguishes hardware called non-RDM, with RDM in RX only, from the RDM version with TX/RX functionality. The sheet/web table omit that distinction and cannot be generalized. FAQ also says firmware V1.0 lacks sACN. No document label establishes actual hardware/firmware. Sources list 18 versus 19 hours battery life: record charge/planned rehearsal duration without promising runtime or radio coverage.
Sidus One · EN v1.0 · PDF 11/12/29 visual · RDM hardware note · Aputure Sidus One · FAQ · universe and FW conditions · Sidus One · web specifications · RDM/runtime differences retained
Prepare segment-by-segment verification
- Identify transmitter and Sidus One receiver separately. Record model, RDM/non-RDM variant, known version, APR0316A34 adapter and destination fixture; leave unsupported data pending.
- Draw data source, universe, TX, CRMX segment, RX and fixture DMX IN. Record address/personality and other final-run devices without applying a patch or changing radio roles here.
- Prepare antenna-function and power fields: documented Sidus One charging is USB-C 5 V/2 A. Transfer no STORM 80c USB-C requirement to this device.
- Define later rehearsal observations: source data, radio link, reception and fixture response. Wi-Fi connection and radio link differ from evidence of a correct scene.
- Agree on owner, window and wired recovery. Press no Link/Unlink/Reset, pair nothing and perform no network/update change to fill gaps; preserve initial state and actual observations.
Sidus One · one-sheet · PDF 1–2 · Sidus One · EN v1.0 · PDF 11/12/29 visual · RDM hardware note · Aputure Sidus One · FAQ · universe and FW conditions
Frequently asked questions
Does Wi-Fi selection 1–4 provide four simultaneous CRMX universes?
No. FAQ limits each unit to one transmitted CRMX universe. Selection identifies the source universe; simultaneous needs require planned units/paths.
Can Sidus One receive for a fixture without CRMX?
This is documented: CRMX into RX and adapter DMX output to a compatible input. Confirm transmitter, adapter, address and personality; actual setup is unverified here.
Is RDM RX-only on every Sidus One?
Do not generalize. Manual p. 29 distinguishes non-RDM hardware with RX-only RDM and RDM hardware with TX/RX functionality. Actual variant remains unidentified.
Does document v1.0 establish installed sACN support?
No. Document revision is not installed firmware; FAQ identifies no sACN in firmware V1.0. Confirm actual version and permitted path without updating from this guide.
Are 18/19 hours and published range guaranteed?
No. Sources disagree on runtime and qualify range by environment. Plan power, positions and an actual rehearsal window rather than treating catalog figures as event results.
Follow the lighting control path
Official edition-specific documentation
Two existing SHA-verified originals: two-page sheet fully read, PDF 2 inspected; 30-page EN v1.0 manual with only PDF 1/2/8–15/29 read and 11/12/29 inspected. Page 29 RDM note visually verified. Official FAQ, specification and controls text consulted; version/RDM/runtime differences preserved. The full manual was not read, no PDF copied/downloaded and local reader/radio/equipment remain untested.
