07-03-2008 10:22 AM
07-03-2008 10:46 AM
07-03-2008 11:42 AM
05-28-2013 11:13 AM
The link http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c49602a79827ddbe86256ce9005757d5
is about using Putty. I used it to connect, but then what? The exec.vi exits and the connection is gone. There is supposedly a scriptfile created by adding "commands" in a control string on the front panel. Using anything in that field seems to generate errors, but the error doesn't get returned from the exec.vi
So where are the SSH VI's ? Internet Toolkit? I am using the full professional development version of LabVIEW 10. Does it not include the SSH VI's?
05-28-2013 01:36 PM
As far as I know there are no standard SSH VIs anywhere. At least at the time that I started this thread there were not. I came up with a solution that I have been using ever since using the program Plink that is installed with Putty. Please take a look at the VI I have attached. It is pretty straight forward. You enter the location of plink.exe, the username, the password, and the host and you can send any command and get a response just as if you were connected via an SSH client. It has been working great for years. Let me know if you have any questions about it.
05-28-2013 03:17 PM
Unfortunately, I am still on version 10. Your VI is version 11.
I tried the Putty plink.exe method but saw no way to login after the connection is made. I do not know what type of commands to send before the session is fully logged-in. After which, I know the commands for the device I need to chat with. Once the plink executes, the device is waiting for a username, but I cannot enter that since exec.vi is still running. Of course, when it isn't running there is no connection anymore.
05-29-2013 05:28 PM
Here you can find below the example attached above for LabVIEW 2010.
Regards
05-30-2013 01:18 PM
Have you been able to open the VI now that you have it saved in the correct version? You should be able to see now that you have to send everything all at the same time. This process basically opens the session, sends the command(s), waits for a response(s), and then closes the session. It is not like a telnet session where you can open it and then interactively send commands as well as get responses. As stated before the VI I have sent you I have been using for years and has been working just fine.
05-31-2013 06:59 AM
Another useful link from rolfk:
http://lavag.org/topic/12346-labview-network-library-to-support-ssl-ping-and-ipv6/#entry74021