Actions

Difference between revisions of "Apartment Building Entry Point"

From Zenitel Wiki

(Event Handler programming)
(Option 1)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{A}}
+
{{AI}}
This article describes an example of using the IP Master station as an entry Intercom point for Office Blocks and Upmarket Apartment Buildings.
+
This article describes an example of using the [[IP Flush Master -V2|IP Flush Master]] station as an entry Intercom point for Office Blocks and Upmarket Apartment Buildings.
  
=Main features=
+
==Main features==
* Use a standard AlphaCom display station as an Entry Unit (or custom made, based on a [[IP Master Station Kit - 1008093000|IP Master Kit]])  
+
* Use a standard Zenitel display station as an Entry Unit (or custom made, based on a [[IP Master Station Kit - 1008493000|IP Master Kit]])  
 
* For each station (entry unit) be able to define (from AlphaPro) which users (apartments) should be available in this stations "Address list"
 
* For each station (entry unit) be able to define (from AlphaPro) which users (apartments) should be available in this stations "Address list"
 
* Four function codes/buttons: Call, Step, Top and End
 
* Four function codes/buttons: Call, Step, Top and End
Line 9: Line 9:
 
* The users (apartments) belonging to one entry point is grouped making it possible to have several entrance points only "responsible" for their relevant users. This also prevents unnecessary disturbance to non-relevant users from visitors
 
* The users (apartments) belonging to one entry point is grouped making it possible to have several entrance points only "responsible" for their relevant users. This also prevents unnecessary disturbance to non-relevant users from visitors
  
 +
==Limitations==
 +
* The users (apartments) will not be shown in alphabetical order. They will be listed by increasing physical numbering.
 +
* Stepping can only be performed in one direction
  
=Limitations=
 
- The users (apartments) will not be shown in alphabetical order. They will be listed by increasing physical numbering.  <br/>
 
- Stepping can only be performed in one direction
 
  
 
+
==Example description==
=Example description=
+
The setup in the following example is:
The setup in the following example is:<br/>
 
 
*Apartment entry 1:
 
*Apartment entry 1:
 
**Physical station 1, 2 and 4 equals apartment 1, 2 and 4. These can be analogue or IP stations.
 
**Physical station 1, 2 and 4 equals apartment 1, 2 and 4. These can be analogue or IP stations.
**Physical 13 is the entry station. An IP Master station is preferred.
+
**Physical 13 is the entry station. An IP Flush Master station is preferred.
<br/>
+
 
 
*Apartment entry 2:
 
*Apartment entry 2:
 
**Physical station 9, 11 and 12 equals apartment 9, 11 and 12.
 
**Physical station 9, 11 and 12 equals apartment 9, 11 and 12.
 
**Physical 14 is the entry station.
 
**Physical 14 is the entry station.
<br/>
+
 
*Each entry point has its own group referred to in the programming in the entry station exp field.
+
*Each entry point has its own group referred to in the programming in the entry station [[%1.exp|exp]] field.
 
*Group 1 contains the apartments belonging to entry 1, and Group 2 has the apartments for entry 2.
 
*Group 1 contains the apartments belonging to entry 1, and Group 2 has the apartments for entry 2.
 
*6 events take care of the function and these six same events are used even if more entries and apartments are added.
 
*6 events take care of the function and these six same events are used even if more entries and apartments are added.
  
=Usage=
+
==Usage==
 
On the entry stations there are four buttons beneath the display. These are “CALL”, “STEP”, “TOP” and “END”. (These are DAK keys 21-24.)
 
On the entry stations there are four buttons beneath the display. These are “CALL”, “STEP”, “TOP” and “END”. (These are DAK keys 21-24.)
 
:STEP – When this button is pressed the first station in the corresponding group is shown in the display. Pressing it again, steps to the next, and so on. When it reaches the end it will automatically jump to the top and continue. If left untouched for 10 seconds the station will exit the list and return to standby.
 
:STEP – When this button is pressed the first station in the corresponding group is shown in the display. Pressing it again, steps to the next, and so on. When it reaches the end it will automatically jump to the top and continue. If left untouched for 10 seconds the station will exit the list and return to standby.
Line 46: Line 45:
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
=Event Handler programming=
+
==Event Handler programming==
 
'''Event 1''' - CALL event
 
'''Event 1''' - CALL event
{|  
+
[[File:Application6a.png|500px|left|thumb|]]
|-
+
<br style="clear:both;" />
|width="100pt"|'''Event Owner''':
+
 
|width="400pt"|Stations w/UDP, Id: 8 (All)
+
{{Code2|
|-
+
$CALL L%1.dir N%udd(%1.phy)
|'''Event type''': || [[Station Input or Station DAK key (Event Type)|30 - Station Input or Station DAK key]]
+
WUDD %1.phy 0
|-
+
}}
|'''Subevent''': || 21
 
|-
 
|'''When change to''': || ON
 
|-
 
|'''Action''': || $CALL L%1.dir N%udd(%1.phy)
 
|-
 
| &nbsp; || WUDD %1.phy 0
 
|-
 
|}
 
  
 
------------
 
------------
 
'''Event 2''' - STEP event
 
'''Event 2''' - STEP event
{|  
+
[[File:Application6b.png|500px|left|thumb|]]
|-
+
<br style="clear:both;" />
|width="100pt"|'''Event Owner''':
+
 
|width="400pt"|Stations w/UDP, Id: 8 (All)
+
{{Code2|
|-
+
WUDD %1.phy %gns(%1.exp,%udd(%1.phy))
|'''Event type''': || [[Station DAK key as RCI (Event Type)|30 – Station DAK key as RCI]]
+
OWN r %rdir(%udd(%1.phy))
|-
+
IF %udd(%1.phy)
|'''Subevent''': || 22
+
$DSPL L%1.dir U18 0311 'SELECT:'
|-
+
$DSPL L%1.dir U18 0312 '%2.nam'
|'''When change to''': || ON
+
$ST L%1.dir W 100
|-
+
STOP
|'''Action''': || WUDD %1.phy %gns(%1.exp,%udd(%1.phy))
+
ENDIF
|-
+
$DIAL_DAK L%1.dir U22
| &nbsp; || OWN r %rdir(%udd(%1.phy))
+
}}
|-
 
| &nbsp; || IF %udd(%1.phy)
 
|-
 
| &nbsp; || $DSPL L%1.dir U18 0311 'SELECT:'
 
|-
 
| &nbsp; || $DSPL L%1.dir U18 0312 '%2.nam'
 
|-
 
| &nbsp; || $ST L%1.dir W 100
 
|-
 
| &nbsp; || STOP
 
|-
 
| &nbsp; || ENDIF
 
|-
 
| &nbsp; || $DIAL_DAK L%1.dir U22
 
|-
 
|}
 
  
 
------------
 
------------
 
'''Event 3''' - TOP event
 
'''Event 3''' - TOP event
{|  
+
[[File:Application6c.png|500px|left|thumb|]]
|-
+
<br style="clear:both;" />
|width="100pt"|'''Event Owner''':
+
 
|width="400pt"|Stations w/UDP, Id: 8 (All)
+
{{Code2|
|-
+
WUDD %1.phy 0
|'''Event type''': || [[Station DAK key as RCI (Event Type)|30 – Station DAK key as RCI]]
+
$DIAL_DAK L%1.dir U22
|-
+
}}
|'''Subevent''': || 23
 
|-
 
|'''When change to''': || ON
 
|-
 
|'''Action''': || WUDD %1.phy 0
 
|-
 
| &nbsp; || $DIAL_DAK L%1.dir U22
 
|-
 
|}
 
  
 
------------
 
------------
 
'''Event 4''' - END event
 
'''Event 4''' - END event
{|  
+
[[File:Application6d.png|500px|left|thumb|]]
|-
+
<br style="clear:both;" />
|width="100pt"|'''Event Owner''':
+
 
|width="400pt"|Stations w/UDP, Id: 8 (All)
+
{{Code2|
|-
+
$C L%1.dir
|'''Event type''': || [[Station DAK key as RCI (Event Type)|30 – Station DAK key as RCI]]
+
WUDD %1.phy 0
|-
+
$DD L%1.dir L9534
|'''Subevent''': || 24
+
$ST L%1.dir
|-
+
}}
|'''When change to''': || ON
 
|-
 
|'''Action''': || $C L%1.dir
 
|-
 
| &nbsp; || WUDD %1.phy 0
 
|-
 
| &nbsp; || $DD L%1.dir L9534
 
|-
 
| &nbsp; || $ST L%1.dir
 
|-
 
|}
 
  
 
------------
 
------------
 
'''Event 5''' - Timeout event: TIMEOUT: reset UDD and display text.
 
'''Event 5''' - Timeout event: TIMEOUT: reset UDD and display text.
{|  
+
[[File:Application6e.png|500px|left|thumb|]]
|-
+
<br style="clear:both;" />
|width="100pt"|'''Event Owner''':
+
 
|width="400pt"|Stations w/UDP, Id: 8 (All)
+
{{Code2|
|-
+
WUDD %1.phy 0
|'''Event type''': || [[Event Timeout (Event Type)|21 – Event Timeout]]
+
$DD L%1.dir L9534
|-
+
}}
|'''Subevent''': || 0
 
|-
 
|'''When change to''': || ON
 
|-
 
|'''When related to''': || All
 
|-
 
|'''Action''': || WUDD %1.phy 0
 
|-
 
| &nbsp; || $DD L%1.dir L9534
 
|-
 
|}
 
  
 
------------
 
------------
 
'''Event 6''' - Conversation Outgoing: STOP TIMER started in the '''STEP''' event.
 
'''Event 6''' - Conversation Outgoing: STOP TIMER started in the '''STEP''' event.
{|  
+
[[File:Application6f.png|500px|left|thumb|]]
|-
+
<br style="clear:both;" />
|width="100pt"|'''Event Owner''':
+
 
|width="400pt"|Stations w/UDP, Id: 8 (All)
+
{{Code2|
|-
+
$ST L%1.dir
|'''Event type''': || [[Conversation Outgoing (Event Type)|8 – Conversation Outgoing]]
+
}}
|-
 
|'''Subevent''': || 0
 
|-
 
|'''When change to''': || ON
 
|-
 
|'''When related to''': || All
 
|-
 
|'''Action''': || $ST L%1.dir
 
|-
 
|}
 
  
=Backlight Control=
+
==Backlight Control==
When using an IP Master station as the Entrance point station it is possible to control the display backlight. Below is shown to different options for this:
+
When using an IP Flush Master station as the Entrance point station it is possible to control the display backlight. Below is shown to different options for this:
  
== Option 1==
+
=== Option 1===
 
Backlight is lit when someone starts pressing the STEP button, Backlight is automatically switched of by either conversation end, timeout or the END button being pressed:
 
Backlight is lit when someone starts pressing the STEP button, Backlight is automatically switched of by either conversation end, timeout or the END button being pressed:
 
* Add the following action string to the '''STEP''' event:
 
* Add the following action string to the '''STEP''' event:
**$DIP N%1.phy "sbl 1 10"
+
{{Code2|
 +
$DIP N%1.phy "sbl 1 10"
 +
}}
 +
 
 
[[File:Entryapp1.jpg]]
 
[[File:Entryapp1.jpg]]
  
 
*Add this line to the '''END''' event and the '''TIMEOUT''' event:
 
*Add this line to the '''END''' event and the '''TIMEOUT''' event:
**$DIP N%1.phy "sbl 1 0"
+
{{Code2|
 +
$DIP N%1.phy "sbl 1 0"
 +
}}
 
[[File:Entryapp2.jpg]]
 
[[File:Entryapp2.jpg]]
 
[[File:Entryapp3.jpg]]
 
[[File:Entryapp3.jpg]]
Line 196: Line 134:
 
*Add this event:
 
*Add this event:
 
'''Event 7''' - Conversation Outgoing: FORCE BACKLIGHT OFF when the conversation is ended.
 
'''Event 7''' - Conversation Outgoing: FORCE BACKLIGHT OFF when the conversation is ended.
{|  
+
[[File:Application6g.png|500px|left|thumb|]]
|-
+
<br style="clear:both;" />
|width="100pt"|'''Event Owner''':
+
{{Code2|
|width="400pt"|Stations w/UDP, Id: 8 (All)
+
$DIP N%1.phy "sbl 1 0"
|-
+
}}
|'''Event type''': || [[Conversation Outgoing (Event Type)|8 – Conversation Outgoing]]
 
|-
 
|'''Subevent''': || 0
 
|-
 
|'''When change to''': || OFF
 
|-
 
|'''When related to''': || All
 
|-
 
|'''Action''': || $DIP N%1.phy "sbl 1 0"
 
|-
 
|}
 
  
== Option 2 ==
+
=== Option 2 ===
 
Backlight is constantly on:
 
Backlight is constantly on:
 
*Put all Entry Point stations in UDP group 1 and add these events:
 
*Put all Entry Point stations in UDP group 1 and add these events:
 
'''Event 7''' - Station Reset: TURN BACKLIGHT ON when station starts after power cycle, or communication restart.
 
'''Event 7''' - Station Reset: TURN BACKLIGHT ON when station starts after power cycle, or communication restart.
 +
[[File:Application6h.png|500px|left|thumb|]]
 +
<br style="clear:both;" />
 +
Action:
 
{|  
 
{|  
 
|-
 
|-
|width="100pt"|'''Event Owner''':
+
| $DIP N%1.phy "sbl 1 10"
|width="400pt"|Stations w/UDP, Id: 1 (Entry Points)
 
|-
 
|'''Event type''': || [[Faulty Station Line (Event Type)|13 – Faulty station line]]
 
|-
 
|'''Subevent''': || 0
 
|-
 
|'''When change to''': || OFF
 
|-
 
|'''Action''': || $DIP N%1.phy "sbl 1 10"
 
 
|-
 
|-
 
|}
 
|}
Line 234: Line 155:
 
------------
 
------------
 
'''Event 8''' - Conversation Outgoing: KEEP BACKLIGHT ON when conversation is ended.
 
'''Event 8''' - Conversation Outgoing: KEEP BACKLIGHT ON when conversation is ended.
 +
[[File:Application6i.png|500px|left|thumb|]]
 +
<br style="clear:both;" />
 +
Action:
 
{|  
 
{|  
 
|-
 
|-
|width="100pt"|'''Event Owner''':
+
| $DIP N%1.phy "sbl 1 10"
|width="400pt"|Stations w/UDP, Id: 8 (All)
 
|-
 
|'''Event type''': || [[Conversation Outgoing (Event Type)|8 – Conversation Outgoing]]
 
|-
 
|'''Subevent''': || 0
 
|-
 
|'''When change to''': || OFF
 
|-
 
|'''When related to''': || All
 
|-
 
|'''Action''': || $DIP N%1.phy "sbl 1 10"
 
 
|-
 
|-
 
|}
 
|}
  
[[Category:Applications]]
+
[[Category:AlphaCom Applications]]
 +
[[Category:ICX-AlphaCom Applications]]

Latest revision as of 15:18, 6 January 2023

AI.png

This article describes an example of using the IP Flush Master station as an entry Intercom point for Office Blocks and Upmarket Apartment Buildings.

Main features

  • Use a standard Zenitel display station as an Entry Unit (or custom made, based on a IP Master Kit)
  • For each station (entry unit) be able to define (from AlphaPro) which users (apartments) should be available in this stations "Address list"
  • Four function codes/buttons: Call, Step, Top and End
  • When stepping, the display shows the number and name as programmed in AlphaPro, Users & Stations.
  • The users (apartments) belonging to one entry point is grouped making it possible to have several entrance points only "responsible" for their relevant users. This also prevents unnecessary disturbance to non-relevant users from visitors

Limitations

  • The users (apartments) will not be shown in alphabetical order. They will be listed by increasing physical numbering.
  • Stepping can only be performed in one direction


Example description

The setup in the following example is:

  • Apartment entry 1:
    • Physical station 1, 2 and 4 equals apartment 1, 2 and 4. These can be analogue or IP stations.
    • Physical 13 is the entry station. An IP Flush Master station is preferred.
  • Apartment entry 2:
    • Physical station 9, 11 and 12 equals apartment 9, 11 and 12.
    • Physical 14 is the entry station.
  • Each entry point has its own group referred to in the programming in the entry station exp field.
  • Group 1 contains the apartments belonging to entry 1, and Group 2 has the apartments for entry 2.
  • 6 events take care of the function and these six same events are used even if more entries and apartments are added.

Usage

On the entry stations there are four buttons beneath the display. These are “CALL”, “STEP”, “TOP” and “END”. (These are DAK keys 21-24.)

STEP – When this button is pressed the first station in the corresponding group is shown in the display. Pressing it again, steps to the next, and so on. When it reaches the end it will automatically jump to the top and continue. If left untouched for 10 seconds the station will exit the list and return to standby.
CALL – Pressing this button simply calls the selected apartment from the list
TOP – Jumps to the top of the list
END – Exits the list, or ends an ongoing call.

PS: CALL and TOP have no functionality without STEP being used first.

Configure the Navigation keys with the "T"-command to show the button functions permanently in the display:

Entryapp4.PNG


Entry1.png


Event Handler programming

Event 1 - CALL event

Application6a.png


Action commands:

$CALL L%1.dir N%udd(%1.phy)
WUDD %1.phy 0



Event 2 - STEP event

Application6b.png


Action commands:

WUDD %1.phy %gns(%1.exp,%udd(%1.phy))
OWN r %rdir(%udd(%1.phy))
IF %udd(%1.phy)
$DSPL L%1.dir U18 0311 'SELECT:'
$DSPL L%1.dir U18 0312 '%2.nam'
$ST L%1.dir W 100
STOP
ENDIF
$DIAL_DAK L%1.dir U22



Event 3 - TOP event

Application6c.png


Action commands:

WUDD %1.phy 0
$DIAL_DAK L%1.dir U22



Event 4 - END event

Application6d.png


Action commands:

$C L%1.dir
WUDD %1.phy 0
$DD L%1.dir L9534
$ST L%1.dir



Event 5 - Timeout event: TIMEOUT: reset UDD and display text.

Application6e.png


Action commands:

WUDD %1.phy 0
$DD L%1.dir L9534



Event 6 - Conversation Outgoing: STOP TIMER started in the STEP event.

Application6f.png


Action commands:

$ST L%1.dir


Backlight Control

When using an IP Flush Master station as the Entrance point station it is possible to control the display backlight. Below is shown to different options for this:

Option 1

Backlight is lit when someone starts pressing the STEP button, Backlight is automatically switched of by either conversation end, timeout or the END button being pressed:

  • Add the following action string to the STEP event:

Action commands:

$DIP N%1.phy "sbl 1 10"


Entryapp1.jpg

  • Add this line to the END event and the TIMEOUT event:

Action commands:

$DIP N%1.phy "sbl 1 0"


Entryapp2.jpg Entryapp3.jpg

  • Add this event:

Event 7 - Conversation Outgoing: FORCE BACKLIGHT OFF when the conversation is ended.

Application6g.png


Action commands:

$DIP N%1.phy "sbl 1 0"


Option 2

Backlight is constantly on:

  • Put all Entry Point stations in UDP group 1 and add these events:

Event 7 - Station Reset: TURN BACKLIGHT ON when station starts after power cycle, or communication restart.

Application6h.png


Action:

$DIP N%1.phy "sbl 1 10"

Event 8 - Conversation Outgoing: KEEP BACKLIGHT ON when conversation is ended.

Application6i.png


Action:

$DIP N%1.phy "sbl 1 10"