Future LabVIEW Features

[Dave Scheck]

Our team programs in C++. When we write a section of code, we always do some sort of logic test before we allow the motors to move. This usually consists of adding a bunch of prints that verify the logic works as expected.

What I would find really useful is a way to use compiled C++ code (maybe Java too?) to plug into a LV simulation. I don't have anything hashed out in detail, but the basic premise is that teams developing in C++/Java could continue to use what they're familiar with, but still use the visualization strength of LV.

What I'm thinking is a way to compile our code in such a way that we could drop it into a VI representing the robot behavior. I envision this block being used in a LV environment running on a PC. Inputs and sensors could be set manually or could be automated for more complex, reproducible behaviors. Output could be visualized however is appropriate.

VIs for different components such as speed controllers and motors developed by people that know how to accurately model the physical components could help out as well.

I know it's a pretty large concept/requiest, but it would definitely help teams out and would provide students a glimpse into real world simulation.

[Phalanx]

Something I've been asking for with Labview for a while..

The ability to "ZOOM" in on sections of VI's. Some VI's can have many wires, connecting many other sub-VI's. It be nice to ZOOM(enlarge) so we can clearly see the connections.

Another nice item, although I'm not certain how feasible it is, would be to have a DESKTOP CRIO simulator. Such that code could be developed, complied, run(pseudo) and debugged without needing a 2nd Crio or using the Robot.

[Greg McKaskle]

There was once an XY chart example. It is probably still there. It is really just a subVI that keeps a window of the data and updates the graph in the loop. On today's computers you can of course set the window quite large and run quite fast. The waveform charts are pretty optimized compared to a waveform graph, but there isn't much to do to outperform the XY graph that redraws everything. Anyway, looking at the example may help a bit.

Skipping to zoom. Yep, it would be nice sometimes, but it just goes to show that when things aren't designed in from the beginning, it is tough to retrofit.

Greg McKaskle

[kamocat]

I'd like to be able to shrink structures to fit.
I'd also like to be able to drag sections of code into and out of structures, and optionally have them retain their wiring.