Hello.

The bug that I described under (2) in my latest post is now fixed, in QuickOPC 5.84.294. This build is on nuget.org (NuGet packages) and on our Web site (installation program).

Best regards
 

Hi there,
Thanks for getting back and the speedy response. Just investigating the custom types and there could be an issue on my end which is resolving to the same type.

Cheers

Andrew
 

Hello.
Thank you for reporting this.

I have inspected the related code. The issue might be more complicated. Here is what I found:

1. By design, if there are two or more Select clauses referring to precisely the same field (same type and same member), they should be joined together in the result dictionary. This is an intentional decision and we want to keep it.

2. The code review shows, however, that there is a bug, and in the case described above, there will be an internal error - same as you have described.

3. However, just by inspecting the code, I could not find a problem for a situation in which there are two Select clauses with fields from different types but same member name. 

My question at this point is, don't you actually have the situation described under (1) in your Select clauses?

Either way, I want to proceed as follows:

- We will fix the obvious bug described under (2) and publish the new build,.
- You will retest. If the problem persists, we will proceed with investigation - in such case we may have to figure out a way how to reproduce the issue on our side.

Best regards

Hi there,
I'm using the EasyUAClient and I have configured two different types with the same field name and getting the following error below.
It looks like your just using the field name in the dictionary rather than type.fieldname. Our customers OPC UA Server uses the same fieldname in two different types.

We are using the latest OPCLabs.QuickOpc Version 5.84.192 which is the latest. NetFrame work 4.8

We should be in support if you need any purchase information.

Please advise?

Cheers

Andrew

OpcLabs.EventTracing.LogEntries Error: 1 : LogEntry("OPCLabs-UAClientEngine",Error,0,1). INTERNAL ERROR. The OPC-UA engine might be in an unstable state.    An exception of type "System.ArgumentException" from source "mscorlib" has occurred in OPC-UA SDK callback 'MonitoredItem.Notification'. The exception descend follows. (0) System.ArgumentException mscorlib (ThrowArgumentException) -> An item with the same key has already been added.    at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)    at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)    at OpcLabs.EasyOpc.UA.Toolkit.Client.UAClientMonitoredItem.MakeFieldResultDictionary(UAClientSession clientSession, UAEventFilter effectiveEventFilter, OperationResult[] selectClauseResultArray, EventFieldList sdkEventFieldList)    at OpcLabs.EasyOpc.UA.Toolkit.Client.UAClientMonitoredItem.SendEventNotification(Exception exception, EventFieldList sdkEventFieldList)    at OpcLabs.EasyOpc.UA.Toolkit.UAEngineBase.SdkCallbackEnvelope(Func`1 usingFunction, String name, Action callback)