Writing into Citadel 5 database with indexes

[tdropulic]

Hello everyone,
I have a question concerning logging into Citadel 5 database (I am using LabVIEW 8.20 Professional development system with DSC).

We have a cRIO - Computer system that will be used as a monitoring system of a switchgear.
We make data acquisition on trigger - so it is not a continuous acquisition and logging. And the triggers are different, for different operation of the switchgear (e.g. open, close, motor operation...), and the data should be saved into database with three indexes - operation number, operation type and opeartion timestamp.

What is concerning me is whether I can do this with Tag Engine or with any other off-the-shelf solution in the LabVIEW and how (if possible)?

Also, can anyone say a proposition of manually creating a solution in LabVIEW - e.g. writing some database-communication module?

Thank you all for eventual replies as this is really a big issue for me and my colleagues in our development team!

[tdropulic]

Ok,
now I've seen that LabVIEW DSC 8.2 module which I'm using does not have Tag Engine or Tags, but Shared Variables.

And that Citadel database is a streaming database - without any option to write data to it by any other index but data sample timestamp for each shared variable. Or not?

If I try to use any other database for my application (SQL, Oracle...), could it all be solved with LabVIEW Database Connectivity Toolkit?

Thanks everyone!

Stay well,
Toni

[Doug M]

Toni,

Using the Database Connectivity Toolset you can talk to any database that provides an SQL OBDC driver.

Citadel is a numeric streaming database that is optimized to log tags (aka shared variables) and is very efficient in how it stores numerical data over long time periods.  It is part of the LabVIEW DSC Module.

With LabVIEW DSC you can also create Dataset Marking I/O servers which is basically creating conditions or triggers on which you want to log a specific set of shared variables (or tags) to Citadel.  Thus you could say "I want to start logging these five tags when the boolean tag goes true, and stop when this other line goes true".  Each dataset run is given a unique ID.  You can create different Dataset Marking I/O Servers for different sets of tags and conditions you want to log.

See the example Dataset Marking Demo.lvproj in the LV DSC shipping examples (Help » Find Examples).

Also see the sections:

Logging Data in Sets (DSC Module)
Creating Data Set Marking I/O Servers (DSC Module)

in the LabVIEW Help.

Hope this helps!

[tdropulic]

Doug,
thanks for the advice.

I will check this possibility of logging data with dataset marking.

Hope it will be OK!
If not, database connectivity toolset :-).