Actions

Difference between revisions of "EBMDR-8 - Configuration"

From Zenitel Wiki

(→‎Enable the use of the EBMDR-8 Module)
(→‎LED Indications)
 
(24 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{AI}} [[ File:EBMDR modules.png|thumb|right|500px|DAK key numbering on the Expansion Module EBMDR-8]]
 +
This article describes how to configure the AlphaCom when using the Call Panel [[ECPIR-3P]] together with the Expansion Module [[EBMDR-8]].
 +
Up to 4 expansion modules can be attached to one ECPIR-3P.
  
 
==Enable the use of the EBMDR-8 Module==
 
==Enable the use of the EBMDR-8 Module==
−
The following setting under '''Users & Stations''' > '''Station Type''' in AlphaPro needs to be checked when using the expansion module.  
+
The following setting under '''Users & Stations''' > '''Station Type''' in AlphaPro must be checked to fully support the expansion module.  
  
−
This is only necessary if any of the 6 I/O's are going to be used, and avoids conflict with the DAK keys on the extension module [[EBMDR-8]].
+
[[File:EBMDR enabled.png|thumb|500px|Enable the Expansion Module EBMDR-8|none]]
  
−
[[Image:ecpir_input_remap_alphapro.png|thumb|left|500px|Remap inputs]]
+
== Redirection of DAK keys ==
−
<br style="clear:both;" />
+
In general every user in AlphaCom has DAK tables for 20 DAK keys. When using '''more than one extension module''', one have to "borrow" DAK tables from other, unused stations.
−
 
 
−
==== Redirection of DAK keys ====
 
−
In general every user in AlphaCom has DAK tables for 20 DAK keys. Because the ECPIR can use up to 35 DAK keys with the extension modules, one have to "borrow" DAK tables from other, unused stations.
 
  
 
DAK tables are "borrowed" by pointing to the other users in the DAK table of the ECPIR. This is done by using the symbol ">", followed by the '''physical''' number of the station from where we want to use the DAK table. Any free physical number in the range 1 to 552 can be used. However, it is recommended to use higher numbers to avoid conflicts if the system is expanded in the future.  
 
DAK tables are "borrowed" by pointing to the other users in the DAK table of the ECPIR. This is done by using the symbol ">", followed by the '''physical''' number of the station from where we want to use the DAK table. Any free physical number in the range 1 to 552 can be used. However, it is recommended to use higher numbers to avoid conflicts if the system is expanded in the future.  
Line 22: Line 22:
 
Several ECPIR stations may redirect to the same DAK tables if they should use the same DAK layout.
 
Several ECPIR stations may redirect to the same DAK tables if they should use the same DAK layout.
  
−
==== LED Indication====
+
== Use as PA Panel ==
 +
The DAK keys can be used to access different zones (= group calls). The DAK keys can be configured to call the group call when pressed, and cancel the call when released.
 +
For configuration details, see: [[Group Call - PTT function]]
 +
 
 +
== LED Indications==
 
The DAK keys on the ECPIR and on the button expansion panels have two LED's each. The two LED's (red and green) are controlled using the [[IND]] command in the [[Event Handler]].
 
The DAK keys on the ECPIR and on the button expansion panels have two LED's each. The two LED's (red and green) are controlled using the [[IND]] command in the [[Event Handler]].
  
−
*Remember to '''remap''' the inputs as described previously.
+
===Incoming Call Request or Ringing Group ===
−
 
 
−
=====Call Request=====
 
 
To turn on the red LED, flashing fast, in the associated DAK key when a [[Call Request|Call Request]] is received, create this event:
 
To turn on the red LED, flashing fast, in the associated DAK key when a [[Call Request|Call Request]] is received, create this event:
  
−
[[File:CRMV CallReq.PNG|left|500px|thumb|'''Action Command''': IND %1.phy %1.dak(I%2.dir) 1 3]]
+
[[File:CRMV CallReq.PNG|left|500px|thumb]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
{{Code2|
 +
IND %1.phy %1.dak(I%2.dir) 1 3
 +
}}
  
−
=====Outgoing Conversation=====
+
===Outgoing Conversation===
 
To turn on the green LED in the associated DAK key when an outgoing call is made, create this event:
 
To turn on the green LED in the associated DAK key when an outgoing call is made, create this event:
  
−
[[File:CRMV ConvOut.PNG|left|500px|thumb|'''Action Command''': IND %1.phy %1.dak(I%2.dir) 2 1]]
+
[[File:CRMV ConvOut.PNG|left|500px|thumb]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
{{Code2|
 +
IND %1.phy %1.dak(I%2.dir) 2 1
 +
}}
  
−
=====Incoming Conversation=====
+
===Incoming Conversation===
 
To turn on the green LED in the associated DAK key when an incoming call is received, create this event:
 
To turn on the green LED in the associated DAK key when an incoming call is received, create this event:
  
−
[[File:CRMV ConvIn.PNG|left|500px|thumb|'''Action Command''': IND %1.phy %1.dak(I%2.dir) 2 1]]
+
[[File:CRMV ConvIn.PNG|left|500px|thumb]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
{{Code2|
 +
IND %1.phy %1.dak(I%2.dir) 2 1
 +
}}
  
−
=====Door Status=====
+
===Door Status===
 
An input of the IP station can be connected to a door magnet, providing indication on the DAK panel, showing if the door is open or closed.
 
An input of the IP station can be connected to a door magnet, providing indication on the DAK panel, showing if the door is open or closed.
  
Line 53: Line 64:
 
[[File:CRMV DoorStat.PNG|left|500px|thumb]]
 
[[File:CRMV DoorStat.PNG|left|500px|thumb]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
−
 
+
{{Code2|
−
'''Action Command''': <br>
+
OWN r 105
−
OWN r 105<br>
+
IND %2.phy %2.dak(I%1.dir) 1 1
−
IND %2.phy %2.dak(I%1.dir) 1 1<br>
+
}}
−
 
 
 
  105 is the directory number of the ECPIR
 
  105 is the directory number of the ECPIR
  
−
=====Station faults=====
+
===Station faults===
 
To turn on the red and green LED in the associated DAK key when a station is reported faulty, create this event:
 
To turn on the red and green LED in the associated DAK key when a station is reported faulty, create this event:
  
 
[[File:CRMV StatErr.PNG|left|500px|thumb]]
 
[[File:CRMV StatErr.PNG|left|500px|thumb]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
{{Code2|
 +
OWN r 105
 +
IND %2.phy %2.dak(I%1.dir) 1 1
 +
IND %2.phy %2.dak(I%1.dir) 2 1
 +
}}
 +
105 is the directory number of the ECPIR-3P
  
−
'''Action Command''': <br>
 
−
OWN r 105<br>
 
−
IND %2.phy %2.dak(I%1.dir) 1 1<br>
 
−
IND %2.phy %2.dak(I%1.dir) 2 1<br>
 
  
−
105 is the directory number of the ECPIR-3P
+
[[Category: Turbine Configuration]]

Latest revision as of 10:48, 3 May 2023

AI.png
DAK key numbering on the Expansion Module EBMDR-8

This article describes how to configure the AlphaCom when using the Call Panel ECPIR-3P together with the Expansion Module EBMDR-8. Up to 4 expansion modules can be attached to one ECPIR-3P.

Enable the use of the EBMDR-8 Module

The following setting under Users & Stations > Station Type in AlphaPro must be checked to fully support the expansion module.

Enable the Expansion Module EBMDR-8

Redirection of DAK keys

In general every user in AlphaCom has DAK tables for 20 DAK keys. When using more than one extension module, one have to "borrow" DAK tables from other, unused stations.

DAK tables are "borrowed" by pointing to the other users in the DAK table of the ECPIR. This is done by using the symbol ">", followed by the physical number of the station from where we want to use the DAK table. Any free physical number in the range 1 to 552 can be used. However, it is recommended to use higher numbers to avoid conflicts if the system is expanded in the future.

DAK table of the ECPIR: Redirecting to DAK tables of physical 501, 502 ... 510


The actual DAK key configuration must be entered in the DAK table of the station to which the ECPIR DAK table is pointing:

DAK 1-10 are configured in the DAK table of physical #501


Several ECPIR stations may redirect to the same DAK tables if they should use the same DAK layout.

Use as PA Panel

The DAK keys can be used to access different zones (= group calls). The DAK keys can be configured to call the group call when pressed, and cancel the call when released. For configuration details, see: Group Call - PTT function

LED Indications

The DAK keys on the ECPIR and on the button expansion panels have two LED's each. The two LED's (red and green) are controlled using the IND command in the Event Handler.

Incoming Call Request or Ringing Group

To turn on the red LED, flashing fast, in the associated DAK key when a Call Request is received, create this event:

CRMV CallReq.PNG


Action commands: 

IND %1.phy %1.dak(I%2.dir) 1 3


Outgoing Conversation

To turn on the green LED in the associated DAK key when an outgoing call is made, create this event:

CRMV ConvOut.PNG


Action commands: 

IND %1.phy %1.dak(I%2.dir) 2 1


Incoming Conversation

To turn on the green LED in the associated DAK key when an incoming call is received, create this event:

CRMV ConvIn.PNG


Action commands: 

IND %1.phy %1.dak(I%2.dir) 2 1


Door Status

An input of the IP station can be connected to a door magnet, providing indication on the DAK panel, showing if the door is open or closed.

Example:
To turn on the red LED in the associated DAK key when input 3 of the IP substation 159 is activated, create this event:

CRMV DoorStat.PNG


Action commands: 

OWN r 105
IND %2.phy %2.dak(I%1.dir) 1 1



105 is the directory number of the ECPIR

Station faults

To turn on the red and green LED in the associated DAK key when a station is reported faulty, create this event:

CRMV StatErr.PNG


Action commands: 

OWN r 105
IND %2.phy %2.dak(I%1.dir) 1 1
IND %2.phy %2.dak(I%1.dir) 2 1



105 is the directory number of the ECPIR-3P
Retrieved from "https://wiki.zenitel.com/w/index.php?title=EBMDR-8_-_Configuration&oldid=232269"