I have a Main Gateway talking to a Edge Device Gateway.
A script to turn a tag off resides on the Edge Device. It is running as a Gateways Script.
On my Main Gateway I have a reference tag to the Edge Device. When I turn the tag on, the Edge Device Script should turn it off after 2 seconds. Handshaking signal.
This only works when I have the Edge Device Designer open. It is like the Gateway script is not running on the Edge Device. Not sure what is preventing it from running. Any thoughts?
Opto22 with Version: 8.1.21
Edge Compute is Active on License:
Discovered the end user was closing the session. Problem solved.
I'm confused. What was running in a session? (Gateway scripts run regardless of client sessions.)
2 Likes
Should clarify. I had some session props running scripts. For example, one was running a historical tag binding with a script transform. It was not updating. I didn't realize the issue until I found the edge device was not running a perspective session. It appeared this was the reason none of the scripts were updating.
A couple things I couldn't figure out. Related to Gateway Scripts. The version of Ignition is not the latest. It's on an Opto22. Everyone was working great with a designer open. As soon as I closed it, the scripts stopped working. I assume any gateway scripts would run regardless of a perspective session active. This is an edge version of Ignition.
-
Tag change script was not working. I have a Gateway that turns a tag on at an edge device. The edge device refreshes some data. The tag turns itself off using a tag change script on the tag. This didn't work when the edge device wasn't running a perspective session.
-
Gateway Timer script not working. I tried running the same code on a Gateway script. Ran into the same issue. The tag comes on, if it's True... Turn the state to False.
You'll have to share your code. There may be a bug in that old version, but not enough information.
