Online Forums
Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
Monitor Item Change
15 May 2015 05:28 #3142
by support
Replied by support on topic Monitor Item Change
In addition to the earlier list of logs to be taken, I would also like to enable the extended tracing inside QuickOPC. This can be done in application configuration file - example attached.
The application configuration file needs to be named the same as your application, with an added “.config” extension, and placed alongside the application, For example, for “MyApp.exe”, the configuration file is “MyApp.exe.config”. Note that the development tools sometimes provide “shortcuts” for the naming and placing procedure. For example, Visual Studio C# projects contain an app.config file, which becomes the application configuration file automatically – Visual Studio copies it to the output folder and renames it appropriately.
In hosted environments, such as ASP.NET, the name and location of the configuration file may be different as well.
Sometimes the configuration does not load for unknown reason (Microsoft?), in which case we would have to live without it; but if it works, it would be good to have.
Best regards
The application configuration file needs to be named the same as your application, with an added “.config” extension, and placed alongside the application, For example, for “MyApp.exe”, the configuration file is “MyApp.exe.config”. Note that the development tools sometimes provide “shortcuts” for the naming and placing procedure. For example, Visual Studio C# projects contain an app.config file, which becomes the application configuration file automatically – Visual Studio copies it to the output folder and renames it appropriately.
In hosted environments, such as ASP.NET, the name and location of the configuration file may be different as well.
Sometimes the configuration does not load for unknown reason (Microsoft?), in which case we would have to live without it; but if it works, it would be good to have.
Best regards
The following user(s) said Thank You: adid@contel.co.il
Please Log in or Create an account to join the conversation.
14 May 2015 17:37 #3141
by support
Replied by support on topic Monitor Item Change
Hello, yes, will work on this tomorrow.
To clarify, in no way I expect the problem be solved or explained during the session. The purpose of the session is to collect the data. I will then have hard enough time to analyze them off-line and cross my fingers that it will give some outcome.
Best regards
To clarify, in no way I expect the problem be solved or explained during the session. The purpose of the session is to collect the data. I will then have hard enough time to analyze them off-line and cross my fingers that it will give some outcome.
Best regards
The following user(s) said Thank You: adid@contel.co.il
Please Log in or Create an account to join the conversation.
- adid@contel.co.il
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 106
- Thank you received: 0
14 May 2015 13:07 #3140
by adid@contel.co.il
Replied by adid@contel.co.il on topic Monitor Item Change
hello,
i saw the email that you sent me.
as written in this email i will wait for you to connect to my computer and see the problem live. i think it's better this way, because in this way i can change the log if needed in my service if we need more additional data. also we can do changes and see if the problem remain or resolved.
i am waiting for your answer to confirm the meating tommorow.
thank you,
Adi Damty
i saw the email that you sent me.
as written in this email i will wait for you to connect to my computer and see the problem live. i think it's better this way, because in this way i can change the log if needed in my service if we need more additional data. also we can do changes and see if the problem remain or resolved.
i am waiting for your answer to confirm the meating tommorow.
thank you,
Adi Damty
Please Log in or Create an account to join the conversation.
14 May 2015 12:18 #3139
by support
Replied by support on topic Monitor Item Change
It is relatively easy, I think. I'd like to set up the logging so that we get the logs from all possible sources for the same case - and with timestamps to correlate them. These sources are:
1. What you yourself log in your application, especially the incoming events or operation results from QuickOPC - we do not log those. I could see that you log them already, and it's good that you log things like ServerTimestamp. The more info you put there, the better.
2. The LogEntry events from QuickOPC that you are already capturing.
3. The Wireshark capture (more about it later).
4. If you can enable some useful logging on the server side, then do it as well.
For the Wireshark, please install the latest version. I do not normally do it, therefore I made a little exercise today. All I needed was to start Wireshark, start a capture, select a network interface, and give it a capturing filter: I used the filter "tcp port 51210", because that's the server port I had for testing, your filter may be different. There may also be additional communication for discovery purposes, and that can run on different ports (4840, 80, 52601, 4843), but we do not have problems with that so they are not strictly necessary. Select a file when the capture should be stored (if not selected, looks like that Wireshark will ask for it anyway when attempting to close it). The press the "Start" button in the "Wireshark: Capture Options" dialog, and it should start doing its job. When enough is captured, there is a stop button on the Wireshark toolbar. It is as simple as that. The remainder of it - the Analysis - can be done off-line.
Because of this, I really think you can do it yourself, but I will contact you by email with further information to my availability.
Best regards
1. What you yourself log in your application, especially the incoming events or operation results from QuickOPC - we do not log those. I could see that you log them already, and it's good that you log things like ServerTimestamp. The more info you put there, the better.
2. The LogEntry events from QuickOPC that you are already capturing.
3. The Wireshark capture (more about it later).
4. If you can enable some useful logging on the server side, then do it as well.
For the Wireshark, please install the latest version. I do not normally do it, therefore I made a little exercise today. All I needed was to start Wireshark, start a capture, select a network interface, and give it a capturing filter: I used the filter "tcp port 51210", because that's the server port I had for testing, your filter may be different. There may also be additional communication for discovery purposes, and that can run on different ports (4840, 80, 52601, 4843), but we do not have problems with that so they are not strictly necessary. Select a file when the capture should be stored (if not selected, looks like that Wireshark will ask for it anyway when attempting to close it). The press the "Start" button in the "Wireshark: Capture Options" dialog, and it should start doing its job. When enough is captured, there is a stop button on the Wireshark toolbar. It is as simple as that. The remainder of it - the Analysis - can be done off-line.
Because of this, I really think you can do it yourself, but I will contact you by email with further information to my availability.
Best regards
The following user(s) said Thank You: adid@contel.co.il
Please Log in or Create an account to join the conversation.
- adid@contel.co.il
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 106
- Thank you received: 0
13 May 2015 06:55 #3134
by adid@contel.co.il
Replied by adid@contel.co.il on topic Monitor Item Change
hello,
i want you to connect to my computer, and to operate with me the Wireshark with the configuration needed, and show me what files to save and send to you after the problem occured again.
After the problem occured again, i will send you the files you request, so you can analyze them two.
Today i also send Kepware, the server vendor, the log files they ask after i recreate the problem, so they can anlazye the problem two.
please contact me throgh my email, so i will give you teamViewer userId and password.
thank you,
Adi Damty
i want you to connect to my computer, and to operate with me the Wireshark with the configuration needed, and show me what files to save and send to you after the problem occured again.
After the problem occured again, i will send you the files you request, so you can analyze them two.
Today i also send Kepware, the server vendor, the log files they ask after i recreate the problem, so they can anlazye the problem two.
please contact me throgh my email, so i will give you teamViewer userId and password.
thank you,
Adi Damty
Please Log in or Create an account to join the conversation.
12 May 2015 19:16 #3132
by support
Replied by support on topic Monitor Item Change
Hello,
Re
We request the keep-alive count 10 from the server. The server may revise it (but I doubt it does). Currently you cannot change it in QuickOPC. The keep-alive interval is calculated in multiples of publish interval. If your publish interval is e.g. 100 milliseconds, the keep-alive interval would be 10*100 milliseconds = 1 second. There is no point in reducing it in your case: It is apparent that because the "subscription publishing has stopped" errors are appearing, that the keep-alive interval is either good enough, or one may think that it may need increasing, but it certainly does not need any reducing.
Re
Wouldn't it be possible to make the behavior reproducible in form of a virtual machine image? That would allow fully off-line investigation.
Best regards
Re
for how much time, the server and and the client exchange messages even when there are no data changes ? if the server and client exchange messasges now, how much time it takes till they exchange messages again ? can i control this time and reduce it ?
We request the keep-alive count 10 from the server. The server may revise it (but I doubt it does). Currently you cannot change it in QuickOPC. The keep-alive interval is calculated in multiples of publish interval. If your publish interval is e.g. 100 milliseconds, the keep-alive interval would be 10*100 milliseconds = 1 second. There is no point in reducing it in your case: It is apparent that because the "subscription publishing has stopped" errors are appearing, that the keep-alive interval is either good enough, or one may think that it may need increasing, but it certainly does not need any reducing.
Re
It would be theoretically possible but it has low value at this current point. In order to figure out what's happening, "seeing" it brings little: There is so much data that needs to be analyzed that during the session itself I won't be able to tell anything. I need to get the communication logs and analyze them, and that's time consuming.can you connect to my computer using TeamViewer, and see this happend live ?
Wouldn't it be possible to make the behavior reproducible in form of a virtual machine image? That would allow fully off-line investigation.
Best regards
The following user(s) said Thank You: adid@contel.co.il
Please Log in or Create an account to join the conversation.
12 May 2015 19:02 #3131
by support
Replied by support on topic Monitor Item Change
As I stated, I cannot conclude more from just this kind of logs. I need to see what is happening closer "to the wire", which can be done using Wireshark, or OPC Foundation CTT (which is however more intrusive and problematic).
Please Log in or Create an account to join the conversation.
- adid@contel.co.il
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 106
- Thank you received: 0
12 May 2015 09:16 #3126
by adid@contel.co.il
Replied by adid@contel.co.il on topic Monitor Item Change
hello,
" It is just a rule that the client and server need to exchange messages even when there are no data changes to communicate from the server to the client. " - for how much time, the server and and the client exchange messages even when there are no data changes ? if the server and client exchange messasges now, how much time it takes till they exchange messages again ? can i control this time and reduce it ?
"In order to move forward, I need either a reproducible configuration that I can investigate here, or a Wireshark log which starts with "good" behavior and then turns into "bad" behavior" - can you connect to my computer using TeamViewer, and see this happend live ?
thank you,
Adi Damty
" It is just a rule that the client and server need to exchange messages even when there are no data changes to communicate from the server to the client. " - for how much time, the server and and the client exchange messages even when there are no data changes ? if the server and client exchange messasges now, how much time it takes till they exchange messages again ? can i control this time and reduce it ?
"In order to move forward, I need either a reproducible configuration that I can investigate here, or a Wireshark log which starts with "good" behavior and then turns into "bad" behavior" - can you connect to my computer using TeamViewer, and see this happend live ?
thank you,
Adi Damty
Please Log in or Create an account to join the conversation.
- adid@contel.co.il
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 106
- Thank you received: 0
12 May 2015 09:09 #3125
by adid@contel.co.il
Replied by adid@contel.co.il on topic Monitor Item Change
hello,
let's try to understand by the event log of another example why there is delay of 3 minutes, in dataChange event.
in this example tag mainConFault was changing in 16:03:57 and i get the dataChange event in 16:06:46.
can you point for Kepware blame or for opcLabs problem in this example ?
thank you,
Adi Damty
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – EasyUAClient_LogEntry Message The OPC-UA client session on endpoint URL "opc.tcp://10.1.101.136:49320" will request a Republish of 1 missing message(s) with sequence numbers between 40 and 40 for the subscription Id 1768. Further such warnings on this session will not be logged.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – EasyUAClient_LogEntry Message The OPC-UA client session on endpoint URL "opc.tcp://10.1.101.136:49320" has encountered a publish error with code 0x80280000 for subscription Id 1768 and sequence number 40. 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: BadSubscriptionIdInvalid 'BadSubscriptionIdInvalid'.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
2015-05-11 16:03:50 – EasyUAClient_LogEntry Message The OPC-UA client session is disconnecting from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:50 – EasyUAClient_LogEntry Message The OPC-UA client session has disconnected from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:56 – EasyUAClient_LogEntry Message The OPC-UA client session is disconnecting from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:56 – EasyUAClient_LogEntry Message The OPC-UA client session has disconnected from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
2015-05-11 16:04:57 – EasyUAClient_LogEntry Message The OPC-UA client session is disconnecting from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:04:57 – EasyUAClient_LogEntry Message The OPC-UA client session has disconnected from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:05:52 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
2015-05-11 16:05:57 – EasyUAClient_LogEntry Message The OPC-UA client session is disconnecting from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:05:57 – EasyUAClient_LogEntry Message The OPC-UA client session has disconnected from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
let's try to understand by the event log of another example why there is delay of 3 minutes, in dataChange event.
in this example tag mainConFault was changing in 16:03:57 and i get the dataChange event in 16:06:46.
can you point for Kepware blame or for opcLabs problem in this example ?
thank you,
Adi Damty
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – EasyUAClient_LogEntry Message The OPC-UA client session on endpoint URL "opc.tcp://10.1.101.136:49320" will request a Republish of 1 missing message(s) with sequence numbers between 40 and 40 for the subscription Id 1768. Further such warnings on this session will not be logged.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2406 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – m_EasyUAClientCoils_MonitoredItemChanged PlantModel 2407 Exception OpcLabs.EasyOpc.UA.Engine.UAClientEngineException: The OPC-UA subscription publishing has stopped.
2015-05-11 16:03:45 – EasyUAClient_LogEntry Message The OPC-UA client session on endpoint URL "opc.tcp://10.1.101.136:49320" has encountered a publish error with code 0x80280000 for subscription Id 1768 and sequence number 40. 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: BadSubscriptionIdInvalid 'BadSubscriptionIdInvalid'.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:49 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
2015-05-11 16:03:50 – EasyUAClient_LogEntry Message The OPC-UA client session is disconnecting from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:50 – EasyUAClient_LogEntry Message The OPC-UA client session has disconnected from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:56 – EasyUAClient_LogEntry Message The OPC-UA client session is disconnecting from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:03:56 – EasyUAClient_LogEntry Message The OPC-UA client session has disconnected from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:04:50 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
2015-05-11 16:04:57 – EasyUAClient_LogEntry Message The OPC-UA client session is disconnecting from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:04:57 – EasyUAClient_LogEntry Message The OPC-UA client session has disconnected from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:05:51 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:05:52 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
2015-05-11 16:05:57 – EasyUAClient_LogEntry Message The OPC-UA client session is disconnecting from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:05:57 – EasyUAClient_LogEntry Message The OPC-UA client session has disconnected from endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:46 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA client session is connecting to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message OPC-UA endpoint selection on discovery URL "opc.tcp://10.1.101.136:49320" candidate report (13 entries) follows.
[0:AcceptedNotWinner(80), 1:AcceptedNotWinner(130), 2:EligibleNotAccepted(90), 3:AcceptedNotWinner(140), 4:EligibleNotAccepted(80), 5:EligibleNotAccepted(130), 6:EligibleNotAccepted(90), 7:EligibleNotAccepted(140), 8:Winner(1000+0), 9:EligibleNotAccepted(80), 10:EligibleNotAccepted(130), 11:EligibleNotAccepted(90), 12:EligibleNotAccepted(140)].
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message An OPC-UA endpoint has been selected for discovery URL "opc.tcp://10.1.101.136:49320" with following parameters:
Endpoint URL "opc.tcp://10.1.101.136:49320", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary".
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA server endpoint URL "opc.tcp://10.1.101.136:49320" 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://10.1.101.136:49320", 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.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message OPC-UA user token selection on endpoint URL "opc.tcp://10.1.101.136:49320" 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"))].
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty list of software certificates.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" returned an empty server signature.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" did not return a valid software certificate for product URI "urn:MES-APP-MGL.netafim.com:Kepware.KEPServerEX.V5:UA Server" listed in server endpoints. The server returned 0 software certificate(s) in total.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message The OPC-UA client session has successfully connected to endpoint URL "opc.tcp://10.1.101.136:49320".
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
2015-05-11 16:06:48 – EasyUAClient_LogEntry Message When creating or modifying a monitored item, the OPC-UA server on endpoint URL "opc.tcp://10.1.101.136:49320" has revised the sampling interval to 5000 milliseconds; the requested sampling interval was 15000 milliseconds. Further such warnings on this session will not be logged.
Please Log in or Create an account to join the conversation.
12 May 2015 08:42 #3124
by support
Replied by support on topic Monitor Item Change
Dear Sir,
Re
Re
At this point, it seems that we have a "publishing stopped" problem for which the cause is unknown. Other problems may be just manifestations of this thing (when the subscription does not work, value changes get delayed because reconnections are needed etc.).
In order to move forward, I need either a reproducible configuration that I can investigate here, or a Wireshark log which starts with "good" behavior and then turns into "bad" behavior - from which it should be at least possible to tell which side has misbehaved (I do not want to play "blame" games, but technically this is the first necessary step).
Best regards
Re
It is up to the server when it sends the first item change. I expect it to do immediately, and us to report it immediately as well (where "immediately" meansL well below the 5 seconds you mentioned). However OPC UA is not a real time protocol, therefore there won't be any fixed time guarantees for anything, ever.about the "subscription published has stopped" issue :
1. if the connection was stopped, and then it establish again. how much time it will take from the connection was established till i get the monitorItemChange ? i need this time to be at maximum 5 seconds.
Re
This might be a misunderstanding of how the keep-alive mechanism works. It is not something that monitors the subscription or connection from "above". It operates *inside* the subscription. It is just a rule that the client and server need to exchange messages even when there are no data changes to communicate from the server to the client. Therefore when we create a subscription, we of course know this fact right away.2. also if the connection was stopped, and than it was established after 5 seconds, does the OPCLabs know this after 5 sceonds, or the keep alive mechanism know this just after one minute ? how can i change the keep alive mechanism to check after connection was stopped evey 5-10 seconds ? also does the keep alive mechanism work when there is connection to the server ?
At this point, it seems that we have a "publishing stopped" problem for which the cause is unknown. Other problems may be just manifestations of this thing (when the subscription does not work, value changes get delayed because reconnections are needed etc.).
In order to move forward, I need either a reproducible configuration that I can investigate here, or a Wireshark log which starts with "good" behavior and then turns into "bad" behavior - from which it should be at least possible to tell which side has misbehaved (I do not want to play "blame" games, but technically this is the first necessary step).
Best regards
The following user(s) said Thank You: adid@contel.co.il
Please Log in or Create an account to join the conversation.
Moderators: support
Time to create page: 0.105 seconds