Hello, I have been experiencing persistent issues with Citect for the past month, and despite our efforts, we have not been able to identify the cause or find a solution. We recently purchased a copy of Citect 7.20 along with a complimentary license key (600 points). The problem we're facing is that the SCADA software Citect crashes and becomes unresponsive after approximately 15 hours of operation. This issue has been ongoing since the software was first installed and started running. The PLC we are using is a SIMATIC ET-200S (6ES7151-8AB00-0AB0), and the communication between the SCADA and the PLC is facilitated through the OPC server SimaticNET 2008 Edition. Originally, Citect was installed on a computer running Windows 7 Professional. However, due to the persistent problems, we switched to a new PC with Windows XP Professional in an attempt to rule out any system-related errors. Unfortunately, the issue persisted even after the change. We also attempted to resolve the problem by installing SP2, but it did not solve the issue. Our project utilizes a single trend server and an alarm server, and there are no custom scripts added aside from those used for calling popup trends or changing pages. The error report from the Windows Event Viewer indicates that the faulting application is Citect32.exe (version 7.20.0.598), with the faulting module being KERNELBASE.dll (version 6.1.7601.17514). The exception code is 0xe0434f4d. I have attached one of the exception reports generated by Citect for reference. Any insights or suggestions on why this issue may be occurring would be greatly appreciated, as the support from Schneider Electric Bulgaria has not been able to provide a solution. I have also reached out to Schneider Electric Global for assistance and I am awaiting a response. Thank you to anyone who can help us with this problem. Best regards, Nikola Hadjinikolov
After receiving no response from anyone, including Schneider and my colleagues, I decided to investigate the project myself. Despite not finding any issues initially, I created a new project that simply displayed PLC data, and it worked successfully. However, I discovered that the client process was rapidly consuming memory at a rate of 40-100 KB per second. Eventually, after approximately 15 hours, the entire 2 GB of RAM was filled, causing Citect to crash due to insufficient memory. I decided to rebuild the project from scratch, only exporting the variables and graphics. Surprisingly, everything ran smoothly without the need for any service packs or fixes. Although all settings were the same as the previous project, I made some minor cosmetic changes to enhance the alarm summary page. This issue was likely caused by a memory leak bug, though the specific reason remains unknown. I hope this information proves helpful to anyone facing a similar problem.
I have yet to implement programming for Citect due to budget constraints this year. However, since there are logging capabilities available, my suggestion would be to consider logging data at a rate of 1.0 or 0.1 per second to ensure smooth operations without the risk of integer overflow. For example, by logging at 1.0 or 0.1 per second, you would accumulate 570,000 tenths within a span of 900 minutes or 54,000 seconds. This approach will help optimize data tracking and prevent any potential issues caused by overflowing integers.
It appears to be a memory leak issue, a common problem in previous versions of Citect. I recommend reaching out to Citect support to report your findings, as they may have a hotfix available to resolve the memory problem.
We are experiencing a common issue with our Vijeo Citect 7.4 SP 2 SCADA Project, where it freezes after 3 to 4 hours, showing outdated values without updating them, impacting client data. Restarting the SCADA on the server temporarily resolves the problem. We would appreciate any suggestions for a permanent solution. Thank you in advance.
Hey Nikola, it seems like you've really been through the wringer with this issue. The problem you're facing could be due to a number of reasons, but the exception code 0xe0434f4d that you're encountering suggests a .NET Framework issue. It might be worthwhile to attempt a full removal and reinstallation of .NET Framework to check if this resolves the problem. If not, you might want to delve into the project settings within Citect as certain SCADA projects are known to face stability issues beyond a certain size or complexity. Just a thought, but you may also want to ensure that both your PLC and Citect versions are compatible with each other. Let me know how it goes!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - The issue of Citect crashing after 15 hours of operation could be due to various factors such as compatibility issues, system errors, or configuration settings. Further troubleshooting and analysis may be required to pinpoint the exact cause.
Answer: - The thread mentions the use of a SIMATIC ET-200S PLC (6ES7151-8AB00-0AB0) and communication facilitated through the OPC server SimaticNET 2008 Edition. This information can be crucial in understanding the system architecture and potential areas for investigation.
Answer: - The discussion mentions that Citect was initially installed on a computer running Windows 7 Professional, and later switched to a new PC with Windows XP Professional. Despite the change in operating systems, the issue persisted. This highlights the need to explore other possible causes beyond the OS environment.
Answer: - The Windows Event Viewer reports that the faulting application is Citect32.exe (version 7.20.0.598), with KERNELBASE.dll (version 6.1.7601.17514) as the faulting module. Understanding the error codes and messages can provide clues for troubleshooting and resolving the issue.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.