Error -201133 occured at DAQmx Start Task

[ThiCop]

Hello Christophe,

About the different questions:

1) First of all I would like to clear up a misunderstanding. It is not my goal to "force" you to live with it.

However, my first goal was to provide you with a work-around/ (temporary) solution for your issue.

As a next step I can file a Corrective Action Request internally about this issue, so that the developers can look into this issue and perform certain changes or provide a reason why this change is necessary.

What I meant with the text "The issue that you experience did not seem to be caused by the warning, but by the setting of the DAQmx States." was the following:

"It does not seem that the Hotfix warning is causing the problems/changes/differences between the two versions of the application (and of MAX)."

2) Wiring a 0% or 100% directly to you Counter Freq will cause an error to appear.

If you don’t want to have the “sloppy code” , then you can also force your values to coerce to the Maximum and Minimum Values that are allowed.

Dependent on your card this can be something like

Minimum: 1,19 E-7 (or 0,000 000 12)

Maximum:  0,999 999881

In most cases I do this, but if these values are  also not ok for this application, then you would have to implement a work-around (like you have done in your application).

[Christ0phe]

Hello again,

1/ I do not consider the problem resolved because I am still unable to test my tasks in the MAX environment. (V5)

2/ 0% and 100% sharp are a must in my case. If there is a cleaner workaround I will be glad to implement it.

Thanks

Christophe

[ThiCop]

Hello Christophe,

First of all thanks for your reply!

I have been Out Of Offic from last week up to now.

About the 2 different topics:

1) The next thing I can personally do to help you is to internally file a Corrective Action Request to get the "old behaviour" of MAX back.

2) Regarding the smoother way to do this.

If you really need the 0% to 100% range when using this combination of hardware and DAQmx functions, then this will require a work-around comparable to the one you currently have.

Regarding possible other ways to implement this work-around:

Are there certain limitations regarding the top-level architecture of your application?