Hello All,
I'm curious about the Edge Panel in Ignition. From what I've gathered online, it seems to be a standalone Ignition gateway running on a device, without direct DB connectivity, but it can maintain 35 days of data. Is the inbuilt MySQL database being referenced here?
If I need to push data from the edge device to a centralized gateway, is using the Gateway Network connection the only option?
It's not MySQL, I think it uses the Internal DB.
MQTT is another option.
Noted Thanks !,
But even if it an internal DB , Will it work as RDB?
because i really don't want to save any process data from the tag . I need the user input to be saved in different DB schemas
Not possible with Edge.
Only possibility is storing a small amount of text in a string memory tag.
As @Matrix_Engineering stated, an explicit tradeoff in Edge is the much cheaper licensing in exchange for no gateway scripting and direct database access.
For posterity, the edge historian does use SQLite, but not the same file as the internal database that stores Ignition's own config.
(And the gateway scripting is included in all new licenses.)
I would also mention that, with any UI option, you only get two live clients (one local, one remote for Vision).
I have a project with a central gateway and 5 edge panels.
Normally, all 5 edge panels just run as clients of the central gateway.
In the event of a network issue, the edge panels have direct connection to their local "area" - with a fallback project.
The central gateway and all of the edge gateways run the same project and there is a gateway tag on each gateway that determines the "area" from the IP. Screens on the edge fallback projects are limited based on the area. You end up with 2 connections to every tag (one from the central and one from the edge). This removes the dependency on gateways in either direction.
For instance, if the central gateway had a remote tag provider from the edge panels and one of the edge panels went down (or connection was lost), you now have no visibility or control into that area.
Or, if the edge panels retrieved data from the central gateway and the central gateway went down (or connection was lost), you now lose that redundancy of having the edge panel be the local controller, unless you create and maintain an entirely independent project for each edge panel.
You now have redundancy at the local area level and only one project to maintain.