artlkp.blogg.se

I plan to write a small application that would take the tag data and create a JSON data set of the Wonderware tags to be added to Ignition. All of the needed tag metadata is in the Wonderware Historian DB, and I can extract that with SQL. It is possible to create tags in Ignition by pasting in a JSON data set of the tags to be added. Which I can then use to create Ignition OPC tags. In addition, to connect to process Historian or Wonderware eDNA, you would need to contact Wonderware support to check if it has OData feed available or how to use its API to retrieve data, it is possible to connect straight to the OData feed from Power BI Desktop or use the web entry in Power BI desktop to connect to Wonderware API.I’m currently testing a 3rd party utility called “Integration Objects OPC UA Server for Databases”, that reads Live and History values from Wonderware Historian and then provides an OPC UA interface to that data. For more details about gateway workflow, please review this blog. Moreover, bandwidth impacts the network, which will impacts the connection between Power BI and SQL data source, to ensure that the refresh process is as fast as possible, the connection needs to be as fast as possible, thus you need to adjust bandwidth based on your requirement. DirectQuery is useful when you build visualizations over very large dataset, you can review this article to get more details about DirectQuery.Īfter you publish Power BI Desktop file to Power BI Service, you can add the SQL data source within gateway, as your dataset is configured for a DirectQuery connection, there is a direct connection between Power BI and the database, there is no need to schedule refreshed, and dataset is refreshed approximately each hour or when interaction with the data occurs. You store the Wonderware Historian Database in SQL Server? If so, you can use DirectQuery mode to connect to the dataset in Power BI Desktop.