Difference between revisions of "RCO - Remote Control Output"
From Zenitel Wiki
(→Software) |
|||
Line 128: | Line 128: | ||
[[Category: AlphaCom features]] | [[Category: AlphaCom features]] | ||
− | |||
[[Category:Additional equipment]] | [[Category:Additional equipment]] |
Revision as of 12:58, 3 November 2016
The Remote Control Output RCO’s are used to operate relays for control of external equipment.
Relay outputs are typically used for:
- Door opening
- PA control
- Call indication
- Queue indication
- Keying of mobile radio transmitter
- CCTV interface
Contents
Devices supporting RCOs
RCO outputs are available on a number of devices:
(x): When the ATLB-12 board is used in AlphaCom XE7 only four RCOs are available
Logical RCOs
There are several ways to control RCOs. Most common is to use Logical RCOs operated by the RCO command.
- The RCO command operates a Logical RCO
- Each logical RCO must be mapped to a Device or Station, and to a Pin Number
- The AlphaCom XE software supports up to 500 logical RCOs.
- The operation of the logical RCOs is configured from AlphaPro, in the Event Handler window.
Mapping of RCOs
The mapping of RCOs is done from AlphaPro, Exchange & System -> RCO window where the logical RCO is assigned to a physical address.
The physical address is given as:
- Device + Pin Number, or by
- Station + Pin Number.
RCO Number: | The "logical" number of the RCO. Use this number in the RCO command. |
Description: | Any text. This information is stored in the AlphaPro database only, and is not sent to the exchange. |
RCO Type: | Device: The AlphaCom (i.e. ASLT or ATLB-12 board) or RIO unit Station: IP Station, Turbine or IPARIO |
Device: |
|
Pin Number: |
|
- RCO 1-138 are by default mapped to the internal RCOs in the AlphaCom, i.e. device 65 - pin 1 to device 65 - pin 138
- Mappings for all other RCOs must be configured manually
- The RCOs can be used freely within the system, e.g. an event on one station can operate an RCO located on a different station.
- The exchange always keeps track of the state of an output in case the device becomes faulty. When a faulty device becomes OK again, the exchange will restore the current RCO state.
Configuration examples
The Event Handler is used to configure the behavior of the RCOs. Here are some examples:
- Door opening and Code lock
- Call indication
- CCTV integration using relays
- CCTV control by relays (RCO) when using Call Request
- PA Interface
- IND command: Direct operation of an output on an IP station or Turbine station. This command does not use logical RCO, so there is no need for RCO mapping.
- Example: IND 14 5 1 1 ON On physical number 14, output 5, turn ON (Assuming a Turbine station)
ACDP commands:
- $X (EXECUTE_COMMAND): Sends a command string to a remote exchange to be executed there. Requires RCO mapping.
- Example: @4 $X "RCO 2 ON": Turn on RCO 2 in node 4
- $SLRC (SET LOGICAL RCO): Set or clear a logical RCO. Requires RCO mapping.
- Example: $SLRC W5 U1 W25: Turn RCO #5 ON for 2.5 seconds
- $SET_IPRCO: Direct operation of an output on an IP station, Turbine station or IPARIO. This command does not use logical RCO, so there is no need for RCO mapping.
- Example: $SET_IPRCO L234 U3 U1: On station number 234, turn output number 3 ON
- %prco: The %prco macro is used in the Event Handler to check state of a physical output on an IP-ARIO.
- Example: %prco(5,1): Return the state of output 1 on IPARIO station 5
Software
- AMC 10.50 or later to control RCOs in slave modules. Earlier AMC versions support RCOs in master module only (pin 1 - 138).
- AMC 10.04: Additional parameter to pulse the RCO ('RCO 12 ON 20' to generate a 2.0 sec pulse on RCO 12)
- AMC 07.40 or later to control RCOs in an AlphaNet installation.