A LabVIEW add-on and toolkit for communicating with a SSH server. This adds SSH client support to LabVIEW by using the libssh2 library and a LabVIEW-friendly wrapper library, libssh2lv. This only adds client-side SSH support. It does not add SSH server support.
A VI snippet of downloading a file from a remote SSH server using this toolkit, similar to the scp.c example from the libssh2 C library project:
A VI snippet of uploading a file to a remote SSH server using this toolkit, similar to the scp_write.c example from the libssh2 C library project:
A VI snippet of executing a single command on a remote SSH server and reading the response using this toolkit, similar to the ssh2_exec.c example from the libssh2 C library project:
For more examples of using this toolkit and VIs instead of VI snippets, see the VIs in the Examples source folder, or (eventually) use the NI Example Finder in the LabVIEW Development Environment after the toolkit has been installed.
- LabVIEW 2009 or newer (All systems)
- libssh2-nilrt-ipk (For CompactRIO only)
- libssh2lv-nilrt-ipk (For CompactRIO only)
- Caraya
- HTML Help Workshop (for compiling the help documentation)
- JKI State Machine
- LabVIEW 2009 or newer (for building)
- LabVIEW 2018 or newer
- Labricator (only for automated builds, private package available upon request)
- OpenG Array Library
- OpenG File Library
- VIPM Pro (only for automated builds)
- VIPM API (only for automated builds)
The Caraya, JKI State Machine, OpenG Array Library, OpenG File Library, and VIPM API dependencies must be installed for all versions of LabVIEW (2009 and 2018) to avoid errors during automated builds.
A VI Package (VIP) is available at VIPM.io. The recommended installation instructions are to:
- Navigate to the LIBSSH2 for LabVIEW package at VIPM.io.
- Click on the Install button to the right. The VI Package Manager (VIPM) (freely available from JKI) will start automatically.
- Follow the on-screen instructions to complete the installation.
Alternatively, the toolkit can be installed by: (i) downloading the source code and building the VIP, (ii) downloading a VIP from the releases section of this project, or (iii) manually copying the VIs from the source code into a project.
Communication from a CompactRIO or PXI controller running the NI Linux Real-Time (RT) Operating System (OS) to a remote SSH or SFTP server for a real-time application is possible, but several dependencies must be installed on the RT target in order to work.
- Follow the Quick Start instructions for installing the libssh2 shared object (SO) onto the CompactRIO. This will place the
libssh2.sofile in the correct location on the CompactRIO. This SO is needed for thelibssh2lv.sofile. - Follow the Quick Start instructions for installing the libssh2lv shared object (SO) onto the CompactRIO. This will place the
libssh2lv.sofile in the correct location on the CompactRIO. This SO is needed for this LabVIEW toolkit's VIs to work. - Install the VIP according to the Desktop installation instructions. This will ensure the VIs are available for development. The VIs will be automatically deployed to the CompactRIO when the real-time application is either built and deployed as an RT executable or when running from within the development environment.
Each component in the LIBSSH2-LabVIEW project has a Source Distribution build specification. The destination of each source distribution build is the builds folder relative to the project root, i.e. same folder as the LIBSSH2.lvproj file. Additionally, the output for the compiled help documentation is also the builds folder. The builds folder should not be included in the version control repository. A Build.vi script is available in the Scripts.lvlib project library that will build all of the components and the help documentation automatically (VIPM Pro is not needed, but the HTML Help Workshop is needed).
The VI Package Build (.vipb) specification, located in the configs folder relative to the project root, is configured for the package source to be the builds folder. Thus, the Source Distribution for each component must be built before opening the LIBSSH2.vipb file in the VIPM; otherwise, the package configuration will be lost.
Important, if creating a package for LabVIEW 2009 from LabVIEW 2018, the VI Server TCP/IP ports must be different for each version of LabVIEW and verified with the VIPM application before proceeding. An error will occur when the VIPM is started if both LabVIEW 2009 and 2018 are running at the same time. Basically, VIPM will not know which VI server to use if both versions of LabVIEW are using the same TCP/IP port.
If VIPM Pro is available, then open the LIBSSH2.lvproj file in any version of LabVIEW newer than 2009 and run the Package.vi located in the Scripts.lvlib project library of the Project Explorer window. Ensure all dependencies are installed before running the Package.vi script.
Note, the version number for the package is set in the configs\LIBSSH2.vipb file. The version number in the VIP build specification file should be modified and saved before running the Package.vi script.
If VIPM Pro is not available, then the following steps can be executed to do essentially the same thing as the Package.vi script. Ensure all dependencies, except VIPM Pro and the VIPM API, are installed before completing these steps.
- Start LabVIEW 2018 or newer and open the
LIBSSH2.lvprojfile. - From the Project Explorer window, File>>Save for Previous Version..., a new dialog will appear.
- Select 9.0 from the drop down menu.
- Click Save.... A new dialog will open.
- Create the
target\9.0folder hierarchy in the project root, i.e. the same folder as theLIBSSH2.lvprojfile, if it does not already exists. - Click Save.
- Close LabVIEW 2018 or newer and the
LIBSSH2.lvprojfile. - Navigate to
<project root>\src. - Copy the
Helpfolder to<project root>\target\9.0\src. - Start LabVIEW 2009.
- Open the
<project root>\target\9.0\LIBSSH2.lvprojfile. Do NOT open the project in any other version of LabVIEW. - Open each Source Distribution build specification under the "Build Specifications" tree item in the Project Explorer and change the Output Destination to
<project root>\target\9.0\builds. Save and close each build specification. - Run the
Build.viin theScriptsproject library to build each Source Distribution under the "Build Specifications" tree item and the compiled help documentation file (LIBSSH2.chm). The output of each build will be available in<project root>\target\9.0\builds. - Open the
<project root>\target\9.0\configs\LIBSSH2.vipbfile in VIPM. - Build the VI package with VIPM. The output will be available at
<project root>\target\9.0\packages. Do NOT modify anything in the package build specification, but ensure the "2009" version of LabVIEW is selected in the upper, right-hand corner of the VIPM application window. - Close VIPM.
- Close LabVIEW 2009 and the
<project root>\target\9.0\LIBSSH2.lvprojfile.
See the in-app LabVIEW Help system for more information and documentation about using the library after it has been installed, or visit the web-based documentation. Examples are also available within the LabVIEW development environment using the "Help->Find Examples..." menu item.
Tests are written in LabVIEW using the Caraya unit testing framework and included in the project via the various Tests.lvlib project libraries and the tests on-disk folder. To run the tests, open the LIBSSH2.lvproj file found in the project root in the LabVIEW Development Environment (32-bit or 64-bit) and run the Test.vi script located in the Scripts.lvlib project library. This will run all of the tests defined in all of the various Tests.lvlib project libraries located in the project.
The tests require a SSH server. The SSH server should support password and public/private key authentication. The SSH test server can be the localhost. The tests will prompt for a IP address, username, password, passphrase, etc. as needed. None of the tests are included in the VIP distribution. They are only included with the source code, but they also provide excellent examples for using each of the VIs in the public API of the toolkit.
LIBSSH2-LabVIEW is licensed under either the BSD-3-Clause or the Apache-2.0 license, and it contains statically compiled code from the libssh2 and OpenSSL projects, which are licensed under the MIT license and Apache-2.0 license, respectively. See the docs folder for more information about licensing and copyright.