Description
GE 369B1860G0028 | MPU51 Nexus Communication Control Module | Nexus OnCore
Key Technical Specifications
| Parameter | Specification |
|---|---|
| Manufacturer | GE / GE Vernova |
| Model | MPU51 |
| Part Number | 369B1860G0028 |
| Product Type | Nexus Communication Control Module |
| System | Nexus / OnCore |
| Processor | Intel Atom N450, 1.66 GHz |
| L2 Cache | 512 KB |
| RAM | 1 GB DDR2 667/800 MHz |
| Flash | 2 GB |
| Operating System | QNX |
| Ethernet Ports | 5 × RJ-45 |
| Ethernet Speed | 100 Mbps |
| RS-485 Ports | 8 isolated ports |
| Serial Baud Rates | 9600 / 14400 / 19200 / 38400 bps |
| Power Input | Dual redundant 24 VDC ±10% |
| Maximum Power Consumption | Approx. 15 W |
| Modbus Support | Yes |
| Application | Nexus communication and data exchange |
GE’s Nexus documentation identifies 369B1860G0028 as MPU51 and describes it as a communication control module with five 10/100 Mbps Ethernet ports, eight isolated RS-485 ports, and dual 24 VDC inputs.
The same documentation specifies an Intel Atom N450 processor, 1 GB DDR2 RAM, 2 GB flash storage, QNX operating system, and configurable serial communication rates of 9,600 through 38,400 bps.
Product Introduction
GE 369B1860G0028 MPU51
The GE 369B1860G0028, designated MPU51, is a communication control module in the Nexus control system. Its job is considerably different from a conventional PLC CPU: the MPU51 provides the Ethernet and isolated RS-485 communication resources used for Nexus data exchange and third-party device integration. GE documentation also identifies as a Nexus Controller in its certified module list.
The hardware provides five Ethernet interfaces and eight isolated RS-485 serial ports. Modbus communication capacity depends on the selected serial baud rate and the amount of analog and digital data being exchanged, so the serial port count alone should not be interpreted as eight independent high-capacity control networks.
369B1860G0028
Application Scenarios & Field Pitfalls — Engineer’s Perspective
Engineering Pain Point
The is typically encountered where a Nexus control system needs multiple serial and Ethernet communication paths. A failed can therefore appear as a communications failure across several connected subsystems rather than as a simple controller fault.
Typical Applications
- Nexus control-system communication — Handles Ethernet and serial communications within the Nexus architecture.
- Modbus device integration — Eight isolated RS-485 ports provide serial connectivity for compatible external equipment.
- Multi-network Ethernet architecture — Five 100 Mbps RJ-45 ports support the system’s Ethernet communication requirements.
- Power-generation control systems — Used as part of GE Nexus/OnCore control architectures and associated turbine/process-control installations.
Technical Pitfalls to Avoid
- Do not call 369B1860G0028 a generic PLC CPU.
The strongest GE documentation identifies it specifically as / Nexus Communication Control Module. Some current listings call it a “processor module” or generic controller, which loses the distinction between the communication role and other Nexus processing modules. - Do not confuse with MPU50 or MPU52.
GE’s module documentation maps:- MPU50 — 369B1860G0026
- — 369B1860G0028
- MPU52 — 369B1860G0029
These are separate Nexus controller models.
- Check the complete power arrangement.
uses dual redundant 24 VDC inputs ±10%. A single failed supply, distribution path, fuse, or power-swapping circuit can produce symptoms that look like an hardware failure. - Check serial isolation and wiring.
The eight RS-485 interfaces are isolated. Replacing the module without documenting which serial port serves which external device can make commissioning difficult, especially where multiple Modbus networks are installed. - Verify software and configuration before replacement.
runs QNX and contains flash storage. A replacement hardware unit should not automatically be assumed to contain the same application configuration, firmware, communication mapping, or system parameters as the failed module. GE documentation notes that software is required for normal operation of Nexus system components. - Do not approve unsupported IEC 61850/DNP3 claims.
Some current listings assign power-substation communication protocols and specifications to 369B1860G0028 without documentation support. The Nexus manual specifically documents Ethernet, isolated RS-485 and Modbus communication for ; those are the safer specifications to use for procurement.
Related Products
- GE MPU50 / 369B1860G0026 — Nexus controller with a different system role and part number.
- GE MPU52 / 369B1860G0029 — Related Nexus controller; not automatically interchangeable with .
- GE MDP10 / 369B1860G0024 — PROFIBUS-DP Master communication module with two DP ports.
- GE MDP11 / 369B1860G0025 — PROFIBUS-DP Master communication module with one DP port.
- GE MVP50 / 369B1848G5007 — 16-channel Nexus digital output module.
- GE MVP51 / 369B1848G5008 — Triple-redundant LVDT valve-position control module.
- GE MVP52 / 369B1848G5009 — Nexus valve-position control module.
- GE MSP50 / 369B1851G5002 — Nexus speed measurement and protection module.
- GE MSP51 / 369B1851G5003 — Nexus speed measurement and logic protection module.
Procurement Check
For 369B1860G0028, the correct technical description should read:
GE — Nexus Communication Control Module — 5 × 100 Mbps Ethernet + 8 × isolated RS-485 + dual redundant 24 VDC.
Before approving a replacement, verify the designation, 369B1860G0028 part number, Nexus system revision, firmware/software image, serial-port assignments, Ethernet topology, and dual-24-VDC power arrangement.
One correction worth emphasizing: 369B1860G0028 should not be marketed as a generic Mark VIe control board. GE/Baker Hughes documentation directly maps this part number to the , and that is the identification I would use on a technical procurement record.
