LabVIEW
Compatibility Windows 11 Labview 2018/2021 FPA RT MyRIO
Hello 38400,
The posts above are correct—the latest available version of the NI myRIO Software Suite (and its Toolkit) is from 2021. While it's not officially supported on Windows 11, some users have reported success running it; however, since it hasn't been tested against that OS, results may vary depending on your setup.
That said, if you're open to programming the NI myRIO as you would any other NI RIO device (such as a Single-Board RIO or CompactRIO), you can use the latest NI software that is compatible with Windows 11. This involves installing LabVIEW, the LabVIEW Real-Time Module, the LabVIEW FPGA Module, and NI CompactRIO. Once set up, the myRIO will appear as a standard NI RIO target in LabVIEW. You can find more details here: Adding RT Targets to a LabVIEW Project
Keep in mind that without the myRIO Toolkit, you won’t have access to the precompiled FPGA bitfiles, express VIs, or the myRIO discovery application. However, the device remains fully usable with LabVIEW RT and FPGA—just with a more manual workflow and a reduced set of tools.
We truly appreciate your patience as we continue to evolve and strengthen our academic offerings. Your feedback and engagement are incredibly valuable as we work to support educators and students alike.
Cheers,
I have used the myRIO with the stock CompactRIO driver several times. It works perfectly but does not provide the drivers and examples that come with the specific MyRIO Software Suite installation. It shouldn't be to difficult to install the MyRIO Software Suite separately and extract the according examples and support functions to use with the stock CompactRIO driver.
The major difficulty is however that with newer LabVIEW FPGA setups (2022 and newer) you ultimately run into difficulties with the available memory on the Xilinx Zynq based RIO devices. This includes also all the other ARM based RIO platforms:
- myRIO (1900, 1950)
- roboRIO()
- cRIO(906x)
- expansion Chassis (9145, 9147, 9149)
- sbRIO boards (9607, 9627, 9637, 9651)
Theoretically it would be relatively simple to have all of these support quadruple the amount of memory than what they are shipped with (256 MB), as the according Zynq 7020 chip supports addressing up to 1GB of DDR3 memory directly. The according memory chips would not cost anymore in fact than what is used now. However it is probably a passed station as the Zynq 7000 platform was considered to be in a mature product life cycle.
But in October 2022 AMD released a statement that they intend to extend the product life cycle of the Zynq 7000 SoC portfolio together with most of the other Xilinx 7 Series offerings until at least 2035. So maybe NI could reconsider their earlier decision to just discontinue all of the Xilinx Zynq 7000 products. With a minor redesign these platforms could all be upgraded to go on for many more years and the current pricing could also be adjusted. Yes downwards, because what they are based on now is the situation of the chip shortage caused by Covid and prices of most components have considerably come down since then again!
The sbRIO-9651 used to cost around $ 700 before Covid and sells now for $ 1600. It could easily contain 4 times as much memory and use a much higher speed grade SoC without costing even nearly as much to sell.
Hi
I can confirm that the base image with CompactRIO 2025 Q1 supports LabVIEW 2025 Q1 in myRIO :
I then used my trick to 'install' myRIO Toolkit support in LabVIEW 2025 Q1 by copying the myRIO related files over from LabVIEW 2021 SP1 as I have described in a thread in the myRIO forum.
The RT project template ran without issues.
The FPGA project template also started its FPGA code preparation but aborted in the step 5 of 5 with this error :
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
Error 7 occurred at Open VI Reference in niFpgaTopLevelGenCallTargetSpecificVI.vi->niFpgaHandleConstraintsAndMiscFPGAFiles.vi->niLvFpgaTopModGen.vi->niLvFpgaTopModGen.vi.ProxyCaller
Possible reason(s):
LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
VI Path:
<Not A Path>
in C:\Program Files (x86)\National Instruments\LabVIEW 2025\resource\RVI\StockIO\private\topModGen\niLvFpgaTopModGen.vi
Google found another user with a similar problem for another device type :
https://ergosterin56.rssing.com/chan-24376831/all_p9804.html
Regards
