Actions

Difference between revisions of "Custom PTT"

From Zenitel Wiki

Line 6: Line 6:
 
[[File:PTT App.PNG|thumb|500px|left]]
 
[[File:PTT App.PNG|thumb|500px|left]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
 +
{{Code2|
 +
$%chg(M,MREL] L%1.dir
 +
}}
 
All IP OR stations are put in to [[UDP group]] 2. They are all set to [[Users_%26_Stations_(AlphaPro)#General|station type "Master Station"]]. Input 1 is then regarded as DAK 11. The event triggers when the input is activated (On) and when it is deactivated (Off), meaning it will do [[$M]] (M-key pressed) when the event goes on, and [[$MREL]] (M-key released) when the event goes off.
 
All IP OR stations are put in to [[UDP group]] 2. They are all set to [[Users_%26_Stations_(AlphaPro)#General|station type "Master Station"]]. Input 1 is then regarded as DAK 11. The event triggers when the input is activated (On) and when it is deactivated (Off), meaning it will do [[$M]] (M-key pressed) when the event goes on, and [[$MREL]] (M-key released) when the event goes off.
  

Revision as of 12:59, 31 May 2022

AI.png

This example describes how the M-key can be controlled through an input on an IP station. The scenario described is an operating theatre with an IP OR station on the wall. Surgeons cannot use their hands to control the M-key and are therefore using a footpedal connected to input 1. When the footpedal is pressed, the input goes active. When it is released, the input is deactivated.

A single event is enough:

PTT App.PNG


Action commands:

$%chg(M,MREL] L%1.dir


All IP OR stations are put in to UDP group 2. They are all set to station type "Master Station". Input 1 is then regarded as DAK 11. The event triggers when the input is activated (On) and when it is deactivated (Off), meaning it will do $M (M-key pressed) when the event goes on, and $MREL (M-key released) when the event goes off.