Studer OnAir 3000 Operating Instructions Manual page 332

Configuration Procedure
Document generated: 10.10.14
GPInputFunction 11
UserLED5
GPOutputFunction 11
UserKey5
Flashing: Call Initiated
F5
Bright: Call Enabled
Dark: Call Disabled
GPInputFunction 17
UserKey5
1 Case
Let's assume that C2 is off-air for a start (i.e., GPOutputFunction 16 of C2
st
is low). The F5 user key on C2 is dark. The F5 user key on C1 is illuminated,
indicating that a call signal from C1 to C2 is allowed.
• The C1 operator presses his F5 key; GPOutputFunction 11 and input 1 of
AND2 go high. The output of AND2 goes high, too
• The output of AND3 alternates with the rate of GPOutputFunction 1
(generator), and the GPInputFunction 5 of C2 makes the C2 F5 key
(UserLED5) flash.
• The output of AND1 alternates too and makes the F5 key on C1 (UserLED5)
flash via XOR1.
• Operator C2 confirms the call signal by pressing his flashing F5 key. Input
2 of AND4 goes high. Since input 1 of AND4 (output of AND2) is high as
well, the output of AND4 goes high and turns, via the GPInputFunction
17, the GPOutputFunction 11 off again.
If C2 is on-air (i.e., GPOutputFunction 16 of C2 is high), the C1 F5 key is
2 Case
nd
dark.
• The C1 operator presses his F5 key; GPOutputFunction 11 and input 1 of
AND2 go high.
• Since input 2 of AND2 is low (output of NOT1 is low), the ouptut of AND3
remains low and the F5 key on C2 remains dark; the C2 operator is not
disturbed.
• The output of AND1 still alternates and makes the F5 key on C1 flash,
telling the C1 operator that his call has been sent out.
• As soon as C2 goes off-air, the output of NOT1 changes from low to high,
opening the call signal path to C2; the F5 key on C2 flashes.
• Operator C2 confirms the call signal by pressing his flashing F5 key. Input
2 of AND4 goes high. Since input 1 of AND4 (output of AND2) is high as
well, the output of AND4 goes high and turns, via the GPInputFunction
17, the GPOutputFunction 11 off again.
Notes As can easily be seen from the diagram above, the whole logic is implemented
in console C1. This is not mandatory, but allows implementing custom logic
in a system that also incorporates OnAir 2500 consoles without a memory
upgrade.
Although the logic diagram is not very complicated, a structured procedure
is recommended. Implementing the desired functionality is much easier if a
diagram is available where also the gate inputs are numbered.
First of all, since no hardware GPIOs are used, neither GPInputs nor GPOut-
puts need to be configured in our case – all that needs to be done takes place
in the GPIOFunctions and CustomLogic sections of the configuration tool.
SW V6.0
OnAir Digital Mixing Consoles
OnAir 3000 (C1)
1
NOT
1
XOR
1 2
GPOutputFunction 1
Generator
1
AND
2
1
1
AND
2
2
1
AND
2
4
OnAir 2500 (C2)
GPOutputFunction 16
RedLight OnAir
1
GPInputFunction 5
AND
2
UserLED5
3
Flashing:
Caller Indication
GPOutputFunction 5
UserKey5
Configuration 6-91
F5