Company Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI

Wait on Notification from Multiple Function

NI LabVIEW 8.6 Help
June 2008

NI Part Number:
371361E-01

»View Product Info

Owning Palette: Notifier Operations Functions

Installed With: Base Package

Waits until at least one of the notifiers you specify receives a message.

When one of the notifiers receives a message, this function continues to execute. Use the Send Notification function to send the message. If a notifier reference becomes invalid, such as when another function closes it, this function stops waiting and returns error code 1122. If the notifier does not contain a message, this function waits until the notifier receives a message.

Details  Examples

notifiers is an array of notifier references. Use the Obtain Notifier function to obtain a notifier reference.
ignore previous indicates whether to ignore messages that LabVIEW sends to the notifier before it calls this function. If TRUE and the notifier contains a message before you call this function, this function waits until the notifier receives another message. If FALSE (default) and the notifier contains a message before you call this function, this function continues to execute.
timeout in ms indicates how many milliseconds the function waits for the notifier to receive a message. The default is –1, which indicates never to time out.If the function waits timeout in ms and the notifier does not receive a message, timed out? is TRUE.
error in describes error conditions that occur before this VI or function runs. The default is no error. If an error occurred before this VI or function runs, the VI or function passes the error in value to error out. This VI or function runs normally only if no error occurred before this VI or function runs. If an error occurs while this VI or function runs, it runs normally and sets its own error status in error out. Use the Simple Error Handler or General Error Handler VIs to display the description of the error code. Use exception control to treat what is normally an error as no error or to treat a warning as an error. Use error in and error out to check errors and to specify execution order by wiring error out from one node to error in of the next node.
status is TRUE (X) if an error occurred before this VI or function ran or FALSE (checkmark) to indicate a warning or that no error occurred before this VI or function ran. The default is FALSE.
code is the error or warning code. The default is 0. If status is TRUE, code is a nonzero error code. If status is FALSE, code is 0 or a warning code.
source specifies the origin of the error or warning and is, in most cases, the name of the VI or function that produced the error or warning. The default is an empty string.
notifiers out returns an array of the notifier references from which messages were received. The indexes of this array correspond to the indexes of the notifications output array. From the notifiers out array, you can determine which messages came from which notifiers—the first value comes from the first notifier, the second value from the second notifier, and so on. If an error occurs, this array contains references to the notifiers that caused an error.
notifications is an array of the last messages the notifiers receive. This data type changes to match the subtype of notifiers, unless the subtype is an array. If the subtype is an array, the data type becomes a cluster of arrays.
timed out? is TRUE if the notifier does not receive a message before the function times out or if an error occurs.
error out contains error information. If error in indicates that an error occurred before this VI or function ran, error out contains the same error information. Otherwise, it describes the error status that this VI or function produces. Right-click the error out front panel indicator and select Explain Error from the shortcut menu for more information about the error.
status is TRUE (X) if an error occurred or FALSE (checkmark) to indicate a warning or that no error occurred.
code is the error or warning code. If status is TRUE, code is a nonzero error code. If status is FALSE, code is 0 or a warning code.
source describes the origin of the error or warning and is, in most cases, the name of the VI or function that produced the error or warning.

Wait on Notification from Multiple Details

Use the Wait on Notification function for a single notifier reference.

Each unique instance of this function remembers the time stamp of the last message it receives. If this function receives only one message, the function stops remembering which message the time stamp refers to, and the only item filled in the notifiers array is the first element.

If you experience deadlock when you use this function repeatedly with different notifiers, use the Wait on Notification from Multiple with Notifier History function to store time stamps for each individual notifier. This function prevents deadlock.

If ignore previous is FALSE, each instance of the Wait on Notification from Multiple function determines if one or more notifier has a message newer than the time stamp most recently received by this function. If one or more of the notifiers has new messages, all messages are returned.

When ignore previous is TRUE, this function always waits for a new message, even if the message currently in the notifier is one it has never seen before.

This function does not remove the message from the notifier. Although a specific instance of the function returns a message only once, other instances of the function or to the Wait on Notification function repeat the message until you call the Send Notification function with a new message.

Examples

Refer to the following VIs for examples of using the Wait on Notification from Multiple function:

  • Wait on Multiple Notifiers VI: labview\examples\general\notifier.llb
  • Wait for All Notifications Demo VI: labview\examples\general\WaitForAll.llb

Resources


 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit