Features:
- Runs Mark VIe application code on a 600 MHz Intel EP80579 processor.
- Uses ECC memory and QNX Neutrino for deterministic industrial control.
- Receives distributed I/O data through three dedicated IONet Ethernet interfaces.
Operates without a battery, cooling fan, or hardware jumper setup.
The General Electric IS420UCSBH1A keeps application execution separate from the distributed I/O packs, allowing every redundant controller to receive the input data it needs.
Network identity and the restored ControlST application are the central service items for General Electric IS420UCSBH1A; there are no field jumpers to copy.
Pricing and sales assistance for the General Electric IS420UCSBH1A Mark VIe UCSB standalone controller module can be requested from Apter Power.
General Electric IS420UCSBH1A Mark VIe UCSB standalone controller module Manuals, Datasheets, Links
Important Notice: Other accessories, manuals, cables, calibration data, software, etc. are not included with this equipment unless listed in the above stock item description. All prices are shown in USD.
Processing and retained resources
- CPU: 600 MHz Intel EP80579 executes the downloaded control blocks and ladder logic.
- Working memory: 256 MB DDR2 SDRAM includes error-correcting code.
- Program storage: 2 GB NAND flash holds controller software and application data.
- Operating system: QNX Neutrino provides real-time multitasking behavior.
- Non-volatile data: Supported program variables, forces, and totalizers depend on ControlST release.
Five Ethernet connections with separate duties
- ENET1: ENET1 supports ToolboxST, HMI alarms, and EGD application communication.
- ENET2: ENET2 can be assigned to supported Ethernet Modbus, OPC UA, or CDH service.
- IONet: Three IONet ports communicate only with Mark controls I/O modules and controllers.
- Cable coding: Red, black, and blue cabling preserves the intended redundant I/O topology.
- Redundancy design: Controller and I/O-network redundancy must be configured as one coordinated design.
Replacement data path
- Controller backup: Create a verified controller backup before disturbing a running unit.
- Identity record: Record the controller IP address, ControlST version, firmware, and hardware identity.
- Address transfer: Transfer the address by the approved flash-drive or COM1 procedure.
- Application restore: Restore the application only after confirming model and software compatibility.
- State comparison: Compare non-volatile variables, forces, totalizers, and controller state before release.
Panel and startup checks
- Mounting: Mount the controller directly to sheet metal in the required orientation.
- Airflow: Keep the vertical airflow path through the heat-sink fins unobstructed.
- DC supply: Verify the 28 VDC supply polarity and peak-power allowance before energizing.
- Network reconnection: Reconnect plant Ethernet and each colored IONet lead to its recorded port.
- Startup check: Confirm boot LEDs, time synchronization, network health, and application state.