LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Wow,

 

This would be super powerful.

 

It's a little hard to grasp at first.

 

If you have sheets or tabs like EXCEL, you could write clean code in small chunks without have all the overhead of many SUBVIs!!!!!

 

I would use "local variables" to get data back and forth from different tabs/sheets.

 

TAKE 1 MINUTE TO THINK ABOUT!!!!!!!!

 

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

It would be very useful to have a way of automatically create subvis when a single vi become too large. What we usually do is :

1. Select the portion we want ton encapsulate in a new vi.

2. ctrl-X.

3. Create new VI, save as, chose name, change icon.

4. ctrl-V.

5. Connect the front panel.

6. Add the new vi to the original diagram.

7. Connect the new vi.

8. Debug mistakes.

 

I think steps 2 to 8 could be automated with a single function (e.g. 'transmute selected code into a single vi'), saving a little time many times.

A conditional terminal for each frame of a sequence structure would allow one to exit the sequnce at any frame.  This could be useful in case something occured in one frame that meant the remaining frames should not be executed.  Easier than having to use case statements in the later frames.

 

I'd like to have a user dialog that shows a message to the user but doesn't wait for the OK button being pressed to continue. I want to use it as a simple informative pop-up window that the user can close whenever he or she read it, without my code having to wait for the OK button.

I now use a self made VI that I call using the VI Server method 'Run VI' with 'Wait until done' set to FALSE. Or did I miss something obvious?

 

Manu

Sorry if this is a duplicate.  I though I posted this a couple of days ago, but it hasn't appeared.

 

 

These are suggestions for this site:

 

Add a label: "Ideas Exchange Enhancements"

 

Put "Previous" and "Next" at the top of the page as well as the bottom.  Better yet allow us to go to the first, last, or particular pages like other forums (ex:   << 1 2 3... >>).  Put this interface at top and bottom.

 

In advanced search give the option to go to the PAGE the idea appears on rather than the idea itself.  Currently if I search for a particular date (the last time I looked at ideas) I get a list of ideas for that date.  If I click on an idea I go to the idea itself and any posted comments.  There doesn't seem to be a way to get to that day's page of ideas short of starting at the first and clicking on "Next" over and over.

 

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.

 

In my project, I wanted to set the cell color in excel as red during a failure condition. But to my surprise I found that the color was set to blue and NOT red.It took me a long time to understand that the hexadecimal values for the color constants are different in Labview and MS Excel.

I wonder why the color constants are not standardised, when Labview supports features like ActiveX controls. 

Add a modifier key when we close one probe (CTRL for example) will close every probe.