# Connecting with Ignition OPC UA server with third-party OPC UA client **URL:** \ **Category:** Ignition\ **Created:** [July 5, 2017, 11:45am UTC](https://forum.inductiveautomation.com/t/connecting-with-ignition-opc-ua-server-with-third-party-opc-ua-client/14691 "2017-07-05T11:45:28Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rudy.bekema](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@rudy.bekema](https://forum.inductiveautomation.com/u/rudy.bekema)\ **Post date:** [July 5, 2017, 11:45am UTC](https://forum.inductiveautomation.com/t/connecting-with-ignition-opc-ua-server-with-third-party-opc-ua-client/14691/1 "2017-07-05T11:45:29Z")
Hello there, I am currently struggling with connecting my C#/.NET application to the Ignition OPC UA server. The setup of the server, PLC device is: ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/23dcbfd8bf4e82c1d98a0ed2a35291841f654661.png) Using the Quick client i have tested the connection with a tag (see image above) Now all I need is the “path” to the tag that needs to be set into my application. Currently what I can think of is the following: “opc.tcp://10.40.120.205:49320/iaopcua/None/[Device1]PROGRAM:SFX0908\_HMI\_01.L\_MACHINENR” However the path above is not valid. What is,based upon the configuration of the server and plc device that i have posted above, the correct path to subscribe to an item in the Ignition OPC server? The application is already working correctly with a Siemens OPC UA server (with a Siemens PLC), now I have to add the possibility to connect to a different OPC UA server that is connected to an AllenBradley PLC. Anyone that can give me the correct path or something else that I am missing? Thanks in advance, Sorry for the long picture, i am only allowed to post one image apparenty… Rudy ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 5, 2017, 12:35pm UTC](https://forum.inductiveautomation.com/t/connecting-with-ignition-opc-ua-server-with-third-party-opc-ua-client/14691/2 "2017-07-05T12:35:36Z")
OPC UA works with NodeIds, so whatever this path might be is specific to your software. The NodeId in the Ignition OPC UA server looks like it it’s `ns=1;[Device1]PROGRAM:SFX0908_HMI_01.L_MACHINENR` in this case. Maybe you need to include the “ns=1” in your path. ---
**Author:** ![rudy.bekema](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@rudy.bekema](https://forum.inductiveautomation.com/u/rudy.bekema)\ **Post date:** [July 5, 2017, 1:48pm UTC](https://forum.inductiveautomation.com/t/connecting-with-ignition-opc-ua-server-with-third-party-opc-ua-client/14691/3 "2017-07-05T13:48:00Z")
Dear Kevin, Thanks for your response! ns=1;s=[Device1]PROGRAM:SFX0908\_HMI\_01.L\_MACHINENR is what is currently used to create a new item to be monitored by the opc ua client. When this is created, an exception is triggered: creation of data monitored item failed… ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 5, 2017, 1:58pm UTC](https://forum.inductiveautomation.com/t/connecting-with-ignition-opc-ua-server-with-third-party-opc-ua-client/14691/4 "2017-07-05T13:58:00Z")
There should be a StatusCode indicating the failure to go with that message… NodeIds are case-sensitive as well… so you might try using the same case as in your screenshot. ---
**Author:** ![rudy.bekema](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@rudy.bekema](https://forum.inductiveautomation.com/u/rudy.bekema)\ **Post date:** [July 5, 2017, 3:18pm UTC](https://forum.inductiveautomation.com/t/connecting-with-ignition-opc-ua-server-with-third-party-opc-ua-client/14691/5 "2017-07-05T15:18:47Z")
The StatusCode is 'BadNodeIdUnknown". For the connection with the Siemens OPC ua server I only had to modify the node number to 6 and use the following path: “opc.tcp://FSE-HMI:55105/PLC.FS4xx.DB\_SFX0908\_HMI\_Part\_2\_1.L\_MachineNr” For the connection with KEPServer EX server I use node 2 and the path: “opc.tcp://FSE-HMI:49321/TestPLC.Device1.PROGRAM:SFX0908\_HMI\_01.L\_MACHINENR” and both of those connections are running fine without any other modifications to the application. I matched the case from the quick client and suddenly the first item to be monitored was no longer triggering the exception but the second item is. I will have to convert some more tags to be sure but for now it looks that the case-sensitivity is the key to my solution… Thank you for your remark about the case-sensitivity! When I have modified my tags I will post the result. ---
**Author:** ![rudy.bekema](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@rudy.bekema](https://forum.inductiveautomation.com/u/rudy.bekema)\ **Post date:** [July 6, 2017, 1:42pm UTC](https://forum.inductiveautomation.com/t/connecting-with-ignition-opc-ua-server-with-third-party-opc-ua-client/14691/6 "2017-07-06T13:42:37Z")
Problem is solved, it turnes out the case-sensitivity was the problem. Kevin thank you