Difference between revisions of "RCO - Remote Control Output"
From Zenitel Wiki
(→Additional Information) |
|||
| Line 13: | Line 13: | ||
=== Additional Information === | === 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. | * For internal RCOs (ASLT/ATLB), the device address is 65, and the pin number is the same as the [[Physical number]] of stations. | ||
| − | * Mappings for the internal RCOs in the master are [[Autoload|autoloaded]]. Mappings for RCOs in slave [[module|modules]] | + | * Mappings for the internal RCOs in the master are [[Autoload|autoloaded]]. Mappings for RCOs in slave [[module|modules]], [[RIO]] units and IP stations must be manually programmed. |
* From AMC version 10.43; RCOs in slave module can be used. (AMC versions 10.xx in slaves need not be upgraded, only master need 10.43) | * From AMC version 10.43; RCOs in slave module can be used. (AMC versions 10.xx in slaves need not be upgraded, only master need 10.43) | ||
* Prior to AMC version 10.43: In a multi-module system, the RCOs must be physically connected to the Master module. The outputs are freely programmable to be used anywhere within the multi-module system. If you need more than the 138 available outputs, you must use the [[RIO]] unit for connection. | * Prior to AMC version 10.43: In a multi-module system, the RCOs must be physically connected to the Master module. The outputs are freely programmable to be used anywhere within the multi-module system. If you need more than the 138 available outputs, you must use the [[RIO]] unit for connection. | ||
| + | * IP stations also have RCIs. See [[IP Station Configuration]] for programming. | ||
* In an AlphaNet installation you can control RCOs in a remote exchange. | * In an AlphaNet installation you can control RCOs in a remote exchange. | ||
Revision as of 11:23, 6 May 2008
The AlphaCom system provides 6 Remote Control Outputs (RCOs) per ASLT/ATLB board, giving a maximum of 138 outputs for control of remote equipment in one basic exchange. The outputs can be used freely within the whole exchange, regardless of physical connections of the stations.
In AlphaPro, there is a RCO mapping table, where all RCOs are given a logical number, and the physical address is entered. The physical address is given as device + pin-number. The Event Handler is used to program the behavior of the RCOs defined in the RCO table.
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.
- 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.
- From AMC version 10.43; RCOs in slave module can be used. (AMC versions 10.xx in slaves need not be upgraded, only master need 10.43)
- Prior to AMC version 10.43: In a multi-module system, the RCOs must be physically connected to the Master module. The outputs are freely programmable to be used anywhere within the multi-module system. If you need more than the 138 available outputs, you must use the RIO unit for connection.
- IP stations also have RCIs. See IP Station Configuration for programming.
- In an AlphaNet installation you can control RCOs in a remote exchange.
Software
- AMC 07.40 or later to control RCOs in an AlphaNet installation.