11/11/2022 9:44 AM | |
Joined: 7/19/2022 Last visit: 10/28/2024 Posts: 410 Rating: (69) |
Hi drogers13, Check that you have Tag Logging configured correctly, that your PC has enough RAM and storage space and that your OS is compatible (excel attached). Also, as I understand it, WinCC 7.5.2 had a problem with long project opening times. This was fixed after Update 5.
AttachmentWinCC_V7.5_compatibility-list_en_2022-09-26.xlsx (640 Downloads) |
If this Information really helps, you could use the Rate function |
|
11/21/2022 9:33 AM | |
Joined: 2/17/2020 Last visit: 10/28/2024 Posts: 1101 Rating: (199) |
Hi drogers13, Have you already tried to delete the DCF file from the project? To regenerate it later, you simply open WinCC Explorer. If this does not work, could you confirm if the database configured for this project (TagLogging and AlarmLogging) does not exceed the following guidelines? - Maximum total size of the database: 6 months. - Total number of segments between Tag Logging (Fast + Slow) and Alarm Logging of 200 segments. You can check this by counting the files inside the 'ArchiveManager' folder. Each file would count as one segment. If you have already deleted them, I understand that not so many files will have been generated. - Maximum size of each segment of 2 GB. |
A rating will be well appreciated. |
|
11/21/2022 6:18 PM | |
Joined: 8/24/2022 Last visit: 5/20/2024 Posts: 5 Rating: (0) |
Hey Itafusna, Thank you for the suggestions. I made another post on Friday mostly updating this issue, here is an overview of that post. It usually took ~6 seconds for pages to come up. After troubleshooting, I narrowed it down to the Alarm Control window. The system is set up as a redundant system with 2 servers and 2 stations. Here is a list of things I've tried that have failed: 1. Tried turning off redundancy between the two servers. 2. Took the slave server offline and left the master server online, alarm control window loaded in ~3 seconds. When the master was turned off and the slave was left on it loaded in ~6 seconds. 3. Reset the alarm logging archives on both servers. 4. Deleted the contents of the AlarmLogging folder in ArchiveManager. 5. Changed the Archive settings for Alarm Logging. 6. Turned off online configuration retention and also tried it with retain permanantly on. 7. Restarted all servers and stations Going off from your post, I deleted the .dcf file following the directions on the Siemens "How do you delete the DCF file of your WinCC Project?". This unfortunately was not the solution. As far as the segment parameters, they seem to fall in line with what you suggested. I am still troubleshooting this, will post if I find anything new. Thanks, drogers13 |
Last edited by: drogers13 at: 11/21/2022 19:13:38 |
|
9/26/2024 3:13 AM | |
Joined: 7/22/2023 Last visit: 10/14/2024 Posts: 2 Rating: (0) |
Hi, I'm having the same issue today. May I know if you've resolved this and the steps you did? |
Follow us on