Actions

Difference between revisions of "RCO - Remote Control Output"

From Zenitel Wiki

(Software)
Line 33: Line 33:
 
* 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.50 or later to control RCOs in slave modules. Earlier AMC versions support RCOs in master module only (pin 1 - 138).
 
* AMC 07.40 or later to control RCOs in an AlphaNet installation.  
 
* AMC 07.40 or later to control RCOs in an AlphaNet installation.  
 +
 +
=== Related articles ===
 +
[[ATLB in AlphaCom E7 - RCO's]]
  
  

Revision as of 22:35, 2 September 2009

The Remote Control Output RCO is used for the operation of relays.

RCOs are available from:

  • AlphaCom exchange via the line boards ASLT or ATLB
  • External RIO unit
  • IP stations

The AlphaCom system provides 6 RCO's per ASLT/ATLB board, giving up to 138 outputs for control of remote equipment in one AlphaCom E26 exchange. The RCO outputs must be connected to MRBD relay board(s).

The RIO unit provides 18 RCOs. The outputs must be connected to MRBD relay board(s).

The IP station has one RCO. The relay is included with the station. See IP Station Configuration for programming.

There are 500 logical RCOs. In AlphaPro there is a RCO mapping table where the logical RCO is assigned to a physical address. The physical address is given as device + pin-number or by station + pin number. The RCO command is used in the Event Handler to program the behavior of the RCOs defined in the RCO table.

The outputs can be used freely within the whole exchange, regardless of physical connections of the stations.

You can link an unlimited number of remote control outputs to one station. The outputs can be used simultaneously and programmed individually for any type of equipment using a closed or open contact for control. For example you can have a door station with remote control of the door lock combined with control of an external loudspeaker or a video camera.

The RCO set-up meets the following requirements:

  • Possibility to assign an unlimited number of remote control outputs (RCOs) per station.
  • A RCO can be switched ON by one event, and OFF by quite a different event at some later time.
  • A RCO can be configured to operate only when two specific stations are in conversation. This can be used, for example to control video cameras by relays. Another application is as access restriction, for example by allowing door opening only when certain stations are in conversation with a door.
  • It’s allowed to control one output by many events. 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 RCOs. The logical RCOs keeps track of the RCO’s state. Logical RCOs are assigned a physical device/pin number in a separate table that also will allow additional kinds of RCO hardware in the future.

Additional Information

  • For internal RCOs (ASLT/ATLB), the device address is 65, and the pin number is the same as the Physical number of stations, 1 - 552.
  • When the ATLB board is used in AlphaCom E7 only four RCO's are available
  • Mappings for the internal RCOs in the master are autoloaded. Mappings for RCOs in slave modules, RIO units and IP stations must be manually programmed.
  • In an AlphaNet installation you can control RCOs in a remote exchange.

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 07.40 or later to control RCOs in an AlphaNet installation.

Related articles

ATLB in AlphaCom E7 - RCO's