how to solve the error of Counter input ( error code 200284)

[Yuzn]

dear sir

i use Counter Input channel to detect the pulse signal ,but the CI channel reminds me that the program can not sample all samples,the error code is 200284.

could you help me ? and i only  can acuqire about  8000 samples but i actuall need 16384 samples. thans you for your reply! 

[Kevin_Price]

The code you posted is quite a bit different from what was running when you captured your error message.  From what I can see, the code behind the error message didn't properly sync up the start of the different tasks.  If the pulse generation task started earlier than the pulse measurement task, you'd miss an unknown amount of early pulses and then get that timeout error after the pulses stopped arriving.

The code you posted appears to try to correct this problem by configuring triggers and sequencing the task starts.  I can't read most of the language, but things look largely ok.  Here are a few things to check more closely:

1. One tiny detail that I have a vague memory about is that you *might* need the ArmStart.TrigType property to be the first one at the top of the property node?

2. You've apparently set up your CI period measurement to use an external timebase at PFI3.  Is this timebase clock always present?

3. I don't think you even need the Arm Start triggers.  The CO task can use a regular Start Trigger.  And because you start the CI task before CO, the CI task doesn't need any triggering of its own.  It can't measure periods until the CO task starts generating pulses to be measured.

4. After you start the AO task, you could let your AO and CO task wait for completion in parallel to running your CI read loop.  You don't need to wait until after the CI loop is done the way your error wire sequencing forces things now.

-Kevin P

[Yuzn]

Thank you for you reply!

fortunately！i have been found the solution to realize the function which i need.

when i use CI Pulse Width Measurement instead of CI Period Measurement,the program do not

 remind me any error for example，error code 200284，the error code is  below! 

But i am really curious about the reason of this phenomenon ,could you tell me the reason?

by the way ,i delete the <relative to >property node setting in my program,because i discover this setting will make 

daq only reads first 128 datas in 128*128 datas every time ,but i need to make daq to read all 128*128 data.

and i also want to know how to configure the connecting line in program to use the <Start task>function ?is my program style right?

looking forward to your reply! you really give me so much help in my learn labview precess！

the right program is below.

if i use formal CI period measurement program(delete the <relative to> property node),the program will remind me this error.

but using CI Pluse Width Measurement do not have.

the error program is below.

the error code is below.

[Kevin_Price]

I can't read the details that are in your native language, but I *can* understand the bulk of what I see.   And I really can't identify anything that would explain why pulse width works ok while period measurement produces errors.   Does it happen consistently?  Does it happen on the first attempt to read or does it happen after some reads succeed?

-Kevin P

[Yuzn]

Thank you for your effort！

The error happens consistently. when i use labview example program to finish this single function,the example program also generate the error.

i have one guess for the error that the daq needs some reading data time when detecting the pulse in rising or falling edge.so in term of the reason,the program will lose some datas and generate the error 200284.

The other guess is that when i use pulse period measurement to achieve the function,the daq do not configure no or enough buffer for it.

this is my understand.

thank you for your help!

without your help,i guess that i can not love the labview so much!

[Kevin_Price]

Try this suggestion from back in my msg #2:  don't configure a start trigger for your CI period measurement task.  Just remove the DAQmx Trigger property node and see if it works.

Because you've done the other task start sequencing correctly, the Arm Start trigger isn't needed there.  (It also shouldn't *hurt*, but I don't have any better ideas right now.)

A second step might be to change the CO task to use a regular Start Trigger using the regular DAQmx Trigger function.   (Counter output tasks can use a regular start trigger, input tasks can't.)

-Kevin P