error 50103 in LabView using NI 6363

Similar Questions

• 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

• error 50103

  Hello

  Can someone help me please... I'm not so new to labview and never had a training. I'm trying to rea measures of the sensors of different temperature using channels NI9203 and also I am generating the output signal of NI9263. I need to know the temperature of all at the same time, but when I run labview I get error 50103. I tried all the steps mentioned on the average error of report previous but still not put my measurements.

  Please help me...

  Right-click on your data cable.  Select 'range of Signal Manipulation.  I'm pretty sure 'Split signals' will do what you want.

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

• Connection diagram DAQ Asst &amp; error 50103

  Hello LabVIEW community.

  I'm trying to integrate two different screws that require an AIGND on my SCB-100.

  The SCB-100 has two distinct AIGNDs (pinout of the 1 and 2), but in the two screws of the DAQ Asst I use, pinout 2 asks the circuit diagram for the two.

  I think that leads to a mistake of 50103 on reserved resources.

  Is it possible to switch, one of the AIGND of data acquisition for pinout 1 assistants?

  Thank you all for your help.

  Sincerely,

  The reasons are common and are totally unrelated to the error-50103. The error is because you are using two different data collection Assistants. Have you done a search here of this code or explanation? Use a simple DAQ Assistant with several channels.

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

• Simultaneous release of digital waveform at different frequencies - cDAQ-9174 with two 9477 maps error-50103

  Hello

  I'm working on a project that requires two outputs digital signals at different frequencies. Frequency of the phase 1 is about 1 kHz and is modulated on and off to a pace that will change during the execution of the program. Wave 2 passes from 1 kHz to about 6 kHz while needing to be pretty accurate to the tenth of a Hertz.

  Initially, I tried to manage the simultaneous output of signals at different frequencies using a single task on a single 9477 daqmx in a cdaq-9174 chassis. As far as I know, the best way to get a specific frequency in a waveform output is to set the sampling frequency up to 2 times the frequency of the wave that is generated and generate a waveform that is given to each clock cycle. This works very well when it comes to a gesture, but I was unable to get the frequency of the modulated wave (wave 1) remains constant when the frequency of wave 2 modified or vice versa.

  I have a few other modules lying around (another 9477, 9403 and 9476) and I thought I would try another task running on a separate module. I find myself receive error-50103 message if I add these modules to my cdaq chassis and run one of the waveforms of a task set to run on the add-on. Is there a way to bypass this error? I guess it would cause by running two digital output on the cdaq-9174 tasks at the same time, but it seems to me that this wouldn't be a problem with an additional module.

  How can I have two outputs digital signals, running at the same time, maintaining their independent frequency frequency of the clock of the other sampling rate changes. In addition, because the wave 1 is enabled and disabled at a defined frequency, I use it to set the number of samples to write when you write a range of waveforms in the module (when generating these two waveforms on the same module).

  I'm sorry if the explanation was difficult to understand. I've attached an example of error 50103 lifting. This isn't really a part of my project as a whole, but it is the easiest way to reproduce the error.

  Thank you

  Hi awol.

  I have a follow up for you. You encounter the error because the cDAQ chassis has only a timing engine of. You will not be able to perform simultaneous tasks of the call by the hardware. Please see the following knowledge base: http://digital.ni.com/public.nsf/allkb/5E0B829E50ADE1BC86257AC50062B2D2

  Mike

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

• Sharing of Variable error-1950679023 in LabVIEW 8.6.1

  Hello

  Is anyone else having problems with this error after installing LabVIEW 8.6.1?

  Programs using variables shared that I wrote (and worked), just in older versions don't seem to work.

  Kind regards

  Sarah

  Hi Sarah,.

  Good afternoon and I hope that your well today.

  Sorry for the delay...

  I've did some more research and found that there is a patch for LabVIEW 8.6.1 and variable - could this be the cause of your faceing...

  Link: http://joule.ni.com/nidu/cds/view/p/lang/en/id/1255

  "This is an update to only LabVIEW 8.6.1 solve a problem when the variable path related is incorrect after variable deployment."

  You don't seem to have proved the issue about outside of your code - I go to the update being installed and not the goal of the solution to reproduce your problem.

  Finally, please run - but do not uninstall! the attached MSIBlast tool. It will list all the packages OR (Packages MSI) installed on the machine. Please note that the list should include,

  Client Variable nor to RT + versions Supprt

  Support for versions + OR motor Variable

  Variable Manager OR

  ... to name a few.

  I would be interested to know if they appear in the list,

  Hope this helps,

• Error 1050 trying to use load 'filename' in matlab script node

  Hello

  I get error 1050 when Labview is trying to load a text via the node of matlab script file.

  I have all ready checked for her on this forum and google but found nothing. I also did this: http://digital.ni.com/public.nsf/allkb/2B3FF46C8512C4F786256CF30071BE53 and tried to use dlmread and much more.

  The thing is that I need the node matlab script for reading a txt file that Labview made a chart with 1 single table, draw the it and export a jpg image. I can't really use the 'export picture' or 'get image' function for cause of Labview, I need the whole route chart (these functions only take a snapshot of it when they are run).

  It's my code I use:

  Data = Load ('file');

  VPP = (Data (1:2000,1));

  XSIZE = (1/2000);

  Plot (0.0005:0.0005:1 VPP);

  axis ([1 0 5 - 5]);

  print ('-images ', 'graph.jpg');

  The usual matlab load to load txt files and print to print the jpeg format. The code works in matlab, but not in labview

  And Yes, I use windows 7 and legal versions of matlab r2009b and Labview 2009

  Hehe, I thought about it

  Path must be converted to a string and skip the ' in the file.

  He worked

• 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 continuous acquisition and triggering

  Hi all

  I'm ai0 data acquisition: 3 4 analog inputs (voltage) in continuous mode, display the data (tables and graphs) and data flow to TDMS files in a loop of the consumer.

  The same time, I want to be able to save "time windows" with my purchase. For example, I want to be probe ai1:2 and when the voltage exceeds a certain value, that is to say 0, 5V, I can trigger with analogue reference and get a certain amount of samples (finished samples) after and before (samples before). I am aware of how I can achieve this, an example of NOR is more useful: http://sine.ni.com/devzone/cda/epd/p/id/4840 .

  The problem is this: I don't want to stop the continuous acquisition which is already underway. If I try to start a new task (somehow "copy & paste" the example) that I get, as expected, error-50103, "the specified resource is reserved.

  So, is it possible to accomplish this task without having to fall on reserving resources problem? And if there is not a way could you suggest a way to make this front trigger and trigger sampling?

  Please find enclosed a snapshot of the code. I use a PCI-6254 with two SCB-68.

  Thank you and looking forward for you advice!

  Best regards

  Panos

  Have you seen this?

• 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