# Ignition Edge data logging to Ignition

**URL:** <https://forum.inductiveautomation.com/t/ignition-edge-data-logging-to-ignition/15452>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [September 22, 2017, 11:55pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-data-logging-to-ignition/15452 "2017-09-22T23:55:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tbackus](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tbackus/32/5091_2.png) [@tbackus](https://forum.inductiveautomation.com/u/tbackus)\
**Post date:** [September 22, 2017, 11:55pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-data-logging-to-ignition/15452/1 "2017-09-22T23:55:08Z")

</div>

Ok, so I know Edge has a limit of 500 tags and history of 1 week. I am thinking of an application where I could use Edge to do much quicker polling from a PLC, but eventually I need to get that data into Ignition and or SQL. I also know you cannot add SQL bridge to Edge.

So could I connect to Edge as if it were an OPC server from Ignition? Or are there other mechanisms to grab that data?

---

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [September 26, 2017, 10:41am UTC](https://forum.inductiveautomation.com/t/ignition-edge-data-logging-to-ignition/15452/2 "2017-09-26T10:41:16Z")

</div>

Disclaimer: we haven’t done anything with Ignition Edge in production yet.

But you should probably check out the difference between “Edge Panel” and “Edge Enterprise”. See [https://inductiveautomation.com/whats-new-ignition-edge](https://inductiveautomation.com/whats-new-ignition-edge)

On “Edge Enterprise”, the edge device connects with a regular gateway, and can sync data using the store-and-forward as usual in Ignition. So it doesn’t act as a plain OPC server, but is tightly integrated.

---

<div class="post-metadata">

**Author:** ![Koen](https://avatars.discourse-cdn.com/v4/letter/k/a9a28c/32.png) [@Koen](https://forum.inductiveautomation.com/u/Koen)\
**Post date:** [October 19, 2017, 12:46am UTC](https://forum.inductiveautomation.com/t/ignition-edge-data-logging-to-ignition/15452/3 "2017-10-19T00:46:46Z")

</div>

We’re working on that problem at the moment.

For normal real-time tags, we simply enable history and set the Edge gateway up to do Tag History Sync with our central Ignition server.

Because we have unreliable 3G connections between Edge and Server, this is our preferred approach since it uses the store and forward engine. It also avoids constant polling between our Server and Edge, which is bad for our bandwith.

On our server we create expression tags that mimic the tags in Edge, and they run a script that gets the latest value out of the history provider on our Server.

The problem we’re having at the moment is for discrete data. For example somebody filling out a form on the Edge project and hitting save. We could push that through the historian approach, but retrieving a distinct dataset from the historian is proving to be a challenge.

---

<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:** [October 19, 2017, 12:59pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-data-logging-to-ignition/15452/4 "2017-10-19T12:59:00Z")

</div>

> [@Koen](#):
>
> The problem we're having at the moment is for discrete data. For example somebody filling out a form on the Edge project and hitting save. We could push that through the historian approach, but retrieving a distinct dataset from the historian is proving to be a challenge.

Look at the `remoteServers` parameter to [system.util.sendMessage()](https://docs.inductiveautomation.com/display/DOC79/system.util.sendMessage). Should enable what you need.

---

<div class="post-metadata">

**Author:** ![Koen](https://avatars.discourse-cdn.com/v4/letter/k/a9a28c/32.png) [@Koen](https://forum.inductiveautomation.com/u/Koen)\
**Post date:** [October 21, 2017, 2:05am UTC](https://forum.inductiveautomation.com/t/ignition-edge-data-logging-to-ignition/15452/5 "2017-10-21T02:05:36Z")

</div>

Hi pturmel,

Many thanks. That’s exactly what we ended up using. More specifically the utility.sendRequestAsync or whatever its exact name.

As for store and forward, we built in a fault handler if the remote gateway doesn’t throw a satisfactory confirmation back, we just keep the payload in cache and try again later.

My team impressed me with sussing all of this out whilst I’m roaming the forum. 🤓

---

<div class="post-metadata">

**Author:** ![astraea.leary](https://avatars.discourse-cdn.com/v4/letter/a/ecd19e/32.png) [@astraea.leary](https://forum.inductiveautomation.com/u/astraea.leary)\
**Post date:** [May 23, 2018, 4:10pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-data-logging-to-ignition/15452/6 "2018-05-23T16:10:28Z")

</div>

How were you able to get he main gateway and the edge gateway to connect? Not having any luck setting up a gateway network connection trying to achieve a similar solution.
