Events or notifiers

[markstab]

i have tested a vi that produce data that must be connected to the same vi serialy (the input of the second vi connect to the output of the first) and so on connect new (same) vi serialy with variable depth. to avoid pooling and send data between vis only when necessary i need to use some technic as events or notifiers. With events (LV7) there is a problem to register the new evnts with new consecutive names according to the depth level cause the control name of the input of the next vi could not be changed programmaticaly. Could that be avoided by call by reference and send by some way new parameters? Or the other way i see is to use notifiers but here i can not miss data, then what could be better solution?

[CoastalMaineBird]

I may be missing something, but that sounds like a case for a WHILE loop with a shift register.
The VI's output goes to a shift reg on one iteration, the shift reg goes to the VI's input on the next. You only need one instance of the VI in that case.

Why do you need several instances of the same VI?

[markstab]

Sorry about my explanation,
i receive continously data (events) from activeX that i want to analize in the first vi and write to files the events and analized data from that level, also the data produced on that level i want to fire simultaneously (when the data are available) to next level which is the same analisys (the same vi) and so on with depth depending on the data. i made that with arrays and serialy connected vis and that works, but the structure is static-only for testing. maybe that could be made with notifiers but the question is how to avoid missing events between vis.

[Jeremy Braden]

You may want to use the old style activeX event VIs. There is a shipping example that queues up multiple events. I found it in 6i but it is probably in 6.1. LabVIEW 7 does not have the same VIs for activeX events but they still shipped. You can locate them at:
C:\Program Files\National Instruments\LabVIEW 7.0\vi.lib\platform\ax-events.llb .

[markstab]

thanks for the example Jeremy,
that is not a problem, i receive the events in the first vi (level) and the output from that vi after analasing i want to connect to other vi on the second level which make the same functions as the first vi and so on undefined depth of connected serialy vis. the question is: when i fire event to the first vi and after some calculation the data comes out from that first vi i want to send them also by some kind of events to avoid pooling to the input of the second vi. Cause the diagram of the vi is the same i want to combine if possible programatically calling that vi on every level of depth when necessary and also avoid pooling in every vi without missing data
is that seem to much?