12-07-2021 12:42 PM
I am getting an error -10403, which gives a possible reason of:
NI-DAQ LV: The specified device does not support the requested action (the driver recognizes the device, but the action is inappropriate for the device).
Any ideas what might cause this?
The error comes from a library call to AO_Buffer_ConfigInterface, shown in the screenshot below:
This is using the lvdaq.dll
12-07-2021 01:32 PM
Hello , i thin i can solve it for you ,, for further assitance you can msg me wup on 002 01153646460
12-07-2021 05:50 PM - edited 12-07-2021 05:51 PM
That looks like a call to the legacy NI-DAQ driver, suggesting a rather old DAQ device and likely a pretty old OS as well.
What OS is this, and what version of LabVIEW and DAQ drivers are installed?
A few older devices (such as E-series MIO) were supported under both legacy NI-DAQ and under DAQmx, but NOT at the same time. Once you accessed it via one driver you'd need to do a device reset (available in MAX) before you accessed it via the other driver. Maybe you need to give this a try?
-Kevin P
12-08-2021 09:35 AM - edited 12-08-2021 09:36 AM
Thank you for your reply Ahmed, but I would prefer to communicate via the forum.
12-08-2021 10:39 AM
Thank you for your reply.
You are right the system is old.
The OS is XP.
The LabVIEW version is 7.1.
and the DAQ drivers visible in MAX are NI-DAQmx 8.3.0f3 and Traditional DAQ 7.4.3f7.
I have tried resetting both DAQmx and Traditional DAQ, but the problem remains.
12-08-2021 11:55 AM
Is this code that's been recently developed or modified? Or are you suddenly getting a new error from long-existing code?
Have you tried implementing the same kind of AO task under DAQmx?
As a very-slightly-educated guess, I'd be looking at the 'allocate mode' input first (what does the value 2 mean?). I'm not certain what the 'number of updates' means either, but am suspecting it might be a total # samples to generate?
Sorry, it's been a loooooong time since I used traditional NI-DAQ, and even then I didn't do much AO.
-Kevin P