Not every client will look for it but it is required if you are returning exchanging instances over the wire.

Specification is fairly clear:

https://reference.opcfoundatio.....erences%2E

We already tested with UAExpert and with that tool we are able to execute the method call. However according to Siemens the method call executed by Opcenter Execution MOM fails because our custom created 'DataType -> BaseDataType -> Structure -> FieldObject' does not return HasEncoding. This is also confirmed when browsing to FieldObject with UAExpert.

Because we now have internally a discussion in whether or not the problem is on the OPC-UA server side or in Siemens Opcenter Connect MOM I wanted to use the UACTT Lite test tool so that it maybe would confirm the feedback of Siemens that the OPC-UA Server is not compliant to the standard.

Is it possible to also answer my initial question if it is possible to test an OPC-UA method call with UACTT Lite?

Regards,

Erik

If that works it is client side issue.

The issue is you have likely created a DataType Node which is used as an argument in the Method.

This DataType Node needs to have an associated DataTypeEncoding Node. If your Server does not return a HasEncoding reference when the DataType is browsed then that would explain the issue.

To validate if our OPC-UA server is compliant with the OPC-UA standard I started testing with the 'UACTT Lite' test tool. However as soon as I try to execute a method call test script I get the error CallService does not exist. After some digging I discovered that I do not have the Call.js file which should be in the following location according to the documentation which is included with the 'UACTT Lite' test tool:

Location: /project>/library/Base/ServiceBased/MethodServiceSet/Call.js

So now I'm wondering is it even possible to test an OPC-UA method call with UACTT Lite or is this only supported in the full version?

Any help is appreciated.

Regards,

Erik

The download includes a powershell script that will clean up a 3.1.1 installation that was corrupted by the duplicate component ids.

Disclaimer: This is my product. You can contact me at sales09 (at) opclabs.com for questions.

Best regards

You can look at vendors that offer their own .NET libraries for COM access.

During development, we got a windows virtual machine that runs the OPC DA server. Using OPC Expert, we can already see the server and read variable changes. 

So far so good, but how can we implement a client that can read the data?

What we tried so far: 

a) python 32bit with pywin32 and OpenOPC

b) Native .net 8 

Both won't work because the automation layer (opcdaauto.dll from OPC Foundation) is not present.

What is the official way to develop a client, and from where do we get the opcdaauto.dll since it is not bundled in the redistributable package download?

Thanks in advance!

Are you available to verify before it is posted?

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: file_OpcEnum.E25DF0F2_0F29_47E8_8537_265285ED9757, ,

Error code 2753 is "The File '[2]' is not marked for installation."

There is a similar issue with UnregisterOpcEnum.E25DF0F2_0F29_47E8_8537_265285ED9757 action which doesn't handle uninstalling an optional feature that includes the merge module without uninstalling the whole application.

A possible fix is to change the register condition to: $comp_OpcEnum.E25DF0F2_0F29_47E8_8537_265285ED9757 = 3

and the unregister condition to: $comp_OpcEnum.E25DF0F2_0F29_47E8_8537_265285ED9757 = 2

which takes into account the action being performed to the OpcEnum component.

The same problem exists in the "opc-com-proxystub-mergemodule-3.1.1-x64.msm" merge module with the RegisterOpcCategoryManager.E68AB89F_6DF7_4750_8BC1_F14B2064F313 and UnregisterOpcCategoryManager.E68AB89F_6DF7_4750_8BC1_F14B2064F313 actions.

Fix for register condition: $comp_OpcCategoryManager.E68AB89F_6DF7_4750_8BC1_F14B2064F313 = 3

Fix for unregister condition: $comp_OpcCategoryManager.E68AB89F_6DF7_4750_8BC1_F14B2064F313 = 2

Second, use the KeepAliveInterval to keep your Publish requests fresh.

i.e. use 10 mins TimeoutHint but a 5 min PublishingInterval and KeepAliveCount = 1.

This ensures a PublishRequest is consumed long before it times out.

You would only get actually data in a response when the SamplingInterval expires (10,000 ms, 15,000 ms or 86, 400, 000 ms)

Given that PublishRequests are using for multiple subscriptions, say you have the following 3 subscriptions:

10,000 ms  Publishing Interval

15,000 ms Publishing Interval

86, 400, 000 ms (24 Hour) Publishing Interval

What would be the recommended Timeout Hint to use for Publishing Intervals given that if I use something greater than 24 Hours it will take 24+ hours for the requests to timeout for the faster publishing intervals?

This would cause excessive delays to users in knowing that the requests for faster publishing intervals have timed out.