Contact HMS Store Manager

Goto HMS-Brightsign Home Page

Contact HMS Technical Support

Roku Brightsign Serial Interface

For Brightsign Compact HD410, 810 & 1010

8 Input, 8 Output with DMX Controller

-or-

16 Input, 16 Output with DMX Controller

    

 

Roku-C-8-DMX (Interface board) w/DMX512 Controller (XLR Connector for DMX)

Roku-C-16-DMX-1 Boards have terminal block for DMX connections

Roku-C-16-DMX-2 Boards have XLR connector for DMX connections

Features: (Rev 3.0 Firmware)

Note: If you have a Roku_C_8_DMX then output port2 data (outputs 8-15) and inputs 8-15 are of not utilized.  However, the data byte for output port2 is still required to be sent from the BrightSign.
Note: Rev 2 boards:  Roku-C-8-DMX and Roku-C-16-DMX use the same boards as 'C-8-DMX or C-16-DMX', but the firmware is different.  'C-8-DMX' and 'C-16-DMX' use the HMS Protocol.  The 'Roku' versions have a label to identify them.
Note: Rev1 boards need to be connected to the BrightSign with BrightSign on.  The 3.3 volts from the BrightSign is required for proper operation!

Description of Operation:

This board is used to interface to a BrightSign 'Compact'.  The fist 8 inputs (inputs 0-7) pass directly to the BrightSign GPIO connections (Btn0-Btn7).  The BrightSign uses the 5V TTL serial port to input 8 bits of data (inputs 8-15 if 'C-16 board').  The BrightSign controls the 16 Outputs via the 5V TTL Serial Port.  The same 5V TTL serial port is used to control the DMX output.

Rev 3 Firmware:  BrightAuthor is expecting strings to represent the serial 'inputs'.  The new format is to send the ascii value for the 'input number'' followed by a carriage return (<CR>). Inputs 8-15 are transmitted to the Brightsign whenever the inputs are detected low.  Only the first input 'low' is reported as an I/O event (similar to the GPIO events).  So, if input 8 and input 9 are both low only input 8 (Serial Event '0') will be sent.  This is '0',<CR> (two bytes).  If input10 goes low  after input 11 goes low, only input 10 will be reported as an event.

Rev 3 Firmware Option5 = On (send binary data byte)

Serial Transmission Protocol:  The BrightSign has to allow 10 milliseconds to elapse between serial data 'bursts' out.  This 10 millisecond 'rest' time is interpreted by the HMS board as a 'break' in serial transmission.  This 'break' condition synchronizes the HMS board to the serial transmissions from the BrightSign.  For 16 input boards, only a single byte has to be sent by the BrightSign followed by a 10 millisecond 'inactive serial port or break) time to request the inputs 8-16 data byte.  I.E. The typical scenario for request of inputs 8-15 is TTLSend(port1value) followed by sleep(10). The BrightSign will have the event TTL Serial Port after this sequence.

Outputs 0-7 and 8-15:  The first two bytes going out the BrightSign 5V TTL serial port are the data bytes for Port1 and Port2 of the HMS board.  Port1 is Outputs 0-7 and Port2 is Outputs 8-15.  If TTLSend(1;128) is sent, then bit 1 of port 1 will turn on (Output0) and bit 7 of Port 2 will turn on (Output15).  All other outputs will turn off because their respective bits are low.

DMX512 Operation:  The DMX first 100 channels are sent every second or whenever the DMX 'Channel' bytes change (instant DMX output).  The DMX512 protocol is so fast that the entire 100 channels of DMX data can be sent out during transmissions of 4 bytes of data from the BrightSign.  All bytes following the Port2 byte go the the DMX channels 1-100.  If only a single byte follows the Port2 byte, then only channel 1 of the DMX512 protocol will every receive data or 'changed' data.  All other channels not receiving data are unchanged..  I.E.  The protocol to send DMX Data is: TTLSend(port1,port2,DMX_CH1,DMX_CH2,DMX_CH3,......,DMX_CH100.  Note: Channel and Address are the same thing!

DMX 'Head' Operation.  If a DMX dimmer pack is utilized, setup the dimmer pack to utilize channels 1-4.  Then set the DMX 'Head' start channel to 5 (or whatever channel is allowed).  If the DMX 'Head' is the only DMX device, then set the 'Head' channel to channel 1.  If the DMX 'Head' protocol expects to receive 20 bytes (20 channels) then all 20 of those bytes need to be sent with each DMX 'Head' command sequence.  Likewise, when using the BrightSign to control the DMX Head, the BrightSign should send all 20 DMX bytes with each TTLSend() command.  I.E. TTL_Send(port1;port2;dimmer channels 1-4 [4 bytes]; DMX 'Head' bytes [20 bytes]).  If the DMX512 'Head' can only be set for 'even addresses' or multiples of a number (I.E. 20,40,60) then the bytes for that address (channel) will have to start at the address or channel set as the base channel.

DMX 'Play Scenes'.  A 'scene' file can be created and stored on the SD card.  BrightScript would be used to interpret the 'scene file'.  Any number of scenes could be stored on the SD card.  Contact Roku if you need help with this programming.

DMX_Demo.AVI (84 mega byte movie demo)                     DMX_Demo.mov 6MB (requires Quicktime)    Link: Setting up the Serial Port and Sending Bytes with 'BrightAuthor'.

 

DMX_Autoplay.zip  This is a BrightScript file that you will install on the SD card as Autorun.BRS

 

DMX_Autoplay.CSV   This is a CSV file that has the commands to running the port1, port2 and DMX channels 1-4

*****************************************************************

Diagnostics:

Option 6 Selects a 'multiple diagnostic' feature.  With Switch 1, slider 6 (SW1-6) on, the board is in a diagnostic mode.  The two 8 bit ports are cycled one bit at a time on (changes every second).  The 5V TTL driver sends decimal 170 (0xAA) to the BrightSign.  And, the DMX output alternates channels 1-4 on and off every second.  This diagnostic allows for a visual on all output drivers, verified connection and baud settings to the BrightSign 5VTTL serial port, and verifies operation of the DMX controller.  This DMX operation of channels 1-4 on and off is a perfect diagnostic for a 4 channel dimmer pack.

Options: (Rev 3 Firmware)

Note: 'Fade Mode' makes Fading the lights on and off' an easy task if utilizing a DMX Dimmer Pack (on channels 1-4).  To Fade up lights just output 255 (decimal) for DMX Ch 1-4) with the appropriate Switch Selection made.  To Fade down the lights, just output a zero (decimal) with the appropriate switch selection made.

Note: Only Channels 1-4 have the 'Fade option'.  My firmware will keep adjusting the value of the channel selected until it reaches the value of the byte for that channel.  I.E. Suppose you want to have Fade control over channel 4 and we will assume that channels 1,2 and 3 are off.  Then with SW1-4 on, you would send this byte set;  TTLSend(port1;port2;0;0;0;255).  The first 3 DMX channels are off. and channel 4 is set to full on.  The HMS firmware will take care of Fading up the value from off (0) to full on(255) over a period of about 4 seconds.

*****************************************************************

Here is a table of 'bit' control and the decimal values to control that bit.

Just add the decimal numbers together to get the bits set that you want.  Setting all bits on is 255d (decimal).  Setting bits 0 and 7 on is 128+1 or 129 decimal

Link to Setting up BrightAuthor for serial-TTL use:

*****************************************************************

! Custom firmware is available for controlling more than the 4 channel dimmer packs or other options as required!

Note: External Supply Voltage:  An External Power Supply is needed to power the loads on the output connector.  Do not connect any loads that have their own power that exceeds the power as applied to the board using the 'Ext. Power Connector'.  Doing so may result in damage to the board.  I.E. Suppose that 12 volts is supplied to this board and you have a relay board with it's own power of 24Volts DC that powers the relays.  The 24VDC will feed back into the board via the foldback diodes.  Note: Foldback diodes are required for inductive loads such as relays or small motors.

 

Updated: March 15, 2010 (Firmware updated).  The options switch uses the 3.3 volts from the Brightsign for the pull up resistors.  When the BrightSign is off, my firmware was detecting this as all options selected and therefore it went into diagnostic mode.  The firmware update now checks to see if all options are low (BrightSign is off or not connected) and does not perform any diagnostics.  The board will appear to be inactive other than the 1 second led flashing.