Access Official Technical PDF

Share Summary:LinkedInEmail

EtherNet/IP safety I/O can simplify how safety devices are connected to a safety control system, but network connectivity alone does not make a machine safe. Engineers must consider the entire safety chain—from input devices and communications through safety logic and outputs—and verify that the system performs its required safety functions. A sound implementation combines risk assessment, correct configuration, careful installation, and documented testing.

What EtherNet/IP safety I/O does

A safety I/O terminal provides a connection point for safety-related input and output signals and communicates with a safety controller over an EtherNet/IP field network using CIP Safety communications. The GI-S series manual describes two terminal models, GI-SMD1624 and GI-SID1224, and covers their configuration, wiring, safety functions, diagnostics, and maintenance. The exact I/O capabilities and specifications should be confirmed in the applicable product documentation for the selected model.

In a machine, safety inputs may come from devices such as emergency-stop pushbuttons, guard switches, safety laser scanners, enable switches, two-hand controls, or light curtains. Safety outputs are used as part of the configured safety function. The terminal, network connection, controller, external devices, and application program must operate together as a system; selecting a safety-rated component does not establish that the complete application is suitable.

Start with risk assessment and system design

Safety design begins before devices are installed or programmed. A risk assessment helps identify hazards and determine what protective measures the machine requires. The system design must then account for relevant standards and regulations, the safety devices selected, the required behavior of the control system, and the conditions in which the equipment will be used.

Safety products provide functions and mechanisms intended for use within a properly designed safety-related system. Qualified personnel should design and install that system, and the completed machine should be tested before commissioning. The design should also identify who is responsible for safety across the machine lifecycle, including installation, operation, maintenance, and eventual disposal.

Plan the network and configuration

EtherNet/IP network layout is part of the implementation plan. The GI-S series documentation describes star, daisy-chain, and combined star-and-daisy-chain connection configurations. The appropriate arrangement depends on the system design. Before connecting a terminal to a network, assign a suitable IP address and communications speed, and ensure the network and device configuration match the intended application.

Configuration and programming use Sysmac Studio. The setup process described in the manual includes creating a project, registering a safety connection, setting the IP address, registering the I/O assembly, configuring safety I/O functions, and registering device variables. Safety programs are then created, debugged, and commissioned. These steps should be managed as a connected workflow: network settings, I/O assembly selection, device configuration, and program logic all need to agree.

Configuration data deserves particular attention when equipment is reused or installed on a different machine. The manual warns that previous configuration data stored in a terminal must be cleared before the terminal is installed in equipment or connected to a network. Configuration should also be checked across all devices before startup. Non-safety signals, including explicit messages and exposed variables, must not be treated as safety signals.

Verify safety reaction time

A safety function is only useful if the complete chain responds within the time required by the application. The total response involves more than the I/O terminal: the configured safety devices, communications, controller task, and output behavior all contribute to the result. The GI-S series manual includes a method for calculating and verifying safety reaction time and addresses the Expected Packet Interval (EPI) used in the communication configuration.

Calculate the reaction time for each relevant safety chain and compare it with the required specifications established for the machine. Do not assume that a network setting or a component value, considered alone, proves that the complete chain is fast enough. During debugging, verify that the terminal and connected external devices behave as programmed by the safety controller. Complete user testing of the configuration and operation before starting the system.

Installation, wiring, and commissioning checks

Physical installation and electrical practices affect reliable operation. The manual calls for installation in an enclosure complying with IP54 or higher and mounting on an appropriate DIN track, with end plates used to help prevent movement due to vibration. The installation environment should also be assessed for temperature, humidity, vibration, contamination, electrical noise, and other conditions covered by the product documentation.

Before wiring, turn off power to prevent unexpected operation of connected equipment. Use the specified wiring methods, suitable wire and tools, and correctly secured terminal blocks and Ethernet cables. The manual also specifies that the 24 V power supply must not be earthed on its positive side, and that the terminal’s test output must not be used as a safety output line. Power supplies must meet the stated requirements, and their capacity should be selected with the documented power demand and inrush current in mind.

During commissioning, treat LED indications as general diagnostic aids only, not as operational indicators or proof that a safety function is working. Verify behavior through appropriate system testing. Safety functions should never depend on an assumption that a status light accurately represents the condition of the complete safety chain.

Maintain the safety function over time

Inspection and maintenance help ensure the installed configuration continues to match the machine’s needs. Follow the product’s procedures for periodic inspection and cleaning, and investigate faults using the documented diagnostic information. If a terminal is replaced, account for its configuration and confirm the replacement system operates correctly. The manual prohibits disassembling, repairing, or modifying the product; maintenance should follow the specified procedures and be performed by qualified personnel.

Keep relevant instructions available to those responsible for operation and maintenance. When machinery or equipment is transferred, the documentation should accompany it so that the receiving organization can operate and maintain the system appropriately.

Conclusion: treat the network as one part of the safety system

EtherNet/IP safety I/O provides a way to integrate safety devices with a safety control system, but safe performance depends on the complete application. For engineers and integrators, the practical priorities are to assess risk early, align network and I/O configuration, calculate and verify reaction times, install and wire according to the documentation, and test the full safety chain before startup. Ongoing inspection and controlled maintenance help preserve that design intent throughout the machine lifecycle.

Access Official Technical PDF

About The Author