# Logix Tag Simulator

**URL:** <https://forum.inductiveautomation.com/t/logix-tag-simulator/116350>\
**Category:** General Discussion\
**Created:** [July 10, 2026, 1:44pm UTC](https://forum.inductiveautomation.com/t/logix-tag-simulator/116350 "2026-07-10T13:44:24Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\
**Post date:** [July 13, 2026, 12:16pm UTC](https://forum.inductiveautomation.com/t/logix-tag-simulator/116350/14 "2026-07-13T12:16:07Z")

</div>

I solved this sorta here: [Ignition & Logix Best Practice Tips for better communications - #83 by pturmel](https://forum.inductiveautomation.com/t/ignition-logix-best-practice-tips-for-better-communications/60386/83)

Basically we have a UDT in Ignition that represents the data we want to use. The in the PLC we have a Wrapper AOI that wraps the internal AOI/Instruction/ETC... and maps the data to a PLC UDT that matches the Ignition UDT. Anything that needs to write the PLC side is done via the divert write tag actors in @pturmel toolkit.

---

_[View the full topic](https://forum.inductiveautomation.com/t/logix-tag-simulator/116350)._