06-28-2023 09:29 AM - edited 06-28-2023 09:41 AM
I have been stuck with this error for two days trying to run my LibraryCallTest on my cRIO 9047. I compiled it following this link: (Part 5: Building a Shared Library with Visual Studio Code and NI Linux Real-Time — nilrt-docs 1.0 do...). I've added the .so called in the .vi to my cRIO under usr/local/lib/ and usr/lib/ and I still have an error. What am I missing?
Solved! Go to Solution.
06-28-2023 09:47 AM
Try specifying the library path.
How to Configure LabVIEW to Use Relative Paths for DLLs
06-28-2023 09:58 AM
On step 3 I cannot find Application Directory.vi under File I/O, File Constants... I am using LabVIEW 2018.
06-28-2023 10:45 AM
Adding a path into allows it to be run, however my the addition is no longer working.
06-28-2023 10:59 AM
@JacobRiley77 wrote:
Adding a path into allows it to be run, however my the addition is no longer working.
What is your CLFN configuration? Are you using the correct calling convention?
06-28-2023 12:43 PM
This is what I was originally using:
Then I checked the specify path on diagram and played with the paths, but the addition was no longer working.
06-29-2023 01:00 PM
It allows me to run it if I have a specific path into the CLFN, but then it does not function properly. Here is an updated SS:
06-29-2023 01:57 PM
The VI is returning Error 7 at the Call Library Function Node using LabVIEW, indicating that the SO library is missing. Are you sure that you have transferred the library to the RT target? Did you use Web Server from NI MAX or FileZilla to transfer the file?
06-29-2023 02:01 PM
I have used WinSCP to transfer the file over to both directories.
06-29-2023 02:24 PM
Here is a SS of my WinSCP in the usr/lib directory, I also have it placed in the usr/local/lib directory. I had a few problems even getting the cRIO to connect to my laptop and I fixed it by installing the cRIO Real-Time Module. Is there another module that I might need to download in NI Package Manager?