Skip to Content

Register Login

Default Header

(header konnte nicht geladen werden)

Navigation

PLC disconnection time from WinCC 7.0

Created by: Donehill at: 6/5/2009 6:04 PM (7 Replies)

Rating (1)

Thanks 0

8 Entries

6/5/2009 6:04 PM	Rate (0)
Donehill Posts: 64 Rating: (0)	Hi again, My WinCC seems to have a problem when I disconnect my PLC from the comp. It takes WinCC about 60 secs to realise that theres no connection. What is the normal time for WinCC to detect connection loss from the PLC? How do I adjust the detection time for WinCC for quicker response? Thanks
Donehill Posts: 64 Rating: (0)
Suggestion To thank Quote Answer

6/5/2009 7:09 PM	Rate (1)
umencho Grandmaster Joined: 3/21/2006 Last visit: 1/10/2026 Posts: 10247 Rating: (1183)	Hello, Of course 60s is too much. It's deppends what kind of process you have, but I think around 5000ms is enough to detect communication timeout. I don't know how is organized your program but easiest way is to look at how is generate this message for communication timeout. Hope this will helps. best regards Hristo Mihalev

Suggestion To thank Quote Answer

6/6/2009 3:16 AM	Rate (0)
Donehill Posts: 64 Rating: (0)	Hi, Thanks for the help. Where do I look for the communication time out? Is there a way for me to reduce the communication timeout?
Donehill Posts: 64 Rating: (0)
Suggestion To thank Quote Answer

6/6/2009 6:06 AM	Rate (0)
umencho Grandmaster Joined: 3/21/2006 Last visit: 1/10/2026 Posts: 10247 Rating: (1183)	Hi, Yes you can reduce this time. In your WinCC project how did you detect that communication is missing with PLC? Did you received some message? If yes, open your editor and look for this "screen or picture". And forwarding which function (script) call it. Another posible way is WinCC just to read one tag from PLC, and inside in PLC to be organized this detection of com timeout. This is just one timer with one bit ("watchdog"), which if miss start to count (60s in your case) and then winCC read output of this timer. Regards

Suggestion To thank Quote Answer

6/6/2009 6:38 AM	Rate (0)
SPV Posts: 61 Rating: (4)	Hi Donehill Yes you can do this excercise of reducing the communication time out which is present in the Set PG/PC setting can i know on which are u networking the system
SPV Posts: 61 Rating: (4)
Suggestion To thank Quote Answer

6/6/2009 7:32 AM	Rate (0)
Donehill Posts: 64 Rating: (0)	Hi, I'm using TCP/IP communication. When I unplugged the LAN cable from the PLC, WinCC takes a long time to detect that there's no connection. Once I disconnected the LAN Cable, the value in WinCC will stop changing then after approx. 34 secs only it will show the analog values shaded. Should it be this way or the detection time can be faster?
Donehill Posts: 64 Rating: (0)
Suggestion To thank Quote Answer

6/6/2009 9:25 AM	Rate (0)
umencho Grandmaster Joined: 3/21/2006 Last visit: 1/10/2026 Posts: 10247 Rating: (1183)	Hi again, In your case misssing any detecion of communication timeout. I mean wihout any message, only visual detection. And I don't think that is possible to reduse this time. Regards

Suggestion To thank Quote Answer

6/6/2009 1:44 PM	Rate (0)
Donehill Posts: 64 Rating: (0)	hi, The alarm log also shows that theres no connection after about 36 secs. I used the WinCC 7.0 OS Project Editor to generate the default template so when theres no connection the alarm line will show a description.
Donehill Posts: 64 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on