Closed thecalle closed 4 years ago
Browsing also (using magnifing button) is limited to 1000!
Hi, check your server settings! We use 10k nodes in other projects.
Hi Klaus. I connect to the same server using UaExpert Windows client and I get about 4K varibles under Tags. Node-red browser stops exactly at 999.
v3.8.0 of the package? Please, Francesco, could you take a screenshot of the sever limits from UAExpert and push it here or send it by E-Mail!
Hi Klaus.
Package is v.3.8.0, here the screenshot feom UaExpert. I'm using our Browser2Listen example to test.
Thanks in advance.
Francesco
[image: image.png]
Il giorno ven 1 mar 2019 alle ore 13:17 Klaus Landsdorf < notifications@github.com> ha scritto:
v3.8.0 of the package? Please, Francesco, could you take a screenshot of the sever limits from UAExpert and pot it here or send it by E-Mail!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/biancode/node-red-contrib-iiot-opcua/issues/87#issuecomment-468646871, or mute the thread https://github.com/notifications/unsubscribe-auth/AMaXx3NOjuVGiWCw13Uai1xRSeGbbXekks5vSRpsgaJpZM4bSlac .
hm - no image to see here
Check now.
F.
Il giorno ven 1 mar 2019 alle ore 15:38 Klaus Landsdorf < notifications@github.com> ha scritto:
hm - no image to see here
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/biancode/node-red-contrib-iiot-opcua/issues/87#issuecomment-468685550, or mute the thread https://github.com/notifications/unsubscribe-auth/AMaXx3l_cyG1GAToNXJKqI_AM5eXmkgWks5vSTtLgaJpZM4bSlac .
sorry, no image just [image: image.png]
Hi Klaus.
I think images are dropped by GITHub. Last mail has a correct .JPG attach
Francesco
Il giorno ven 1 mar 2019 alle ore 16:26 Klaus Landsdorf < notifications@github.com> ha scritto:
sorry, no image just [image: image.png]
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/biancode/node-red-contrib-iiot-opcua/issues/87#issuecomment-468702261, or mute the thread https://github.com/notifications/unsubscribe-auth/AMaXx-53p7BHhSledjyhYaHmef6rolarks5vSUaggaJpZM4bSlac .
Please, just send it by E-Mail. I did not get any image. Just [image: image.png] also in the E-Mails
Hi Klaus.
I checked the parameter you suggested. The MaxNodesPerBrowse is set to
Francesco.
Il giorno lun 4 mar 2019 alle ore 17:33 Klaus Landsdorf < notifications@github.com> ha scritto:
[image: image] https://user-images.githubusercontent.com/4369867/53747467-9d3b2080-3ea3-11e9-9baa-72adfc164e77.png
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/biancode/node-red-contrib-iiot-opcua/issues/87#issuecomment-469319801, or mute the thread https://github.com/notifications/unsubscribe-auth/AMaXx5hSXiJPf7B1VbYS99qi3Vuw11xmks5vTUrngaJpZM4bSlac .
I have experienced similar with only returning 1000 tags, and ultimately bringing the opc server down (WinCC... Again! I can't confirm max nodes per browse either with wincc as the server does not expose this)
How can I reproduce this use case?
browse is restricted now from node-opcua and it will provide the browse next in a next step end of the month march 2019
@biancode browse will limit the number of returned node to 1000 and will set a continuous point in the response if more than 1000 nodes exists. To get all the node , one shall call browseNext repeatedaly until continous point becomes null.
@erossignon you said it is not possible to call browseNext for now last time. Is it possible now and from which version of node-opcua, please?
on the client side, OPCUACLient#browseNext can be used since a long time and shall be available in v0.7.0. version 2.0.0 will add further enhancements and browseNext support in the server and in the client crawler.
browseNext works
needs v3.11.3 or above
fixed with v3.12.0 - but the listener itself is also limited by the server how many items to be monitored at the same server
I'm submitting an unexpected behaviour.
Current behaviour: IIoT OPC UA Browse2Listener example scenario. Connect to OPC-UA server exposing 4000 variables, Response gives 1000 variables, Listener subscribes to 1000 variables.
Expected behaviour: Connect to server exposing 4000 variables, Response gives 4000 variables, Listener subscribes to 4000 variables.
Environment: I am using just the Node-RED package and got node-opcua installed with it.
Device : Raspbian: GNU/Linux 9