ABB
CI520V1 3BSE012869R1
$1600
In Stock
T/T
Xiamen
| Availability: | |
|---|---|
| Quantity: | |
The CI520V1 is the physical and logical carrier of the Advant Fieldbus 100 communication interface. It plays the dual and critical role of a "communication gateway" and "bus manager" within the Advant Controller 400 series (including AC410 and AC450). It is not a standalone device but a communication submodule inserted into a carrier module within the controller subrack.
Hardware Entity: As a hardware module, the CI520V1 provides the electrical and protocol conversion interface between the controller backplane (Futurebus+) and the external Advant Fieldbus 100 physical medium (e.g., cable).
Software Interface: At the controller system software level, its functionality is configured, managed, and monitored through a specific data element named "AdvantFieldbus 100." Users and engineers define the CI520's operational mode and the behavior of the bus network it manages by configuring various parameters within this data element.
2.1 Core Functions
The core function of the CI520V1 module is to establish and maintain bidirectional, real-time data communication between the Advant Controller 400 series controllers and various nodes (stations) connected to the Advant Fieldbus 100 network. Specifically, this includes:
Protocol Handling: Implements the proprietary Advant Fieldbus 100 communication protocol stack, handling data frame encapsulation, transmission, reception, verification, and error handling.
Medium Access Control: Manages access to the shared communication medium by multiple stations on the bus, ensuring real-time and deterministic communication.
Data Routing: Establishes mapping relationships between the controller's internal data space (data elements) and remote data points on the fieldbus, enabling transparent data transmission.
Network Management: As the master station on the bus (default configuration), it is responsible for bus initialization, time synchronization, node diagnosis, and status monitoring.
2.2 Technical Characteristics
Master/Slave Mode Configuration: Via the MASTER terminal, the CI520V1 can be configured as a Master or Slave. In the vast majority of configurations, the CI520V1 operates as the master, controlling the bus communication cycle and scheduling. This is its default operating mode.
Time Synchronization: Via the TIMESYNC terminal, the CI520V1 can (and typically does) broadcast high-precision time synchronization messages to all slave stations across the entire Advant Fieldbus 100 network. This ensures that devices distributed across the network share a unified time reference, which is crucial for Sequence of Events (SOE) recording and coordinated control. It is important to note that only one station on the same physical bus should have this function enabled.
Single/Redundant Medium Support: Via the CABLE_I terminal (CABLE connection), it can be configured for a single cable (S) or redundant dual cables (R). Redundant medium configuration significantly enhances communication link availability; if one cable fails, the system can automatically switch to the backup cable without interrupting communication.
Network Addressing: Each CI520V1 instance is uniquely identified and managed within the system through two key parameters:
Bus Number (BUSNO): A number (1-255) unique within the controller, used to refer to that specific Advant Fieldbus 100 physical network during data configuration. For example, when specifying the address for a remote I/O module's data element, one must indicate which bus (with which BUSNO) it is connected to. A value of zero is invalid or indicates an inactive bus.
Station Number (STNNO): Specifies the logical address of the Advant Controller itself on that physical Advant Fieldbus 100 network (1-80). This is akin to a node address on the network. The default value is 80, suitable for single-controller systems. If multiple controllers are connected to the same bus, each must be assigned a unique station number.
Diagnostics and Monitoring: The CI520 provides comprehensive online diagnostic functions, feeding back real-time status on module and bus health through multiple status output terminals in its data element. This is key to achieving high availability and fast maintenance.
In the software world of Advant OCS, hardware functionality is abstracted and managed through the software concept of "Data Elements." The CI520's functionality is fully embodied in the data element of type "AdvantFieldbus 100."
3.1 Data Element Structure
This data element contains multiple "terminals," each representing a configurable parameter or a piece of status information. They are primarily categorized as follows:
Address Terminals (BUS, STATION, POS_I, SPOS_I): These are predefined by the system and used to precisely locate the physical position of the CI520 module within the controller hardware framework (e.g., which rack, slot, and submodule position). This ensures the system software can correctly identify and access the hardware.
Control and Parameter Terminals: Configured by the user or engineer, defining the CI520's behavior and bus attributes.
IMPL: Implementation flag. When set to "1," the system includes and activates this module in its configuration during initialization or runtime. Setting it to "0" logically removes the module; it remains inactive even if physically present. Used for system construction and modification.
SERVICE: Service status. Similar to IMPL but more focused on "temporary disable/enable" during online maintenance. It can be toggled while the system is running, facilitating hot maintenance of the module or bus.
TYPE: Fixed as "CI520," identifying the module type.
BUSNO and STNNO: As mentioned earlier, define logical network identification and controller node address.
MASTER, TIMESYNC, CABLE_I: Define core operating modes.
Status and Diagnostic Terminals: Updated automatically by the system for user monitoring.
WARNING: Warning flag. Indicates non-fatal errors or abnormal conditions, such as degraded communication quality, backup cable failure, etc. The system may continue to run but requires attention.
ERR: Error flag. Indicates fatal hardware or configuration errors, such as module missing, severe failure, configuration conflict, etc. The bus communication function may be disabled at this point.
ERR_I1, ERR_I2: Specifically indicate error status for cable 1 or cable 2 in a redundant configuration.
DIAG_I: Diagnostic code. Provides more detailed information about the error or warning, e.g., "IE" might indicate an internal module error or not found, "PE" might indicate a physical layer (cable) error. This is key for in-depth troubleshooting.
3.2 Address Space and System Integration
The configuration of the CI520 directly impacts the data organization of the entire system. When creating a data element for a remote device (e.g., an analog input module of an S800 I/O station) connected via Advant Fieldbus 100, its address configuration must reference the BUSNO defined by the CI520. For instance, the data element of an S800 I/O module will include address terminals such as BUS (set to the CI520's BUSNO), STATION (the station number of the I/O station itself), and POSITION (the slot number of the module within the station). This hierarchical addressing method (Bus -> Station -> Module -> Channel) enables the Advant Controller to manage thousands of I/O points distributed across the network clearly and efficiently.
4.1 Module Setup Procedure
Setting up the CI520 is accomplished by configuring the "AdvantFieldbus 100" data element, following a clear procedure:
Implementation: Set the IMPL terminal to 1. During system initialization, the controller will configure and start the CI520 module based on the parameters (BUSNO, STNNO, MASTER, etc.) in this element. If IMPL is changed from 0 to 1 in a running system, it will also trigger dynamic configuration and startup of the module, attempting to establish connections with other stations on the bus.
Disabling: Use the SERVICE terminal for temporary enabling/disabling operations, facilitating online maintenance and testing without complex system reconfiguration.
Parameterization: Carefully set key parameters like BUSNO, STNNO, MASTER, TIMESYNC, CABLE_I before putting the system into operation (or while IMPL=0). Special attention is required: BUSNO cannot be changed after the system enters operational mode, so its uniqueness must be ensured during planning.
Diagnostics: Continuously monitor diagnostic terminals such as WARNING, ERR, DIAG_I during system operation to understand the health status of the module and bus.
4.2 Typical Diagnostics and Fault Handling
The diagnostic information integrated into the data element is a powerful tool for rapid problem localization. The attached documentation provides several typical examples:
Condition: CI520 module missing or faulty
Symptoms: ERR = 1, DIAG_I = "IE"
Action: Check and re-insert the module, or replace the module.
Condition: In redundant configuration, Cable 1 faulty
Symptoms: WARNING = 1, ERR_I1 = 1, ERR_I2 = 0, DIAG_I = "PE"
Action: Check and replace the first communication cable.
Condition: In redundant configuration, Cable 2 faulty
Symptoms: WARNING = 1, ERR_I1 = 0, ERR_I2 = 1, DIAG_I = "PE"
Action: Check and replace the second communication cable.
With these clear indications, maintenance personnel can quickly determine whether the problem lies with the module itself, its configuration, or the physical wiring, enabling targeted actions and significantly reducing Mean Time To Repair (MTTR).
5.1 Building a Distributed System Architecture
The CI520 is a key component in realizing the "decentralized control, centralized management" philosophy of control systems. Through Advant Fieldbus 100 and the CI520, users can distribute large numbers of I/O modules from central control cabinets to remote cabinets closer to field devices, thereby:
Saving significant amounts of signal cabling, reducing installation costs and complexity.
Mitigating interference and signal attenuation issues associated with long-distance analog signal transmission, improving signal quality.
Increasing system configuration flexibility, facilitating plant expansion and modification.
5.2 Achieving High Reliability and Deterministic Communication
The redundant medium support and time synchronization capabilities of the CI520 enable it to meet the needs of high-reliability applications, such as in power, petrochemical, and metallurgy industries. Its communication mechanism ensures deterministic data transmission, capable of meeting the strict requirements for communication cycle times in fast control loops.
5.3 Simplified Engineering and Maintenance
Abstracting complex communication hardware functionality into a unified data element interface makes engineering configuration work standardized and intuitive. Engineers do not need in-depth knowledge of underlying hardware details; they simply fill in the various terminals of the data element in an engineering station (like Advant Station 100/500 Series Engineering Stations) to complete the configuration. Integrated diagnostic functions also provide great convenience for maintenance throughout the lifecycle.
5.4 Relationship with System Evolution
It is worth noting that the documentation also mentions its evolved model, CI522. The CI522 is an enhanced version of the CI520, specifically providing support for fully redundant Advant Fieldbus 100 communication. This means it not only supports redundant cables but can also be configured with redundant communication interface modules themselves (Submodule I and II), achieving complete redundancy in the communication path, suitable for applications with extremely stringent availability requirements.
The CI520V1 is the physical and logical carrier of the Advant Fieldbus 100 communication interface. It plays the dual and critical role of a "communication gateway" and "bus manager" within the Advant Controller 400 series (including AC410 and AC450). It is not a standalone device but a communication submodule inserted into a carrier module within the controller subrack.
Hardware Entity: As a hardware module, the CI520V1 provides the electrical and protocol conversion interface between the controller backplane (Futurebus+) and the external Advant Fieldbus 100 physical medium (e.g., cable).
Software Interface: At the controller system software level, its functionality is configured, managed, and monitored through a specific data element named "AdvantFieldbus 100." Users and engineers define the CI520's operational mode and the behavior of the bus network it manages by configuring various parameters within this data element.
2.1 Core Functions
The core function of the CI520V1 module is to establish and maintain bidirectional, real-time data communication between the Advant Controller 400 series controllers and various nodes (stations) connected to the Advant Fieldbus 100 network. Specifically, this includes:
Protocol Handling: Implements the proprietary Advant Fieldbus 100 communication protocol stack, handling data frame encapsulation, transmission, reception, verification, and error handling.
Medium Access Control: Manages access to the shared communication medium by multiple stations on the bus, ensuring real-time and deterministic communication.
Data Routing: Establishes mapping relationships between the controller's internal data space (data elements) and remote data points on the fieldbus, enabling transparent data transmission.
Network Management: As the master station on the bus (default configuration), it is responsible for bus initialization, time synchronization, node diagnosis, and status monitoring.
2.2 Technical Characteristics
Master/Slave Mode Configuration: Via the MASTER terminal, the CI520V1 can be configured as a Master or Slave. In the vast majority of configurations, the CI520V1 operates as the master, controlling the bus communication cycle and scheduling. This is its default operating mode.
Time Synchronization: Via the TIMESYNC terminal, the CI520V1 can (and typically does) broadcast high-precision time synchronization messages to all slave stations across the entire Advant Fieldbus 100 network. This ensures that devices distributed across the network share a unified time reference, which is crucial for Sequence of Events (SOE) recording and coordinated control. It is important to note that only one station on the same physical bus should have this function enabled.
Single/Redundant Medium Support: Via the CABLE_I terminal (CABLE connection), it can be configured for a single cable (S) or redundant dual cables (R). Redundant medium configuration significantly enhances communication link availability; if one cable fails, the system can automatically switch to the backup cable without interrupting communication.
Network Addressing: Each CI520V1 instance is uniquely identified and managed within the system through two key parameters:
Bus Number (BUSNO): A number (1-255) unique within the controller, used to refer to that specific Advant Fieldbus 100 physical network during data configuration. For example, when specifying the address for a remote I/O module's data element, one must indicate which bus (with which BUSNO) it is connected to. A value of zero is invalid or indicates an inactive bus.
Station Number (STNNO): Specifies the logical address of the Advant Controller itself on that physical Advant Fieldbus 100 network (1-80). This is akin to a node address on the network. The default value is 80, suitable for single-controller systems. If multiple controllers are connected to the same bus, each must be assigned a unique station number.
Diagnostics and Monitoring: The CI520 provides comprehensive online diagnostic functions, feeding back real-time status on module and bus health through multiple status output terminals in its data element. This is key to achieving high availability and fast maintenance.
In the software world of Advant OCS, hardware functionality is abstracted and managed through the software concept of "Data Elements." The CI520's functionality is fully embodied in the data element of type "AdvantFieldbus 100."
3.1 Data Element Structure
This data element contains multiple "terminals," each representing a configurable parameter or a piece of status information. They are primarily categorized as follows:
Address Terminals (BUS, STATION, POS_I, SPOS_I): These are predefined by the system and used to precisely locate the physical position of the CI520 module within the controller hardware framework (e.g., which rack, slot, and submodule position). This ensures the system software can correctly identify and access the hardware.
Control and Parameter Terminals: Configured by the user or engineer, defining the CI520's behavior and bus attributes.
IMPL: Implementation flag. When set to "1," the system includes and activates this module in its configuration during initialization or runtime. Setting it to "0" logically removes the module; it remains inactive even if physically present. Used for system construction and modification.
SERVICE: Service status. Similar to IMPL but more focused on "temporary disable/enable" during online maintenance. It can be toggled while the system is running, facilitating hot maintenance of the module or bus.
TYPE: Fixed as "CI520," identifying the module type.
BUSNO and STNNO: As mentioned earlier, define logical network identification and controller node address.
MASTER, TIMESYNC, CABLE_I: Define core operating modes.
Status and Diagnostic Terminals: Updated automatically by the system for user monitoring.
WARNING: Warning flag. Indicates non-fatal errors or abnormal conditions, such as degraded communication quality, backup cable failure, etc. The system may continue to run but requires attention.
ERR: Error flag. Indicates fatal hardware or configuration errors, such as module missing, severe failure, configuration conflict, etc. The bus communication function may be disabled at this point.
ERR_I1, ERR_I2: Specifically indicate error status for cable 1 or cable 2 in a redundant configuration.
DIAG_I: Diagnostic code. Provides more detailed information about the error or warning, e.g., "IE" might indicate an internal module error or not found, "PE" might indicate a physical layer (cable) error. This is key for in-depth troubleshooting.
3.2 Address Space and System Integration
The configuration of the CI520 directly impacts the data organization of the entire system. When creating a data element for a remote device (e.g., an analog input module of an S800 I/O station) connected via Advant Fieldbus 100, its address configuration must reference the BUSNO defined by the CI520. For instance, the data element of an S800 I/O module will include address terminals such as BUS (set to the CI520's BUSNO), STATION (the station number of the I/O station itself), and POSITION (the slot number of the module within the station). This hierarchical addressing method (Bus -> Station -> Module -> Channel) enables the Advant Controller to manage thousands of I/O points distributed across the network clearly and efficiently.
4.1 Module Setup Procedure
Setting up the CI520 is accomplished by configuring the "AdvantFieldbus 100" data element, following a clear procedure:
Implementation: Set the IMPL terminal to 1. During system initialization, the controller will configure and start the CI520 module based on the parameters (BUSNO, STNNO, MASTER, etc.) in this element. If IMPL is changed from 0 to 1 in a running system, it will also trigger dynamic configuration and startup of the module, attempting to establish connections with other stations on the bus.
Disabling: Use the SERVICE terminal for temporary enabling/disabling operations, facilitating online maintenance and testing without complex system reconfiguration.
Parameterization: Carefully set key parameters like BUSNO, STNNO, MASTER, TIMESYNC, CABLE_I before putting the system into operation (or while IMPL=0). Special attention is required: BUSNO cannot be changed after the system enters operational mode, so its uniqueness must be ensured during planning.
Diagnostics: Continuously monitor diagnostic terminals such as WARNING, ERR, DIAG_I during system operation to understand the health status of the module and bus.
4.2 Typical Diagnostics and Fault Handling
The diagnostic information integrated into the data element is a powerful tool for rapid problem localization. The attached documentation provides several typical examples:
Condition: CI520 module missing or faulty
Symptoms: ERR = 1, DIAG_I = "IE"
Action: Check and re-insert the module, or replace the module.
Condition: In redundant configuration, Cable 1 faulty
Symptoms: WARNING = 1, ERR_I1 = 1, ERR_I2 = 0, DIAG_I = "PE"
Action: Check and replace the first communication cable.
Condition: In redundant configuration, Cable 2 faulty
Symptoms: WARNING = 1, ERR_I1 = 0, ERR_I2 = 1, DIAG_I = "PE"
Action: Check and replace the second communication cable.
With these clear indications, maintenance personnel can quickly determine whether the problem lies with the module itself, its configuration, or the physical wiring, enabling targeted actions and significantly reducing Mean Time To Repair (MTTR).
5.1 Building a Distributed System Architecture
The CI520 is a key component in realizing the "decentralized control, centralized management" philosophy of control systems. Through Advant Fieldbus 100 and the CI520, users can distribute large numbers of I/O modules from central control cabinets to remote cabinets closer to field devices, thereby:
Saving significant amounts of signal cabling, reducing installation costs and complexity.
Mitigating interference and signal attenuation issues associated with long-distance analog signal transmission, improving signal quality.
Increasing system configuration flexibility, facilitating plant expansion and modification.
5.2 Achieving High Reliability and Deterministic Communication
The redundant medium support and time synchronization capabilities of the CI520 enable it to meet the needs of high-reliability applications, such as in power, petrochemical, and metallurgy industries. Its communication mechanism ensures deterministic data transmission, capable of meeting the strict requirements for communication cycle times in fast control loops.
5.3 Simplified Engineering and Maintenance
Abstracting complex communication hardware functionality into a unified data element interface makes engineering configuration work standardized and intuitive. Engineers do not need in-depth knowledge of underlying hardware details; they simply fill in the various terminals of the data element in an engineering station (like Advant Station 100/500 Series Engineering Stations) to complete the configuration. Integrated diagnostic functions also provide great convenience for maintenance throughout the lifecycle.
5.4 Relationship with System Evolution
It is worth noting that the documentation also mentions its evolved model, CI522. The CI522 is an enhanced version of the CI520, specifically providing support for fully redundant Advant Fieldbus 100 communication. This means it not only supports redundant cables but can also be configured with redundant communication interface modules themselves (Submodule I and II), achieving complete redundancy in the communication path, suitable for applications with extremely stringent availability requirements.