Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI

Document Type: Tutorial
NI Supported: Yes
Publish Date: Sep 6, 2006

Historical Data, Alarm, and Event Files in Citadel 4

4 ratings | 2.50 out of 5
Print

Overview

Citadel 4 database is used for historical data storage by Lookout and the LabVIEW Datalogging and Supervisory Control Module.

Historical Data Files

Historical data is contained in the following collection of files.

File NameDescription
thd00001.thdStores the actual historical data. Contains the pages of data from the traces. Each page is 4096 bytes. There are 256 pages per file, with 256 additional bytes of header information.
tdb.tdbThis file defines the database. It includes trace names, database version info, similar information. If this file is lost or corrupted, you will need the backup file to recover.
tdb.bakThe backup for the tdb.tdb file. If both this file and the tbd.tbd file are lost or corrupted, data cannot be recovered.
tdx.tdxTemporary meta block and page index. This contains a quick-lookup index for the components of a trace. This file will be regenerated if lost. The disadvantage is that it takes a while to regenerate if your database is large.

Alarm and Event Files


Alarm and event data are contained in files with the Ale prefix. Files with the .adx extension can be regenerated if they are lost or damaged.

File NameDescription
Ale00000.aleStores the actual body of alarm and event data.
Aleack00000.adxQuick lookup index for currently acknowledged alarms that have not been reset.
Aleset00000.adxQuick lookup index for currently set alarms that have not been acknowledged.
AleIdx00000.adxLookup Index of all alarms in the ALE files.
areas.datStores alarm areas.
mdx.mdxTop-level meta-index. This is similar to tdx.tdx in that it can be regenerated if lost. This file increases the speed of opening the database.
4 ratings | 2.50 out of 5
Print

Reader Comments | Submit a comment »

 

Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).