Aputure Sidus One

Network connection and lighting output are separate checks. If the unit still runs firmware V1.0, Aputure’s FAQ states that sACN is unavailable; record the version before troubleshooting that protocol.

1. Confirm TX and the listening universe. The FAQ supports universes 1–4 and excludes Art-Net Universe 0. Patched information must be present on the selected universe.
2. Sidus One latches the first protocol detected between Art-Net and sACN. If another source took priority, remove it in a controlled test before checking Art-Net again.
3. Check CRMX linking and each light’s patch. In TX, tapping CRMX sends a link command; holding for 3 seconds unlinks all receivers, so do not use a hold as a test tap.

Follow the physical path and radio role.

1. For CRMX reception to DMX output, use RX and connect the adapter’s OUT branch to the light’s DMX IN. Console input uses a different route.
2. Do not connect DMX to Sidus One USB-C. A light using a USB port for DMX needs its own specific compatible active adapter.
3. Match light address and personality to the console; terminate the DMX chain and test a known cable. RDM is documented only in RX.

Sidus BT controls compatible fixtures through Sidus Mesh. CRMX BT is a compatible app’s Bluetooth connection to Sidus One, which can output CRMX or wired DMX; these are different paths.

1. Confirm whether the app controls a Sidus BT fixture or a patched DMX/CRMX fixture. Check the selected connection type and model compatibility.
2. For Sidus BT, check Bluetooth and fixture pairing using the installed app version’s workflow. A CRMX link does not establish a mesh connection.
3. For dropouts, separate source/patch testing from radio and battery checks. Do not assume a nearby light retransmits CRMX or add another transmitter without planning links.

Each unit transmits one CRMX universe. The decision depends on patch and required signal routes, not fixture count alone.

1. List fixtures, modes, and destinations; distinguish the selected universe from the simultaneous capacity needed. Record firmware and application. We can assess a route for that universe, several designed routes, or wired distribution; unit count and compatibility require confirmation with the planned system.
2. Tell us the date, venue, approximate dimensions and positions, who supplies the lights, and who will operate. Flag cameras and the changes the show needs. A provisional inventory is enough to inquire: the proposal should define equipment, control, adapters, configuration, testing, and operation as requested, without assuming services are included.

The official FAQ describes receiving CRMX with Sidus One and distributing wired DMX to fixtures. Confirm receiver, adapter, and the actual chain.

1. Define source and destination before choosing TX or RX; check connectors, profile, and addresses, and test one fixture before expanding the branch. We can compare this mixed route with wired data distribution through approved access routes. The whole system does not need to be wireless to assess a solution.
2. Send connection photos, positions, and possible cable routes. Agree separately on power for the fixtures and control system, plus setup and rehearsal time. We can assess reinforcement of the existing system or a configuration and operation scope; receivers, cables, accessories, and availability require confirmation.

You can inquire about that need, but each route requires assessment: Sidus BT and CRMX are distinct systems. A fixture appearing in an app does not establish that it responds to the same scene or source as the others.

1. Send exact models, application and version, known firmware, and which fixtures must change together. We can assess a verified compatible workflow, separate functions between groups, or compare a DMX/CRMX route with appropriate receivers or adapters. Joint control or simultaneous changes are not promised without checking the actual system.
2. Describe entrances, pauses, and endings, which light must remain steady, and who calls cues. Ask to distinguish equipment rental, patch setup, programming, rehearsal, and operation. During testing, agree on what to do if the app connection or radio link is lost; the recovery scene and procedure require confirmation for each fixture.