Description
ABB Bailey INNPM01 Network Processing Module
Product Introduction
In an older ABB Bailey INFI 90 control system, network processing is handled by dedicated hardware rather than by a modern Ethernet switch or standard PLC communication card. The INNPM01 Network Processing Module forms part of the Process Control Unit interface and works with the INNIS01/INNIS11 Network Interface Slave Module. Its job is to process communications between the INFI-NET side and Controlway-based modules within the PCU. ABB documentation identifies INNPM01 as a supported legacy control-network component.
The module uses 1 Mbaud Controlway communication and 83.3 kbaud module-bus communication, with 256 kbytes of ROM and 512 kbytes of RAM. It occupies one slot in the standard INFI 90 module mounting unit and requires +5 VDC at 2 A, with 10 W nominal power consumption. For a legacy DCS repair or migration project, firmware revision and the companion INNIS module should be checked before treating an INNPM01 as a direct replacement.
Key Technical Specifications
| Parameter | Specification |
|---|---|
| Product Model | INNPM01 |
| Manufacturer | ABB Bailey |
| System Family | INFI 90 / INFI-NET |
| Product Type | Network Processing Module |
| Primary Function | INFI-NET / Controlway network processing |
| ROM | 256 kbytes |
| RAM | 512 kbytes |
| Controlway Communication Rate | 1 Mbaud |
| Module Bus Communication Rate | 83.3 kbaud |
| Supply Voltage | +5 VDC |
| Supply Current | 2 A |
| Nominal Power | 10 W |
| Mounting | One slot in standard INFI 90 module mounting unit |
| Associated Network Module | INNIS01 / INNIS11 |
| Approx. Weight | 0.45–0.50 kg |
| Application | ABB Bailey INFI 90 Process Control Unit |
The published technical documentation consistently identifies the memory, +5 VDC supply, communication rates, and single-slot mounting arrangement.
Application Scenarios & Pain Points
1. INFI 90 Process Control Units
The INNPM01 is used within an INFI 90 PCU network architecture. It is paired with the appropriate Network Interface Slave Module rather than operating as a standalone modern Ethernet interface.
INNPM01
2. Legacy DCS Network Maintenance
For plants maintaining an existing Bailey INFI 90 installation, an can be relevant when troubleshooting communication faults involving the PCU interface, Controlway modules, or the INFI-NET connection.
3. DCS Migration Projects
ABB’s own evolution-planning material identifies as an existing Control Network component and lists INNPM12 as the evolution path, with replacement occurring as failures occur. That makes the exact module family important when planning phased migration rather than simply replacing hardware one-for-one.
4. PCU Communication Troubleshooting
A communication problem should not automatically be attributed to the . The INNIS module, termination hardware, Controlway wiring, module mounting unit, power supply, and firmware configuration can all be involved. The sits inside that larger architecture.
Related Products
- ABB Bailey INNIS01 — Network Interface Slave Module that works with as part of the Process Control Unit interface.
- ABB Bailey INNIS11 — later Network Interface Slave Module used with the INNPM family.
- ABB Bailey INNPM11 — related Network Processing Module variant; verify firmware and system revision before substitution.
- ABB Bailey INNPM12 — evolution-path Network Processing Module identified by ABB for systems using /11.
- ABB Bailey NTCL01 — Communication Termination Unit associated with the INNIS01 network interface.
- ABB Bailey NICL01 — communication termination hardware used within the PCU interface arrangement.
- ABB Bailey NKMP01/NKMP11 — redundancy cable family associated with -to- arrangements.
Compatibility warning: These components belong to a tightly defined INFI 90 architecture. Similar-looking part numbers should not be treated as interchangeable without checking the system generation, firmware, network architecture, and associated termination equipment.
Engineer’s Guide — Field Pitfalls to Avoid
1. Do not confuse with INNIS01
This is the most common identification problem. is the Network Processing Module, while INNIS01 is the Network Interface Slave Module. The two work together but perform different functions.
2. Firmware matters
Some procurement references specifically request the required firmware version when sourcing an . For an operational DCS, matching the hardware part number alone is not sufficient. Record the existing firmware revision before approving a replacement.
3. Check the complete PCU architecture
The is only one component of the communication path. Check the associated INNIS module, termination unit, cables, mounting unit, Controlway modules, and network configuration before replacing hardware.
4. Do not assume modern Ethernet compatibility
The documented communication rates are 1 Mbaud Controlway and 83.3 kbaud module bus. This is legacy INFI 90 architecture, not an Ethernet-based network interface.
5. Verify the power supply before commissioning
The module is specified for +5 VDC at 2 A, with approximately 10 W nominal consumption. A marginal backplane power supply can produce communication symptoms that look like processor or network faults.
6. Watch the evolution path
ABB’s migration documentation identifies /11 as existing components and INNPM12 as an evolution path. If the plant is already planning INFI 90 modernization, procurement should consider the larger migration strategy rather than accumulating unsupported legacy spares indefinitely.
FAQ
What is the ABB Bailey ?
The is an INFI 90 Network Processing Module. It forms part of the Process Control Unit interface and handles network processing associated with the INFI-NET and Controlway architecture.
What does the communicate with?
The module is associated with the or INNIS11 Network Interface Slave Module and communicates with Controlway-based modules within the PCU.
What is the communication speed?
The published specifications give 1 Mbaud for Controlway and 83.3 kbaud for the module bus.
What power does the require?
The documented requirement is +5 VDC at 2 A, with 10 W nominal power consumption.
How much memory does have?
The documented configuration contains 256 kbytes of ROM and 512 kbytes of RAM.
Can be replaced by INNPM12?
ABB identifies INNPM12 as an evolution path for systems using /11, but that should not be interpreted as an unconditional plug-and-play replacement. The actual INFI 90 architecture, firmware, companion network interface, and migration requirements need to be checked first.
What should procurement verify before buying an ?
Match the complete designation, hardware revision, firmware revision, physical board condition, and associated INNIS module. For used or refurbished inventory, inspect the edge connector and board for corrosion, contamination, damaged components, or previous repair work. Published specifications establish the design characteristics—not the condition of a particular spare.
