Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Bryan last won the day on November 6 2023

Bryan had the most liked content!

1 Follower

Profile Information

  • Location
    Land of Confusion
  • Interests
    Stuff and things.

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since

Recent Profile Visitors

6,519 profile views

Bryan's Achievements


Contributor (5/14)

  • Conversation Starter Rare
  • Dedicated Rare
  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges



  1. Looks like I was able to get the Zorin16/LabVIEW 2018 example quicker than I thought:
  2. I don't know if this helps in any way, but I wanted to see if I would see similar behavior with LabVIEW 2021SP1 CE on my Linux Mint 21 installation - and I did not. You had mentioned that you were using LabVIEW 2020 (Not officially supported). Does your circumstances prohibit you from moving to a supported version of LabVIEW? If I think about it later today, I'll do this same thing on a Zorin16/LabVIEW2018 VM that I have running at work to see if I see the behavior there. I don't know if it contributes anything other than another data point.
  3. Last time this happened to me (On Zorin Linux), I logged onto my account on NI.com and had to re-activate it there. It's been a while, so I don't remember the details of how I did.
  4. It looks like it's trying to find the DAQNavi.dll in your Windows\System32 directory. Did you confirm that it is there? Also, it looks like your build directory is on your D:\ drive. Is it there and accessible/writable? I'm somewhat old school, so D:\ drives mean CD/DVD ROMs to me, but that may or may not be your case.
  5. Well, now I've learned two new words. Thanks!
  6. I'm just now hearing of the word 'eggcorn' as well. The definition sounds like something that I have often done intentionally while talking with friends for comedic effect.
  7. The solution is in your image on the "Status" line. Activation is required, which means that you have to purchase a license from NI for the module to continue using it past November 23rd.
  8. You're very welcome! The Community edition for Ubuntu should, (I emphasize, should) hopefully install without any modifications to installation scripts.
  9. I saw it under his avatar and thought it was strange, and maybe I had missed an announcement or something, but went with it since, like Antoine Chalons said: it's a selectable option.
  10. I've never used this package, but I figured I would see if I could help a little as the large font seems to convey a sense of urgency. Per the package information release notes, does your setup meet all of the requirements for the package - including having the LabVIEW DSC 2010 or higher already installed? If not, the Data logging & Supervisory Control Module is an add-on toolkit that must be purchased separately from NI. Were there any other errors or messages that may have popped up during package installation? Any additional information you can provide may be helpful to anyone else on here who may have used the module or any developers that may stumble upon this thread. This also appears to have been released back in 2016 - so I'm not sure if there are any compatibility issues that may arise with later versions of LabVIEW (e.g. LabVIEW 2024 as shown under your avatar).
  11. Out of curiosity, what distribution are you using (or considering using)? I've been able to install LabVIEW Community Edition on both Zorin and Linux Mint and created a little "How To" on installation for these two distributions for LabVIEW 2021 Community Edition. FYI - NI has a limited number of distributions for which they support LabVIEW for Linux, mostly those using RPM - but there is some support for Debian based distros, though installation is not completely straightforward.
  12. I've confirmed that this method also works with installing LabVIEW 2021 SP1 Community Edition on Linux Mint 21.2. In the "INSTALL" and "utils/install_helpers.sh" files, replace all instances of "ubuntu" with "ubuntu|linuxmint".
  13. I would hope that if an employer were to say that they were switching to something else, opportunities (and funding) for proper training would also be offered and utilized. Though I know that's not always the case. I've seen first hand (though maintenance and update of LabVIEW code with my current employer) the effects of mandating a new programming language and people learning on their own without training (taken or offered).
  14. When I said at least one, I meant whichever one that I feel would be more beneficial to my own career ambitions, be it Python, Rust, etc. I didn't (mean to) infer that they were generic and interchangeable, (I know better than that). For me though, my introduction and programming experience has primarily been in LabVIEW. Changing my mental process to go from a graphical to a text based language feels like it would be more difficult for me than switching between text-based languages. As I said though, I realize that there are differences ranging from simply syntax to the more drastic.
  15. I've had similar thoughts over the past few years. My introduction to the programming world was LabVIEW. I've dabbled in a few text-based languages, but not enough to become anywhere near proficient. Perhaps I should choose at least one and begin attempting to become proficient as I'm also looking in the 20-something year range until retirement.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.