Unsubscribing works in an asynchronous manner. Regarding #2: It is likely that I know the cause. Rebuild your project with it, and re-test. 1 or later on the first page of the installation wizard.
#KEPSERVEREX TAGS FROM TXT INSTALL#
Before we proceed further, please download and install the current QuickOPC 2018.3 from the Download page of our Web site. You might be facing a different problem, but it could also be the problem we have fixed. Regarding #1: We have recently discovered and fixed a similar issue. Unsubscribing from items is not always reflected on the server.
LblStop.BackColor = Color.FromArgb ( 192, 0, 0 )ĭebug.Print ("Error with FrmMain ItemChange " & ex.ToString & vbCrLf & " Ctl problem? " & ctl.Name & " VAL? " & & "." )Ģ. LblTime.Text = sw.ElapsedMilliseconds.ToString Private Sub Da_Client_ItemChanged (sender As Object, e As EasyDAItemChangedEventArgs ) Handles Da_Client.ItemChangedĭim ctl As Control = Tr圜ast (e.Arguments.State, Control )ĭebug.Print ("ITEM CHANGED Da_Client ctl name: " & ctl.Name )ĭebug.Print ("ctl.tag :" & & " ctl.name: " & ctl.Name ) So, in essence, I suggest that the basic structure of the handler is like this: This is where some communication errors can be "lost". However, what's worse, in case that e.Vtq is Nothing, your code does not do anything (not even "Debug.Print").
So, in essence, these two tests can be replaced by one - usually by testing the e.Exception. Or, if e.Exception is Nothing, then there is no error, and in such case, e.Vtq is never Nothing. Either e.Exception is not Nothing - that indicates an error, and in such case, e.Vtq is Nothing.
But, when "e.Vtq Is Not Nothing", e.Exception is *always* nothing. In your code, if "e.Vtq Is Not Nothing", you further test whether "e.Exception Is Nothing" (and if it is not, you do "Debug.Print"). files/onlinedocs/QuickOpc/Latest/User%2.%20the%20actual%20result_.html Therefore, it is possible that what you describe as "not getting changes" are actually some errors, but they are "swallowed" - not indicated in any manner. I think that the error handling is not correct in your code.