are spaces supported in translateBrowsePath ? about node-opcua HOT 14 CLOSED

It's coming from 800xA

from node-opcua.

That may very well be the case. Just for completeness sake: yes, display name and browse name is the same for these nodes.

I am not really deep into OPC UA, so i can't really evaluate the stuff some device manufacturers do, but it seems to me that there are cases where browse names do include white space. For better or for worse.

from node-opcua.

Another useful thing might be that I've also tested putting ' and " around in the string, also in combination with %20 which should be the url-encoded equivalent to a space. Neither of them worked.

EDIT: I escaped the quotes using a backslash, github removes them for some reason

from node-opcua.

Hi!

Hope you are doing well, I was wondering if I could do something to help solving this issue? I'm not too familiar with with typescript but I would be glad to help. Currently I'm falling back to nodeIds but for my internship projects using the browsePaths is a pretty big must.

from node-opcua.

to be honest i have never seen spaces in a BrowseName!?
its uasually upper camelcase.

what server is it?
is it a common model (companion spec.)?
is it a custom own created model?

from node-opcua.

All BrowseNames should be upper camel case (also known as PascalCase), that is, all words written without spaces, and the first character of each word is upper case, the other characters are lower case.

https://opcconnect.opcfoundation.org/2020/09/opc-ua-modelling-best-practices/

from node-opcua.

Hi, i experienced the same issue this week.
In my case the server is created by a PLC, so it follows the PLCopen companion spec from my knowledge. The manufacturer of the device uses the device model name some of the browse names. The manufacturer does this for all its devices from my knowledge.

When i try to use translateBrowsePath there it returns an error.
For now i just browse recursively to resolve the nodes i need.

from node-opcua.

What is typically shown in UI tools is the Displayname. Here spaces are allowed.
The BrowseName on the other hand need to follow the rules @AndreasHeine posted.

from node-opcua.

it actually violates the OPC-F Moddelling best practises...

i assume wago uses the browsename like the displayname which is not according to the spec...

https://reference.opcfoundation.org/Core/Part3/v104/docs/5.2.4

A BrowseName should never be used to display the name of a Node. The DisplayName should be used instead for this purpose.

from node-opcua.

@GoetzGoerisch we need a tool to validate model compliance!? does the OPC-F Certification require model checks?

from node-opcua.

They typically do so.

from node-opcua.

Would this be something that can be fixed code-wise? As I don't have any freedom over the systems I'm listening to :D

from node-opcua.

An immediate workaround is to build the BrowsePath datastructure directly without using the makeBrowsePath helper function.

from node-opcua.

@InstantlyMoist,

The issue is not related to the "space" , in fact I confirm that <space>'s are properly handled in makeBrowsePath.

In fact, Root and Control Network are browseNames defined in a namespace that is not the default namespace. For this reason, you need to prefix the text part with the namespace index and the ':' separator.

-let browsePath = "/Objects/Root/Control Network";
+let browsePath = "/Objects/2:Root/3:Control Network";
let actualBrowsePath = makeBrowsePath("RootFolder", browsePath); 

• check the namespaceIndex with your favorite OPCUA Client
• refer to https://reference.opcfoundation.org/Core/Part4/v104/docs/A.2 for more info about the browsePath syntax.

from node-opcua.