Ignition Exchange - Network Device Ping UDT problem

Ignition
1

Good morning, I add the UDT in my project and it works great to check the status of the connected devices. This is the link: Ping UDT

The problem is that sometimes I have some disconnection counts but if I check on the PLC log actually they are not true.

I tried to increase the rate of the ping from 1000ms to 2000ms and the timeout from 1000ms to 3000ms just and however I have miscount. I check this on multiple PLC logs and in none I have this disconnections.

Thank you for the help

2

Perhaps the author of the UDT @Arnaud_Declerck can help with this.

3

Hi @Aiasa21,

I will take a look but no one complains about this before.
To be sure that I test like you setup I need some information

  • what OS are you using
  • what version of ignition are you using.
  • how is your network configuration
  • what type of plc do you try to monitor

Regards

Arnaud

4

Thank you @justinedwards.jle for the help.

Hi @Arnaud_Declerck, thank you too, here you have some information.

  • Ignition is installed on a Windows Server 2019
  • Ignition Platform 8.1.23
  • All the PLCs in the industry and the server are installed under different vlan (Do you need need some specific info?)
  • Most are Omron NJ/NX type

Thanks for the help

5

@Aiasa21,
I will try to replicate as close as possible your layout.
Do you mean vlan instead of wlan ? (I don't think extra info about it is needed.)

Regards

6

Yes sorry vlan, you're right.

Thank you

7

Hi @Aiasa21

image
image1027×427 39.2 KB

I've tried to replicate as close as possible your situation.

  • Win 19 server in one vlan with ignition 8.1.23
  • PLC Compact logix (i don't have a omrom plc) in another Vlan
  • Server in the same Vlan as the windows one

It has been running for almost two day and not disconnect count coming. I even tried to do multiple download to the plc to see if that have an impact.

I don't thing this come from the code but more from your config.

Hope this help and don't hesitate if needed or post some feedback if you find something

Regards

8

Hi @Arnaud_Declerck, thank you for your tests.

As you say probably we have something strange on the network that trigger this "fake" errors.

Thanks again, I appreciate you help.
Have a nice day