User guide

35
•
•
•
•
•
•
STATE
After the EVENTS row, the interactive playlist may include one or more STATE rows. These rows
begin with the keyword STATE. The first cell after the STATE keyword is the name of the video or
image file to display, or audio file to play. When the state is entered, this file starts playing. The
remaining cells describe what state to jump to when the corresponding event happens. For
example, in the demo example, the first state is DEMO_MENU.BMP. While in this state, the main
menu for the demo appears on the display. If the user presses the elo touch screen or clicks the
mouse in the right spot to trigger the elo:110:180:350:400 event, then BrightSign jumps to the
new state CARS.TS. Look at the STATE rows in the demo example; notice one of these rows starts
with CARS.TS. It is also important to note that there can be only one state with a particular file.
To understand this better, open the demo’s AUTOPLAY.CSV file in Excel while playing the demo
on your BrightSign. As you select options on your BrightSign, look at the interactive playlist to
see how it tells your BrightSign what to do. You can then edit the autoplay interactive playlist in
Excel and Save As… a CSV file to create your own applications.
Controlling GPIO outputs from an interactive playlist
To control GPIO output for a particular state, add a GPIO command to the second column of the
state specification in the interactive playlist.
The general syntax is:
<state name>:<gpio command>(<gpio_num>;<gpio_num>;gpio_num)
Enter the state name followed by a colon, then the gpio command, then a list of GPIO’s separated
by semicolons inside parentheses. For the HD2000, GPIO values must be between 17 and 22. For
all other models, GPIO values must be between 0 and 7. GPIO value 0 or 17 corresponds to the
first LED on the button board.
The GPIO commands are:
• gpiosOn: Turns on the specified GPIO’s; unspecified GPIO’s are unchanged.
• gpiosOff: Turns off the specified GPIO’s; unspecified GPIO’s are unchanged.