10-18-2024 11:14 AM
I have the ehternet port on my laptop statically configured to 192.168.1.224, it is direct connected to eth0 of the pi. After I downloaded and installed your 2024 image on my pi, I booted it and during to the boot process it shows on the screen the NetworkManager-wait-online.service failed to start. If I can statically configure the pi eth0 to 192.168.1.223 it will be on the same subnet and I should be able to connect I had hoped. I do not a have a wired connection with a router on my server since I am on Starlink.
10-18-2024 12:19 PM
Hi Ken,
I see the Target Configuration wizard and I am connected and working on the Blink example, thanks for the help!
11-04-2024 12:19 PM
Hello,
Apologies for the nOOb question - once I install LabView on my Raspberry Pi 4, should I be able to run labview from the Pi directly, or from my Windows computer?
I have installed this experimental solution and the Pi boots into a coding screen not the UI which is a little above my level. Is this what it is supposed to do?
Thank you!
11-05-2024 12:53 AM
No problem Larmander, you will be able to run LV code on the Raspberry Pi similar to a real-time target. So if you download a executable to it you can have it run without UI or you can connect a host application through network.
11-05-2024 09:49 AM
Hi JonasM, thank you for your helpful response!
I noted a short while after posting this that the images on github are lite which I understand has no GUI.
I have my Pi plugged in, my sensor plugged in to power and my Pi, and I am able to get to this screen in labview - should I be able to go now?
I am reading this and it seems very intimidating - does this apply for the RPi 4? Introduction to Modbus using LabVIEW - NI
Also, why does LV think I'm running a Pi2? Is that just the one they have a picture of?
Thank you!
11-05-2024 09:59 AM
The LabVIEW runtime on the PI runs in its own chroot which is a sort of lightweight virtual machine and has no access to the monitor. So even if you would install the non-lite version, you could connect a display to the Raspi, but the LabVIEW VI running on your Raspi won't be visible on the display. It is running in "the Dark" just as with other LabVIEW embedded targets like the cRIO and sbRIO hardware.
And yes the Linx Toolkit was created around 2014 when the Pi2 was the newest and greatest board available. The image was never updated and nobody ever bothered to have it adapt to the actual Raspi connected. The Toolkit was however updated to work with Pi3 and Pi4 after 2021.