What to confirm before choosing a communication entry
The site trigger and host system determine the communication method; ports, payloads, and command parameters follow the selected interface.
- EntriesFive names, one system
- DMX512Console master, MSP slave
- UDPNetwork trigger
- ConfigurationBy interface
Five entries, one system
| Communication | Typical use | Configuration information |
|---|---|---|
| Buttons and inputs | Local input starts a sequence | Terminals and input conditions |
| UDP | A host on the local network starts a sequence | Port and payload |
| DMX512 | A lighting console calls a sequence | Channel and address setup |
| Command interface | A business system sends control commands | Command sheet |
| API | Software integration and custom development | Library and calling guide |
These communication methods connect to the same XMatrix and MSP system. A project can use one method or combine several according to the site control system.
DMX512 operation
In the standard DMX512 setup, the lighting console is the master and the MSP unit receives channel data as a slave. Channels and addresses follow the project sequence.
Two facts to send with the inquiry
- Whether the trigger comes from a button, an input, UDP, DMX512, the command interface, or the API.
- Whether the machine must keep executing after the computer disconnects.
Interface configuration
Application: the trigger entry is already known.
Configuration: ports, payloads, the command sheet, and the API notes follow the project check.
Related information
Related pages: Command interface, UDP, DMX512, API
State the communication method, trigger data, and whether the computer remains connected when requesting configuration details. Contact