2/14/2006 8:14 AM | |
Posts: 3149 Rating: (171)
|
Hi Jaapie, what about using WinCC Lifebeat Monitoring: http://support.automation.siemens.com/WW/view/en/9918678 regards, nemo |
3/6/2006 2:53 PM | |
Joined: 1/17/2006 Last visit: 7/19/2024 Posts: 800 Rating: (63) |
Thnx for your answer, but this is the standard solution. I don't like the standard[:D]. Any other solutions? |
3/9/2006 1:05 PM | |
Joined: 1/17/2006 Last visit: 7/19/2024 Posts: 800 Rating: (63) |
clever solution [:o][:o] |
3/9/2006 5:28 PM | |
Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19) |
I've read the FAQ in Lifebeat Monitoring, and I'm confused.
It doesn't say where from, or how to, it just says "do it". I can't find it anywhere. |
3/9/2006 5:40 PM | |
Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19) |
OK, we're making progress. The 'OS projecteditor'? |
4/21/2006 1:35 PM | |
Joined: 1/17/2006 Last visit: 7/19/2024 Posts: 800 Rating: (63) |
Hi all, I have configured Lifebeat monitoring with the discription of: http://support.automation.siemens.com/WW/view/en/9918678 The AS-connection part is going fine, but we have still alot of problems with the OS-server and OS-client part of the lifebeat monitoring. OS-client (From one server we check a few clients): The'state of driver connection' to a client (on the server) is not ok. OS-server (From one server we check another server): The state of driver connectionis ok, but when we look in the @CONFIG-picture in runtime the connection is not ok. I wonder how it could work, because the tag (witch is made on the server by lifebeat monitoring in the OPC channel) is not created on theserver witch is monitored. The tag shows "No-connection to te PLC", because it is not present on that server. Am I forgetting something? If we test the client. The test is ok but we cannot browse on a client. Is this wrong? Hope you can help. Jaap |
Last edited by: Jaapie at: 4/21/2006 3:29 PMLast edited by: Jaapie at: 4/21/2006 1:37 PMLast edited by: Jaapie at: 4/21/2006 1:36 PM |
|
Follow us on