22
• Give the Event a useful description (e.g., “Mute”)
• If you want to have the Event initiated by a button press, be sure the event number corresponds to the correct
button (see Appendix B.2).
• If you want to have the Event initiated by a general purpose input signal, select Event 9 or higher (and be sure
the CB2000 jumper (see page 2) connects pins 1 and 2). The CB2000 constantly scans all inputs, searching for an
event that matches any Triggers you have defined. When a matching event is recognized, the corresponding out-
put actions are executed in rapid succession.
• If you want to have the Event initiated according to a schedule, select the schedule you’d like using the Time
Start menu
• Select the mode in which you would like to run the defined Actions:
• All: the CB2000 will attempt to execute all Actions for that event simultaneously, but in no particular order
(e.g., Action 2 and Action 1 and Action 3...)
• One per call: the CB2000 will treat the actions as a loop, executing the next Action in the series each time the
Event is initiated (e.g., Action 1 on the first button press, Action 2 on the second button press, Action 1 on the
third button press, etc.). This is useful for toggle functions like power, or freeze.
• Assign or remove one or more Actions to this Event using the fields under Actions 1–4 and the guidance under
Create Action (Appendix A.10).
If the CB2000 has been physically installed, you can test the Event you created by clicking the Test Event button.
(Note that you can also test Events via the Event Viewer by clicking on the checkmark to the right of each Event.)
Be sure to Save the Event before moving to another section.
Events 1-8 are used for the CB2000 buttons.
Events 9-10 are for use with the GPI.
Events 12-14 are used with the CB50.
To Next Page
Loading...
Need help?
General