UDP problems when building executables

[Tom C]

I am using LabView 5.1.

I have applications that send UDP messages (UDP Write.vi) to a Device Under Test with 300 ms intervals. The DUT always sends reply messages, so I use UDP Read.vi with 5000 ms timeout to receive the messages. This works fine when running the application as a VI in LabView. But when I build an executable of it, some reply messages somehow get lost, because the timeout in UDP Read.vi occurs. This happens with an interval of a few minutes. This means that approximately 1 % of the messages are lost.

What could be the reason to that the application works fine in LabView, but not as a stand-alone executable?

[Jeremy Braden]

There could be a number of reasons for this behavior. It may be that the function is not working properly on the run time engine (RTE). The best fix for this is to see if the problem persists in LV 7.1. It is the best version of LabVIEW to date. If you can post code that shows the problem then it can be tested in other versions.

Your executable may not have all the settings that are in the development environment. The follow KB discusses a solution:
Setting LabVIEW Preferences For a Windows Executable

Lastly, UDP is a lossy protocol by definition. Consider using TCP instead if the losses are unacceptable.