OPC communication between equipmets and Ignition fails unexpectedly

General Discussion
1

Hi,
in my company we just installed a new line, which is a clone of another one we already have, so this new line is running the same Ignition project as the old one.
To give you a bit of context, we have
7 OPC servers
2 TCP Modbus devices (they are datamtrix readers)

On our first day of testing everything went good and we produced 2 pieces.
The day after, it was horrible, nothing worked as expected anymore. I'll explain better.
Basically the OPC communication between the equipments (see the 7 opc servers above) and Ignition often gots lost. Sometimes the OPC server sends a tag that should trigger an event on the scada but the scada doesn't get the tag, even though I can see the tag value changed from the Designer. Sometimes it's the opposite, so Ignition writes a tag which should trigger an event on the equipment, but the equipments just keeps waiting and nothing happens.
When we get stuck on one equipment, if we try to reset and start the machine cycle again 2-3 times, then it eventually go smoothly.
What bugs me the most is that the behavior apppeared overnight...

Have you ever found yourself in this situation? Do you have any suggestions?
Thank you

2

There are so many ways that communications with devices can break that a description of your symptoms provides no clues.

There are likely many error messages in your gateway logs the correlate with your problems. You should also examine your gateway OS's logs to see if network interfaces were reporting any problems.

(If you cannot share all of the details here, you should open an IA support ticket.)