Another option is to purchase a computer with a faster bus to expedite data transfer from the FIFO buffer to the PC buffer. RF EngineerHigh Frequency Measurements bucky.gif 2 KB 0 Kudos Message 2 of 6 (6,921 Views) Reply 0 Kudos Re: ni daq error 10401 Clay Upton Member 11-15-2007 08:23 PM Options Mark Browse by task and select Hardware Input and Output»DAQmx.Incorrect: Correct: Case 3: Using multiple counter tasks on the same device. With that being said, you can look in NIDAQmx.h for a complete list of DAQmx error codes.
This error may also occur if you are using the TDAQ drivers and your program is referring to a hardware reference that is enumerated incorrectly. You can turn this off, but the default is on. Architecturally it was annoying because I had to know about all possible tasks in one VI and configure them all before doing any of the reads. I was able to find an NI knowledge base entry, Causes of NI-DAQmx Error 50103 "The Specified Resource is Reserved", which addresses this issue.
Ni Daqmx Error Codes
Solution: One reason you may be receiving the unknown device Error -10401 is because LabVIEW obtains all of its hardware handles from the Traditional NI-DAQ (Legacy) Driver when it first launches. Restarting LabVIEW or unplugging and re-plugging the device back into the USB port may fix this problem.Error -6006This NI-DAQmx Base error can occur when an incompatible version of NI-DAQmx is installed You can access a test panel by right clicking on the device and selecting “Test Panels…” These are great tools to verify whether your device is functioning properly and you are
- Once the board has acquired the specified number of samples, it will stop acquiring data.
- Generated Fri, 21 Oct 2016 10:20:43 GMT by s_wx1085 (squid/3.5.20)
- You generally want Offset = -1 if you really want the currently available sample with no waiting.
- Since the timeout function is really for the reading of the channel not for the autostarting, it sort of makes sense that the driver does not contain code to loop on
- Unplugging and re-plugging the device back into the USB port may fix this problem.
- You can find compatible versions of NI-DAQmx in the NI-DAQmx Base readme.
- Answered Your Question? 1 2 3 4 5 Document needs work?
- I'd think that your best bet is to use van18's semaphore suggestion.
- Created 2 AI tasks.
- In addition, this error may occur if NI-DAQmx was recently removed, or if NI-DAQmx Base was recently upgraded.
Jason, Thanks for the advice. Another possible reason you might be encountering this error is because you are attempting to use Traditional NI-DAQ (Legacy) Driver functions to communicate with your DAQ device, but the drivers need This can also occur randomly as an internal software error. Remove power from the USB device, then reconnect it.
What sort of hardware are you using? Ni Error Code All rights reserved. Cart|Help KnowledgeBase Request Supportfrom an engineer NIHome > Support > KnowledgeBase EnglishJapaneseChinese(China)GermanFrench 65 ratings: 3.55 out of 5   Causes of NI-DAQmx For DAQmx 7.3 and later, it is possible to do this even with multiple types of analog input if you use multiple DAQmx Create Channel VIs.Note: Case 6 is common when read review DAQmxGetErrorString will return a message that corresponds to the DAQmx error number, but the numbers you have are not DAQmx error codes.
Please tell us why. The collision rate increased dramatically when I moused stuff around onscreen. Today I am getting -3621 from DAQmxReadAnalogF64, and again DAQmxGetErrorString cannot tell me what this means. NitishLo Member 01-12-2016 03:41 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Link below gives you driver code
Ni Error Code
Share this post Link to post Share on other sites LAVA 1.0 Content 1
Regards, Laura 1 Kudo Message 2 of 7 (3,537 Views) Reply 1 Kudo Re: Is there a document that lists error codes for NIDAQmx? Because the task has reserved these resources, any task that tries to access these resources will encounter Error -50103.You can resolve this by doing one of the following: Add a DAQmx IMO, this is either a bug or a very poor design of the DAQmx API/behavior. If you find a different way, it would be great to hear about it, but I gave up.
Disconnect other devices that may try to share the PCI bus. I was using sample timing so I also set the property node to read the last N samples which I wanted. The error indicates that information is lost and occurs when LabVIEW does not read data from the PC buffer quickly enough. The cDAQ-9174 and 9178 chassis have three analog input timing engines and thus can support three concurrent analog input tasks if all tasks are on separate modules.Case 7: Failing to properly
For single point input/output (I/O), wiring False to the stop input optimizes performance, but it does not release the device's resources. DAQmxGetErrorString doesnt work. [Edited] kossem Member 03-11-2016 09:41 AM - edited 03-11-2016 09:44 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Called DAQmx Read in 2 separate While loops that had no delays.
With PCI devices, it is possible that LabVIEW booted before MAX finished installing the device.
This error can occur with a "factory fresh" device or after upgrading your application from NI-DAQmx Base 2.x or earlier. I was reading the on one of those USB-cDAQ devices and it said it could only support one active task at a time. Specifically AOonePoint.C7.3Just VisualC++ I believeNI PCI-6251yesI'm under the impression that this should be a numarical value, where MAX displays only a character value followed by a numberThe test panel works flawlessly Related Links: KnowledgeBase 25OCPJJE: MAX Returns Error 10007 or 10401 When Using Virtual ChannelWhite Paper: Transition from Traditional NI-DAQ to NI-DAQmx in LabVIEWKnowledgeBase 2P4BAE0T: Error -10401 When Swapping PCMCIA DAQ Cards
I believe that the reserved resource is actually the analog sample clock subsystem, which can't be shared. To access the channels independently (after the global task start), just set DAQmxRead.ChannelsToRead immediately before calling DAQmx read. Active Participant 07-14-2006 02:40 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hello kmagas, NI-DAQmx error codes Why would this cause an error?
Note that if you set DAQmxRead.RelativeTo = Most Recent Sample, and Offset = 0, it will actually wait until the next sample arrives (Traditional NI-DAQ did this too). If the application requiresFinite Samples, there is a second solution.To do this, place a DAQmx Start Task.vi and DAQmx Stop Task.vi in line with DAQmx Read.vi inside a while loop.