Actions

RCO - Remote Control Output

From Zenitel Wiki

Revision as of 12:40, 5 May 2022 by Asle (talk | contribs)
AI.png
Examples of RCO usage

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


Devices supporting RCOs

RCO outputs are available on a number of devices:

Device # of RCO's Comment Hardware required
AlphaCom XE26 138 6 RCOs per ASLT card or ATLB-12 card MRBD relay board + PDB Power Distribution Board
AlphaCom XE20 102 6 RCOs per ASLT card or ATLB-12 card MRBD relay board
AlphaCom XE7 12 Need ASLT or ATLB-12 in position 1 and 2 (x) MRBD relay board
AlphaCom XE1 0 RCOs not available in the server. Use external device, e.g. TKIS-2, TKIE-2, IP-LCM, IPARIO External device
IPARIO unit (IP) 8 Remote outputs over IP network IPARIO unit
IP-LCM 15 Provides 8 high power relays and 1 signal relay 6 more relays using MRBD relay board
IP Substation board (PCB 8022) 2 One relay on connector P3, pin 3/4 The second output is a logical signal. Transistor + relay required
IP Flush Master/IP OR station (PCB 8024) 2 One relay on connector P3, pin 3/4 The second output is a logical signal. Transistor + relay required
Turbine Compact/TKIS-2 kit 7 One relay included Use MRBD relay board if more than 1 relay is needed
Turbine Industry/TKIE-1 kit 10 Two relays included Use TA-10 connection board if high power relays are needed.
The MRBD relay board can also be used if more relays are needed
ENA Amplifier 6 Each output has a relay (NO, NC and COM) in parallel with a 24VDC signal No additional hardware required
RIO unit (analog) 18 Remote outputs over RS232/485 MRBD relay board

(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 ICX-AlphaCom (and AlphaCom XE) 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:

  • Station + Pin Number, or by
  • Device + Pin Number.
Note icon "Device" is not supported in the ICX-AlphaCom server. Here you should always use "Station".


AlphaPro: Exchange & System > RCO window


RCO Number: The "logical" number of the RCO. Use this number in the RCO command.
Description: Any descriptive text. This information is stored in the AlphaPro database only, and is not sent to the exchange.
RCO Type: Device: (AlphaCom XE servers only) The AlphaCom (i.e. ASLT or ATLB-12 board) or RIO unit

Station: IP Station, Turbine, IPARIO, IP-LCM or ENA amplifier

Device:
  • 65 = AlphaCom
  • 1-64 = RIO unit adress
  • When 'RCO Type' is set to Station, enter the physical number of the IP Station, Turbine station or the IPARIO
Pin Number:
  • AlphaCom: Pin 1 - 552 (the same as the physical number of stations)
  • RIO unit: Pin 1 - 18
  • IPARIO unit: Pin 1 - 8
  • IP Station: Pin 1 - 2 (the relay is pin 1)
  • Turbine compact: Pin 1 - 7 (the relay is pin 7)
  • Turbine Industry: Pin 1 - 10 (the relays are pin 7-10)
  • ENA Amplifier: Pin 1 - 6
  • IP-LCM: Pin 1 - 7 (the TKIS-2 relay is pin 7), pin 17-24 (external relays)


  • 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:


Other RCO related commands

Built-In Action Commands:

  • 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


Event Handler macros:

  • %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.
Retrieved from "https://wiki.zenitel.com/w/index.php?title=RCO_-_Remote_Control_Output&oldid=227986"