Component: DMX-512 Master (Comms: System): Difference between revisions

Latest revision as of 14:37, 13 July 2026

Author	MatrixTSL
Version	2.0
Category	Comms: System

DMX-512 Master 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 Source Code

Please click here to download the component source project: FC_Comp_Source_DMX-512_Master.fcfx

Please click here to view the component source code (Beta): FC_Comp_Source_DMX-512_Master.fcfx

Detailed description

No detailed description exists yet for this component

Examples

DMX Master Example, reads the value of two ports using switch arrays to set the values and then transmits the data in a DMX packet.

DMX Master Example1

For DMX 512 slave example see: DMX Slave

Macro reference

Initialise

	Initialise
Configures the UART serial interface.
- VOID	Return

SendDataChain

	SendDataChain
Transmits the BREAK, MAB and StartCode followed by the contents of the data channels.
- BYTE	StartCode

- VOID	Return

SetDataChannel

	SetDataChannel
Sets the data byte in a data channel
- UINT	Channel

- BYTE	DataValue

- 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.
	Baud Options
Baud rate option selector
	Baud Rate

	TX
Pin to be used for Transmit data
	DMX Properties
	Data Channels
Number of data bytes used by the DMX chain, Max 512 bytes per transmission. 24 Bytes minimum to match minimum 1204us timing requirements, not all channels need to be used.
	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.

@@ Line 183: / Line 183: @@
 |-
 |-
-| width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]]
+| width="10%" align="center" class="mtx-class-propfolder" | [[File:Fc9-conn-icon.png]]
 | width="90%" class="mtx-class-propfolder" | Serial Properties
 |-
@@ Line 207: / Line 207: @@
 | colspan="2" | Pin to be used for Transmit data&nbsp;
 |-
-| width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]]
+| width="10%" align="center" class="mtx-class-propfolder" | [[File:Fc9-conn-icon.png]]
 | width="90%" class="mtx-class-propfolder" | DMX Properties
 |-
@@ Line 216: / Line 216: @@
 | colspan="2" | Number of data bytes used by the DMX chain, Max 512 bytes per transmission. 24 Bytes minimum to match minimum 1204us timing requirements, not all channels need to be used.&nbsp;
 |-
-| width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]]
+| width="10%" align="center" class="mtx-class-propfolder" | [[File:Fc9-conn-icon.png]]
 | width="90%" class="mtx-class-propfolder" | Simulation
 |-

SteveT (talk | contribs)