Citadel logging

Hi ,
I am using Labview DSC 8.5 and logging data to Citadel database.
But when try to log the data programmatically on remote machine , only the database is getting created, but the data is not being logged.
But when this is done manually using project library , data is being logged to remote machine.
But programmatically ( by using property nodes ...etc) it is not logging data on remote machine.
I am attaching the vi . What may be the problem ???
regards
Santosh
Attachments:
Demoproj.vi ‏117 KB

Hi,
Thanks for the reply
1.) Normally with DSC, if you run the vi from your project file (.lvproj), it will automatically deploy your library. I do not see any vis to deploy your library in the vi you attached. (It is at the end part of the vi.)
2.)Also, is there a reason that you need to create everything with the property nodes?? Why not create/configure everything using the DSC Module Wizard (Tools > Dsc Module > "choose your option here")?? ( I want to use property nodes because the user should be able to give the path for data logging .DSC Module wizard cannot be used with the exe. )
3.)More information on your system setup would help out too. Are you running your vi on a computer, and it is logging all the data to a remote computer (server). Or are you developing the program on a computer, and then transfering the .exe to another computer to run it in the test environment. (Yes i am running the vi on local computer , and logging all the data to a remote computer ( with FDS and full DSC module installed).
4.)Make sure that the remote computer has the full LabVIEW run-time installed on it, as well as DSC (you must have a DSC run-time license if you do not have the full Development environment with the full DSC module installed on it).(FDS and full DSC module installed )
if u carefully see the previous vi logging.enabled property is set as true.
Now i tried giving localhost as path for data logging , but only the database folder is getting created.
Manually creating the project and creating shared variable,deploying it, is logging datato any system (local or remote)
Is there any problem with this vi.
i am attachment the latest vi.
regards
Santosh
Attachments:
Demoproj1.vi ‏66 KB

Similar Messages

How to control Citadel logging

I have Pot object that reflects actual tank level. Sometimes communication in the field is broken and I have last value of Pot object in the Citadel database during comm failure. This results with incorrect data when viewing data using Hypertrend object. Is there a way to mark the trend line with different color if communication tag goes to zero or is there a way to stop logging data if communication fail.
Albert

QGood() and QBad() uses the lookout quality features for object properties/data members. An example is the Red X that goes across objects that on no connected. Some drivers do not have quality features (we have a custom driver that doesn't use quality features). Modbus uses the quality features.
Good luck
Mike
Mike Crabtree - Lead Developer
Destek of Nevada, Inc. / Digital Telemetry Systems, Inc.
(866) 964-6948 / (760) 247-9512

Lookout 4.5.1 and Citadel Not Logging

I am running Lookout 4.5.1. It had stopped logging data and the trends are empty. I was getting Citadel Logging buffer is full for the individual objects. I had shutdown Lookout and logged into the PC as administrator to look at the MSConfig file to verified that Citadel is set to start up. Then I stared Lookout. The process started and is reading data fine. There are no more Citadel logging buffer full alarms, but there is still no logging going on. I even cleaned out the database file where the data is saved. The lighthouse in the task bar says that Citadel is running. I have tried stopping and restarting it with no success.

Could you give me your email address?
I'm trying to build a 5.1 version, it seems working. But maybe it's not easy to build a 4.5.1 version. There are some technical problems.
Ryan Shi
National Instruments

How to use "Days to keep historical data" & "Maximum time between logs(hh:mm:ss)

Iam using LabVIEW DSC. Values are being logged continously into citadel.
Is it possible to retain data of just one month and delete the earlier data as fresh data is being logged into citadel?
Is it possible to achieve this feature with "Days to keep historical data" & "Maximum time between logs(hh:mm:ss)" options in the history menu of Tag configuration editor ?

Yes, Days to keep historical data does what you are looking for. After the specified number of days, the old data gets overwritten with new data. So, you always have only the specified number of days' of data in Citadel.
Note: You may sometimes see that old data doesn't get overwritten till after a day or so of your setting (depending on how much data is being logged). This is because Citadel logs in "pages" and waits till the current page it's logging to is full before it starts overwriting the old ones.
You do not have to use the 'Max time between logs' option for this. This option forces Citadel to log data every so-many hh:mm:ss regardless of whether or not the data has changed. Note that this is NOT a way to "log data on
demand". Because, this periodic logging of data would change for a particular tag when its data changes. So, even with this setting all data may not get logged at one shot. Anyways, as I said, you do not have to use this setting for what you're trying to do.
Regards,
Khalid

Citadel 5 service Stopped

i am having big issue with Citadel 5 service on Windows Server 2008 STD 64 bit. It doesnt start automatically and if manually starts stops immediately. i have uninstalled DSC and reinstalled without sucess. i have also unistalled LV2012 SP1 and re-installed without solving the problem. Citadel logging is not working currently. hope somebody can help. here is a snapshot of the event viewer errors: "
"The description for Event ID 0 from source NI Citadel cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Citadel failed to create alarms and events database in this folder......"
Also have these warning on NIPALK which is one of the dependency of Citadel 5:
Log Name:      System
Source:        NIPALK
Date:          6/21/2013 5:58:54
Event ID:      8192
[NI-VISA] [PXI] Warning: 'PXIPreallocatedMemBlockSize' key not found
Thanks

Hello,
How are you logging the data to the Citadel Database? Do you receive any errors when logging data in LabVIEW?
I would recommend trying one of the examples that programmatically logs data to the Citadel Database. You can find the examples by going to Help >> Find Examples >> Browse Tab >> Expand Toolkits and Modules >> Datalogging and Supervisory Control >> Data and Alarm Historical Logging.
Have you ever been able to log proper data?
Regards,
M. Whitaker
ni.com/support

Using event risen to log data into citadel

Hi all,
I have an HMI application in LV & DS 8 reads My OPC items, and log data, alarms and events into citadel. Knowing Citadel is event-driven, I want to use this event to distinguish a change in database and update my Historical Alarm & Even List in the HMI front panel instead of ever polling the database.
I really appreciate any help.

Can you post more information on what you are doing? I haven't done much with Citadel but I thought that it is aimed at logging data as it changes, i.e. all of the data logged in there will be different else it wouldn't have been logged in the first place?!
There are block diagram functions that allow you to read the traces back and this is all you need. Check out the examples that come with the DSC module.
Let me know if I can help you further.

Can I log the Alarms & Events in Citadel?

Platform - LabVIEW DSC 6.1
OS - WinNT 4.0 SP 6.0
Hardware - NONE
By using "HIST Alarm & Event Query.vi" I can view the Alarms and events occured over a span of time. The data can be retrived even when the DSC Engine is shutdown but if I re-start my PC the Alarm & Event data is lost though the file "Ale00000.ale" which logs the Alarms & Events is there. Can you tell me what the problem is ? Is there a method of logging the Alarm & Event data automatically in the Citadel like the logging of the tag values ?

Somehow nobody replied to you. Maybe this is because we do not exactly understand what you describe.
Just in general : LabVIEW DSC 6.1/7 logs all the values/data and all the alarms and events through the Tag Engine (DSCEngine). Therefore, you need to do everything through tags. I can imagine that you configure a discrete tag with a certain alarm configuration. Once you set this tag to high it will generate an alarm. The unfortunate thing is that you can not specify a unique customized HIHI/HI/LO/LOLO message.
The behavior you descirbe with the "life-time" of alarms is wired. Either you ran an older version of Logos which might had - a long time ago - an issue with some 'zero-files' or you mix up the historical alarms with the current, live alarms. The LabVIEW
DSC Engine could keep some alarms and shows them up in the alarm summery as long a the engine is running (live-alarms) once you shut down the engine the alarm summery will not show those alarms anymore. However, when you query the historical alarms you should get those alarms back from the database (regardless if the engine is running or not)
In LabVIEW DSC 7.0 National Instruments distinguishs between historical alarms and life alarms much better by having a "DSC Engine-internal" alarm server implemented. The Citadel Service is monitoring this alarm server and once it gets a new alarm it will put it to a relational database (MS SQL Server/MSDE).
This new change sounds quite promising for the new feature set of LabVIEW DSC 7.
Hope this helps
Roland
PS: ftp://ftp.ni.com/support/lookout/logos - Where you can get the latest logos 4.4 version for LV DSC 6.1.

Data Logging a programmatically created shared variable of cluster or array datatype into citadel DB

Hi,
Is there a way to log a programmatically created shared variable of cluster or array datatype into citadel DB?
I have attempted to programmatically create a shared variable of type 'double' and was able to successfully log the same into Citadel DB. In the attachment, Please refer to the attached project SV_TC.lvproj and specifically to SV_W.vi for the code that i have used (W.png file shows the dB in MAX and shared variable in NI Distributed System Manager)
However when i tried the same approach to create a shared variable 'array of double', i noticed that traces are not getting created and hence data logging isn't happening into the Citadel DB. I was however able to write and read the shared variable array without issues. The same is true with cluster datatype also. Please refer to SN_NW.vi for the code that i have used - only difference from SV_W.vi is that i have tried to create a shared variable of type 'array of double'
One observation is that if i create an 'array of double' or cluster in a shared variable library using the project explorer and deploy, i could see that these being logged into Citadel DB.
Hence i want to understand what could be done to achieve the same programmatically? Could you please advice?
Regards,
Sridhar
Attachments:
SV_TC.zip ‏3925 KB

Why is the transaction happening over remote?
Because we need the information to be on our database immediately when they submit it.
I don't know anything about streams or replication.....
The web database is run by the company that hosts our web site. We use PL/SQL to show the pages and output the html. It fetches the data the customer is requesting from our database, but I'm struggling to get the best way to insert into our database from there.

Configuring Database for logging to citadel Database using shared variable engine

Hello All,
I have two systems with me here, one with LabVIEW 8.5 and one with LabVIEW 8.6, I'm using Shared Variables in my code and I am Logging to citadel Database. In a PC with LabVIEW 8.5, I am able to Log Data to citadel Database, but with the same code I am not able to Log Data from the PC with LabVIEW 8.6. Both the PC's have Database Installed and the connection with the Database Exists when I test connection with database through control panel. I would Like to know any configurations (in LabVIEW or in code or in Database or in PC) that have to be done for Logging to Database because the PC with LabVIEW 8.6 was added recently and the code was upgraded to 8.6.

It was due to a dll in LabVIEW, a dll named nitaglv.dll
Now I have a issue with Data Logging from the EXE, once the shared variables are deployed programatically from the EXE the Data Logging stops,
can I get any input on this issue..???

How do you change values after logging data to the citadel database (DSC)?

How would one go about changing values that already exist in the citadel database. So say I were logging a numeric value with a timestamp for 1 year and then wanted to change a few values for the month of June because my sensor wasn't working at that time. How could I do this? Is it possible without re-creating the whole database over?
Thanks
Matt

mattyk wrote:
Hey Ben,
Thanks for the quick response. I called NI and asked about this because this would be a big show stopper for me. Their applications engineer said that the best way to change previous data would be to read in the trace that you want to change, modify it and save it as a new trace. I am also looking into SQL querying. I was able to connect to the citadel database by setting up a ODBC data source and using the database connectivity toolkit to query the database. This worked. Now I am trying to come up with a statement in SQL to change previously saved data. I'll Keep you posted.
Thanks
Matt
That reinforces my suspicions.
I have an app running for about 8 years now that keeps a paper trail to enusr ethe cartdiges used in respirators (operated NIOSH National Institute of Occupational Safety and Health par teh CDC) that use DSC to enusre nobody can ever falsify those records. If they can be hacked I my customer and anyone using a respirator with a NIOSH sticker on the side of it, want to know.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

CITADEL and RELATIONAL DATABASE Alarms & Events Logging Time Resolution

Hello,
I would like to know how I can setup Logging Time Resolution when Logging Alarms & Events to CITADEL or RELATIONAL DATABASE.
I tried use Logging:Time Resolution Property of Class: Variable Properties without success.
In my application I need that timestamp of SetTime, AckTime and ClearTime will be logged using Second Time Resolution, in other words, with fractional seconds part zero.
I am using a Event Structure to get SetTime, AckTime and ClearTime events and I want to UPDATE Area and Ack Comment Fields thru Database Connectivity but when I use SetTime timestamp supplied by Event Structure in WHERE clause Its not possible get the right alarm record because there are a different time resolution between LV SetTime timestamp and timestamp value logged in database.
Eduardo Condemarin
Attachments:
Logging Time Resolution.jpg ‏271 KB

I'm configuring the variables to be logged in the same way that appears on the file you send, but it doesn't work... I don't know what else to do.
I'm sending you the configuration image file, the error message image and a simple vi that creates the database; after, values are logged; I generate several values for the variable, values that are above the HI limit of the acceptance value (previously configured) so alarms are generated. When I push the button STOP, the system stops logging values to the database and performs a query to the alarms database, and the corresponding error is generated... (file attached)
The result: With the aid of MAXThe data is logged correctly on the DATA database (I can view the trace), but the alarm generated is not logged on the alarms database created programatically...
The same vi is used but creating another database manually with the aid of MAX and configuring the library to log the alarms to that database.... same result
I try this sabe conditions on three different PCs with the same result, and I try to reinstall LabVIEW (development and DSC) completelly (uff!) and still doesn't work... ¿what else can I do?
I'd appreciate very much your help.
Ignacio
Attachments:
error.jpg ‏56 KB
test_db.vi ‏38 KB
config.jpg ‏150 KB

Logging large .ctl to citadel database is slow

Hi, All
I'm using LV 8.5 with DSC.
I'm logging my own.ctl types shared variables to citadel database. This own.ctl includes 52 piece doubles, strings and boolean datatypes. I have 200 piece this tape of shared variables and I record all that shared variable information to citadel database. All operations as writing, reading, achieving, and deleting database are very slow. They also consume lot CPU time. Is there any capacity limits on citadel database ? Which is best structure to record this kind of data to database? I have tested (see attacment) structure but it seems to be very slow because I have to delete and create database trace references after 1st database is full.
BR,
Attachments:
code_structure.jpg ‏51 KB

When you say "...to Log Data only when necessary... " I assume you are using Set Tag Attribute.vi to establish this behavior.
National Instruments recently added a feature (as a hot-fix) to the DSC Engine to be able to ignore timestamps coming from servers to prevent to log values with "back-in-time" timestamps. Citadel is really critical taking values back in time (logs a ) and therefore retrieval of Citadel data with such back-in-time traces could act wired.
You can find more info from:
Why Do I See a Lot of NaN (Not-a-Number) In My Citadel Database When I Use the Set Tag Attribute.vi?
blic.nsf/websearch/B871D05A1A4742FA86256C70006BBE00?OpenDocument>How Do I Avoid Out-of-Synch (a.k.a....
The Hot-Fix can be found:
LabVIEW Datalogging and Supervisory Control Module Version 6.1 for Windows 2000/95/98/ME/NT/XP -- Fi...
I assume you run into such a use case - maybe. It happen to me, too . And I've created a small VI which would analyze traces on back-in-time (NaN - Not a number) values. I assume the missing Data in DIAdem are those Not-a-Numbers aka Break.
If you still encounter some problems after applying the DSCEngine.ini UseServerTimestamps=false, you might contact a National Instruments Support Engineer.
Hope this helps
Roland
Attachments:
BackInTimeAnalyzer.llb ‏622 KB

Editing tag values logged in tag history / citadel database

Hi,
I having been logging data from input/output tags and memory tags to my citadel database over the past week and due to some errors in my vi (my fault) some values are showing on my trends that are incorrect. These values are affecting my calculations (e.g. zeros, infinite numbers etc) and I would really like to delete them if possible.
Does anyone know a way of going in to the database/tag history and selecting and deleting values whilst still leaving other data in tact?
Many thanks,
Stuart

You can remove the data from a Citadel database using LabVIEW, Lookout or Measurement and Automation Explorer (MAX). This is a two step process:
First you archive the data that you want to delete. When archiving, choose to delete this data from the original database. The archiving operation will move the data from your database to new database.
The second step is to delete the new archived database. This removes the extra database that was created by the archive operation. Once the data has been archived you can remove the archived data by either deleting the database manually or by using file VIs from LabVIEW.
The document elaborates this process for MAX, LabVIEW and Lookout separately
Measurement and Automation Explorer (MAX) You must have Historical Data Viewer installed. It comes with Lookout 5.0 and LabVIEW DSC 6.1.
To remove the historical data in MAX, follow these steps:
Under the Historical Data folder in MAX, select the database that you want to remove data from.
Right-click the database and select New View»Trace. This creates a trace view with the default name of New View under the database folder.
On the Trace Attributes page, click on Add new traces. Select the traces you want to archive.
Select a starting and stopping time.
Right-click New View and select Archive.
Enter a directory path to store the archived data.
Check the Delete data from source database checkbox to delete the data from the source database.
Click Start.
Once it is complete, click Close.

Unable to access citadel edit log.

I just installed LV-DSC 8 on my PC and I am trying to view some historical data through the Historical Data Viewer in MAX. The historical data is on a remote PC running LV-DSC 7. I can connect to the remote PC and see the database name, but when I click on it to view the tag names, I recieve the error message "Unable to access citadel edit log. Database files may be read-only or invalid". Does anyone know what causes this type of error? And what is the 'edit log'?
I verified that the files are not read-only. I can view an example database that ships with LV-DSC 7 on the same PC, so the problem seems to be specific to this database. Strangely I can read the database without any problem locally or read it from another machine with LV-DSC 7 so the database is not completely corrupted. Thus the problem exists only on this database and only when viewing it from a LV-DSC 8 machine.
In LV-DSC 7 is there a way to run a "repair" routine on the database? I wonder if detaching from the database and then reattaching might help.

I'm not sure what would cause that. On the LabVIEW 8 PC, verify that you have write permission for the files under C:\Program Files\National Instruments\Shared\Citadel\__LocalCache. If user-level security is enabled for your file system, you should also verify that the SYSTEM user has write access to those files.

In Lookout 6.0 or 6.5 how do you log to Citadel a gauge or expression?

Im fairly sure it is posible and have searched here and in Knowlwdge base without sucess

Create the Object (expression).
In Object Explorer, find the expression or the gauge, right click and select Data Member Configuration, there is a check for Log to database.
Ryan Shi
National Instruments

Citadel logging

Similar Messages

Maybe you are looking for