Reset buffer underflow

[ken hopkins]

I have an application where I send a buffer using  DAQmxWriteAnalogF64. It works fine until I get a buffer underflow. Then my it stops trying. Is there a way to reset the fault so that I can continue sending output?

[AdnanZ]

What exact error are you getting? Have a look at the following forums link and post back if you have any questions:

http://forums.ni.com/ni/board/message?board.id=250&requireLogin=False&thread.id=19597

[ken hopkins]

I get a 200290 error.

It appears that when the error occurs, the task stops.

Subsequent calls of the OnEveryNSamplesEvent results in the same error.

I need to reset the error and get the outputs going again as fast as possible.

I got some results by recreating the task but it take longer than the 0.1 seconds I have available. Beyond 0.1 seconds, I am destroying product. Beyond 0.2 seconds, I am destroying equipment.

I have increased buffers to prevent the error from occuring during normal operation but it can still happen because Windows is doing something. I need the system to handle the error and keep trying.

[AdnanZ]

As mentioned earlier, you might have to change the way you program the application right now. I did a search for the error and this link might really be helpful:

Error -200290 When Performing an Event Driven, Buffered Analog Output Operation with NI-DAQmx

[ken hopkins]

My code is capable of running a twice the designed speed without generating the error.

Unfortunately, being a Windows based application, things happen and may slow my application down - resulting in the error.

The code is rapidly moving an energy beam. If the beam stops moving for 0.1 or longer, the beam will burn through the product. A little longer will burn through the machine.

I have code to turn off the beam when the error occurs but that request is done through the ethernet connection. It may take longer that the 0.1 seconds to shut down the beam. For that reason, I need to keep the beam moving to give the beam generator time to shut down.

I have put in restart task code but it takes about 0.5 seconds to get the beam moving again. I am hoping a reset can be issued which would take less time.

My current belief is that the NI software is not capable of meeting the requirements.