strings[] property node fails at fieldpoint?

[vd]

Hi

does anyone know a workaround for the following problem:

My main VI has a enum control where the enum is defined by a external
..ctl file (strict typedef) . For that control i create a strings[]
property and pass the output string array to an indicator. That's it.

Running that VI in Labview (windows or remote) works fine. But if i
build, download to fieldpoint and watch it via remote panel, the string
array is empty. So what's the trick to make the property node output
the enum strings if running at fieldpoint?

(I'm using LV 7.1.1)

Thanks in advance,
Volker

[tst]

RT targets do not support working with properties. You can use the enum's type descriptor to extract the strings as shown in the attached VI. You can get it by using Flatten to String.

[Synap]

I just ran across this today too.  RT not supporting property nodes is a real bummer.

So, if I wanted to SET what the strings[] were, how could I do that?

[tst]

Since enum strings can't be edited for a VI which is reserved for running, you would need to load the VI dynamically anyway, in which case you can probably use the Set Control Value method, which requires the TD. You could reverse the code in that VI to build that part of the TD.

In general, though, you should not use VIs running on the RT target for the interface as it usually hurts the determinism. Instead, the common solution (which is definitely more complex) is to write a UI VI which runs on the PC and speaks with the RT VIs using TCP\IP or a direct connection (usually in a messaging protocol).

[vd]

sorry - TD means what?

By the way, i dont want to edit the enum at fieldpoint, just read it. I
suppose this is not possible until i uncheck "'Disconnect type
definitions and remove unused polymorphice VI instances" in build
options, but if I do, LV7.1.1 immediatly crashes when opening the
remote panel.

However, i created a helper vi that writes my strings[] property to a
file and read that file at fieldpoint, that works.

[tst]

---

@vd wrote:
sorry - TD means what?

---

Type Descriptor.

You seem to have already solved this, but for another solution you might want to have a look at the OpenG data tools, which also get enum data based on the TD.