Navigation

Screen Update Speed

Created by: Bog at: 11/14/2005 12:18 AM (8 Replies)

Rating (0)

Thanks 0

9 Entries

11/14/2005 12:18 AM	Rate (0)
Bog Posts: 6 Rating: (0)	Does anyone with WinCC (V6.0 SP3 + Web Navigator V6.1) ever get screens with 500+ tags to update in <250ms? I am working with a company that has a scaled-down SCADA which easily does this, so when WinCC takes 2-3 seconds to update tags on the graphics they get irriated. The only workaround I've found is to put all of the screens together on a long PDL, and change the Picture X Offset when displaying the picture in a picture window. This simulates changing pages in <100ms, after 30s initial load, but I worry there will be ramifications for having every client always be on every screen so I haven't put that on the floor yet. How do I speed up WinCC?
Bog Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

11/14/2005 7:44 AM	Rate (0)
Nemo Posts: 3149 Rating: (172)	Hi Bog, well, I don´t think, that your idea to put all screens in a PDL is really usefull. => have a look at your C/VB-Scripts, I guess that you are using lots of them? http://support.automation.siemens.com/WW/view/en/10538600 http://support.automation.siemens.com/WW/view/en/12124767 http://support.automation.siemens.com/WW/view/en/10113139 http://support.automation.siemens.com/WW/view/de/22196555 Do you use GetTagxxxWait-/SetTagxxxWait-calls? http://support.automation.siemens.com/WW/view/en/18943009 You should first check your scripts with the WinCC-log files and APDiag. Good luck, Nemo
Nemo Posts: 3149 Rating: (172)
Suggestion To thank Quote Answer

11/14/2005 3:45 PM	Rate (0)
Bog Posts: 6 Rating: (0)	>>well, I don´t think, that your idea to put all screens in a PDL is really usefull. Why not? I've tried this and it works perfectly on a single terminal. I am worried about using it on multiple terminals, and have not yet tired that. >>=> have a look at your C/VB-Scripts, I guess that you are using lots of them? No, I just use dynamic dialogs and tags. I do have scripts for button presses and other user-triggered events. And for those I log start and stop times to verify scripts aren't continously running. Any suggestions other than scripting? Thanks, bog
Bog Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

11/14/2005 4:19 PM	Rate (0)
Nemo Posts: 3149 Rating: (172)	Hi Bog, it´s quite easy, the more variables per picture the more time is needed. If you have variables which are changing e.g. just every minute, you should use for them another cycle (and not 250 ms!) for actualisation in order to lower the system load. Regards, Nemo
Nemo Posts: 3149 Rating: (172)
Suggestion To thank Quote Answer

11/14/2005 4:26 PM	Rate (0)
Bog Posts: 6 Rating: (0)	All of my tags are in the 500ms cycle to save the overhead of having multiple cycles, and only a few could reasonably be changed to a 1s or slower cycle. Naturally removing detail from the screen is always an option. Our other SCADA package has no problems displaying more complicated screens quicker, however. How long does it take your screens to update? Thanks
Bog Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

11/14/2005 4:34 PM	Rate (0)
Nemo Posts: 3149 Rating: (172)	Hi Bog, you can find more informations in your wincc-online help > contents > performance data. And you should keep in mind, that you are connected via WebNavigator, so the bottleneck could be your network as well. Regards, Nemo
Nemo Posts: 3149 Rating: (172)	Last edited by: Nemo at: 11/14/2005 4:34 PM
Suggestion To thank Quote Answer

11/14/2005 4:42 PM	Rate (0)
Bog Posts: 6 Rating: (0)	Thanks
Bog Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

10/30/2007 8:12 AM

Rate (0)

PeejeeP

Posts: 2

Rating:

(0)

Hey All,

I have a similar problem like Bog.

we have a conveyor system and the status of each conveyor has a color. To change colors we use cscripts.

We we load a screen with webnavigator it takes around 5 to 15 seconds to get a first update of the screen. After that first update, webnavigator reacts normal. So just every time we load an other screen we have to wait those 5-15 sec.

we have a server core duo @1.8 with 2Gb ram.

this is tested over multiple clients on various configurations.

many thanks in advance,

Pieterjan

10/30/2007 9:36 AM	Rate (0)
PeejeeP Posts: 2 Rating: (0)	found a solution! Thanks to Nemo's link! http://support.automation.siemens.com/WW/view/en/10538600 just make an 'dummy' object in those screens that load slow and put some c-code in it (it doesn't have to be functional). the importent part is to add all the tags that you ar using in scripts to the tag trigger section. see explenation on nemo's link. Problem solved! Thanks PeejeeP
PeejeeP Posts: 2 Rating: (0)	Last edited by: PeejeeP at: 30.10.2007 09:37
Suggestion To thank Quote Answer

Share this page:

Share this page on...

Created by: Bog at: 11/14/2005 12:18 AM (8 Replies)

Rating (0) Thanks 0

9 Entries

Last edited by: Nemo at: 11/14/2005 4:34 PM

Last edited by: PeejeeP at: 30.10.2007 09:37

9 Entries

Follow us on

Rating (0)

Thanks 0