Multiple instances of a subVi to display data

[Dynamik]

Hi JoeSz,

      You're back!  and it sounds like we're on the right track...  Sorry if exampl/explanation was confusing.

Regarding the Array to Cluster, to establish the resulting cluster size, right-click on the icon and choose "Cluster Size"!  If you update the big-cluster's elements while they're in the array-form, it may be helpful to know in what order the sub-clusters will be mapped from the big-cluster into the array.  Have you used "Reorder Controls in Cluster"?  It's a cluster-option available by right-clicking on [big] cluster border.

      Thanks for sharing your background.   If you find the LabVIEW diagram to be very strange - as I did - hope you stay with it.  As a CS grad., IMHO that LabVIEW is "Way Cool" - and under-appreciated in academia.

cheers!

Message Edited by Dynamik on 10-05-2005 07:53 PM

[JoeSz]

That fixed the problem! Thanks.

I've finished the remainder of the display portion VI with no problems (the other stuff was easy).

Now I have to wait for the sensors and wire them into the NI DAQ system.

[Chris_Cilino]

To all,

I think that this topic is great and everyone has done some great work! 

I'm happy to be able to announce that one of the new features of LabVIEW 8 might directly address the issue. Wouldn't it be nice if you could create a custom control that had a program associated with it and reuse that control or indicator as many times as you'd like in as many programs as you'd like? Wouldn't it be nice....

May I  present Xcontrols

Here's an excerpt from the article

Xcontrols are represented on the block diagram by a single icon and hence dramatically reduce code size

• They are re-usable. They can be used created on one computer and used on another with full functionality.
• User functionality can also be easily added to an XControl. By simply adding an additional component to the XControl front panel and programming the new component in the XControl block diagram, the new functionality can be directly ported to all dependent VIs.
• They are packaged into one library and hence all related VIs are grouped together for ease of portability.
• They can be used in the project they are created in or added to the control palette and used by another VI that may not be part of any project.

Best regards and have fun!

Chris C

Applications Engineering

National Instruments

[Dynamik]

Hi Chris,

      Thanks for the info.  - this sounds like Active-X made easy.  ARE XControls dependent on Actve-X?  (Would XControl code port to a Linux/LabVIEW environment?.)   I perused the XControl-link (above),  but didn't notice Active-X explicitly mentioned...

Cheers

[Chris_Cilino]

Hey Dynamik,

Actually the XControls can incorporate ActiveX technologies, but they aren't dependant on ActiveX. You can make an XControl that has no ActiveX functionality in it.

I think one of the best ways to think of an XControl is as though you were making a custom indicator or control that already has a program behind it. For example, imagine if you created a waveform chart that already had all of the DAQ functionality you wanted associated with it. All you'd have to do is place this special waveform chart on your front panel and the DAQ programming gets pulled along with it in a nice neat package. You can create a palette of Xcontrols that you design so that programming time is reduced and the programs themselves become much more organized. Post if you should have more questions.

Best Regards,

Chris C

Applications Engineering

National Instruments