LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

UDP receiver does not receive messages

Solved!
Go to solution

Did the Simple UDP project work before the changes you've made?  That'll make it easier to troubleshoot what's going on with it.  If you can use the example without modifications, try changing the ports.  If that still works, check the logic.

 

If anything doesn't work at any step, you know what to look at.  (if the first port works but the second doesn't, you're looking at a firewall issue related to the specific port for example)

0 Kudos
Message 11 of 16
(1,973 Views)

Firewall is desabled. 

Private network

MCU --> microcontroler

0 Kudos
Message 12 of 16
(1,971 Views)

This definitely should work just fine. (Many years ago I wrote a program to receive syslog messages)

 

Is this the only active network interface? Maybe you should try to wire the net address after all to see if you get an error if you specify the 192.168.100.1?

0 Kudos
Message 13 of 16
(1,966 Views)

On local PC ports work just fine. I can read dataWrite and read_local PC.PNG

0 Kudos
Message 14 of 16
(1,957 Views)

It end up to be firewall issue.

I found out that our IT guys would reset firewall settings if firewall was turn off complitly.

It would be nice if labvew error message would tell you this.

 

Thanks everyone for help 

Message 15 of 16
(1,941 Views)

@Rus_K wrote:

It end up to be firewall issue.

I found out that our IT guys would reset firewall settings if firewall was turn off complitly.

It would be nice if labvew error message would tell you this.



It did.  It told you it wasn't able to connect.  I don't know how LabVIEW could expect to know which of the 100's to 1000's of reasons it was not able to connect, in this case your IT people screwing around with firewall settings.

0 Kudos
Message 16 of 16
(1,937 Views)