09-01-2009 03:59 AM
rolfk wrote:I'm not sure how that redundancy already exists today. You can't AFAIK drop in a VI in the CBR to be called instead of having to wire a VI reference to it.
No, but if you right click a subVI and select Call Setup and one of the dynamic options, it will be wrapped in a "static" CBR which has no reference input. This admittedly is not exactly the same, since it does have additional functionality (the loading-unloading part), but it is the same syntax.
09-01-2009 04:03 AM
09-01-2009 07:27 AM
F. Schubert wrote:...
Questions on Bens Code:
* Is the logger launched multiple times?
* Am I correct that you pass the VIRef via Class to the launched vit instance? So it closes the reference on it's own (but auto dispose ref is set to true)?
Felix
Yes it is launched multiple times. here is the SSD (System Sequence Diagram)
That app require reconfiguring the hardware inbetween acq cycles so one the new configuration is established and everything is ready to go, the logger is created.
Good eye re: the "Auto Dispose Ref" = True !
I wonder why it working.... (maybe because I am forking the ref and stuffing it into a class ???)
The data is getting logged as I expected. Hmmm....
Thank for the heads-up!
if you have any other comments, let them fly since I am still trying to learn OOP.
Ben
09-02-2009 07:57 AM
Felix,
The owning app input is a safety issue that may no longer be necessary. If the application is not wired, it defaults to the application of the calling VI. However, I remember there are/were some weird cases where the application would not be set correctly, so I always set it. But, this information is several years old and could be LabVIEW 8.0 or 8.2 specific or only pertinent to internal development at National Instruments. I have been trying to track it down, with no current success. I will let you know when/if I find out anything.