Error -201133 occured at DAQmx Start Task

[ThiCop]

Hello Christophe,

I'm happy to hear that you were able to resolve the issue!

When you're using the test panels in MAX, then you're also calling code.

The Test Panels and DAQ Assistant (used to configure a task)  for your DAQ cards are also made in LabVIEW by using DAQmx VI's.

So in this case the problem would still reside in one of 2 things:

- Changes in the DAQmx driver and or VI's that are used to make the test panel/DAQ assistant

- Changes in the code behind the test panel/DAQ assistant

I'm just adding this information to provide you the complete feedback.

[Christ0phe]

To stop upgrading to newer versions of DAQmx/MAX and downgrading the stations that are already in higher version than MAX 4.6 is not an acceptable solution I am afraid !

Nothing is resolved and worse, I do not know which steps I need to follow now to better understand what is going on.

Thanks to let me know

Christophe

[ThiCop]

Hello Christophe,

That was why I was trying to find a solution together with you, but this would be a solution that requires changes in code.

I will help you find a solution, but it will require code changes and also tests from you.

I have loaned a 9172 with 9401 in the 5th slot from a colleague of mine and I will do tests at my side. (That was also why I could not do the hardware tests at my side)

The first indeed indicated that

With the tasks you defined and the channels the same as in the tasks you sent me, you do get the error.

I'll now further troubleshoot at my side to check where the source of the error resides.

Is this an agreeable troubleshooting process for you?

[Christ0phe]

Everything that will move me closer to resolving the issue is good for me!

Let me know what I can do next.

Thanks for your support.
Christophe

[ThiCop]

Hello Christophe, I have made a very basic example (DO and Pulse Train in parallel) that should work. Can you test this? It worked over here with LabVIEW 2011 and DAQmx 9.3.5. Remarks: You have to place the Control Task VI and also the DAQmx Start Task VI for the DO. If you don't do both, then you'll receive the same error. Is it based on this clear what you'll have to do in your application? If you have any questions, then you can always contact me.. "The attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system, or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense"

[Christ0phe]

I do not see any code attached.

Please attach a Labview 8.2 code as it is the version that most of our 100+ stations use to run those kind of application. The migration towards Labview 2011 is planned later this year.

Thanks again.

[ThiCop]

Here's the 8.2 code.

"The attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system, or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense"

[Christ0phe]

Hello again,

And sorry for my late reaction...

This is an update from my side: from your post and others I was able to compile a new code (see attached) that seems to work well. Nevertheless I have 2 questions left:

- In MAX 5.1: I said I could not start both tasks concurrently. In MAX 4.6.1 I could. Well this was true with a 9172 connected to my PCs. If I connect a USB-6210 the problem disappears in MAX 5.1. Although the 6210, as well as the 9172 are both with an exclamation mark related to the USB hotfix (although I have applied Microsoft fix suggested by NI)... Strange, isn't it?

- In the code you will notice that in the subroutine called Injector Driver.vi I had to make a very sloppy (but maybe necessary) programming to take care of the fact that people can select a PWM of 0% or 100%. In that case I read that I needed to stop the counter task, restart it with a different setting, then stop it once more... Please check the code. Is it really the only possibility to have my code smoothly change from a x% to a 0 or 100% PWM then back to a y%,...?

Note that I am now working with 2xcounters out and one digital output. What I discovered for 2 tasks in the past are the same as with 3 tasks now...

Thanks for your support

Christophe

[ThiCop]

Hello Christophe,

This is indeed special.

One thing you however have to keep in mind that there's also a functional difference between the cDAQ platform and the USB M-series cards.

In the case of cDAQ you'll use C Series Modules and in the case of USB M-series you have one card on which everything is integrated.

This could explain the difference in how the tasks are created.

The issue that you experience did not seem to be caused by the warning, but by the setting of the DAQmx States.

Regarding the 0 to 100% of the PWM:

Does your duty cycle have to be exactly 0 and 100% or can it also be (for example) 0,5 and 99,5 %?

[Christ0phe]

Hello again,

1/ So about my issue with the cDAQ, what are the next steps? Do you consider that I just have to live with it? The fact that it is MAX-version dependent is something really weird and I really would like to resolve it especially considering the number of cDAQ that we have throughout our company.

Also I do not really catch what you said here:

The issue that you experience did not seem to be caused by the warning, but by the setting of the DAQmx States.

2/ Yes, PWM should be exactly 0 or 100% in some cases.

Thanks for your answers

Christophe