Why do I receive an error stating that my driver does not exist on the path when trying to run DAQHWINFO with the Data Acquisition Toolbox?

1 view (last 30 days)
Why do I receive an error stating that my driver does not exist on the path when trying to run DAQHWINFO with the Data Acquisition Toolbox?
This happens when using Windows NT or 2000.
The error message is as follows:
??? Error using ==> daqhwinfo
Error using ==> daqregister
Error using ==> daqregister
Unable to load Driver F:\matlabR12\toolbox\daq\daq\private\mwnidaq.dll
The driver does exist on that path.
I have checked that my installation of the toolbox was successful, and I also checked that the board has been installed properly.

Accepted Answer

MathWorks Support Team
MathWorks Support Team on 27 Jun 2009
This error occurs as the result of not running these commands with administrative privileges first, before running them on machines that do not have these privileges. To resolve this error, run the commands on the machine with administrative priveleges prior to running them on machines without these priveleges. You will be able to run these commands without administrative privileges once you have done this.
To ensure that you are actually logged in as administrator, not just a user with administrative privileges, run a test at the DOS prompt to check this by typing 'echo %username%'. It should return administrator.
Also, the problem may be that you have not installed NI-DAQ. This file is available on the National Instruments web-page. Make sure you do this prior to running the toolbox. After doing this, you should see 'nidaq' in the structure for the daqhwinfo command.
The third suggestion is to check that the regedit file is actually looking at the latest version of the DLL. Sometimes you may be looking at the old registry because MATLAB keeps the old DLLs even when you have uninstalled the older version.
Try the following:
daqregister('nidaq','unload')
Then reload the DLL for the version of MATLAB you are using.
There are no new solutions to offer at this time, other than the solutions that are recommended above.
NOTE: The solutions above have been reported to us by other customers as not fixing the error in some instances. If these suggestions did not fix the problem you are experiencing, please be aware that we have reported this to our development staff for further investigation.
At this time, there is currently no known workaround, but this solution will be automatically updated when one becomes available.

More Answers (0)

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!