How things work - history splitter - can edge remote history provider be shared with the history splitter?

I got history splitter working and storing both locally and to remote history provider over gateway network.
I had also separate history provider for storing data from Ignition Edge.

When i tried to use Edge history provider in History splitter settings as one of connections the storing did not work until i create separate local database connection and automatically history provider.

So fundamental question is when using history provider for edge remote sych this history provider cannot be used in the history splitter? Is there any fundamental reasoning behind that?


I'm having a little trouble understanding.

Are you syncing the Edge node's history to a remote history provider on a standard gateway? Are you then using a history splitter to take the history from the remote tag provider, and split it into a local database, and a remote database? Please give greater detail on what and where connections are being made

If you can provide an illustration of your architecture to give some more context that will be extremely helpful.

1 Like

You understood it well.
I was trying to use the same database connection from gateway 1 to the SQL database for both data synch and history splitter (local destination). This did not work until i created separate (second) database connection to use for the history splitter and point to the local sql database. I try to understand how things work and wonder if sharing the same connection is not possible?


What kind of database are you connecting to (Internal SQLite, MySQL, MSSQL, etc)? Did you have any database connections set up when the history splitter wasn't working?

Can you share screenshots of the configurations for your tag historian and history splitter?

The two sources for the tag history splitter can be targeted towards historical providers that are configured on the same gateway. Remote data sync (configured on the edge gateway) will target a historical provider that exists on a remote gateway.

Since the splitter exists as a historical provider, you would configure data sync to target the splitter provider on the edge gateway, and then have the splitter target Gateway 1 database and the remote historical provider pointing to Gateway 2.

1 Like

@Kurt.Larson @Bryson_Prince
it works and the subject is well understood - many thanks