SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Delay when opening picture

5/6/2008 6:48 PM	Rate (0)
Nene Posts: 35 Rating: (0)	Hi, We've migrated a project from WinCC 6.0 to WinCC 6.2 . Since then I've noticed that some of the pictures took a long time to load (over 10 seconds). Comparing those pictures to identical ones (that are loaded immediately), I've noticed no difference. First I thought that it was a communication problem, but after checking that those Tags transfer was not driven by PLC, the pingto those PLCs was under 4 ms and that the cycle time wasunder 18 ms(the cycle time limit for communications was 20%) I've started to wonder... After disconnecting the Ethernet cable (from those PLCs)the two that opened immediately kept opening as soon as I called them, but the other ones kept the delay. If this delay situation was kept even when there was no data to read, and in the other two pictures (also without communication) opened immediately, the delay can not be caused by communication. Does anyone have some idea to help me solve this problem? Thanks in advance
Nene Posts: 35 Rating: (0)	Last edited by: Nene at: 5/6/2008 7:40 PM
Suggestion To thank Quote Answer

5/7/2008 10:57 AM	Rate (0)
April Posts: 1776 Rating: (95)	Hi, have you done some diagostics in WinCC?? For read diagnostic see FAQs http://support.automation.siemens.com/WW/view/en/22892165 http://support.automation.siemens.com/WW/view/en/22089969 http://support.automation.siemens.com/WW/view/en/22892720
April Posts: 1776 Rating: (95)
Suggestion To thank Quote Answer

5/7/2008 3:26 PM	Rate (0)
Nene Posts: 35 Rating: (0)	Hi April, Yes, I've checked the diagnose files. I've encountered some errors in scripts (that I've corrected), but none of those was related with this pictures. Since I believe it isn't a communications problem (as I told you before), and there's no entry in the diagnose files related to this pictures or created when the pictures are opened, I stand empty handed in what concerns a solution for this problem. Can you please help me in this matter?
Nene Posts: 35 Rating: (0)
Suggestion To thank Quote Answer

5/14/2008 8:36 AM	Rate (0)
April Posts: 1776 Rating: (95)	Hi, now it´s not so easy. Are these only migrated pdl´s? Try one thing take an slow pdl, copy all elements, paste these to an new pdl. Is the new pdl also slow?
April Posts: 1776 Rating: (95)
Suggestion To thank Quote Answer

5/14/2008 1:49 PM	Rate (0)
Nene Posts: 35 Rating: (0)	Hi April, No... All the .pdl were migrated from the 6.0 project. The only thing that those .pdl have in common is that they all gather data from PLCs connected to the same reuter. But as I said before, one other .pdl that is related to a PLC connected to the same reuter works fine, there are no errors in the diagnose files, the cycle time is within limits (and 20% to communications) and the ping time is also ok (average of 2/3 ms). Can this be a configuration problem in the connection to those PLCs in WinCC? I will try to copy the .pdl to a new .pdl and post the result here... Thanks,
Nene Posts: 35 Rating: (0)
Suggestion To thank Quote Answer

5/15/2008 4:46 PM	Rate (0)
Nene Posts: 35 Rating: (0)	Hi, I've tried to copy all elements of a slow .pdl to a new .pdl... But the new .pdl is also slow... Do you have any more ideias? Thanks,
Nene Posts: 35 Rating: (0)
Suggestion To thank Quote Answer

Share this page:

Share this page on...