Configuring the gpio triggers for the channel type, With, Configuring the gpio triggers – Grass Valley GV STRATUS Playout v.2.0 User Manual
Page 34: For the channel type

34
Configuring your account
Changing the channel type settings
To configure the router sources:
1 If you are continuing to configure a selected channel type, skip to step 2. To open the
Channel Settings page:
• In the top menu, click Settings.
• Click the Channel Types tab.
• In the Select Channel Type list, click the name of the channel type you created for
devices connected to a router.
2 Click the Router Configuration tab.
3 Assign a router source to each box as required. Each box represents a router source
made available for a source event. To assign the router sources:
• Click the box for the box you want to configure.
• In the Select Device list, click one of the devices that is configured with a router.
• Click the router source you want to assign to the box.
• Click Select.
• Repeat for each router source you want available.
4 Click Update Channel Type.
Configuring the GPIO triggers for the channel type
Each SSP-3801 card has two General Purpose Input/Output (GPIO) connectors offering up
to four opto-isolated, open collector GPIOs (see the SSP-3801 User Guide for more
information). The pinouts are 1|G|2 and 3|G|4. The GPIO pins function both as inputs and
outputs. As outputs they can be used to trigger downstream external hardware. As inputs
they can be used to trigger internal pre-programmed actions when they change from one
state to another. It is not recommended to use the GPIO pins as both inputs and outputs
simultaneously.
To configure the GPI triggers:
1 If you are continuing to configure a selected channel type, skip to step 2. To open the
Channel Settings page:
• In the top menu, click Settings.
• Click the Channel Types tab.
• In the Select Channel Type list, click the name of the channel type you want to
change.
2 Click the GPI tab.
3 In each GPI section, specify the action for each state.
• No Action: a change to the state is not acted upon.
• Take Next: a change to the state triggers a Take Next action, which places the next
event in the playlist on air.
• Cue Next: a change to the state triggers a Cue Next action, which cues the next
primary event, its related secondary events, and any subsequent automatic events
so they are ready to go on air safely when a Take Next action is performed.
• Hold Next: a change to the state triggers a Hold Next action, which prevents the
next events from going on-air.