|
What are modules?
Modules are applications that are built on the Ignition platform and integrate into the platform in order to offer functionality. Most of the main features of Ignition are actually provided by different modules such as the Vision and SQL Bridge modules.
Modules integrate seamlessly into the system and provide things like new designer workspaces, new gateway settings, new drivers, and much more.
Why Modules?
The modular architecture of Ignition offers a wide array of benefits.
| • | Flexible licensing - only license the modules that you need, saving money and reducing complexity compared to big monolithic applications that try to do everything. At the same time, the modules have been designed to offer a broad swath of functionality, to avoid having too many pieces. |
| • | Hot-swappable - Modules can be dynamically loaded and unloaded, allowing you to install, remove and upgrade them without affecting other parts of the system. This can have huge implications for big projects where up-time is important. |
| • | Increased system stability - Building modules on a common platform means fewer bugs, better isolation, and all around increased stability. |
Types of Modules
|
|
|
OPC-UA Module
|
Provides OPC-UA server functionality and an open device driver API.
|
SQL Bridge Module
|
Offers transactional datalogging, bi-directional OPC-to-DB synchronization, stored procedure support and more.
|
Vision Module
|
Provides HMI/SCADA functionality with web-launched clients.
|
Reporting Module
|
Works with the Vision module to provide robust reporting capabilities.
|
OPC-COM Module
|
Allows Ignition to connect to older COM based OPC-DA servers.
|
|