11-20-2015 12:40 PM
Hi,
I have been trying to let LabView send text messages, only I keep getting Error 59 (the network is down, unreachable or has been reset). I think this has something to do with the server I fill in (I used the template from this site). Does anyone know what I do have to fill in to the "Outgoing Mail Server (SMTP)"?
Thank you!
11-20-2015 12:53 PM
11-24-2015 07:49 AM
Hi Annabel2001. My name is Hashim, and I am an Applications Engineer at National Instruments.
I believe the problem you are experiencing is due to an invalid server name. The format of just "smtp" won't work within the VI as the program doesn't recognise this as a server to send texts to. There are a range of different servers you can set this control to, to get the VI working. As mentioned in another one of your forum posts, with what may be the same issue, the example referenced here may give a good indicator as to what to choose the server name as:
https://decibel.ni.com/content/docs/DOC-35093
This KB may also help with your application:
http://digital.ni.com/public.nsf/allkb/5C55FAEDC7BF5C0C862570930054D39F?OpenDocument
Let me know if this helps with your issue.
11-24-2015 04:22 PM
Where did you get the VI you are using to send this message? Is this something you wrote? It doesn't look like the SMTP VIs that come with LabVIEW 2015. What version of LabVIEW are you using?
Bob Schor
03-01-2016 09:21 AM
i am also getting the error59 when i connecting both the mitsubishi FX_3ge PLC and Labview throughTCP/ip.
so can anybody help me to resolve this issue.
its urgent
here i attached the error file.
03-01-2016 09:36 AM
Attach an actual VI. That last picture doesn't provide any information on what you are doing. I see an empty error case, and a TCP close. This one doesn't even show what TCP connection you tried to open or where you even did that.
03-01-2016 09:55 AM
03-01-2016 09:56 AM
here i am using open TCP/ip and close. Kindly go through the vi.
03-01-2016 10:24 AM - edited 03-01-2016 10:29 AM
As Gerd noticed, you have some network connectivity issues.
Have you opened up a command prompt to be sure you can ping the 192.168.1.250 address?
I also see a race condition in your code. Why are you opening and closing the TCP/IP connection twice in the same loop? Your two TCP/IP opens are going to execute in parallel to each other. When the first TCP/IP close happens after the first while loop ends, the other TCP/IP open would likely have already occurred, to the address and port will actually be closed by the time the 2nd while loop starts executing.
Why do you even have a first while loop? It seems odd that you will read a value continuously until the stop 3 button is pressed, then proceed to pass out only the last value to the next part of your code. Then have the 2nd part of your code execute as fast as possible updating a chart with the exact same data until "Stop" is pressed. Then to finish off with a final Write and Read with a connection that had already been closed.