Closed bjaben closed 3 years ago
Is there any news on this issue? We are facing the same problem in our project.
This is old, but something similar is happening to me.
We're using the Wrapper with a GE iFIX OPC DA server. If we use a standard OCP UA Client (like Integration Objects one) it works flawlessly, but I soon as I try to get a NodeID variable with node-opcua
library it throws this same error.
Hello,
we start to have a lot of issues as soon as we start to acquire like 130k signals,i was trying to debug but i have no idea how ths Wrapper exposes opcua methods.
we have timeout when our client (opcpublisher) istrying to setmonitoreditem (1000 monitored nodes )
the issue as well is there is no documentation about how this Wrapper works !
if anyone could help i'd appreciate.
I am using the wrapper to get 30K from DeltaV OPC Server subscribing at 1000ms.
@bjaben @AlinMoldovean - I am wondering if this issue should be marked closed for now due to inactivity.
Note that I have used the wrapper subscribing to 30K and the parameter were changing every second.
Hello,
I know that is issue is closed, but I need some help with something like this (maybe I will put another issue). Basically I can use the wrapper with few items, but when I tried to load more than 500 items, the client just trace timeout's messages. I can´t monitore the items in ths case... Am I missing something basic? Please if someone could help i'd appreciate ...
@EdnerPontes, can you please check if the server is able to handle 500 items? I would start with CPU usage of the server.
By the way, what OPC classic server are you wrapping?
@tukotech thank you for your comment ! We are using (wrapping) our DA Server - (2.05a classic and CTT Compliant) and its normal the usage of thousands items. We tested against others OPC UA Clients with the same behaviour. We still tested with some simulation DA Server (Matrikon, Integration
@EdnerPontes - how does the item path looks like for your OPC DA server?
For example, DeltaV OPC server looks like this:
MODULE1/FB/PARAM.CV
The reason I am asking is that path separator should be configured on the wrapper correctly otherwise it will have to traverse the address space to look for the item. So for the above example, path separator is /
See link below for a fork I did and how it was configured: https://github.com/wickedtuko/COMtoUA/blob/deb57685b11bdb8c74a0ca22846f4903556951a5/ComIOP/Wrapper/ServerWrapper/Opc.Ua.ComServerWrapper.Config.xml#L152
@tukotech it was a really good tip ! Once again thank you !
Our tag separator is "." (dot) so our tag looks like: Block.Parameter.Element
Now I changed the xml to: "... <"SeperatorChars">.<"/SeperatorChars"> ..."
Now I´ll do some tests to observe the performance and if we can reach more than is expected...
@tukotech once again thank you for your time and for have answered my question...
"The reason I am asking is that path separator should be configured on the wrapper correctly otherwise it will have to traverse the address space to look for the item. So for the above example, path separator is /"
Our tag separator is dot "." ....I follow your instruction and changed the xml ... this maked the difference and now everything is working fine !
Best Regards !
In a project we're seeing the below exception when using the UA COM Server Wrapper. We're running against a Cimplicity 8.1 and 8.2 OPC DA Servers. We have the UA COM Server Wrapper set up on the same machine as Cimplicity (running Window 7). We can sample nodes through the Wrapper using UAExpert but when we sample nodes through the Wrapper using the OPC Publisher from Microsoft the following exception is thrown repeatedly by the UA COM Server Wrapper:
Id: Bad Description: Cannot access a disposed object. Object name: 'The COM server has been disposed.'. Cannot access a disposed object. Object name: 'The COM server has been disposed.' --- at Opc.Ua.Com.Client.ComObject.BeginComCall[T](String methodName, Boolean throwOnError) in C:\Users\User\source\repos\UA-.NETStandard\ComIOP\Common\Client\ComObject.cs:line 171 --- at Opc.Ua.Com.Client.ComDaClient.ReadPropertyValues(String itemId, Int32[] propertyIds) in C:\Users\User\source\repos\UA-.NETStandard\ComIOP\Common\Client\Da\ComDaClient.cs:line 843
This happens even if we're just sampling one node every 2 seconds.
Here are the reproduction steps:
Opc.Ua.ComServerWrapper.Config.xml:
publishednodes.json:
Any idea what could be happening here?