Hello,
I have come across a situation in your EasyOpcUADemo application under QuickOPC 5.3\ExamplesNet that causes a complete freeze of the application. See the attached file for steps to reproduce.
[File Attachment: ApplicationHungUp.pdf]
An issue similar to the one discribed above also happens on our HMI. When OPC Logging is disabled it never recovers. When I enable the OPC logging I get the following crash:
With the following logs:
[File Attachment: HMI.txt]
[File Attachment: HMI-OPCTrace.txt]
What is happening is that we have a button writing a boolean value of true and then starts a timer, after 100ms it writes false. Just before we press this button we disconnect the network cable to "fake" a connection loss.
We obviously cant have the OPC logger running at all times as it does not use a ring buffer and would just overflow the system with huge logs. (Can I Feature request that?)
Best regards
Erik
I have come across a situation in your EasyOpcUADemo application under QuickOPC 5.3\ExamplesNet that causes a complete freeze of the application. See the attached file for steps to reproduce.
[File Attachment: ApplicationHungUp.pdf]
An issue similar to the one discribed above also happens on our HMI. When OPC Logging is disabled it never recovers. When I enable the OPC logging I get the following crash:
With the following logs:
[File Attachment: HMI.txt]
[File Attachment: HMI-OPCTrace.txt]
What is happening is that we have a button writing a boolean value of true and then starts a timer, after 100ms it writes false. Just before we press this button we disconnect the network cable to "fake" a connection loss.
We obviously cant have the OPC logger running at all times as it does not use a ring buffer and would just overflow the system with huge logs. (Can I Feature request that?)
Best regards
Erik