> I have two questions.
> 1) I haven't gotten data to update properly in the subvi. The "Get
> Image" always snaps a picture of the default vi and without the
> values. What's the best way to pass the data in?
The Set Value method should work. Also, if the VI is not looping, you can
simply put it's panel in the sub panel, and call the VI like any ordinairy
VI, using it's connector pane to pass data. That is the best, if it means
"easiest". If best means the most scalable, you'll need a more elaborated
architecture (see 2)).
> 2) Is their a better architecture to use for this goal? I'm
open to
> other ideas it their is a more efficient and streamlined approach.
>
Yes. There probably are better architectures. Most of the time I create
seperated user events for each seperate type of info I need to communicate.
I put the user event in a buffer, and each dynamic VI that needs that info,
registers for it's events. Often those VI's are in subpanels, but sometimes
they are VI templates, so I can start multiple instances. Sometimes there
front panels aren't visible at all, for instance DAQ VI's. I don't mean to
say this architecture is the best, but it has been great for all my projects
so far.
Any good architecture will need a lot of effort and experience. Not only
experience with LabVIEW, but also with the kind of projects it is made for.
That is why thee is no "best" or "standard" architecture. A power plant
needs another architecture then a word processing program...
Regards,
Wiebe.
Search LabVIEW like a graph! 