Ver videos: Using PLCs & SQL Databases Together

Learn ways to use the versatile SQL Bridge Module and ways to apply it to your enterprise.

Video: SQL Bridge or Tag Historian: When to Use Which

Industrial data has been inaccessible for far too long, and traditional SCADA solutions do not fully provide the data that organizations are thirsting for. Leveraging modern IT technologies, Ignition’s SQL Bridge Module and Tag Historian Module free data from its confines. Both modules have the ability to log data but are also different in numerous ways. This video clarifies the differences between the two modules so you can get the most out of them. See all of Inductive Automation's Modules:

Video: History With Context, OEE Implementation/OEE Downtime, and Production Tracking

SQL Bridge and Tag Historian are two Ignition modules with specific functions. By combining the two modules, you can pair the process values gathered by the Tag Historian Module with the contextual data collected by the SQL Bridge Module. This yields rich data that enables you to identify and quickly resolve issues in your industrial process. See the fully integrated Ignition modules:

Video: Synchronizing 2 or More PLCs, and Mapping to Stored Procedures

SQL technology has opened the doors on what you can do with your HMI/SCADA system. The SQL Bridge Module is a robust transaction manager that goes beyond data storage — it also brings logic to your data, allowing limitless potential with your HMI/SCADA application.

Video: Barcode Scanning, Sequencer, and Scheduling

So far in this series, we have learned the difference between the SQL Bridge Module and the Tag Historian Module, how both modules can be used, and how SQL Bridge is a powerful transaction manager. Now we’ll dive deeper and look at other use cases that SQL Bridge is ideal for.

Video: Recipe Management with Configuration Demo

The Ignition SQL Bridge Module is an incredibly versatile tool with nearly limitless possibilities. Having a SQL database not only helps to make your data accessible, it helps free up memory on your PLCs. For example, PLCs are commonly used to store recipes but this is actually an inefficient and risky practice. By using SQL databases for this task, you can alleviate data-storage headaches and keep the PLCs focused on process control.

Chatea con nosotros !