DMX Channel S changes. DMXcas publishes the new value to Gateway Channel 1.
DMX-512 → CASAMBI · EIGHT-CHANNEL GATEWAY
DMXcas
Let the house console command the Casambi network.
DMXcas receives one fixed block of eight adjacent DMX channels and publishes them as eight Casambi Gateway channels. Map those channels to fixtures, groups, scenes or project logic—without giving up app and local control.
MADE IN USADesigned, built and supported in Mesa, Arizona
DMX CONTROLLER → DMXcas → CASAMBI GATEWAY
DMX INCASAMBI
Eight DMX values enter. Eight Gateway channels reach the Casambi network.
8 channelsfixed adjacent DMX input block
1–505valid start-address range
9 parametersstart address + eight transmit delays
THE BRIDGE GOES THIS DIRECTION
DMX in.
Casambi out.
DMXcas is the other side of casDMX. It listens to a conventional DMX controller and publishes changed levels into Casambi; it does not generate a DMX universe.
DMX consoleArchitectural controller, show console or building control
source
→
DMXcasEight-channel receiver + Casambi Gateway
→
Casambi networkMapped fixtures, groups, scenes and control logic
INTERACTIVE EIGHT-CHANNEL MAP
Set S once.
Receive S through S+7.
The channel count is always eight and the addresses are always consecutive. DMXcas cannot skip a slot or pick eight unrelated addresses.
Choose the first address
Valid range is 1–505 so the complete eight-channel block stays inside one 512-channel universe.
ONLY CHANGES ARE PUBLISHED
Moving a DMX value creates a new Gateway update. An unchanged DMX level does not continuously overwrite a newer app or switch action.
Moving a DMX value creates a new Gateway update. An unchanged DMX level does not continuously overwrite a newer app or switch action.
DMX INPUT BLOCK201–208
CASAMBI PAYLOADGateway 1–8
INTERACTIVE TRANSMIT-DELAY STAGGER
Spread eight updates across a busy network.
Leave delays at zero when the network is reliable. When a simultaneous eight-channel move overloads a large network, increase the step gradually and prove it under real traffic.
Build a stagger
Each channel waits until its DMX value remains unchanged for its delay interval.
DO NOT GUESS
Delay is intentional latency. Large settings make rapid moves and fades feel slow because each new DMX change restarts that channel’s timer.
Delay is intentional latency. Large settings make rapid moves and fades feel slow because each new DMX change restarts that channel’s timer.
EXAMPLE RELEASE WINDOW0–700 ms
CHANNELS8 independent
ONE FIXED PROFILE · NINE VENDOR PARAMETERS
One address chooses the block. Eight delays tune traffic.
Every Gateway channel has its own stabilization delay, from immediate publishing through 2500 ms.
IDPARAMETERRANGEFIELD EFFECT
0DMX Start Address1–505Selects the first address of the fixed S…S+7 block.
1Channel 1 Transmit Delay0–2500 msStabilization interval before Gateway Channel 1
publishes.
2–8Channels 2–8 Transmit Delay0–2500 ms eachIndependent matching intervals for the remaining seven
channels.
ONE NON-ISOLATED DMX INPUT
Receive the bus. Preserve the bus.
Power from 12–24 VDC Class 2. Carry DMX+, DMX− and common continuously; terminate DMXcas only when it is the actual final receiver.
X2-1 · X2-2 · X2-3
DMX+ input, DMX− input and required common/ground.
X2-4 · X2-5
Not used. Leave both terminals unconnected; DMXcas has no Digital I/O feature.
No internal termination: if DMXcas is last and the bus is unstable, fit 120 Ω across DMX+ and DMX−. If the bus continues, terminate the actual far end instead.
MAP · STAGGER · PROVE
Commission the complete signal path.
Record the eight-address block, Gateway mapping, all eight delays, termination status and loss-of-DMX behavior.
PDFInstallation manualRatings, terminals and field wiring.PDFCommissioning guideMapping, delays, shared control and tests.
Need to bring a console into Casambi?
Bring us the DMX schedule and the intended Gateway targets.
Bring us the problem ↗