Random Ramblings on LabVIEW Design
-
cbutcher
on:
LabVIEW in a Box!
-
richardscheff
on:
Influence
-
swatts
on:
TMiLV (This Month in LabVIEW) - Definitely NOT another podcast!
-
Jacobson
on:
AI is going to take our jobs - everyone should panic now.
-
swatts
on:
LabVIEW Firmata - Easy control of Arduino Microcontrollers
-
Dhakkan
on:
LabVIEW OpenSUSE Leap15.5 on a LattePanda V1
-
swatts
on:
LabVIEW and Linux - Intro
-
swatts
on:
It's time for me time.
-
LFBaute
on:
Sneaky Peak and Some Love to Spread (CTI)
-
swatts
on:
News Drop! Community Training Progress, GDevCons
LabVIEW OpenSUSE Leap 15.5 on a little PC
Hello LabVIEW/Linux Lovers
As previously mentioned in this series of articles I will be installing the distro, LabVIEW 2024Q1 and NI-VISA on a Lenovo SFF (Lenovo Thinkcentre M72e Tiny i3-3220T 8GB RAM 120GB SSD. 2.80GHz).
The Intel i3-3220T has a PassMark average score of 1933 which is approximately twice as fast as the LattePanda V1.
I won't go through the install process as it is essentially similar to the LattePanda, but this time I chose the KDE desktop and it is NICE!
I used ScreenConnect to get the images as my TeamViewer license was causing me issues and interestingly ScreenConnect only showed the screen when logged into the root desktop, on the general login it was just a black screen.
I also chose LabVIEW 2024Q1 as it matches well with OpenSUSE Leap 15.5.
Testing with CTI Pico Hardware
How does LabVIEW feel? It feels fine, built the HandsOn emulator into an exe in less than 15 seconds, moving a largish event structures around was fine, user interface moves around screen nicely.
How does the User interface function? Responsive.
How does the hardware function?
One thing I wanted to get my head around was the issue with non-root logins and the discovery of serial ports. Adrian furnished me with a solution.
What we wanted to see was this.
But at first all we saw was lots of question marks and these incremented every time you hit refresh. (root was OK, the cti login wasn't)
This was also observed in the HW Config utility and in a third party utility called cutecom.
As with all things Linux it was to do with permissions and when the login was added to the dialout group and the system restarted all became good.
So we could check what groups the user is in by (my user is called "cti" on this system)
groups cti <-- this displays all the groups that cti is part of.
sudo gpasswd --add cti dialout <-- this adds cti to the dialout group
After a reboot everything worked as expected. LabVIEW works very nicely on the KDE desktop.
Next article I will be doing some very interesting with the on-board arduino on the LattePanda V1 (if I can get it working)
Lots of Linux love
