Difference between revisions of "ECPIR-3P"
From Zenitel Wiki
(→Installation) |
(→Configuration) |
||
Line 44: | Line 44: | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
− | + | === 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. | 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 | + | 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. |
− | [[File:DAK Redirect2.PNG|left|thumb|500px|DAK table of the ECPIR | + | [[File:DAK Redirect2.PNG|left|thumb|500px|DAK table of the ECPIR: Redirecting to DAK tables of physical 501, 502 ... 510]] |
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
− | The actual DAK key configuration must be entered in the DAK table of the station to which the ECPIR | + | The actual DAK key configuration must be entered in the DAK table of the station to which the ECPIR DAK table is pointing: |
[[File:DAK Redirect.PNG|thumb|left|500px|DAK 1-10 are configured in the DAK table of physical #501]] | [[File:DAK Redirect.PNG|thumb|left|500px|DAK 1-10 are configured in the DAK table of physical #501]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
+ | Several ECPIR stations may redirect to the same DAK tables if they should use the same DAK layout. | ||
+ | === LED Indication==== | ||
+ | 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. | |
− | + | ===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 | ||
[[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|'''Action Command''': IND %1.phy %1.dak(I%2.dir) 1 3]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
− | + | ===Outgoing Conversation=== | |
− | To turn on the green | + | 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|'''Action Command''': IND %1.phy %1.dak(I%2.dir) 2 1]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
− | + | ===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 | ||
[[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|'''Action Command''': IND %1.phy %1.dak(I%2.dir) 2 1]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
− | + | ===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 | ||
Example: <br> | Example: <br> | ||
− | To turn on the red | + | To turn on the red LED in the associated DAK key when input 3 of the IP substation 159 is activated, create this event: |
[[File:CRMV DoorStat.PNG|left|500px|thumb]] | [[File:CRMV DoorStat.PNG|left|500px|thumb]] | ||
Line 99: | Line 94: | ||
IND %2.phy %2.dak(I%1.dir) 1 1<br> | 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 |
− | |||
− | |||
− | To turn on the red and green | + | ===Station faults=== |
+ | 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]] |
Revision as of 11:31, 17 October 2016
The ECPIR-3P call panel is developed for console mounting. The call panel features three fully programmable buttons.
Contents
- 1 Highlights
- 2 InterCom connections
- 3 Starting up
- 4 Configuration
- 5 Advanced Network Settings
- 6 Software Upgrade
- 7 Station Indication LEDs
- 8 Restore Factory Defaults
- 9 Board Connections
- 10 ECPIR Dimensions & Mounting Instructions
- 11 Additional Documentation on Zenitel.com
- 12 Additional Configuration
- 13 Related Articles
Highlights
- Network call panel for console mounting
- Compatible with AlphaCom and Exigo systems
- Three programmable buttons with individual labels and status indicators
- Separate PTT button
- Optional button protection covers
- Indicators for power, call and fault
InterCom connections
Starting up
Configuration
Advanced Network Settings
Software Upgrade
Station Indication LEDs
Restore Factory Defaults
Board Connections
ECPIR Dimensions & Mounting Instructions
Additional Documentation on Zenitel.com
Additional Configuration
Remap input 1-6 as DAK 101 - 106 (Default 11-16)
The following setting under Station Type in AlphaPro needs to be checked when using the button 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.
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.
The actual DAK key configuration must be entered in the DAK table of the station to which the ECPIR DAK table is pointing:
Several ECPIR stations may redirect to the same DAK tables if they should use the same DAK layout.
LED Indication=
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.
Call Request
To turn on the red LED, flashing fast, in the associated DAK key when a Call Request is received, create this event:
Outgoing Conversation
To turn on the green LED in the associated DAK key when an outgoing call is made, create this event:
Incoming Conversation
To turn on the green LED in the associated DAK key when an incoming call is received, create this event:
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:
Action Command:
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:
Action Command:
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
Related Accessories
100px | ||||
EBMDR-8 | MB-30G | EMMAR-1H | EMBR-1 | EMBR-2 |