# Remote stack light triggering off tag values in kepware

**URL:** <https://forum.inductiveautomation.com/t/remote-stack-light-triggering-off-tag-values-in-kepware/103699>\
**Category:** General Discussion\
**Created:** [March 14, 2025, 12:58pm UTC](https://forum.inductiveautomation.com/t/remote-stack-light-triggering-off-tag-values-in-kepware/103699 "2025-03-14T12:58:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![a-vanmeter](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@a-vanmeter](https://forum.inductiveautomation.com/u/a-vanmeter)\
**Post date:** [March 14, 2025, 12:58pm UTC](https://forum.inductiveautomation.com/t/remote-stack-light-triggering-off-tag-values-in-kepware/103699/1 "2025-03-14T12:58:39Z")

</div>

We currently have a system where machines in need to be monitored by personnel in different locations. When the machine in question alarms, they cannot hear the alarm or see the stack light. The alarms do translate into Ignition already, but it just displays on a monitor.

Is there a stack light that can be triggered by tags using kepware and ignition?

---

<div class="post-metadata">

**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\
**Post date:** [March 14, 2025, 1:30pm UTC](https://forum.inductiveautomation.com/t/remote-stack-light-triggering-off-tag-values-in-kepware/103699/2 "2025-03-14T13:30:33Z")

</div>

There's a few different ways to handle something like that.

If the monitor is Vision based, you could have a PC-based indicator light like a busylight or something similar and use Vision to control that by running code on the local PC.

You could also have some remote I/O controlled over the network by a PLC or by Ignition directly if the protocol is supported.  
Banner has a wireless version of the above (DXM gateway and TL70 stack lights), others probably do as well.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 14, 2025, 3:10pm UTC](https://forum.inductiveautomation.com/t/remote-stack-light-triggering-off-tag-values-in-kepware/103699/3 "2025-03-14T15:10:02Z")

</div>

There quite a few I/O-Link master field devices that support OPC-UA for direct connection to Ignition, and many I/O-Link stack lights you can use with those. Very flexible.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 14, 2025, 3:23pm UTC](https://forum.inductiveautomation.com/t/remote-stack-light-triggering-off-tag-values-in-kepware/103699/4 "2025-03-14T15:23:35Z")

</div>

Tip: just a note on terminology. A **trigger** is usually a brief action to turn something on or off. e.g., Turning a car's ignition key to the Start position starts the engine running but releasing it doesn't turn it off. You probably mean to **control** the stack lights directly. If the relevant tag is True then light is on, etc. Getting terminology right can avoid miscommunication and is worth doing.