07-21-2016 10:09 AM
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)
07-21-2016 10:13 AM
Firewall is desabled.
Private network
MCU --> microcontroler
07-21-2016 10:27 AM
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?
07-21-2016 11:16 AM
On local PC ports work just fine. I can read data
07-21-2016 02:32 PM
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
07-21-2016 02:42 PM
@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.