![inductive automation ignition string escaping inductive automation ignition string escaping](https://www.inductiveautomation.com/blog/sites/default/files/2020-04/Resources-Featured_0.jpg)
Additionally, we specified the table name (into which the data will be logged) as “ Dream Report_data_log”. In the example below, we created a transaction group named “ Logging Group”, selected a set of tags to include in that group, and set the storage rate to be every 10 seconds. Transaction Groups are created in Ignition Designer:
![inductive automation ignition string escaping inductive automation ignition string escaping](https://www.industrialnetworking.com/Inductive-Automation-Ignition-Edge-LG.jpg)
Note: For more information configuring Ignition data logging, please refer to the Ignition product documentation. We will reference this view from Dream Report when creating reports: When we query the v_ignitiondata view, for instance, we see data nicely displayed for reporting. We actually need to create two views – one to display the numeric data (integer, float and discrete data points, and one for string tags.) The two views are scripted at follows, but please note that the syntax will vary slightly from one database package to another:įrom_unixtime((`d`.`t_stamp` / 1000)) AS `DateTime`, This table separate table will need to be joined with the sqlth_te table to cross-reference the tag ID’s with the actual tagnames:įortunately, we can create a SQL “view” to organize the data into a human-readable form.
![inductive automation ignition string escaping inductive automation ignition string escaping](https://aws1.discourse-cdn.com/business4/uploads/inductiveautomation/original/2X/7/7912d4f6d0a234694b3afe90bed639ed67251b0f.png)
The downside to the data partitioning is that from reporting standpoint, it is difficult to know which table name(s) to query. From a trending (or query) efficiency standpoint, smaller tables of data can be queried, allowing for faster data retrieval. What this means is that every month, a new table will be created in the SQL database, and the tag history will be logged to that month’s table. The default data partition length is set for 1 Month. Then, under the “Tags – History” configuration, you can specify how the data is “partitioned” – i.e., the mechanism by which new tables are created periodically in which the data will be logged: In the Ignition configuration environment, the project database is configured by creating a connection to a specific database, on a specific database platform (MySQL, MS SQL Server, etc.) Dream Report can access either of these data table types, but with slightly different approaches. Another method is to create “Transaction” groups in Ignition Designer, where you select the items/tags to be logged, storage rate, and the specific SQL table into which the data will be logged. One of the methods is to simply select tags to be historized for trending, and they will be logged to a set of “generic” tables in the project’s database. Ignition provides a few different ways to log process data into SQL database. We’ve created the following information to help you configure Ignition for use with Dream Report. Dream Report is a recommended solution for Inductive Automation’s Ignition HMI/SCADA solution. As such, we’ve worked together to test the connectivity and operation of each product. Inductive Automation is a member of the Dream Report Proven Partner Program.