Multiple VI Controller Values

[COIEngineer]

I have an application in which I want two VI's to run simultaneously, but share information of the load frames. The first application has 3 almost identical tabs - one for each load frame. The second application will be used for validation reports, and I'd like to be able to do that without tabs and the significant extra programming that involves. There are some parameters, such as load cell scale, that need to be passed between the two applications. Using data binding on some controls, I can make a single control in App 2 share binding with the corresponding control in each tab in App 1. For instance, when "Axis 1" is selected, the control in App 2 shares data with the control in the first tab in App 1. Changing to "Axis 2" changes the binding to the control in Tab 2 in App 1.

This works well for standard data types. The clusters, however, fail to write data to the shared variable from either application. Is there a better way to do this?

I've included screenshots of both applications and the Distributed System Manager. I'm using Labview 2014.

Thank you!

[SeaSick]

Hey COIEngineer,

When you create a shared variable with a cluster data type you have to customize it. The Knowledge Base linked below walks through the correct steps to do this. Have you already formatted the clusters in this way?

http://digital.ni.com/public.nsf/allkb/DDEB4D9BC34705C086257242000FF7DB?OpenDocument

[COIEngineer]

The link isn't working for me, but I believe I have. 

The clusters are saved as a Type Def control, which I then used as the data type. In the variable editor, I can successfully select the type def.

[SeaSick]

Sorry! This link should work instead

http://digital.ni.com/public.nsf/allkb/DDEB4D9BC34705C086257242000FF7DB?OpenDocument

[COIEngineer]

@SeaSick wrote:

Sorry! This link should work instead

http://digital.ni.com/public.nsf/allkb/DDEB4D9BC34705C086257242000FF7DB?OpenDocument

---

Thank you for the new link.

Yes, I have effectively done this, as saving a type def is essentially the same as saving a custom control. The third attached picture shows a screenshot of the variable editor depicting that I have successfully attached a custom data type.