IS420UCSBH1A - UCSB Controller Module

Functional Description

Overview of IS420UCSBH1A

IS420UCSBH1A is a UCSB Controller Module developed by GE. UCSB controllers are self-contained computers that execute application-specific control system logic. The UCSB controller does not host any application I/O, unlike traditional controllers that do. Furthermore, all I/O networks are connected to each controller, providing it with all input data. If a controller is powered down for maintenance or repair, the hardware and software architecture ensures that no single point of application input is lost.

Advantages of IS420UCSBH1A

• Single module
• Built-in power supply
• No need for jumper settings
• No battery
• No fan
• Smaller panel footprint
• Flash memory can be easily updated

The UCSB controller is installed in a panel and communicates with I/O packs via on-board I/O network (IONet) interfaces. IONet is a private special-purpose Ethernet that supports only Mark controls I/O modules and controllers.

Characteristics

• Microprocessor: 600 MHz Intel EP80579
• Memory: 256 MB DDR2 SDRAM with error-correcting code (ECC), Flash-backed SRAM, NAND flash size is 2 gigabytes
• Operating System: QNX Neutrino
• Weight: 2.4 lbs

Installation

Installation

The UCSB controller is housed in a single module that attaches to the panel sheet metal directly.

• The UCSB controller should be mounted to the panel with unobstructed vertical air flow through the fins.

Operation

Operation

The controller is pre-loaded with application-specific software. It is capable of running rungs or blocks. Minor changes to the control software can be made online without restarting the system.

• The IEEE 1588 protocol is used to synchronize the clocks of the I/O packs and controllers to within 100 microseconds via the R, S, and T IONets.
• External data is transferred to and from the controller's control system database via the R, S, and T IONets.
• Process inputs and outputs to I/O modules are included.

This also includes the following in a dual system:

• The designated controller's internal state values and initialization information
• The status and synchronization information from both controllers

This also includes the following in a Triple Modular Redundant (TMR) system:

• Internal state values for voting and status, as well as synchronization information from all three controllers
• Data from the designated controller for initialization