View alarm status of shared variable

Hello:
I need to know the alarm status (I mean, if the shared variable is currently alarmed) of some shared variables hosted in a Compact Fieldpoint Controller.
I've seached for options on how to do this (like searching for a property through a property node of the SharedVariableIO class) but haven't found a succesful method to do it.
Anybody knows how to do that?
Thanks in advance!
Robst.
Robst - CLD
Using LabVIEW since version 7.0

Hola Robst, para ver las propiedades de una variable lo que necesitas hacer es habilitar el porperty node para que acepte como entradas las constantes de Variables Compartidas. Para que property node acepte esta referencia como entrada tienes que decirle que en clase es una variable compartida. Para seleccionar la clase da clic derecho sobre el nodo, y ahí aparece en el menu class. Después selecciona Shared Variable. Una vez que tengas la Shared Variable vas a tener todas las propiedades, sin embargo aquí no hay una propiedad que diga si está o no activa la alarma este nodo más bien te permite saber la configuración de la alarma y modificarla.
Aquí hay tres opciones sencillas para sacar esto. La primera es utiliza solo una variable y conectala al Read Alarms, o Alarm Status a partir de aquí puedes saber si existe o no alarmas.
Con el de Read Alarms si el arreglo regresa vacio es que no hay alarmas. Con el de alarm Status hay una elemento del Cluster que te indica que si hay alguna alarma.
Ahora otra opción es utilizar Read Alarms y de ahí extraer cuales son las alarmas.
Saludos
Message Edited by BeCeGa on 12-18-2008 05:43 PM
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD
Attachments:
Alarmas2.PNG ‏21 KB
Alarms Variables.vi ‏22 KB

Similar Messages

What's the meanning of "bad status" in DSC alarm config for Shared Variable?

as the title
LabVIEW 8.20程序设计从入门到精通已经出版，敬请关注！
欢迎访问LabVIEW学习乐园: http://labviewstudy.blog.edu.cn

Can I read the quality of an OPC tag which binded with a Shared Variable by using this "status"?
LabVIEW 8.20程序设计从入门到精通已经出版，敬请关注！
欢迎访问LabVIEW学习乐园: http://labviewstudy.blog.edu.cn

Change Alarm / Quality of Shared Variables for I/O Server

How does one set the Bad Status of a Shared Variable in 2009?
IE). I have a custom device that communicates via TCP/IP. I wrote my own I/O server that handles this communication and publishes a set of Shared Variables that my Main Application displays on a screen. These variables are all doubles and hold pressures and temperatures. If my I/O server in labview loses communication I would like to be able to set the status of the variables to bad so they will set off an alarm. In our main application we have colour indicators that are able to display this status. For example the background goes yellow for all indicators that are in "HI" alarm status, red in "HI HI" and orange when "Bad Status" (disconnected).
We were able to accomplish this using LabVIEW 7.1 DSC, by creating a VI to register all our "Tags" and a VI to run the server. The server vi's that came with 7.1 allowed us to set the quality when writing to the server item. Therefore when the device was disconnected or failed we could set the bad status and use the DSC system to log an alarm and use the alarm features to colour code our indicators.

None of the Shared Variable IO Properties can be configured to allow you to set the alarm. You can only configure the properties such as turning the possibility of the alarm status on/off and the priority, name etc. You do not have the ability to indicate that this shared variable is in alarm because your custom server has encountered a problem. I've talked to tech support about it and I've been informed that this was something that was removed when the shared variable engine was introduced. I've been told informed that the recommended alternative is to create an additional boolean shared variable that will contain the status of the items, or to write some sort of unique garbage value to the actual tag value to indicate there is a problem with it.
I now have to come up with a new way of providing this information. I just find it will likely be a poor programming choice because now my entire system will have to handle "tags" differently based on what hardware is being used. (IE) if its coming from a custom I/O device or from an OPC / Modbus etc capable device.

Blink while alarm on using shared variables with remote panel

I am creating an application where I have front panel indicators data bound to shared variables. I also set it up to have them blink when the alarm is on. I am using the DSC module.
This works great under the development environment. But when I connect using the remote panel, I can no longer see the blinking indicator if there is an alarm. I can see the blinking indicator on the machine that is running the program, but no on any of the remote panels (I have no problems connecting to the remote panel and controlling the program).
I have the remote panel set as embedded, since I want the user to be able to change some settings over the network.
I am sure I am missing something simple, any ideas??
thanks
Kenny

I have been using IE6 and Firefox, and I have found that the blinking does show up, if you refresh the page. And then if the alarm stops and the blinking stops, you will not notice it until you refresh again.
Kenny

How Can i retain the Shared Variable Values after PC rebooting

Hi all,
I am facing a paculiar problem with Shared Variables. I have an application in which shared variables are used for data communication.
One of the application requirement is to retain the variable values eventhough PC is rebooted or started after crashing.
As per the my understanding, the variable values will retain eventhough the PC is rebooted. But here i can observe a paculiar problem like some library variables are retaing the values while some others not. I enabled logging for all the variables.
I tried many ways. like logging enabled, logging disabled, changing variable names, changing process names etc... But i am not getting a consistent behaviour.
I hope some you can help me in solving this issue.. "How Can i retain the Shared Variable Values after PC rebooting"
Thanks and Regards,
Mir

Hi Blackperl,
Thanks for the post and I hope your well.
What do you mean by not getting consistent behaviour.. this will all depend on excatly when the crash happens i.e. before the write or after.
Surely a better method would be to log the data to a file during the reboot...
I beleived the value read back
will be the default value for the shared variable's data type.
The LabVIEW DSC 8.0 module adds more functionality to the shared variable, including initial values and alarms.
If you enable an initial value on a shared variable, when the variable
engine comes back on-line it will default to this value. Setting a bad
status alarm for the shared variable is also a good way of handling
this type of event. Additionally, if you are using a LabVIEW Real-Time
target such as Compact RIO or Compact FieldPoint, it is appropriate to
consider hosting the shared variable engine on the real-time target.
These devices have watch-dog capabilities and are typically the
hardware controlling the critical pieces of an application. Most
Windows or PC-based targets do not have these fail-safes.
I guess, if you could explain to me again that would be great. From my point of view, if I have a cRIO and a Windows PC. If the windows PC crashes, the cRIO will still update its shared variables. Then once the PC has started up its own shared variable engine, and the bindings are loaded, it will once again continue to update its copies of the variables.
Please let me know what you think,
Kind Regards,
James.
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Datasocket Server vs. Shared Variables

Does anyone have any thoughts on what is better - Datasocket Server vs. Shared variables? I have a table on my application that has text indicating application status, information, warning and debug messages and would like to view it remotley over a network. The old way was to use the datasocket server and bind it to the other control. Is the new shared variable engine more efficient? These machines are at different sites.
John

Hi John,
It definitely seems as if you want to gauge user experience on this issue, but since you've had no response I'll chime in and give the "National Instruments view" on the DataSocket/Shared Variable debate.
Shared Variables were created to expand the functionality of DataSocket and simplify the programming style required to pass information between networked computers. We have extensive literature on this topic and the most pertinent is linked here.
I hope some users will post to this forum to give you a less formed response than you get from me, but I am more than willing to answer more specifically if you have any more questions regarding this issue.
| Michael K | Project Manager | LabVIEW R&D | National Instruments |

Can i fire Shared Variables' "Bad Status" alarm artificially?

And what shall I do to experience 'Bad Status' alarm. SVE is running on Windows platform PC.
Solved!
Go to Solution.

One shared variable one heat level sensor(DS18B20).
I want use it's "Bad Status Alarm" to alarm person on duty -
the corresponding DS18B20 sensor was failure!
But what shall I do to experience 'Bad Status' alarm first?
Don't know why, don't know the solution. Is that right?
Why there is no example project about "Bad Status Alarm"?
http://forums.ni.com/t5/LabVIEW/what-s-the-meanning-of-bad-status-in-DSC-alarm-config-for-Shared/m-p...
NI call this "answer"?

I want to Host my Shared Variables on a cRIO, but use DSC for Logging/Alarming/SCADA

Hi everyone,
What I'm trying to do is this:
-Host shared variables on my RT targets (cRIO-9022) for reliability
-Use the DSC module to log to database, track Alarms, develop distributed HMI
The problem I'm running into is that the DSC engine (it seems) needs the shared variables it is monitoring to be hosted on that computer. The DSC engine can not run on a real-time target.
My end goal is to create a plant-wide network of cRIO's that are all linked back to a central server/PC that runs DSC to collect and stores data in a database. The plant HMI would also connect to the central server and get their information from there (not directly connected to the cRIO process). Is this possible/does any one have ideas on how to do this efficiently?
Thanks for the help.
--CLD--
LV 6.1, 8.6.1, 2011 SP1, 2012 SP1
Solved!
Go to Solution.

Sachsm,
Thanks for the input. I tried to create a test project for this type of architecture (bound NSV's) but am running into some errors.
I have attached a screenshot of the project and front panel showing the binding status of each variable **see attached picture**
Hosted on PC:
-Clone (Variable1) ---- This is bound to Variable1 on cRIo using the "Create Bound Variables" option in the Library
-Variable3
Hosted on cRIO
-Variable1
As you can see, when I drag variable 1 directly onto the PC front panel, the variable connects (indicator is green). Likewise, when I host Variable3 on the PC and drag it to the front panel, it connects. However, when I drag the Clone (variable bound to Variable1 on cRIO) onto the front panel, it cannot connect. Any thoughts?
--CLD--
LV 6.1, 8.6.1, 2011 SP1, 2012 SP1
Attachments:
Binding Error.jpg ‏127 KB

Build specification freezes when trying to view "Shared Variable Deployment" screen

Labview 2009 f3
For some strange reason, any applications that include shared variable libraries will no longer build into executables.
I was able to build these applications without issue a week ago. However, when I went to make an updated build today, the build failed and I had to force Labview to close. When I view the build specification properties, I can navigate through all the option screens except the "Shared Variable Deployment" screen. As soon as I click on that option, the interface freezes up and I have to force Labview to close.
This problem does not occur for applications that do not include shared variable libraries.
I tried removing the shared variable libraries from the applications that were failing, but that did not correct the issue.

I never did find a proper fix to this issue.
One day I attempted to build the application again, but this time I got distracted doing something else. When I finally checked the build status a few minutes later I expected it to still be frozen, but to my surprise I found that the application did successfully build. To this day, that particular application still looks like it is going to lock up, but about about 8 minutes later it finally takes off and builds like nothing was wrong...like every other shared variable application I have created. So I guess my only suggestion is to let the application sit for a while and see what happens.

Issue with use of shared variables in Crystal Reports 2008 Offline Viewer

Hi,
I have a report that contains a number of sub-reports which include drill-down functionality. The report returns data relating to an individual team with the user being able to view top level summary information in each area from the parent report and then drill into the sub-reports to view see more detail. The data returned by the sub-reports is filtered, using sub-report links, based on the team code parameter value given by the user. This parameter field resides in the main report.
One of the values returned by the main report is the team name. This is passed to each sub-report using a shared variable and each sub-report displays this team name as part of a heading.
This all works fine in Crystal Reports 2008, but when a report, containing data, is opened using Crystal 2008 Offline Viewer there is a problem with the shared variable. The value is displayed correctly when the user initially drills into the sub-report. However, when the user begins to drill into grouped data within the sub-report the value passed to the sub-report using the shared variable disappears.
How can I ensure that, when a report is viewed using Crystal Offline Viewer 2008, the value within the shared variable is not lost when users drill into grouped data within sub-reports
Thanks
Stuart

Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with you directly:
http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551

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

What happened to my shared variable DSC alarms?

I would like to programmatically alter the alarm levels of my shared variables using the recommended datasocket write method, but for some reason my alarm levels disappear. If I open Variable Monitor, sometimes the alarm data isn't there. I have them configured, and sometimes they are there. This also means that the Datasocket URL doesn't exist for the alarm levels. Why is that?
Attachments:
Shared Variable Monitor.JPG ‏94 KB
Shared Variable Properties.JPG ‏46 KB

Hi Brian,
I am not sure what resource pointed you to using Datasocket Write to change the alarm levels of a shared variable programmatically, but that is not the recommended method.
One resource that you I suggest you check out is the example called Library Generation.lvproj, it is in the example finder under Toolkits and Modules->Datalogging and Supervisory Control->Fundamentals. This shows how to add variables to a library and set the alarms.
For an existing library, please check out this Knowledgebase article, which describes getting a shared variable reference. One you have the reference, you can use the property "Alarming..." to set Hi, Lo, etc. Then, once you're done, redeploy the library programmatically (Deploy Library.VI).
Best regards,
-Sam F, DAQ Marketing Manager
Learn about measuring temperature
Learn how to take voltage measurements
Learn how to measure current

LabVIEW DSC: How to get alarm status from the area?

Colleagues,
I have, lets say, 50 Shared Variables where alarming enabled. Some of these variables assigned to area, so I can get status of the entire area or acknowledge an entire area of alarms (prior to version 8.x there was groups of the tags).
Now I would like to get alarm status from the entire area. How can I do it?
In version 6 I was able to wire tag group to Get Alarm Summary Status. Now, in version 8, Alarm Status.vi can be wired to the array of the variables, but not to area. Is it possible to get all variables from the area?
regards,
Andrey.

I am not sure if I should be posting my problem under this particular topic. I am having trouble understanding acknowledge alarm vi and what this vi is supposed to do is not clear to me yet.
I have around 300 shared variables in my project and I have created a particular vi just to view the alarms that may pop up during runs. I created a main menu and this alarm vi can be accessed upon a button click in the main menu. Users get alarm alert based on sound configuration. Then he can navigate to the alarm vi and acknowledge the alarm. The alarm vi only contains alarm and event display found under DSC module.
The problem is everytime I click the alarm button in the main menu, it takes around 2 minutes for the alarm vi to update which is very annoying and unsatisfactory in the middle of run. I am not sure why it happens and I haven't got any response from support yet. These shared variables are managed under 10 different library files that are set up based on different loops of the process (flow, pressure and so on).
Then I looked into three alarm examples that ship with DSC module. None of these examples use acknowledge alarm vi. I implemented another vi similar to alarm demo vi in that example - containing multicolumn listbox. I created acknowledge event containing acknowledge button and used the acknowledge alarm vi under this event. Read vi alarm is under timeout event.
When I click the acknowledge button as soon as I see the alarm in multicolumn listbox, nothing happens - the color of font does not get changed to purple neither any alarms get acknowledged. I tried to aknowledge alarm by variable name or alarms or alarm area, it does not give me anything. What is this acknowledge alarm supposed to do? I tried to find examples everywhere in the web that uses this particular vi and haven't found one yet.

EPICS alarm status is incorrect

I am using LV2010SP1 with the DSC module and EPICS Server/Client. I have used EPICS in DSC before, but only for passing values. Now I am interested in alarms and alarm status and I am getting strange results. I have attached a zip file with a project that illustrates the problem. The server publishes a single integer, and in DSC I enabled alarms with the default thresholds: below 10 is LOLO, 10-25 is LOW, 25-75 is NO_ALARM, 75-90 is HIGH and above 90 is HIHI. When I run the server and look at the values of the shared variable and the EPICS Server variable using Distributed Server Manager then everything looks good. On the client side, though, the alarm status readings are messed up. The status changes at the correct levels, but the status reads wrong. LOLO shows up as STATE, LOW shows up as COS, HIGH shows up as LOW and HIHI shows up as LOLO! STATE and COS are not even legitimate options for status. Here is a screen shot of the Distributed System Manager display. Has anyone else encountered this problem? I have tried Int16 and Int32 with the same results. I will try DBL next, but eventually I need this to work for integers.
Rich
Attachments:
EPICS Alarms.zip ‏19 KB

Rich:
So, it turns out that COS and STATE are valid values for the STAT field in EPICS, but they definitely don't make sense for the alarm states of the bound shared variables.
(Brief mention of some of the STAT field values can be found on aps.anl.gov here)
I've filed this under Corrective Action Request (CAR) #297362 with R&D. In the meantime, is it possible to use the server's STAT value (instead of the client's) as a workaround?
Caleb Harris
National Instruments | Mechanical Engineer | http://www.ni.com/support

Using Modbus TCP I/O Server with new DSC Shared Variables in LabVIEW 8.6

Hello,
I'm using LabVIEW 8.6 and want to communicate with a Beckhoff BK9000 Ethernet TCP/IP Bus Coupler via Modbus TCP. Instead of using the NI Modbus Library, I've tried the new LabVIEW 8.6 feature "DSC Shared Variables" as described at the bottom of this page: Latest NI LabVIEW DSC Module Features and Demos. Reading of analog input bus terminals works fine. However, I haven't figured out yet how to write on an anolog output bus terminal with these shared variables.
It's about a 16 bit analog output and I need to write to the registers 0x1121 and 0x0801. It works with the NI Modbus Library (just using function code 6 and choosing the registers), but on the other hand I don't know which shared variables I have to choose for these registers. I've tried several data items (e.g. 400001 upwards as well as 402049 for 0x0801) but none of them worked. I would be glad for a short explanation - thanks in advance for your support!
Regards
utechle

The Beckhoff documentation says, that holding registers start with 0x0800. I've checked this by using the NI Modbus Library. I used the "MB Ethernet Master Query.vi" togehter with the function code 6 for "Write Single Registers", changed the settings of the starting address to hexadecimal view and entered 801 (since it starts with a control byte in 0x0800 and the data out word follows in 0x0801). Furthermore, I had to address register 0x1121 in the same way for resetting the watchdog. As I've mentioned in my first post, this method works fine. However, I haven't found out yet which shared variables i have to use for accessing these registers.
On the other hand, it's no problem to read data from analog input bus terminals using shared variables. They start with 0x0000 (status byte) and 0x0001 (data in word) and I can read data with the shared variable and data item 300001, respectively.
Message Edited by utechle on 01-27-2009 11:12 PM

View alarm status of shared variable

Similar Messages

Maybe you are looking for