7/11/2013 11:52 AM | |
Joined: 3/14/2008 Last visit: 10/15/2024 Posts: 2111 Rating: (942) |
Hello 6.1sp4 In the auto generated @ charts, there is a message that is created when the OB1 exceeds the cycle time. This message is generated 160x per hour and I want to disable the message. The CFC chart is called @(2) and the block where the message is generated is OB_BEGIN (CPU function block). The EV_SIG3 is generating the message but I cannot disable it. I also tried in the OS project editor, but that message PLC process control message is not showing. I can delete the message in alarm logging on the servers, but when a compile is done, the message is back...i think.. How can I disable it? The servers are accessed by clients all over the plant. So setting a filter in the client message logging is a bit too much work... How can I do this? |
If I could help you, you can use the RATE button. Thank you. |
|
7/11/2013 8:45 PM | |
Joined: 5/18/2006 Last visit: 10/21/2020 Posts: 170 Rating: (64) |
Why would you ever want to delete/disable and/or hide this alarm/message? This alarm/message is letting you know that the controller CPU utilization/performance is being exceed at times (at least 160 times per hour).If this is indeed the case the contoller cyclic tasks (OB3x) will not be running within the set scan rates/cycles. As noted below please check the CPU Diagnostic Buffer to help identify what cyclic OBs are being compromised. If corrective action is not taken and more code is added to the controller the CPU is at risk of shutting down from being completely over utilized. The proper response should be the fix the controller configuration so the CPU is not being over utilized. This can be done by moving parts of the configuration to slower scan classes, changing the scan rates in the CPU properties, or removing un-needed code. The below excerpt is for the alarm in question from FAQ 37696303 (What are the causes of PCS 7 control technology and system messages and what measures are to be taken to clear them?). Although this FAQ is applicable to V7.1 this particular message is applicable to V6.1. cabreytj |
This contribution was helpful to1 thankful Users |
7/12/2013 8:35 AM | |
Joined: 3/14/2008 Last visit: 10/15/2024 Posts: 2111 Rating: (942) |
Well, I'm dealing with a plant programmed with pcs7 6 years ago. PCS7 is abused, molested like a fat girl on a shetland pony. It time to fix all the problems they having. Almost all hardware devices on that plc are put in OB1. during the big plant stop, the plc have to go to stop to solve all problems, but for now...operators are getting crazy with all those messages, and the real threats are overlooked. It is just a temporarily solution. Edit: the scan cycle time is set to 1000ms, default should be 6000 and the actual time is 1998ms. It can handle it....except it is made shitty |
Last edited by: Oreca at: 7/12/2013 8:37 AMIf I could help you, you can use the RATE button. Thank you. |
|
Follow us on