By Dovydas Kersys · Chapter 34 of 58 in Machine Commissioning.

Before you begin: Follow the machine documentation, risk assessment, site procedures and lockout/tagout requirements. Commissioning can expose personnel to electrical energy, stored pressure and unexpected motion. Never defeat a safety function merely to make a test easier. Examples and diagrams are generic and must be checked against the actual machine.

Real-time industrial networks add device configuration, cyclic I/O and diagnostic relationships on top of Ethernet. Commissioning should prove device identity, module configuration, I/O data and fault response.

Why this matters during commissioning

A device can be pingable and still not exchange the correct process data with the controller.

Advertisement

Commissioning procedure

  1. Confirm the controller project expects the installed device type and module layout.
  2. Verify device name/IP assignment and slot/module configuration.
  3. Check controller diagnostics for connection or ownership errors.
  4. Operate a real I/O point and confirm cyclic data.
  5. Disconnect the device and verify diagnostic/alarm response.
  6. Reconnect and confirm automatic recovery without manual project intervention.

Common failure patterns

  • Correct IP but wrong device name or identity.
  • Remote I/O module inserted in wrong slot.
  • Input data shifted because module layout differs from project.
  • Drive owned by another controller/session.

Evidence to record

  • Measured value and test point
  • Expected value / expected state
  • Observed value / observed state
  • Pass/fail result and any deviation
  • Name/date or responsible person where required

FIELD RULE: Ping proves IP reachability. It does not prove industrial I/O configuration.

Continue the series

Adapted from Machine Commissioning for Maintenance and Automation Technicians, by Dovydas Kersys. © 2026 Dovydas Kersys. Featured cover image is an AI-generated editorial illustration.

Advertisement