about global task for counter

[dragondriver]

Hi all,

  I am trying to create a global task in MAX for counter output. In the MAX, while creating the task for counter, I input the specific high time, low time and idle state. However, when I use the task as following, it ask me to import high/low time again. So if it requires those initial parameters in this way, why there is GUI in the MAX to create the rnage for the task?

[GerdW]

Hi driver,

as we already stated yesterday a task only define the hardware (and their settings) needed for the job. It does NOT define the actual output value!

In MAX you define a range. But when you use that task in LabVIEW you still want to output a value, hence that input is needed...

[dragondriver]

---

@GerdW wrote:

Hi driver,

as we already stated yesterday a task only define the hardware (and their settings) needed for the job. It does NOT define the actual output value!

In MAX you define a range. But when you use that task in LabVIEW you still want to output a value, hence that input is needed...

---

Thanks for the reply. I understand that but just don't know why if that's the case, what's the point to provide Pulse Output Setup in MAX.

[JÞB]

See that big blue run button in the DAQ Wizard?  That's the only reason the Wizard needs that information.  its not a persisted property of the task.

[dragondriver]

---

@JÞB wrote:

See that big blue run button in the DAQ Wizard?  That's the only reason the Wizard needs that information.  its not a persisted property of the task.

---

Oh, I see. Thanks.

[JÞB]

---

@dragondriver wrote:

---

@JÞB wrote:

See that big blue run button in the DAQ Wizard?  That's the only reason the Wizard needs that information.  its not a persisted property of the task.

---

Oh, I see. Thanks.

---

Sometimes, its easy to confuse an object property with an argument for one of its methods.  In this case, we need some parameters to invoke the Run method on the DAQmx Task.

[dragondriver]

---

@JÞB wrote:

---

@dragondriver wrote:

---

@JÞB wrote:

See that big blue run button in the DAQ Wizard?  That's the only reason the Wizard needs that information.  its not a persisted property of the task.

---

Oh, I see. Thanks.

---

Sometimes, its easy to confuse an object property with an argument for one of its methods.  In this case, we need some parameters to invoke the Run method on the DAQmx Task.

---

Yes, it is true.

It is confusing me because if I input the wrong parameter like high time set to zero, I cannot save the task in MAX, that's give me a illusion that the task is bind to the parameters I set there. By thanks anyway.

[John_P1]

The counter high/low time should persist.  You can change any of these parameters at runtime if you want (i.e. by calling DAQmx Write), but if you just start the task without changing the parameters it should give you what you configured in MAX:

Best Regards,

[dragondriver]

---

@John_P1 wrote:

The counter high/low time should persist.  You can change any of these parameters at runtime if you want (i.e. by calling DAQmx Write), but if you just start the task without changing the parameters it should give you what you configured in MAX:

Best Regards,

---

---

Hi John, I run the same code as your did except for my code is run in 2013 and the DAWmx Write is a polymorphic VI, will it make any difference? Anyway, I did get an error while running the code similiar to your, so it seems that the high/low time configurated in MAX doesn't not presist?

[John_P1]

My code doesn't have DAQmx Write at all.

Best Regards,