8/7/2012 10:16 PM | |
Joined: 9/27/2006 Last visit: 9/18/2024 Posts: 12282 Rating: (2684) |
Hello bray; WinCC alarms are based on tags setup in the Tag management editor. The easiest way to have access to all the Step 7 data in your WinCC project is to integrate WinCC in the Simatic Manager. The following recent discussion on the forum gives a lot of links and hints on how this is done: Integrate WinCC in Simatic Hope this helps, Daniel Chartier |
8/14/2012 11:05 PM | |
Joined: 9/27/2006 Last visit: 9/18/2024 Posts: 12282 Rating: (2684) |
Hello bray; Normally, WinCC Alarm Logging will let you create alarm messages associated with process tags. You can see an example ofalarm message generationhere (chapter 9): SIMATIC V7.0 SP1 Getting started However, I don't see why you cannot use DBx.DBWxy tags (not internal tags, they must be read from the PLC) and set them up as bit_messages in Alarm logging. But that will mean more work for yourself and the PLC programmer. First the PLC must introduce some alarm management: every alarm condition must set an alarm bit in the DB words selected. Then you have to think about what happens when the alarm condition comes back down: and what about operator acknowledgement, and how iwll that be handled (based on the mechanisms of WinCC: you will need to create a secondary DB bit for every alrm bit as an Acknowledgemnt tag that will force the alarm bit to be reset in the PLC). Then in the SCADA you will need to create the messages for each bit_message in Alar Logging (using the bit_no column you will tell WinCC which bit in your alarm DB word will trigger this message). You will also need to create the Acknowledge_bits and match them with the PLC Acknowledge bit area. So I guess it can be done the way your boss suggests, but make sure to tell him about the expected extra work for both the PLC and SCADA programs that will be required before you accept the task Hope this helps, Daniel Chartier. |
Last edited by: dchartier at: 8/14/2012 11:07 PM |
|
Follow us on