S7 - Alarm_S Examples

RMA

Member
Join Date
Sep 2004
Location
North of Hamburg, Germany
Posts
2,052
o_O I think I'm getting to the stage where I should give up before I get a headache!

So now I need to ask if anybody out there has an example of using Alarm_S messages in practice. In particular how, exactly, they have to be called.

However, before we get that far, I need the answer to another question. In the specification for the 317-2 DP CPU, it specifies the maximum number of simultaneously active Alarm_S Blocks as being 60. What do they consider as being active in this sense - does it mean an active alarm condition, or does it mean the Block is active, in the sense that it is being run every cycle? If it's the latter case, I can abandon Alarm_S now, as far as I can see!

A second question, which is possibly related, regards the use of the SIG Parameter which tells the SFC that an alarm condition has occurred. According to the help files you should only call the SFC when the SIG input has changed it's state compared with the previous call of the SFC (I assume, in this instance). This seems to imply that I can't simply couple SIG to my fault detector output (because then it would be called every cycle even though SIG hasn't changed). Nor, if I understand it correctly, will simply putting in an edge detector suffice, because the second change of state of SIG, presumably signals the "Alarm gone" condition. So effectively, I need to put in a complete new layer of handling overhead between actually detecting a fault condition and reporting it with Alarm_S!

Maybe Jesper's right and I should stick to Alarm Bit signals! On the other hand, I would quite like to understand how Alarm_S works, because I assume the principles may well also apply to the other Alarm Blocks, like Alarm_8P for example. This may be about to become relavent, because there are whispers about that my next project may be a PCS7 one.
 
RMA said:
... there are whispers about that my next project may be a PCS7 one.
If that is going to be the case, then get on a PCS7 training course.
If you are going on a training course in PCS7, then it is a big advantage that you have prepared some questions beforehand. So your time spent on ALARM-S isnt wasted.

I cannot imagine anything else than that ALARM-S is supposed to be an all-encompassing system (for alarms and events I mean). So there should not be serious limitations. If there were, how is it supposed to work with very large systems ? And isnt that what ALARM-S and PCS7 is all bout ?

Disclaimer: My real experince with ALARM-S and PCS7 is nil.
 

Similar Topics

I'm a newbie who started a job as a repair tech recently. I've had plenty of luck with ABBs, Allen Bradleys, and a few others, but I can't seem to...
Replies
1
Views
67
Hello, I made a change in alarm setup in factory view studio, where I changed a alarm message text. After that I made a run application and...
Replies
0
Views
76
I am trying to enable an external alarm via computer speakers for Factory Talk Network Distributed Edition. I am using Alarm and Events setup. I...
Replies
7
Views
126
FactoryTalk View ME running on PanelView Plus 7, connected to Compact GuardLogix 5380 PLC Customer is asking for a physical push button to be...
Replies
6
Views
169
Hi all. I´ve got a little problem with my FT View SE alarm window. On my PLC program, I have 200 SINT for alarms, in which every bit is for one...
Replies
2
Views
134
Back
Top Bottom