showstack / hardware / etc-response-mk2-gateway
ETC Response Mk2 DMX/RDM Gateway
One, two, four or eight port DMX/RDM gateway for Net3 systems, configured from the console or from Concert. The standard way an Eos rig reaches copper DMX in an installed venue.
Protocols it speaks
| Protocol | Direction | Notes |
|---|---|---|
| sacn | bidirectional | sACN in, DMX out, and DMX in to sACN. |
| art-net | bidirectional | Art-Net supported alongside sACN. |
| etcnet3 | bidirectional | Net3 device discovery and configuration. |
| dmx512 | bidirectional | DMX out and in on the physical ports. |
| rdm | bidirectional | RDM proxy for discovery and configuration from the console. |
Connectors
- 1-8x XLR5F DMX/RDM
- 1x etherCON or RJ45
- PoE on supported models
What to watch for
A gateway set to output and a console outputting the same universe over a second protocol is the classic double-drive fault. Decide sACN or Art-Net per universe and stick to it.
RDM through a gateway only works if every device in that DMX chain passes RDM. One non-RDM splitter in the line makes everything past it invisible.
Gateways hold configuration locally. A swapped spare comes up in its previous show's configuration unless it was reset, which is worse than a factory default because it looks configured.
Sources
- ETC — ETC primary
Understand the mechanism
Something wrong, or missing?
Known gaps on this entry: released. If you can source one of them, that is a ten minute pull request.
Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.
Work at ETC? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.