Powerbuilder writing using the same OpcLabs.BaseLib.Collections.ElasticVector - by: spaxman

February 28, 2019, 2:29 pm

≫ Next: Method Call in Python - by: Enrico

I am trying to use the same vector over and over and load different DAItemValueArguments into the vector to call the WriteItemValueList I am doing this because each time I hit the database I can have different data to send back to the plc. I can also have different amounts of DAItemValueArguments to send back.

Everything works great the first write. I then tried to call the clear() method on the vector to empty it out and load for the next time. This does not seem to work.
What should I do to send data back. I was trying for speed purposes not recreate everything every time.

FYI I am Still on the demo code. Is this why I can only do One write?

↧

Method Call in Python - by: Enrico

March 1, 2019, 6:16 am

≫ Next: Random Disconnect from OPC server - by: Olya

≪ Previous: Powerbuilder writing using the same OpcLabs.BaseLib.Collections.ElasticVector - by: spaxman

I'm trying to find an example how to use Python to call OPCUA Methods.
My first question: when using the com interface is it at all possible to call methods?
If yes would you have a link to an example?
If not any chance to use .net with Python?

↧

Random Disconnect from OPC server - by: Olya

March 2, 2019, 2:48 pm

≫ Next: Wrong values returned from ReadMultiple - by: veda

≪ Previous: Method Call in Python - by: Enrico

Hello,
Recently we also encountered a very similar problem. Our company is using OpcLabs.EasyOpcClassic EasyDAClient (version 5.54.453.1) inside WCF service application written in c#.
It is also using ReadMultipleItems method inside some timer from multiple threads and in some cases, after receiving errors it is not able to reconnect again and data flow stops.
The first time we spotted this issue on one of our production servers and we are not sure what was the status of the OPC server when this happened. After this, we tried to reproduce it in our test environment. In our case, it usually happens after we lose the connection between client and server for more than ~5 min and it is much easier to reproduce when the OPC is on the remote machine (we tried to physically disconnect the machine from the network). But in some cases much more rear it happens when the client and the server are both on the same machine (we tried to stop OPC server abruptly).
The symptoms are next:

- after disconnecting from the network we are receiving some errors (usually "The RPC server is unavailable. ") which looks OK;

- then we connect to the network again (after 5-10min) and receive an error again (but in this case timeout for the first call seems to be a little longer);

- then we receive a few more errors.(usually: Read not completed. This error indicates that it could not be verified that the requested read operation was completed during the timeout period. It is possible that the read operation will actually succeed or fail, but later. Increase the timeout period if you want to obtain positive or negative indication of the operation outcome. Other reason for this error may be that under heavy loads, topic request or response queue is overflowing. Check the event log for queue overflow errors (if event logging is supported by the product and enabled).
+ The client method called was 'ReadMultipleItems'.ultipleItems'.);

- then after some time system doesn't return control from the ReadMultipleItems method;

We also tried to connect with different applications (using EasyDAClient and other OPC clients) while getting this errors from our main application and were able to connect succesfully.
It may be worth to mention that we also have created very small application that does the same job related to EasyDAClient but uses much less resorces, only 3 threads, and with less aggressive garbage collecting and on this application we were not able to reproduce the issue in the same environment.

It is really important for our company to make it work ASAP. Please advice how can we troubleshoot the issue if possible.

↧

Wrong values returned from ReadMultiple - by: veda

March 4, 2019, 11:38 pm

≫ Next: Unable to reconnect to OPC Server - by: veda

≪ Previous: Random Disconnect from OPC server - by: Olya

We have an application where we have an array of "UAReadArguments". We pass this array to EasyUAClient.ReadMultiple. When we examine the result of this call, the values returned are not correct even though we get UAAttributeDataResult.Succeeded and UAAttributeDataResult.AttributeData.HasValue (we compare with the values shown in Siemens OPC Scout client). I have not found any definitive pattern, but it looks like the values are old, and not updated correctly. Is this a known issue? Any idea how to fault find this?

↧

Unable to reconnect to OPC Server - by: veda

March 5, 2019, 12:12 am

≫ Next: Assembly has method 'OnDeserializedMethod' with an incorrect signature - by: usmanshahid

≪ Previous: Wrong values returned from ReadMultiple - by: veda

We have an application that connects to several OPC Servers, and we have one instance of EasyUAClient per server. On my development computer I connect to the OPC servers via VPN connection. I am doing some stability verification and disconnect and reconnect the VPN connection several times to verify that the EasyUAClient reconnects to all the OPC servers automatically. Normally all servers are reconnected within a reasonable time, but I have seen several cases where the EasyUAClient fails to connect to one of the OPC servers (random which server). Typically one of the servers get "stuck" in Connecting state (have waited 20 minutes for reconnect without success). If I restart my application, all connections are working. Do you have any idea how to fault find on this issue?

Note: The ServerConditionChanged callback is set on an instance of EasyUAClient, but acts like a static function. We (sometimes) get callback on the wrong EasyUAClient object and needs to verify the EasyUAServerConditionChangedEventArgs.EndpointDescriptor to perform the correct state change on the correct object.

↧

Assembly has method 'OnDeserializedMethod' with an incorrect signature - by: usmanshahid

March 5, 2019, 2:48 am

≫ Next: Connection problem with x64 client to x86 server - by: Olya

≪ Previous: Unable to reconnect to OPC Server - by: veda

I recently updated my application to the QuickOPC 2018.3 but now whenever I try to run the application, it throws the following exception:

↧

Connection problem with x64 client to x86 server - by: Olya

March 5, 2019, 5:29 am

≫ Next: BadSessionClosed causes disconnect and reconnect of server when subscribing - by: veda

≪ Previous: Assembly has method 'OnDeserializedMethod' with an incorrect signature - by: usmanshahid

Hello.

Recently we encountered a problem when connecting from EasyDAClient in x64 process to x86 OPC server on high load.

Attached is a code to c# console Application which connects to OPC server using EasyDAClient and requests 5000 tags per 2 seconds. When it is being started from 32bit process it runs smoothly but if we run it from x64 process it is starting to fail after a few requests with the next error : Read not completed. This error indicates that it could not be verified that the requested read operation was completed during the timeout period. It is possible that the read operation will actually succeed or fail, but later. Increase the timeout period if you want to obtain a positive or negative indication of the operation outcome. Other reason for this error may be that under heavy loads, topic request or response queue is overflowing. Check the event log for queue overflow errors (if event logging is supported by the product and enabled).
+ The client method called was 'ReadMultipleItems'.

The problem may be related to this topic but Iam not sure because we are not using any subscriptions there (only pulling).

We also attached an xml document with Matrikon OPC simulation server namespace configuration that we are using.
Can you please tak a look into it? Thank you in advance.

↧

BadSessionClosed causes disconnect and reconnect of server when subscribing - by: veda

January 22, 2019, 4:09 am

≫ Next: Getting 'Read not completed' and 'Write not completed' errors while trying to read from Softing.OPC.S7 - by: djorsher

≪ Previous: Connection problem with x64 client to x86 server - by: Olya

Hi

Currently reviewing your product. I have an application where I am connecting to several different OPC servers (with seperate instances of EasyUAClient). The application is running and retrieving values at defined interval, but I have some connection issue at regular intervals (typically approx every minute). The client disconnects and immediately connects again. Se below for output from EasyUAClient.LogEntry. Do you have any idea why this is happening? I connect to Siemens NET OPC servers and have removed all security (this is located in an isolated network).

Output:
[12:59:22 INF] Warning(2051): The OPC-UA client session with connect sequence number 51 on endpoint URL "opc.tcp://192.168.23.212:4845" has encountered a publish error with code 0x80260000 for subscription ID 0 and sequence number 0. The error might be from the Publish or the Republish service. Further publish errors with this code on this session will not be logged.
Service result: BadSessionClosed 'BadSessionClosed'.
[12:59:22 INF] Information(2024): The OPC-UA client session with connect sequence number 51 is disconnecting from endpoint URL "opc.tcp://192.168.23.212:4845".
[12:59:22 INF] opc.tcp://192.168.23.50:4840: Disconnecting
[12:59:22 INF] opc.tcp://192.168.23.249:55101: Disconnecting
[12:59:22 INF] Information(2026): The OPC-UA client session on endpoint URL "opc.tcp://192.168.23.212:4845" failed at tick 90495265 and will retry in 10000 milliseconds.
[12:59:22 INF] opc.tcp://192.168.23.50:4840: Disconnected
[12:59:22 INF] opc.tcp://192.168.23.249:55101: Disconnected
[12:59:22 INF] Information(2034): Failed to close the OPC-UA client session (with connect sequence number 51) to endpoint URL "opc.tcp://192.168.23.212:4845". This error is generally ignored.
OPC-UA service result - (no description available) = BadSessionIdInvalid.
---- SERVICE RESULT ----
Status Code: {BadSessionIdInvalid} = 0x80250000 (2149908480)

[12:59:22 INF] opc.tcp://192.168.23.212:4845: Disconnecting
[12:59:22 INF] opc.tcp://192.168.23.212:4845: Disconnected
[12:59:22 INF] Information(2025): The OPC-UA client session with connect sequence number 51 has disconnected from endpoint URL "opc.tcp://192.168.23.212:4845".
[12:59:22 INF] opc.tcp://192.168.23.61:55101: Disconnecting
[12:59:22 INF] opc.tcp://192.168.23.61:55101: Disconnected
[12:59:22 INF] Information(2026): The OPC-UA client session on endpoint URL "opc.tcp://192.168.23.212:4845" failed at tick 90495281 and will retry in 10000 milliseconds.
[12:59:22 INF] opc.tcp://192.168.23.211:4845: Disconnecting
[12:59:22 INF] opc.tcp://192.168.23.211:4845: Disconnected
[12:59:22 INF] Warning(3201): The status subscription for an OPC-UA session on endpoint URL "opc.tcp://192.168.23.212:4845" is in failure. Further such warnings on this session will not be logged.
OPC-UA service result - An error specific to OPC-UA service occurred.
---- SERVICE RESULT ----
Status Code: {BadSessionClosed} = 0x80260000 (2149974016)
Description: BadSessionClosed
Additional Info: <ExceptionTrace>

[12:59:32 INF] Information(2021): The OPC-UA client session with connect sequence number 52 is connecting to endpoint URL "opc.tcp://192.168.23.212:4845".
[12:59:32 INF] opc.tcp://192.168.23.249:55101: Connecting
[12:59:32 INF] opc.tcp://192.168.23.50:4840: Connecting
[12:59:32 INF] opc.tcp://192.168.23.212:4845: Connecting
[12:59:32 INF] opc.tcp://192.168.23.61:55101: Connecting
[12:59:32 INF] Information(2031): The OPC-UA client session with connect sequence number 52 for discovery URL "opc.tcp://192.168.23.212:4845" will use an endpoint selection policy that has warnings. The policy warnings are:
- An endpoint with obsolete security policy may be selected by this policy.

[12:59:32 INF] opc.tcp://192.168.23.211:4845: Connecting
[12:59:32 INF] Information(2001): OPC-UA endpoint selection on discovery URL "opc.tcp://192.168.23.212:4845" candidate report (2 entries) follows.
[0:AcceptedNotWinner(130), 1:Winner(1000+0)].
[12:59:32 INF] Warning(2002): The OPC-UA server endpoint URL "opc.tcp://MaintHMI:4845" with security policy URI " opcfoundation.org/UA/SecurityPolicy#None " and transport policy URI " opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary ", selected using discovery on endpoint URL "opc.tcp://192.168.23.212:4845", has zero security level. Using this endpoint is not recommended and is only supported for backward compatibility. This happens when no other endpoints are available and eligible for selection.
[12:59:32 INF] Warning(2005): The preliminary OPC-UA server endpoint URL selected using discovery on endpoint URL "opc.tcp://192.168.23.212:4845/" differs in host name or port number from the discovery endpoint. The original endpoint URL "opc.tcp://MaintHMI:4845" has been replaced by "opc.tcp://192.168.23.212:4845/".
[12:59:32 INF] Information(2007): An OPC UA endpoint has been selected and normalized. Endpoint URL: "opc.tcp://192.168.23.212:4845/", security mode: 'None', security policy URI: " opcfoundation.org/UA/SecurityPolicy#None ", transport profile URI: " opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary "
[12:59:32 INF] Information(2032): The OPC-UA client session with connect sequence number 52 has preselected an OPC-UA endpoint for discovery URL "opc.tcp://192.168.23.212:4845" with following parameters:
Endpoint URL "opc.tcp://192.168.23.212:4845/", message security mode 'None', security policy URI " opcfoundation.org/UA/SecurityPolicy#None ", transport profile URI " opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary , use binary encoding: yes.
[12:59:32 INF] Information(2011): The OPC-UA client session with connect sequence number 52 user token selection on endpoint URL "opc.tcp://192.168.23.212:4845" candidate report (2 entries) follows.
[0:Winner(""), 1:ValidNotEligible(NotApplicable(" docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0 "))].
[12:59:32 INF] Information(2013): The OPC-UA client session with connect sequence number 52 on endpoint URL "opc.tcp://192.168.23.212:4845" has been associated with user identity token type 'Anonymous', display name "Anonymous".
[12:59:32 INF] opc.tcp://192.168.23.50:4840: Connected
[12:59:32 INF] Information(2171): The OPC-UA server on endpoint URL "opc.tcp://192.168.23.212:4845" returned an empty list of software certificates.
[12:59:32 INF] opc.tcp://192.168.23.212:4845: Connected
[12:59:32 INF] Warning(2181): The OPC-UA server on endpoint URL "opc.tcp://192.168.23.212:4845" returned an empty server signature.
[12:59:32 INF] opc.tcp://192.168.23.249:55101: Connected
[12:59:32 INF] Information(2023): The OPC-UA client session with connect sequence number 52 has successfully connected to endpoint URL "opc.tcp://192.168.23.212:4845". The server-assigned session Id is "ns=1;g=777741a3-8de9-4f65-8ef7-f8833c665bb3".
[12:59:32 INF] opc.tcp://192.168.23.211:4845: Connected
[12:59:32 INF] Information(3002): The OPC-UA subscription on client session with connect sequence number 52 to endpoint URL "opc.tcp://192.168.23.212:4845" has been successfully created and checked, and given subscription ID 384. Revised publishing interval is 7500, keep-alive count is 11520 and lifetime count is 34560.
[12:59:32 INF] opc.tcp://192.168.23.50:4840: Connected
[12:59:32 INF] opc.tcp://192.168.23.212:4845: Connected
[12:59:32 INF] opc.tcp://192.168.23.249:55101: Connected
[12:59:32 INF] opc.tcp://192.168.23.61:55101: Connected
[12:59:32 INF] opc.tcp://192.168.23.61:55101: Connected
[12:59:32 INF] opc.tcp://192.168.23.211:4845: Connected
[12:59:32 INF] Information(3002): The OPC-UA subscription on client session with connect sequence number 52 to endpoint URL "opc.tcp://192.168.23.212:4845" has been successfully created and checked, and given subscription ID 385. Revised publishing interval is 50, keep-alive count is 1728000 and lifetime count is 5184000.
[13:00:42 INF] Warning(2051): The OPC-UA client session with connect sequence number 52 on endpoint URL "opc.tcp://192.168.23.212:4845" has encountered a publish error with code 0x80260000 for subscription ID 0 and sequence number 0. The error might be from the Publish or the Republish service. Further publish errors with this code on this session will not be logged.
Service result: BadSessionClosed 'BadSessionClosed'.

↧

Getting 'Read not completed' and 'Write not completed' errors while trying to read from Softing.OPC.S7 - by: djorsher

February 27, 2017, 9:15 am

≫ Next: BadSessionClosed causes disconnect and reconnect of server when subscribing - by: veda

≪ Previous: BadSessionClosed causes disconnect and reconnect of server when subscribing - by: veda

Hi,

I'm trying to read and write to a Softing S7 server running on localhost, but getting errors.

I'm using OpcLabs.EasyOpc.DataAccess.EasyDAClient via the win32com client for Python.

I've installed on my machine (Windows 7) both the Softing S7 server and the Softing Demo Server.

When reading and writing from/to the Demo Server - it works.

The commands I'm issuing are:
client = win32com.client.Dispatch('OpcLabs.EasyOpc.DataAccess.EasyDAClient')
client.WriteItemValue('localhost','Softing.OPC.S7.DA.1', 'NodeB/Test1', 1)
client.ReadItemValue('localhost','Softing.OPC.S7.DA.1','NodeB/Test1')

I'm getting these errors:

1. Read not completed. This error indicates that it could not be verified that the requested read operation was completed during the timeout period. It is possible that the read operation will actually succeed or fail, but later. Increase the timeout period if you want to obtain positive or negative indication of the operation outcome. Other reason for this error may be that under heavy loads, topic request or response queue is overflowing. Check the event log for queue overflow errors (if event logging is supported by the product and enabled).

2. Write not completed. This error indicates that it could not be verified that the requested write operation was completed during the timeout period. It is possible that the write operation will actually succeed or fail, but later. Increase the timeout period if you want to obtain positive or negative indication of the operation outcome. Other reason for this error may be that under heavy loads, topic request or response queue is overflowing. Check the event log for queue overflow errors (if event logging is supported by the product and enabled).

After issuing the write operation, the item value is set to 1, but it hangs for a while, and then I'm getting this error.

Any help would be appreciated.

↧

BadSessionClosed causes disconnect and reconnect of server when subscribing - by: veda

January 22, 2019, 4:09 am

≫ Next: Updaterate 0 - by: treams-gmbh

≪ Previous: Getting 'Read not completed' and 'Write not completed' errors while trying to read from Softing.OPC.S7 - by: djorsher

↧

Updaterate 0 - by: treams-gmbh

March 11, 2019, 6:50 am

≫ Next: Unable to reconnect to OPC Server - by: veda

≪ Previous: BadSessionClosed causes disconnect and reconnect of server when subscribing - by: veda

Hi,

I have an very fast OPC-DA Item and the documentation tells me:

A very fast transfer rate is required for the measuring data. The "Data" item is notified when a modification occurs. Therefore, the "Update Rate" zero is required for the group that contains this item.

If i set the updaterate in the subscripeItem() function to zero I receive an exception. Currently I work with updaterate 1. It works but sometimes i miss data.

Is there a workearound to solve that problem.

Thanks and Regards
Tony

↧

Unable to reconnect to OPC Server - by: veda

March 5, 2019, 12:12 am

≫ Next: Callback enqueuer overflow. - by: zaglerp

≪ Previous: Updaterate 0 - by: treams-gmbh

↧

Callback enqueuer overflow. - by: zaglerp

March 12, 2019, 5:43 am

≫ Next: Error Bad Not Readable - by: 333nt

≪ Previous: Unable to reconnect to OPC Server - by: veda

Hi!

During a OPC server failure, we were experiencing lots of LogEntry calls in out client:
Information(1102): The overflow condition of the callback enqueuer is clearing. The overflow count was 2.
Error(1101): Callback enqueuer overflow. The bounded queue capacity is 100000.

What is the reason for this logging?
We are also getting many calls from item subscriptions, although there were no value changes on the items.

Has anyone seen this before? Is it safe to ignore?

Kind regards
Peter

↧

Error Bad Not Readable - by: 333nt

March 12, 2019, 10:13 am

≫ Next: DAClient not getting changes / tags remaining active after disposing - by: saratalley

≪ Previous: Callback enqueuer overflow. - by: zaglerp

Hi,

We seem have a problem at reading values from an OPC UA Server.
At connection it shows the alert i put in the attachments, Saying the certificate is not Validated.
We went through the problem just by adding the line

EasyUAClient.EngineParameters.CertificateAcceptancePolicy. AcceptAnyCertificate = True;

in the code. Or by pressing Yes in the window.

When reading the node from our client it results in a null value.
When using the connectivity exporer gives the status BadNotReadable = 0x803A0000

.

We tried using the client that comes with the machine and it works fine giving back the value

How could we solve this issue?

Best regards.

↧

DAClient not getting changes / tags remaining active after disposing - by: saratalley

March 15, 2019, 11:57 am

≫ Next: Cannot find or open the PDB file - by: khanhqhoang

≪ Previous: Error Bad Not Readable - by: 333nt

I have a .Net application in which I am using EasyDAClient. On starting the app. I run SubscribeMultipleItems to read approximately 600 tags. Sometimes when I run the app the tags populate my controls (textbox.text, etc.) correctly - this is done through the ItemChanged event. Other times it can anywhere from 5-10 minutes for the ItemChanged event to fire - this should obviously happen on startup and anytime a tag value changes. On closing the form I unsubscribe all items and dispose of the client. On the server I have noticed that the client will be disposed, but sometimes it will show 0 of 600 tags active - if I run the app a second time the number will be 600 of 1200 tags active, this doubles each time on restarting the app. If I wait a period of time (I haven't clocked it but it seems to be between 5-10 mins) eventually it will drop to 0 of 0 tags active, and I can run the app and tags usually (90% of the time) begin to populate correctly again. Any help on what I am missing would be appreciated.

↧

Cannot find or open the PDB file - by: khanhqhoang

March 17, 2019, 7:13 am

≫ Next: Get data from ARRAY Excel VBA - by: Šilhavý

≪ Previous: DAClient not getting changes / tags remaining active after disposing - by: saratalley

Suddenly, I ran into the following error message when I tried to run my program. It used to work before but somehow I encountered this error suddenly. I tried uninstall and reinistall OPC Lab and also from NuGet but it did not fix the issue. I am able to build the application but ran into issue when I tried up click on buttons that attempt to update or read OPC UA tags from Kepware EX 5.18. My Kepware EX is working fine.

File Attachment:

File Name: Program.cs
File Size: 1 KB

File Attachment:

File Name: Program.cs
File Size: 1 KB

Please help,

Thanks

Khanh

Below is the debug ouput from VS2017

'OPCUATest.exe' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Users\kqh8269\source\repos\OPCUATest\OPCUATest\bin\Debug\OPCUATest.exe'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\Users\kqh8269\source\repos\OPCUATest\OPCUATest\bin\Debug\OpcLabs.EasyOpcUA.dll'. Cannot find or open the PDB file.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\Users\kqh8269\source\repos\OPCUATest\OPCUATest\bin\Debug\OpcLabs.BaseLib.dll'. Cannot find or open the PDB file.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'Opc.Ua.Client'. Cannot find or open the PDB file.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'Opc.Ua.Core'. Cannot find or open the PDB file.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'Opc.Ua.Configuration'. Cannot find or open the PDB file.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\Users\kqh8269\source\repos\OPCUATest\OPCUATest\bin\Debug\OpcLabs.BaseLibForms.dll'. Cannot find or open the PDB file.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll'. Symbols loaded.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xaml\v4.0_4.0.0.0__b77a5c561934e089\System.Xaml.dll'. Cannot find or open the PDB file.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'BoxedAppSDK.Managed'. Cannot find or open the PDB file.
'OPCUATest.exe' (CLR v4.0.30319: OPCUATest.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll'. Symbols loaded.
Exception thrown: 'Opc.Ua.ServiceResultException' in Opc.Ua.Core
Exception thrown: 'Opc.Ua.ServiceResultException' in Opc.Ua.Core
Exception thrown: 'System.ObjectDisposedException' in Opc.Ua.Core
The thread 0x16fc has exited with code 0 (0x0).
The thread 0x3bfc has exited with code 0 (0x0).
The thread 0x14d0 has exited with code 0 (0x0).
The thread 0x3cb0 has exited with code 0 (0x0).
The thread 0x1470 has exited with code 0 (0x0).
The thread 0xd34 has exited with code 0 (0x0).
The thread 0x456c has exited with code 0 (0x0).
The thread 0x14b4 has exited with code 0 (0x0).
The program '[5140] OPCUATest.exe' has exited with code 0 (0x0).

↧

Get data from ARRAY Excel VBA - by: Šilhavý

February 14, 2019, 11:27 am

≫ Next: Performance with 500 to 1000 devices - by: sjscheider

≪ Previous: Cannot find or open the PDB file - by: khanhqhoang

Hello.
Can you help me with getting data out of the UA Server (Arburg machine) using EasyOPCUA.
Single value works fine. ut how can I get the full array or just given part of the array?:
Single:
mClient.ReadValue("opc.tcp://1.1.1.1:4880/Arburg", "ns=2;i=212365") OK

And value, which is an array?:
mClient.Read("opc.tcp://1.1.1.1:4880/Arburg", "ns=2;i=12345;2") or [2] or ,2 ?

Thanks for your reply.

↧

Performance with 500 to 1000 devices - by: sjscheider

March 20, 2019, 7:30 am

≫ Next: OPC XML-DA Basic Authorization doesn't work - by: Slavik

≪ Previous: Get data from ARRAY Excel VBA - by: Šilhavý

We are currently prototyping with the trial and have questions about the performance. We are ready to purchase and have asked this question on the contact us page but for some reason we need to ask it here.

Do you foresee any issues connecting to 500 to 1000 OPC-UA devices? Each device will have 3 subscriptions to complex data nodes. One of the subscriptions will be at 500 ms, but there should less than 100 messages per day per device. The most active node the subscription is currently at 2000 ms, with data change about 15 to 20 times per minute.

Any guidance you can offer would be greatly appreciated. I currently have a prototype connecting to 4 devices without issue. We would like to stress test but we are limited to the 30 minutes of the trial license.

↧

OPC XML-DA Basic Authorization doesn't work - by: Slavik

March 20, 2019, 9:57 am

≫ Next: Failed to detect server disconnect/subscription update - by: veda

≪ Previous: Performance with 500 to 1000 devices - by: sjscheider

Hello,

We have an OPC XML DA server that requires authorization for writing values. Obviously, when I'm trying to write values without specifying username and password I'm getting error saying.

Looking for a solution I've found that I can pass NetworkSecurity object as a parameter of ServerDescriptor constructor, so I changed
new ServerDescriptor("http://IP:port/DA") to new ServerDescriptor("http://IP:port/DA", new NetworkSecurity(user, password)). But, unfortunately it doesn't helped me.
Then I've compared using Wireshark requests sent from dOPC Explorer client and from my program and found that they are differ by Authorization request header. Requests sent from dOPC Explorer contains this header with specified username and password needed for Basic authorization while requests from my app doesn't contain such header at all.

Then I realized that NetworkSecurity might have nothing about HTTP authorization so I simply tried to specify user and password in URL like this:
http://username:password@IP:port/DA
And now I instead of access denied error I have another one saying

Here is the code:

Does basic HTTP authorization supported by the library? If yes - could you please correct me what I'm doing wrong.

Thanks in advance!

↧

Failed to detect server disconnect/subscription update - by: veda

March 21, 2019, 2:11 am

≫ Next: Get data from ARRAY Excel VBA - by: Šilhavý

≪ Previous: OPC XML-DA Basic Authorization doesn't work - by: Slavik

First observation:
We see an issue with some subscribed variables/values not being updated after the client has been running for some hours/days. If I start a second instance of the same client code on a different machine this client will receive update of subscription updates. So I end up with two identical clients running on two servers connected to the same OPC Server. The client that has been running for a long time will stop reporting updates (only some values, not all), while the newely started client will work as expected.

Additional note: The OPC server we see the problem realted to has very seldom updates of values.

Second observation:
If we add a new subscription to the same server, it seams like we do not get any callbacks on the new subscription either (can not verify directly, but status is "bad" and hence not updated by the DataChangeNotification callback). We have not received any callbacks on ServerConditionChanged about disconnect, even though the client behaves like it is not connected. If we start a new (additional) instance of the client, this new instance works as expected and will receive callbacks as designed.

↧