DDK Driver Crashing sometimes on DriverScanner FlushUpdates
EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted:
1 week ago
DDK Driver Crashing sometimes on DriverScanner FlushUpdates
Hi All,
We have somewhat recently upgraded to GeoSCADA 2022 - September 2023 Update. We have a DDK driver we have been using for many years, and has been crashing more frequently.
I've personally yet to reproduce this issue, but a customer of ours has had this driver crash 15 times in the past ~20 days.
For this customer, our driver is crashing when it calls "FlushUpdates" on the DriverScanner. This code is from the DDK, so I'm not sure what is going wrong.
Does anyone have thoughts as to why this is failing sometimes? Once a day or so for this customer. Personally I've been testing for about 2 weeks and haven't seen this crash once.
I'll attach an image of a stack trace from Windows Event Viewer.
Link copied. Please paste this link to share this article on your social media post.
Posted:
Monday
. Last Modified:
Monday
Has the DDK driver on site been compiled against the DDK for the version of Geo SCADA installed on site? A mismatch in version, even minor version, can cause some odd behaviours. Can also be fine, just don't know until something happens so usually best practice to keep them aligned.
Running it on your machine you may have compiled from source so it does match and so might be why you can't reproduce the issue?