Alarm & Event Query To Spreadsheet.vi

dear all,
 i m using  "Alarm & Event Query To Spreadsheet.vi" for alarm transfer using following inputs
1. Filter
2.Display Format
3. Output file path(C:\Program Files\National Instruments\LabVIEW 7.1\*.ALR)
and Database URL it will take by default i.e current tagfile.scf
on running this i get following error
"HIST_AlarmsToSpreadsheet.vi, Citadel:  (Hex 0x8ABC1008) Read alarm failed because of connection or query failure."
if i give the database URL manually in the following way
\\computer name\Labview
then i get the following error out
"HIST_AlarmsToSpreadsheet.vi, IAK_SHARED:  (Hex 0x8ABC700A) Not found."
so pls solve my problem as early as possible for u
 thanks and regards,
dhanwanti

Hi dhanwanti,
There could be a couple possibilities here -- one is that the database you are trying to reference has become disconnected -- Make sure you can see historical data in MAX.  If needed, reconnect your database or create a new one and change this in the .scf file in the Tag Configuration Editor.
Another possibility is that some of the parameters you have set in the filtering could be incorrect such as start and stop time.  I would suggest creating a simple test VI to make sure you can get the Alarm & Event Query To Spreadsheet.vi working, and then double check how it integrates into your project.   You may also want to take a look at the example that ships with the DSC Module for this VI, found in the Example Finder under Toolkits and Modules » Datalogging and Supervisory Control » Alarms and Events » Export Alarms to File.VI.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Similar Messages

  • Alarm & Event Query To Spreadsheet File VI doesn't work correctly (DSC 7.1)

    I am using the Alarm & Event Query To Spreadsheet File VI to write alarms/events to an Excel spreadsheet. However there are two things it does wrong:
    1. Global variables in the header are not correctly inserted. I am using the header "{creationDate}{delimiter}{creationTime}" but none of the variables are translated to their actual values. The same header in Write Traces To Spreadsheet VI works correctly, so I assume it is only the Alarm & Event Query To Spreadsheet File VI that isn't working.
    2. My display format is set to display the date of the alarms but it never appears. Set time/ACK time, etc all appear, just not the date.
    Can anyone explain what might be wrong?

    Hi AndrewWilliams,
    I have been looking into this problem for you and I can't quite figure out exactly what it is you are trying to do. Could you possibly send me your VI's (for the Alarm & Event Query To Spreadsheet File VI and for the Write Traces To Spreadsheet VI) so I can get a better idea of it.
    Have you looked at the Export Alarms to File VI in the LabVIEW examples that are installed with the DSC module. This is a very good VI and it might help you to see any faults in your code.
    Hope this helps, I look forward to speaking to you soon.
    Best regards,
    Peter H.
    Applications Engineer.
    National Instruments.

  • In the Alarm & Event Query VI how to show the alarm data

    In the Alarm & Event Query VI how to show the alarm data in the front pannel using the table or multicolumn listbox .thank you very much!!!

    Hi,
    Most likely there is something wrong with your specific database or your LabVIEW DSC installation. I just used the Alarm & Event Query.vi in my machine and it seems to work fine, I can see all the alarms as well as events containned in the database.
    You may considerer generate another database (change the logging directory) and see if the behavior goes away. Also, make sure you have alarms and events on that database.
    I could run the Alarm & Query.vi by just openning its front panel and placing the correct database in the appropriated control.

  • Alarm and Event Query Very Slow

    Group,
    I am using the DSC Alarm and Event Query vi to pull data from the SQL database (not the Citadel).  I have a filter set up that specifies the "Alarm Area" and the start and stop dates with maximun results set to 22.  These dates are set to only pull the last 24 hrs.  This vi will return around 10 to 20 entries out of perhaps 80-90 total events in the last 24 hours in the database.   This database is ~2M in size.   I have to set the timeout to almost 10 min for this vi to not produce a timeout error.  The results returned are correct but it just seems that the time to run this vi is excessive.  It is quering a database on the same system that the quering vi is running on.  Should I expect better preformance?
    Thanks
    Todd

    Verne,
    I have boiled down the code to this attachment.  This query took almost 7 min to return 22 results from a database size that is listed as 2.09877E+6.  I have also tried the Alarms and Event Query to spreadsheet vi also and it takes the same amount of time.  I am wondering if I place the Alarms and Events into the same (Citidel) database that the traces are going if it would be much faster.  I seem to get trace data back very fast.  If I recall correctly I seperated the alarms from the trace because I was having some sort of problem accessing the alarm data in the combined database...but that was several labVIEW versions ago.  Anyone else having this problem?
    Thanks
    Todd
    Attachments:
    Generate Alarm Log General Test.vi ‏19 KB

  • 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.

  • Alarm & Event Qery Error

    I have an application with LV & DSC 8. I've created a project with libraries and shared variables. A VI is designed to retrieve Alarms and Events from citadel database using "Alarm & Event Query.vi". When I run the VI, this function has an error with this error source: "HIST_RunAlarmQueryCORE.vi, IAK_SHARED:  (Hex 0x8ABC700F) Invalid argument(s)."
    and one more problem with my citadel database is, when I configure the database in ODBC(data source), and hint the OK button, the ODBC window goes to a non responding state and I should end the process, then my ODBC has a problem.
    I can't understand where these problems come from. I really appreciate any suggestion.

    Please see the below link for further discussion.
    http://forums.ni.com/ni/board/message?board.id=170&message.id=198179
    Rob
    Field Sales Engineer | National Instruments | UK & Ireland

  • Failed to query Alarms & Events, alarms not logging

    Hi all,
    I've recently run in to an issue with the DSC Alarm & Event logging. I have a number of shared variable libraries all setup to log both data and alarms to Citadel. I've double checked that the library itself is configured for logging data and alarms, as well as all the variables. Using the DSM, I can see all of the active alarms in the system across all libraries, and can receive all alarm change events programmatically.
    For some reason, alarms for only one of the libraries are logging, and attempting to query the historical Alarms & Events through MAX throws an error roughly 14 out of 15 times (with no error code or indication of why it fails). I've also attempted to archive the Citadel database, with it failing with an unspecified error (presumably when archiving the alarms side of things, the data archive seemed to work).
    Can anyone offer some insight on how to resolve the problem, preferably without data loss? Further, how can I prevent the issue in future?
    Solved!
    Go to Solution.

    Thanks for your reply Joey.
    Libraries are being deployed using the DSC Deploy Libraries VI. The libraries also have data and alarm logging enabled programmatically. At the moment they're both being logged to the same database.
    I can't find the "Read Historical Trend.vi" through the DSC Examples. The article was written in 2005 and I'm using DSC 2012 SP1, so I don't know if things have changed since then. I can view the data through MAX without issue if that's any consolation.
    The mdf file is about 60MB, with the entire Citadel database at around 6GB.
    The Citadel service is definitely running. I've also attempted restarting it (and the PC itself) but the issue is still present.
    It's entirely possible there was a power failure, as this has been during a period of plant commissioning. When I can query the alarms through MAX there's a lot of data up to a certain point (end July), then it's very sporadic after that with only certain variable's alarms being logged.
    I attempted another database archive and this time it managed to get all the way through, though the archived database also has the same problems querying alarms and events. So at this point I suspect the mdf/mds files are corrupt in some way.
    Using the DSM, I've tried manually pointing the libraries to log alarms to a newly created database but this doesn't seem to work. No alarms or events are logged to the new database, and checking the library properties shows that the alarm database which I configured the library to log to had reverted to the original database. Am I missing something obvious here? Do I need to pre-create some traces in the new database before alarms and events will get logged there?
    Given I have managed to make a 'good' archive of the database, I'd like to try just deleting the alarms and events portion of the database and start clean. Is there a correct way to do this? I did find this article, but am unsure if this will work with a potentially corrupted database: http://digital.ni.com/public.nsf/allkb/9D3A81218264C68686256DE1005D794F If I stop all of the Citadel and SQLServer related services, can I simply delete the mdf/mds files?

  • [Bug?] DSC - Clusters Different between 'Read Alarm.vi' and 'Alarm and Event Query.vi" but Contain 'Same' Data

    Howdy!
    Why are the clusters different coming out of the Read Alarm.vi and the Alarm and Event Query.vi when they have the exact same data?
    The only difference is the order of two last elements.
    I am leaning towards bug on this one, unless these clusters need to be distinct for some reason?
    Certified LabVIEW Architect * LabVIEW Champion

    Thanks for posting Ravens Fan
    I re-jiggered my API to reverse my datatypes then applied changes to my application code.
    It wasn't that painful to update. 
    My current understanding is that this bug affects one VI, so I decided it was easier to wrap that VI with the bugfix.
    Attached is my implementation if anyone wants it too.
    Cheers
    -JG
    [LV 2009]
    Certified LabVIEW Architect * LabVIEW Champion
    Attachments:
    Alarm & Event Query_bugfix.vi ‏30 KB
    Convert Alarm And Event Query Cluster.vi ‏21 KB

  • 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

  • Historical Data Viewer does not show Alarms/Events after date but trace working.

    Dear users
    The DSC Historical Data Viewer no longer shows any Alarms or Events after 31/10/06 using Citadel 5 Universe.  The trace still works to current  time and you can search for the alarms by tag names in the trace and it works fine.  Therefore the database data is there. Does the Alarms/Events View use a different file?  Any help would be much appreciated as I'm a novice working with a predecessors project.
    Please keep the answer simple.
    Thanks
    Dave

    Hi Integrators,
    Well I had drafted out a whole long post and it then died in me.  Sometimes I hate windows... anyway...
    http://digital.ni.com/public.nsf/websearch/A4F007F96AB1EB1E862569C30080C731?OpenDocument
    Might help.. maybe someone has turned off the Alarm viewing?
    http://digital.ni.com/public.nsf/websearch/E6611BC10294608886256A4800724210?OpenDocument
    It may be a corrupt database.
    The files you need to look at with all of the alarms in are files with the extensions "ale"
    http://ae.natinst.com/operations/ae/public.nsf/web/searchinternal/6fc62f75b74d706d8625694900768f69?O...
    This link will give you a bit more information as to which of the file extensions apply to which database files.
    Hope this all helps. (I am also handeling your e-mail query into NIUK so feel free to e-mail me back)
    I'll keep looking into the problem.
    Post back if you need more help.
    AdamB
    Applications Engineering Team Leader | National Instruments | UK & Ireland

  • DSC-Merging the Alarm Events Generated

    I am afraid whether I will be able to merge the alarm events generated in two different database configured in two PC’s (Servers).
    Both the data base monitors same traces and processes, one pc will be an active server and another will be an backup server. We have situation that one server may fail and come back alive.  In this situation how can I combine the alarm events generated in two different PC's?
    Merging the database doesn’t helps instead generates the error when queried for logged Alarms and Events. However merging the data base combines the traces data.
    We are using Labview 8.2.1 and DSC 8.2.
    Any help will be much appriciated.
    Thanks,
    Vijay Jayabalan.

    Thanks for your reply
    We are monitoring about 25000+ I/O points (cFP-180X), we are using Shared Variable in order to read data from cFP and update the data for Shared Variable deployed on Two Central Server Computer (One Duty and other standby named A and B servers respectively) each hosting a separate set of shared variable for the I/O points (only difference being the computer names)
    The Set of shared variable deployed on both servers, have the same configuration information such as alarms, logging etc as well as the same names.
    Given a situation that Server A fails (PC Crash/shutdown/restart), then the other server B will still provide the Alarms and Event information.
    However, when Server A return to normal operation then the Alarm and Event Set Time, Acknowledgement Time and Clear Time will be different than that in Server B.
    With an example let us say that,
    At 4.00 am in the morning Server A works fine and Server B is down, now the Shared Variable Deployed in the Server A will read data from the Field and Update any alarm information, if an alarm occurs (Shared Variable) at 4 am then this information of Set Time of Alarm (Read Alarm VI) is present in Server A and not in Shared Variable deployed Server B.
    Now, on the same day let us say Server B start working normally at 11.00 am, so the (Read Alarm VI) from the Shared Variable deployed in Server B will return the Set Time of the alarm as 11 am and not as 4 am (which is when the alarm actually occurred)
    What we would like to know is there any way we could merge the alarm information between both the computers for two sets of Shared Variables (similar to Redundancy in Lookout)?
    Kindly reply in case you need more details.

  • Does OPC UA Shared Variable Server support Alarm&Event and historical access?

    OPC UA Shared Variable Server is a sample code and resides at https://decibel.ni.com/content/docs/DOC-25602
    It seems to support DSC <-> OPC-UA tag synchronization.
    But does it support alarm&event and historical access?
    I tried to open it with LabVIEW 2012, but lots of VIs were missing in the code, and I am not familiar with DSC and OPC-UA.

    Hi iCat,
    From your post on the example itself, a colleague of mine responded with: "This uses the OPC UA server included in DSC 2011 SP1 which does not include direct support for Alarms and Events. However you could use this idea to synchronize to shared variables on a Windows host which could have those abilities enabled."
    So it looks like it doesn't directly do this.
    Matt S.
    Industrial Communications Product Support Engineer
    National Instruments

  • Cluster Events Query Incomplete

    I have a six-node 2012 R2 Failover Cluster running Hyper-V.  When I go to Cluster Events, it says on the title: "Cluster Events (0 events, query incomplete)". When I query one node at a time, only node 2 returns results, and every other
    node says "query incomplete". I can read all the event logs separately through remote MMC.  What does this mean, "Cluster Events (query incomplete)", and how do I get all the nodes to report in? 

    Hi rpseekell,
    Please refer the following article to confirm whether this node FailoverClustering ETW session is running. Please install the Recommended hotfixes and updates for Windows
    Server 2012 R2-based failover clusters updates.
    The related article:
    View Events and Logs for a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc772342.aspx
    Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
    http://support.microsoft.com/kb/2920151
    How to create the cluster.log in Windows Server 2008 Failover Clustering
    http://blogs.msdn.com/b/clustering/archive/2008/09/24/8962934.aspx
    Windows Server 2008 and R2 Cluster Log Appears to Be Missing Gaps of Data
    http://blogs.technet.com/b/thbrown/archive/2010/07/31/windows-server-2008-and-r2-cluster-log-and-missing-gaps-of-data.aspx
    The similar thread:
    Cluster events not written to system event log
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/b713b63c-4674-4491-847c-75c6f8b9ea55/cluster-events-not-written-to-system-event-log
    How to find event log and system information of Nodes in Cluster
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/59365d4f-1a10-4c6d-bead-496bf67628e2/how-to-find-event-log-and-system-information-of-nodes-in-cluster?forum=sqlgetstarted
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Reading Alarms/Events Failed. No Alarm History.

    Lookout 6.1 build 3. No alarm history within Lookout.  When saving alarm data to CSV file, file creates but is empty. Trends and other logged data seem OK.
    Measurement & Automation Explorer. No problem connecting to database. New A&E View, Refresh, returns the message "Reading Alarms/Events Failed". 

    Control Panel->Administrative Tools->Services, restart the service SQL Server(Citadel)
    Ryan Shi
    National Instruments

  • DSC Module: Alarms & Events: How can I programmatically set the 'set user'?

    How can I set the Alarm&Event 'set user'?  Right now, it is always '(Nobody)'

    Thanks for the info.  I had not discovered the Security dialog under the Options.  However, now that I have delivered the first version of the software and have more time to play around, I have discovered the Account Domain Manager under Tools->Security, and that seems to be what I need.  In the image below, I used the Example entitled 'DSC Dynamic Alarm Update'  (available in Example Finder).  But first, I created a local domain called 'Skelly', and logged in as a user named 'zimmer'.  When the alarm came in, you can see that the set user is no longer 'Nobody'.  So now, all I need to do is modify my startup VI, to have each operator log in (using the DSC Security VIs).  That way I will have a record of which operator adjusted the valves & pumps.  ( I write all commands going to control devices to a text shared variable which I log. I also have checked the option to Generate an event upon value change.)

Maybe you are looking for