GE IS200ISBBG1A | Mark VIe Bus Bridge Module

Description

Product Introduction

You’ve got two turbine decks, 200 meters apart. The control room is in the middle. You could run fiber between them—but then you’ve got a single cable that, if it gets cut, takes down both racks. The GE IS200ISBBG1A is the smarter play. This Mark VIe bus bridge lets you create independent bus segments—one for each deck—and bridge them at the controller level. If one segment loses power or a cable gets damaged, the other stays alive. You don’t lose the whole system.

The “ISBB” designation tells you this is a bus bridge—not a bus adapter, not an I/O module. It’s a pass-through device with isolation and segmentation. It has two bus segments, each with a redundant A/B port pair running at 100 Mbps. The propagation delay across the bridge is 2 ms, so it’s transparent to the controller’s data scan. The isolation between segments is 1,500 V—you can use it to separate electrical zones, like a noisy switchgear area from a clean control room. It’s a niche module, but when you need it, nothing else does the job.

Key Technical Specifications

Quality Inspection Process (SOP Transparency)

The ISBB is a bridge—if it fails, you lose one or both segments. Our 28-point inspection verifies both sides independently and the isolation between them.

Incoming Verification. OEM packing slip matched to GE’s serial database. We log the serial and photograph the anti-static bag before cutting. The holographic GE label gets a UV check. The PCB edge must read “–ISBBG1A” clearly.

Visual Inspection. Magnifying lamp, full board scan. The two segment sides are visually distinct—we check for any signs of rework or component damage. The isolation barrier (a row of optocouplers or transformers) must be intact. The four RJ45 connectors (two per segment) show zero wear. The 96-pin backplane connector must show zero wear.

Live Functional Test. Mark VIe test rack with a working CPU and two remote I/O rack simulators—one on each segment. ToolboxST v5.3 logs the data.

• Segment A test: Connect remote rack simulator to Segment A, disable Segment B. Verify data exchange at 100 Mbps. Throughput >95 Mbps.
• Segment B test: Swap to Segment B—same throughput test.
• Bridging test: Connect simulators to both segments simultaneously. Verify the CPU sees both sets of racks and data is exchanged correctly.
• Isolation test: Inject a fault on Segment A (disconnect cable)—Segment B must remain active. Then inject a fault on Segment B—Segment A must remain active.
• Redundancy test per segment: For each segment, test A/B port switchover—<10 ms.
• Propagation delay: Measure the time from a data packet entering Segment A to it appearing on Segment B (and vice versa)—must be <2.5 ms.
• 24-hour soak: Both segments active with continuous data exchange. Log any errors—zero tolerance.

Electrical Parameters. Insulation resistance: 500 VDC via Megger MIT420, >10 MΩ between segments and backplane. Ground continuity: <0.1 Ω. We also test isolation between the two segments—>10 MΩ at 500 V. Skip hi-pot on the bus ports.

Firmware Verification. Read the FPGA firmware via ToolboxST—verify the checksum. The bridging logic is in firmware; a mismatch can cause data corruption.

Final QC & Packaging. The QC report includes throughput per segment, redundancy timing, propagation delay, isolation test data, and a photo. Into an anti-static bag with desiccant, 2″ foam, double-wall carton. “QC Passed” label with date.

Field Replacement Pitfalls

The ISBB is a bridge—it sits between your control racks and your remote I/O. I’ve seen these mistakes at power plants across the US.

Segment Isolation—Don’t Cross the Streams. The whole point of the ISBB is to keep segments isolated. If you connect Segment A’s cable to a switch that also has a connection to Segment B’s switch, you’ve defeated the isolation. One site in Florida did exactly that—they used the same network switch for both segments, and a ground loop developed that caused data corruption on both buses. The fix: keep the physical cabling separate. Segment A uses its own switches, Segment B uses its own switches. Never bridge them at the Ethernet level.

Propagation Delay—It Adds Up. The ISBB adds 2 ms of propagation delay. If you chain two bridges together (Segment A → Bridge 1 → Bridge 2 → Segment C), you’ve added 4 ms. The Mark VIe controller’s scan time is typically 20–50 ms, so 4 ms is fine—but if you’re running a fast loop (10 ms), that extra delay can push you over the edge. One site in Texas had three bridges in series for a large distributed system—6 ms of delay—and their fast pressure control loop started oscillating. The fix: use a star topology instead of a daisy chain, or adjust the loop timing. Document your topology and calculate the total delay.

Power Budget. The ISBB draws 12 W. If you’re using it in a rack with multiple comms modules, the power adds up. I’ve seen a rack with two ISBBs (24 W), two ISBAs (20 W), and a CPU (25 W)—total 69 W, fine. But they added two analog modules and a discrete pack, pushing it to 135 W—close to the 150 W limit. At startup, the 5 V rail sagged and the ISBBs started resetting. Leave 20% headroom.

Firmware Mismatch—Segment-Specific. The ISBB uses the same firmware image as the ISBA—but the bridging logic is enabled by a configuration bit in ToolboxST. If you install an ISBB without setting that bit, it acts like a standard ISBA—no bridging. One site in Ohio installed an ISBB, configured it as an ISBA, and wondered why the remote racks on Segment B weren’t visible. The fix: check the configuration in ToolboxST before you commission.

Ground Potential Differences—The Isolation Handles It, But… The ISBB has 1,500 V isolation between segments. That’s enough to handle most ground potential differences. But if you have a massive fault (say, a lightning strike that drives one segment’s ground to 2,000 V relative to the other), the isolation can fail. One site in Florida had a lightning strike on the turbine deck—the ISBB’s isolation was breached, and both segments went down. The fix: install surge suppressors on the bus cables. GE’s manual recommends this for exposed cabling.

ESD. The PHY chips are CMOS. I watched a tech handle a bare ISBB on a dry day in Arizona—he discharged through an RJ45 connector, and the A port on Segment A stopped working. Strap up.

New Original vs. Refurbished: Why It Matters

The ISBB is a bridge—refurbished ones often have worn PHY chips or degraded isolation.

What “New Original (New Surplus)” means. This IS200ISBBG1A came from GE’s factory, never mounted. The PHY chips are fresh. The isolation barrier is intact. We break the seal only for testing.

Refurbished risk in plain terms. The isolation barrier—typically a bank of transformers or optocouplers—degrades with age and thermal stress. A refurbished unit may have been exposed to transients that stressed the barrier. I’ve tested refurbished ISBB units that passed the throughput test but failed the isolation test—the resistance between segments dropped below 1 MΩ at 500 V. That means the isolation was compromised. Failure rate on refurbished comms modules runs 4× higher than new, based on our service data.

Real cost of a refurbished failure. Let’s say a refurbished ISBB fails the isolation test in the field—a ground fault on Segment A propagates to Segment B. Both segments go down. All remote I/O is lost. The turbine trips. Lost generation: 30,000. The refurbished module saved you 1,500. The outage cost you 20× that.

What we provide as proof. For every IS200ISBBG1A we ship: a photo of the OEM packing slip, serial traceability to GE’s records, a full test report that includes isolation resistance, throughput per segment, propagation delay, redundancy timing, and a sealed anti-static bag.

Pricing context. Our price sits 30–50% above refurbished, 20–30% below GE’s current list price. The delta covers our sourcing, our isolation testing, and a 12-month warranty.

Performance Benchmarks & Test Results

Data from our Mark VIe test rack (ambient 45 °C, supply +5.0 VDC, ToolboxST v5.3, two remote I/O simulators).

• Port throughput—Segment A: 97.2 Mbps, zero CRC errors over 24 hours.
• Port throughput—Segment B: 97.1 Mbps, zero CRC errors.
• Propagation delay: Segment A to Segment B: 2.1 ms. Segment B to Segment A: 2.0 ms. Both under the 2.5 ms spec.
• Redundancy switchover—Segment A: 8.2 ms. Segment B: 8.5 ms. Both under 10 ms.
• Fault isolation: Fault on Segment A—Segment B stayed active. Fault on Segment B—Segment A stayed active. No data loss on the active segment.
• Isolation resistance: >100 MΩ at 500 V between segments—well above the 10 MΩ spec.
• Thermal performance: At 60 °C ambient with both segments active, the FPGA ran at 68 °C—under the 85 °C rating.
• Reliability estimate: MIL-HDBK-217F gives a demonstrated MTBF of 50,000 hours at 40 °C—that’s 5.7 years. Refurbished units with degraded isolation show a demonstrated MTBF around 10,000 hours—the isolation barrier fails prematurely.

140AII33010 SCHNEISER
140AII33000 SCHNEISER
SCHNEISER 1400DM69000
SCHNEISER 1400DM39000