Shared Variable Library - Separation

[Joachim082]

In the LabVIEW development environment it is possible to separate the shared variables via virtual folders. In cases with more than 100 variables it is very difficult to keep a structure at runtime. Therefore it would be a great improvement for us to implement a new hierarchical level (name of the virtual folder) to ensure a well-arranged structure also in the runtime. This structure should be kept in the Shared Variable Engine and also in the Citadel Database.

[AristosQueue (NI)]

Separate your shared variables into different .lvlib files. This not only provides namespacing but it helps with modularization -- when a component needs access to one variable, the rest do not come into memory. This will also help your projects load faster because when a VI loads, it will trigger the loading of a smaller library file. If you want nested namespaces, you can nest the .lvlib files.

[Joachim082]

We are using connection to a opc server and need the data logged to the citadel database. A separation into lvlib-files is absolutely undesired. For example when connecting to a S7-400 we have one opc-client in our lvlib with more than 200 variables (one citadel lifespan per process and one programtically deployment via Deploy Library.vi). In the project explorer we separate the variables with virtual folders. If this separation can be transfered into runtime (shared variable engine and citadel) this would be a great improvement for us.

[YanYuan]

Hi Joachim082,

Not sure if I understand your point correctly, but as Aristos mentioned, you can use nested .lvlibs to separate the variables in shared variable engine and citadel. It will look like this:

[Joachim082]

YanYuan,

ok - now I've unterstood the nesting functionality - great. thanks a lot.

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined.