udp not working after exe built

[Sanith]

No. It will show an error, if there is no packets present at the port and once the packets are available it starts taking it, does't matter the previous error condition. This is the way it works prior to making the executable. But its not working after making the executable!

[BCL@Servodan]

How do You stop Your Application?

If the VI is wired exactly like You've shown in Your first Post, it'll keep running until You kill the Application.

If so, Your UDP close node will never run, thus not freeing the assigned port.

[Sanith]

Hi Servodan,

This is not the actual application software, this is extracted just to test this scenario - why it is not working when converted to the executable!

Sanith

[ico82]

This extraction is really minimal... However have you implemented something to keep alive the connection? If connection is opened and no messages are received connection is closed by OS.

The port number is hard coded written?

I have to repeat look at the example, what you have published is just three VIs, it is not enough.

[altenbach]

---

@Sanith wrote:

That is the maximum packet size.

---

High level UDP as implemented here does not care about "packets" and their payload sizes. That's at a much lower level. Of course if you always send much smaller messages, it is less likely to get fragmented. Who is the sender? Do you know anything about the message structure?

While LabVIEW is allowed to used the network because you allowed certain firewall rules during installation, your build application probably does not have that permission, so look into that.