DAQmx Error: -200428

I tried to run my application on the PDA, and it works for one iteration. Then it displays an error message: Value passed to the Task/Channels in control is invalid. Error code: -200428.
After looking at the solutions on the website, I still cannot figure out what's wrong with the application. I think it's the way my task is configured. I am using NI 6004 card on a Pocket PC 2003 device. Right now I have two custom tasks on the task list: analog input (enable all 4 channels) and digital io (enable all 4 channels), which I created on the NI-DAQmx Base Configuration Utility. I deleted all the previous imported tasks for my device. Would that contribute in causing the error? Now I am unable to retrieve any tasks for Dev5: NI 6004 Pocket PC 2003. I already looked at the default task lists from the NI DAQmx --> examples --> Labview PDA 8.0, but none of them are compatible with Dev5, so I still could not retrieve those tasks I deleted before.
I'm not sure what to do. To anyone dropping by an advice, thanks for helping!

Hi Teresa,
Error -1073807343 is caused when
no USB device is connected to the PDA. This information can be found in the KnowledgeBase
article, Errors with USB and NI-DAQmx Base on PDA. It may be
that your PDA’s USB port does have hosting capabilities needed to control the
USB-6008. Your PDA must have the ability to act as the master USB device. I was
not able to find any technical specifications for your model PDA. In addition to this the PDA must be able to
provide enough power for the USB-6008. Typically the USB-6008 uses 80 mA. The
maximum it uses is 500 mA. This information is in the NI USB-6008/6009
User Guide and Specifications.
Please let me know if you have any questions.
Thanks,
Nathan
National Instruments
Digital Hardware Engineer

Similar Messages

DAQmx Error -200428 occurred at Write Dig Chan.vi

Hello,
I am trying to read the task name, channel name, and physical channel from a configuration file and using this information create a DAQmx task and two global virtual channels. Everything seems to be working ok (no error) until I am trying to write to one of the channels, then I get an "Error -200428 occurred at Write Dig Chan.vi". What am I doing wrong? Thanks for your help.
Peter
Attachments:
Write Dig Chan.vi ‏37 KB

Hello Corey,
I tried it out for both the Write Dig Chan.vi and the Write Dig Chan (modified).vi, but in both cases, I get the same errors as before.
Write Dig Chan.vi Error -200428
Write Dig Chan (modified).vi Error -200587
Attachments:
Write Dig Chan.vi ‏38 KB
Write Dig Chan (modified).vi ‏44 KB

Error -200428 on DAQmx Write

Hello,
I am new to DAQmx, so please forgive me if this is a trivial question. I created several DAQmx tasks in LabVIEW, then wrote my vi automatically generating the configuration code by right-clicking a DAQmx Task constant and selecting generate code. When I run the Standalone Solenoid Controller.vi in the Standalone Modules folder, I get a Error -200428 during the first call of DAQmx Write.vi.
What is going on? Please advise. Thank you.
Best regards,
Peter
Attachments:
Solenoid Controller.zip ‏657 KB

The problem with having a single task is that you have designated those channels to be used for that task. Once that has been done, you shouldn't be able to put those channels into another task or use them on their own.
When wiring the channel into the DAQmx Write, a task is created. That task is what is passed out. So by having that channel already designated for a task, you can't put it into another one. You need to either write to everything with a single task or separate them into multiple tasks.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Static task Error -200428

I am using Labview 8.2 with an AI Input card 9215 on CDaq 9172. The application uses a static task to read the voltage(displacement).
The app works fine, except when the app is closed(using the x in the top RH corner), then restarted I get the error -200428 at DAQmx Start Task.Vi(Value passed to the task/Channel is invalid). The only fix is to restart the PC.
I have checked that the Stop Task VI is called when the app closes. I have tried resetting the Daq device using Max but it makes no difference.
I believe there is some problem in my code closing the task properly, hence the need to restart the PC to release task resources.
Any suggestions ?
Attachments:
simpleVi.JPG ‏18 KB

Enclosed a simple Vi that demonstrates the installed app. I have used a simulated CDaq device (identical to the customer cDaq)on my development PC and the simple VI works fine(both built as an exe and just running the VI on the development PC). The static task is identical to the task on the production app that is giving problems
<Item Name="VoltageIN" Type="NI-DAQmx Task">
   <Property Name="\0\AI.Max" Type="Str">10</Property>
   <Property Name="\0\AI.MeasType" Type="Str">Voltage</Property>
   <Property Name="\0\AI.Min" Type="Str">-10</Property>
   <Property Name="\0\AI.TermCfg" Type="Str">Differential</Property>
   <Property Name="\0\AI.Voltage.Units" Type="Str">Volts</Property>
   <Property Name="\0\ChanType" Type="Str">Analog Input</Property>
   <Property Name="\0\Name" Type="Str">VoltageIN/Displacement</Property>
   <Property Name="\0\PhysicalChanName" Type="Str">AnalogIN/ai0</Property>
   <Property Name="\1\AI.Max" Type="Str">10</Property>
   <Property Name="\1\AI.MeasType" Type="Str">Voltage</Property>
   <Property Name="\1\AI.Min" Type="Str">-10</Property>
   <Property Name="\1\AI.TermCfg" Type="Str">Differential</Property>
   <Property Name="\1\AI.Voltage.Units" Type="Str">Volts</Property>
   <Property Name="\1\ChanType" Type="Str">Analog Input</Property>
   <Property Name="\1\Name" Type="Str">VoltageIN/Loadcell</Property>
   <Property Name="\1\PhysicalChanName" Type="Str">AnalogIN/ai1</Property>
   <Property Name="Channels" Type="Str">VoltageIN/Displacement, VoltageIN/Loadcell</Property>
   <Property Name="Name" Type="Str">VoltageIN</Property>
   <Property Name="SampClk.ActiveEdge" Type="Str">Rising</Property>
   <Property Name="SampClk.Rate" Type="Str">20</Property>
   <Property Name="SampClk.Src" Type="Str"></Property>
   <Property Name="SampQuant.SampMode" Type="Str">Continuous Samples</Property>
   <Property Name="SampQuant.SampPerChan" Type="Str">100</Property>
   <Property Name="SampTimingType" Type="Str">Sample Clock</Property>
   </Item>
However on the customer PC it throws the error -200428 even after a restart of the PC
Any ideas would be appreachiated
Attachments:
StopTaskOnPanelClose.vi ‏61 KB

Error -200428

Hi,
I am trying to run a program that logs temperatures but I am having the following issue:
The program as a vi works it logs the temperatures and saves all the data like expected. Also if i run the executable on the same pc that created the exe it works. However when I make it into an excutable and try to run on another pc the program stops giving me error -200428 and states "Property Node DAQmx Timing (arg 1) in DAQmx Timing(Sample Clock).vi:1->16_ThermocoupleDAQ(Triggered).vi<append><B>Task Name:</B>LogData" How do I fix this error?
Please help this is quite urgent.
Thanks
Chris
Solved!
Go to Solution.

What I'm saying is that when you create an installer in your project, one of the options is to export the MAX config and then include that and when run on a new pc, that config will be imported into MAX.
If you want, you can manually export a MAX configuration and manually import one. Just look under the File menu in MAX. You would need to install MAX.
You could also place all of the required configuration steps in your program instead of hiding some of it in MAX.
Message Edited by Dennis Knutson on 02-26-2009 12:06 PM

USU 6009 counter error: DAQmxBase Error -200428

I want to use USB 6009 as an edge counter. I got this ouput :
create task
createCounterChan
start task
DAQmxBase Error -200428: Value passed to the Task/Channels In control is invalid.
with following code:
// Channel parameters
   const char counter[] = "Dev3/ctr0";
   // Read parameters
   uInt32 readArray[1];
   uInt32 arraySizeInSamps=1;
   uInt32 initialCount=0;
   int32 numSampsPerChan=1;
   int32 sampsPerChanRead;
   float64 timeout=100;
   DAQmxErrChk (DAQmxBaseCreateTask ("", &taskHandle));
   printf("create task\n");
   DAQmxErrChk (DAQmxBaseCreateCICountEdgesChan (taskHandle, counter, NULL, DAQmx_Val_Falling, initialCount, DAQmx_Val_CountUp));
   printf("createCounterChan\n");
   // Start Task (configure port)
   DAQmxErrChk (DAQmxBaseStartTask (taskHandle));
   printf("start task\n");
   DAQmxErrChk (DAQmxBaseReadCounterU32 (taskHandle, numSampsPerChan, timeout, readArray, arraySizeInSamps, &sampsPerChanRead, NULL));
   printf("Data read: 0x%X\n",readArray[0]);
Please help

Hello nguyendyhung,
Thank you for posting to the discussion forum. Here is a KnowledgeBase that explains this error.
NI-DAQmx Base Error -200428
http://digital.ni.com/public.nsf/websearch/7705D38D59EF562886256F79007E4B5A?OpenDocument
This document is going to reference LabVIEW, but the theory is still going to be applicable with your code. You can get this error message if the task is not configured correctly.
Also take a look at some of the shipping examples that come with DAQmx Base. You can find them in the following folder:
C:\Program Files\National Instruments\NI-DAQmx Base\Examples
Please take a look at these resources and let us know it resolves your issue.
Regards,
Sandra T.
Applications Engineer | National Instruments

Why do I get error 200428 from executable?

I have a NI-DAQ application running correctly using a project under development LabVIEW 8.6 and NI-DAQ 8.8. When I use the exact same project to build the executable on the same PC, I get error 200428 - "Measurements: Value passed to Task/Channels In control is invalid" on startup. How could this be? I am using DAQ tasks built with the DAQ wizard and stored in the project.
Solved!
Go to Solution.

I am well aware that the executable is not the project. LabVIEW executables, however, are always built within project context. The NI-DAQ tasks defined inside the project are part of that context. If I make the NI-DAQ VI a top-level VI and build the executable, everything works fine. It is something about embedding this VI in a larger application (executable only, not development) that is causing my problem.

Daqmx error num: -50103 with message: The specified resource is reserved. The operation could not be completed as specified.

Hi, I am running a program where I have 4 nidaq cards on a single machine, all connected. I am trying to start a counter and keep getting that error (daqmx error num: -50103 with message: The specified resource is reserved. The operation could not be completed as specified.) in two places in my code. I understand what the error means (you can only have one task of a type per card), but I don't see where that is occuring in my code.
See below for code. I noted the two places where the error is occuring. I am debugging someone else's code, which is part of the problem.
Thanks!
counterTask = 0;
daq_err_check( DAQmxCreateTask( "counter_generation_task",
&(counter_generation_task) ));
daq_err_check( DAQmxCreateTask("counter_count_task",
&(counter_count_task) ));
char co_chan_name[40];
char ci_chan_name[40];
char ci_trig_chan_name[40];
sprintf( co_chan_name, "%s/ctr0", niDev);
sprintf( ci_chan_name, "%s/ctr1", niDev);
sprintf( ci_trig_chan_name, "/%s/PFI9", niDev);
printf("OK1");fflush(stdout);
daq_err_check( DAQmxCreateCOPulseChanTicks( counter_generation_task,
co_chan_name, "", "ai/SampleClock",
DAQmx_Val_Low, 32,16,16) );
daq_err_check( DAQmxCfgImplicitTiming( counter_generation_task,
DAQmx_Val_ContSamps, 1000) );
daq_err_check( DAQmxCreateCICountEdgesChan( counter_count_task,
ci_chan_name, "",
DAQmx_Val_Rising, 0, DAQmx_Val_CountUp) );
daq_err_check( DAQmxCfgSampClkTiming( counter_count_task,
"Ctr0InternalOutput", 1000.0, DAQmx_Val_Rising,
DAQmx_Val_ContSamps, 1000) );
daq_err_check( DAQmxSetRefClkSrc( counter_generation_task, "OnboardClock") );
daq_err_check( DAQmxSetRefClkSrc( counter_count_task, "OnboardClock") );
printf("abt to start counter_count\n"); fflush(stdout);
daq_err_check ( DAQmxStartTask( counter_count_task ) ); // ERROR OCCURS HERE
printf("abt to start counter_gen\n"); fflush(stdout);
daq_err_check ( DAQmxStartTask( counter_generation_task ) ); // ERROR OCCURS HERE
fflush(stdout);
Thanks again for your patience!

I get it when capturing from my mini DV cam (which is not controllable by FCP). To resolve, I have to click Capture Now a split second after I start the DV tape rolling.

DAQmx Error: Non-buffered hardware-timed operations are not supported for this d evice and Channel Type.

Hello,
I am new to NI and to data acuasition cards in general. I am trying to put an application togather that would play large audio file using NI9263.
And i am getting the following error.
DAQmx Error: Non-buffered hardware-timed operations are not supported for this device and Channel Type.
Status Code: -201025
Does my hardware support buffering ?
can i use the EveryNSamplesCallbackAO function ?
Any sample code, will be helpful at this time. Thanks.

Hi yma200,
Are you using a USB 9263? If so, this might be of help:
http://digital.ni.com/public.nsf/allkb/EC1968728E660B288625780700570D06?OpenDocument
If it doesn't help, can you please post the code that you have that is causing your error?
Regards,
Bogdan Buricea
Applications Engineer
National Instruments

DAQmx Error -200550

Currently I have a PXI-1000B, and I have opnly ever used the same card in the same slot. I have a much faster sampling card and I'd like to try it out but I receive this error message when trying to use it. The interesting problem is that there is a exact duplicate of the card that I am using right now in another slot and it also does not work, giving the same error message. I did not setup the lab so I don't know if there was a procedure to make the one slot operational that the other haven't recieved. Do I need to set up the clock somehow?
DAQmx Error -200550 occurred:
Hardware clocking error occurred.
If you are using an external reference or sample clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that its rate matches the specified clock rate. If you are generating your clock internally, please contact National Instruments Technical Support.
Status Code: -200550
Thanks

Hopefully this covers everything:
We have a NI PXI-1000B crate & several digitizer modules (2 PXI-5122 and 1 PXI-5152) in our lab. We have been heavily using one of the PXI-5122 with no problems, but need to move on to using the faster PXI-5152.
We find that we cannot read out either the 2nd 5122 or the 5152. They both consistently fail with "hardware clocking - error 200550". This occurs both while attempting to test the cards in MAX as well as while trying to sample with them. There is one difference between the errors, when rebooting the system, when the drivers access the cards the 5122 cards behave in the same way with green lights, however the 5152 flashes a red light before resuming a green light for access.
We have swapped modules and slots. Both the bad 5122 and the 5152 produce the same error in different slots, including the one the good 5122 normally operates in. We have also moved the good 5122 and it works fine in different slots, including the ones the bad modules fail in.
The bad 5122 was once repaired (replaced fuse) at NI for the same problem, but we have no history of repairs to the 5152. We "inherited" this setup from a technician who is now in another lab but reachable, so we don't know the exact history of the set-up.
It seems strange that both bad modules exhibit the same error. We're happy to try any other suggested tests here before sending them for repair. Any suggestions would be much appreciated.

DAQmx error 200279

Here's a link to a thread on the Measurement Studio discussion board dealing with DAQmx error 200279 (trying to read data buffer that has been overwritten while running continuous aquisition):
http://forums.ni.com/ni/board/message?board.id=232&message.id=2926&query.id=12659#M2926
These errors can be dealt with by modifying the RelativeTo and Offset properties of DAQmx Read. The same thing applies when using DAQmx in LabVIEW, so I thought this may be useful here.
Zador

Update:
Changing the priority under VI properties to a higher or time sensitive setting has helped decrease the build up of samples in the task and increase performance of the loop, but it seems that there are more issues possibly related to the number of visible items on a VI front panel. I have a number of objects that toggle their visibility based on which item is selected in a menu, and when objects with graphs are displayed, I notice performance dropping and samples accumulating. No solution yet.

DAQmx Error 88709

I'm running TestStand in conjunction with LabVIEW on a PXI/SCXI system. I experience DAQmx Error 88709 only when running my TestStand sequence file the first time after all equipment has been powered down. For all subsequent executions of the TestStand sequence file, I don't experience the error (everything runs fine). I can reboot the controller and I don't get the error. I only get the error after a complete power-down (all PXI and SCXI equipment).
In my attachment, the VI that causes the error is Output_Drive.vi. In this VI, I'm acquiring data from two PXI-5114 Digitizers. When the error occurs, data from the first digitizer is displayed on the front panel graph, but before the data from the second digitizer is displayed, the error occurs. Data from the second digitizer is coming from a PXI-6711 Analog Out card.
In my attachment, Error Report.bmp shows the error report that I get.
Any ideas will be greatly appreciated.
Attachments:
DAQmx Error 88709.zip ‏225 KB

Hello,
Do you get this error if you just run the VI in LabVIEW and not in TestStand?
Best Regards,
Adam G
National Instruments
Applications Engineer

An issue with DAQmx Error messages

Greetings,
I'm using a 6602 counter board with DAQmx 7.4, ANSI C API. A strange issue concerning the errors due to faulty attribute values keeps occuring, that being no error is reported when the (faulty) attribute value is set but only when it is read back afterwards. Shouldn't the faulty value be reported by the Set function?
To be specific, I'm creating a period measurement counter input channel with implicit timing, sample mode = finite, then setting the number of samples per channel to 0 (bear with me, I know the 0 value makes no sense here, the point is how the errors are being reported so that they can be handled in a reliable and consistent way). While DAQmxSetSampQuantSampPerChan(taskHandle, 0) does not produce an error, calling DAQmxGetSampQuantSampPerChan(taskHandle, &SampPerChan) for verification on the very next line returns Error -200077 : "Requested value is not a supported value for this property". So, my question is why the error is reported by the Getter instead of the Setter? Is this normal behavior (if so why?) or is something amiss here?
Jeff

This is the expected behavior. Validating attributes is tricky when attributes are dependent upon other attributes. There are two main approaches that can be taken by NI-DAQmx.
One, when every attribute is set, NI-DAQmx could verify the value of that attribute in the context of the task (i.e., in the context of all other attributes). This is problematic for at least a couple of reasons. One, validating the task after every attribute is set is time consuming and not efficient. Two, validating the task after every attribute is set requires that customers set attributes in a specific order such that dependent attributes are set after their dependencies. This would dramatically decrease the usability of NI-DAQmx. In fact, if attributes are mutually dependent, this approach is impossible.
The second approach is that NI-DAQmx doesn't verify the task until it is forced to do so. Starting a task forces it to be validated. Querying an attribute also forces the task to be verified since the value of an attribute may be dependent upon the value of another attribute.
As you've noticed, we've taken the second approach with NI-DAQmx. This approach leads to a more efficient execution as well as allow customers to set attributes in an arbitrary order. If you want to force the task to be verified in order to check for errors, you can do so explicitly at the desired time. However, the need to check attributes for errors is most often needed when the application is under development and the NI-DAQmx error reporting features makes it easy to determine which attribute has been set to an invalid value even when that error is not reported immediately.
Now, in reality, the way NI-DAQmx handles attributes is a bit more complicated than what I just described. Since some attributes are not dependent on other attributes or, since some attribute values can never be valid regardless of the values of other attributes, these attributes are verified when they are set and errors are returned immediately. We refer to this as coarse attribute verification. For example, if you set the sample rate to 100 MHz on an E-Series device you will immediately get an error.
Hope this helps clarify the behavior.
geoff
Geoffrey Schmit
Fermi National Accelerator Laborary

Error 200428 in linux example code

Hi All;
I'm trying to use the mx daq-base on a redhat 9.0 system. I have a 6031E installed(pci). I've installed the hardware, then the software and compiled the example code. When I try to run the writeDigPort example I get;
Device indentifier is invalid.
DAQmxBase Error: -200428
lsdaq reports:
NI 603E: "Dev2" (PXIO::16::0)
Nay ideas?
Pat

After further looking into the problem I'm getting an error -200220
here is the suspect code
char chan[] = "dev1/port0:1";
error1= DAQmxBaseCreateDOChan(taskHandle,chan,"",DAQmx_Val_ChanForAllLines);
DAQmxBaseGetExtendedErrorInfo (errBuff, 2048);
printf("\nDAQmxBaseCreateDOChan returned %d %s",error1,errBuff);
This gives the following output
DAQmxBaseCreateTask returned 0
DAQmxBaseCreateDOChan returned -200220 Device identifier is invalid.
Data to write: 0x55
DAQmxBaseGetExtendedErrorInfo returned -200428 Value passed to the Task/Channels In control is invalid.
Anyone have any idea?
Pat

Error -200428 Occurred at DAQmx Write (Digital Bool 1Line 1Point).vi

The working program started giving this program after we have had a hard_disk crash. We are just using the program that was backed up. Will appreciate any suggestions on this one.
Naresh

Have you read the explanation for the error and did you verify the task or virtual channels exist?

DAQmx Error: -200428

Similar Messages

Maybe you are looking for