RCI - Remote Control Input

Examples of RCI usage

A Remote Control Input (RCI) is triggered by an external potential-free contact.

Inputs

Typical external triggers can be:

• Fire and gas alarm systems
• Temperature detectors
• Doors sensors
• Lift status
• Alarm buttons

An RCI signal can be received by a number of devices:

Device	# of RCI's
AlphaCom XE20/XE26	6
AlphaCom XE7/XE1	2
IPARIO unit (IP)	8
RIO unit (analog)	8
IP Substation	3
IP Flush Master	3
IP Turbine station	6

Physical RCI connections in AlphaCom XE

RCI inputs in an AlphaCom XE20 and XE26

RCI inputs in an AlphaCom XE7

RCI inputs in an AlphaCom XE1 (top lid removed)

Actions

The set-up for the RCI input and the actions you want it to activate is very flexible. An RCI can activate almost any function in the exchange by using action commands, either Built-In Action Commands or Data Protocol Commands. The configuration of the RCI's is done with the AlphaPro programming tool.

Some examples of features that can be activated:

• Dispatch prerecorded voice messages to stations and PA system (fire alarm etc.)
• Show status information on a DAK48 panel, e.g. door open/closed
• Send text message to a station or a group of stations, e.g. temperature warning
• Set up group calls, audio program or conferences
• Activate Call Forwarding
• Control Remote Control Output

etc.

Configuration

Inputs from AlphaCom, IPARIO and RIO

In AlphaPro there is an RCI table, where the physical address of the input is entered, along with the desired actions. The physical address is given as device + pin-number.

The RCI table supports up to 140 inputs.

• For internal RCIs in the AlphaCom, the device address is 65-68, and the pin number is 1-6.
• Internal pin number 8 is the temperature alarm.
• Mappings for the internal RCI's are autoloaded. Mappings for external RCI's (Slave modules, RIO's or IPARIO) must be manually programmed.

	RCI Type	Device/Station physical Number	Pin Number
AlphaCom XE20/XE26	Device	65 - 68	1 - 6
AlphaCom XE7/XE1	Device	65 - 68	1 - 2
IPARIO unit (IP)	Station	1 - 552	1 - 8
RIO unit (analog)	Device	1 - 64	1 - 8

Example configuration:

RCI configuration window. Here input 2 will trigger voice alarm message number 3 to group 1, and turn on the RCO 5

Inputs from IP Stations

Inputs from IP Stations must be configured using the Event Handler.

	RCI Type	Station Physical Number (Event Owner)	Input number	Sub-Event (= DAK key)
IP Substation	Station	1 - 552	1 - 3	1 - 3
IP Flush Master and IP OR	Station	1 - 552	1 - 3	11 - 13 (*)
IP Turbine station	Station	1 - 552	1 - 6	11 - 16 (**)

Important notes:
(*): When set as station type "Master station" in AlphaPro, the inputs are mapped as DAK 11, 12 and 13. When set as "CRM" the inputs are mapped as 251, 252 and 253.
(**): The DAK and SubEvent number depends on the AMC software version:

• AMC 11.2.3.9 and lower: DAK and SubEvent number is 1 - 6
• AMC 11.2.3.10: DAK and SubEvent number is 101 - 106
• AMC 11.2.3.11 and higher: DAK and SubEvent number is 11 - 16

In the Event Handler, use the following parameters:

• Event type: 30 - Station DAK as RCI
• Subevent: The input number according to the table above
• When Change to: ON = Input goes on. OFF = input goes off.

Example configuration:

Event Handler configuration window. Here Input 2 (DAK 2) will trigger alarm message 3 to group 1, and turn on RCO 5

See also:

• Disable alarm input feature
• Enable alarm input feature

Software

• AMC 10.50 or later supports RCI's in slave module (devices 66-68). (The software in the slave modules must also be upgraded)