LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

UDP open error 54 issue

Hi Romain,

 

what happens with a fresh VI, containing just the UDPOpen to local port 6000?

(Please do a restart of your laptop first. Can you show a screenshot of "ipconfig" in a command shell?)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 21 of 30
(2,040 Views)

errorUDP.PNG

I created a fresh VI, I got the same error.

 

Here is what you asked for

 

ipconfig.PNG

0 Kudos
Message 22 of 30
(2,034 Views)

Hi Romain,

 

you cannot open a port which is already in use!

Two notes:

- close any port you have opened

- try a different port (the example VIs use something in the 61000 range…)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 23 of 30
(2,026 Views)

Hi,

Thank you for the tip, I'll try to find which other device have opened the port (I am connected to a network of several computers communicating at the same time).

For your second note, the thing is I can't use another port actually.

Regards,

Romain

0 Kudos
Message 24 of 30
(2,023 Views)

Hi Romain,

 

why can't you use a different local port?

It's the port where you send your messages from…

The receiver (IP and port) is specified with UDPSend!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 25 of 30
(2,017 Views)

Hi again,

I checked about the use of the different ports, and I saw that the port 6000 was used thanks to netstat -a -n -o in cmd. But after removing the process (as you can see below) that used the port (which was the NI domain service) , I still got the error 60

Edit : Nevermind, the error was occuring when I run the VI on Compact RIO. But if I run the VI in the laptop, it just works ! The other computer doesn't receive my message yet but it is an other issue. Thank you very much !

 

 

netstat -a -n -o.PNG

0 Kudos
Message 26 of 30
(2,016 Views)

Hi Romain,

 

please try a different port. Choose a port which is known to be unused.

 

Have you tried the example VIs I referred to earlier?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 27 of 30
(2,011 Views)

Hi everyone,

I am communicating with a piece of hardware through UDP protocol. The information given by it is a value of a physical quantity (pression of the system). I run on Labview 2014 SP1 on Windows 7

 

I began to run the VI on my laptop and it worked. Now, I want to run it on compact RIO because the algorithm controlling the physical quantity will run on it. But when I run the same VI on cRIO, error 60 (port already in use) appears on the open UDP VI. I can't change the port due to the hardware I am communicating with.

 

I think that use of the port is due to the cRIO (I am new to networks actually). And I don't know how to remove the process except from my computer using these commands in cmd (which is useless now that the VI is running on cRIO).

 

 

netstat -ano | findstr :{num_port}
taskkill /PID {PID_using_mum_port} /F

 

So I am trying to do is killing the task (probably coming from the cRIO) which is using the UDP port I need (6000) so to be able to open a connection on it.

 

So I tried to use the System Exec VI to use the commands from above and the equivalent in Linux. But it gave either nothing or the error 2 (full memory). Also, I was not able to read anything on the outputs of the System Exec VI.  Looking at the example VI didn't help me with my problem.

 

If you have other solutions to kill the process, I can try it too. It is not important if I have to do it manually.

 

Thank you for your help !

Download All
0 Kudos
Message 28 of 30
(2,027 Views)

Hi Romain,

 

again: why do you need to use a local port of 6000? Local and remote port can be different…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 29 of 30
(1,990 Views)

Hi,

I finally understand what you meant by using a different port. I thought that I couldn't open a connection on the port A with the UDP Open VI and write on the port B with the UDP Write VI. I thought it had to be the same port in both functions.

Now it works. Thank you

0 Kudos
Message 30 of 30
(1,981 Views)