Running Script on Standard Gateway Triggered by Tag Events in Remote Edge Gateway

Ignition
, ,
1

Hi everyone,

I’m working with a distributed Ignition setup where:
Edge Gateway collects data from PLCs and triggers tag events
Standard Gateway handles logic like API calls and external integrations
The Edge Gateway is connected as a remote tag provider to the Standard Gateway

Goal:

When a tag (e.g., alarm or dataset) changes on the Edge Gateway, I want to:
Detect that event (e.g., in a valueChanged script)
Trigger a Python function defined on the Standard Gateway (not Edge)
Keep all external logic centralized in the Standard Gateway

Questions:

1.Is it possible to trigger a script on the Standard Gateway from a tag event on Edge?
2.Is system.util.sendMessage() from Edge to Standard the correct/recommended approach?
3.Can this scale well if multiple Edge gateways are sending data to one Standard?

Any guidance or patterns appreciated. Thanks in advance!

2
  1. No, not directly.
  2. Yes, or system.util.sendRequest() if Edge needs a reply.
  3. Should scale OK, but not great. Will require some logic on Edge to deal with comms breakage in a custom fashion. There's no Store and Forward for messaging.
1 Like
3

Thanks, pturmel that clears it up!

Good to know system.util.sendMessage() is the right path, and I’ll look into sendRequest() as well since I may eventually want confirmation or results back.
Also appreciate the heads-up about messaging not having Store and Forward.
I hadn’t considered comms failure handling yet, so I’ll plan to add some retry or logging logic on the Edge side.

Much appreciated!