Counter/Timer

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmxCreateCOPulseChanTicks -200077

I am using the 6602 board and the c++ libraries.  When I try to create a continuous pulse using 1 as the pulse width I get the -200077 error.  So I am assuming that there is a minimum width or > 1.  Is that correct?
0 Kudos
Message 1 of 6
(5,489 Views)
Hi dck,

Can you please post the exact error message that is given? That error code means you tried to use a property or functionality that that board doesn't support and the error dialog will tell you what functionality is not supported. If you look in the DAQmx C reference help you will see that there is a high ticks and low ticks input. I assume that when you said you put a 1 in for pulse width you put a 1 for both of these inputs. Is this correct? Take a look at some of the shipping examples found at C:\Documents and Settings\All Users\Documents\National Instruments\NI-DAQ\Examples\DAQmx ANSI C\Counter\Generate Pulse for good examples of how to properly set this up.
PBear
NI RF
0 Kudos
Message 2 of 6
(5,468 Views)
My error I am sending in a 1 as the low time for the pulse not the pulse width, so here is the information you requested.

The complete error message is:

error: -200077 running command: DAQmxCreateCOPulseChanTicks( H_TR ) output: Requested value is not a supported value for this property.

The code I am using is:

DAQmxCreateCOPulseChanTicks( taskHandke, "Dev1/PFI39", "", DAQmx_Val_Low, 0, 1, 101 )


I have previously looked at the example codes, unfortunately it only shows the DAQmxCreateCOPulseChanTime and the manual gives no indication
if there are min/max values that can be used for this parameter.  Note that I implement the same
signal using the DAQmxCreateCOPulseChanTime for testing and it works however when the times are converted into ticks and a value of 1 is supplied
for the lowticks then I get the listed error.

0 Kudos
Message 3 of 6
(5,464 Views)
Hi dck,

Try putting ""Dev1/ctr0" and wiring to pin 5 (PFI 36) as your channel name. Also, what timebase are you using?


Message Edited by PBear on 05-05-2008 03:51 PM
PBear
NI RF
0 Kudos
Message 4 of 6
(5,461 Views)
Is this the commad you wanted?

DAQmxCreateCOPulseChanTicks( taskHandke, "Dev1/ctr0", "", DAQmx_Val_Low, 0, 1, 101 )

The same error occurs with this.

I am using a 5MHz external clock for now.
0 Kudos
Message 5 of 6
(5,456 Views)

Hi dck,

I did some checking into this error and it turns out that the minimum value for both high ticks and low ticks is 2.  Try increasing the number of low ticks to 2 and you should not get this error.

Here is the function call that I was using:
DAQmxCreateCOPulseChanTicks (TaskHandle, "Dev1/ctr0", "", "",DAQmx_Val_Low, 0, 2, 101)

When the second last parameter is set to one, I get the same error that you were seeing.

Chris_K

 

0 Kudos
Message 6 of 6
(5,438 Views)