force an daq vi to stop

[twrc]

I am upgrading a system from LV7 to 2012 which involves upgrading to Daqmx vis. However not all of the olddaq functions are directly interchangable with the new Daqmx vis. 

The system has 7 while loops for various functions. When the system is stoped local variables are used to shut the while loops down.  This worked before and still does with the exception of the Analog capture loop.

The analog capture loop is triggered by a function in the main loop and is acomplished with an occurance.  The analog fuction is based on the analog voltage read finite from the 2012 examples. The function is configured outside of the while loop and the read takes place inside the while loop when an occurance takes place.  The function works well but cannot be stopped.  The Analog read is inside the while loop and is waiting for the digital trigger to occur so it will not stop.  I have tried a number ot things but cannot find a way to abort this function.

Any idea would be appreciated

Thanks

[P@Anand]

Can you attach a snap shot of that loop which is not able to stop? (In any case 7 while loops is too much)

[apok]

---

@twrc wrote:

I am upgrading a system from LV7 to 2012 which involves upgrading to Daqmx vis. However not all of the olddaq functions are directly interchangable with the new Daqmx vis. 

The system has 7 while loops for various functions. When the system is stoped local variables are used to shut the while loops down.  This worked before and still does with the exception of the Analog capture loop.

The analog capture loop is triggered by a function in the main loop and is acomplished with an occurance.  The analog fuction is based on the analog voltage read finite from the 2012 examples. The function is configured outside of the while loop and the read takes place inside the while loop when an occurance takes place.  The function works well but cannot be stopped.  The Analog read is inside the while loop and is waiting for the digital trigger to occur so it will not stop.  I have tried a number ot things but cannot find a way to abort this function.

Any idea would be appreciated

Thanks

---

have you handled your errors properly? by wiring some kind of stop process to happen if found...and or you can send a notifier messege to multiplte loops for the wait on notification inside the loop wired to the stop, to stop the process. ofcourse, change the timout in ms to "0" to instantaneously stop

[apok]

also look under Help>>Find Example...type Search>>Notifier Demultiplexer.Vi, this is what you say," A Notifier is a "One-to-Many" tool. One data source can feed many data sinks."

Spoiler

[twrc]

Sorry I am out of the office until monday and I do not have the vi at home.

As far as the while loops go they are justified as there are a number of activities that are taking place and the most important activity is not slowed down by less important activities. There is a main loop that handles the most important issues; other while loops perform functions such as serial port transmit, serial port receive, sub panel functions, gps clock status, archiving, and analog capture.  The system communicates with a duplicate of itself in a remote location 555 miles away and shares information.  The system captures transients on HVDC transmission lines and determines fault locations. The system runs 24-7 and has been sucessfully operating in a number of countries for the last decade.  I am working on an upgrade to make sure it can operate with new computer systems and LabView development systems in the future.  The transformation from LV7 to LV2012 is almost done but I had some difficulties with the changeover of the analog capture VIs and was lookng for a quick fix.

I appreciate your interest and will send a pix of the loop next week.

Regards

[twrc]

Thanks for your reply

I must say that I have not taken a keen interest in error handling :o( which may be part of the issue however when i stepped through the shutdowm process the Analog read VI had a green arrow indicating it was still operating-actually waiting for a digital trigger so setting the timeout to zero would not help since it had already executed.  After thinking about it I will try to isolate the daq read vi so that it does not begin to run so it can be shut down.  This is probably an issue of understanding the occurance better.  See my previous reply on what the system is doing.

Regards

[twrc]

Thanks for your suggestion, I definately will have a look at Notifiers

Regards