04-27-2023 06:04 AM
Hello there!
I‘m desperately trying to get LV running on my Raspberry Pi 4B.
I first tried to download the standard LabView programm to the Raspberry with translation layers. (So that the programm thinks it runs on a windows/ x64 machine) - that didn‘t worked as expected.
You‘ll may ask yourself, why didn‘t I used Linx or the hobbyist toolkit - And I can just say that I liked the idea of running the standard LabView programm 😉
But I want to proceed with my project for which I need some sort of possibility to run a LabView code on a RasPi. So far so good.
Furthermore I‘d like to use the Raspberrys USB ports for communication with a motor and it should run headlessly without the Raspberry being connected to a PC (that would work but would also kind of defeat the usage of the Pi…)
After all this buildup my question: Is it possible to succed my expectations with the Linx toolkit or with the hobbyist toolkit ???
Thank you very much in advance for any respond !
Dirac5
04-27-2023 11:04 AM - edited 04-27-2023 11:04 AM
I don't understand. Are you having an issue? or Are you asking question?
Your question "Is it possible to succed my expectations with the Linx toolkit or with the hobbyist toolkit ??"
My answer would be: Give it a try and see what happens. I personally learn by doing. Learn by doing is one of the best, most effective ways to learn.
Also, it would be nice to let us know what you have accomplished and where you are now.
04-27-2023 12:16 PM
Thanks for the respond!
Im just asking questions, trying to avoid wasting time with testing.
Yes, I‘d prefer to just try it out, but I‘m in kind of a hurry because the project (for university) needs to create results - otherwise I won‘t be able to do further developement .
If anyone could just say: Yes, its possible to run a pi without an ongoing connection to a windows PC and to use the pis USB ports in LabVIEW, just like I‘m used to do with a normal PC.
Or negotiate this - I‘d help me a lot!
Nevertheless I will report if or what worked, if I‘m faster than any response!
04-27-2023 12:29 PM
I see. No problem, but while you are waiting for an answers, you can always try it to save yourself time. You are in good position to try it out, you have LabVIEW and you have hardware. Many people in here may not have the hardware that you have.
04-27-2023 06:13 PM
Long story short, if you're depending on this to be a robust solution for a university project, experimenting on unofficial combinations of hardware and software isn't the way to go. Just use LINX with LabVIEW (Hobbyist Toolkit is only for Community Edition - although they really are the same thing). Develop on the PC, deploy to the target (RPI).
04-28-2023 05:22 AM - edited 04-28-2023 05:32 AM
Please don’t recommend to install the Linx Toolkit in LabVIEW 2020 and later. That will certainly cause problems. If you use LabVIEW Professional or Full 2020 or later you should install the Hobbyist Toolkit.
And yes it allows to run a LabViEW program. But accessing USB in this way is not trivial. If it is in reality a virtual serial port things should be quite easy, but if you expect to do this over a different USB protocol, you may want to reconsider if your are constrained in time.
Headless LabVIEW development (your LabVIEW executable foesn’t really have an front pannels once you deploy it to the Raspberry Pi to run there on its own) is a considerably different development experience than what you are used on your PC. So if your time is really that limited, you may want to reconsider and maybe rather use an Intel NUC or similar device, which gives you a much more familiar debugging experience.
04-28-2023 07:57 AM
@rolfk wrote:
Please don’t recommend to install the Linx Toolkit in LabVIEW 2020 and later. That will certainly cause problems. If you use LabVIEW Professional or Full 2020 or later you should install the Hobbyist Toolkit.
And yes it allows to run a LabViEW program. But accessing USB in this way is not trivial. If it is in reality a virtual serial port things should be quite easy, but if you expect to do this over a different USB protocol, you may want to reconsider if your are constrained in time.
Headless LabVIEW development (your LabVIEW executable foesn’t really have an front pannels once you deploy it to the Raspberry Pi to run there on its own) is a considerably different development experience than what you are used on your PC. So if your time is really that limited, you may want to reconsider and maybe rather use an Intel NUC or similar device, which gives you a much more familiar debugging experience.
Thank you for that knowledge update. I didn't know that Hobbyist Toolkit existed as a standalone product.
04-28-2023 03:36 PM
@billko wrote:
Thank you for that knowledge update. I didn't know that Hobbyist Toolkit existed as a standalone product.
Seems however to be for LabVIEW 2021 and greater. May have remembered the cutoff point wrongly.
04-28-2023 07:49 PM
@rolfk wrote:
@billko wrote:
Thank you for that knowledge update. I didn't know that Hobbyist Toolkit existed as a standalone product.
Seems however to be for LabVIEW 2021 and greater. May have remembered the cutoff point wrongly.
Minor detail compared to the major update to my knowledge update.
04-29-2023 04:35 AM
Hi
NI has written a detailed page about this confusing subject :
Both solutions are designed to be generic hardware abstraction layers for embedded devices, rather than designed for just one specific microcontroller platform.
They allow for communication with hobbyist hardware like Arduino, Raspberry Pi, BeagleBone, chipKIT, and others.
None of these options is supported with LabVIEW NXG.
Regards