LabVIEW needs native SSH and SFTP connection support.
In the past, LabVIEW users have had to rely on third party applications like PuTTY or ExtraPuTTY to do very basic Linux/Unix secure shell operations. Not only does it add an extra layer of complexity to the code but it is also quite inflexible. Increasing interoperability requirements of present day (and future) computer systems rely heavily on terminal services with a vast percentage of those being SSH based. In the past 5 years I have needed to use SSH type connections more and more inside of LabVIEW, I do not see it ending anytime soon and I know I am not alone.
An SSH connection could be managed in much the same manor as the current VISA and TelNet connection are managed. An example of some of the tools could look something like the below image and could come standard or part of the Internet Connectivity Toolkit.
Great idea and I kudo'ed, but I didn't see Labvolution mentioned yet. Only used it in testing sftp but it worked well for what I needed, and it has no licensing cost. The included license sounds similar to BSD but didn't specifically mention BSD.
Unofficial Forum Rules and GuidelinesGet going with G! - LabVIEW Wiki.12 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
Happy 8th birthday! Glad to see you are still a new idea.
I've been well. I've learned a lot about (and failed once or twice) using putty and ssh.net over the years.
I'm starting to learn Python now, and I've made a new, slightly paranoid friend named Paramiko. I also found something called PyVISA that I can use in a pinch.
Many of the little projects that I use LabVIEW for seem more and more suited to these new tools because they end up needing to interface to IoT and cloud based stuff that doesn't even relate to RS-232 or VISA.
Best of luck; I'm pulling for ya and hope you will someday transition to "In Progress".
Finally got to the point where I can no longer avoid SSH in my test system. After digging into the issue I found this link and added my kudos. Not like it will help much since this issue seems to be getting zero traction after nearly a decade now.
Hopefully I will be able to roll my own solution somehow or leverage one of the .NET solutions. Not holding out any home NI will solve this one for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.