Bryan

Guess who's back? Back again? Spammers back. Tell Admin...

Just checked and it seems responsive for me. I'm not on it as much as I am on LAVA though.

I was relieved to login this morning and not see pages worth of spam when I clicked on the "Unread Content" link. Awesome job to all!

I was interested in downloading it to have a look. However, the download page will not accept an email address from providers such as gmail, hotmail, etc.

Using an old SFX installer is likely the case. I don't recall deleting anything, but my C:\National Instruments Downloads directory is empty.

Below is a snapshot of all of the RTE installers shown when I un-check "Automatically select recommended installers". As you can see, I do have the 2018 SP1 f4 (64-bit) RTE. With that I am able to BUILD an installer, but I haven't checked to see if it would work properly on a target machine. I don't have any 64-bit versions of the LabVIEW IDE installed. I'll bet that this is the RTE installed with my install of VIPM (I'm using 2020)

I maintain several machines in our factory, all running various versions of LabVIEW executables. One of the many versions I have installed on my machine is LabVIEW 2018 v18.0.1f4 (32-bit). It's been 'many moons' ago, but I remember updating my 2018 runtime to SP1 f5, but I haven't had to build an installer in 2018 since then. I ran into a situation yesterday where I needed to create an installer in 2018 and left "Automatically select recommended installers" checked, which auto-selects the 2018 SP1 f5 RTE. When I select "OK" in "Additional Installers", the "Select Source" dialog appears with a single entry, which is a 2018 application that I had built and installed on my local machine. Clicking on "OK" prompts for a media path as expected, but I don't have (or can find) and installer for 2018 SP1 f5. Even pointing it to the installer it's referencing (that I created) gives me an error message stating that the "...media you have provided is a different version of the requested media" (which it isn't). I ended up giving up on creating an installer in 2018 and recompiled everything in a later version of LabVIEW since I needed to get an update deployed immediately. However, I am curious whether anyone has any insight into this. I can't be the only one to have seen it.

Mads' VI will give you the 'address' of your search value (row and column index values). You can use those values with the "Index Array" function to return an entire row or column.

So, you have no interest in joining the Illuminati or occult to be free from poverty and ancestral curses without a human sacrifice? Personally, I prefer my sacrifices to be as human-y as possible.

I use the "Unread Content" link almost daily, and it appears that spammers are still hitting the forums pretty hard as that's where I see the most evidence. I don't know if new account creation was turned back on, but if it hasn't yet, it looks like they're still finding a way.

LabVIEW has been my forte throughout my quarter-century or so of employment. It's what has made me most valuable to present and past employers, (and is what I enjoy doing the most). My only real concern at this point would be in finding another job within my purview, that wouldn't require me to relocate my family, should I not be able to continue working for my current employer. In the current state of things, I'm not concerned - but often wonder if I should be.

I'm glad it worked for you! Unfortunately, I haven't attempted to install NI Device Drivers at this point.

Looks like I was able to get the Zorin16/LabVIEW 2018 example quicker than I thought:

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.

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.

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.

Well, now I've learned two new words. Thanks!

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.

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.

You're very welcome! The Community edition for Ubuntu should, (I emphasize, should) hopefully install without any modifications to installation scripts.

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.

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

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.

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