Jump to content

Recommended Posts

Posted
Hi everybody. I'm developing an application on a Red Lion G315, and I have a question about alarms. I've figured out how to set them up, and can successfully activate them. But I can't seem to find any alarm history function that will keep track of what alarms happened when. Since setting up the alarms is fundamentally different on the Red Lion from other HMIs that I've worked with, I'm guessing there a likewise different way of doing the alarm history, but it's escaping me. Any help would be appreciated!
Posted
I see it now. "Event Viewer" is somewhat of a misnomer to me. It looks like it displays more information than alarm history, but still...
Posted (edited)
Yes, its just a lingo thing. I guess Red Lion views Alarms as a sub set of Events but the model works pretty well. The Event Viewer is like an extendable alarm history. You can have it show other events without triggering alarms, but as far as I know, all alarm activities are also events. The event viewer primitive is always used on my page called "Alarms and Events (History)" or just "Alarm History", and then I use a hand coded button to clear all events so I can secure it separately. I think the Alarm Viewer is best configured to show only active alarms, but I found those two primitives on separate pages filled my needs and I have not revisited how I have them configured since now I just drag/drop the pages into each new app. from a 2nd instance with that first one open. It is really nice if you use their security and put everyone in there individually with appropriates rights and put the real user name as an expression in the Event Label for any of your critical alarms. If you want to know "Who? put the dang thing in manual in the middle of the high speed cycle?!?", and what time, it's slick'r'frog snot when combined with the CF card backup (log al levents) and FTP...I have not dabbled with SQL access in Crimson, but I know very little about SQL at all yet. When folks start seeing their names pop up in an alarm history that they can't clear every time they make a critical adjustment or mode change, somehow the number of screw-ups magically drops. And if they do get their other buddy to log in and clear the history, before someone looks back through, well guess what, they can't erase what you can download from a browser in two seconds from the CF card... I think I have a good starter example applicable to the SLC which shows the use of both viewers in the downloads section...pre loaded with CPU Major error codes. Crimson alarms can be accepted and cleared rather than ack'd and reset. I actually find their terminology less ambiguous than acknowledge and reset. (is reset a verb or a noun?) You should also look at using the alarm ticker primitive. Just use it "stock" right off the resource pane, size and position to suit you and it works no configuration necessary, or you can customize what is dsiplayed (if anything) when no alarms exists (unaccepted or not cleared alarms will always show up in the ticker)... Don't overlook the built in alarm debounce time property...very handy for non critical stuff not intended to affect control, just for logging/alarming, I debounce several of my favorite scripts like IsDeviceOnline(SLC) wich I always have as a tag with an alarm set up. The G3 is ready to talk a bit too quick for the SLC (and this one gets power cycled frequently) so, I have had to delay this alarm as much as 3 seconds so far. I always try to put the alarm ticker and the clock and anything else global on one page, and use it as the Master Slide for all the rest of them that will show it. You can then add a hollow rectangle border to the ticker and have it take the operator to the history page by touch. (Add Action, Goto Page(page_name)). Hope this helps Paul Edited by OkiePC

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...