# Using Ignition as OPC-DA server to PI? OPC COMM DA functionality **URL:** \ **Category:** Ignition\ **Created:** [March 7, 2024, 6:13pm UTC](https://forum.inductiveautomation.com/t/using-ignition-as-opc-da-server-to-pi-opc-comm-da-functionality/86987 "2024-03-07T18:13:09Z")\ **Posts on this page:** 1\ **Showing post:** 13
**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:** [March 27, 2024, 5:01pm UTC](https://forum.inductiveautomation.com/t/using-ignition-as-opc-da-server-to-pi-opc-comm-da-functionality/86987/13 "2024-03-27T17:01:51Z")
If they need a hint about what's wrong I've explained a little bit elsewhere: > [@OPC-UA Client connection issues](https://forum.inductiveautomation.com/t/opc-ua-client-connection-issues/79799/2): > > You may need to point the software at the discovery endpoint instead: opc.tcp://host:62541/discovery. This is at least what you would need to do with UaExpert via its "custom discovery" flow. The server has two endpoints: one for discovery, one for sessions. The discovery endpoint is unsecured, and the session endpoint only allows secured connections by default. You're pointing your software at the session endpoint, and despite configuring it to use security, it's probably trying to start with … --- _[View the full topic](https://forum.inductiveautomation.com/t/using-ignition-as-opc-da-server-to-pi-opc-comm-da-functionality/86987)._