You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing firstname.lastname@example.org.
We are experiencing playback issues from our video hosting provider. Please check back shortly.
Learn how to provide realtime tag values through a database table using transaction groups.
Video recorded using: Ignition 7.9
Transcript(open in window)
[00:00] In addition to storing history, Transaction Groups can be used to write the current values of tags to a database in real time. This can be a great way to share real-time values with other systems external to Ignition, or to other Ignition Gateways on different machines. As long as different systems have access to the same database, they can all see the same values. So, for example, if we wanted to store the values of a Tank into a database in real time, we can create a New Standard Group, drag our tags into the Group, configure the table name, in this case, I'll call it Table tanks, and set the group to update the first or last row. If I Enable a Group, we'll see that every time the Group executes, the values are updated in the database. If we wanted to go a step further, and store values for multiple Tanks, we could alter the database table to include an ID for the Tank number. We could insert a couple of rows with new IDs, and now we could create additional groups that targeted those rows. So, here in our existing Group, we'll call this one Tank One, and we'll configure key/value pair to target our new column. We can create additional Groups for the other Tanks. If we start all of these Groups, we can now see that each of the rows for the corresponding IDs is being updated. Both the Standard Group and the Block Group can be used to store real-time values into a table. It's worth noting that the Group takes care of noticing which values specifically have changed, and only writes those values to the database, reducing overhead. Additionally, the Group will look at the database table, and if a value is changed in the database, it will update it according to the Group's rules. By default, the setting of OPC to DB means that the Group's value will override the database value.