RCO - Remote Control Output

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:

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.

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" 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 device ID 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.

The Event Handler is used to configure the behavior of the RCOs. Here are some examples:

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

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.