Error-50103 occurred at DAQmx Start Task

Hello!

I use the attached VI to control a stepper motor which works perfectly under LV2010 but begins to throw error (image below) when used under LV2012. If anyone has any idea please help... -Thank you!

Note I have DAQ assistant is configured correctly.

Hi KowdTek,

Thank you for the update.  I assumed you didn't intend the output to be continuous (smooth).

Screw Express generally are not designed for this type of use because they open and close a session whenever you call one.  This should result in a glitch in the output as you have seen.  To be honest, I'm quite surprised you did not see this before not smooth behavior with your application on Windows XP, and I don't have a good explanation of why it worked.  I can, however, recommend a more robust approach to generate this smooth output you are looking for.

If the goal is to only move once by INIT (for example once you start moving, do not stop until you are finished, how the VI returns to INIT state), you must convert your VI Express DAQmx code (right-click"NOR-DAQmx generate code).  And try a similar implementation in your case EXEC & LUN.  This should produce the desired behavior.

Kind regards

Tags: NI Hardware

Similar Questions

  • Error-50103 occurred at DAQmx start Task.vi:11

    Hello

    I use a nor-6008 to perform a thermal sector and I get the error "error-50103 occurred at DAQmx Start Task.vi:11 '. I have read other forums of discussion and it seems combe because I use the wizard DAQmx who don't properly resolve the resource when finsihed. I've dug further and saw that it is linked to an on-board clock synchronization problems. However, I can understand how to solve this problem.

    I thought that I create a loop that continuously monitors inputs and sometimes to interrogate the memory so I'm not kidding to the top of the clock. It's much harder to do than sounds. Can someone take a look at my code and give me some advice/suggestions to clean the DAQmx assistants.

    Thanks in advance

    Cole

    I finished by dividing my resource between the two input channels using a single assistant DAQ and dividing down the data rate and the number of samples. Works fine now.

    Big pain in the ass well.

  • error-50103 occurred at DAQmx control Task.vi:6

    I'm new to LabVIEW. I'm using LabView 8.6 and one NEITHER cDAQ-9172. For practice, I'm doing a program that takes the temperature and pressure readings and graphs.

    I don't have the modules or sensors yet, so I started by simulating a RTD temperature measurement NI9217 and a NI9237 module for the measurement of pressure.

    I created 2 while loops that run in parallel. One with an assistant of data acquisition for the temperature and the other with an assistant of data acquisition for the pressure.

    Highlight run out, when I run the program, the signal is both while loops. The temperature seems to work ok and the data graphic. The pressure, however, only goes in once, and I get the error message: "error-50103 occurred at Task.vi:6 DAQmx control Possible reason (s): the specified resource is reserved." The operation could not be performed as indicated. »

    In addition, the stop button does work on my front. I have to use the button stop in the toolbar.

    Anyone has any advice on what I can do to fix this problem or any suggestions on the best ways to address the issue?

    Thank you.

    Search the forums for error 50103.  That will tell you everything you need to know about this error code.

    For more information on your questions, post your VI so we can see what might be wrong.

  • Error-200022 occurred at DAQmx start Task.vi

    Hello

    I have peripheral cDAQ and 3 modules that nor-9234 connected.

    My program (see attachment) works correctly with only 2 modules, but does not work with 3 modules.

    With 3 modules I have this error: "error-200022 occurred at Task.vi DAQmx Start.»   "Possible reasons: resource requested by this task has already been reserved by another task."

    To solve this problem, please help me

    Thank you

    Now I understant the error. This is correct (see below)

  • Error-50103 occurred at DAQmx control

    We strive to take into two signals in LabVIEW through our acquisition of data, and then pass them through two channels of detection of distinct peaks, however, when we try to run the program, we get the following message is displayed:

    Error-50103 occurred at DAQmx control Task.vi:14

    Possible reasons:

    The specified resource is reserved. The operation could not be performed as indicated.

    Task name: _unnamedTask<9>

    I have attached the circuit we use below, any help woud be appreciated.

    Problem solved, use:

    http://digital.NI.com/public.nsf/allkb/485201B647950BF886257537006CEB89#case4

  • Error 200485 error has occurred to DAQmx create Task.vi:2

    I continue to have this error:

    The specified task cannot be loaded because it is not in the area of data.

    Check the data area to the MAX. You are looking for similar characters, such as the capital letter 'o' and the number zero.

     


    I would like to know what is the problem with the program.  I have attached the VI.

    Basically I'm controlling a physical light connected to the NI Elvis II by comparing input from 0-7 DIO and DIO 8-15.

    So if DIO 0 is enabled, 8 DIO must also be to turn on the LED.

    But for the moment, the program may not run. Need assistance to locate the error! ><>

    Try the function AND.

  • Do you need 'DAQmx start task' vi read from a device NI DAQ (NI 9205)?

    I have a NI 9205, which I use to get a waveform data. To get started quickly, I used the wizard DAQ Vi. The code below (FIGURE 1) is the acquisition of data help VI looked like when I convert LabVIEW code and made some minor adjustments.

    When I looked online to see how to get hardware DAQ data, many sources use the task start DAQmx in figure 2.

    DAQmx start using VI makes another?  Materials using DAQ assist in loop gives you a lack of performance?    If so, figure a will have a lack of performance too as it is basically the DAQ help code?

    FIGURE 1

    Hello sticyfinger,

    Help for the Start Task function:

    "If you do not use this VI, a measurement task starts automatically when execution of the reading DAQmx VI. Automatic start of theDAQmx VI entry write determines if a build task starts automatically when the execution of the writing DAQmx VI.

    If you do not use the DAQmx start task VI and VI task DAQmx stop when you use DAQmx Read VI or VI to write DAQmx several times, as in a loop, the task starts and stops several times. Start and stop a task repeatedly reduce the performance of the application. »

    Hope that helps!

  • Daq stop task VI back to the State of the task was really forward the DAQmx Start Task or DAQmx writing?

    Hello

    I use DAQmx and DAQ Assistant and try to get the details on the following questions.

    1 does Daq stop task VI really return to the State of the task is in front the DAQmx Start Task or DAQmx writing? Digital Input taking as an example, I don't think that the status of the task means that input data because I tried and I can't really back to the entry level it was.

    Maybe more experienced people can help to share their expertise.

    2. the information in help indicates "virtual channels created with the function/VI DAQmx create Virtual Channel are called virtual channels the and cannot be used in the task." But I don't know what "in his work" means.

    3. could I get some guidelines or expertise on the Labview programmers when use virtual channels the and when, to the more global?

    Thank you!

    Best regards

    Allen

    If you create a channel of the task, or scale just usuing the screw to create or Assistant session wire io is the only way to pass the info autour.  It is not saved anywhere on the disc.  A channel of the task or the scale in a project can be used by anything in this project.  A channel of the task or the scale recorded in MAX can be used by anything on this machine.  Its an extended thing.

    And Yes, the DAQ Assistant fresh extra performance overhead and the poor than the DAQmx API.  Often, it won't have the impact of a little experiment.  Large applications should avoid the express Visa.

  • Error-50103 took place at DAQmx start Task.vi

    Hi all

    I'm having quite the difficulties of merging the two screws I'm trying to get the thermocouple readings and pressure readings in a VI. I think the two AOs are competing for the resources of the clock. Please forgive my noob-ness. I am very new to LabVIEW and it is not the most intuitive. I have attached the thermocouple VI I try to insert in the VI pressure. I appreciate all help. Two screws were working before the merger.

    Sorry!

    You gave the wrong link, here's the good: http://digital.ni.com/public.nsf/allkb/3296BA2AEF586B7386256D6D00528E3D?OpenDocument

  • Error-200278 occurred at DAQmx Read

    Hello

    Following an updated example developed by an engineer to support NOR super useful. I did a routine very simple acquisition of a certain level of synchronization between tasks (attached) to use in a PXI system between modules of strain gauges (4330), voltage module (6341) and a frame of independent SCXI1000. The routine seems to work very well up to a certain point, when a very strange problem appears (-200278). It's always the voltage task that generates the error.

    Any suggestions?

    The task of voltage is set to acquire finished samples.  You want "Continuous samples" I think.

  • Error-200077 occurred at DAQmx control

    Hello

    I'm having a problem with a sample less than a rate of 1 k with the NI USB-4431.

    Possible reasons:

    Requested value is not supported for this property value. The value of the property may be invalid because it is in conflict with another property.

    Property: SampClk.Rate
    Asked the value: 100.000000
    Valid values begin with: 1.0e3
    Valid values ending with: 102.400000e3

    My vi is attached.

    I tried to change the wait, but it makes no difference.

    I would really appreciate the help on this one please.

    Thanks in advance,

    AT12.

    Hello

    http://www.NI.com/PDF/products/us/cat_usb4431.PDF

    According to the specificaitons in the aforementioned document, the sampling rate is 1kS/s to 102.4kS / s

  • USB-6221, replaced by USB - 6221 BNC - error-50103

    My client is reproducing a system that worked well with NI USB-6221 enclosure. Now, I get an error with the NI USB-6221 BNC. The error only occurs when I try to perform auto calibration.

    ---
    The error:

    Error-50103 occurred at DAQmx Self Calibrate.vi:1

    Platform AND Services: The specified resource is reserved.
    ---

    I've implemented the pilot as a driving force.

    What is strange to me is that I can run the engine of the autonomous action to set up the device and run the auto cal without getting an error. But when I call these routines of an another vi - the error occurres.

    To specify (and reproduce the problem) - with USB-6221 BNC is defined as 'dev1 ':
    (1) acquisition of analog data in AE.vi - select 'Configuration' as an action on vi and then run it
    (2) acquisition of analog data in AE.vi - select 'Cal' like action then don't run it - no error
    (3) place the screw DAQ in a new vi as shown - run and that's when I get the error

    This is my first experience with DAQmx, any ideas what could cause this problem would be appreciated.

    Thank you
    Steve

    LV2009 Sp1
    MAX 4.71
    NOR-DAQmx Device Driver 9.2.1

    Hi Steve,.

    "Setup" action leaves the DAQmx run task, so the 6221 AI resources are reserved to prevent other programs and live to interfere. When the top-level performance, LabVIEW VI automatically tells DAQmx to clear the task. That's why you get different behavior when you run the action as the first level VI engine when you run the engine of the action as a Subvi. Self-cleaning, you must cancel (e.g. stop or clear) all the tasks before you can calibrate the device automatic, try performing the action 'Close' before 'Cal

    Brad

  • Error-200431 occurred at .vi DAQmx Create Channel (I-acceleration-accelerometer)

    Hello

    I tried to use DAQmx Create Channel to accelerometer and yet it responds with error (see below). When I use max OR to measure the accelerometer (I-acceleration-accelerometer), there is no error, and I see that acceloremeter works.

    OR PXI-1042 and I use OR-4462 card to measure vibration vith acceloremeter.

    Error-200431 occurred at DAQmx Virtual Channel Create

    Possible reasons:

    Physical channel selected does not support the type of measure required by the virtual channel you create.

    Create a channel to a type of measure that is supported by the physical channel, or select a physical channel that supports the type of measure.

    Property: I. MeasType
    Requested value:
    You can select: sound pressure, voltage: Microphone, accelerometer, Position: Eddy Current proximity probe, Force sensor: IEPE, speed sensor: IEPE

    Task name: _unnamedTask<104>

    Hi serdaryilmaz,

    I'm not sure why the accelerometer mode does not work, but it works very well in normal mode - it maybe has to do with the accelerometer, you?  Whatever it is, if it works with the voltage mode, I am happy that we found a way to make it work.  Is this an acceptable work around you?

  • My Windows mail keep blocking saying an error has occurred and it will reopen its doors again. It does this all the time. Can anyone help?

    A week ago when I go to the various emails in my Inbox, my mail will close and then reopen again.  It just says: an error has occurred and it starts up.  If I do not jump in my email box, it doesn't seem to happen as well but if I want to keep something an email, and then go to another, he stops.

    Try to compact and repair the database.
     
     
     
    If that does not do it, delete the account, restart and it add.
  • What is error 50103? the task of DAQmx START?

    Hello

    I use cDAQ 9174 with NI 9401 to measure the period of the encoder.  I have two encoders and learned that I need to have a separate task for each.  Initially, I got an error telling me that the task was not reserved, so I followed the advice of the forum and added the TASK of CONTROL DAQmx, STORE of the value.  That eliminates the error, but now I have a new error 50103, which offers very few details of what actually is the error.  The seal is a snippet of the code, you see where there are three tasks, two tasks of meter to measure the period of encoder, and task of measurement of blood pressure, which in my opinion is not related to this error.

    Error 50103 to DAQmx controls TAsk.vi:3.

    The possible reasons: NI Platform Services: T / he said that resource is reserved.  the operation could not be performed as indicated.

    TAKS name: task _unnamed<3E>

    Thus, at the beginning, said he reserved the task, now it tells me that the problem is the reserve.  Does anyone know what this error is talking about?  The attached code is connected to a WHILE loop that aims to do a bunch of stuff with the data from the period after it was collected.

    Thank you

    Dave

    Hi dav2010,

    I modified the original example of working with the two counters at the 9174. It worked for me. Let me know if it works for you also.

    Best,

Maybe you are looking for