Thanks all for your answers so far!
PatrickLye wrote:
- Are all of the machines on the same subnet?
- Do you have good gigabit connections on all machines?
- Download WireShark and look at your network traffic to see if you are having packet crashes.
- Try Putting the machines all on a separate switch that is their own network for testing and see if the problems go away. If it does you may be able to set up a virtual network in the switch for these machines and then only allow traffic in/out of the network that is needed.
- Can you turn off the firewalls for testing?
- Try turning off logging in your network variable properties.
- Turn on buffering and set up a buffer size that will work on your network variable properties.
- Disable the enable enhanced DSC run time support in the Advanced tab of the build executable.
- I’ve found shared variables to be incredibly dependable on my industrial network and a bit problematic on our office network. They need to have good connectivity, and our office network isn’t all that good. They are working on it.
1. Yes
2. It's gigabit, bit if good or not - I don't know. They are all on the same switch. But some other traffic is also there (remote access, database connection...) and the IPs are accessible in the whole company (~3000 employees in 4 countries).
3. I tried wireshark in the past, but I don't know how to use it properly to detect network issues. Maybe I can get some support here.
4. We would need an USB->Ethernet adapter, because there is no free ethernet port on the machines. Because we don't really trust these USB devices, we didn't try yet. We'll try it in the next days!
5. Firewall already is turned off, antivirus has been disabled
6. I don't have an "Logging" section. Means I don't have DSC installed?
7. Will buffering improve the "reliability"? If we just get old buffered values, the alive-bit also might be missing.
8. We don't have any EXE running yet. All stations running in IDE. Is it a disadvantage?
---
I read about a logos.ini, which can be used in LV 8 to restrict shared variables to a specific MAC. Is this also possible in LV 2014?
/EDIT: Is seems that the problems are not totally random. The line might run without any issue for some hours. Once the problems start, they will occur frequently. Closing LabView and restarting it on all stations seem to clear the issues for some time. Maybe the SVE will run into problems after some time? Originally we just jused Read/Write shared variable with a connection-string wired to it. Then we started to open the SVs once and then use the refnums - but it did not really improve the situation. But like I said, the read/write VIs do not throw an error - the values are somehow just not equal on both sides.
Is it possible that the network (switch?) can run into problems after some time?