LabVIEW 2023 and newer does not work for Linux #64
Comments
|
Using a SSH terminal, such as PuTTY or OpenSSH with Windows 10+, can you connect to the cRIO and navigate to the Then, run You are using LabVIEW 2023 32-bit, but the cRIO-9038 is running an Intel Atom 64-bit processor. It is possible to run 32-bit LabVIEW on a 64-bit processor and previous versions of LabVIEW Real-Time and FPGA modules only worked with 32-bit LabVIEW, but maybe something with LabVIEW 2023 is different now? |
|
Here is the result of ls -l. lrwxrwxrwx 1 admin administrators 14 Mar 31 2020 libssh2lv.so -> libssh2lv.so.1* I'm definitely using 32-bit LabVIEW and always have since I don't trust 64-bit yet nor had it supported all the toolkits (it's getting better) |
|
NI support just stated there was a Kernal change in 2023...that may be the issue. I'll try LV2020SP1 |
|
You could always compile the libssh2 and libssh2lv libraries from source on your cRIO-9038 as another possibility. The output from the At the moment, the only difference I can see is LabVIEW 2023, so I will be curious if the Kernel change was the problem. |
|
I tried to update the cRIO for a build environment, but I have been unsuccessful (0% success in building anything from github)...some depenecy is missing as usual. I had my cRIO online and ran the following cmds: opkg install packagegroup-core-buildessential Then started the build process for libssh2lv, which fails at "cmake ..". Here is the result.CMake Error at /usr/share/cmake-3.19/Modules/ExternalProject.cmake:2542 (message): -- Configuring incomplete, errors occurred!I give up. I'm going to figure out Telnet handshaking (Telnet is another path I can use, and the NI Internet Toolkit doesn't work with my device). |
I am sorry. Hopefully the Telnet will work for you. I do know LabVIEW 2021 introduced "native" support for some SSH and SFTP functionality. Maybe that will work for your needs? FYI, the error for the build environment is because |
|
NI didn't implement interactive SSH, only a single command method......pretty much useless except for simple commands...totally useless for a continual interactive application. I'll give "opgk install git". Thanks! |
|
I was able to get past "cmake ..", but not "cmake --build . --target ipk" make: *** No rule to make target 'ipk' |
|
Great to hear you were able to build the The You don't have to build the IPK. If the cRIO you are using to build the
Copy the |
|
Hi, I had the same issue when trying to use the library in LabVIEW 2024, I managed to get over the error 7 and 13 building the packages in the cRIO as mentioned here, but, now, when I execute the code in RT, the cRIO restarts automatically and doesn't show any errors, @volks73 told me that I might need to build the OpenSSL library as well, @volks73 where could I get the .tar.gz file? I share the building log: admin@NI-cRIO-9057-XXXXXXXX:~# cd /tmp -- extracting... Update the VERSION argument value or use a ... suffix to tell -- The C compiler identification is GNU 11.4.0
-- The following REQUIRED packages have been found:
-- The following features have been disabled:
-- Configuring done -- extracting... |
volks73
changed the title
|
After building new IPK binaries, we have overcome this issue and faced error code 11 (Key exchange error) on connect.vi Possible reason(s): [Key Exchange Failure Error] If the client is executed from Windows target there is no issues. Only from RT Linux target the error occurs. |
|
See my comment: #65 (comment). The libssh2lv build will download and use its own OpenSSL and LIBSSH2 if you build it from source. Thus, if you have an Internet connected NI Linux RT device, it will download a specific version of these dependencies, build them and use these as opposed to the system OpenSSL or LIBSSH2 shared libraries. This might be the source of issues for some users as LabVIEW 2023 or newer probably uses a newer version of OpenSSL and it may even provide LIBSSH2 as a system library, too. The system libraries might be different versions. If bumping the dependencies versions work, then creating a Pull Request (PR) for the libssh2lv project with the newer versions would be greatly appreciated. |
I see error 7 (file not found) and error 13 (failed to load dynamic library).
I followed the instructions to download and install the 2 support files...I have a cRIO-9038 (x86) so the files are libssh2lv_0.2.1-r0.5_core2-64.ipk and libssh2_1.9.0-r0.4_core2-64.ipk, transferred to the cRIO, and installed them (opkg instal).
opkg list shows the 2 packages are installed:
libssh2 - 1.9.0-r0.4-r0.4 - Client-side C library implementing the SSH2 protocol
libssh2lv - 0.2.1-r0.5-r0.5 - LabVIEW-friendly C library for the libssh2
I had the same issue with a virtual machine so I tried with a real cRIO (9038)...eexactly the same issue.
I'm using 32-bit LabVIEW 2023 Q3
I must be doing something wrong since others are using this in their LabVIEW application, but I don't know what it is.
The text was updated successfully, but these errors were encountered: