Error -201133 occured at DAQmx Start Task

[Christ0phe]

I do not understand what information are misssing, I had attached the nce few messages above... Please explain in details if you still miss things...

[ThiCop]

Hello Christophe,

In the .nce file you sent, there seems to be a task missing:

"Commande Tension"

Is this task available in your MAX environment?

[Christ0phe]

Here it is. Although I do not understand why an analog output tasks would cause an issue to my PWM/Digital output.

Thanks.

[ThiCop]

Hello,

I just wanted to test your code as it is.

Two things that I saw during the first test.

This error popped up 2 times:

"Error -200462 occurred at DAQmx Start Task.vi:5
Possible reason(s):
Generation cannot be started, because the output buffer is empty.

...

Task Name: Commande Tension"

Do you also get it at your side?

If I continue, then I get the following error:

"Error -200526 occurred at Test_Digital_PWM_V2-cleanedUP.vi

Possible reason(s):
Write cannot be performed because this version of DAQmx Write does not match the type of channels in the task. 
Use the version of DAQmx Write that corresponds to the channel type.

Task Name: Commande Tension"

Is it normal that I get these errors?

Do you have code that works as is and that should only produce the error 201133?

The error 201133 I don't seem to get at my side however.

[Christ0phe]

Maybe this version will be easier to depict my issue...

[ThiCop]

Hello Christ0phe,

I just tested the VI with the provided .nce file.

I don't get this error message.

Is this PC continuously running?

Do you get this error also after a fresh restart or only after you run another application first?

Can you try a reset device (from inside MAX) and then run this last VI?

[Christ0phe]

Hello

1/ Fresh restart of the PC

2/ Launch the application : error out - Write CMD WAke up: error -201133

3/ Reset device successfull but when restarting the application, still the same error -201133

Note that when I click on the device in Max (it has an exclamation mark on it) it says:

You are currently using a USB DAQ device on Windows XP. Please visit ni.com/info and enter "WindowsXPUSBHotfix".

But its modules are well seen and all other functions work well (AI, AO)

What shall I do? I would like to remember that everything worked perfectly well with MAX 4.6.1...

Thanks

[ThiCop]

Hello Christ0phe,

Can you try using simulated devices for troubleshooting purposes?

Do you still get the same error in the application for that (simulated) device?

Did you already install the hotfix?

[Christ0phe]

Hello again,

Hotfix from Microsoft downloaded and installed. PC restarted. Warning message about the hotfix needed still there in MAX. Error message in my application still there and in MAX as well.

I have created a simulated device and recreated new tasks based on it and then no error at all (in MAX or in my app)

Thanks, I hope this helps you to further troubleshoot what is going on.

Christophe

[ThiCop]

Hello Christophe,

I think I might have found a possible reason for the error at your side.

If you look back at this KB (http://digital.ni.com/public.nsf/allkb/0495B7D5E2345DF386257730007EFD17?), then you see that there has to be a specific order in which the tasks are started.

I did not see this in your code.

Can you implement this order (first start the task without the DAQmx Control Task, then the one with it) in your code and test it again?

I think that the reason for the differences in behaviour between us both is that I had resaved your code at my side and by doing this, this probably will have recompiled your code and changed the order of execution.