LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

UDP open error 54

Solved!
Go to solution

To attention of NI: I have encountered error 54 in LabView 2016 Version 16.0f2 64-bit: 

"Error 54 occurred at UDP Open in NAME.vi

Possible reason(s):

LabVIEW: The network address is ill-formed".

 

I have read about it on the forum ( https://forums.ni.com/t5/forums/v3_1/forumtopicpage/board-id/170/thread-id/875785/page/2 ).

The synopsis is the same: the vi in question works perfectly well until one day it stops to work for no reason. I DID NOT MAKE ANY CHANGE IN THE VI NEITHER IN THE NETWORK ADAPTER SETTINGS. Then it resumes working. I CANNOT DEPEND UPON ARBITRARY FUNCTIONALITY OF THE SOFTWARE.

NI did not offer any advise on this issue. That's not a way to treat customers. It wasted several hours of my life. Please provide clear guidelines on the stable use of UDP Open function. See code in attachment.

Please send your answer to maxim.morozov@strath.ac.uk

Thank you,

Maxim

0 Kudos
Message 1 of 9
(10,206 Views)

Can you ping the IP address when you get the error?

Message 2 of 9
(10,061 Views)

so YOU TALKED TO NI SERVICE DIRECTLY and they said they won't help you?

 

and BTW you HAVE some SPONTANEOUS outbreak OF capsLOCK screaming going!

 

you should keep in mind, that most of the ppl here are users,

so venting like this might feel good but does not help you at all here.

 

regarding your problem, i presume that it is a network issue, like some other process having a socket with the same port you want,

or an old instance of your program did not close the socket it was using.

 

please make sure, that it is not a general network problem.

 

regards


If Tetris has taught me anything, it's errors pile up and accomplishments disappear.
Message 3 of 9
(10,059 Views)

so the wrong port would throw a ERR(60)

 

ERR(54) means you have either a wrong ip address or wrong hostname,

by which i mean the address can not be resolved by labview.

 

why that happens i don't know, but im sure that is not a labview problem,

but something with your network/dns

 

http://zone.ni.com/reference/en-XX/help/371361N-01/lverror/tcp_and_udp_error_codes/

 

for a demonstration go to the Examples Finder and search for "udp",

there is a "Simple UDP" example project.

 

regards


If Tetris has taught me anything, it's errors pile up and accomplishments disappear.
Message 4 of 9
(10,051 Views)

A DHCP server which re-assigns IP addresses on your network for some reason (e.g. devices connecting and disconnecting from the network)?

Message 5 of 9
(10,045 Views)

yes, pinging is alright

0 Kudos
Message 6 of 9
(10,022 Views)
Solution
Accepted by MAXIM_MOROZOV
In general, networks change and communications can sometimes be lost for various reasons. It is important when using networking that you make your software robust against changes/disconnects in the network. Sometimes these changes are accidental (e.g. knocked a network cable) and sometimes they are deliberate (e.g. DHCP server renewing IP).

If you get a network error, you should try to reconnect until the connection can be re-established.

If you want to be sure that the error is in your code versus a network problem, try creating a local server VI that listens for your UDP connection and run it (i.e. talking on localhost). If it runs fine talking to 'localhost' but sometimes fails when talking to a non-local IP, then you know it is a network issue.


LabVIEW Champion, CLA, CLED, CTD
(blog)
Message 7 of 9
(10,018 Views)

Thank you.

The problem is not LABVIEW related since the same purpose code written in C++ did not work either.

I did contact our IT department (as I suspect that a network "update" caused the problem) but they were not able to help...

 

0 Kudos
Message 8 of 9
(10,002 Views)

I had this same error after editing some of the firmware. I changed all of it back at the error was still there. Funny enough I just copied and pasted the program and saved it to a new file and everything worked fine. I did the same thing again and just edited and saved my program and this also resolved the error for some reason

0 Kudos
Message 9 of 9
(8,528 Views)