Skip to content Skip to navigation

Connexions

You are here: Home » Content » LabVIEW Inter-VI Communication Within a Shared Memory Space

Navigation

Recently Viewed

This feature requires Javascript to be enabled.

LabVIEW Inter-VI Communication Within a Shared Memory Space

Module by: Felix Annan. E-mail the author

User rating (How does the rating system work?)
Ratings

Ratings allow you to judge the quality of modules. If other users have ranked the module then its average rating is displayed below. Ratings are calculated on a scale from one star (Poor) to five stars (Excellent).

How to rate a module

Hover over the star that corresponds to the rating you wish to assign. Click on the star to add your rating. Your rating should be based on the quality of the content. You must have an account and be logged in to rate content.

:
(0 ratings)

Summary: Introduces the concept of Inter VI communication in LabVIEW where all the virtual instruments are part of the same application

There is a big difference between how most procedural or event based interaction models and the dataflow model implemented in NI LabVIEW exchange data within the same memory space. This difference is mainly in the actual implementation of the data exchange methodologies. Though some concepts are represented in all, there are a few new additions in LabVIEW.

For example, in Microsoft Visual Basic or Borland Delphi a user might create multiple user interface forms, these forms are basically front panels through which the user interacts with the application. Each form would have a unique name such that variables in different forms could have the same name simply because they are active on different forms.

If a programmer desired to use a variable available from, say, FormA on FormB, and the variable was called ‘name’, the syntax to call the variable on FormB would look something like: FormA.name.

Since there is no text in the graphical programming method of NI LabVIEW (except the formula node and mathscript node), the previously described model does not directly apply. The graphical programming model used in LabVIEW calls for some new and innovative methods of exchanging data. Exchange between virtual instruments in LabVIEW that are part of the same application, meaning that they all share the same memory space, can be by any of the following methods:

Content actions

Give Feedback:

E-mail the module author | Rate module ( How does the rating system work?)

Rating system

Ratings

Ratings allow you to judge the quality of modules. If other users have ranked the module then its average rating is displayed below. Ratings are calculated on a scale from one star (Poor) to five stars (Excellent).

How to rate a module

Hover over the star that corresponds to the rating you wish to assign. Click on the star to add your rating. Your rating should be based on the quality of the content. You must have an account and be logged in to rate content.

(0 ratings)

Download:

Module PDF

Add module to:

My Favorites (?)

'My Favorites' is a special kind of lens which you can use to bookmark modules and collections directly in Connexions. 'My Favorites' can only be seen by you, and collections saved in 'My Favorites' can remember the last module you were on. You need a Connexions account to use 'My Favorites'.

| A lens (?)

Definition of a lens

Lenses

A lens is a custom view of Connexions content. You can think of it as a fancy kind of list that will let you see Connexions through the eyes of organizations and people you trust.

What is in a lens?

Lens makers point to Connexions materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

Who can create a lens?

Any individual Connexions member, a community, or a respected organization.

What are tags? tag icon

Tags are descriptors added by lens makers to help label content, attaching a vocabulary that is meaningful in the context of the lens.

| External bookmarks