11-10-2023 11:09 PM
Hello,
I have been using LabVIEW for a while, but I am new to VeriStand. I got a new cRIO controller for more robust real-time performance without Windows hiccups. I need to start using VeriStand custom devices. I will use VeriStand APIs in a LabVIEW program running on the host PC to control various devices using the VeriStand Engine. I took a look at an example LabVIEW project shipped with VeriStand 2023 in the following folder as it looked simple.
C:\Program Files\National Instruments\LabVIEW 2023\examples\NI VeriStand\Custom Devices\Communication Example
I opened Example Client.vi and followed the instructions. I verified that Configuration and Engine libraries were created in the following folder by building their Source Distribution.
C:\Users\Public\Documents\National Instruments\NI VeriStand 2023\Custom Devices\Communication Example
I created a new VeriStand project and added the Communication Example custom device in System Explorer. Target’s Operation System is Windows and its IP address is localhost. I press Deploy and run the Example Client VI. It works fine.
Now I want to deploy the example system definition file to the cRIO RT target. Target’s Operating System is Linux_64 and IP address is 169.254.148.39. I press Deploy and get these error messages.
Any guidance would be appreciated.
11-11-2023 06:46 AM
Did you create the custom device using the template shipped by VeriStand or niveristand-custom-device-wizard
The custom device XML should define SupportedTarget of Linux_x64. You should also need to build Engine Release for Linux_64.lvlib. See Create VeriStand Custom Device for Real Time Target
11-12-2023 04:07 PM
Thank you for the pointers. The custom device is one of the examples that came with VeriStand. I didn't use any template or wizard. It seems I have to digest more basics first to make sense of it.
11-13-2023 11:35 AM
Have you edited your VeriStand system def (press the config button) and clicked on hardware to set the IP for the system def to deploy to?