I have a remote RT target running linux RT. I am controlling this from a windows host PC running teststand 2019. Both the host PC and RT target are connected to system link. I want to be able to upload a TDMS log file (logged from Veristand on the RT target) to system link. Is there a way to do this using the upload file teststand step for systemlink, on the host PC? I just dont know how to pass the file path to the TDMS file stored on the remote target.
Any help appreciated!
Hi jdkdev -
My name is Darin, I'm the lead Product Owner for VeriStand. I see two options here:
I hope that helps explain enough so that you can evaluate these two and understand the tradeoffs between each approach. Best of luck and please let us know how you go forward, happy to continue the discussion.
So I was trying to access the system link API from the RT controller, however I get the error pasted below stating that the library is not installed. When I try to add the SystemLink Labview API under the software tab of the RT controller (Linux RT System Image 21.5) I don't get any option to install it since it is not listed. The SystemLink Labview API is definitely installed on the host however. So is it possible to install this on the RT controller? Any ideas what I am doing wrong here?
Error -251046 occurred at NI Skyline Configuration Library.lvlib:Open Configuration (Desktop).vi
Unable to load the LabVIEW HTTP client library. Ensure the HTTP Client is installed on the target system.
Complete call chain:
NI Skyline Configuration Library.lvlib:Open Configuration (Desktop).vi
NI Skyline Configuration Library.lvlib:Open Configuration API Key (Desktop).vi
NI Skyline Configuration Library.lvlib:Initialize From Auto Configuration.vi:4270001
NI Skyline Configuration Library.lvlib:Open Default Configuration.vi
NI Skyline Utilities.lvlib:Execute HTTP Verb.vi:7500001
NI Skyline File HTTP Library.lvlib:Get Version.vi
NI Skyline File HTTP Library.lvlib:Send File Core.vi:40001
NI Skyline File HTTP.lvclass:Send File HTTP.vi:5980001
target - single rate.vi
My goal here is to have a custom device just upload a file to system link directly from the RT target.
From MAX or SystemLink you need to install the generic HTTP Client with SSL Support for the SL LV API to work on RT.
I tried to install this and it works if I deploy a VI from a project. However I get error 1003 when I try to add the system link labview APIs into a veristand model or custom device (compiled in LabVIEW). It seem like it is still missing the system link labview APIs on the RT target. Do you know if there is a way to manually add the system link labview APIs to the NI Linux RT?
I am actually trying this in a very basic veristand model. See the screen shot below. My biggest question here is that this VI obviously calls the SystemLink API, so I can see how this wouldnt work since there isn't an option to install this SystemLink API on the RT target when I try to install software in NI MAX. Can you help me understand how this is expected to work without installing the SystemLink API on the RT target? Do I need to install it manually perhaps?
Theoretically, you can do file I/O and network comms in a lv model.
But you really shouldn't -- because we treat all models as deterministic and so any network comms or file I/O can wreak havoc.
Instead we would recommend creating an async Custom Device for this code, as explained here:
and be sure the build spec for building this is set up correctly.
This approach will get you where you need to go fastest.