10-11-2022 03:29 PM
I'm a long term user of LabVIEW but haven't used it for 2 years since I switched employers. I am new to Veristand. We are evaluating the capabilities of Veristand and CompactRIO to solve some product development challenges we are facing. The problem I'm having is I cannot locate the functionality that I read about and my technical sales representative was talking about when I had a pre-sales call.
We purchased 2 NI CRIO-9063 chassis and NI9381 modules to create a working demo project with. I'm following the steps outlined in the New Getting Started with Veristand Tutorial When I get to the Installing Software on the RT Target I cannot find NI VeriStand Engine in the list. I just found this link for Real-Time Controllers and Real-Time Operating System Compatibility at the bottom of this Tutorial and I find that my CRIO target is NI Linux Real-Time (Arm-based) which I assume is 32-bit on does not meet the requirements of VeriStand 2021.
I also cannot find the template in LabVIEW to create a FPGA project. They are supposed to be in the vi.lib/NI VeriStand/FPGA folder but I notice these files are only in the 64-bit version of LabVIEW.
I imagine I could go back to Veristand 2020 or 2019 and do what I want but I cannot evaluate this option since an evaluation only allows the latest version of SW. Is there any solution that would allow me to get this working ahead of me spending the money for the HIL and Real-Time Test Software Suite for one year just to find out what we are hoping to do is not possible.
Thank you,
Brad Retzlaff
Solved! Go to Solution.
10-11-2022 06:11 PM
HI bradretzlaff,
Unfortunately, cRIO is not supported on the 64-bit LabVIEW Real-Time module yet. You would need the 32-bit LabVIEW, LVRT and LVFPGA to create the FPGA bitfile. See Announcing VeriStand 2021.
I would recommend you reach out to our sales representative and request for temporary evaluation activation code for VeriStand 2020.
DISCLAIMER: The attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system, or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense