For Brightsign Compact HD410, 810 & 1010

16 Input, 16 Output with 200 DMX Channels

      
HMS-C16-DMX-1 Board Shown (3 Terminal Block for DMX Connection)

HMS-C16-DMX (Interface Board) w/DMX512 Controller

or, HMS-C8-DMX (Interface board) w/DMX512 Controller

Features:

• 24 Fade channels
• Footprint:  4.8 x 2.8 inches
• Utilizes the 5V TTL Serial Port (.9 meter cable included).
• 16 or 8 Output Drivers for Lamps or Relays (.3 ampere each driver)
• Terminal blocks for all I/O connections
• Diagnostic Mode and 'Options' selectable on board
• Requires 12V External Power Supply (use 2.1mm jack or Terminal Block connections)
• On board LED's to indicate Roku Power and Processor running.
• 5VTTL Serial Setup: 38400 baud, N,8,1
• 3.3 Volts available on 'Input Terminal Strip' for PIR connections.
• Individual DMX Channels can be set using the new 'HMS Protocol' command structure.
• Special 'Channel Set Commands' to enhance 'DMX Head' controlling.

Recommended: Use the HMS RS232-TTL 'Roku Adapter Board' to use your computer to test your strings to the C-16 and C8 boards prior to testing with the BrightSign.  Trial and error using the BrightSign to 'debug' strings will take hours or days troubleshoot.  With the RS232-TTL board it will take minutes to verify your command strings.

Description of Operation:
This board is used to interface to a BrightSign 'Compact'.  The first 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) from this 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. The 8 inputs (8-15) are transmitted to the Brightsign as ascii strings '8' -'15' plus carriage return (decimal 13).  These are evaluated as values 8-15 in BrightAuthor.

Serial Transmission 'Break' Protocol:  The BrightSign has to allow 10 milliseconds to elapse between serial data 'bursts' going out if a command is not completed.  This 10 millisecond 'off' 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.  The next byte following 'Break' is a command byte.

HMS Protocol Commands:
Note: Bytes in brackets [ ] are the command bytes

• Command0:  Send the Input Port byte (inputs 8-15).
   C-16             [0]  1 Binary byte is returned that represents the inputs 8-15.  (1,2,4,8,16,32,64,128 for the one associated input low (Input 7,8,9,10,11,12,13,14 or 15)
   C-8               [0]  A zero is returned for this board configuration as there are no inputs 8-15
  
• Command1:  Set Output Ports (Port1 and Port 2 values), (next Command may follow)
    C-16             [1, Port1 Value, Port2 Value]
    C-8               [1, Port1 Value]
  
• Command2:  Set Some or All values of Output Ports, DMX Channels.
    C-16             [2, #Bytes, Port1, Port2, 1  to #Bytes DMX Bytes]    Note: #Bytes Range is 1 to 250
    C-8               [2, #Bytes, Port1, 1 to 200 DMX bytes], followed by 'Break'
  
  **********COLOR SPECIFIC COMMANDS (These are 'RGBW' board commands and do not apply to 'non-RGBW' board sets.)
  
  *********DMX SPECIFIC COMMANDS 16-31
  
• Command16:  Set DMX Channel Values (Starts at Channel 1)
                         [16, #Bytes,  DMX_CH1 to #bytes]
  
• Command17:  Set Multiple DMX 'Fade Channel' values
                         [17, #Bytes, Channel#,'Channel Value', 'Fade Value', Channel#, 'Channel Value', 'Fade Value',.... to #Bytes]
  
• Command18:  Set 1 DMX 'Fade Channel' Value and Fade
                         [18, Channel#, Channel Value, Fade Value]
  
• Command19:  Set all 24 DMX Fade values to one value
                         [19, Fade Value, 204]
  
• Command20:  Set Channels 1 to 24 Fade Values (values have to be in Channel order!)
                         [20, #Bytes, Ch1_Fade Value, Ch2 Fade Value,... to #Bytes]
  
• Command21:  Set 1 or more DMX channels to a value. 
                         [21, #Bytes, Channel#, Value, Channel#, Value....to #Bytes]
  
• Command22:  Set 1 DMX channel to a value
                         [22, Channel#, Value]
  
• Command23:  Set all DMX channels to one value. Channels 1 to 250
                         [22, Channel Value, 204]
  
• Command24:  Set all 24 DMX ' Fade' channels to one value (Channels 1-16)
                         [24, Channel Value, 204]
  
• Command25:  Set all DMX 'Non Fade' channels to one value. Channels 25-250
                         [25, Channel Value, 204]
  
• Command26:  Set DMX Channel#, first byte to this channel, successive bytes to successive channels.  Well suited to DMX Head Controlling!
                         [26, #Value Bytes, Start Channel#,  Value1, Value2,.... to #Bytes] Note: Do not include the Start channel for '#Value Bytes'
  
• Command27:  Set the Default 'Power UP' Fade value for Channels 1-16. Note: Recorded and retained in EEPROM on chip.
                         [27, Default Value, 204] Note: Range 0-250 Not a 'Play Command'
  
• Command28: Set all DMX channels off Instantly (does not affect fade values)
                        [28,204]
  
• Command29: Set Maximum DMX Channels for transmit Note: Recorded and retained in EEPROM on chip.
                        [29, Maximum Channels, 204] Note: Range 4 to 250
  
  Note: DMX Commands 30,31 are for future development.

*********Play/Record and Other 'Scene' Commands 32-34

Link to 'Scene Format (Protocol)'

• Command32:  Play 'Recorded' Scene  
  4 bytes             [32, Scene# (1-64), REPEAT(0-255), 204] Note: If Repeat=255, the scene plays 'forever', or until a cancel command or next play scene command is received
                          Note: Version 4.xx firmware, allows for a scene to call another scene.
  
• Command33:  Record 'Scene' (256 byte limit) (Scenes can be concatenated)
                          [33, Scene# (1 to 64), 204, 1 to 256 bytes]
  
• Command34:  Cancel 'Play Scene'. This command should be issued prior to any new command if Command32 was last command.  This insures that the 'Play Scene' Command is stopped.
  2 bytes             [34, 204]
  

*********Development Commands (use these commands only from your computer and connected to the RS232-TTL Adapter)
                  Note: These commands are disabled by Option7!

• Command 43 (0x2B): Say Channels 17-48 values to Serial Port
                2 bytes         [43,204]
  
• Command 44 (0x2C): Say Scene# to the serial port (256 bytes to the Serial Port)
                3 bytes         [44, scene#, 204]
  
• Command 45 (0x2D): Say Software Version to the serial port. Note: Includes Board Setup (DMX, RGBW or HCA)
                2 bytes        [45,204]
  
• Command 46 (0x2E): Say Goals & Fade Values for DMX channels 1-16, plus 'Default Fade' and  'Max Channels' to the serial port
                2 bytes        [46,204]
  

Firmware Upgrade Command:

Notes:

1. Any 'Command' followed by a 'break condition' terminates the Command. So, if zero bytes follow Command=1, Command 1 will simply be terminated at the break condition (10 milliseconds of no serial port activity).
2. If you use 255 for the #bytes, then the command will be terminated at 'Break' and fast flashing (Hz LED) will indicate that the command did not terminate correctly (#bytes was not received).
3. If #bytes is less than the bytes you are sending as part of the protocol, unexpected results will happen!  
4. Any 'illegal' command results in 'dumped bytes' until 'Break' condition.  So, if a large string of bytes is sent, and a channel fade number is out of range (>16), then the remaining bytes of that string are discarded.
5. To 'Concatenate' Scenes:  see 'Scene Format Protocol'

To Send Multiple Commands (not concatenated) , Send 1 command, then pause for 10 milliseconds, then send the next command and pause and so on except where designated above.

Note: Fast Flash of the 1Hz LED (3 Hz).  When any command is terminated with 'Break', fast flashing occurs.  When a command is sent incomplete or out of range, (I.E. set fade for channel 20), because channel 20 is out of range (not a fade channel), fast flashing is set.  Fast Flashing is cleared upon complete reception of a command not requiring the 'Break' condition.  I.E. Send 'Command0', to clear the fast flashing after 'Break'.

Note: Any 'Command' followed by a 'break condition' terminates the Command. So, if zero bytes follow Command=1, Command 1 will simply be terminated at the break condition.

Note: Any 'illegal' command results in 'dumped bytes' until 'Break' condition.  So, if a large string of bytes is sent, and a channel fade number is out of range (>16), then the remaining bytes of that string are discarded.

PORT's , and DMX Protocol Bytes:

Command #2, Port1 Value, Port2 Value, 1 to 'Max Channels' DMX Bytes (See the DMX protocol below).  'Max Channels' is set by command 29.

DMX512 Operation:  The DMX first 100 channels are sent every second or whenever the DMX 'Channel' bytes change (resulting in 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 (C16 Board) or (Port1 Byte if C8 Board) go to the DMX channels 1-'Max Channels'.  If only a single byte follows the Port2 byte, then only channel 1 of the DMX512 protocol will  receive the new data.  All other channels not receiving data are unchanged..  I.E.

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 plus the two Port bytes.  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.

'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'.

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

Diagnostics:

Option 6 Selects a 'multiple diagnostic' feature.  With Switch 1, slider 6 (SW1-6) set 'on', the board is in a diagnostic Command.  The two 8 bit ports are cycled one bit at a time to 'on' (changes every second).  The 5V TTL driver sends decimal 170 (0xAA) to the BrightSign.  The RGBW board is cycled to 50% on (all channels) then off. The DMX output alternates channels 1-12 on and off every second (no fading).  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:

• Option8    Enable Firmware Upgrade (Only checked on Power-Up with Rev 4 Firmware)
• Option7    Disable Development Commands (Commands 44 and up will not respond).  Set this switch 'On' once your development is completed!
• Option6    Diagnostic (see description above)
• Option5    Polling Required to get the Status of the Inputs.  If Off, any change in inputs (buttons) is immediately transmitted to the BrightSign. (C-16 boards only)
• Option4    Continuous transmit of DMX Data (Note: This may cause flickering on some DMX units)
• Option3    Transmit DMX every .8 seconds (Some DMX devices will time out and go into standby after 1 second and the lights will turn off)
• Option2    Future
• Option1    Future

Note Fade Control: Fade Control makes 'Fading the lights on and off' an easy task if utilizing a DMX Dimmer Pack.  Channels 1-16 are dedicated for fade control (adjustable rate of change of Brightness)
Note: Fade Speed: The Fade speed value is the number of milliseconds to increment (increase brightness by '1') or decrement (decrease brightness by '1') of the channel value.  If the channel value is 255, and the speed value=20, then it takes 20 milliseconds for each step or 5.1 seconds to obtain full brightness (0 to 255).  If the Fade Speed is zero, the new value is output immediately to the DMX channel.  So if the channel value was 0, then 255 and the speed value is 255 (255 milliseconds per step of 1),  then it will take 65535 milliseconds (255 times 255) to finish Fade (1092 seconds).  You may want to keep the value below 50.

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

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

• Bit     Binary              Decimal
• 0       00000001b      1d
• 1       00000010b      2d
• 2       00000100b      4d
• 3       00001000b      8d
• 4       00010000b      16d
• 5       00100000b      32d
• 6       01000000b      64d
• 7       10000000b      128d

To set Port Bits, 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 1+128 or 129 decimal.

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

Page Updated 02/15/2012