Error 10401 - PCI 6023E

Hello everyone,
I have a LabView code running on LabView 6.1 (on Windows 2000).  It has a PCI 6023E DAQ card.
Everything was working fine for many days, until suddenly today I got the Error 10401 - occured at AO Single update.
if I click OK, the code tries to run then displays the same error again and again.   I have attached the LabView code. 
I checked in NI-MAX, and the device is located there as (Dev1), and seems to be fine.  I also tried restarting the computer but still get the same error.
What might be the problem?  Any help is appreciated.  Thanks.
Attachments:
Lion_Rail_Pressure_Control.vi ‏92 KB

Hi nithyan2,
I believe that you are using Traditional DAQ drivers, please take a look to this article.
Best,
Carmen C.

Similar Messages

  • Getting error 10401:Unkn​own Device Error from configured PCI-6036E

    I have installed a PCI-6036E into a PC with a P-II and 32MB RAM. I am running NT4.0 SP6 operating system. Attached to the PCI-6036E is an SC2345 with one SCC-A10 attenuator module. When I try to run either one of the sample solutions or a VI that I have written, I get an error 10401 Unknown Device. The text goes on to say that the board is either unsupported or not configured. When I go to the MAX software, I can see the board and it lists the interupt as IRQ 11 and DMA as 0. The values are grayed out. The SC2345 and installed module are set up as accessories. If I click the Test Resources button on the Properties window, it comes up with the error that the device is not responding to the first IRQ level
    How can I fix this? Is this an NT specific problem or will this sort of thing happen under Win9x and Win2k?

    Videojet,
    The types of errors you are receiving usually indicate improper installation or a bad board. Please make sure you have followed the proper installation procedure outlined in the Hardware Installation Wizard: http://www.ni.com/support/install/.
    If you find that you may have a bad piece of hardware, please initiate a service request on www.ni.com/ask. Call into to our technical support line to repair your board.
    Have a great day.
    Message Edited by Support on 01-22-2007 11:24 AM

  • Error 10401 when switching to a new DAQ Card

    Hello,
    I am running LabVIEW 7.1. Initially the computer had a PCI-6024E DAQ card installed with Traditional NI-DAQ 7.2 and NI-DAQmx 7.2. The card worked fine.
    Recently I replaced the 6024E with a PCI-6225 DAQ card and it was not recognized by MAX. I then downloaded a newer version of DAQmx, 8.6.1 (I chose this because it is compatible both with the new 6225 and also the old version of LabVIEW, 7.1). Once I installed this, MAX recognized the 6225 and it passed all of the MAX tests, so I think the hardware is fine. However, when I run I get an error 10401. I then removed the 6225 and replaced it with the 6024E again, and the old card still works fine.
    With the 6225, the error 10401 occurs in 2 different subVI’s. I've attached a screenshot of the error and the subVI "DIO Port Config" where it occurs. The other subVI where there is the same error is "AI Group Config".
    I have a guess for why the error 10401 is occurring. I read on this forum that these two subVIs are Traditional DAQ subVIs, which can't be used if the board (6225) is setup to use DAQmx. Is this true?
    In addition to the error screen shot, I've attached a screen shot of MAX with the old card and a screen shot with the new card. You can see that the 6024 is setup to use the Traditional DAQ, but the 6225 uses the DAQmx. If the code is written using Traditional DAQ functions therefore it makes sense that there would be errors with the new card. When installing DAQmx 8.6.1 I was told that "a newer version of Traditional DAQ was suggested". MAX shows that my Traditional NI-DAQ is version 7.2. Recall this was also the version of DAQmx I had prior to installation of 8.6.1.
    Could installing an updated version of the Traditional NI-DAQ and then setting up the 6225 to use this instead of the DAQmx remove these errors? If this is a solution, does the 6225 support Traditional DAQ?
    I appreciate any help,
    Stefan
    Attachments:
    Error.GIF ‏153 KB
    MAX_new_card.GIF ‏48 KB
    MAX_old_card.GIF ‏70 KB

    It takes a little getting used to if you have never done anything but Traditional. I find that it is easier after using it for a few years now. It may be a bit of work depending on how complicated your code is. If you need help we can point you in the right direction. Look at the examples and work from there.
    Tim
    Johnson Controls
    Holland Michigan

  • Help - Error 10401

    Hi All, 
    Let me open by saying I am an IT person trouble shooting this for someone else and I have almost no experience with the Labview software. The scientist using the software is only informing me that his program will not execute properly.
    A little background; the program I am trying to run was developed approximately 10 years ago using Labview v5.1 and a NI PCI-6052E data card. The machine that ran the program is no longer working so I brought the program and card over onto a Windows 7pc with Labview 2012. (the older installation discs are not available to us)
    I posted to the forum and had the program updated via the Version Conversion section so that it works with v2012 (or at least opens). The problem that I am getting when I run it is this error ‘Error – 10401 occurred at AI Group Config. The specified device is not a National Instruments product’.
    Tech support suggested an older driver, which I installed, NI-DAQmx 9.6.1, and the error still persists.
    The tech thinks that since the program was developed using T-DAQ that I need to update it somehow to recognize DAQmx functions.
    Any help is very much appreciated. I am willing to share whatever I need to get this sorted out quickly. Please let me know if you need the program, screenshots, system specs, or any other information.
    Thank you in advance for any assistance you can provide.
    Kristian
    Attachments:
    OCDR.llb ‏1160 KB

    I agree with the sub vi assessment. When I open the program it looks for the lvdaq.dll in a certain location, where v5.1 kept it, but finds it in a new location that corresponds to v2012 and this seems to be ok.
    Do you have a sample graph you could send me? I only have the one program to troubleshoot. Or maybe point me in the direction of sample programs. As I mentioned earlier I am troubleshooting for the scientist and have extremely limited program knowledge.
    Your help is highly appreciated.

  • Help resolving "Error 10401 occurrred at AI/AO Group Config"

    Hello, I know this is a common error but I'm unable to find a solution looking through these forums and other websites.  I am trying to convert a program wrote on an old computer running LabVIEW 6 to a new computer (with newer hardware) running LabVIEW 8.5.  I've resolved all issues that have came up so far (installing the traditional legacy drivers and such).  The only error I am getting now is a run-time error that pops up and reads:
    "Error 10401 occurred at AI Group Config" and "Error 10401 occurred at AO Group Config"
    I've already run the Measurement and Automation Explorer (MAX) and that did not help.  I'm using Windows XP and my hardware is a NI PCI-6281 M series DAQ.
    Do I have to re-write the sub-VI's, or is this fixable?  Is there an easier way to convert a program?
    If anyone can provide any help or insight what so ever it is greatly appreciated.
    Thanks,
    Alex

    Alex,
    This Developer Zone article may also be of some help to
    see the differences between Traditional DAQ and DAQmx for the most common tasks.
    Mark E.
    Precision DC Product Support Engineer
    National Instruments
    Digital Multimeters (DMMs) and LCR Meters
    Programmable Power Supplies and Source Measure Units

  • Can PCI-6023E support hardware Analog trigger

    I try to use the PCI-6023E to do the hardware analog triggering, but it gives me the Error-10403 while I test with the vi example, Aiacquires N Scans Analog Hardware Trig.vi. Is there any way for this board to do the hardware triggering?

    Jack,
    The PCI-6023E DAQ board only supports digital triggering. You can check all the features of this board in the Data Sheet and Specifications on the Catalog page (see link below)
    2002 Catalog - PCI-6023E
    http://sine.ni.com/apps/we/nioc.vp?cid=1063〈=US
    If you need to perform analog triggering, you have three options:
    1) You can simulate it by acquiring continuosly all the signals that you want to monitor including the one that acts as the analog trigger. Compare the value read from this last one with the boundary that is supposed to trigger the acquisition, and when the value read reaches this boundary, you can save or display the data from all your channels.
    2) You could implement an external circuit that will compare the analog trigger signa
    l with the boundary value, and when they coincide, will generate a digital pulse that you can use as a digital trigger. This option optimizes your CPU usage.
    You can find detail information on how to set up the digital trigger in Chapter 4>>Timing Connections of the User Manual linked below.
    6023E/6024E/6025E User Manual
    http://digital.ni.com/manuals.nsf/websearch/0C88F40FFE7F28CD862569AE00574AC1?OpenDocument&node=132100_US
    3) Finally, you could get one of our boards that supports analog triggering. The PCI-MIO-16E-4 board has similar specifications that the PCI-6023E, and it has some additional features as well. See link below for more information.
    2002 Catalog - PCI-MIO-16E-4
    http://sine.ni.com/apps/we/nioc.vp?lang=US&cid=10795
    Good luck with your application,
    Claudia Lorente
    Applications Engineer
    National Instruments

  • Error 10401 when running LabView

    To start, I am using a PCI 6032E, SC-2345, SCC-SG04, and load cell as my means of DAQ. I have configured a VI for this both in traditional and DAQmx using the example on this site. I can also run a test in MAX and if I push on the load cell, the reading changes. However, when I try to run the strain.vi LabView program found on this site, I get an error 10401. I tried closing the programs and opening them again, but I still get the error. I even have tried restarting the computer, but I still receive the error. Any suggestions? Thanks.

    After looking at the program I think I might know why you were receiving the 10401 error with the program. By default, the program doesn't give a channel to acquire from. The array of channels is empty (grayed out) initially and you will get the 10401 error until to enter a channel number or select a virtual channel.
    With regards to the new problem, what OS do you have? If you have Windows 2000/XP, then here is what I would try. Go to the device manager in Windows and choose to uninstall the device. Then go into MAX and refresh (press F5) and make sure that the device doesn't appear in Traditional NI-DAQ folder (you may have to delete the device in NI-DAQmx). Close MAX. Then, go back to the device manager and choose Action>>Scan for hardw
    are changes and let Windows reinstall the device. Now, go to MAX and test the device in Traditional NI-DAQ and NI-DAQmx.
    Let me know if this doesn't get things working.
    Regards,
    Todd D.

  • Error -10401 when running example

    I have a PCI-6071E and I'm trying to run the AO and AI examples. I keep getting error -10401, but I've configured the board and checked the device number. Any ideas?

    Hi Erin,
    The best place to begin troubleshooting this issue is in Measurement and Automation Explorer (MAX). The first thing you should do is reset the traditional NI-DAQ driver. If you open MAX and go to devices and interfaces>>Traditional NI-DAQ devices>>right click and select "reset traditional NI-DAQ driver."
    Also from there you can select your card and run a test panels. If the test panels works, then you will be able to run the examples in LabVIEW.
    If the test panels will not acquire any data or give you an error, then do the following: delete the card in MAX, turn off your computer, remove and replace the card in the computer, and re-install the card.
    Regards,
    Hal L.

  • Help with Error -10401 occurred at AO Group Config

    I am receiving the error: "Error -10401 occurred at AO Group Config" and have been unable to fix it. 
    Some background: This is someone else's program who has since left, so I am not very familiar with it. It was running fine a little while ago, until the PCI-GPIB card broke.  We got a new GPIB card (essentially the exact same model; the old one was 183619B-01; the new one is 183617K-01) and now this error appears every time I try to run it. 
    I believe this is being thrown by the "AO Config.vi" in my VI Hierarchy.  From reading other forums, such as this: http://digital.ni.com/public.nsf/allkb/46F78EDD19BA0CC386256CEE007201FC and this: http://forums.ni.com/t5/LabVIEW/Change-in-PCI-Device-Number/m-p/2312186#M726679, it seems it may be a problem with properly assigning device numbers.  (The new GPIB card  may have been assigned a new device number while the program is calling the old one).  However, the solution offered is to right-click on the device in MAX and change the device number, but when I right-click I am not given that option (see attached image). On the other hand, it could also be some sort of driver problem.  
    I am running LabVIEW 8.2.1 and Measurement and Automation Explorer 4.2.1.3001 on Windows XP SP2.  Any help is greatly appreciated.  
    Attachments:
    error.PNG ‏89 KB
    right click.PNG ‏77 KB
    hierarchy.PNG ‏94 KB

    Hi bh424,
    I would make sure that you have updated drivers as you mentioned. If you are using TDAQ make sure to reset the device driver mentioned in the KB you listed.
    Another thought would to be to remove and readd the device in MAX to refresh it, and potentially change the naming in your program to reference a new named device. If you cannot rename the device in MAX you could look at repointing the device in your code.
    Are you able to communicate with the device at all in MAX through simple queries? From the right click screenshot it looks like *IDN did not communicate properly.
    Have you also refreshed the list or rebooted your machine?
    http://digital.ni.com/public.nsf/allkb/23B5918E5604915B86256C2B005F4D70?OpenDocument
    I would first ensure you can communicate with the new card in MAX alone. Here are some troublehsooting steps if that is not the case:
    http://digital.ni.com/public.nsf/allkb/A80DBFCCAC36EBDE862562C80058856E?OpenDocument
    There is also the possibility that the card is broken as well. If it was indeed purchased from a 3rd party vendor, there is less we know about the card or what could have been done to it before you acquired it.
    Regards,
    James W.
    Applications Engineer
    National Instruments

  • Wiso bekomme ich Error 10401, wenn ich eine Applikation laufen lasse?

    Ich habe eine neue PCI Karte installiert (mit DAQ 7) und den Test durchgeführt und bestanden. Wenn ich nun eine Applikation (mit Runtime Engine 6.0.2) laufen lassen will, bekomme ich immer den Error 10401 (ungefähr:"Die Karte ist von einem anderen Anbieter oder älter als der Treiber")
    Wie kann ich den Error beheben?

    Hallo Petric
    Ich möchte zuerst das Ganze rekapitulieren:
    Du hast deine Karte in MAX getestet und alles hat funktioniert. In der LV 6.0.2 Entwicklungsumgebung funktioniert auch alles. Erst wenn du aus deinem VI ein Executable machst, dann kriegst du diesen Fehler!
    Wenn das der Fall ist, dann musst du sicherstellen das auf dem Zielrechner die gleiche NI-DAQ Version wie auf dem Entwicklungsrechner installiert ist und auch das die Device Number der Karte auf Ziel- und Entwicklungsrechner die gleichen sind. Dieser Fehler tritt oft auf, da es vorkommt das die beiden Systeme verschiedene Device Nummer verteilen. Die Device Nummer kannst du auf dem Zielrechner im Eigenschaftsfenster der Karte neu zuordnen.
    Falls du diese Punkte schon alle ausprobiert hast ode
    r ich etwas falsch verstanden habe, dann melde dich erneut.
    Gruss
    Luca
    Regards,
    Luca

  • Reading PCI-6023E counter by Delphi/NI-DAQ

    One current goal of mine is to read out the counter of a NI I/O board PCI-6023E by Delphi/NI-DAQ! But I don't get it work.
    I am interested in having a Delphi code using NI-DAQ commands *without ActiveX components*. At NI support doesn't exist yet any example code in Delphi using NI-DAQ just commands.
    What part is missing in my code "PCI6023E_Counter.pas"?
    http://www.home.fh-karlsruhe.de/~egra0011/Projects/SIM
    The "same" prog in VB works fine! Do the NI-DAQ commands/drivers work with Delphi? Thanks.

    Rawi,
    NI-DAQ provides a function prototype for Borland Delphi, so NI-DAQ function calls should work fine in that environment. Your program seems to be correct. However, you don't state why it's not working, and I've noticed that you don't seem to be checking the iStatus return value for an NI-DAQ error. You might want to check to see if an error is being returned. That could point you in the right direction. If you continue to have problems, I would recommend contacting National Instruments support for troubleshooting assistance.
    Also, the counter/timer developer exchange is targeted towards 660X and TIO-10 counter/timer products. The PCI-6023E is a multifunction I/O board, and in the future, you may want to consider posting your inquiries to the multifuncti
    on I/O exchange for assistance.
    Regards,
    Erin

  • PCI-6023E maximum working voltage2

    Thanks Mr. Alan A
    I am "434343" memeber.
    I recive your response to my question about "Max input voltage of PCI-6023E" .But I have some questions.
    According to the "Data Acquistion Specification- a Glossary by Richard House" ( Application Note 092):
    "Maximum Working Voltage (signal+common mode)= the highest voltage level that can be input to board without saturating the input."
    And according to your response:
    "measuring a signal with higher common mode voltage than that(11V) might not accurate"
    But in may experiment with a potentiometer (floating differntial source with (-)13.5V and (+) 5to22V),I could successfully measure the signal without saturating and without error (Max error is about +/- 0.02 volt)!!
    I think that the maximum working voltage of PCI-6023E is greater then 11 volt??!!
    or my measurement has a little error.
    I think that I don't need to use a signal conditioning circuit.
    Please Help me.
    Thans again.
    Edward Hb.

    Please see this thread.
    -Alan A.

  • MXI-3 not working get error 10401 from max

    get error 10401 when triying to access cards in PXI1000 chassis using MAX test panels

    The 10401 error is usually indicative of a problem with a DAQ card, not a MXI-3 card, but anything is possible. I will give you some general tips for troubleshooting the MXI-3 kit, but the DAQ card could ultimately be the problem.
    First, do you have the MXI-3 Optimization Software installed? If so, does it run properly on boot up? This software should detect the presence of the MXI-3 link. If the optimization software is having problems running, I would recommend emptying your chassis of all cards but the MXI-3 and try booting up and running the software. If problems persist, you could try changing the PCI slot of your PCI-MXI-3 card, or, if you have other MXI-3 hardware available, you could switch pieces between the kits. You could even try the system with ano
    ther PC.
    If the MXI-3 kit is working properly, then the DAQ card or the chassis could be causing the problem. Have you tried any other cards behind the MXI-3 link? Have you tried the problematic card in multiple slots? Was the system ever working properly? If you feel the DAQ card is the problem, I would recommend creating a new support thread so that we can get our DAQ Applications Engineers to help you troubleshoot the issue.
    Here is a link to more troubleshooting tips for MXI-3:
    http://digital.ni.com/public.nsf/websearch/484f81e6570ad803862569ed007aaa41?OpenDocument
    Ryan Tamblin
    Applications Engineer
    National Instruments

  • Error -10401 occurred at AI Group Config - in relation to USB-6008

    I'm attempting to run a simple vi that uses AI Aquire Waveforms.vi to input voltage data that I have coming in from the USB-6008 DAQ.  However, when I try running the program, I receive the error:
    Error -10401 occurred at AI Group Config
    Possible reason(s):
    NI-DAQ LV:  The specified device is not a National Instruments product, the driver does not support the device (for example, the driver was released before the device was supported), or the device has not been configured using the Measurement & Automation Explorer.
    And I'm not sure how to fix it.  In MAX, the device seems to be working properly and everyhting seems to work fine in the test panel, so I'm slightly at a loss.  I'm running Labview 7.1, and installed NI-DAQmx 7.5 which came with the USB-6008.

    Never mind.  I'm new to Labview, and didn't realize that I could not use the traditonal Data Aquisition components with the USB-5008 (I didn't even realize that NI-Daqmx was different).

  • Error 10401 occurred at AI Hardware Config, when using AI Acquire Waveform vi

    I can successfully run applications that use the AI Sample Channel vi, however when I use the AI Acquire Waveform vi the following errors are generated:-
    Error -10401 occurred at AI Hardware Config, followed by
    Error -10401 occurred at AI SingleScan.
    All applications have been developed using Labview 6.0.2, on an NT machine.  The applications are then run (or atleast attempted to be run) using the Labview Run-Time Engine on a different NT machine.
    The driver software I am using is the NI-DAQ Native Data Acquisition Driver Software Version 6.1.

    Hi,
    I've found a Knowledge Base on the NI website describing some situations where this problem occurs:
    http://digital.ni.com/public.nsf/websearch/46F78EDD19BA0CC386256CEE007201FC?OpenDocument
    That error code is generally seen when something has changed in the DAQ card's configuration, or the drivers are not installed properly. It's strange that this is showing up only on certain functions for your application.
    Also try having a look through the DAQ troubleshooting pages on the website:
    http://www.ni.com/support/daq/
    Regards,
    Mark Lee
    National Instruments

Maybe you are looking for