DAQmx package #3
Comments
|
Is there a chance you installed the 32bit version of NI MAX? |
|
It is possible. My system is 64bit. Since I have the NI device working in Bonsai32 reliably now, this is not a major issue for me. But it would be nice to know why I am running into this and whether it is an issue with how I am installing, etc. Are there any downsides to working with the Bonsai32 version? Seems weird to do since my Windows is 64bit? Thanks! |
|
@neurologic Even when using a 64-bit version of Windows, it is still possible to install and run applications and drivers compiled for 32-bit architectures. Windows will support both, but a 32-bit driver or library will only work with a 32-bit application, so you cannot mix and match. It is likely that the NI-DAQmx installer sets up both 32- and 64-bit versions of the drivers, to ensure they work with any application in the computer. What may be happening is that there is some missing or conflicted dependency that is missing for the 64-bit drivers. I am moving this discussion to the DAQmx package repository, so we can continue pinning down the problem, but in the meantime, can you check if something like the following path exists in your system? C:\Program Files (x86)\National Instruments\MeasurementStudioVS2010\DotNET\Assemblies (64-bit) |
|
I'm having the same problem. The NI-DAQmx installer specifies an Application Bitness of 32 and 64-bit, but the list of supported operating systems are all 64-bit, so I assume I have the right version installed. The directory you mentioned is present on my system. |
|
I'm also having issues, potentially caused by the same problem. I'm migrating computers and trying to reinstall the National Instruments DAQmx package. However, after installing the package, the nodes do not show up in the Bonsai toolbox. When I try to open a workflow with DAQmx nodes included, I get this error:
This issue has been described in multiple previous posts, but none of the solutions are working for me. I've made sure the National Instruments .NET Framework support is installed. I've also tried replacing the package folder in AppData with one from a working installation on a different computer, including NationalInstruments.DAQmx.dll. The problem persists in 32bit as well as 64bit applications. I'm using NI-DAQmx version 2022 Q4, and Windows 11 Pro for Workstations version 10.0.22000.1219 |
|
I was also using 2022 Q4 – could it be a problem with recent NI-DAQmx installs? @glopesdev which version do you have on your dev machine? |
|
@jsiegle I just checked and it looks like 2022 Q4... and the nodes do show up (here's a side-by-side screenshot):
This specific computer is a Windows 10 Pro machine, but I actually developed the new package version on my Windows 11 Pro laptop (also working) so I'm also scratching my head a bit at what the issue might be. What I would do next is trace down which exact dependency is failing to load so we can pin down the problem. If you can collect some assembly binding logs as detailed below on the affected machines we should hopefully be able to learn more: https://stackoverflow.com/questions/17681432/how-can-i-enable-assembly-binding-logging |
|
I just installed the DAQmx package on a different computer and everything was fine. Will try to collect the assembly binding logs when I'm back in lab on Monday. |
|
Here's what I get from fuslogvw. Looking in |
|
Yep, seeing the same thing. It doesn't seem to contain any info about which file could not be found. |
|
Hmm, these tools can be quite painful to configure correctly unfortunately. Was checking that maybe there is this alternative: https://github.com/awaescher/Fusion Looks active and maybe more intuitive to get right. |
|
Based on the Fusion output, it seems like it could be looking for |
|
Ok, the DAQmx operators are showing up when I run Bonsai32.exe...any idea why they're missing for the 64-bit version? |
|
Thanks @jsiegle now we are on to something. This line is key: These assemblies are meant to be in the GAC (Global Assembly Cache). They are usually put there by the NI installer. Many years ago there were two versions of the installer, one for 32-bit and another for 64-bit. I believe they are now bundled together but it's worth double-checking. Can you try uninstalling and reinstalling the NI software on that machine? I'm wondering if it could be something like the .NET framework not being installed at the time the NI software runs so it skipped that step. |
|
I did indeed install NIDAQmx before Visual Studio, but uninstalling and re-installing didn't fix the problem. |
|
Reinstalling the entire NI software suite didn't work for me either. |
|
Hmm, I'm a bit at a loss as to what is going on here. At this point if I had access to the machine I would just start exploring in different places to understand what is being installed and uninstalled where. For example, it is possible to view the contents of the GAC using this tool: https://learn.microsoft.com/en-us/dotnet/framework/tools/gacutil-exe-gac-tool There must be some logic as to why dependencies are not ending up where they should be, but it's not clear to me. I wonder whether the NI support forums could help at some point. |
|
I'm happy to grant you remote access to my machine if that would be helpful, Gonçalo. I'll try running gacutil later today. |
|
Here's the NI block of the output of
and another block here meanwhile here's the contents of |
|
I just reinstalled the Bonsai DAQmx package (which it looks like was updated today), and no longer get the 'could not load file or assembly' error. Now I have the same problem as OP, the nodes just don't show up in the editor in either 32 or 64 bit. I also tried going back and repairing the NI-DAQmx .NET drivers to no effect. |
|
Finally got the package to work by reverting the National Instruments software to version 19.0 (2019). |
|
Worked for me too! FWIW, I initially tried v19.6 and the DAQmx package still wasn't loading. So something happened to the NI library in the course of 2019 that made it incompatible. |
|
This is interesting since the only driver we have installed in our test computer is the 2022 Q4 driver and it works well for Windows 10 Pro 🤔 would be really curious to understand why it works for us and not for you, but it's good to have a workaround to test. It's possible to upgrade the DAQmx dependencies in the package but it could then break legacy installs with earlier drivers. Will keep an eye out for this one. |
I (and others) have ran into a problem consistently when installing the DAQmx package.
Steps to get to issue
Expected Behavior
Be able to find the Analog Input node in the DAQmx menu in the workflow editor
Issue
The DAQmx menu is not included in the workflow editor tools menu even after install with no error feedback.
See the google groups discussion. I forget if there were other threads in which it was discussed.
**and not having the nodes show up in the editor) when doing a fresh install of Bonsai (after messing up the old one somehow) on my computer.
Solution?
I have gotten it to work by unknown means in the past, but today I found something logical that consistently 'solved it' for me.
I did not notice this before, but when Bonsai.exe download does the install, it makes TWO separate 'Applications' that are stored in the default (for me user\AppData\Local\Bonsai). One of them is called Bonsai and the other is Bonsai32. I don't know what the difference between these is on the backend. But, after installing the DAQmx package, if I run the Bonsai32 application the editor has the DAQmx nodes, while if I run the Bonsai application the DAQmx nodes are nowhere to be found in the menu.
Hope this helps.
Let me know if anyone knows the "why" on this (or has other solutions).
The text was updated successfully, but these errors were encountered: