CITADEL DATABASE NOT CONFIGURED AS A RELATIONAL DATABASE

[Ignacio]

HI:
I have the same problem described by another member before, and I haven't found any  resolution of this problem:
The problem was:

>I enabled database logging, and configured the shared variables that I wanted to log. Then I deployed the variables. When I try to read alarms and events (Alarm & Event Query.vi), I get this message:

>Error -1967386611 occurred at HIST_RunAlarmQueryCORE.vi, Citadel:  (Hex 0x8ABC100D) The given Citadel database is not currently configured to log alarms to a relational database.

Please help me with this topic

Thanks in advance

[Ignacio]

BY THE WAY, I'M USING LABVIEW DSC 8.2.1 MAY 2007 EDITION

[akokot]

Hi Ignacio,

In order to log alarms it's necessary to enable logging option and set the Log Alarms and Events option for each Shared Variable. Then, you need to enable and configure the Alarming option. All these configuration options are found in Shared Variable properties page.

Let me know if you have further questions.

Alisson Kokot
Applications Engineering
NI BRAZIL

[Ignacio]

Hi Allison:
Thanks for your answer, but i think you didn't understand my question; i don't have problem in logging the alarms and events, is the Citadel database created with LabVIEW that gives me a headache because I create the corresponding database, I enable every "Shares variable" and "Library" options needed to log the alarms and events, but when I try to acquire the alarms (and events) logged into this database I get the error described before. I realize that every alarm is logged to the "default database", and this behaviour occurs when the database created is wrong.
In order to create the corresponding database I've used every procedure: Manually from Measurement & Automation Explorer (MAX) and programatically by using the "Create Database.vi" in LabVIEW but neither works... I think it is a bug of LabVIEW DSC 8.21, because there's no other way of creating a Citadel Database...

I'd appreciate very much any help...

Thanks in advance

[akokot]

Ok, I think I understood it now.

What did you mean for "this behaviour occurs when the database created is wrong"? You receive some errors when logging to the database?

Is it possible to read the alarms and events in MAX?

Alisson Kokot

[Ignacio]

I mean that is not a normal behaviour for LabVIEW and I suppose that if I'm creating the database by means of NI tools, there should be no problems like these (configuration of the corresponding database), and alarms should not be stored in another database...
When I try to log alarms to that database, i receive no error messages, but these alarms are logged in another database "Default Database", so I can't see then in the database I created, but I can see them in the "Default Database"

Thanks in advance

[akokot]

Hi Ignacio,

How are you configuring the variables to be logged in Citadel? I've attached a configuration where I log data to a database (Log Data Test) and I configured the Alarms and Events to be logged in another database (Log Alarms Test). All works fine in my configuration. I want to take a look at your configuration and maybe I can try it in my side.

Regards,
Alisson Kokot

[akokot]

Sorry, I forgot to attach the file.

[Ignacio]

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

[akokot]

Hi Ignacio,

Sorry for the delay, I was out of office.

I tested the VI you sent and it worked here. I was able to log alarms to the test__database_alarmas database. But I'm using LV 8.2. I'm looking for a computer with LV 8.2.1 to test your VI. I attached a picture of the VI with the indicator showing the registered alarms.

Did you tested this configuration in another computer?

I think this problem can be related with the installation of citadel or it can be a LV issue.

Regards
Alisson Kokot