Leah's LabVIEW Blog

 Greetings LabVIEW nerds, It's been a while! I've been busy. You see, recently I've been working on a re-use library that has the potential to be used by any LabVIEW developer within the organisation who is in a manufacture or test role - in fact, it could be included in every jig. So considering the number of people who might use it, it's worth taking the time to make it nice and developer-friendly. I've spent many hours writing the documentation, unit tests, examples, etc. Even to the point that I did a re-write to remove all dependences. (I hadn't realised that different versions of OpenG would cause headaches for people, oops.) Something that I sought advice on was my folder structure for my library. I had always been on team ' Project Explorer structure mirrors the disk ', but when it came to where my Unit Tests, VI Tree, Examples etc. lived, I couldn't make my mind up. And moving them around isn't an easy task. Top tip: You can click on a ...

Virtual Machines has always sounded like an awesome idea for developing. No unexpected dependences sneaking in, a clean version of LabVIEW and drivers for each project, what's not to like? And no more poking through the dusty PC graveyard every time I want to test an installer.

It's 1 year now since I graduated and started work! So a good time for reflection.

Hello LabVIEW friends, Sometimes it can be very useful to know where a bit of code is used or called from. There's several ways of doing this in LabVIEW: Find Callers, Find All Instances and VI Hierachy to name a few.

I wrote 'Toaster for LabVIEW' in my free time, back when I had just started full-time work. You see, I was eating my breakfast at work, but we didn't have a toaster so it was breakfast sandwiches for me. Sad violin time. At least I could open up my LabVIEW Toast Simulator and imagine I was eating toast...

  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 ...

  "0".."9","9"  ... Looks kind of dumb, right?   This is the kind of thing that if you know it, it is boring. If you haven't seen it before, you might learn something.