LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Many-To-One Notification

None of the existing synchronization VIs work for "instantaneous" many-to-one notification, (or do they?)

Notifier is one-to-one or one-to-many,
Rendezvous is many-to-many
Occurances is one-to-many
Semaphore handles a different sync issue!

In many cases, one VI may need to wait for several other VIs before performing a task, simple example is on closing,

Even more specifically, other VIs could do the "notification" and continue, but the one VI must wait until those VIs have met (and passed) the "notification" point.

Although the mechanism can be built easily, it could be defined by NI as a standard VI.

Sia

LabView Control and Simulation Design Toolkit

-A simulation subVI fails to compile if an initial condition of zero exists on an integration block.

IDEA: Run a zero initial condition check on a system before attempting to compile. If the condition exists, don't attempt to compile and report the problem to user.

-A simulation subVI fails to compile if a change is made after the subVI is created.

IDEA: If a change is detected in the subVI, force the subVI to recompile every time a file command is implemented.

LabVIEW Idea Exchange

Many-To-One Notification

Compiling errors in Control & Design Simulation SubVI