Security measures for TIA Portal Openness applications
It is recommended
-
to install a TIA Portal Openness application with admin rights to the programs folder.
-
to avoid the dynamical loading of program parts like assemblies or dlls from the users area.
-
to run the TIA Portal Openness application with user rights.
Hardware parameters
A description of hardware parameters is available in the installation folder of TIA Portal at Siemens\Automation\Portal V*\PublicAPI\V*\HW Parameter Description\Openness_hardware_parameter_description.pdf
Attributes can have dependencies and influence each other. Therefore, if an attribute of a device item or channel has been changed, all attributes of the device item or channel must be verified.
|
Note V* refers to adapted path according to the installed version of TIA Portal. |
Copying a TIA Portal Openness application
When you copy an executable TIA Portal Openness application, it may occur under certain circumstances that the directory path in which the TIA Portal Openness application was originally created is read out by the TIA Portal Openness application.
Remedy:
If you have copied the TIA Portal Openness application to a new directory, open and close the properties dialog to update the Windows cache.
Support of specific features in a TIA Portal project
Failsafe
When you are using TIA Portal Openness there are restrictions regarding failsafe. Please consider the documentation "SIMATIC Safety - Configuring and Programming" for further information.
Test Suite
Openness Support for TIA Portal Test Suite is documented in the respective online help from Test Suite V19
Improvement of the TIA Portal Openness performance
To achieve the maximum performance of TIA Portal Openness you can switch off the global search feature of the TIA Portal. To switch off the global search use the GUI or the TIA Portal Openness API call. When the TIA Portal Openness application is finished the global search could be switched on again. Although this is improving the performance, all TIA Portal Openness features work fine even with global search switched on.
Thread-safe program code
Take care that your code is thread-safe, an event appears in a different thread.
Export behaviour of screen items with style enabled
Export of a screen items with style enabled will not export the attributes of the style item, but those of the screen item before activating the style. If a style is selected and UseDesignColorSchema for the screen item is checked, the screen item fetches the attribute values from the style in the user interface but the attribute values of the screen item that were set before selecting the style are still stored in the database for this screen item. TIA Portal Openness exports these actual values that are stored in the database.
After disabling and enabling the style and exporting the screen item again, the same attribute values will be exported for the screen item like in the style item. If UseDesignColorSchema is unchecked, the attribute values of the selected style item are saved to the database for that screen item.
This problem can be solved by following the steps below:
-
Associate the screen item to the style item:
-
The database contains the attribute values before activating the style.
-
The user interfaces fetches attributes from the style item directly.
-
-
Export the screen item associated to the style item:
-
The XML file contains the attribute values from the database which are those before activating style.
-
-
Disable the UseDesignColorSchema:
-
The attribute values of style item are written in the attributes of the screen item in the database.
-
-
Enable the UseDesignColorSchema:
-
The attribute values of the screen item in the database are not changed and are still the ones from 3.
-
The user interfaces fetches attributes from the style item directly.
-
-
Export the screen item associated to the style item:
-
The XML file contains the attribute values from the database which were set at step 3, which are the same as the values in the style item.
-
Importing ASi slaves via AML
If one of the following ASi slaves is imported via an aml-file the firmware version of the device item will be set to V13.0 in all cases:
-
ASIsafe FS400 RCV-B: 3SF7 844-*B***-***1
-
ASIsafe FS400 RCV-M: 3SF7 844-*M***-***1
-
ASIsafe FS400 TRX-M: 3SF7 844-*M***-**T0
-
ASIsafe FS400 RCV-C: 3SF7 844-*T***-***1
Exporting and importing function keys
Function keys are synchronized during the import. If a function key is created in the global screen and the key is empty in the screen, the corresponding function key will use the global definition in all screens.
If you want to disable the global use of function keys after the import, define empty keys in the screens and import the screen types in the following order: Global screen, templates, screens.
If you want to ensure when exporting the screens that the global definition of a function key is not used by the template or by the global screen, create an empty function key in the screen. Select the required function key in the screen, then enable the "Use global assignment" property and disable it again.
Accessing a device while Online
Writing attributes of a device that is Online is not supported. Reading attributes is supported.
Disconnecting a subnet is not supported when the device is online.
Instance-specific attributes when importing blocks via TIA Portal Openness
In certain situations, the import rules can mean the loss of instance-specific attributes, such as start values, for example.
Writing access for OB block priority attribute
The Priority attribute name for write access for OB block is changed to PriorityNumber.
Information on specific features
Please See FAQ entries in Siemens Industry Online Support for further information concerning the following Openness functionalities:
-
Archive/retrieve project
-
Export/import watch tables
See also