Optix Runtime with Base Token Package (XS)
The following example shows a system architecture that uses a panel PC and one web
client.
System Architecture - Base Package XS
The example architecture has the following components.
- Built-in touch screen is not required
- Communicates with aRockwell Automation®controller
- Acts as an OPC UA server
- Logs data to an internal database
- One web client
The following table shows example runtime sizing for a package that includes the application
components.
Selection | Base Token Value | Extended Token Value | |
|---|---|---|---|
Clients | |||
Web HMI client - 1 connection | 1 | - | |
Features | |||
Runtime retentivity | 1 | - | |
Data logger | 1 | - | |
Embedded database | 0 | - | |
Controller Connections | |||
Rockwell Automation®
EtherNet/IP™ - 1 connection | 1 | - | |
Interoperability | |||
OPC UA Server - 1 connection | 1 | - | |
Total: | 5 | 0 | |
Base token package (XS), which includes five base tokens, is recommended for this example.
There is no need for an extended package. Use the Device Sizing tool to select the best deployment
option for your application.
For this configuration, you can select one of the following deployment options.
- Embedded Edge Compute module
- OptixEdgeStandard
- Optix Runtime base token package (XS) + consider bundling with ASEM 6300 Industrial Computers
Provide Feedback