PLCViewerApp requirements
- Last UpdatedJul 18, 2024
- 3 minute read
You should have already imported the PLCViewerApp to your computer hosting the Galaxy Repository. Refer to the AVEVA PLC Viewer OMI App Readme for instructions to import the app.
This version of the PLCViewerApp must adhere to the following requirements:
-
The PLCViewerApp is targeted for System Platform 2017 Update 3 Service Pack 1 and later.
This version of the PLCViewerApp can be upgraded to subsequent versions of System Platform when they become available.
-
This version of the PLCViewerApp supports Rockwell, Schneider Electric, and Siemens Step7 PLCs.
-
The PLCViewerApp requires controller project data from a source logic file, which can be created by each PLC vendor's software utilities.A logic file contains the following data referenced by the PLCViewerApp:
-
Ladder programs
-
Controller and program tags
-
Add-on instructions
-
User function blocks
-
I/O tags
-
User defined data types
For Siemens Step7 PLCs, an export utility application has been provided to export the project configuration into a portable file for each CPU using the Siemens API.
-
Rockwell RSLogix 5000-compatible products
PLCs compatible with the Rockwell RSLogix 5000 family of products require a logic file that must be exported as a .L5X file.
A RSLogix source file is an ASCII file whose data is formatted using Extensible Markup Language (XML). A logic file contains exported controller configuration information and ladder logic of a controller project. You must use your RSLogix-compatible software to export a L5X source logic file.
Schneider Electric Unity Pro-compatible products
Controllers compatible with the Schneider-Electric Unity Pro family of products require a logic file that must be exported as a .zef file. This version of the PLCViewerApp supports Unity Pro 11 to the latest version known as EcoStruxure™ Control Expert.
*.ZEF files are used for exporting projects with global DTMs configuration and are compatible with all versions of Unity Pro.
You must place the source logic file in a folder accessible to the computer hosting the System Platform IDE. Unity Pro needs to be installed on the PC where the PLCViewerApp is configured to access Unity Pro library files. The PLCViewerApp only accesses the XML files included by the installer and does not require the application to be licensed.
Note: If Unity Pro is not installed, a browser dialog appears to enable sourcing the Unity FBLIBSET folder from a user specified location.
-
When using context following with the PLCViewerApp, you can optionally create an asset mapping file to alias the context string to a PLC tag and set the context to a specific controller in a comma separated value (CSV) file.
You must place the asset mapping file in a folder accessible to the computer hosting the System Platform IDE.
For more information about an asset mapping file, see Create an asset mapping file.
Siemens Step7-compatible products
Projects configured using Siemens Step7 must be exported using the PLCViewerAppExporter provided with the package. The PLCViewerAppExporter uses the Siemens Step7 API to export each Stations to an encrypted file. You must place this file in a folder accessible to the computer hosting the System Platform IDE
To export a Siemens project:
-
Copy the PLCViewerAppExporter folder containing the PLCViewerAppExporter.exe and ArchestrA.Prometheus2.Shared.dll to the computer where Siemens SIMATIC Manager is installed and licensed.
-
Confirm the project is accessible in SIMATIC Manager
-
Export SFC source if the source is not current
-
Close SIMATIC Manager
-
Open PLCViewerAppExporter.exe
-
Select the Controllers to export
-
Override the Block and Symbolic name by entering a Display Name (optional)
-
Select File – Import – Display names (*.csv) to load previously saved Display Names (optional)
-
Select File – Export – Display names (*.csv) to save overridden Display Names (optional)
-
Select File – Export – Project (*.S7X) to export controllers to disk
-
Check Exclude unreferenced programs to include programs not being executed (optional)
-
Select OK
-
Select the folder location to save the controller export files
NOTE: Siemens GRAPH (SFC) source files may require updating manually using SIMATIC Manager to ensure the logic presented in the PLCViewerApp is up to date. A message will appear in the output window for each GRAPH file that requires manual export.
When using context following with the PLCViewerApp, you can optionally create an asset mapping file to alias the context string to a PLC tag and set the context to a specific controller in a comma separated value (CSV) file.

You must place the asset mapping file in a folder accessible to the computer hosting the System Platform IDE.
For more information about an asset mapping file, see Create an asset mapping file.