Product Core Brief
- Model: INNPM12
- Brand: ABB Bailey
- Series: INFI 90 / Symphony / Symphony Harmony
- Core Function: Network Processing Module (NPM) that provides the Cnet-to-HCU communication interface for Harmony Control Units in Bailey DCS systems.
- Product Type: Network Processing Module
- Key Specs: Cnet-to-HCU interface | paired with INNIS01 | supports hardware redundancy
- Condition: New Original / New Surplus (depending on stock)
Key Technical Specifications
- Manufacturer: ABB (Bailey INFI 90 / Symphony product line)
- Part Number:
- Product Type: Network Processing Module (NPM)
- System Compatibility: ABB INFI 90 OPEN, Symphony, Symphony Harmony DCS
- Primary Function: Works with the INNIS01 Network Interface Slave Module to provide a Harmony Control Unit interface to the Cnet communication network
- Paired Module: INNIS01 (Network Interface Slave Module)
- Communication Network: Cnet (Control Network) — high-speed serial data highway at 10 MHz or 2 MHz
- Internal Bus: Communicates with HCU modules via Controlway (cabinet-internal communication bus)
- Redundancy Support: Supports hardware redundancy with dual NIS + dual NPM configuration; standby NPM monitors primary via direct ribbon cable
- Supported Functions: process data exchange, configuration transfer, alarm/status reporting, and Cnet-wide time synchronization
- Power Requirement: +5 VDC from the Bailey MMU backplane
- Mounting Style: Standard Bailey module for MMU rack installation
- ESD Handling: Requires Bailey field static kit during maintenance
- HS Code: 853710 (electrical control panels / assemblies)
Product Introduction (No Fluff)
The ABB INNPM12 is a Network Processing Module used in Bailey INFI 90, Symphony, and Symphony Harmony DCS systems. It operates as part of the Cnet-to-HCU communication interface, working together with the INNIS01 Network Interface Slave Module to connect a Harmony Control Unit to the Cnet high-speed data highway.
The INNPM12 manages Controlway communication within the HCU cabinet and exchanges process data, configuration parameters, alarm/status information, and time synchronization data with the rest of the Cnet network. It is commonly found in Symphony HCU interface assemblies and supports hardware redundancy through a primary/standby NPM pair monitored via direct ribbon cable.
This module is distinct from the INNPM11, which serves a similar role in the INFI-NET architecture. Substitution between INNPM11 and INNPM12 should only be considered after confirming the specific network topology and HCU configuration.
QA & Testing SOP (Dynamic & Transparent)
This is a network processing module, so testing focuses on Cnet registration, NIS pairing, and HCU communication integrity.
- Incoming visual inspection: Check the module housing, edge connector, ribbon cable connector, status LEDs, and PCB for corrosion, burnt components, or prior repair marks.
- Pairing verification: Confirm the INNPM12 is correctly paired with an INNIS01 Network Interface Slave Module. A mismatched or faulty NIS will prevent Cnet communication even if the NPM is functional.
- Backplane communication test: Seat the module pair in a known-good Bailey MMU and verify power-up without fault indicators.
- Cnet registration test: Verify the HCU node registers on the Cnet network and that the module shows no fault codes on its status LEDs.
- Redundancy test (if applicable): In dual NIS/NPM configurations, verify primary/standby failover behavior to confirm seamless transfer.
- ESD-safe handling and packing: Store and ship in anti-static packaging; handle by the module frame and avoid contact with the edge connector.
Installation Pitfalls & Guide (Engineer to Engineer)
❗ INNPM12 cannot operate alone. It must be paired with an INNIS01 Network Interface Slave Module to form a complete Cnet-to-HCU interface. Installing the NPM without a valid NIS will not restore Cnet communication.
❗ Do not confuse INNPM12 with INNPM11. INNPM12 is used for Cnet-to-HCU interfaces in Symphony/Symphony Harmony systems, while INNPM11 is used for INFI-NET interfaces in INFI 90 OPEN systems. They are not interchangeable.
❗ Verify redundancy ribbon cable connection. In redundant configurations, the standby NPM monitors the primary via a direct ribbon cable. A loose or damaged ribbon cable can disable failover capability even if both modules are healthy.
❗ Check Cnet termination and topology. Communication faults attributed to the INNPM12 may actually be caused by missing Cnet termination or topology mismatches at the network level.
Replacement steps:
- Pre-install: Document current HCU node address, record active alarms, and notify operations.
- Removal: If redundant, confirm the standby NPM/NIS pair is active before removing the failed primary pair.
- Install: Seat the new INNPM12 with the correct INNIS01, reconnect the redundancy ribbon cable if applicable, and verify slot alignment.
- Power-on test: Verify LED status, confirm Cnet registration, and validate HCU communication with the network.
Technical FAQ
1. Is the INNPM12 still available? Yes, but it is a legacy Bailey module. Availability depends on inventory condition. We carry new original and new surplus stock.
2. Can INNPM12 work without INNIS01? No. The INNPM12 is a network processing module that requires the INNIS01 Network Interface Slave Module to form a complete Cnet-to-HCU interface.
3. Can INNPM11 replace INNPM12? Not directly. INNPM11 is used for INFI-NET interfaces in INFI 90 OPEN systems, while INNPM12 is used for Cnet-to-HCU interfaces in Symphony/Symphony Harmony systems. Substitution should only be considered after confirming system compatibility.
4. Does this module need firmware loading? The INNPM12 operates as part of the Bailey Cnet infrastructure. It does not require user firmware loading like a controller, but correct node addressing, Cnet configuration, and NIS pairing must be verified after installation.
5. What happens if the INNPM12 fails? The associated Harmony Control Unit may lose Cnet communication. In non-redundant configurations, this can interrupt data exchange between the HCU and the rest of the DCS network, affecting operator visibility and control.
6. What warranty do you offer? Standard warranty is 12 months unless otherwise stated. For surplus stock, warranty terms are confirmed at quotation.
INNPM12与INNIS01配对用于Cnet-to-HCU接口，需要我为您生成INNPM11（用于INFI-NET架构）的对比页面吗？
