03-24-2006 06:01 AM
03-24-2006 06:21 AM
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
03-24-2006 06:24 AM
03-24-2006 10:16 AM - edited 03-24-2006 10:16 AM
Message Edited by phili on 03-24-2006 10:16 AM
03-24-2006 11:43 AM
I had a similar need not too long ago except I was running under Fieldpoint RT some of the time and from a Windows PC some of the time.
I learned that templates are not supported under Fieldpoint RT -- perhaps this restriction also holds for PC-based LabVIEW RT? I ended up with 2 work-arounds:
1. Poor-man's template: I would manually perform a file copy from the "template" vi to uniquely-named instance vi's. These simply had a numeric value appended to the base filename, just like a real template vi would have done. Here are the pros/cons. The file copy was VERY slow under Fieldpoint because the file system is implemented on slow flash memory. It took many seconds to instantiate a handful of vi's through the file copy process. This is unlikely to be a problem on a PC-based file system. Unlike real templates, these didn't prompt you to save if you closed the front panels. I had to manage deleting the files when done -- not a big deal, just another bit of housekeeping. And because they were regular vi's, the front panels could be opened for interaction and monitoring of the control loops.
2. Reentrant vi. This launched separate instances reasonably quickly. However the front panels could not be used for interaction or monitoring.
I used technique 1 for most of the development so I could use the front panels for debug purposes. Then I switched to technique 2 for the final app to get rid of delays when instantiating vi's.
-Kevin P.