Excellent PLC Co.,Ltd

PLC and DCS professional supplier

HIMA F3 DIO 8/8 01 Module – Network-Induced Input Glitch and Software Adjustment

Troubleshooting

HIMA F3 DIO 8/8 01 Module – Network-Induced Input Glitch and Software Adjustment

HIMA F3 DIO 8/8 01 Module – Network-Induced Input Glitch and Software Adjustment

Troubleshoot HIMA F3 DIO 8/8 01 module input glitches caused by network latency. Includes step-by-step software configuration adjustments and preventive advice.


Scenario

During peak production hours, engineers observed that several digital input channels on the HIMA F3 DIO 8/8 01 module sporadically failed to update on the HMI. The module’s diagnostic LED did not indicate any hardware failure, and power readings were within specifications.

The problem was intermittent, appearing mostly when multiple PLC-controlled batch operations were executed simultaneously.


Investigation

A detailed review of the network traffic revealed significant PROFIBUS latency spikes. The I/O scan time occasionally exceeded the module’s polling window, resulting in missed input events.

Simultaneously, a recent software patch introduced a new input debounce routine that was not fully synchronized with the real-time scanning of the module. This combination caused the observed “glitching” effect on the HMI.


Resolution Procedure

  1. Access the module configuration via HIMA Safety Configurator.

  2. Adjust the input scan interval to accommodate network latency:

MODULE_CONFIG>INPUT>SCAN_INTERVAL=15ms
SAVE
RESET_MODULE
  1. Temporarily disable the new debounce logic for testing.

  2. Monitor input behavior on HMI for at least two full batch cycles.

  3. Once stable, gradually re-enable debounce logic with adjusted parameters to ensure synchronization.

After these adjustments, all digital inputs reported correctly, and the module no longer missed events.


Recommendations

  • Continuously monitor network traffic to identify latency issues before they impact modules.

  • Test software changes in a simulated or isolated environment prior to deployment.

  • Log scan intervals and input debounce settings for traceability.

  • Consider segmenting high-traffic networks to reduce PROFIBUS congestion.

Prev:

Next:

Leave a message