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

Tags: NI Software

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.

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

  • Compression filter incompatible error-1074396007 took place at IMAQ AVI write Frame

    OK, so I have two computers.
    On one of them, the VI works fine, on the other hand, I get an error and no AVI file.

    I'm taking a bunch of tif files and compression of AVI file with Compression Indeo® video 5.10 filter.
    Two computers running Windows XP.  He who works is more older and slower (but still quite new, 2 years old).  The news that does not work is a dual core with 3 GB of RAM.
    One difference is that with the old computer Labview is installed on the C drive with windows.  On the new computer Labview is installed on a second partition (drive D) while windows is installed on drive C.

    Initially the demo write avi file and compare the VI compression filters would not work on the new computer, but after upgrading Direct X version 9 and restart the computer, they work now.  With the compare compression VI IndeoR 5.10 Compression filter filter example video works fine.

    When I try to start my VI (joint) on the new computer it works, but I get an error (error-1074396007 is produced through the filter of compression IMAQ AVI write Incompatible framework.) Possible reasons: IMAQ Vision: Incompatible compression filter (Hex 0xBFF60499).) and no avi file is produced.  When I run other filters with the VI, I get an avi file which works fine!

    I have NEITHER Vision 8.2.1 installed on both computers.  On the old computer, I also have older versions of Labview installed.

    I even is gone to the windows/system32 and found the CODEC (ir50_32.dll) on the old computer and copied and replaced the version I had on the new computer.  This had no effect.

    A reflection as to why I get this error?
    André

    Adding a strip of 2 worked, so I guess that the div by 4 the rule applies.  Thank you.
    André

  • Update error, error 6 took place in AB_Source_VI.lvclass:

    When I Isaiah to compile an .exe Labview file gives me an error listed below:

    An error occurred during the recording of the following file:

    C:\Program Files (x 86) \National Instruments\LabVIEW 2009\vi.lib\Utility\error.llb\Convert property node font chart font.vi

    Visit ni.com/ask support request page to learn more about the resolution of this problem. Use the following as a reference:

    Error 6a held at AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller

    Possible reasons:

    LabVIEW: File generic i/o error.
    =========================
    NOR-488: IO abandoned operation.

    So I have no idea where this problem, I built this dozens of time request before.

    I would appritiate any help you guys can provide

    Dublin:

    It is possible you may have exceeded the limit of file path to 255 characters, which would cause this error in the application Builder (see this KB). If the temporary path, the application builder used was close to the limit, it may have changed when you create a new file with an extra character or something.

    You can try the steps listed in the KB to see if it's the problem for sure. Alternatively, you can try restarting the computer and/or compensation to your temporary directory of Windows and tent build again.

    Hope that helps!

  • Error 6 took place in AB_Source_VI.lvclass:Close_Reference.vi... RTBUIP_CreateNewWizard_Invoke.VI.ProxyCaller


    NVM. Found the answer on the basis of knowledge... The folder name is too long.

  • Mystery, error-50103

    OK, so I'm finally up to LV2009f3, making a few cDAQ work.

    I add code for devices, one at a time and check them out.

    (I use OR simulated chassis and features simulated - thank you, for that ability!)

    When I add the extensometer (NOR-9237). I started getting an error (- 50103 - resource is reserved).

    MAX said the jury works very well and gives me the simulated sine wave.

    Boil my my program code, and it works fine by itself.

    But when I try to do BOTH module 4 (9201) and module 6 (9237), I get the error.

    Extract attached (like extracts, BTW) illustrates the code.

    Before I added the thread error to force the strain gauge module to configure the voltage MODULE, I would get the error each time.

    But, sometimes it would occur on the module of TENSION and sometimes on the module of DEFORMATION.

    I could run several times and the error would come from one or the other, but it would occur every time.

    So what are the rules here?  They are completely different modules, and yet something is temporarily tied up when I try to set them up in parallel.

    It's a kind of race, judging by the error happening on one or the other.  A string claimed this "resource", and the other considers it occupied and complains.

    However, the error is attributed to the vi START TASK.

    What Miss me?  What are the rules about this?


  • Error-50103 during the VI call for the second time

    I have a main VI who, after the initial installation, called a VI that reads and writes several times to a data acquisition (USB 6356). This VI subroutine is called several times for each of the stages of the program. On the first pass through, there is no problem. During subsequent calls to the sub VI, however, it throws error-50103. I've identified the task that resolves this error. I made sure to do a self-cleaning on the task, create the task outside of loops and stop and clear the task after all the iterations are performed. To check if it is only the following calls may cause the error, I created a simple VI who just ran the sub VI twice now, and there are no errors.

    Any ideas on what is causing my problem or why it does occur during subsequent calls to my VI more complex?

    A picture of the frame and the task which gives me the number is attached.

    Thank you!

    I finally found the problem, although it was not the task that LabVIEW had identified. The problem task was a separate sub - VI who was called from the main VI and the Subvi that threw the error. I got this task stopped and cleared and it's not like he has over the matter.

    Thanks to all who have contributed.

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

  • 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 50103 - simultaneous analog Vout and wine with start of analog triggering

    Hello

    I'm stuck error 50103.  I looked on the Web site of NOR and worked through the 7 cases and think that my problem is the 6 case - although I'm not sure - and have no idea how to fix this. Basically, what I would do is out my signal and have receive side save after it passes through a noisy channel. To start, I have attached a trigger control so that the transmission or recording start before the input trigger exceeds a certain value (in my case, 3V).

    Could someone please look at my code (attached, called 'Optical_DPPM_V3.vi')) and try to give me an indication as to what I'm doing wrong? Thank you!

    Furthermore, I use examples of OR that I have also included in the .zip for reference file.

    SP

    P.S. hardware: LabView 8.2, NI PCI-6070E

    Hi gt3000,.

    Thanks for your reply. I actually solved the problem I called one of your offices directly and spoke with someone last night.

    Indeed, the problem was "case 6" as it is stated on the page you gave. "." When I spole with one of your colleagues, I was directed to an example that does most of what I wanted. If anyone is interested, you can follow this path to find:

    Help--> find examples--> material input and output--> DAQmx--> synchronization--> multifunction--> multi-function Synch AI - AO.vi

    It seems that the trick is to use an internal digital triggering to synchronize the CLK for VI and VO.

    If people are interested, I can send my final code around for a differential pulse modulator, triggered by an external analog voltage which the receiver registers and stores the values in a worksheet. My next goal is actually write the code for the receiver to demodulate information... here go us!

    Thanks again,

    SP

  • 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

Maybe you are looking for