Good Morning, I have tried to create an example of an OPCUA method using an AXC2152 (2021.0.0 LTS) as per the instructions on the following Github page: https://github.com/PLCnext/OpcUaMethodsGitHub - PLCnext/OpcUaMethods: Describes the basic steps for creating an OPC UA method for a PLCnext Control device. · GitHub However when I try to call the method in UA expert - I get the error “bad call” Looking in my ouput.log file I see the following error: 09.03.21 10:51:08.061 Arp.Services.OpcUAServer.Internal.InformationModel.Xml.NodeManager ERROR - No extension data found So with error, where should I start looking for the fault? My test was a very simple one (the FB just adds 3 number (inputs) and provides the average). I have my extension configured as per attached images and the exported XML is in my /opt/plcnext/projects/Default/Services/OpcUA/NodeSets directory. Any help would be appreciated, thank you. Andy
Fixed it after reading the PLC Info centre article: OPC UA Info model (Info Centre) It seems the xml file must be called NodeSet.xml, which if you just export out of UA modeller, it won’t be. UA modeller gives it the same name as the project. I had to rename the xml and then copy it to the correct directory in the controller. This was not explicitly mentioned in the Github post as far as I can see.
Hi Andy, Thanks for the feedback on the tutorial - you can also raise these types of issues on the Issues page of the Github repo, if you want. I don’t think it is necessary for the file to be names NodeSet.xml - I am currently using OPC UA methods with a single file called “mymodel.xml” (in the /opt/plcnext/projects/Default/Services/OpcUA/NodeSets directory), and it is working fine. Perhaps there was a limitation on earlier versions of firmware? I am currently running firmware version 2021.0.3 on an AXC F 2152, but it should work with all 2021.0.x versions (at least). If the file name was not the problem - and I don’t think it was - then I am not sure what the problem was. Perhaps the Extension text was added to the wrong node in UaModeler? ~ Martin.
Martin, It gets stranger. I’ve renamed the file back to it’s original name. And it still works (I did remember to reboot the 2152 just in case). So I have no idea why it didn’t work originally. I’ll keep working with it to see if I can break it again 
Thank you for the support
No worries. One thing I am not sure about - the Github tutorial does not say that you should “compile” the project in UaModeler before exporting the XML file. At some stage I should check if this makes a difference to the content of the XML file, but if someone knows if a “compile” step is necessary, then feel free to let us know. So perhaps it was a missing “compile” step that caused the original problem?
After a little more investigation, I don’t think that “compile” is necessary. I can reproduce that error message in the Output.log file by removing the “Extension” text from the method in UaModeler, so I suspect that this may have been the cause of the original problem.
Martin, Thanks for the update. I did actually check the Nodeset.xml file when the problem first manifested itself and the extension was in the xml - now I’m not so much of an expert to say if the xml was correct, but the extension was definitely listed in the exported xml. I’m more than happy to admit I probably changed something to get it working, or did something wrong in the first pIace, I just wish I knew what it was. I’ve now started on the next step and attempted to integrate an external information model into the controller. To remove any potential issues I have upgraded the controller FW to 2021.0.3 LTS just incase. I have then followed the steps in the PLC next info centre https://www.plcnext.help/te/Service_Components/OPC_UA_Server/OPC_UA_integrate_external_information_models.htm and added the PA_DIM model to the controller and this works fine. So it must of just been me Thanks again