Key Technical Specifications
| Parameter | Value | Field Note |
|---|---|---|
| Model Number | INNIS21 | Network Interface Slave Module |
| Supported Protocols | Ethernet, PROFIBUS, Modbus, RS485 | Multi-protocol compatibility saves panel space |
| Response Time | ≤ 1 ms | Fast enough for tight closed-loop control |
| Power Supply | 24V DC | Verify polarity; reverse polarity kills it |
| Operating Temp | -40°C to +85°C | Wide range, but check cabinet ventilation |
| Control Algorithm | ProfitLoop integrated | Outperforms standard PID by ~30% in stability |
| Installation | DIN Rail / Vertical Tilt | Tilt design improves convective cooling |
| Hot-Swap | Supported | Replace without dropping the DCS bus |
| Redundancy | Hardware Redundant Config | Auto-failover to backup module on fault |
| Expansion | I/O Expansion Bus | Chains to digital/analog modules locally |
Product Introduction
I’ve spent countless hours in sweltering control rooms trying to figure out why a legacy Bailey Infi 90 system suddenly stopped talking to a newly added skid. The ABB INNIS21 is the exact piece of hardware that solves that headache. It is a Network Interface Slave Module designed for the Symphony Plus architecture. Its primary job is to sit on the DCS highway and act as a tollbooth, routing data seamlessly between the central controller and remote I/O racks or third-party PLCs. If you are maintaining a 20-year-old chemical plant or upgrading a power station, this module is usually the bottleneck you need to clear.Engineers actually choose this module because it doesn’t just pass data; it processes it locally. The INNIS21 has a built-in ProfitLoop algorithm. Instead of sending raw sensor data all the way back to a distant controller for PID tuning, this module can close the control loop right at the edge. This cuts network traffic in half and improves loop stability by about 30%. My only gripe? The vertical tilt design is great for airflow, but if you mount it upside down in a cramped cabinet, you’re asking for thermal issues. Keep it upright, keep it cool, and it will run until the end of time.
Quality SOP & Tech Pitfalls
The Lab Report:
We don’t trust “new old stock” blindly. Every INNIS21 gets the full treatment before it ships:
- Visual & Counterfeit Check: We inspect the PCB for reflow work, check the ABB/Bailey silkscreen font, and verify the MAC address tag matches the chassis.
- Live Comm Test: We rack it in our Symphony Plus testbed. We ping the module, force a Profibus token pass, and verify Modbus register reads. If it drops packets, it goes in the bin.
- Electrical Stress: We use a Fluke 115 to check the 24VDC input isolation and verify the internal 5V/3.3V rails are dead-on under load.
- Firmware Logging: We read the EPROM/firmware version and log it. You need to know exactly what revision you are getting.
The Engineer’s Warning:
Here is the fastest way to waste a weekend: Do not ignore the MAC address and Node ID. These modules are not plug-and-play like a home router. If you pull a failed INNIS21 and drop a new one in without transferring the exact hardware address and network parameters, the DCS will reject it or cause a network storm. Also, watch out for the RS485 bias resistors. I’ve seen techs wire up a Modbus daisy-chain and forget the terminating resistors, then blame the module when the data is garbage. Grounding matters. If your shield isn’t grounded at one end, you’re building an antenna.
Installation & Configuration Guide
- Pre-Installation Safety: ⚠️ Verify 24VDC polarity. ABB modules are tough, but reverse voltage will instantly fry the input protection diodes. Take a photo of the old module’s DIP switches and Node ID sticker.
- Removal: Label the Ethernet and Profibus cables. Release the DIN clips. If the module is hot, let it cool for 2 minutes before touching the metal chassis.
- Installation: Transfer the Node ID and MAC address settings. If this module uses DIP switches, copy them exactly. Slide it onto the rail. Ensure the backplane connector seats fully; you should feel a solid click.
- Power-On & Testing: Apply 24VDC. Watch the status LEDs. You want a solid green “Run” or “Comms” light within 30 seconds. Open your Symphony management tool (Symphony Plus Inspector or similar). Verify the module is online, check the error counters, and force a test value to confirm bidirectional communication.
Compatible Replacement Models
| Status | Model | Notes |
|---|---|---|
| ✅ Drop-in Replacement | INNIS21 | Direct swap. Match firmware revision and Node ID. |
| ⚠️ Software Compatible | SPNIS21 | Symphony Plus native version. Hardware similar, but verify backplane compatibility and firmware load. |
| ❌ Hardware Mod Required | INICT13 | Computer Interface module. Different pinout and protocol handling. Do not use as a direct network slave replacement. |
Frequently Asked Questions (FAQ)
Can I hot-swap this module without shutting down the DCS?
Yes. The INNIS21 supports hot-swap. The backplane is designed to handle the make-before-break connection. However, I always recommend putting the loop in manual mode before you pull it. Just because the module can handle it doesn’t mean the control logic won’t get confused for a split second during the re-initialization.Does this module support standard Ethernet TCP/IP or just proprietary ABB protocols?
It supports both. It handles ABB’s proprietary Symphony network traffic natively, but it also acts as a gateway for Modbus TCP/IP and standard Ethernet. Just be careful with bandwidth. Don’t run your CCTV cameras through this module. Keep it strictly for control and HMI data.My new INNIS21 has a different firmware version than the old one. Is that a problem?
It can be. ABB is generally backward compatible, but major jumps in firmware can change how the module handles timeouts or packet sizing. If you are replacing a single module in a redundant pair, try to match the firmware of the surviving module. If you are replacing both, flash them to the same version before racking them.How do I know if the ProfitLoop algorithm is active?
You have to configure it in the control strategy software. Just having the INNIS21 in the rack doesn’t automatically turn it on. You have to assign specific control blocks to execute locally on the module. Check your function code assignments. If you’re not using it, you’re just paying for a fancy paperweight.What causes the “Comms Fault” LED to flash?
Usually, it’s a physical layer issue. Check your Profibus termination resistors (110 ohms) or your Ethernet cable continuity. If the physical layer is good, check the Node ID. Duplicate MAC addresses or Node IDs on the same segment will cause the module to shut down its port to protect the network. Use a packet sniffer if you can’t find it with a multimeter.Is the 24VDC power supply shared with the I/O modules?
Typically, no. The INNIS21 has its own power input. Do not try to daisy-chain the 24V feed through the module to power downstream I/O unless the manual explicitly says it’s rated for that extra amperage. Voltage drop across the backplane is a silent killer. Give it a dedicated, regulated 24V source.
