We still have been metting the same problem on all windows-machines which have more than one interface. Really I can see solution when to UDP connect.vi wired interface name (or array of interface names or their system numbers), and not IP address. Because IP addr could be (and sometimes they are) dynamically changed, when network is reconnected or when computer obtains new addr from DHCP-server.
We have tested few situations. Here is one of them:
1. PC has 2 network interfaces Ethernet and WiFi.
2. When our LabVIEW program started, it opens UDP connection and listens to multicast traffic on all interfaces (0.0.0.0). Works fine.
3. Until Ethernet interface disconnected, and then reconnected. That is done via Windows Control Panel. LabVIEW never gets an error, and will never restart to listen on Ethernet interface. That is problem.
4. But here is the bigger problem. Restart program. It opens connection and (vua-lya). Connection is opened on WiFi interface only without any errors and warnings. Many restarts will not help. But it will work if wire IP addr of Ethernet interface to UDP connect.vi
5. So what? Normal behaviour?!
@billko wrote:
My question: Why a virtual network with no vritual boxes?
....
This must not bother LabVIEW. Sometimes they works, sometimes stopped. LabVIEW must listen their interfaces always without any problems, or that problems must be able to be solved at run-time.
Other applications, for example simple reader-listener written in Python (25 lines) has no such problems.
