String refnum

[Nghtcrwlr]

Hello

I have  Main VI that contain a cluster of 13 elements (string)
I want to connect this cluster as an input to a subVI. See Attachment

But then there is this string --> String Refnum error. Can anyone please help

Thanks

[MarcoMauri]

In the subvi you have a cluster containing 13 references to strings,

and it's a different thing compared to the control you wire to it in the main vi.

I think you want instead to pass the reference to the whole cluster you have placed in the main vi.

[Eric.M]

Hello NightCrawler,

As Marco said, references and values are different, and you can not connect them to each other.

If you just want to read/write values of the elements of your cluster in a subVI, you may need to pass the reference of your cluster, and play with the property nodes related to it.

See the example attached ! 😉

Eric

[GerdW]

cross post in German LV forum...

[Nghtcrwlr]

Hello Eric

I cant open the attachment. I am having Lbaview 2011... Could you please repost it in 2011 format``??

Thanks

[Nghtcrwlr]

MarcoMauri...

But one question.... is it possible to make a cluster of references? I have strings in another part of the same VI. Nw when I have a lot of references together, Can i make a cluster of it to make the VI look small.???

[GerdW]

Hi mathew,

yes, it's possible to bundle a cluster of references. Infact it has been done in your subVI!

Use a Bundle(ByName) node to create your cluster...

[MarcoMauri · Accepted solution]

Hi!

If all you need is to update a lot of indicators you may consider using the reference to the cluster (and avoid using tons of references for single controls).

hope this helps,

Marco

[Nghtcrwlr]

Thank you guys!!

[rolfk]

And unless the cluster contains tons of long strings and arrays and you branch the wire to 500 different places in your program, it would be even better to simply pass the entire cluster through the subVI instead and wire its output value back to the terminal or a local.

Value Property updates happen synchronously in the UI thread and are VERY slow. They never can win in performance from a more dataflow oriented wire diagram even if such a diagram may cause some data copies somewhere because of branched wires, but with a proper dataflow wiring you shouldn't get that problem either.