Closed ryan-ms closed 5 years ago
Hi @ryan-ms, we have seen several similar issues in our lab testing, and are looking at root causing it.
Hi @ryan-ms, I'm not sure if this is an incorrect setting in the PLC, nevertheless I think the opctwin should be able to display the address space consistently like other clients. So we would like to know a bit more about your setup: 1) what version of the opctwin are you using? 2) what are the node IDs of the items that are not displayed (just 2-3 of them)? 3) can you share with us the namespace array of the server?
Hi @cristipogacean ,
Thanks for your reply, let me provide the detail.
I used the opc twin image which I download and build from develop branch on 7/23.
Here is my image: ryan77119/azure-iiot-opc-twin-module:latest
It's a linux container running in ubuntu.
NodeId: Sensor_100_ON: "ns=3;s="Sensor_I00_ON"
Sensor_IW2_PV: "ns=3;s="Sensor_IW2_PV"
Sensor_IW2_SCALE: ""Sensor_IW2_SCALE"
The namespace array are:
Thank you very much. Looking forward your reply.
This looks like an issue in connected factory and a naming/functionality issue in the API.
Any continuation point reported by the server as result of browse is passed back to the client and client should call BrowseNext with same continuation point. However, connected factory browse controller uses only NodeBrowseAsync
, which is actually NodeBrowseFirstAsync
.
I propose to rename the original NodeBrowseAsync on the API interface to NodeBrowseFirstAsync to be in line with the business logic service API, and then add an extension method called NodeBrowseAsync which browses the entire set of references - same as the service extension.
Released in 2.5.1. It is not yet in CF but you can use the CLI to validate.
Thanks @marcschier , I will try it. But how can I know when is the CF updated? Can you leave message here while the CF updated? Thanks a lot.
Hi @marcschier ,
I still met the same issue while using latest opc twin service and module.
I've download the latest code yesterday (9/11) and follow the latest document ,Deploying Azure Industrial IoT Microservices and dependencies instructions to deploy service to Azure
and follow Deploy OPC Twin and OPC Publisher Edge Modules instruction to deploy the opc twin(mcr.microsoft.com/iotedge/opc-publisher:latest) and publisher module (mcr.microsoft.com/iotedge/opc-publisher:latest) to Linux gateway.
Then I use the opc twin react web app to discover, browse the OPC UA Server. But there is the same issue...
Like the following picture, I can see servals OPC tag in Tags node
But cannot see them in the web app.
Please use the command line interface to browse and see if the results match the other client, it should. We did not update the sample app not connected factory, both do not use continuations properly. The CLI however does.
Holen Sie sich Outlook für Androidhttps://aka.ms/ghei36
From: ryan-ms notifications@github.com Sent: Wednesday, September 11, 2019 8:25:03 PM To: Azure/Industrial-IoT Industrial-IoT@noreply.github.com Cc: Marc Schier Marc.Schier@microsoft.com; Mention mention@noreply.github.com Subject: Re: [Azure/Industrial-IoT] OPC tag not showing when browsing node in some PLC (#26)
I still met the same issue while using latest opc twin service and module.
I've download the latest code yesterday (9/11) and follow the latest document ,Deploying Azure Industrial IoT Microservices and dependencieshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FIndustrial-IoT%2Fblob%2Fmaster%2Fdocs%2Fhowto-deploy-microservices.md&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053443243&sdata=WUnK5L7eOl6Ef%2Fm3SE2mwjUp7PA7sgwGNllDQxi3ytY%3D&reserved=0 instructions to deploy service to Azure
and follow Deploy OPC Twin and OPC Publisher Edge Moduleshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FIndustrial-IoT%2Fblob%2Fmaster%2Fdocs%2Fhowto-deploy-modules.md&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053443243&sdata=LfflhGjNfeVAlz27f61P8xbxBuHuuFM6QpyPspOZqqo%3D&reserved=0 instruction to deploy the opc twin and publisher module to Linux gateway.
Then I use the opc twin react web app to discover, browse the OPC UA Server. But there is the same issue...
Like the following picture, I can see servals OPC tag in Tags node [Client]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29178018%2F64751354-6f1f5300-d54e-11e9-909a-f0687abeeff6.png&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053453201&sdata=0lVZjD%2BdnZ20NxjGpNDaRX%2BAESi%2FfqoND8bdAaF9g8c%3D&reserved=0
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FIndustrial-IoT%2Fissues%2F26%3Femail_source%3Dnotifications%26email_token%3DACVGVVQKPOY6443YYDDQEPTQJGZA7A5CNFSM4IGXOXA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6QQ3ZA%23issuecomment-530648548&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053463167&sdata=6TOQcFFWHI7T6TjX7OLar%2BwyZbK9Tz96hhACvGv7TM0%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACVGVVSFN2LKKNMLTWWY4U3QJGZA7ANCNFSM4IGXOXAQ&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053463167&sdata=bOiBdHxorKXwTZIKKdiHe%2Fcoa05SbG8a7T7ugas4zZM%3D&reserved=0.
Hi @marcschier ,
I still met the same issue while using latest opc twin service and module.
I've download the latest code yesterday (9/11) and follow the latest document ,Deploying Azure Industrial IoT Microservices and dependencies instructions to deploy service to Azure
and follow Deploy OPC Twin and OPC Publisher Edge Modules instruction to deploy the opc twin(mcr.microsoft.com/iotedge/opc-publisher:latest) and publisher module (mcr.microsoft.com/iotedge/opc-publisher:latest) to Linux gateway.
Then I use the opc twin react web app to discover, browse the OPC UA Server. But there is the same issue...
Like the following picture, I can see servals OPC tag in Tags node
But cannot see them in the web app.
I think that's a different issue from original issue. I just test the Siemens PLC which I tested before, and notice the issue is resolved and works very well, thank you.
And for the new issue in other PLC seems like caused by bad nodeId error without error handler. Do you have any idea?
Please use the command line interface to browse and see if the results match the other client, it should. We did not update the sample app not connected factory, both do not use continuations properly. The CLI however does. Holen Sie sich Outlook für Androidhttps://aka.ms/ghei36 … ____ From: ryan-ms notifications@github.com Sent: Wednesday, September 11, 2019 8:25:03 PM To: Azure/Industrial-IoT Industrial-IoT@noreply.github.com Cc: Marc Schier Marc.Schier@microsoft.com; Mention mention@noreply.github.com Subject: Re: [Azure/Industrial-IoT] OPC tag not showing when browsing node in some PLC (#26) Hi @marcschierhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmarcschier&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053433286&sdata=5vlAwUVKZvzcPum9kl%2Ff8dqQLyji95TqcxdJfYgLplg%3D&reserved=0 , I still met the same issue while using latest opc twin service and module. I've download the latest code yesterday (9/11) and follow the latest document ,Deploying Azure Industrial IoT Microservices and dependencieshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FIndustrial-IoT%2Fblob%2Fmaster%2Fdocs%2Fhowto-deploy-microservices.md&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053443243&sdata=WUnK5L7eOl6Ef%2Fm3SE2mwjUp7PA7sgwGNllDQxi3ytY%3D&reserved=0 instructions to deploy service to Azure and follow Deploy OPC Twin and OPC Publisher Edge Moduleshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FIndustrial-IoT%2Fblob%2Fmaster%2Fdocs%2Fhowto-deploy-modules.md&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053443243&sdata=LfflhGjNfeVAlz27f61P8xbxBuHuuFM6QpyPspOZqqo%3D&reserved=0 instruction to deploy the opc twin and publisher module to Linux gateway. Then I use the opc twin react web app to discover, browse the OPC UA Server. But there is the same issue... Like the following picture, I can see servals OPC tag in Tags node [Client]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29178018%2F64751354-6f1f5300-d54e-11e9-909a-f0687abeeff6.png&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053453201&sdata=0lVZjD%2BdnZ20NxjGpNDaRX%2BAESi%2FfqoND8bdAaF9g8c%3D&reserved=0 But cannot see them in the web app. [web]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29178018%2F64751522-ee148b80-d54e-11e9-822f-61de3a6a8a60.png&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053453201&sdata=EkMeulJ1kZ9%2F97Vy%2BQR%2BeW2h64XmNCXSqCyYOixad14%3D&reserved=0 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FIndustrial-IoT%2Fissues%2F26%3Femail_source%3Dnotifications%26email_token%3DACVGVVQKPOY6443YYDDQEPTQJGZA7A5CNFSM4IGXOXA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6QQ3ZA%23issuecomment-530648548&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053463167&sdata=6TOQcFFWHI7T6TjX7OLar%2BwyZbK9Tz96hhACvGv7TM0%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACVGVVSFN2LKKNMLTWWY4U3QJGZA7ANCNFSM4IGXOXAQ&data=02%7C01%7CMarc.Schier%40microsoft.com%7C0c1af954a51d4b9768a708d73730cd86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038555053463167&sdata=bOiBdHxorKXwTZIKKdiHe%2Fcoa05SbG8a7T7ugas4zZM%3D&reserved=0.
Thanks, Let me try the CLI first, thank you.
I built the OPC Twin module from
develop
branch, and use Connected factory to test the discover, read, write.And it work fine on my Siemens S7-1500 PLC. But when I changed to another Siemens S7-1500 PLC (but with different CPU module).
It cannot shows all tag when I expanded the node. Like picture below, it only shows "icon"
But when I use other OPC client ( OPC Foundation Sample Client )to connect to PLC and browse the OPC node. it can successfully show all tags.
But before showing all the tag, it prompt a window with "more reference exists" message when I clicked "memory" which not happened whenI connected to other OPC UA server.
There are sightly different on CPU module in PLC, like table below.
Not sure is the CPU matter or the incorrect setting in PLC? Any idea?