AVDT-BOB
User’s manual
v1.3
Page
21
/
25
4.6.4.1
GPIO in GPI Mode
When GPI Mode is selected for a GPIO, 2 trigger conditions can be chosen:
-
Pulse
: Task1-8 are running when a rising edge is detected on the selected GPI
between 2 GPIO periods. This trigger must be used for push button.
-
State
: Task1-8 are running if a level change appears on the selected GPI between
2 GPIO periods. This trigger must be used for button with 2 states (On/Off)
For each GPIO defined as a GPI, up to 8 tasks can be set to manage a specific action on the
AVDT-BOB:
-
Each task can be set individually and may be started/stopped via ON/OFF button.
-
The actions that can be set for a task are the following
Group
Component
Function Managed
Inputs
MicLine1-2
Mute, Unmute, Phase[On/Off], 48V[On/Off]
AES3 in1-2
Mute, Unmute, Phase[On/Off]
Dante in1-4
Mute, Unmute, Phase[On/Off]
All Inputs
Mute, Unmute
Mixers
Master1-4
Mute, Unmute
All Mixers
Mute, Unmute
Outputs
Analog out1-2
Mute, Unmute
AES3 out1-2
Mute, Unmute
Dante out1-4
Mute, Unmute
All Outputs
Mute, Unmute
Scene
SceneName1-7
Load
Notices:
-
The actions are treated sequentially from task 1 to task 8
-
When “State” is selected for the GPI
trigger, all functions except “Scene/Load”
reflects the State of the GPI. For instances
1.
If “Mute” function is
set as an action, the mute is done when the external GPI
is changed from 0 to 1 and Unmute when it is changed from 1 to 0.
2.
If “Unmute” function is
set as an action, the Unmute is done when the external
GPI is changed from 0 to 1 and Mute when it is changed from 1 to 0.
-
The use of the Scen
e must be done with care and should be the last task “On” for
the GPI
-
The GPIO settings are saved with each scene and it is possible to cascade the
automation using multi scenes
