LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Assigning Chart's History Data

The only method available to assign all the data from one chart to another is to use the History Data property node.

Without using the property node, all you get is the last value of the chart.

Take for example this use case:

I have several functional globals holding unique chart data. Using one Front Panel chart on the main VI, i swap whichever operations data i'd like to see in and out of that chart. Currently, i have to fumble around with searching for the correct reference number of the Func Global chart and use a property node to do my data assignment. Totally inefficient!

Adding the ability to select assignment of the entire history to the "Data Operations" context menu, and making the chart polymorphic to recognize the input difference would be incredibly helpful.

Front panel data probes

I would love to have an option to remove scrollbars from block diagram. I have been using LabVIEW since 2001 and I am constantly having to modify code from engineers who are using LabVIEW for the first time. If there was a way to enforce the good practice of making the block diagram the size of a single screen, this would help me a ton. I realize that developers use computers with different screen resolutions so the option to display scrollbars still needs to be there but it would be great if it could be disabled.

The Lego NXT software release (not toolkit) is a wonderful interactive environment, that should be provided as an add-on application

on its own, call it "block application builder". I see many useful applications in a variety of different industries where businesses wish to extend to their customers interactive and intuitive interface that they can program in their desired configuration of the product's behavior according to their own use cases.

That means we need an environment where we can prepackage blocks that is functionally specific to their applications, with ability to sequence them, run them in parallel, add conditional runs, and iterative loops. The blocks themselves could be computational in nature, or additionally provide user interface popups for interrogating the user, and have access to the full range of Labview functionality. Each block properties settings can appear as front panel settings for user to customize the behavior of that block. This is exactly how the

Log mindstorm software was configured, except we ask that you extend the availability of that functionality for the general users to develop their own intuitive applications using the same environment framework design. This application can target building the customer created sequence of operations as a windows .exe or .dll. We also would like to customize the menus in the application. In other words, make the Lego mindstorm application a generic template for us to develop our own applications with similar intuitive framework.

LabVIEW uses 5 types of operation behavior for push buttons. However, I have come accross a rather annoying obstacle, whenever I need to execute an event for once (turning on a simple LED AND keeping lit AND keeping the button released, for instance), I need to run through Loops or structures which consumes the space of the block diagram. Although this may sound very simple, after all I am a newbie when it comes to LabVIEW, it really helps in certain places, namely in my very simple project. Here are two of the ways that demonstrate what I am doing at the moment:

And here is how the new pressonce/execute once and for all/release block diagram looks like (excuse my English, I believe the digrams must illustrate what I want to say)

As I have said, maybe it doesn't make a difference to you, but it does to others and I am one of them, well you can either go with a while loop or without, let's keep it to the big guys to decide (this is if my suggestion gets accepted). And I am choosing a random label 😄

Thank you for your time.

🙂

Message Edited by toniaz on 28-11-2009 12:46 AM