Valid operational range 1-511. Address S is the selector; address S+1 is intensity.
DMX-512 → CASAMBI SCENES · TWO-CHANNEL GATEWAY
SceneDMXcas
Give the show console direct access to the Casambi scene stack.
SceneDMXcas receives two consecutive DMX addresses. The first selects one of twenty mapped Casambi scenes; the second scales that scene from zero to its stored maximum—without consuming twenty DMX channels.
MADE IN USADesigned, built and supported in Mesa, Arizona
DMX CONSOLE → SceneDMXcas → CASAMBI SCENE
DMX S + S+1SCENE + SCALE
One fixed adjacent address pair controls as many as twenty prebuilt scenes.
2 addressesalways adjacent: S and S+1
20 scenesassignable mapping slots
21 parametersstart address + scene assignments
ONE FIXED PROFILE
DMX S selects.
DMX S+1 scales.
Create the scenes in Casambi first. Then map selector values 1-20 to those scenes and place the two-channel footprint anywhere from DMX address 1 through 511.
DMX controllerScene number + 8-bit intensity
→
SceneDMXcasAdjacent pair + scene lookup + level scalar
→
Casambi networkMapped scene at its scaled stored maximum
INTERACTIVE TWO-CHANNEL GATEWAY
Place the block. Select a scene. Set its level.
Only the first two addresses are used, and they must remain adjacent. Selector 0 intentionally sends no new scene command; values above 20 are unsupported.
Drive the Gateway
SCALING DOES NOT EDIT THE SCENE
The second DMX value scales the stored scene for this command. It does not overwrite the scene's colors, groups or saved levels.
The second DMX value scales the stored scene for this command. It does not overwrite the scene's colors, groups or saved levels.
Scene Slot 7 → Scene 7
DMX FOOTPRINT101 + 102
RESULTING MAXIMUM60%
TWENTY-ONE VENDOR PARAMETERS
One address parameter. Twenty explicit scene bindings.
There is no hidden arithmetic in the Casambi mapping: selector value 1 recalls Scene Slot 1, value 2 recalls Slot 2, and so on through value 20.
Each parameter binds its matching selector value to one pre-made Casambi scene.
Use zero intentionally when the console should stop issuing scene recalls.
Keep the selector within 0-20. Higher values are outside the mapping table.
255 preserves the scene's stored maximum; 128 requests approximately half of each stored level.
Keep the device powered after Vendor Parameter changes so deferred storage can complete.
CHANGE-DRIVEN SHARED CONTROL
The console participates without continuously fighting the room.
A scene command is sent when either DMX value changes. Unchanged DMX is not continually retransmitted, so a later app, switch or automation command can remain effective until the console moves again.
SceneDMXcas sends the current mapped scene and scalar as a zero-duration command.
An app, switch or automation can take control because the unchanged DMX pair is not hammered into the network.
No forced blackout is sent. Confirm that behavior against the project's approved sequence of operations.
ONE NON-ISOLATED DMX INPUT
Receive the bus and preserve its topology.
Use DMX-rated twisted pair, carry common continuously, and terminate only the true far end.
POWER + / POWER -
12-24 VDC Class 2 supply, polarity sensitive. Do not connect a constant-current LED output.
X2-1 / X2-2 / X2-3
DMX+, DMX- and required common/ground. The three-wire input is non-isolated.
X2-4 / X2-5
Not used. Leave both positions unconnected.
No internal termination: if SceneDMXcas is the final receiver and the bus is unstable, install 120 ohms across DMX+ and DMX-. Use an optically isolated splitter for branches—never a passive T or star.
CREATE · MAP · PROVE
Commission the scene stack from end to end.
Record the address pair, all used Scene Slots, termination status, intensity tests and approved DMX-loss behavior.
PDFInstallation manualRatings, terminals and field wiring.PDFCommissioning guideMapping, addressing and acceptance tests.
Need to map a show-control scene stack?
Bring us the console patch and the Casambi scene schedule.
Bring us the problem ↗