Processes network messages
Executes the communication work required between Cnet and controller modules in the Harmony control unit.
ABB Symphony Harmony · Rack Communications
ABB INNPM12 Cnet Network Processing Module
The processing half of a Cnet-to-HCU communication interface. INNPM12 works with INNIS01 to move system messages between the control network and Harmony controller modules, with documented support for redundant interface arrangements and legacy INFI 90 migration.
TypeNetwork processing module
SystemSymphony Harmony / INFI 90
FocusCnet-to-HCU messaging
BrandABB Bailey
Talk to a spare-parts specialistMiya Zheng
Email for quotationsales@amikon.cn
WhatsApp+86 180 2077 6792
04 / Product Introduction
The processing stage between Cnet and the controller rack
For an installed spare check, confirm the INNPM12 marking, the adjacent INNIS01 network interface and the node's redundancy arrangement. Together, the two modules form the documented communication interface.
Works with INNIS01
The network interface module supplies the Cnet connection; INNPM12 handles the processing side of the interface.
Supports redundant nodes
ABB documents primary and redundant interface configurations for higher communication availability.
Control networkCnet / INFI-NET
→
Interface pairINNIS01 + INNPM12
→
Controller sideControlway / module bus
05 / Technical Specifications
Confirmed electrical, communication and environmental data
| Model | INNPM12 |
|---|---|
| Product type | Network processing module |
| Interface function | Cnet-to-HCU communication processing when paired with INNIS01 |
| Read-only memory | 512 KB ROM |
| Random-access memory | 512 KB RAM |
| Power requirement | +5 VDC at 2 A |
| Power consumption | 10 W |
| Controlway communication rate | 1 Mbaud |
| Module-bus communication rate | 83.3 kbaud |
| Mounting | One slot in a Harmony module mounting unit |
| Operating temperature | 0 to 70°C (32 to 158°F) |
| Relative humidity | 5% to 90% up to 55°C; 5% to 40% above 55°C, noncondensing |
| Altitude | Sea level to 3 km (1.86 mi) |
| Air quality | Noncorrosive |
| Hazardous-location approval | FM approved for Class I, Division 2, Groups A, B, C and D |
| Ordinary-location approval | CSA certified for ordinary locations |
02 / Communication Architecture
One interface, two clearly separated jobs
The INNIS01 connects to Cnet and the INNPM12 provides the network-processing function. This separation helps maintenance teams isolate network-side and controller-side faults.
Message path
- System messages arrive through the INNIS01 network interface.
- INNPM12 processes the messages for controller modules in the HCU.
- Controller-side traffic uses Controlway and the module bus at their documented rates.
03 / Compatibility & Replacement
Documented migration paths for older communication nodes
ABB identifies INNPM12 as the evolution path for earlier network processor revisions and documents a Plant Loop migration arrangement.
INNPM01 / INNPM11
ABB evolution planning identifies INNPM12 as the replacement network processor for these earlier models.
Plant Loop interface migration
INNIS01 plus INNPM12 in Plant Loop mode can replace the functions of INLIM03 plus INBIM02.
Pair-level validation
Check both modules, node mode, addresses and redundancy assignment before changing an installed communication pair.
04 / Diagnostics & Redundancy
Use the node status to narrow the fault before swapping hardware
A loss of controller-network communication can originate in the Cnet interface, the processor, backplane power or node configuration. Record the status of both modules before removal.
1Compare primary and redundant sidesA healthy partner can distinguish a module-specific fault from a wider network or rack condition.
2Check INNIS01 statusThe processor depends on its network-interface companion for the Cnet path.
3Verify rack power and seatingThe module requires +5 VDC and a sound MMU connection.
4Preserve addressing and modeRecord node, module and Plant Loop mode settings used by the installed interface.
06 / Applications & Fault Scenarios
Where INNPM12 failures create operational risk
The module sits in a critical communication path, so symptoms often appear outside the card itself.
HCU disappears from the network
Controller data and status are no longer visible across Cnet even though local controller functions may still be running.
Intermittent node communication
A marginal module, backplane contact, power condition or companion interface can produce repeated loss and recovery.
Legacy interface migration
A site is replacing an INNPM01/11 or retiring an older Plant Loop interface during a planned outage.
07 / Official Documentation
INNPM12 manufacturer documents
| Manufacturer | Document | Number / Version | Official link |
|---|---|---|---|
| ABB | Harmony Rack Communications — Data Sheet | WBPEEUD250001C1, Rev. C1 | View document |
| ABB | Harmony Rack Communications — Overview | WBPEEUS250002C1, Rev. C1 | View document |
08 / Supply & RFQ
Inspection, packing and quotation support
Amikon Service
InspectionPart identity and agreed test scope
Export packingAnti-static and impact-protective
DOA supportPrompt review with photos and evidence
Warranty & returnsTerms confirmed on the quotation
09 / FAQ
INNPM12 questions from buyers and maintenance teams
What is ABB INNPM12 used for?
It is the network-processing module in a Cnet-to-HCU interface and works with INNIS01 to exchange messages between the control network and controller modules.
Which companion module does ABB INNPM12 require?
The documented network-interface companion is INNIS01. The two modules divide the network connection and message-processing functions.
Can ABB INNPM12 be used in a redundant communication node?
Yes. ABB documents redundant Cnet-to-HCU interface arrangements; the installed primary/redundant assignment and node configuration must be preserved.
What communication rates apply to ABB INNPM12?
Controlway operates at 1 Mbaud and the module bus at 83.3 kbaud.
Does ABB INNPM12 replace earlier network processors?
ABB evolution material identifies it as the migration replacement for INNPM01 and INNPM11.
What should be provided for an ABB INNPM12 quotation?
Send the part number, quantity, destination, required date and machine or system model. A photo of both installed communication modules is useful for checking the interface pair.
10 / Multi-brand Spare Parts Also Requested
Independent procurement references
These models are separate sourcing references, not substitutes for INNPM12. Compatibility and stock must be confirmed independently.
210N2272972-01268-6A-IP20311637312863-A01319828-A01332985-C013G3MX2-A4007-ZV13IF722.93IF761.93IF766.93IF771.93IF772.93IF779.9
No interchangeability, migration or replacement relationship is implied by this list.
