OPCUA device protocol not working

[vachaspati_Diwevedi1 (vachaspati Diwevedi)]

What product/components do you use and which version/fix level are you on?

OPCUA device protocol , Cumulocity version 10.6.6

Is your question related to the free trial, or to a production (customer) instance?

Customer tenant

What are you trying to achieve? Please describe it in detail.

I have subscribed the OPCUA gateway service. Setup the OPCUA gateway Agent and configured the OPCUA gateway Server within tenant. All setup if working fine so far.

I have scanned all the namespaces of the OPCUA server. Now I have configured the device protocol with one namespace and enabled it. Now it suppose to create a child device for the OPCUA server and subsequent measurements but it’s not doing anything and I do not see any error in the gateway agent logs as well.

Even if I have configured one data point as measurement in the device protocol, the resource count is showing as 0.

Do you get any error messages? Please provide a full error message screenshot and log file.

no error message in the agent logs
2022-12-13 03:32:55,107 19332325 [pool-327-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:33:55,108 19392326 [pool-328-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:33:55,408 19392626 [pool-328-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:34:55,408 19452626 [pool-329-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:34:55,701 19452919 [pool-329-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:35:55,702 19512920 [pool-330-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:35:55,992 19513210 [pool-330-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:36:55,993 19573211 [pool-331-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:36:56,335 19573553 [pool-331-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:37:56,335 19633553 [pool-332-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:37:56,681 19633899 [pool-332-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:38:56,682 19693900 [pool-333-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:38:56,969 19694187 [pool-333-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:39:56,970 19754188 [pool-334-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:39:57,266 19754484 [pool-334-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:40:57,266 19814484 [pool-335-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:40:57,613 19814831 [pool-335-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:41:57,614 19874832 [pool-336-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:41:57,963 19875181 [pool-336-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:42:57,964 19935182 [pool-337-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:42:58,307 19935525 [pool-337-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032
2022-12-13 03:43:58,308 19995526 [pool-338-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Start checking for subscription update on server: 2468032
2022-12-13 03:43:58,652 19995870 [pool-338-thread-1] INFO c.c.o.c.g.s.UpdateServerSubscriptionTask - Finished checking for subscription update on server: 2468032

Have you installed all the latest fixes for the products and systems you are using?

Yes

[Marco_Stoffel]

Hi, can you please share a bit more information? E.g. show the variable configuration?

[vachaspati_Diwevedi1 (vachaspati Diwevedi)]

@Marco_Stoffel

tion

Hi @Marco_Stoffel

Below find the OPCUA Variable properties

Device protocol variable configuration -

[vachaspati_Diwevedi1 (vachaspati Diwevedi)]

I have tested the same setup with prosys OPC UA simulator everything working fine. I can see the child device and measurement but the same device protocol is not working with customer OPC UA server.

[apes (Alexander Pester)]

Hi Vachas,

have you tried this operations to analyze the device protocol a bit more:

https://cumulocity.com/guides/protocol-integration/opcua/#testing-a-device-type-against-a-node-on-an-opc-ua-server
https://cumulocity.com/guides/protocol-integration/opcua/#analyzing-the-set-of-nodes-to-which-a-device-type-can-be-applied-dry-run

if the device protocol can’t be applied, usually something is wrong with the path. What apply constraints are you using? Is the “THEGEAR” browseName your root node, can you try to add “1:THEGEAR” to your path?