EthernetIP communication

[versum1]

Since upgrading to Labview 2019 I continue to lose communication with my SMC EX600 ethernet IP device. I am using a CRIO-9045. I can still communicate with the SMC device through a web portal on a computer on the same network so I know the IP address of the CMS device is active.

The only way to get the CRIO to communicate once again with the SMC device is to hard reset the CRIO.

Anyone have any ideas, other than downgrade back to Labview 2018.

[cbutcher]

We need more information.

Is there some common pattern in which the cRIO stops communicating? (i.e. it always happens when/after you ...?)

How is the device communicating with the cRIO (what LabVIEW patterns, designs etc are you using?)

Can you show at least the code handling communication, along with anything that can stop those loops (if you have some variable stop condition for a loop, etc).

How busy is the CPU/network on your cRIO? Is it possible other code is suffocating your communication (use the utilities to view CPU usage, you can use Linux tools to profile the network if necessary).

Edit: taking a wild-ass-guess, are you using Maps for your application on cRIO? Are you trying to index one into a For loop?