Error -10401 occurred at CTR Control

i am trying to build a vi that wil count the number of digital pulses from a source between a specified start and stop trigger . in my case i have not wired the digital trigger yet i use boolean buttons to give my start and stop signals .
i am not very familiar with this vi and may be i am going in the totally wrong direction .
please correct me if i am wrong .
thanks
Attachments:
counter.vi ‏14 KB

The error has absolutely nothing to do with the 4278A. It's coming from the traditional DAQ function you have in there for a counter on an NI DAQ card. Your image does not show that traditional DAQ is even installed.

Similar Messages

  • 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

  • Error -10609 occured at AI Control

    Recently we have been getting the following error message when trying to run 5 of our programs all at once.
    "Error -10609 occured at AI Control
    NI-DAQLV: A transfer is already in progress for the
    specific resource, or the operation is not allowed
    because the device is in the process of performing
    transfers, possibly with different resources."
    I believe that this error is coming from the AI Control.vi which is on of the subVIs of AI aquire waveform.vi. We have been using the AI aquire waveform.vi to read our thermocouples from the DAQ board and in the past have had no problems running multiple programs (with multiple thermocouples) using LabVIEW 6.0. When we switched to using the Executables that we created using LabVIEW
    6.1 on another computer we started running into this problem. The development computer is a sony VAIO 1.6GHz P4 with 128 MB Ram, the operating computer is a Dell OptiPlex P1 of unknown processor speed with 64 MB of Ram.
    If you have any ideas on how to fix this problem I would greatly appreciate it. Also, we are running the NI-DAQ 6.3.9 version and a PCI-MIO-16E-4 DAQ board.

    Filipe,
    Thank you for your response. One of NI's field engineers contacted me about this problem and I think that we have it solved. I am now using the Semaphore commands to control access to the DAQ board so that only one program can access it at one time.
    Thank you for your help. If I can figure out how to add all tasks to one code then I will try that. The current problem with that is that not all tasks are always needed.
    Thank you,
    Timothy

  • 'Error -10401 Occurred at AI Clock Config' When Running Certain Examples ...

    I tried following the suggestion given earlier on the website link http://digital.ni.com/public.nsf/3efedde4322fef198​62567740067f3cc/50f8faa83c79f07f862569f90041855b?O​penDocument
    So I changed the Channel A to 0 and Channel B to 1, but still get the same error. I am doing a VI on my own that is getting the same error so I am very confused.

    Hello;
    I don't have detail on what exactly you are trying to accomplish there.
    Can you give me more details such as what board you are using, what you need to accomplish, etc?
    Meanwhile, the error -10401 occurs if you are trying to address a device that is not present. If MAX cannot see the DAQ card or you have changed the device number of the card, you will get this error. So, I recommend you first use MAX to do basic testing with the board, and check if the device number you are setting at the LV VI corresponds to the device number MAX assigned to that board.
    Hope this helps.
    Filipe

  • An error has occurred because a control with id '%spPlaceHolderMain%' could not be located or a different control is assigned to the same ID after postback.

    Hello All, When i try to do a filter on an entity and click filter button, i see the below error message being popped up. Can someone provide a solution to this ?
    "An error has occurred because a control with id '%spPlaceHolderMain%' could not be located or a different control is assigned to the same ID after postback. If the ID is not assigned, explicitly set the ID property of controls that raise postback events
    to avoid this error."
    Please let me know the process to set the ID explicitly.

    Can you try resetting the IIS?

  • The error "-10401" occurred in the current database connection "LCA"

    Hi everyone,
    I installed livecache 7.7 with scm7.0,when i did postinstallation  Initialization or run t-code lca03,i got error dump as below.now the livecache states is good.in scm server I not installed package Lcapps.please help give your advise,thank you so much.
    untime Errors         DBIF_DSQL2_SQL_ERROR
    xception              CX_SY_NATIVE_SQL_ERROR
    ate and Time          01/20/2010 03:26:32
    Short text
        An SQL error occurred when executing Native SQL.
    What happened?
        The error "-10401" occurred in the current database connection "LCA".
    How to correct the error
        Database error text........: "Conversion of parameter/column (1) would tru
         data"
        Database error code........: "-10401"
        Triggering SQL statement...: "EXECUTE PROCEDURE "APS_PLAN_VERSION_GET""
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:

    Hi Natalia,
    thanks for you much help,the livecache version is 7.7.02,so I will try to upgrade to 7.7.04,thank you.
    Server Utilities    d:/sapdb/programs      7.7.02.08     64 bit    valid
    DB Analyzer         d:/sapdb/programs      7.7.02.08     64 bit    valid
    PCR 7301            d:/sapdb/programs      7.3.01.21               valid
    PCR 7500            d:/sapdb/programs      7.5.00.42     64 bit    valid
    SAP Utilities       d:/sapdb/programs      7.7.02.08     64 bit    valid
    APO LC APPS         d:/sapdb/k1p/db/sap    6.00.004      64 bit    valid
    Base                d:/sapdb/programs      7.7.02.08     64 bit    valid
    Redist Python       d:/sapdb/programs      7.7.02.08     64 bit    valid
    JDBC                d:/sapdb/programs      7.6.03.02               valid
    Messages            d:/sapdb/programs      MSG 0.5010              valid
    ODBC                d:/sapdb/programs      7.7.02.08     64 bit    valid
    SQLDBC 77           d:/sapdb/programs      7.7.02.08     64 bit    valid
    Database Kernel     d:/sapdb/k1p/db        7.7.02.08     64 bit    valid
    Loader              d:/sapdb/programs      7.7.02.08     64 bit    valid
    SQLDBC              d:/sapdb/programs      7.7.02.08     64 bit    valid
    Fastload API        d:/sapdb/programs      7.7.02.08     64 bit    valid
    SQLDBC 76           d:/sapdb/programs      7.6.01.15     64 bit    valid

  • 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

  • AI Control gives error: 10452 occurred at AI control. Possible reasons: NI-DAQ LV no interrupt level is available for use.

    How can I run out of interrupts while accessing my DAQPad? Does
    the community have troubleshooting suggestions?

    You don't say which DAQpad. If this is a device on your parallel port then
    you will need to make sure that the parallel port has an interrupt assigned
    and not just a base address.
    Check out the following from the NI Knowledgebase:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/bf7960eb90
    ef882a8625654e007d8b1a?OpenDocument
    Ian
    "Riverside Consulting, LLC" wrote in message
    news:[email protected]..
    > AI Control gives error: 10452 occurred at AI control. Possible
    > reasons: NI-DAQ LV no interrupt level is available for use.
    >
    > How can I run out of interrupts while accessing my DAQPad? Does
    > the community have troubleshooting suggestions?

  • Error 10401 occured at AI config

     Hi,
    This error is displayed when i run the VI . Im using  MAX software when I open it go to devicesI have GPIB0 and under that I have 2 folders called instrument 0 and instrument1 when I right click on these folders it will bring up another window where you can read, write and configure EOS ,this is where the problem comes in when I go to configure EOS I can change the settings but they will not stay saved there. I found another window that will let me confiqure devices and changed all the info there to what I need but i still errors
    Thanks
    Attachments:
    0960_0961_Test Power.vi ‏351 KB

    I am using a DAQ board...I have both NI - DAQ max and NI - DAQ legacy devices. This VI uses the mulifunction I/o PXI 6070 E . I reset driver for NI - DAQ legacy devices and relaunched the VI in labview...and i am still getting the error. All these VI were done on a different machine...and were working then. I have configured all my devices in MAX too..
    Any Advise?
    Thanks

  • 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

  • Error -10401 appears when I try to read in my Encoders (TTL-Signa​l) via a LabView-"n​uDrive 2SX-411" and Motion Controller Card

    Hy there.
    Im using two "Haidenhain ERN 420" Encoders with TTL-Output Signal
    A NI-Motion Controller 7334 with an NI-"nuDrive 2SX-411"
    When I try to Read the Encoders Position (with ex.-Programm/Source) the Message: "Error -10401 occurred at AI Group Config ... the specified device is not a NI-product" appears
    Can anybody help me to initiallize/Use the Encoders in Labview 6.01?
    thanks, phil.

    Phil,
    It looks to me according to the error that you were trying to use DAQ functions to access the Motion controller. The Motion controller uses its own functions. There are two for reading position:
    Functions Palette >> Motion & Vision >> Flexmotion >> Trajectory Control >> Read Position.
    Functions Palette >> Motion & Vision >> Flexmotion >> Analog & Digital I/O >> Read Encoder Position.
    You may find a useful example in:
    C:\Program Files\National Instruments\LabVIEW 6.1\examples\Motion\FlexMotion\One Axis.llb\One Axis Move with Position Monitor.vi
    Make sure that you have configured and initialized your board properly in MAX.
    I would suggest that you post your question on the Motion Control section and not in the LabVIEW section. Also, check the Dev
    elopment Library section of the NI Developer Zone for the Motion Control section with tutorials and example code.
    Good luck!
    Nestor.
    Nestor
    National Instruments

  • Error -50103 occuring in one program, but not occuring in another similar program

    Hello,
    I'm a new user of LabView and I'm trying to figure out how a part of this programming process works.  Anyway, the block diagram of the working program consists of the first two pictures (C:\Users\Labview\Pictures\errorsetupnew1.jpg  -and-  C:\Users\Labview\Pictures\errorsetupnew2.jpg).  The parts in question are the DAQAssistant9 and DAQAssistant12 in the lower half of the diagram.  When I run the program, everything goes fine.
    So now I'm trying to run two other programs that both share the same properties as these two DAQAssistants, but they are in two separate programs.  When I run one program, it works, but when I run the other program, Error -50103 occurs at DAQmx Control Task.vi:10.  Pressing continue yields Error -50103 occuring at DAQmx Read (Analog 1D Wfm NChan NSamp).vi:3. 
    So my first attempt at solving it was to consolidate it into one program and run it all together, however the same error shows up.  I isolated the two While loops which seem to be causing the problem into a test program (third picture) and the error occurs there as well. 
    My question is what is different from the program in the first two pictures that is allowing the program to run correctly and the test program (which can be extended to the program that I need to work).
    I'm new, so please let me know how many beginner mistakes I might be making here!
    Thanks
    Attachments:
    errorsetupnew1.jpg ‏137 KB
    errorsetupnew2.jpg ‏113 KB
    errortest.jpg ‏82 KB

    I'm not currently at the computer with the files in question, but what if I attached those instead when I got the chance?  The problem is that I don't believe I am using the same DAQ resource in two different tasks.  The command line runs correctly in one, but can not run in the other even though the part giving the error is just a copy of the other program.
    I'm trying to run through the previous posts about this particular error but the LabView lingo is something I'm still getting used to.  Thank you for bearing with me and helping.

  • 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.

  • Error 10401

    Whenever I attempt to use the analog input vi's (such as AI Sample Channel, AI Acquire Waveform, etc.), then go to run the application Error message 10401 pops up: "Error 10401 occurred at AI Group Config."  I'm able to set up equivalent code using the DAQ assistant feature and the applications runs perfectly fine.  But every time I try to write the code myself using the vi's I just always get this same error message.  I'm very inexperienced with using Lab View and MAX so I haven't been able to find a solution and was wondering what I might do to fix it.  Thanks for any help you can give.

    AI Sample Channel and AI Acquire Waveform are functions in the old traditional DAQ driver. The DAQ Assistant uses the newer (and better, imho) DAQmx driver. You should look at the DAQmx low level functions. There are numerous shipping examples. You can also (depending on the version) right click on the Assistant and select Gnerate DAQmx Code or right click on it and select Open Front Panel to view the DAQmx functions that the Assistant is using.
    Your other option is to switch to the traditional DAQ driver but then you won't be able to use the DAQ Assistant.

Maybe you are looking for