# Connecting Ignition to Vendor Device/OPC Client

**URL:** <https://forum.inductiveautomation.com/t/connecting-ignition-to-vendor-device-opc-client/116904>\
**Category:** Ignition\
**Tags:** opcua\
**Created:** [August 26, 2026, 3:20pm UTC](https://forum.inductiveautomation.com/t/connecting-ignition-to-vendor-device-opc-client/116904 "2026-08-26T15:20:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Everett\_Cass](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/everett_cass/32/86983_2.png) [@Everett\_Cass](https://forum.inductiveautomation.com/u/Everett_Cass)\
**Post date:** [August 26, 2026, 3:20pm UTC](https://forum.inductiveautomation.com/t/connecting-ignition-to-vendor-device-opc-client/116904/1 "2026-08-26T15:20:36Z")

</div>

Okay I have this Vendor Device from FOSS/ProcessScan2. It has an option to connect to an OPC UA Server, from my understanding from that server its expecting to have pre-defined opc paths/string node ID's. The purpose of this being to transfer data from the FOSS to ignition. Is it possible to directly connect this client to ignition and read those tags? I have adjusted the OPC Server settings on ignition and it says connected, but I'm not sure how I would read or map these specific tags. I'm running a simulator and ignition on my local host

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/e/ae333bd0b020e9741c5f7b16d08f2c87990ede49.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/6/c6c55e3ccbbdf11666495bb106fb4e6b5b9df250.png)

---

<div class="post-metadata">

**Author:** ![Everett\_Cass](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/everett_cass/32/86983_2.png) [@Everett\_Cass](https://forum.inductiveautomation.com/u/Everett_Cass)\
**Post date:** [September 2, 2026, 8:47pm UTC](https://forum.inductiveautomation.com/t/connecting-ignition-to-vendor-device-opc-client/116904/2 "2026-09-02T20:47:01Z")

</div>

Okay for anyone with something similar in the future, the trick was to create a Programmable Device Simulator (Under Devices), and make the OPC paths match

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/6/76c11bf12e982d8fbf4253200c50075d2b1c30e8.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/3/032b69158f8557d5db5c3e09e6c8fb7e912ba458.png)