09-07-2024 01:26 PM - edited 09-07-2024 01:42 PM
You need to consider also the time a post was written, 10 years ago the statement that LabVIEW code can’t run on an ARM CPU was pretty true. Then NI released their Zync based RIO targets and things weren’t as clear cut anymore. And then came the Lynx Toolkit that muddied the waters even more.
The Lynx Toolkit allows to use a Raspberry Pi as target to execute a LabVIEW program. But it doesn’t run the LabVIEW IDE. It installs a special VM environment on the Raspi in which the LabVIEW executable developed on a Windows PC can run. This is a separate minimalistic Debian OS on the Raspi which has only limited access to the file system and none to the display, so you can’t see the VI front panel on the display attached to the Raspi if you have one.
So yes you can deploy your LabVIEW program to the Raspi with the Hobbyist Toolkit but:
- you have to develop it on a Windows PC and compile it there
- you have only access to a subset of the file system on the Raspi
- there is no UI to watch your program frontpanel, it runs literally in the dark once you let it run on its own and not from within the LabVIEW IDE on your Windows PC
- the Toolkit offers a number of functions to access the built-in analog and digital pins and also I2C and SPI interfaces but has limitations in terms of on which pins you can have these
- it tends to have difficulties with more modern hardware (eg. Raspi 5) and 64-bit Raspian OS.
- NI has difficulties to commit any resources to this project and the limited progress in the last few years seems to be from community members and very few NI employees who spend time on this project rather despite NI than because of NI.