LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Clusters break when changed. How do I plan for future growth of clusters?

Solved!
Go to solution

Clusters look like they can be used to "future proof" what gets passed to a sub vi.

 

But they break too often, and are not flexible enough. 

 

Is there a "software engineering" solution to making them more future proof?

How about using arrays inside of clusters?

Just skip clusters, and pass references?

 

What's the best solution?

Thanks

Chris

 

0 Kudos
Message 1 of 7
(2,957 Views)
Solution
Accepted by Chris_in_Colorado

Make your cluster a type def.  It is an option under customizing a control.

 

Lynn 

Message 2 of 7
(2,954 Views)

johnsold wrote:

Make your cluster a type def.  It is an option under customizing a control.

 

Lynn 


And here is a Nugget to go with that topic.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 3 of 7
(2,927 Views)

Thanks for the replies folks.

 

But do Type Def suffer the same problem that Globar variables do? They are hard wired to a file. Which means any subVi using can't be truly portable

with a group of programmers. (I use universal shift registers that are 100% portable, but they're weird).

 

Thanks

 

Message Edited by Chris in Colorado on 08-03-2009 02:13 PM
Message 4 of 7
(2,914 Views)

Chris in Colorado wrote:

Thanks for the replies folks.

 

But do Type Def suffer the same problem that Globar variables do? They are hard wired to a file. Which means any subVi using can't be truly portable

with a group of programmers. (I use universal shift registers that are 100% portable, but they're weird).

 

Thanks

 

Message Edited by Chris in Colorado on 08-03-2009 02:13 PM

Define "Truly portable" Type-defs are a blessing when working ina group development environment. I shiver at the thought of doing group development with them.

 

Q: What is a "universal shift register" ?

 

Ben

 

 

PS Please concider marking Lynn's reply as the solution since he replied first. The best I would get is an "assist" (still in hockey land) You can un-mark my post as the soltion using the "options" located in the top right corner of that post.

Message Edited by Ben on 08-03-2009 02:23 PM
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 5 of 7
(2,906 Views)

USR are the trick where you use a shift register on a wire inside a while loop that runs once, but do NOT define the starting value.

 

The subVI retains the value between calls = hence a true global. 

 

Great for Write-Once-Read-Many variables like Serial Number, IP address, etc.

 

 

0 Kudos
Message 6 of 7
(2,897 Views)

OK now I see.

 

USR = Un-initialed Shift Register also known as Action Engine.

 

I use Type-defs with them as well (see the nugget linked above)

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 7 of 7
(2,890 Views)