LVOOP objects via Network Shared Variables - State-of-the art

[bokorpet]

Hello,

I'd like to share LVOOP objects between a PC and the cRIO RT via network shared variables (SV).

As far as I know, LVOOP objects cannot be directly sent over SV.

Is there a recommended workaround?

Some of the options I'm aware of:

1) Serialize into string/variant; with following issues:

• RT FIFO option unavailable; what is the practical disadvantage here?
• Variant doesn't work? http://forums.ni.com/t5/LabVIEW/Passing-an-object-through-a-shared-variable/m-p/1212755/highlight/tr...

2) Serialize into fixed-size cluster

• Any known disadvantage?

3) Other ways??

Many thanks,

Peter

Some older sources:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Shared-Variables-should-support-LVOOP-as-a-data-type/i...

[royam]

Hello!

I recommend you use the flatten2string function and send the objects via network shared variables, or, preferably, network streams.

I think there are no generic disadvantages to name here, it all comes down to how you choose to design your application.

Like for the RT FIFO: No variable sized data types can be used here, but do you really need to send entire objects through? 

Hope this helps!

Kind regards,

Rome

NI Germany

[bokorpet]

Hi Rome,

thanks for your help!

What I still don't see is what a buffer adds to a network shared variable with RT FIFO? Isn't a FIFO already a buffer?

You may want to have a look at this thread: http://forums.ni.com/t5/LabVIEW/Shared-network-variables-RT-FIFO-versus-buffering/m-p/2648035/highli...

Regards,

Peter