LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

UDP Recieve

Solved!
Go to solution

Hello,

 

I'm communicating with a device via UDP using a Win7 x64 workstation. I can sucessfully send datatgrams and the device responds correctly. The transmit port on the workstation is 10.1.0.68, port 61556 the receive port on the device is 10.1.0.230, port 25999, the transmit port on the device is 10.1.0.255, port 26000. The device is continuously brodcasting 824 byte packets at 60 Hz. However, I have not been able to read any output from the device.

My .vi is below:

 

UDP Listen.png

 

What have I missed?

 

Thanks!

Bill

0 Kudos
Message 1 of 7
(3,208 Views)

Where is your broadcast stream coming from? You have so many devices and transmit/receives in your post it is not clear what is happening.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 2 of 7
(3,201 Views)
Solution
Accepted by optiplex

Could it be Windows Firewall or Anti-Virus software blocking the inbound data?

Message 3 of 7
(3,184 Views)

Do you have more than one network interface in the workstation? If so, you might be listening on the wrong interface. Use the optional net address input on UDP Open to specify which interface to listen on. Use the String to IP function on the TCP palette to convert an IP string to a net address.

 

With a timeout input of -1, I assume you are using the Abort button to stop the VI shown. You won't see any error message when you do that. Try using the default of 25000 ms.

 

The other suggestion regarding anti-virus and firewall settings are certainly possible...

 

udp example.PNG

 

0 Kudos
Message 4 of 7
(3,174 Views)
Message 5 of 7
(3,166 Views)

Philip,

 

That was it. Thanks for your assistance!!

0 Kudos
Message 6 of 7
(3,159 Views)

You hit on the nose. I should have known to check this first -- I've encountered it before, but I guess I was lulled into thinking since I was on a closed network it wouldn't be considered private. Thanks for the help, you've saved me a great deal of time and frustration!

0 Kudos
Message 7 of 7
(3,158 Views)