DAQmx error code -200452

[bfeddeck]

I cannot find any detailed information on this error code.
I created a task with 2 counters. One Channel (Fuel_Press_Ctrl) is running at 100hz and the other (TachOut)is at 1000Hz. During the program they work fine. When I try to clear the task I get this error.
Property: CO.Pulse.Freq
Channel: TachOut
I did not have this problem until I added the 2nd channel (TachOut).

[Jens_DE]

Hi!
I haven't worked with counters so far, but
-200452 means DAQmxErrorAttributeNotSupportedInTaskContext
maybe someone can help you further.

Good luck
Jens

[Otis]

Are you trying to generate two finite pulse trains, or are you trying to generate two continuous pulse trains? Which board are you using?

If you are doing finite on an MIO board, then you will run into errors because a finite pulse train actually requires both counters.

"Finite pulse trains are produced in the same manner as continuous pulse trains, except that the counter is gated so that the gate is high for exactly the length of time it takes to generate the required number of pulses, then the gate falls low and no pulses are generated. Finite pulse trains require a second counter"
Taken from Generating a Pulse Train with a Counter 

However, if you are just doing two continuous pulse trains you shouldn't have a problem from a hardware standpoint.

[bfeddeck]

I have attached a VI with a case statement to show the error. I am using an M-series board PCI-6229.

[Otis]

The best way to create two counter pulse trains with two completely different settings is to simply create two separate tasks.

Here is a VI that creates two continuous pulse trains, one on each counter, and outputs those pulse trains on the assigned counters until the user stops the operation.

[gus]

The error with the attached VI is occurring because your assistant task is configured in a "as time" manner (high time/low time) whereas the property nodes you are using are "as frequency" (frequency/duty cycle). It is strange (and quite possibly a bug) that you are not getting an error with the Write VI call in this program. I'll have to look into that more. For now, you shouldn't get that error if you modify the high time and low time properties instead of the frequency/duty cycle ones.

I hope this helps!
gus....