Description
Note: Many products are not yet listed. Please contact us for more product information. Our supply channels are constantly expanding, and we currently have 20 stable shared supply channels. Please confirm the model, product, price, and all other necessary information with customer service before placing an order. We offer new, refurbished, and used products, and prices are adjusted according to the year of the item you require.
3. Key Technical Specifications
Do not order against this table alone. The UCSA build, firmware revision, and port configuration must be verified against the label on your existing module and the OEM datasheet.
| Parameter | Value |
|---|---|
| Model | IS220UCSAH1AK |
| Brand | GE |
| Product Family | Speedtronic Mark VIe |
| Module Type | UCSA controller / control module |
| Processor | Verify with OEM datasheet — confirm on the module label |
| Memory (RAM / Flash) | Verify with OEM datasheet |
| IONet Ports | 2 x RJ45, 100 Mbps full-duplex (verify on your build) |
| Additional Ports | Verify — USB or serial maintenance port varies by build |
| Redundancy Support | Verify — confirm simplex, duplex, or TMR configuration |
| Configuration Software | GE ToolboxST / ControlST — verify supported version |
| Pack Supply | 24V DC nominal via the I/O pack rack — verify range and current draw |
| Power Consumption | Verify with OEM datasheet |
| Isolation | Verify — field side to logic side |
| Status Indicators | Power, run, fault, IONet link/activity — verify LED arrangement |
| Hot Swap | Supported in redundant configurations only — follow the OEM procedure |
| Operating Temperature | –30 °C to +65 °C (typical — verify for your cabinet) |
| Storage Temperature | –40 °C to +85 °C (typical — verify) |
| Humidity | 5% – 95% RH, non-condensing |
| Certifications | UL, CE, ATEX / Class I Div 2 where marked — verify on the unit label |
4. Product Introduction
The GE IS220UCSAH1AK is a UCSA controller module for the Speedtronic Mark VIe turbine control platform. It executes the control application, coordinates the I/O packs over the IONet network, and manages communication with the operator interface. The H1AK suffix identifies a specific build and firmware revision; verify the full string on your existing module.
The engineering value is the integration of the controller and the I/O network in one module. The UCSA handles the control logic and the network traffic, so the I/O packs can be distributed across the turbine hall without a separate controller rack. In a redundant configuration, a second UCSA provides backup control if the primary faults. Verify the firmware revision and the ToolboxST project version before you swap.
IS220UCSAH1AK
IS220UCSAH1AK
5. Application Scenarios & Field Experience
Part 1 – Narrative Paragraph
The failure that hurts most on a Mark VIe controller is not a dead module — it is a module that runs but loses synchronization with its redundant partner. The primary keeps executing, the turbine stays online, and the backup sits out of step. I have seen that on a combined cycle plant where the two UCSA modules had different firmware revisions and nobody noticed until a forced switchover test. When you replace a UCSA in a redundant pair, verify the firmware revision and the synchronization status before you return the unit to service.
Part 2 – Numbered List (Application Scenarios)
- Gas Turbine Control – Auxiliary and Small Frame Units – The UCSA executes the start-up sequencing, fuel control, and protection logic for smaller turbines or auxiliary systems. It coordinates the I/O packs over the IONet network.
- Steam Turbine Control – Balance of Plant Interface – Used where the Mark VIe system controls the turbine and the associated balance-of-plant equipment. The controller manages the I/O packs that interface with the field devices.
- Combined Cycle Plants – Redundant Controller Pair – In a redundant configuration, two UCSA modules run in parallel and vote on the output. A forced switchover test verifies the backup is synchronized.
- Industrial Turbines – Mechanical Drive Control – The controller manages the turbine speed and load for a mechanical drive application, such as a compressor driver. The IONet network connects the controller to the I/O packs.
Part 3 – Short Field Story
A combined cycle plant had a gas turbine that would not start after a scheduled outage. The maintenance team had replaced the backup UCSA during the outage and the system would not synchronize. We asked them to check the firmware revision on both controllers. The replacement had a newer firmware revision than the primary, and the two would not pair. The plant rolled the replacement firmware back to match the primary, and the system synchronized on the next power-up. The hardware had been fine — the firmware revision was the problem.
6. Standard Operating Procedure (SOP) for Quality Control
- Visual & Origin Inspection – Verify the GE marking, IS220UCSAH1AK model string, and date code. Inspect the RJ45 ports and the rear connector for bent pins or damage. Reject modules with cracked connectors or moisture ingress.
- Revision and Firmware Documentation – Read and photograph the full model string, firmware revision, and pack ID. That record ships with the module so you can compare it against the unit you are replacing.
- Rack Fit Verification – Seat each module in a Mark VIe test rack and confirm the connector engages fully and the retention mechanism holds.
- Power-Up Self-Test – Power the module in a live rack and verify it completes its boot sequence and the controller recognizes the module type without a fault.
- IONet Communication Test – Verify both Ethernet ports at 100 Mbps full duplex. Run a continuous exchange loop and log dropped frames.
- Redundancy Synchronization Test – Where a redundant pair is ordered, verify the two controllers synchronize and a forced switchover completes without data loss.
- Control Output Verification – Load a test control application and verify the controller executes the logic and produces the expected output on the I/O network.
- ESD-Safe Packaging – Anti-static film, conductive foam, protected connectors, double-wall carton with static warning labels.
7. Frequently Asked Questions (FAQ)
Q1: Will this UCSA module work in my Mark VIe rack without a firmware change?
A: Only if the firmware revision matches or is compatible with your ToolboxST project. The controller firmware governs the project download and the redundancy pairing. A mismatched revision can initialize and still fail to synchronize. Read the firmware revision off your existing module and compare it to the replacement before you order.
Q2: Can I replace just one controller in a redundant pair?
A: Yes, but the two controllers must match in model and firmware revision, or the pair will not synchronize. Before you order, read the firmware revision off both existing controllers and send it to us. If we cannot match the revision, plan to replace both and re-download the application.
Q3: What is the warranty on this module?
A: We offer a 12-month warranty from the ship date. It covers processor failure, IONet communication failure, and connector failure under normal operating conditions. It does not cover damage from hot-swapping the module in a simplex configuration, bent pins from forced insertion, or ESD damage from handling without a wrist strap. We test every module in a live Mark VIe rack before it ships.
Q4: Do you have this exact model in stock?
A: Mark VIe inventory moves quickly, and stock varies by revision. Confirm availability before you plan an outage. If we are out of the revision you need, we will tell you what we actually have rather than quote a date we cannot hold.
Q5: Any installation pitfalls I should watch for?
A: Four. First, power down the rack before inserting or removing the module in a simplex configuration — hot-swap is only supported in redundant systems. Second, record the firmware revision and the pack ID from the old module before you remove it. Third, verify the controller firmware matches the ToolboxST project version before you power up. Fourth, in a redundant pair, verify the synchronization status before you return the unit to service. A controller that powers up is not necessarily synchronized with its partner or executing the correct application.
