cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

OPCUA: TranslateBrowsePathToNodeIds (Specification Part 4) fails

OPCUA: TranslateBrowsePathToNodeIds (Specification Part 4) fails

leonberger-m
Established Member

Hello, 

to identify the correct NodeId of an OPC-UA BrowsePath the OPC UA service called "TranslateBrowsePathsToNodeIds" (described in the OPC-UA specifiation part4) should be used. 

The OPC UA structure + variable "mamode" have been created within the KVD nodes.json
objects/Datalayer/test/mamode 

leonbergerm_0-1687501031263.png

leonbergerm_3-1687501350676.png

 

Starting from the root folder browsing and translation the path for 0bjects/8:Datalayer succeeds. 
(Therefore a small piece of software of the OPC UA toolkit is used) 
As a result the target ns=8, i=2000 is shown. 

leonbergerm_2-1687501224548.png

 

leonbergerm_1-1687501213813.png

But if we try to translate the path created within the KVD configuration (Objects/Datalayer/test/mamode) to retrieve the NodeId of this path the command fails with an error message provided by the OPC UA server within the CtrlX core. 

leonbergerm_4-1687501462597.png

leonbergerm_5-1687501576947.png

The error message: StatusCode=Bad_NoMatch (0x806F0000) "The requested operation has no match to return." is shown for every folder/structure except of Objects/8:Datalayer.

Spelling and NamespaceIndex are correct and have been verified several times. But it seems that something goes wrong underneath the DataLayer which avoids a correct execution/translation using the "TranslateBrowsePathToNodeIds". 

Does anyone have any experience using this OPC UA specified command? 
Thanks for your help.

Markus

 

 

 

2 REPLIES 2

NoRisk4Project
Long-established Member

Hello Markus,

we have a bug in our implementation of the service "TranslateBrowsePathToNodeIds", therefore it's actual not working for variables. A bugfix is currently not prioritized.

Do you need this function for your certain/actual project?

greetings

Christian

Hello Christian, 

meanwhile we got a workaround from our ME-system partner. So it's not a very urgent situation since it works with the workaround. But in general it would be helpful to fix this issue even if there is no big priority. 

Thanks for your support, 
Markus  

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist