DAQ Assistant not initializing correctly

[ry78]

Hi all, I'm having problems with the DAQ Assistant vi opening correctly. I can get the vi graphic to display easily enough on the block diagram. Although it's without the connection points for the wires and properties/options window. I cannot open the vi from the graphic. I've tried reinstalling software and daqmx drivers to no avail. Attached is a picture of what I see.

Side note, when I double click on the DAQ Assistant graphic another box does open, and it appears to be loading items. If I'm quick and click on browse it seems to be trying to locate "DAQmxAssistant_nimaglvu.dll".

Any thoughts?

Thanks again

Ryan R.

 

[Bob_Schor]

Hello, Ryan.

Most of us know what the DAQ Assistant VI looks like (though I stopped using it more than a decade ago, and would advise you to do the same).  What we don't know is the following:

• What version of Windows are you running?
• What version of LabVIEW are you using?  Tell us (please) the Version number and if 32 or 64-bit.  Note that many of the more experienced developers are not using the latest versions of LabVIEW (I'm mostly using LabVIEW 2021, for example).
• Did you install LabVIEW yourself?  Installing and uninstalling LabVIEW can trip you up (and an over-aggressive uninstall can require a re-installation of Windows -- I know because it happened to me when NIPM was introduced in 2017).

I highly recommend you search the Web for "Learn 10 Functions in NI-DAQmx and Handle 80% of Your Data Acquisition Applications".  Skip the first item, which discusses the DAQ Assistant.  Most "beginner" DAQ tasks require 4 or 5 DAQmx Functions, which are the first ones described.  You basically have to Create Channel, Start,  Read (or Write) (usually inside a While or For loop), Stop, and Clear.  

Do learn to plug your device into your computer, open MAX (the Measurement and Automation eXplorer), and create a Test Panel to (for example) configure 2 A/D channels to take Continuous Samples at 100 Hz using a 100 point buffer and a range of -10v to +10v.  MAX will let you start and stop this "task" and show you the results, so all you have to do is "the same things" using the simple DAQmx commands mentioned in the previous paragraph (plus add "visualizing" code, for example by wiring the output of the A/D Read to a Chart display).

So I've touched on two things.  One is the problem you asked about, getting the DAQ Assistant to open.  If this is due to an "installation problem", you may need to (safely) uninstall LabVIEW, then re-install, choosing only the packages and options that are appropriate for your needs (I recommend not selecting everything on the "Additional" (last) sheet).  I also recommended not using the DAQ Assistant, but using the DAQmx functions directly -- it is not that difficult.  You can also open LabVIEW Help and search for DAQmx, where you'll find lots of code provided by NI that has far too many Bells and Whistles shown, but you can edit out the features you don't need.  Note when you open an Example, the first thing you should do is to rename it and save it in your "My Documents\LabVIEW" folder somewhere -- you don't really want to directly edit the "demo" code that NI provides.

Bob Schor

[ry78]

Hi Bob, thanks for the response. To answer your questions; 

- I'm running Windows 10 Pro

- Labview 2018 Version 18.01f4 (32 bit)

- I did install it myself and had problems. I wiped windows, tried it again and now I'm here.

My other computer is running Labview 2010 it works great, I don't have nearly the issues. I'm starting to regret the upgrade. When you acquire software you expect it to work fully.

Ryan 

[Bob_Schor]

Hello, Ryan.

     2017 marks an important date in LabVIEW installations -- the birth of NIPM, the program that manages installing (and removing) LabVIEW.  I'd been running LabVIEW for a decade by this time, and handled multiple installations (for myself, my colleagues, students to asked "can I install LabVIEW on my laptop?", to which I answered "Yes, but bring your laptop to me and let me o it for you".

     Up to 2016, the "rule" for multiple versions of LabVIEW was to "install the oldest first", and install in "version sequence".  When I wanted to "sunset" a version, I usually completely uninstalled LabVIEW, then reinstalled (oldest first) the versions I wanted to use.  I also installed in a particular order (drivers last).

     All went well until 2017.  Made my first mistake in trying to "start over" when the installation didn't work -- ended up ruining my PC, so I saved everything, wiped the hard drive, and reinstalled Windows, my apps, my data, then LabVIEW (2015, 2016, and 2017).  Whew.

     Then came LabVIEW 2018.  Took me 3-4 months of trying to install (what I called) "Quad LabVIEW".  Worked with NI Software Support (I'm sorry I don't remember the name of the wonderful Tech Support person to helped me).  She bugged the Developers, and told me I needed to install LabVIEW 2018 first, then 2017, then 2016, and last 2015.  Of course, with 10 years experience, I knew better, but when it still didn't work, I tried a "reverse installation" -- and it worked!

     And now Windows 11 is coming, and we'll all be moving to LabVIEW 2023 or later.  But while you still have Windows 10, you should be able to install LabVIEW 2018 (32-bit).  On the Installation screen, install only the drivers you need, and pick and choose from the "Additional Features".  "Modern LabVIEW/NIPM" really does go pretty smoothly, particularly if it's the only version you are installing.  

     Good luck.

Bob Schor

[ry78]

Ok Bob, I'll try a few different methods this weekend along with some pointers you suggested. I will only be installing one version of Labview on this computer. That hopefully will make it less painful. lol

Thanks

Ryan

[ry78]

I have an update regarding the above issue.

I have tried numerous installation methods, driver selections and starting over by wiping of the hard drive. I keep getting the same issue. I have found a temporary work around. I manually point the pop up dialog box (selecting "browse" button quickly) to the correct file location. On my computer it's "C:\Program Files (x86)\National Instruments\MAX\Assistants\DAQ Assistant\common\supportFiles\DAQmxAssistant_nimaglvu.dll". Not sure yet why this is an issue. I'm curious to know where it's expecting this file to reside. But I now have the DAQ Assistant up and running. 🙂 I just have to select the file every time I open up the DAQ Assistant. Minor annoyance, but luckily I don't use it that often.

Curious to know if there are any other suggestions?

Ryan 

[ry78]

Update 2.0

Adding to my previous post. Found the file path Labview was looking at. "C:\Windows\System32\DAQmxAssistant_nimaglvu.dll" The file obviously was not located there. Found the file under another directory. I copied and pasted the .dll file into the system32 folder.

Noticed it was then moved to "C:\Windows\SysWOW64\DAQmxAssistant_nimaglvu.dll" after a computer restart.

Now DAQ Assistant works successfully. I'm curious how many things I'm going to upset by doing this. 🙂 

Ryan