11/17/2010 12:46 PM | |
Joined: 3/21/2006 Last visit: 9/10/2024 Posts: 10228 Rating: (1181) |
Hello, Look at Monitoring whether OP on STEP 7 is on-line or off-line BR, Hristo Mihalev |
11/30/2010 9:47 AM | |
Joined: 10/7/2005 Last visit: 9/23/2024 Posts: 3022 Rating: (1054) |
Hello @Nick I have a question for you: Is your Panel connected to aDP Master or Profinet I/O controller port of the CPU (NOT MPI)? If so, may I suggest an alternative method for detecting a HMI Panel related comms failure which is the usage of the so called "DP Direct Keys". For this you add the HMI as a DP Slave (or Profinet I/O Device)in the HWconfig of Step 7. You now get the "direct keys" as Profibus (or Profinet) Inputs into the PLC. You now allocate one "direct key" and set it status to 1 upon HMI startup. If the comms fail, the input will automatically turn off (Standard DP slave ehaviour assuming "Watchdog" is ticked in the properties of the DP Slave) and you can use it to stop your conveyor. Alternatively you can use OB86 to detect the DP Slave failure. Either way, the "direct keys" DP Slave method will reactmuch faster than the other method and may be easier to implement(food for thought anyhow). Should this way interest you then you'll find more info on how to configure them in chapter 2.3 of the SIMATIC HMI WinCC flexible 2008 Communication Part 1manual. Last but not least a word of caution: Neither this nor the otherwayarea "safe stop" in the context of machine safety. For that you would need an E-Stop (I'm sure you are aware of this, but thought I mention it anyhow). I hope this helps and pelase let us know the outcome (and make sure to test too that it does what it should not only upon comms failure but also in case the HMIruntime shuts down or is powered off). |
Cheers |
|