Here are the known limitations based on the solution operational design:
1. Application Mode Restriction (Vision OR Perspective Only)
The device can be configured exclusively for either Ignition Vision or Perspective applications.
Because of the very high level of integration between Firmware, Ignition Launcher, Ignition Gateway, the simultaneous use of both application types on a single terminal is strictly unsupported. Switching modes requires a manual reconfiguration that takes approximately 2 minutes.
2. Active Maintenance Contract Requirement
Continuous lifecycle management, central firmware distribution, and automated OS updates are strictly tied to licensing compliance.
Accessing and downloading critical OS updates requires an active maintenance contract for the underlying Ignition module ("Factory Devices Controller").
3. Restricted to Plantformance OS Managed Interfaces
The solution enforces tight environment control to ensure zero-maintenance operations on its immutable Linux firmware.
-
Limitation: Only peripheral interfaces natively recognized and managed by the Plantformance OS are enabled and exposed within the Ignition tag provider. Any physical ports or functionality not explicitly defined in the platform's standard configuration are unavailable besides keyboard and/or mouse.
4. Incompatible with Ignition Failover Configurations
The architectural design focuses on streaming state-of-the-box hardware integration from a centralized gateway module to independent terminals.
The module is currently not compatible with standard Ignition fail-over configurations. If application-level high availability (HA) is required, separate licensing and architecture rules apply.
We are working on making the module redundancy aware.
5. Non-Guaranteed Multi-Screen Operations
While newer hardware iterations (such as those built on the 12th Gen Intel architecture) feature physical external video outputs like HDMI, the display configuration remains locked down.
Support for industrial operations involving multiple simultaneous screens is not guaranteed, and the secondary display port remains inactive or restricted under standard deployment.
6. Restricted Bluetooth Protocol Stack
While a full Bluetooth communication stack is physically embedded within the hardware extension module, its operational access is currently restricted.
The Bluetooth stack is not open for general third-party connectivity or custom device integration at this moment. Wireless communication is strictly limited to peripherals natively integrated and approved by Plantformance.
Contact info@plantformance.com for any requirements.