Difference between revisions of "Component: DMX 512 Slave (Comms: System)"
From Flowcode Help
Jump to navigationJump to search| (4 intermediate revisions by 2 users not shown) | |||
| Line 14: | Line 14: | ||
==DMX-512 Slave component== | ==DMX-512 Slave component== | ||
A serial based communications protocol designed for controlling theatrical equipment such as dimmers, fog machines and intelligent lights. DMX-512 Slave devices are daisy chained together with a final 180R terminating resistor at the end of the chail. DMX requires the signal to be level shifted from VCC and GND to +2.5V and -2.5V. | A serial based communications protocol designed for controlling theatrical equipment such as dimmers, fog machines and intelligent lights. DMX-512 Slave devices are daisy chained together with a final 180R terminating resistor at the end of the chail. DMX requires the signal to be level shifted from VCC and GND to +2.5V and -2.5V. | ||
| + | |||
| + | ==Component Pack== | ||
| + | |||
| + | COMMSC | ||
==Detailed description== | ==Detailed description== | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| Line 30: | Line 40: | ||
| − | + | ||
| − | + | ||
| + | |||
| + | |||
| + | |||
| + | |||
DMX Slave Example, captures the first DMX data channel sent from the Master and outputs the value onto a Port using the LED array component. | DMX Slave Example, captures the first DMX data channel sent from the Master and outputs the value onto a Port using the LED array component. | ||
{{Fcfile|DMX_Slave_Example1.fcfx|DMX Slave Example1}} | {{Fcfile|DMX_Slave_Example1.fcfx|DMX Slave Example1}} | ||
| + | |||
| + | |||
| + | For DMX 512 Master example see [[Component: DMX 512 Master (Comms: System)]] | ||
==Downloadable macro reference== | ==Downloadable macro reference== | ||
| Line 94: | Line 111: | ||
| width="10%" align="center" style="background-color:#D8C9D8;" | [[File:Fc9-prop-icon.png]] | | width="10%" align="center" style="background-color:#D8C9D8;" | [[File:Fc9-prop-icon.png]] | ||
| width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''Properties''' | | width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''Properties''' | ||
| + | |- | ||
| + | |- | ||
| + | | width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]] | ||
| + | | width="90%" style="background-color:#EAE1EA; color:#4B008D;" | Serial Properties | ||
|- | |- | ||
|- | |- | ||
| Line 115: | Line 136: | ||
|- | |- | ||
| colspan="2" | | | colspan="2" | | ||
| + | |- | ||
| + | | width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]] | ||
| + | | width="90%" style="background-color:#EAE1EA; color:#4B008D;" | DMX Properties | ||
| + | |- | ||
|- | |- | ||
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]] | | width="10%" align="center" | [[File:Fc9-type-21-icon.png]] | ||
| Line 136: | Line 161: | ||
| colspan="2" | Start code value to listen out for, range 0-255 | | colspan="2" | Start code value to listen out for, range 0-255 | ||
|- | |- | ||
| − | | width="10%" align="center" style="background-color:# | + | | width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]] |
| − | | width="90%" style="background-color:# | + | | width="90%" style="background-color:#EAE1EA; color:#4B008D;" | Simulation |
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|- | |- | ||
Latest revision as of 17:19, 9 November 2022
| Author | MatrixTSL |
| Version | 2.0 |
| Category | Comms: System |
Contents
DMX-512 Slave component
A serial based communications protocol designed for controlling theatrical equipment such as dimmers, fog machines and intelligent lights. DMX-512 Slave devices are daisy chained together with a final 180R terminating resistor at the end of the chail. DMX requires the signal to be level shifted from VCC and GND to +2.5V and -2.5V.
Component Pack
COMMSC
Detailed description
No detailed description exists yet for this component
Examples
DMX Slave Example, captures the first DMX data channel sent from the Master and outputs the value onto a Port using the LED array component.
DMX Slave Example1
For DMX 512 Master example see Component: DMX 512 Master (Comms: System)
Downloadable macro reference
|
GetDataChannel |
| Gets the data byte from a data channel | |
 - UINT
|
Channel |
 - BYTE
|
Return |
|
|
ReceiveDataChain |
| Waits for a BREAK, MAB and StartCode followed by the contents of the data channels. Returns 0 to indicate a timeout and 1 to indicate succesful reception. | |
| - BYTE
|
Timeout |
| 0 = Don't wait, 1 - 254 = 1ms - 254ms, 255 = Wait forever | |
| - BYTE
|
Return |
|
|
Initialise |
| Configures the UART serial interface. | |
 - VOID
|
Return |
Property reference
|
Properties |
|
Serial Properties |
|
Channel |
| UART Channel selector Software channels are bit banged using generic I/O pins but are not as reliable as hardware channels. Hardware channels use the selected peripheral on-board the target microcontroller. | |
|
RX |
| Pin to be used for Receive data | |
|
|
Baud Options |
| Baud rate option selector | |
|
Baud Rate |
|
|
DMX Properties |
|
Data Channels |
| Number of data bytes to receive from the master, Max 512 bytes per transmission. 24 Bytes minimum from Master to match minimum 1204us timing requirements, not all channels need to be used. | |
|
|
Start Channel |
| Channel from the master which we want to start taking our data channels | |
|
Use Start Code |
| Do we wait for the start code or simply begin receiving data? | |
|
|
Start Code |
| Start code value to listen out for, range 0-255 | |
|
|
Simulation |
|
|
Scope Traces |
| Selects if the scope traces are automatically added to the data recorder window or not. Simulation - draws an approximation of the UART data onto the scope trace. ICT - sets up the scope trace for incoming data and adds UART packet decoding at the correct BAUD. | |
|
|
Console Data |
| Selects if the console data is automatically generated or not | |
|
|
Console Columns |
| Number of characters that can be displayed on a single line of the console. | |
|
|
Data Source |
| Simulation data source used to allow the component to connect to various remote devices Nothing - Simulation data is ignored COM port - Routes the communication data to and from a physical or virtual COM port Injector - Routes the communication data via a data injector component on the Panel. | |
