User guide

25
later in the document). To do this, append the following to the state name specified in an
event column:
:counter(<registry key name>)
In the example above, the state cars.mpg is in the “elo:110:180:350:400” event column.
To track the number of times that the user activates this transition, enter
“cars.mpg:counter(TouchToDemoMenu) in place of “cars.mpg”. The value in the registry
corresponding to the TouchToDemoMenu key is incremented when the corresponding
event is triggered.
To display the contents of the registry from a CSV file, use the reserved state name
“DisplayRegistry”. That is, add a row to the table with the word “DisplayRegistry” in the
column to the right of the keyword STATE. The remainder of the row is like any other
row in the table – it contains other states to transition to when events occur. Elsewhere in
the table, add the state DisplayRegistry in the column for the event intended to cause the
registry to be displayed.
When the system transitions to this state, playback from the prior state is stopped and the
contents of the registry are displayed on the monitor attached to the BrightSign.
To display only a subset of the registry, use the following syntax:
DisplayRegistry-<registry section name>
To copy the contents of the registry to a file on a CF card, SD card, or USB mass storage
device, enter the following in the state table:
Execute(CopyRegistry <file-name>)
Examples of <file-name> include:
registry-output.csv
sd:/registry-output.csv
usb1:/registry-output.csv
The contents of the registry are written in a comma separated value format, allowing easy
import into spreadsheet applications.
The entry “Execute(CopyRegistry <file-name>)” should be placed in the CSV file in the
appropriate row and column (appropriate state / event). Unlike other entries in this part of
the state table, this entry only executes the specified command (CopyRegistry) and does
not transition to a new state.
Controlling GPIO Outputs from a CSV File (HD2000 only)
When using CSV files on the HD2000, it is possible to control the GPIO outputs from a
CSV file. GPIO’s can be set by appending a GPIO command to the state specifications in
the second column of CSV files. The GPIO’s are set based on the appended command
when the state is entered.