Overview
The Solution Settings is interface provides a centralized configuration interface, facilitating the modification of general solution settingslocation for configuring various aspects of your solution. Users can adjust parameters ranging from licensing considerations, solution file size details, and runtime processes, to Python interpreter paths through specific sections: related to licensing requirements to run the solution, Python interpreter paths, among others. This page includes Solution Information, Target Platform and License, Solution Options, Run Modules inside the main in Runtime processProcess, and Python Interpreter. To make solution configuration changes, simply navigate to Solution → Settings on the module sidebar.
On this page:
| Table of Contents | ||
|---|---|---|
|
Key Concepts and Terminology
Target Platform
The target platform refers to the operating system and hardware environment on which your solution will be deployed and executed. Our platform supports various target platforms, including Windows, Linux, and real-time operating systems, ensuring flexibility and compatibility with a wide range of industrial automation systems.
By selecting the appropriate target platform, you can optimize your solution's performance and ensure seamless integration with your existing infrastructure.
Target License
The platform uses a licensing model to provide different levels of functionality and scalability, depending on the needs of your solution. The target license determines the features, modules, and tag limits available within a specific solution.
We offer several licensing options, catering to various solution sizes and complexity levels. By choosing the right target license for your solution, you can ensure access to the necessary tools and features while optimizing costs.
Categories
One interesting feature in the software platform is the ability to use Categories to organize and group items on runtime, such as variables, alarms, and trends.
Plugins
Plugins are additional software components that can be integrated into the platform to extend its functionality and compatibility. These plugins can be developed by third-party vendors or even end-users. They enable you to add custom features, support for specific devices, or integration with other software systems.
Our platform provides an SDK (Software Development Kit) that allows developers to create their own plugins, ensuring maximum flexibility and adaptability to meet unique solution requirements. By leveraging plugins, you can tailor the platform to fit your specific needs and create highly customized automation solutions.
Check Import Plugin for more information.
|
Solution Settings User Interface
Access the Solution Settings through Solution → Settings to tailor your solutions to specific requirements and ensure seamless integration with external systems. Here, you'll find the configuration options that apply to the entire solution and you can view and change the solution settings that you configured when you created the solution.
Solution Information: Includes solution information (read-only), such name, file size, description, solution path and tag counters for local and external.
Target Platform and License: Includes options to modify the solution's target platform and enables license customization, allowing you to select the best family and product model for your solution. You can also customize the historian license.
Solution Options: Defines runtime behavior, including language settings in "Culture Info," enabling client-side tasks for WPF applications, and activating diagnostic logging for system analysis.
Run Modules inside main Runtime process: Checkboxes allow the use of script-based tasks and enable the primary communication channel utilized for device interactions.
Python Interpreter: Users must specify the location of the Python interpreter when running Python scripts and tasks within the application. There are two options available: "Local," which refers to a Python installation on the user's machine, and "Server," which points to a Python installation on a remote server.
Settings Configuration
Understanding Solution Settings and Utilities
Overview
Access the Solution Settings through Solution Settings → General to tailor your solutions to specific requirements and ensure seamless integration with external systems.
The Solution Settings (Solution → Settings) has the configuration options that applies to the entire solution.
You can view and change the solution settings that you configured when you created the solution.
The Solution Settings navigation on Solution Explorer has general settings that applies to the entire Solution , and Utilities to assist the creating and maintenance of the solution. It includes:
Solution Information
The Solution Settings (Solution → Settings) has the configuration options that applies to the entire Includes all the basic information about your solution.
Solution information | |
|---|---|
Description | A description for the solution. |
Solution Path | Read-only path to the solution. |
Tag Count | How many tags the solution has. |
Communication Points
Help URL | This feature allows users to integrate additional support for their solution by adding Help URLs for knowledge bases and documentation |
. |
Target Platform and License
Content placeholderProvides an overview for understanding the capabilities and limitations of your selected solution.
Target Platform and License | |
|---|---|
Target Platform | Shows the target platform selected in the solution creation procedure. |
Product Family
A basic description of the product families is
FrameworX — Complete FactoryStudio functionality
FactoryStudio — Scales based on the number of Tags & clients.
Edge HMI — Use for smaller applications and embedded systems.
Express — Use only for test or demonstration purposes.
Edge Gateway — Create a solution to work as an OPC server or Data Acquisition Gateway, providing data to other applications from the native protocol drivers.
Changing the family settings may cause some configurations to be invalid. For example, some features are only available in the Enterprise version.
Check our product families:
Product Model
ProductFamily and ProductModel | Go to Product Series for information about the options available. When deployment this solution to product, the Product Family and Model select must match your license. Check Managing Licenses for more information. |
Solution Options
Content placeholderHere, the users can fine-tune the following configurations:
Solution Options | |
|---|---|
Culture Info | Select the target language for the runtime application. This setting controls the formatting of dates, numbers, and other information so they are in compliance with the selected language. It is possible to change this setting later. |
Allow Client Tasks (WPF only) | |
This checkbox allows the execution of client-side tasks in WPF. |
Enable Diagnostics Logging
Checkbox that allows enabling diagnostics logging.
Diagnostics Log Files Location | This dropdown let's you define the location of diagnostic data, aiding in system analysis and troubleshooting. |
Retentive Database Settings
In the Solution Option, click on the gear icon next to the Retentive Database to open the Edit Database Connection popup window.
Edit Database Connection Popup window | |
|---|---|
Name | Defines the database connection name. |
Description | A brief overview informing the purpose or specifications of the database connection. |
Provider | Data providers serve as bridges between applications and specific types of databases. While some providers like ODBC and OleDb offer multi-database support, others like OracleClient, SQLClient, SQLite, and PostgreSQL are specialized for their respective databases. |
Database | The databases you can connect to will vary depending on the selected Provider. |
ServerIP | If the database you want to connect to isn't on the local computer, the ServerIP should be the IP address or network name of the computer with the database. If a tunneling service is required to access the remote computer, the TWebServices utility must be enabled and running on the remote computer. |
Test button | To test the connection. |
DataSource | Displays the configuration string used to connect to the SQLite database. This string specifies the file path and name of the database file, directing the system to the correct database location. The format typically follows "Data Source =ExecutionPathAndName.dbRetentive". |
Password | The security key to authenticate and access the database. |
Run Modules Inside Main Runtime Process
Here, the users configure the solution settings related to module executions.
Run Modules inside main Runtime process
Content placeholder
Solution Options | |
|---|---|
Script Tasks | Enables script-based tasks on the solution. |
First Device Channel | Selects the primary route for communication between a software application and connected devices, ensuring a stable and reliable exchange of data and commands. |
Python Interpreter
Specifies the directory location folder where the Python interpreter is installed.
Python Interpreter | |
|---|---|
Local | |
Server
Troubleshooting and Best Practices
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Troubleshooting and Common #Issues
The Historian module may encounter some issues in its operation. Here are some common issues and their troubleshooting:
#Issue
Solution
Best Practices and #Recommendations
To ensure the smooth operation of the Historian module, follow these best practices:
#Best practice
Defines the path for Python installation folder on the local machine. | |
Server | Defines the path for Python installation folder on the remote server. |
In this section:
| Page Tree | expandCollapseAll | true|
|---|---|---|
|