Error: Cannot find dataType Definition ! with nodeId =ns=3;i=3400

[jadevicpavel]

Hello, I have some trubles with OPC UA browser. I created script that loads all objects of my custom unit, basically I input my custom path and broweser returns an object payload with all children of my custom object. I tried to writed everything dynamically so I could reuse my script on other projects. When I did so and changed ip, OPC UA broweser started to trow new error (like 10000+ times) and it becomes much slower.

Error names: populate_data_type_manager_104:38 Error: Cannot find dataType Definition ! with nodeId =ns=3;i=3400 populate_data_type_manager_104:167 err= Error

I include pictures of both old working project and new error project. Even thoe it trows multiple errors OPC UA broweser returns payload with all children but as I said before its much slower and problem is I upload to to web and speed is esential for me. We are talking about 30 sec+ per unit and there are over 80 units. another problem is that old project was developed in Tiaportal16 for PLC cpu 1518 and new poject was developed in Tiaportal 17. I havent noticed any changes in properties but still I think its worth mentioning.

Versions: node-red = 2.2.2 opc-ua = 0.2.260

I've tried to upgrade to newer versions and problem remained.

after few hours of testing I created test scripts that show what excatly bothers me. It's set up in the way that I compare 2 differente results of OPC browser, all other functions are same to eliminate any possible mistakes made by me like typos etc.

• first picture describes how shloud it work
• Second picture returns falty resault, even thoe opc broweser found all of my custom objects and their childern, it didn't return values hidden inside value object as it should compare to first picture
• and lastly I looped in that empty object and expected no answer but somehow it found 3 keys inside, unfortenately I dont think I have any use for it so its basically empty

[mikakaraila]

There has been changes on node-opcua: https://github.com/node-opcua/node-opcua/issues/1174

We have to wait until those are solved.

[jadevicpavel]

@mikakaraila Thank you for fast replay. I did some testing on my own and come to interesting conclusion, I think main problem lies in Tiaportal verision because project developed in Tiaportal 16 works well after upgrading this same project to Tiaportal 17 it starts to throw errors mantion both by me and issue you refrenced.

I work in company that has direct connection to Siemens support and we can provide direct connection between you and them to help resolve this problem directly with source.

[mikakaraila]

I expect @erossignon could help also. Have you checked namespace index is correct?

[jadevicpavel]

There were no namaspace changes as I understand because we upgraded working project to tiaportal17 and unleass upgrade it self changed namaespace, there should not be problem. In both cases path ns=3;i=3400 leads to SimaticStructures.

[mikakaraila]

Please test, I updated dependency node-opcua v2.73.0 that contains fixes related to this.

[mikakaraila]

New node-opcua v2.77.0 contains fixes to entension object.

https://github.com/node-opcua/node-opcua/releases

[jadevicpavel]

I've updated to last version and tried to run script. Unfortunatelly for me it didn't resolve the problem. Except error with nodeId =ns3;i=3400 there are 5 new nodeId errors: nodeId =ns=2;i=6522 nodeId =ns=2;i=6525 nodeId =ns=3;i=3500 nodeId =ns=2;i=15888 nodeId =ns=2;i=15889

And same problem remaines OPC broweser can't find schemas in SimuticStructures even thoe they are there but isntead of error message, now there is notation fix me!

@mikakaraila

[mikakaraila]

Ok, perhaps @erossignon can find out reason why data type manager cannot handle those.

There is support for v1.03 and v1.04 but older ones can be still problem or Siemens has a bit different implemention.

[cdac2019]

@mikakaraila @jadevicpavel @erossignon currently I ave updated latest pkg showing such type of issues appreciate your support

[mikakaraila]

This is inside node-opcua, there is some special Siemens datatype that cannot be converted.

If you can find it report it to this issue: https://github.com/node-opcua/node-opcua/issues/1174 For some reason it seems to be closed??