Leah's LabVIEW Blog

Greetings LabVIEW friends, Yesterday I decided to have another go at LabVIEW on Linux, to see if I could help make Antidoc compatible with Linux machines. I decided to use Ubuntu because it's compatible with LabVIEW and still fairly popular. I started off with several failed attempts: I dug around for my old Raspberry Pi 2B+ which was running Ubuntu and I'd already installed LabVIEW on, but it looks like I must have left it at work before I got made redundant last year. 😕 RIP. I borrowed my fiancé's spare Pi 4B and put Ubuntu 22.04 LTS AMD64 on an SD card using Balena Etcher, but it wouldn't boot from it. I switched to Raspberry Pi Imager to prepare the SD card and got my Ubuntu up and running. Success! But when I went to install the LabVIEW 2023 Q4 package I realised the new Pis use ARM architecture and LabVIEW doesn't support that. Also explains why I didn't have any success with that AMD64 ISO... I decided to use Hyper-V to make myself a VM... nope, I am usi...

This year I did Advent of Code  again for the second year running. If you're not familiar with it, it is a set of daily language-agnostic code challenges during December. Here are some thoughts on my experience this year.

Do you use the LVCompare diff tool? I do, all the time now. If you haven't used it before, it's like playing spot the difference between 2 versions of the same VI but LabVIEW will list what is different and take you to the location of the differences. It's great. My favourite uses are: Double checking before committing files that what I think I changed is what I actually changed, to make sure I have good commit notes and didn't do anything by accident Especially when I see a file listed that I didn't think I did any work on... This normally results in reverting it after checking what the difference is! Understanding what someone actually changed, usually when doing code reviews or pull requests If I find what looks like 2 versions of the same file, checking they are actually the same. I had the tool set up to work with my Git GUI of choice, TortoiseGit. I would normally run it by navigating to Windows Explorer, right clicking on a file or a log entry and selecting w...

Nowadays at work I get to use LabVIEW 2020, which has some great inbuilt shortcuts. One of these is 'Arrange VI Window'. Arrange VI Window was added into LabVIEW 2019, but can be downloaded for earlier LabVIEW versions here . The default QuickDrop shortcut is Ctrl + Space, Ctrl + F . It does many things apart from arranging the windows - moving the origin to (0,0), aligning controls on the front panel to match the connector pane ('clean up front panel'), and resizing the windows to fit the code or as much code as possible with a small border. These are all great. But I was after something in particular that it didn't seem to provide.

I had been looking forward to GLA summit for months, so much so that I booked the time off work so I could concentrate fully!   There were so many great presentations, but some personal highlights for me were:

So there's a lot of takes on why some people hate LabVIEW. Here's mine. I have a friend who is an engineer and had been asked to learn LabVIEW for a work project. 'Oh goodie', I thought, 'someone else to talk LabVIEW with!' But to my sorrow, he gets angry even when the word 'LabVIEW' is mentioned. He hates it. 'I can't find the examples. It's so slow to write. I can't get it to work.'.

This is the final post about the MLUG Beer Money challenge: if you are lost, start here . The first solution method that I describe isn't particularly fast, but it is fun.

This is Part 2 of the beer money problem, see intro and Simple Nested Loops Solution (#1) . Recursion - yay. Having a VI that calls itself that calls itself that calls itself... then finally breaks out. 

This post is about my first attempt at answering the MLUG beer money challenge outlined in this post . So, where to start? After grappling with this problem for a while, I decided to type up exactly what I was doing when trying to solve it on paper, and go from there.

I like a good coding challenge, and this one is particularly fun. It was set by the wonderful folks at MLUG and goes like this: I went to the supermarket to get some beers for the Euros final and my bill came to £11.99. With the money detailed [below], how many combinations are there that make up the exact change to pay my bill?  

  So I realise that VI Week happened a couple of months ago, but I didn't have a blog back then. Better late than never!   I attended a couple of the sessions 'live', and have caught up with others afterwards. The recordings were handy for when I was busy or at work... or when the meeting had reached full capacity. (Great to see that serial comms drew such a crowd!)  It was surprising how different a 'live' session felt to a recorded session, with the messages pinging away and faces looking back at you on webcam. It felt exciting and personal. Next time I'd definitely try and attend more of the sessions 'live'.   Here are some things that stood out for me from the sessions that I watched:   Proper way to communicate over serial -   I've written a couple of serial drivers in the past, and this talk really helped me organise my thoughts by categorising serial protocols by their data format and response type. I'll be ...