Displays the current selected Session State. Users can choose to save the Import Session properties to a Session State file that can be later restored for quickly importing the same or a similar set of data source files.
Displays the File System Folder where the data source files exist to import. This will be an export folder that contains the various documents that were exported using the TriStation application software. The following set of documents are expected in this export folder path:
All Program Logic PDF documents { Note: users can name them in any convenient manner as the import operation will rename them appropriately to the name of the program. }
"Project Implementation" PDF document
Program Variable Listing.xls
Tagnames Where Used.xls
TagnameDeclarations.xls
Program Logic PDF document files.
Users can choose to name these program logic PDF document files as in 1.pdf, 2.pdf, etc. The import operation will read the Title Block for each Program Logic PDF document and rename them to the program name.
The "Project Implementation" document must be exported as a PDF type so that the Project Information header content is there for reading.
Excel (*.XLS) type data files must be exported using the option
The following documents are required to be exported as Microsoft Excel (*.xls) Data-Only types:
Displays the auto-generated name of the PLC Controller Strategy that will be created during import.
You can choose to manually edit this name, but its uniqueness must be guaranteed as other PLC types can also be imported into the same Collection snapshot.
Click this drop-down button to select the PKS Release to use when generating PKS compliant Control Module strategies to contain the PLC import data.
It is recommended to use a mimimum of R430 due to the new Chart View visual rendering model that is now used due to changes that occurred in Control Builder Chart View rendering beginning with PKS Release 430.
Displays the name of the TriStation "Project Implementation.pdf" file that is exported from the TriStation application. This is the default name that is expected. If users choose to use another name, then they can click the browse button to select another file that contains the expected Project Implementation details.
This project detail information is used to extract various data types such as NodeName, ProjectName, DownloadDate, etc. to auto-generate a unique PLC Controller Strategy name.
Choose this option to append data that is imported to the existing Database:Collection snapshot.
If you do not choose to append, then any existing configuration data in the selected Database:Collection snapshot will be deleted prior to importing the new data sources.
If the data being imported has already been appended to this Collection snapshot, then reimporting it will simply delete all document data associated with the unique Triconex node. Existing generated Control Strategies that represent the PLC Controller and Program Logic will also be overwritten during this reimport operation.
Click this Expander to view the Templates and Styles that are used when generating the Control Module blocks. The TriStation import makes use of the PROGRAM and CONTROLLER blocks. These blocks are generic to all PLC type strategies used to represent a PLC Controller node and its Program Logic strategies.
