This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
controllers:dmx:primer [2022/01/24 23:53] – [Testing Tools] made easier to read jazzy | controllers:dmx:primer [2022/01/28 19:35] (current) – jazzy | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== DMX Control Primer ====== | ====== DMX Control Primer ====== | ||
This article is to introduce you to how DMX works and some tips to troubleshoot it. If you are looking for resources on how the serial protocol is written so that you can create your own DMX code library, there are some details at the end. | This article is to introduce you to how DMX works and some tips to troubleshoot it. If you are looking for resources on how the serial protocol is written so that you can create your own DMX code library, there are some details at the end. | ||
+ | |||
+ | For info on how to set up DMX lights in Horizons, check out the [[controllers: | ||
==== DMX Basics ==== | ==== DMX Basics ==== | ||
Line 46: | Line 48: | ||
**RDM** is Remote Device Management. Horizons doesn' | **RDM** is Remote Device Management. Horizons doesn' | ||
+ | |||
+ | **DMX Loss Behavior** is what a fixture does when it stops receiving DMX packets. Some fixtures will **Hold Last Look** based on the last packet, waiting for a new packet to arrive. Others will **Wait and Fade** at the last packet look for a specific time, before fading the lights out. Other fixtures will just turn off when DMX packets stop flowing. *Check your ConstandDelivery setting in Horizons based on how your fixture handles packet speed/ | ||
==== Using Multiple Fixtures ==== | ==== Using Multiple Fixtures ==== |