INNIS01 Network Interface Slave Module (NIS) ABB Bailey

The ABB INNIS01 Network Interface Slave Module can be used in various industrial environments as it supports multiple protocols like Modbus RTU, Modbus TCP, Ethernet/IP, and PROFINET. It is resistant to severe environmental conditions and is very quickly installed in both old and new systems. Automated production lines, energy management, and smart buildings are the areas in which INNIS01 eliminates downtime and improves the effectiveness of the system.

Emphasize system boundaries rather than functional stacking
The design focus of INNIS01 lies in clearly defining the system hierarchy, ensuring a distinct boundary between the field signal layer and the control network layer, and minimizing the mutual influence between different system layers.
The communication behavior is consistent, facilitating engineering management.
During the operation of the module, a fixed data interaction mode is maintained, with a stable communication rhythm and data processing methods, which helps engineering personnel to manage uniformly during the configuration, debugging, and maintenance stages.
System architecture suitable for large-scale deployment
In a multi-node system, the operation mode of INNIS01 does not change significantly with the increase in the number of nodes, making it suitable for use in engineering projects with a large number of I/O points.
The design is oriented towards long-term operation requirements.
The operation logic of the module is relatively simple, with limited state changes, and it focuses more on theconsistenty performance of the system during long-term continuous operation rather than short-term performance indicators.

INNIS01 is typically used in industrial control systems where a large number of on-site signals need to be centrally connected to the control network. It is particularly suitable for projects that have specific requirements for the clarity of the system structure and the manageability of communication.
In process industries, continuous production facilities, or traditional DCS systems, INNIS01 is often used as a basic interface unit between the field signals and the control network, providing a stable and predictable data input channel for the control system.
In scenarios of system expansion or renovation, INNIS01 is also suitable for supplementing or reconstructing the on-site signal access layer. It helps engineers complete the adjustment of the system scale without significantly altering the control logic.

Configuration process:
Power connection: Connect the 24V DC power supply to the INNIS01 module.
Network settings: Network parameters can be set through the Web interface or a dedicated configuration tool to ensure a stable connection with other devices.
Equipment testing and calibration: After the configuration is completed, conduct equipment tests to ensure that the communication between all devices is normal and that the modules can operate stably.

The process control unit interface is made up of the INNIS01 Network Interface Slave Module (NIS) and INNPM11 Network Processing Module (NPM). Through this interface, the process control unit has access to INFI-NET. At the same time,e the NPM module communicates with the control modules via the Controlway.

The process control unit interface can support hardware redundancy (refer to Figure 1-1). In a redundant configuration, there are two NIS modules and two NPM modules. One pair of modules is the primary. If the primary modules fail, the backup modules comonlinene. Redundant data highway communication capability is a standard feature.

The NIS module is an I/O module that works in conjunction with the NPM module. This allows a node to communicate with any other node on the INFI-NET loop.

The NIS module is a single printed circuit board that occupies one slot in the module mounting unit. The circuit board containsmicroprocessor-basedd communication circuitry that enables it to interface with the NPM module.

Two latching screws on the faceplate secure the NIS module to the module mounting unit. There are 16 LEDs on the faceplate that display error codes and event/error counts.

The NIS module has three card edge connectors for external signals and power (P1, P2, and P3). Connector P1 connects to the module power source. Connector P2 connects the NIS module to the I/O expander bus to communicate with the NPM module. Serial communication to other nodes is through connector P3 using a cable connected to a termination unit or termination module. Communication between nodes is through coaxial or twinaxial cables that connect the termination units or modules on each node.e