APROL R 4.0 - Installation APROL System A3 Upgrade Notes
We reserve the right to change the contents of this manual without warning. The information contained herein is believed to be accurate as of the date of publication; however, Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. makes no warranty, expressed or implied, with regards to the products or the documentation contained within this book. In addition, Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. shall not be liable in the event of incidental or consequential damages in connection with or resulting from the furnishing, performance, or use of these products. The software names, hardware names, and trademarks used in this document are registered by the respective companies.
The following documentation A3 Upgrade Notes (Version 3.09 / 23.09.2014) refers to APROL R 4.0
2014 Bernecker + Rainer Industrie-Elektronik Ges.m.b.H.
The APROL System Installation manual group includes the following manuals A1 Release Notes A2 Getting Started A3 Upgrade Notes Order number of the APROL System installation manual group: MAAPINST40-ENG
A3 Upgrade Notes
Contents A3 Upgrade Notes V3.09
A3-1 Upgrade notes 1-1 1.1 Limitations in the current APROL release 1-2 1.1.1 Redundant controllers 1-2 1.1.2 KDE version 4.x 1-3 1.1.3 Use of an external sound card for APC 810 1-3 1.2 New features after updating to APROL R 4.0-08 1-1 1.2.1 Controller AR-OS versions 1-1 1.2.2 New features in the AutoYaST DVD V4.0-080 1-1 1.2.3 Compiling equipment and parameter set templates 1-2 1.2.4 Changes in the 'MonCtrlCpuRed01' hyper macro 1-2 1.3 New features after updating to APROL R 4.0-07 1-1 1.3.1 Controller AR-OS versions 1-1 1.3.2 New features in the AutoYaST DVD V4.0-070 1-1 1.3.3 Changing the JasperReport theme after an update 1-1 1.3.4 Display of company logos in the as-built documentation 1-2 1.3.5 Checks after an incorrect shutdown of an APROL server/system 1-2 1.3.6 Access of Historical Data via SQL 1-3 1.4 New features after updating to APROL R 4.0-06 1-4 1.4.1 Controller AR-OS versions 1-4 1.4.2 New features in the AutoYaST DVD V4.0-060 1-4 1.4.3 Access of Historical Data via SQL 1-4 1.4.4 Extended use of ST/SFC blocks in CFCs 1-5 1.5 New features after updating to APROL R 4.0-05 1-1 1.5.1 Controller AR-OS versions 1-1 1.5.2 Access of Historical Data via SQL 1-1 1.5.3 Uniform nomenclature for bit-coded system variables 1-1 1.5.4 Validity of the 'SysDataTransfer' transfer file 1-2 1.5.5 Selecting an APROL system in the ParameterCenter 1-2 1.6 New features after updating to APROL R 4.0-04 1-1 1.6.1 Controller AR-OS versions 1-1 1.6.2 New features in the AutoYaST DVD V4.0-040 1-1 1.6.3 Access of Historical Data via SQL 1-1 1.6.4 Replacement of APROL-specific constants from the 'runtime' AS library 1-2 1.6.5 Self ID for the 'EmbeddedApp' visualization element 1-2 1.7 New features after updating to APROL R 4.0-03 1-1 1.7.1 Controller AR-OS versions 1-1 1.7.2 AutoYaST DVD V4.0-030 update 1-1 1.7.3 System variables for downloads to controllers 1-2 1.7.4 Buffering and subsequent provision of log entries during a disturbed recording 1-2
iii
1.8 New features after updating to APROL R 4.0-02 1-1 1.8.1 Controller AR-OS versions 1-1 1.8.2 AutoYaST DVD V4.0-020 update 1-1 1.8.3 Configuration of the AprolJobDispatcher 1-2 1.8.4 Assignment of the minimum password length 1-2 1.8.5 Use of the 'AprolCaeRename' script 1-2 1.8.6 Provision of bit-coded system variables 1-2 1.8.7 Extension of the SNMP diagnosis for redundant controllers 1-4 1.8.8 Change of CSV export in the TranslationManager 1-4 1.8.9 Support of internal UPS modules for APC810/APC910 1-4 1.9 New features after updating to APROL R 4.0-01 1-1 1.9.1 Controller AR-OS versions 1-1 1.9.2 New features in the AutoYaST DVD V4.0-010 1-1 1.9.3 Driver for NVIDIA graphic cards 1-1 1.9.4 Update of the AprolSqlServer driver 1-2 1.9.5 Reactivation of all APROL systems 1-2 1.9.6 Use of the BR modules needed by the 'PAL' CAE library 1-2 1.9.7 Update of optional hardware upgrades 1-2 1.9.8 Creation of the exclude files for the optimization of the RRAD configuration framework 1-3 1.9.9 SVG check during an import into the image container 1-3 1.9.10 Library-spanning Export / Import of library blocks 1-4 1.9.11 SFC: Display of the live values for array variable elements 1-4 1.9.12 Preview of the 'Color' dynamization type 1-4 1.9.13 Filter function in the alarm report via APROL system 1-5 1.10 New features after updating to APROL R 4.0-00 1-1 1.10.1 Minimum release for an upgrade to APROL R 4.0-00 1-1 1.10.2 AutoYaST installation 1-1 1.10.3 Controller AR-OS versions 1-2 1.10.4 Use of different Automation Studio variations in one engineering environment 1-3 1.10.5 Change of VMware on Windows 7 Professional 1-3 1.10.6 Update of the MySQL version 1-3 1.10.7 Change of the logging path for trend data 1-5 1.10.8 Change of the database structure 1-6 1.10.9 Limitations with the names of customer-specific ChronoLog FIFOs and containers 1-7 1.10.10 Cancellation of the APROL 'DCS' library 1-7 1.10.11 Cleansing of the CAE library 'APROL' 1-7 1.10.12 Removal of old images from process graphics and graphic blocks 1-8 1.10.13 Switching of all icons to SVG format 1-8 1.10.14 Extension of the master data 1-8 1.10.15 Substitute blocks for discontinued blocks of the 'APROL' CAE library 1-9 1.10.16 Reactivation of the VNC configuration after an upgrade from APROL release < 3.6-08 1-10 1.10.17 Exchange of applications in the KDE 1-10 1.10.18 Discontinuation of the ChronoChartPrinter and the 'old' Iosys web interface applications 1-10 A3 Upgrade Notes iv 1.10.19 Provision of the cluster configuration for multi-runtime systems 1-10 1.10.20 Use of the new Intel graphic driver 1-11 1.10.21 Uniform syntax for system variables in the engineering and runtime environments 1-12 1.10.22 New 'Library Type Definition' project part 1-12 1.10.23 Change of the APROL services' TCP ports 1-13 1.10.24 Update of the VMware 1-13 1.10.25 Driver system variables 1-14 1.10.26 Recording rate for PDA blocks 1-14 1.10.27 Revision of the project and properties dialogs 1-15 1.10.28 BuR Gateway connection 1-15 1.10.29 Provision of further system variables 1-16 1.10.30 Handling hyper macro-intern variables 1-16 1.10.31 Re-definition of the image container of libraries within a project 1-17 1.10.32 Extension of the language switching 1-17 1.10.33 Simplified input of process variables and their respective Iosys connection 1-18 1.11 New features after updating to APROL R 3.6-10 1-19 1.11.1 Controller AR-OS versions 1-19 1.11.2 Substitution of the 'rint' function 1-19 1.11.3 Change of the AR structure from '3.6-06' to '3.6-08' 1-19 1.11.4 Use of an APC 910 / HP-Desktop 8300Elite-CMT 1-20 1.11.5 New features in the energy monitoring reports 1-20 1.11.6 Hardware PV global volatile 1-21 1.11.7 Update of the CAE database 1-21 1.12 New features after updating to APROL R 3.6-09 1-1 1.12.1 Controller AR-OS versions 1-1 1.12.2 Support of Intel Atom CPUs 1-1 1.12.3 Usage of the VMware workstation version 9.0.0 1-1 1.12.4 Manual setting of the link of the used PAL modules after an AR upgrade 1-2 1.12.5 Adoption of module dependencies is possible for B&R libraries 1-3 1.12.6 Integration of the EnergyMonitoring report 1-4 1.12.7 Additions to the SFC transition diagnosis 1-6 1.12.8 Clean-up directory before import 1-6 1.12.9 Automatic detection of the system directories is no longer supported 1-8 1.12.10 Extended configuration possibilities for the APROL shift logbook 1-8 1.13 New features after updating to APROL R 3.6-08 1-1 1.13.1 Controller AR-OS versions 1-1 1.13.2 Update to the current AutoYaST version 1-1 1.13.3 Consistency check of project part names 1-3 1.13.4 Problems when using the visualization 'TextView' element 1-5 1.13.5 Warning due to obsolete directory 1-5 1.13.6 Renewed password entry for existing users in the customer-specific MySQL databases 1-5 1.13.7 Update step for the SFC function blocks and programs 1-6 1.13.8 Maximum length for transition names 1-6 1.13.9 Locking of the control of an SFC with concurrent access 1-6
v
1.13.10 Use of the 'AsBrMath' library instead of 'AsMath' 1-6 1.14 New features after updating to APROL R 3.6-07 1-1 1.14.1 Optional installation of the PHP version 5.3 1-1 1.14.2 Controller AR-OS versions 1-3 1.14.3 Opening and saving all SFC programs and function blocks 1-3 1.14.4 Corrections to the UcbServer 1-4 1.14.5 Change to VMware version 8.0.1 1-4 1.15 New features after updating to APROL R 3.6-06 1-1 1.15.1 Controller AR-OS versions 1-1 1.15.2 Extended logging of interactions in alarm handling 1-1 1.16 New features after updating to APROL R 3.6-05 1-1 1.16.1 Controller AR-OS versions 1-1 1.16.2 Adjustment of the SFC logging function 1-1 1.16.3 New system variables for warning about not enough free hard-disk space1-1 1.16.4 Automatic configuration of the EventDriver 1-1 1.17 New features after updating to APROL R 3.6-04 1-1 1.17.1 Controller AR-OS and Visual Components versions 1-1 1.17.2 Configuration of a cluster for the process bus 1-1 1.17.3 Re-saving existing SFC function blocks 1-2 1.17.4 Use of an LDAP server for authentication 1-2 1.18 New features after updating to APROL R 3.6-03 1-1 1.18.1 Controller AR-OS versions 1-1 1.18.2 Use of the process graphic preview 1-1 1.18.3 Configuration of a guaranteed instance name 1-1 1.18.4 Display of the database connections 1-2 1.18.5 Necessary adjustments to existing SFCs from the Automation Studio 1-2 1.18.6 Discontinuation of the ChronoChartPrinter and the 'old' Iosys web interface 1-2 1.18.7 Provision of a KDE 'Service' configuration 1-2 1.18.8 Change of the unit and IEC type of system variables for memory evaluation 1-3 1.18.9 New status monitoring of the 'LSTRING_TO_
A3 Upgrade Notes vi 1.19.12 Historical recording and evaluation of the limit inputs of a trend block 1-8 1.19.13 Value change with the multiple choice of trend slots 1-9 1.20 New features after updating to APROL R 3.6-01 1-1 1.20.1 Actualized controller AR-OS versions 1-1 1.20.2 Changed download behavior of the controller variables 1-1 1.20.3 Changed settings for the controller encoding 1-1 1.20.4 Reactivation of the APROL systems 1-1 1.20.5 Import / Export of hyper macros, CFCs and process graphics 1-2 1.21 New features after updating to APROL R 3.6-00 1-1 1.21.1 Actualized controller AR operating system 1-1 1.21.2 Current AutoYaST DVD 1-1 1.21.3 Installation of the APROL system software 1-1 1.21.4 Problems when using the Intel graphic chip set with SLES 11 1-1 1.21.5 Change of the Python version in SLES 11 and the resulting adjustments 1-2 1.21.6 Removal of cancelled 'Control computer (R 3.2 mode)' 1-3 1.21.7 'Supervised' flag for newly created controllers 1-3 1.21.8 Discontinued 'Controller (R 3.2 mode)' 1-4 1.21.9 No support of the VMware version 7.0 on an APC 620 1-4 1.21.10 Uniform nomenclature for control computer driver launching options 1-5 1.21.11 Renaming of the CaeViewer in CFCViewer 1-6 1.21.12 New UcbServer launching option 1-7 1.21.13 Changes in the 'SysMon' CAE library 1-7 1.21.14 Configuration of an empty string as default value 1-8 1.21.15 Extended system variables for "SystemType" and "APROLDATASpace" 1-8 1.21.16 Removal of discontinued blocks from the 'APROL' CAE library 1-9 1.21.17 Typecasting of the CFCs for controller and control computer tasks 1-10 1.21.18 Import of existing Python modules 1-11 1.21.19 Renaming of the 'STRING' data type to 'SSTRING' 1-13 1.21.20 Use of the AS 3.0 code generation 1-14 1.21.21 New location of the TrendServer 1-15 1.21.22 DTD for TrendViewer configurations 1-15 1.21.23 Adoption of values in the DisplayCenter via confirmation with [Enter] key1-16 1.21.24 Clear marking of the CiR status 1-17 1.21.25 Firefox as new standard browser 1-17 1.21.26 Handling the VMware images 1-18 1.21.27 Use of the entire 32 characters for naming hardware I/Os 1-19 1.21.28 Classification of a function block's local variables 1-20 1.22 New features after updating to APROL R_3.4-08 1-1 1.22.1 Actualized controller AR version 1-1 1.22.2 Preparatory measures for connecting several AlarmServers to one AlarmMonitor 1-1 1.22.3 Extensions in the OperatorManager 1-1 1.22.4 Usage of the VMware version 6.5 1-1 1.22.5 Specifics after updating to VMware version 7.0 1-2 1.22.6 Optional use of the 'License Protection Hardware Key' 1-3 1.22.7 Checking of the password security 1-3 1.23 New features after updating to APROL R_3.4-07 1-1
vii
1.23.1 Actualized controller AR version 1-1 1.23.2 Special points for the AutoYaST DVD update 1-1 1.23.3 New UcbServer launching option 1-1 1.23.4 Stricter plausibility control for AS 3.0 code generation 1-2 1.23.5 Substitution of PVs in the Gateway Editor 1-2 1.23.6 Import/export of the I/O mapping of all of a controller's modules 1-3 1.23.7 Dynamic assignment of a file or URL for the 'TextView' visualization element 1-4 1.23.8 Multiple-choice in the OperatorManager 1-5 1.24 New features after updating to APROL R_3.4-06 1-1 1.24.1 Actualized controller AR version 1-1 1.24.2 Additions in the licensing mechanism 1-1 1.24.3 Overlapping order of placed image macros 1-1 1.24.4 Performance increase when checking the APROL installation 1-2 1.24.5 New options for the RK512 driver 1-2 1.24.6 Adjustment of the status variables for the monitoring of the cross driver 1-3 1.24.7 Actualized firmware version for DP master cards 1-3 1.24.8 Adjustments for the InaDriver 1-4 1.24.9 New menu navigation in the APROL installation 1-4 1.25 New features after updating to APROL R 3.4-05 1-1 1.25.1 Actualized controller AR version 1-1 1.25.2 Special procedure when installing the AutoYast DVD 1-1 1.26 New features after updating to APROL R 3.4-04 1-1 1.26.1 Actualized controller AR version 1-1 1.26.2 Web based licensing procedure 1-1 1.26.3 Cancellation of "control computer (R 3.2 mode)" project part 1-2 1.26.4 Use of the AS 3.0 code generation in the future APROL R 3.6 1-3 1.26.5 Importing CAE blocks 1-3 1.26.6 Improved system monitoring 1-4 1.26.7 Additional saving of the TrendViewer configuration as generated project state 1-4 1.26.8 Quicker activation of several connectors 1-5 1.27 New features after updating to APROL R 3.4-03 1-1 1.27.1 Actualized controller AR version 1-1 1.27.2 Simplified configuration of the control computer task 1-1 1.27.3 Change of the validator for host names 1-2 1.27.4 Stricter plausibility control for AS 3.0 code generation 1-3 1.27.5 Dynamic configurability of the AprCcTrend block's MIN and MAX pins 1-4 1.27.6 Additional plausibility checks in the parameter management 1-4 1.27.7 Changed identifiers for process variables on the controller 1-4 1.27.8 Simplified handling of images 1-4 1.27.9 Special features when using the visualization elements "InputOutputBox" and "Slider" 1-5 1.27.10 Functionally typified block pins 1-5 1.27.11 New configurations editor for control computer and APROL system 1-6 1.27.12 Optimized CC module options for the DisplayCenter 1-6 1.27.13 Simplification when using the VM for the AS configuration 1-7
A3 Upgrade Notes viii 1.27.14 Special features when installing the APROL system software 1-7 1.27.15 Discontinuation of the AprUcSMS block 1-8 1.28 New features after updating to APROL R 3.4-02 1-1 1.29 New features after updating to APROL R 3.4-01 1-1 1.30 Important notes for upgrading to APROL R 3.4 1-2 1.30.1 Selective remanence as an attribute of block pins 1-2 1.30.2 Replacement of the TrendData application 1-2 1.30.3 Replacement of the "SYSTEM", "SYSTEM_RIO", and "SysMon_2005" libraries 1-3 1.30.4 Changed data storage for all I/Os 1-3 1.30.5 Checking of rights allocated to users and operators 1-3 1.30.6 New IEC data type LSTRING 1-4 1.30.7 Simplified CFC creation 1-4 1.30.8 KDE configurations 1-5 1.30.9 SNTP configuration via the controller's OS 1-5 1.30.10 Simplification of the control computer configuration 1-5 1.30.11 Checking the visualization 1-6 1.30.12 Extended project properties 1-6 1.30.13 Name change of system variables 1-6 1.30.14 Activation of the control computer before the upgrade to APROL R 3.4 1-6 1.30.15 Replacement of the ApEx450Gw.br module 1-6 1.31 New features after updating to APROL R 3.2-04 1-8 1.31.1 Exchange of CPUs in the project part "controller" 1-8 1.32 New features after updating to APROL R 3.2-03 1-1 1.32.1 Actualized controller OS version 1-1 1.32.2 Sysconf switch for increased performance and reduced memory requirements 1-1 1.32.3 Changed mechanism for the creation of backup files 1-2 1.32.4 Actualized firmware version for DP master card 1-2 1.32.5 Updated B&R hardware catalogue for the controller configuration 1-3 1.33 New features after updating to APROL R 3.2-02 1-1 1.33.1 AR-I/O operating system S0290 as new default OS version for SG4 targets 1-1 1.33.2 Support for the IF766 as an additional DP master card 1-1 1.33.3 Deactivation of the I/O shoveler in service mode 1-2 1.33.4 Prevention of unnecessary write jobs for SG4 CPUs 1-2 1.33.5 Increased system stability via evaluation of the AprolLoader status 1-3 1.33.6 Simplified configuration of the control computer task 1-3 1.33.7 Provision of Python service functions 1-4 1.33.8 Updates in the gateway-editor 1-4 1.33.9 Check-box for reduced plausibility check 1-5 1.33.10 Logging of the quantity structure for Iosys variables 1-5 1.33.11 Patch information when checking the installation 1-6 1.33.12 Notes about the XML configuration of the alarm line 1-6 1.34 New features after updating to APROL R 3.2-01 1-1 1.34.1 New controller OS version for SG4 targets 1-1 1.34.2 Use of the MD5 check sum with TAR archives 1-1
ix
1.35 Important information for an upgrade to APROL R 3.2 1-1 1.35.1 Combination of project parts 1-2 1.35.2 Backup of the cancelled blocks without replacement block 1-3 1.35.3 Plausibility check for the naming of CAE libraries 1-3 1.35.4 Changed behavior by activation of the default OS for CAE libraries 1-4 1.35.5 Special features during the configuration of a second Ethernet interface for SG4 targets 1-4 1.35.6 Additional plausibility check for multiple connections with the same myNode 1-5 1.35.7 New TrendViewer for the graphical representation of the course of the processes 1-5 1.35.8 Conversion of the old TrendViewer configurations 1-5 1.35.9 Replacement of the Ult1mo fonts 1-8 1.35.10 Additional plausibility check during checking and compiling 1-8 1.35.11 RemoteCompiling configuration 1-9 1.35.12 Replacement of the external library documentation with As-Built documentation 1-9 1.35.13 Encoding entry for Python modules 1-10 1.35.14 Adaptation of the KDE configuration 1-10 1.35.15 Creation of the physical view independent of the identification system 1-11 1.36 New features after updating to APROL R 3.0-07 1-1 1.36.1 Display of record gaps in the trend system 1-1 1.36.2 Starting several instances with the same Self ID 1-1 1.36.3 Conversion of files from latin1 to UTF-8 1-1 1.37 New features after updating to APROL R 3.0-06 1-1 1.37.1 Additional consistency check with the Profibus DP configuration 1-1 1.37.2 Determining the download order in a redundancy system 1-1 1.37.3 Automatic Start of the virtual keyboard for touch screen operation 1-2 1.37.4 Extended support from the Modbus controller driver 1-3 1.38 New features after updating to APROL R 3.0-05 1-1 1.38.1 Download without restart of the visualization 1-1 1.38.2 Upgrades in the controller management 1-1 1.38.3 Automatic CPU platform recognition with the InaDriver 1-2 1.38.4 Output language code in python 1-2 1.38.5 Assignment of BOOL variables in the EventDriver 1-2 1.38.6 Fallback mechanism for use of fonts 1-3 1.39 New features after updating to APROL R 3.0-04 1-1 1.40 Important information concerning the update to APROL R 3.0-03 1-1 1.41 New features after updating to R 3.0-03 1-1 1.42 Important information concerning the update to APROL R 3.0-02 1-1 1.43 New features after updating to R 3.0-02 1-1 1.43.1 Preparing OS version V0285 for SG4 targets 1-1 1.43.2 Importing the APROL SSL CA certificate 1-2 1.43.3 Init and exit code for function blocks 1-6 1.43.4 Security and transparency when handling the B&R controller 1-6 1.43.5 Change to the interface name in the configuration for a DP master connection 1-7 1.43.6 Support of the new IF761 and IF762 interface modules for SG4 targets 1-7 A3 Upgrade Notes x 1.43.7 Special features for an OS change of SG4 targets 1-7 1.43.8 Preparation of the current B&R hardware catalog 1-8 1.43.9 Changes to the IEC61131 library 1-8 1.43.10 Forced use of scaling blocks 1-9 1.43.11 Increased efficiency for the configuration 1-10 1.43.12 Using multiple function blocks 1-10 1.43.13 As-built documentation for the CAE libraries 1-11 1.43.14 Using extended text attributes when creating visualization application 1-11 1.43.15 Marking if compilation/generation is required for project elements 1-12 1.43.16 DisplayEditor configuration file 1-13 1.43.17 Change to the ChronoLog directory 1-13 1.44 Important information concerning the update to APROL R 3.0-01 1-1 1.45 New features after updating to APROL R 3.0-01 1-1 1.45.1 Support of systems with 64-bit architecture 1-1 1.45.2 Updated physical view dialog box 1-1 1.45.3 Cancellation of special layer for controls and widgets 1-1 1.45.4 Preparation of the S5/S7 driver for B&R controllers 1-1 1.45.5 Easy login for WEB reports 1-1 1.45.6 Standardized time navigation for WEB reports 1-1 1.45.7 Defined display of small objects when zooming out of process graphics 1-2 1.45.8 Redundant connection of B&R controllers to APROL 1-2 1.45.9 New search engine for documentation 1-2 1.45.10 Additional help dialog boxes for IEC types and DEFINES 1-2 1.45.11 New import/export functions in the ParameterCenter 1-2 1.45.12 System pin as function block pin attribute 1-2 1.45.13 Updated function block documentation 1-3 1.46 Starting the Engineering system after an update 1-3 1.46.1 Engineering system update 1-3 1.47 Implementing UNICODE into existing projects 1-4 1.47.1 Converting CAE files to UTF-8 1-5 1.47.2 Converting the Web area to UTF-8 1-6 1.48 Adapting an R 2.4-04 Engineering system to R 3.0 1-6 1.49 Converting a system's runtime data to UTF-8 1-16 1.49.1 Parameter data conversion 1-16 1.49.2 Backup historical data 1-17
A3-2 Appendix 2-1 2.1 Revision history 2-1 2.2 Document information 2-4
xi
APROL Documentation A3 Upgrade Notes V3.09
belongs to the manual set Installation APROL System
Target group, conventions, and format The manual A3 Upgrade Notes is intended for users or system administrators who are responsible for the installation and upgrade of the Linux operating system, the installation of the APROL system software, and the configuration of the APROL systems on a Linux machine. In this documentation the following formatting is used: Key [Esc]-Key Menu item „Module-Groups/open“ Directory name HOME/ENGIN/HTML/049 In this manual the following icons are used to highlight special information: Listing
Listing
Listing
Tipp or suggestion
Note
Warning
Reference
This description is under construction at present. This point is to be carried out by the user List of necessary configuration steps Next step
Configuration finished
xiii
A3-1 Upgrade notes
An upgrade to the highest subsequent main APROL release must always be made in order to guarantee a consistent state of the project data. The following builds are the minimum requirements for an upgrade to a new main release: APROL R 2.4-05 APROL R 3.0-06 APROL R 3.2-04: APROL R 3.4-06 APROL R 3.6-06 The following upgrade/update notes, which are in chronological order, should be observed for the respective release/build.
Upgrade notes 1-1
1.1 Limitations in the current APROL release There are the following limitations in the current APROL release:
1.1.1 Redundant controllers .
1.1.1.1 Controller boots permanently The behavior occurs when the CPU configured in Automation Studio does not correspond to the actual physical controller.
1.1.1.2 Redundancy configuration after an Automation Studio update The redundancy configuration must be checked in Automation Studio after an Automation Studio update. The 'Redundancy configuration' entry and the network configuration must be checked. The 'Project name' entry can contain the value 'Aprol1_Config1' and must be corrected to the instance name of the controller. The IP addresses in the network configuration may have to be reconfigured.
1.1.1.3 Use of the ControllerManager with a redundant AR via ANSL Some services are deactivated or can only be executed on the active CPU during the communication with a redundant controller via ANSL and ControllerManager. This is due to changes in the AR-OS versions. These are the following services: Setting the date / time (can only be used on the active CPU)
Module downloads and derived functions (restoring the CPU content, moving a module in memory) are deactivated. Starting and stopping tasks and task classes (only possible on active CPU)
Setting single link node force values or activating/deactivating single link node force values (only possible on active CPU) Deactivation of all link node force values with one action (only possible on active CPU)
If these functions are used with an INA connection, there will always be an error message. The insertion/removal of modules can only be done in the CaeManager in project engineering and then transferred to the controller with the download mechanism.
A3 Upgrade Notes 1-2 1.1.2 KDE version 4.x There are the following limitations because of the used KDE version 4.x: 'Okular' crashes in VNC sessions:
The PDF reader 'Okular' cannot be used in the scope of a VNC session at present. Therefore, the configuration/use of the 'Adobe Acrobat' as standard PDF reader is recommended. KDE configuration for 'BuRBasic':
The configuration of the control bar or the desktop can no longer be regulated or switched off. Multiscreening: The background image on the first monitor of a multi-screen configuration in a newly created CC account can only be seen after having logged into the KDE environment for the second time. Control bar
The control bar (kicker bar) cannot be retracted.
1.1.3 Use of an external sound card for APC 810 Sound cards are not supported in B&R computers of the type 'APC810'. An external sound card must thus be used for sound output.
Upgrade notes 1-3
1.2 New features after updating to APROL R 4.0-08 Amongst various corrections, the following additions are contained in APROL R 4.0-08:
1.2.1 Controller AR-OS versions The AR-OS versions R0309 (Default) and K0406 (Default for Atom processors) are supplied in the scope of APROL R 4.0-08. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version V0408 (necessary for redundant controllers) is also supplied. The current versions 4.0.19.69 SP and 4.1.4.368 (necessary for redundant controllers) of Automation Studio for the controller hardware configuration are supplied in APROL R 4.0-00. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
1.2.2 New features in the AutoYaST DVD V4.0-080 APROL R 4.0-08 requires the AutoYaST DVD version 4.0- 080. It contains the following changes: Update of the Wine environment to version 1.4.1
(Elimination of the 'MIT-SHM' messages with Xming) python-simplepam
(authentication via PAM from Python. Necessary for APROL-SQL) Update libgsm1
(dependencies to Wine 1.4.1)
Upgrade notes 1-1
1.2.3 Compiling equipment and parameter set templates When APROL R 3.6-xx is upgraded to APROL R 4.0-xx, all project parts of the type 'Equipment' and 'Parameter set template' must be compiled once.
The corresponding runtime system (the 'Default runtime system' per default) is entered in the PDL path of the parameter management during the compilation of these project parts. A 'Build (project)' is not enough in this case, because only the 'Process graphic', 'ST', 'SFC', and 'CFC' project parts are compiled with that.
After the 'Equipment' and 'Parameter set templates' have been compiled, the system assignment is entered in the parameter management database (engineering environment) during a 'build'. This information is read during the subsequent download and the parameter management data is transferred to the MySQL database of the runtime environment.
1.2.4 Changes in the 'MonCtrlCpuRed01' hyper macro The 'MonCtrlCpuRed01' hyper macro from the 'SysMon' library has been extended to monitor an ANSL controller-controller connection. The height of the block has been changed from 15 to 17, with respect to future developments. Because of the change in height, instances that have already been placed in CFCs and hyper macros may partially overlap connections or blocks, and would lead to a build error and termination. Eventual errors must be eliminated by correcting the affected project parts.
A3 Upgrade Notes 1-2 1.3 New features after updating to APROL R 4.0-07 Amongst various corrections, the following additions are contained in APROL R 4.0-07:
1.3.1 Controller AR-OS versions The AR-OS versions R0309 (Default) and J0406 (Default for Atom processors) are available in the scope of APROL R 4.0-04. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version M0408 (necessary for redundant controllers) is also supplied. The current versions 4.0.18.71 SP and 4.1.4.348 (necessary for redundant controllers) of Automation Studio for the controller hardware configuration are supplied in APROL R 4.0-07. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
1.3.2 New features in the AutoYaST DVD V4.0-070 APROL R 4.0-07 requires the AutoYaST DVD version 4.0- 070. It contains the following changes: Update of Jaspersoft Studio to V5.6.0
Quagga (routing software suite)
1.3.3 Changing the JasperReport theme after an update The JasperReport server is supplied in the current version 5.6.0. The update is carried out automatically after the APROL installation if the JasperReport server was already installed and configured on the server in an older APROL release. If the APROL system software is update to R 4.0-07, the standard theme must be changed manually to the new APROL theme.
If the APROL system software is installed for the first time, the new theme is set per default.
Detailed information can be found in manual 'X14 Jaspersoft reports in APROL - Installation guide English', chapter 'Changing the theme after an update'.
Upgrade notes 1-1
Illustration 1: Changing the JasperReport theme
1.3.4 Display of company logos in the as-built documentation The system stores changes to the master data of the CAE project, libraries, and project parts in the CAE database and uses them for the creation of the as-built documentation. The as-built documentation can be extended by a user when configuring the project parts. The as-built documentation is saved in XHTML format, and its content can be shown in a web browser.
Because of a change of the internal format, a company logo could not be displayed if it was stored and linked in the CAE database. The company logo must be re-assigned and saved in the project/library properties ('Master data' tab) in order to ensure that the company logo is shown in the as-built documentation.
1.3.5 Checks after an incorrect shutdown of an APROL server/system The APROL databases and the ChronoLog containers are now also checked and eventually repaired after an APROL server/system has been shutdown incorrectly. The incorrect shutdown of an APROL server by a simple loss of power, for example, leads to a loss of data and an inconsistent state. The check detects and repairs possible damage in these components. This is necessary, because all of the files which were just being written during the power loss may be zeroed.
A3 Upgrade Notes 1-2 Backup copies are created during the check, and must be removed by the user if they are no longer needed.
APROL databases: The backups (with additional time stamp) are stored in the original directory parallel to the existing databases.
ChronoLog container: The Backups are stored in the following directory: /home/aprolsys/APROL_DATA/defect
The log files in /var/log/incorrect_shutdown.dat contain a list of the checks and actions which have been carried out.
Detailed information can be found in manual 'B5 Download and Debugging', chapter 'Reaction to incorrect shutdown'.
1.3.6 Access of Historical Data via SQL It is possible to query and evaluate APROL historical data via the APROL SQL server and an SQL client. The following additions / optimizations have been made in APROL R 4.0-07:
Processing of sub-queries: SQL statements with sub-queries which were in the context of IN, EXISTS or ANY/SOME/ALL expressions are not carried ot correctly.
Rounding floating point to string conversions: There was only three places after the comma when converting floating point numbers to strings. The procedure has been set to the normal APROL behavior of 15 places after the comma.
Correction when using the DECIMAL data type: There may have been an ODBC error message when using the DECIMAL data type for accessing column definitions (i.e. in a table definition file with the 'json' suffix).
Processing of Boolean expressions without column reference: SQL statements with Boolean expressions which do not have column references are now carried out correctly.
1.3.6.1 Update of the AprolSqlServer driver The SQL server framework has been updated. The old Simba driver must be uninstalled, re-installed, and configured on Windows computers, because of a framework upgrade. The JDBC database driver must be reconfigured both in Linux and Windows.
Upgrade notes 1-3
1.4 New features after updating to APROL R 4.0-06 Amongst various corrections, the following additions are contained in APROL R 4.0-06:
1.4.1 Controller AR-OS versions The AR-OS versions P0309 (Default), H0406 and I0406 (Default) for Atom processors are available in the scope of APROL R 4.0-06. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version I0408 (necessary for redundant controllers) is also supplied. The current Automation Studio versions 4.0.16.81 SP and 4.1.4.281 (necessary for redundant controllers) for the controller hardware configuration are supplied in APROL R 4.0-05. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
1.4.2 New features in the AutoYaST DVD V4.0-060 The new AutoYaST DVD version 4.0-060 is necessary for APROL R 4.0-06, and contains the following changes:
Kernel update to version 3.0.101-0.29.2 Adoption of the library 'libedit0 3.0.snap20140213-3'
1.4.3 Access of Historical Data via SQL
1.4.3.1 Optimization of SQL queries by the AprolSqlServer
The AprolSqlServer can speed up 'group by' queries considerably.
In doing so, the following must be noted: 1) An accelerated query is only then possible if columns are accessed in the 'group by' query where the content is detected by using of the ChronoLog identifier.
Example query: SELECT pv from Alarm GROUP BY pv In this case, 'pv' is part of the identifier of the corresponding ChronoLog data record.
A3 Upgrade Notes 1-4 2) A performance gain with trend queries is only then possible when the column 'pv' is accessed in the 'group by' query.
Example query: SELECT pv from Trend GROUP BY pv 3) Queries can only be accelerated if the 'group by' aggregation is executed before a filter command.
Example query: Optimization: SELECT pv FROM Trend GROUP BY pv HAVING pv LIKE 'Value%'
No optimization: SELECT pv FROM Trend WHERE pv LIKE 'Value%' GROUP BY pv
'DISTINCT' queries cannot be accelerated by the AprolSqlServer. Example: 'SELECT DISTINCT pv FROM Alarm' delivers the same amount of results as the query in 1). Even so, the processing of the 'DISTINCT' queries takes much longer.
1.4.3.2 Update of the AprolSqlServer driver The SQL server framework has been updated. The old Simba driver must be uninstalled, re-installed, and configured on Windows computers, because of a framework upgrade. The JDBC database driver must be reconfigured both in Linux and Windows.
1.4.4 Extended use of ST/SFC blocks in CFCs
You have the possibility to comfortably define your own data types and constants in the context of the CAE library with the 'Library Type Definition' project part, which can be used in the different programming languages of the APROL system. The 'Library Type Definition' project part is abbreviated with 'LTD' in the following.
ST and SFC blocks can be used in ST/SFC programs, CFCs, and hyper macros. In order to be able to use LTD data types and LTD constants in ST/SFC blocks, it is necessary to automatically create the corresponding ST/SFC block header files which are used in the CFCs. In this case, it is necessary that the header files from LTD definitions are included in the correct order.
All of the CAE libraries which are used in the LTD definitions have a priority and are determined for this purpose when an ST/SFC block is saved.
Upgrade notes 1-5
All libraries and all LTD project parts have obtained a priority, which results in the order in which the necessary ST/SFC block includes are created. These priorities are taken into account for the build process in the CAE. The user can change the priority if a problem occurs with the order of the included header files. The priority is specified in the master data of the 'LTD' project part and CAE library. The LTD priority overview can be opened for each library from the master data of an 'LTD' project part with the [Priority] button, and in the context of the CAE library via the 'Edit / LTD Priority' menu entry. A library priority overview is opened in the properties of the CAE project, 'Libraries' tab. The respective blocks must be re-saved if problems occur with ST/SFC blocks which are placed in CFCs, because LTD definitions are not known. The dependent libraries are determined by doing so. The necessary definitions are then announced when the CAE library is built.
A3 Upgrade Notes 1-6 1.5 New features after updating to APROL R 4.0-05 Amongst various corrections, the following additions are contained in APROL R 4.0-05:
1.5.1 Controller AR-OS versions The new AR-OS versions P0309 (Default), H0406 and I0406 (Default) for Atom processors are available in the scope of APROL R 4.0-05. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS versions G0408 and I0408 (necessary for redundant controllers) are also supplied. The current Automation Studio versions 4.0.16.81 SP and 4.1.4.242 (necessary for redundant controllers) for the controller hardware configuration are supplied in APROL R 4.0-05. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
1.5.2 Access of Historical Data via SQL The SQL server framework has been updated and the string length of the different columns has been reduced to the size which is actually used. The maximum specified VARCHAR length is 255. Furthermore, the LONGVARCHAR(32767) type is given to columns which can contain longer strings. Columns in the tables UseractionSys, UseractionController and UseractionParameter have also been converted from VARCHAR to the suitable types INTEGER or TIMESTAMP. The old Simba driver must be uninstalled, re-installed, and configured on Windows computers, because of a framework upgrade. The JDBC database driver must be reconfigured both in Linux and Windows. The 'AprolConfigJasperReportsServer -- configure' script must be executed in order to supply the JasperReport server with the new drivers.
1.5.3 Uniform nomenclature for bit-coded system variables The nomenclature of the bit-coded system variables has been standardized and now has the suffix '_BC' to identify the bit-coded variables. Old name: New name: NTPStatus NTPState_BC UPSStatus UPSState_BC MySQLReplication MySQLReplicationState_BC ControlBusClusterStatus ControlBusClusterState_BC ProcessBusClusterStatus ProcessBusClusterState_BC GlobalClusterStatus GlobalClusterState_BC
Upgrade notes 1-1
Please note that the following non-bit-coded variables contain the same information as the above mentioned bit-coded variables which will be dropped in a future APROL release. Only the bit-coded variables should be used.
- NTPTimeSourceConStatus - MySQLReplicationStatus
Please re-activate all APROL systems in order to activate the new nomenclature. If the system variables which were introduced in APROL R 4.0-02 are in use, the corresponding CFCs must be adjusted.
1.5.4 Validity of the 'SysDataTransfer' transfer file The APROL 'SysDataTransfer' system service has obtained a new parameter: New option: -durationOfValidity
1.5.5 Selecting an APROL system in the ParameterCenter The ParameterCenter has obtained additional functionalities in the scope of the support for multi-runtime systems. Together with the above mentioned additions, the '-downloadRestart' and '-iosys' launching parameters have been removed from the ParameterCenter. The '-system
A3 Upgrade Notes 1-2 1.6 New features after updating to APROL R 4.0-04 Amongst various corrections, the following additions are contained in APROL R 4.0-04:
1.6.1 Controller AR-OS versions The new AR-OS versions M0309 (Default) and H0406 (Default for Atom processors) are available in the scope of APROL R 4.0-04. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version G0408 (necessary for redundant controllers) is also supplied. The current Automation Studio versions 4.0.16.81 SP and 4.1.4.213 (necessary for redundant controllers) for the controller hardware configuration are supplied in APROL R 4.0-04. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
The new AS variation (AS41) must be selected for the redundant 'Controller' project part configuration, because the 'REDU' AS variation has been dropped. The selection is made with the 'Module Configuration / AS Hardware configuration (select AS variation)' context menu in the 'Hardware configuration' tab.
1.6.2 New features in the AutoYaST DVD V4.0-040 The new AutoYaST DVD version 4.0-040 is necessary for APROL R 4.0-04 and contains the following changes:
Package 'gtk-vnc' (to connect directly to the VNC server on the controller)
1.6.3 Access of Historical Data via SQL The SQL server framework has been updated. The old Simba driver must be uninstalled, re-installed, and configured on Windows computers, because of a framework upgrade. The JDBC database driver must be reconfigured both in Linux and Windows.
Furthermore, the following new features are in APROL R 4.0-04:
Support for ARKPATH: The SQL server now supports the well-known arkpath function from ChronoLog, which allows access to a secured ChronoLog container.
Upgrade notes 1-1
Support for conversion operations: The SQL server now allows the use of the SQL conversion operation CAST. Example: SELECT * FROM base.Alarm WHERE CAST(base.Alarm.ts as TYPE_TIME) > '12:00:00' Change identifiers for switching from summer to winter (daylight saving): All database tables now also offer access to the ChronoLog change identifier for switching from summer to winter (daylight saving).
The identifier can be seen via the ts_switch_mark column of the type Varchar(1). Complete domain name: The JDBC driver URL configuration now demands a complete SQL server domain name (Fully Qualified Domain Name (FQDN)).
1.6.4 Replacement of APROL-specific constants from the 'runtime' AS library Because of system-internal adjustments, the 'runtime' AS library constants with the name 'rt_xxx' have become obsolete and must be replaced with the general AS constants if they are in use. The following constants must be replaced: removed constant: replaced by constant: rt_ERR_FUB_BUSY ERR_FUB_BUSY rt_ERR_FUB_ENABLE_FALSE ERR_FUB_ENABLE_FALSE rt_ERR_NOTIMPLEMENTED ERR_NOTIMPLEMENTED rt_ERR_OK ERR_OK
If the 'rt_xxx' constants are in use, they must be replaced before a 'Build (library)', because the build process will otherwise abort!
1.6.5 Self ID for the 'EmbeddedApp' visualization element The 'EmbeddedApp' visualization element allows APROL applications to be embedded in a process graphic or faceplate.
A3 Upgrade Notes 1-2
Illustration 2: Embedding an SFCViewer in the APROL visualization
The fundamental APROL frontends (TrendViewer, CFCViewer, SFCViewer, ParameterCenter, ControllerManager, OperatorManager, TranslationManager, StartManager) can be displayed and operated directly in the frame of the 'EmbeddedApp' widget, in the process graphic or faceplate, by using the '-embed %1' option. The application is started according to its respective start options in the intended widget when it is displayed in a process graphic or faceplate as an embedded application. It is then closed when the graphic is changed, and started again when the process graphic is shown once more. Thus, it should be noted that there is a slightly longer waiting period and the system load rises for a short time.
As of APROL R 4.0-04, there are the following additions: The DisplayCenter creates a unique self ID if the '-embed %2' option is used, in order to guarantee the unique identification of an 'EmbeddedApp', and that its user-specific settings can be saved. The self ID has the following structure:
DCEmbed_
A3 Upgrade Notes 1-4 1.7 New features after updating to APROL R 4.0-03 Amongst various corrections, the following additions are contained in APROL R 4.0-03:
1.7.1 Controller AR-OS versions The new AR-OS versions M0309 (Default) and G0406 (Default for Atom processors) are available in the scope of APROL R 4.0-03. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version F0408 (necessary for redundant controllers) is also supplied. The current Automation Studio versions 4.0.16.81 SP and 4.1.4.189 (necessary for redundant controllers) for the controller hardware configuration are supplied in APROL R 4.0-03. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
The new AS variation (AS41) must be selected for the redundant 'Controller' project part configuration, because the 'REDU' AS variation has been dropped. The selection is made with the 'Module Configuration / AS Hardware configuration (select AS variation)' context menu in the 'Hardware configuration' tab.
1.7.2 AutoYaST DVD V4.0-030 update The new AutoYaST DVD version 4.0-030 is necessary for APROL R 4.0-03 and contains the following changes:
- Update of the UPS tools - Update of the Flash player - Update of the JAVA runtime environment - Updates in openssl - Update of the 'monit' tool for system monitoring - Added: Linux tools for system and process monitoring (atop, ftop, iftop, htop)
The notes in Update einer bestehenden AutoYaST must be taken into account when updating AutoYaST from V3.6-060 / 3.6-070 / 3.6-080 / 3.6-090 to the current AutoYaST DVD V4.0-010!
Upgrade notes 1-1
1.7.3 System variables for downloads to controllers Up-to-now, it was necessary to create a 'Device-free connection' in an 'APROL system' project part to make variables available to controllers which were assigned to that 'APROL system' and which contained information about downloads to the controller.
As of APROL R 4.0-03, the system variables '
All affected 'APROL system' project parts of the type 'Runtime' must be reactivated in order to create the new system variables.
1.7.4 Buffering and subsequent provision of log entries during a disturbed recording In certain situations, there may be disturbances with components such as APROL system messages or alarm events, when logging entries are transferred by the ChronoPlex service. The following causes are possible: The ChronoPlex service is not running
'Defect' ChronoLog container
Apart from the loss of logging entries in these cases, there may have also been a blocked application in the worst case. Disturbances of this kind can be bridged with a buffer as of APROL R 4.0-03, and the blocking of an APROL application due to a disturbed recording is avoided. The buffering takes place at first in an application-internal memory for over 10,000 entries (e.g. system messages, alarms). If this buffer is overrun, the entries are stored in files which are in the form of a ring buffer. A buffer for 100,000 more entries is thus available. After the disturbance has ended, the buffered logging entries are provided subsequently in chronological order. You can also compare this with manual 'D2 System Manual', chapter Diagnosis of the buffering of logging data.
A3 Upgrade Notes 1-2 1.8 New features after updating to APROL R 4.0-02 Amongst various corrections, the following additions are contained in APROL R 4.0-02:
1.8.1 Controller AR-OS versions The new AR-OS versions M0309 (Default) and G0406 (Default for Atom processors) are available in the scope of APROL R 4.0-02. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version E0408 (necessary for redundant controllers) is also supplied. The current versions 4.0.16.81 SP and 4.1.4.142 (necessary for redundant controllers) of Automation Studio for the controller hardware configuration are supplied in APROL R 4.0-01. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
The new AS variation (AS41) must be selected for the redundant 'Controller' project part configuration, because the 'REDU' AS variation has been dropped. The selection is made with 'Module Configuration / AS Hardware configuration (select AS variation)' context menu in the 'Hardware configuration' tab.
1.8.2 AutoYaST DVD V4.0-020 update As of APROL R 4.0-02, the new enhancements are made available with the new AutoYaST DVD V4.0-020. The following changes, amongst others, are available:
Kernel update to 3.0.101-0.15.1 Firefox update to 24.3.0 ESR SSL for Monit activated Modified 'nut' UPS driver for APCs
The notes in Update einer bestehenden AutoYaST must be taken into account when updating AutoYaST from V3.6-060 / 3.6-070 / 3.6-080 / 3.6-090 to the current AutoYaST DVD V4.0-010!
Upgrade notes 1-1
1.8.3 Configuration of the AprolJobDispatcher As of APROL R 4.0, the transfer of user and operator data into an LDAP server was greatly simplified. The 'AprolJobDispatcher' takes over the job of importing the data into the LDAP server.
The AprolJobDispatcher configuration has been simplified in R 4.0-02. A checkbox specifies if the server offers the transfer directory via NFS and the main database for jobs. If the checkbox is not activated, the intended server host name must be entered. Due to an changed AprolConfig configuration, the 'Job dispatcher' configuration aspect must be reactivated once again. Additional rights are added and eventual missing rights are corrected for the AprolJobDispatcher transfer directory.
1.8.4 Assignment of the minimum password length Up-to-now, a password minimum length could be entered in the LDAP password policies. Users could no longer be imported into the LDAP server if the rule was activated. This configuration is no longer possible. The minimum length of passwords can now only be set in the CaeManager, via the 'Extras / Global Engineering Options / Security Options' menu item. The minimum password length which is entered here applies to APROL operators and CAE users.
1.8.5 Use of the 'AprolCaeRename' script Block pins, hyper macro constants, and instance names can be renamed in all of the existing versions of a library block with the 'AprolCaeRename' service script.
Use of the substitution identifiers for global variables in blocks: If blocks for global variables are used in a hyper macro, substitution identifiers can be used in the instance names of AprFuIn and. AprFuOut in order to generate the PV names. A substitution above and beyond a nested hyper macro level is also possible. The 'AprolCaeRename' script cannot be used for renaming these substitution identifiers. It is ensured that the value of a substitution identifier will not be lost if hyper macro instances are renamed. If the instance identifier of a global variable block is changed manually in the CaeManager, the customer must also adjust all places where the substitution identifier is used manually.
1.8.6 Provision of bit-coded system variables In addition to the special status information of the UPS, NTP, cluster, and MySQL replication configuration aspects, system variables which contain all of the information in bit-coded form have been made available in APROL R 4.0-02. All of the following system variables are of the IEC data type WORD:
A3 Upgrade Notes 1-2 System variable Explanation: Processing the information from:
Bit 0 = Configuration value valid Bit 1 = Live value valid Bit 2 = Configured (is also 0 upon erroneous configuration) Bit 3 = Erroneous configuration Bit 4 = Partner can be reached Bit 5 = Replication OK Bit 6 = Replication active
Bit 0 = Configuration value valid Bit 1 = Live value valid Bit 2 = redundant system Bit 3 = Cluster configuration necessary Bit 4 = Cluster configured Bit 5 = Cluster address can be reached Bit 6 = Cluster is local Bit 7 = Cluster is on partner
Key:
A corresponding decoder block is available for a comfortable preparation of the information. The following decoder blocks are available in the 'APROL' CAE library, in the 'ControlComputerFunctions/SystemVariables' group:
AprUPSState (for bit-coded information about the UPS status) AprNTPState (for bit-coded information about the NTP status) AprMySQLReplicationState AprClusterState
Upgrade notes 1-3
1.8.7 Extension of the SNMP diagnosis for redundant controllers The SNMP diagnosis in the ControllerManager has been extended with new attributes for controller redundancy. The new 'Redundant', 'AnslPort-Nummer', 'ProcessControlState', 'SwitchOverLevel', 'InterfaceHostname', 'ClusterIpAddress', 'ClusterSubnetMask', 'ClusterHostname' and 'ParterMacAddress' fields are now available.
1.8.8 Change of CSV export in the TranslationManager The separator in CSV exports of PO files from the TranslationManager has been changed. The '#' character is now used as separator, in order to avoid problems when importing into 'oocalc' or 'Microsoft Excel'. This must be taken into account when importing into 'oocalc' or 'Microsoft Excel'. The ',' (comma) is still used as column separator.
1.8.9 Support of internal UPS modules for APC810/APC910 The UPS driver now recognizes the existing APC hardware (APC810 bzw. APC910) automatically. The APC910 hardware does not currently supply values for the remaining battery capacity, i.e. the UPS variable 'ups.BatteryCapacity' delivers the return value '-1'.
A3 Upgrade Notes 1-4 1.9 New features after updating to APROL R 4.0-01 Amongst various corrections, the following additions are contained in APROL R 4.0-01:
1.9.1 Controller AR-OS versions The new AR-OS versions M0309 (Default) and G0406 (Default for Atom processors) are available in the scope of APROL R 4.0-01. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version E0408 (necessary for redundant controllers) is also supplied. The current versions 4.0.16.81 SP and 4.1.3.0 (necessary for redundant controllers) of Automation Studio for the controller hardware configuration are supplied in APROL R 4.0-01. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
1.9.2 New features in the AutoYaST DVD V4.0-010 As of APROL R 4.0-01, the new enhancements are made available with the new AutoYaST DVD V4.0-010. The following changes, amongst others, are available:
The 'fcitx' tool used up-to-now for inputting Chinese characters, for example, has been replaced with the new 'uim' tool.
The Java version from SUN has been replaced with the Java version from IBM. Firefox update to 17.0.10 ESR Kernel update to 3.0.101-0.8.1 Integration of the 'monit' tool for system monitoring Provision of language switching in APROL for Korean (082)
The notes in Update einer bestehenden AutoYaST must be taken into account when updating AutoYaST from V3.6-060 / 3.6-070 / 3.6-080 / 3.6-090 to the current AutoYaST DVD V4.0-010!
1.9.3 Driver for NVIDIA graphic cards Incomprehensible problems occur in the Linux system with the current long-term NVIDIA graphic card driver version 331.20. Amongst others, the VMware cannot be started, the computer freezes for 10-20 seconds when the screensaver is active, and the key combination [Ctrl] + [C] does not work. Upgrade notes 1-1
It is recommended to use the short-term driver with version 325.15. Because of existing license conditions, it is not contained in the scope of the APROL delivery, but can be downloaded with the following URL: http://de.download.nvidia.com/XFree86/Linux-x86_64/325.15/NVIDIA-Linux-x86_64- 325.15.run
1.9.4 Update of the AprolSqlServer driver The SQL server framework has been updated. The old Simba driver must be uninstalled on Windows computers before the new driver is installed and configured, because of a framework upgrade. The JDBC database driver must be reconfigured both in Linux and Windows.
1.9.5 Reactivation of all APROL systems The reactivation of all 'APROL system' project parts is necessary because of the changes to the launching options of the CC modules and the provision of additional system variables. Note: Warnings which point out the obsolete '-downloadRestart' StartManager option are output if the reactivation is not carried out. The AnslDriver is started with different options, depending on the fact that it is connected to a single or redundant controller. If a driver is configured automatically, the launching options are adjusted automatically during the reactivation and compiling of an APROL system, depending on the configured controller. Furthermore, there are new diagnosis variables for the AnslDriver, which are available after a reactivation of the APROL systems.
1.9.6 Use of the BR modules needed by the 'PAL' CAE library If the functionalities of the 'PAL' CAE library are already used in existing projects, it is necessary to transfer the required 'MTBASICS' and 'MTFLOW' BR modules which are required by the 'PAL' library to all existing controllers. After the APROL system software has been updated, all controllers must be opened once and saved again, so that BR modules are added automatically. Subsequently, a compilation, build, and download must be carried out.
1.9.7 Update of optional hardware upgrades Extensions and corrections for hardware modules which have already been delivered in Automation Studio are available via hardware upgrades which can be imported into AS. Hardware upgrades which are absolutely necessary for a smooth operation in the current APROL release will be automatically updated when the AS/HW configuration is opened in the CaeManager.
A3 Upgrade Notes 1-2 A manual installation of the optional HW upgrades can be carried out in APROL to update other hardware modules which are used in existing projects Proceed as follows: 1) Call up the 'Extras/Configure Windows (VMware)' menu item in the CaeManager. 2) Open Automation Studio (AS) in the VMware. 3) Press the [Cancel] button in the HW selection dialog. 4) Start the BR Automation Studio upgrade with 'Tools / Upgrades ...' in AS.
5) Navigate to the z:\APROL directory in the 'Local' tab and select the 'HW_Upgrades_STD' directory. 6) All available HW upgrades are shown after confirming with [OK]. 7) Select the desired HW upgrades and install them with 'Install selected upgrades'. 8) After a successful installation, Automation Studio should be closed and a new snapshot must be created in the CaeManager.
Only select modules which are used in the project. It is unnecessary to install all of the available optional HW upgrades, and depending on the hardware this may take a considerable amount of time.
1.9.8 Creation of the exclude files for the optimization of the RRAD configuration framework Function blocks which are used in hyper macros or CFCs and have their inputs marked as being 'redundancy-relevant' must not be aligned in a redundant environment. This is only necessary if the function blocks are used in an ST/SFC project part. As of APROL R 4.0-01, the above mentioned inputs are summarized in an exclude list for the creation of the RRAD configuration, and are no longer taken into account when the configuration is created, so that the number of variables which are to be aligned between the redundant controllers is reduced and optimized.
1.9.9 SVG check during an import into the image container The remarks and limitations mentioned in the documentation in APROL should be taken into account when creating and adopting SVGs, amongst others, because of about the rendering engine used. Detailed information can be found in manual 'B2 Project Engineering', chapter Special features when creating a graphic object The image containers have a new check function during an SVG import, in order to check the use in APROL and prevent possible problems and output warnings or error messages for the respective SVG. The image container check can also be triggered manually.
Upgrade notes 1-3
The following SVG tags are currently checked: 1) Using of
The use of
2) Use of
SVGs which have
1.9.10 Library-spanning Export / Import of library blocks If a library block is exported and imported in another CAE library, the assigned block icons are adopted in the target library, so that the same block icon is shown. 1. A conflict entry, which must be resolved manually, is made in the image container if a block icon with the same name exists in the target library, but has a different content. A message in the project part (blue icon) points this out. 2. Block icons always originate from the image container in the same library as the block. If the icon import file has been manipulated to point to another image container, the block icon is discarded with the appropriate message.
1.9.11 SFC: Display of the live values for array variable elements In the scope of the SFC debugging, an overview of the local variables can be opened in the SFCViewer. The view also shows the live values for each variable. Array variables can also be created as local variables in SFC function blocks. As of APROL R 4.0, a list of all array elements and the corresponding live values is now also shown in the local variable listing.
1.9.12 Preview of the 'Color' dynamization type The preview of color dynamization has been completely redesigned in APROL R 4.0. An evaluation of the effect on foreground and background color, line type, and fill pattern can be made during the configuration with a new preview in the list of color dynamizations. The new preview contains examples for different object types such as lines, areas, and widgets.
A3 Upgrade Notes 1-4 Object properties can also now be varied, with respect to the existing properties, and the resulting display checked in the preview.
1.9.13 Filter function in the alarm report via APROL system It became necessary to specify information about the source runtime system in the alarm data records, because of the support of multi-runtime systems as of APROL R 4.0, in order make the respective filtering in the reports possible. The system instance and name are now available in the ChronoLog data records and via the APROL SQL interface. The alarm report has been extended with the name and instance of the runtime system and now offers the possibility to filter this information comfortably.
Upgrade notes 1-5
1.10 New features after updating to APROL R 4.0-00 Amongst various corrections, the following additions are contained in APROL R 4.0-00:
1.10.1 Minimum release for an upgrade to APROL R 4.0-00 The engineering system must have a 'minimum APROL release' of R 3.6-06 in order to be able to upgrade to APROL R 4.0-00. A controller that was last edited with an Automation Studio V3.0.81.xy cannot be updated automatically to the version 4.0.
It is necessary to actualize the controller project parts once by using the Automation Studio (AS) version AS 3.0.90.12 (or higher) that is integrated in APROL R 3.6-05. For this purpose, the project parts must be opened, the 'AS/SD Hardware Configuration' must be started, and a re-build must be carried out in that AS.
1.10.2 AutoYaST installation .
1.10.2.1 APROL uninstallation before AutoYaST update If an AutoYaST update to V4.0-000 (contains, amongst others, the operating system update to SLES 11 SP3) is carried out from an installed APROL < R 3.6-08, then the installed APROL system software can no longer be executed. This is due to a downgrade of the Python interface, which results in the APROL systems not starting properly after a reboot. This is the reason why the 'AprolPrepareUpgradeAutoYaST' scripts on the AutoYaST DVD demands that APROL is uninstalled beforehand.
The necessary uninstallation can be carried out with 'AprolInstall -deinstallAprol'.
1.10.2.2 Updating an existing AutoYaST DVD The following steps must be carried out when updating an existing AutoYaST DVD from V3.6-060 / 3.6-070 / 3.6-080 / 3.6-090 to the current AutoYaST DVD V4.0-000: Due to the resolution of many package dependencies, B&R provides the 'AprolPrepareUpgradeAutoYaST' script on the AutoYaST DVD that carries out the necessary conflict resolution by uninstalling the obsolete packages and installs those that are necessary. This script must be manually executed before the update.
Upgrade notes 1-1
Mount the AutoYaST DVD with the LINUX 'mount' command:
Example: mount -t iso9660
Detailed information about the 'AprolPrepareUpgradeAutoYaST' script can be found in chapter Update to the current AutoYaST version.
1.10.2.3 New features in the AutoYaST DVD V4.0-000: As of APROL R 4.0-00, the actual enhancements are made available with the new AutoYaST DVD V4.0-000. The current AutoYaST version contains, amongst others, the following changes: Integration SLES 11 SP3
New kernel 3.0.93
New X server 1.6.5 (1.11)
Update to PHP 5.3
AprolCluster / Keepalived as substitute for Heartbeat
Components for Dutch, Polish, Swedish, Norse, Finnish, Turkish, Lithuanian,
Portuguese, Danish, and traditional Chinese for Taiwan language switching. KDE 4.4.4
QT 4.8.5
boost 1.49
LibreOffice 4.0.3
APROL Possibility of uninstalling with the script 'AprolInstall'
1.10.3 Controller AR-OS versions The new AR-OS versions M0309 (Default) and F0406 (Default for Atom processors) are available in the scope of APROL R 4.0-00. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version B0408 (necessary for redundant controllers) is also supplied.
A3 Upgrade Notes 1-2 The current versions 4.0.16.50 SP and 4.1.3.0 (necessary for redundant controllers) of Automation Studio for the controller hardware configuration are supplied in APROL R 4.0-00. The current SafeDESIGNER version 3.0.16.262878 is supplied for the SafeLOGIC configuration.
1.10.4 Use of different Automation Studio variations in one engineering environment As of APROL R 4.0, different Automation Studio variations which have not been put into an official Automation Studio release can be used in order to support new functionalities of hardware engineering for controllers in APROL projects. One AS variation can be selected per controller, and is then used for the configuration of the controller. The selection of another AS variation is made in the 'Controller / Hardware configuration' tab, with the 'AS Hardware configuration (Select AS variation)' function, in the context menu of the 'Module configuration' entry. The selection is saved dependent to the versions in the 'Controller' project part, and displayed in the [AS/HW configuration] button.
The AS variation 'Standard' (default) and 'Redundancy' are supplied in APROL R 4.0. The 'Standard' variation is marked as the recommended AS variation, and is used
automatically when a new controller is created. The 'Redundancy' variation must be used explicitly for the configuration of a redundant
controller.
1.10.5 Change of VMware on Windows 7 Professional The VMware used for the controller hardware configuration has been switched from 'Windows 7 Home Premium' to 'Windows 7 Professional'. Customers are offered the possibility to post-install the old VMware on systems with an existing Windows 7 Home Premium license because a new license is necessary for the version 'Windows 7 professional'. A separate DVD named 'APROL_DVD-R4.0-VMimage_V1.2.iso' has been provided for this purpose and installs the old VM image in /opt/aprol/AS/VMIMAGE after calling 'AprolInstall'. The subsequent installation of the old VMware must be carried out after each update, when it is required, because the current VMware is always installed with 'Windows 7 professional'.
1.10.6 Update of the MySQL version The MySQL version has been updated from version 5.0.94 to 5.5.33
Upgrade notes 1-3
The MySQL database of existing projects which have parameter sets saved in the runtime must be converted according to the following steps and 'BuRMySqlBackup' program:
Before the upgrade to APROL R 4.0-00: Step Description 1 Create a backup of all relevant parameter management data from MySQL. In the case of the parameter management data, this can be carried out with the supplied 'BuRMySQLBackup' program. It is necessary to execute the program once for each runtime system as Linux super user 'root' and as follows: BuRMySQLBackup -backup -hostname
Upgrading from MySQL 5.0 to 5.1: https://dev.mysql.com/doc/refman/5.1/en/ upgrading-from-previous-series.html
Upgrading from MySQL 5.1 to 5.5: https://dev.mysql.com/doc/refman/5.5/en/ upgrading-from-previous-series.html
After the upgrade to APROL R 4.0-00: Step Description 1 Stop the MySQL daemon as Linux user 'root' /etc/init.d/mysql stop 2 Delete the /var/lib/mysql directory as Linux user 'root' rm -rf /var/lib/mysql 3 Start the MySQL daemon as Linux user 'root' /etc/init.d/mysql start 4 Set up the parameter management database as Linux user 'root' AprolConfigParameterMgmt --update 5 Restore the backed up parameter management database as Linux user 'root' BuRMySQLBackup -restore -timestamp
A3 Upgrade Notes 1-4 Step Description 6 Set up the replication, if the runtime system is redundant: The replication setup can be carried out as usual with AprolConfig. 7 Handling of customer databases: Restore customer databases. Pay attention to the notes in the MySQL documentation about a database upgrade to MySQL 5.5
1.10.7 Change of the logging path for trend data The local logging of trend data by the TrendServer is now made in a different directory, because of the scope of the extensions for multi-runtime systems. Directory up-to-now: /home/aprolsys/APROL_DATA/chronotrend/
New directory: /home/aprolsys/APROL_DATA/chronotrend/
The following adjustments are necessary, because of the changes: Access to trend data from application-specific scripts (e.g. backup scripts) and UCB blocks must be adjusted to the new directory.
The URLs for opening trend data reports, which are stored as bookmarks in a browser for example, must be adjusted.
In the 'runtimesystem' CGI parameter,
1.10.7.1 Detecting the instance of the runtime system The following possibilities are offered for detecting the runtime system instance and the current project name:
'GetEnvi' call: GetEnvi -aprolsystem Instance of the current APROL system GetEnvi -assigned_aprolsystem Call in operator or gateway systems: Instance of the assigned runtime system Upgrade notes 1-5
GetEnvi -project_name Name of the CAE project
If the -silent and -noheader options are used, the rest of the text output of GetEnvi is switched off and reduced to the queried information.
Use of the corresponding system variables:
1.10.8 Change of the database structure
Font selection list and image container: The basic paths of the font selection list and the image container have changed in the CAE project. Note: Due to the structure change, the entire CAE project and all project parts are no longer compatible for imports or exports with older releases. Due to the plausibility check when importing from older releases, the import is prohibited for R 4.0-00.
Blocks in the CAE library: The APROL R 4.0 CAE library blocks now have new attributes for redundancy capability, redundancy relevance, translatability of the string inputs, and assigned block icons. APROL system: As of APROL R 4.0, the selection of an APROL system type (runtime / operator / gateway) is made once when the project part is created. A subsequent change of the selected type is not possible.
Changed handling of the PAL modules: The database structure of AR upgrades had to be changed, because of the PAL modules which are now no longer contained in the AR, but are contained in the APROL 'PAL' library as library modules. Note: An AR-OS upgrade for an APROL R 3.6 can therefore no longer be used in an APROL R 4.0-00, or vice versa. The relevant ARs for both APROL releases are thus supplied separately. A3 Upgrade Notes 1-6
1.10.9 Limitations with the names of customer-specific ChronoLog FIFOs and containers The name which is configured on the input of the 'fifo' pin on an 'AprCcTrigRec' block () must now correspond to the 'ChronoLogCustomerFifo' validator. This validator only allows the input of alpha-numeric characters and expects the prefix 'custom_'. One exception is the 'triggered' default value of the block. This is still allowed. If the block or a copy is being used in the CAE project or customer library, the constant value of the 'fifo' input must be checked for its validity and eventually adjusted. If used in a hyper macro, the connected constants and default values must also be checked and eventually adjusted. If FIFO names were changed, the ChronoPlex configuration must be adjusted and a new container created with 'AprolConfig'. The name of the ChronoLog container in the file system is the same as the name of the FIFO with the file ending '.clc'. The records up-to-now are to be adopted in the new container on the runtime server
in the directory /home/aprolsys/APROL_DATA/chronolog with the following command:
ChronoLog
1.10.10 Cancellation of the APROL 'DCS' library The 'DCS' CAE library, up-to-now of the type 'APROL (B&R)', has been dropped in favor of the 'PAL' CAE library. The status of cancelled libraries is set to the type 'Customer' during an APROL R 4.0 upgrade if parts of the 'DCS' library (properties such as online rights also belong to this) are still being used in existing projects or libraries.
The responsibility for this library is then transferred to the customer, as of APROL
R 4.0, and only contains the project parts that are used by the customer.
If the customer has not used the CAE library, it is removed from the CAE database during the update.
1.10.11 Cleansing of the CAE library 'APROL' The 'AprFbAlarmSel' scalable block in the 'APROL' CAE library up-to-now has been deleted. The derived block variations must therefore be removed before upgrading to APROL R 4.0.
Alternatively, the script 'AprolSaveObsoleteBlocks' can be executed after the installation
of APROL R 4.0 and before opening the CaeManager for the first time , in order to move referenced blocks into a customer library named 'SavedBlocks' before the CAE database update takes place.
Upgrade notes 1-7
1.10.12 Removal of old images from process graphics and graphic blocks In older APROL releases, images and the background images of process graphics were saved in the respective project part. This sort of data storage was optimized with the introduction of the image container in an earlier APROL release, so that the use of the images only references one entry in the image container. If existing projects have images stored in the project parts, they are stored automatically in an image container in the path '__APROL_converted__' durinmg the CAE database update of APROL R 4.0. Process graphic background images are stored automatically in the sub-directory '__APROL_converted__/__BG_PICTURES__'.
1. The allocations of the images and background images should be checked after the update step and any unused images should be deleted. 2. The 'BG_PICTURES' directory (Previously Backgroundpictures), 'PB_IMAGES' (Images of the graphic blocks, and 'PIC_IMAGES' (Images of the process graphics) should be removed from the file system after having checked them. A gain in performance may be achieved because of the removal of obsolete data. 3. The obsolete images that remain in the paths of the project parts should be removed using the database optimization.
1.10.13 Switching of all icons to SVG format The use of icons in the pixmap based form such as PNG, XPM, GIF, etc. has been switched in favor of the general use of Scalable Vector Graphics (SVG). The icons used in existing CAE projects should be checked and switched to SVG.
The operator-specific toolbar in the DisplayCenter should be checked and any pixmap files that are being used are to be substituted with the respective SVG files.
The corresponding configuration files with the name
1.10.14 Extension of the master data The CAE project master data has been revised as follows: New 'Country' field
(necessary, amongst others, for a unique country allocation of digital signatures in PDF documents)
New 'State' field and division of 'Zip code' and 'City' in two separate fields. 'Description', 'Project manager', 'Client', and 'Company name' change to mandatory fields.
A3 Upgrade Notes 1-8
The address data in the user and operator management was newly structured together with the extension of the 'Project master data'. The 'Contact address' field has been dropped, and all address parts (street, zip code, etc.) are now stored separately. All address-related data is necessary for the users and operators to be able to create digital signatures for PDFs. All existing users and operators are marked as 'incomplete' after the CAE database
update to APROL R 4.0. The master data of the users and operators must be completed in order to be able to use the 'Digital Signature for PDFs' functionality.
Detailed information about digital signatures can be found in manual 'D1 System Manual', chapter Digital signatures in PDF documents.
1.10.15 Substitute blocks for discontinued blocks of the 'APROL' CAE library Blocks in the 'APROL' CAE library which have been discontinued for some time have been removed in APROL R 4.0, and replaced by the named substitution blocks. Group 'Bit Functions': Block up-to-now: Replacement block: AprFuGetLSB_BYTE AprFuGetLsbBYTE AprFuGetLSB_WORD AprFuGetLsbWORD AprFuGetLSB_DWORD AprFuGetLsbDWORD AprFuGetLSB_LWORD AprFuGetLsbLWORD AprFuGetMSB_BYTE AprFuGetMsbBYTE AprFuGetMSB_WORD AprFuGetMsbWORD AprFuGetMSB_DWORD AprFuGetMsbDWORD AprFuGetMSB_LWORD AprFuGetMsbLWORD
Group 'Control Computer Functions': Block up-to-now: Replacement block: AprFuPicConBool AprFuPicConBOOL AprFuPicConString AprFuPicConSTRING
Group 'Trend': Block up-to-now: Replacement block: AprFbDelTrd AprFbTrdCtrl
Upgrade notes 1-9
If the above mentioned blocks are still being used in CAE projects, the following
script must be executed as an engineering user before an upgrade to APROL R 4.0.
AprolExchangeDiscontinuedBlocks --dbpath
1.10.16 Reactivation of the VNC configuration after an upgrade from APROL release < 3.6-08 After updating from an APROL release <= 3.6-08, it is necessary that the VNC configuration is saved again ('Reactivation' option), because of an internal change in format.
1.10.17 Exchange of applications in the KDE The current APROL release 4.0 uses the KDE version 4.4.4. Because of the update to KDE 4, it was not possible to adopt all applications which were in the KDE version 3. Applications which are no longer supported have been replaced with a corresponding KDE 4 application: Application up-to-now (KDE 3): New application (KDE 4): quanta bluegriffon kxmleditor XML Copy Editor OpenOffice.org Draw LibreOffice Draw kftpgrabber FileZilla Ethereal WireShark knmap Zenmap KJobViewer system-config-printer
1.10.18 Discontinuation of the ChronoChartPrinter and the 'old' Iosys web interface applications The 'ChronoChartPrinter' application and the old 'Iosys web interface' have been discontinued and are no longer supported as of APROL R 4.0. The time-controlled output of printouts via a ChronoChartPrinter entry in the crontab file can be replaced with an AprCcTrigReport block ('APROL' CAE library), which calls a suitable ChronoLog template. Please use the Iosys HTTP interface as an alternative to the Iosys web interface.
1.10.19 Provision of the cluster configuration for multi-runtime systems . A3 Upgrade Notes 1-10 1.10.19.1 Local cluster: An individual cluster IP must be selected in the 'APROL system' project part for each runtime system as it is now possible to execute several runtime systems of one CAE project on one runtime server as of APROL R 4.0. This is only relevant if the respective control computer is set up for redundancy.
During the CAE project update of redundant control computers, the cluster IPs are read
automatically from the control computer into a cluster list, and are then used by the APROL system.
If only the cluster name was previously used, the cluster IP address must be entered in to the cluster list of the control computer.
1.10.19.2 Global cluster The use of a logging or documentation server on a redundant control computer necessitates the configuration of a global cluster. A global cluster is also necessary for a redundant LDAP server.
An additional cluster name and cluster IP address are necessary for the 'global cluster'.
The cluster name and cluster IP address that are allocated must be entered in the 'Control computer' project part.
The corresponding configuration must be carried out in the new 'Global cluster' configuration aspect of AprolConfig. The AprolConfig aspect 'Heartbeat' that was used in the previous APROL release has been discontinued in this release.
Detailed information about local/global clusters can be found in manual 'A2 Getting Started', chapter Clusters for redundant runtime servers.
1.10.20 Use of the new Intel graphic driver The manufacturers of the graphic cards only offer new Linux kernel drivers that support one kernel mode. The graphic driver contacts the kernel, which tries to detect the make, type, and supported graphic modes of the monitors that are connected, and then reports this information back to the graphic card driver. The pre-requisite for a correct detection is a completely plugged monitor cable and a completely plugged DVI to VGA adapter (if necessary). It is no longer possible to use monitor resolutions that are no longer supported because the graphic card driver only supports the kernel mode. These resolutions can be configured in Sax2, but are ignored by the X server. The reconfiguration of the X server for recognized Intel graphic cards takes place with the command 'sax2'. The desired resolution can then be set in Sax2. If this configuration method is not successful, an Intel Legacy driver can be used for older computers such as the B&R APC 810, as of AutoYaST DVD V 4.0-000. In this case, it is necessary to switch off the 'Mode setting' in the kernel.
Upgrade notes 1-11
In order to do this, the 'nomodeset' option is added as kernel parameter to the /boot/grub/menu.lst file. The computer must then be started with the new kernel parameters. The 'nomodeset' option can also be set as boot option for test purposes when the computer starts. Kernel parameters that have been set are lost after an AutoYaST update and must be re- entered. The following command is now used for the configuration of the X server: sax2 -r -m 0=intellegacy The further configuration of the desired resolution takes place with Sax2.
The B&R APC 620 is no longer supported as of APROL R 4.0.
1.10.21 Uniform syntax for system variables in the engineering and runtime environments In the scope of the additions for multi-runtime systems, the nomenclature of the system variables have been standardized in the engineering and runtime environments, so that the instance name of the APROL system now always depicts a clear differentiation. New (uniform) syntax:
These names must be adjusted to the new nomenclature in all of the text configurations where the system variables have been entered explicitly. The following changes must be carried out: - TrendViewer configurations - ST / SFC code, in which the system variables are used and contain the explicit name of the system variables.
1.10.22 New 'Library Type Definition' project part You have the possibility to comfortably define your own data types and constants in the context of the CAE library with the 'Library Type Definition' project part, which can be used in the different programming languages of the APROL system.
The configuration of the data types and constants is done in the 'Variables' and 'Types' tabs with the IEC programming language 'Structured Text (ST)' according to IEC 61131- 3. The handling is the same as the program editors of the other ST project parts in APROL. It is thus possible to create definitions which are independent of the programming language and target system and which can be accessed by the CAE blocks function (C), function block (C), function (ST), function block (ST), function block (SFC), graphic block (Python), and UCB block (Python).
A3 Upgrade Notes 1-12 The files generated from the 'Library Type Definition' contain the constants and type definitions in the required form for the respective target language. Constants and structures can thus be stored and changed centrally in one project part with this type of declaration and definition for all project parts which use these 'Library Type Definitions'. The use of the 'Library Type Definition' project part is on requirement for creating an IEC- conform block.
Detailed information about the 'Library Type Definition' project part can be found in manual 'B3 CAE Library Engineering', chapter Library Type Definition.
1.10.23 Change of the APROL services' TCP ports The entire port range has been shifted in conjunction with the port extension for multi-runtime environments and the target of having a continuous range for the APROL service ports. The shift also made sense because the ports used up-to-now were in an area controlled by the IANA regulations. The port area of the APROL services (5204 - 5252) was shifted to the new area 55501 - 55621.
The ports used in APROL are also entered in the /etc/services file. A maximum of 16 AprolLoader ports per control computer hardware ('Control computer' project part) are possible. A maximum of 16 Iosys ports per control computer hardware ('Control computer' project part) are possible. This means that up to 16 CC-Accounts of the type 'Runtime system', 'Operator system', or 'Gateway system' can be created on one control computer hardware. This limitation applies over all projects. APROL APROL 1) An Iosys access from an R 3.6 (or lower) to an R 4.0 is possible, because an automatic port forwarding is carried out from the old ports to the new Iosys ports on the APROL R 4.0. 2) The port forwarding can be switched off on the APROL R 4.0 server with the 'AprolConfigureOldPortForward' script if required. The das Skript 'AprolConfigureNewPortForward' is made available to automatically set up the necessary port forwarding for an Iosys access from an APROL R 4.0 to an APROL R 3.6-03 (or higher). The script must be executed on the R 3.6 control computer.
1.10.24 Update of the VMware The VMware workstation has been updated to the version 10.0.0. A new license key is supplied to license the VMware work-station 10.0.0.
Upgrade notes 1-13
It has been possible, since the VMware version 8.0.1, to use an APROL engineering system in a VMware. The VMware 10.0.0 must be used for the host system in order to be able to use the VMware version 10.0.0 in a virtual machine (VM).
1.10.25 Driver system variables As of APROL R 4.0, the status variables of the configured CC driver are made available as system variables and can be placed directly on the input border of a CFC. A use of these status variables was possible up-to-now by placing a global variable block (AprFuIn
The nomenclature has been standardized in the scope of the provision of the system variables. If global variable blocks have been used, then a check must be made and the variable name, i.e. the instance of the block, must eventually be adjusted. If a device-free connection has been used, then all these must now be removed from the project and the border variables must be replaced with the system variables. No further warnings are shown about these variables not having an active provider after adjusting these system variables, because the system variables are supplied properly by the respective APROL system. All 'APROL system' project parts in which drivers are configured must be reactivated one time. A message is shown when the APROL system is activated, informing about the automatic conversion of existing project connectors with the same name to system variables.
1.10.26 Recording rate for PDA blocks A classification for quick or slow recording rates can be made via the 'rec_rate' input of a 'Block for process data acquisition' that uses the new 'RecordingRate' pin type. A 'Block for process data acquisition' can be created in the context of a CAE library via the 'File / New / Control System Block / Block for process data acquisition' menu. Data records from a slow triggering are stored in a different ChronoLog container as the data records from a fast triggering. Thus, data records that are written seldom (slow recording rate) can be stored for much longer periods, because the ChronoLog container then goes over to the ring buffer operation. Thus, it is possible to access data in the reporting that does not change often and lies further in the past, such as tariff data or monthly values.
A3 Upgrade Notes 1-14 The classification is understood as a prognosis, as the actual recording rate is specified through the signal that is configured on the 'trigger' input. The 'slow rate' setting should be chosen when there is a middle trigger frequency of less than one data record per day, otherwise the 'fast rate'.
1.10.27 Revision of the project and properties dialogs Changes made in the project and library properties are now marked by an icon in the tab of the page where the changes have been made. Possible errors are also marked with an icon in the head of the tab. The changes made can be overwritten with the [Restore Standard] or [Restore Standard for all tabs] buttons.
1.10.28 BuR Gateway connection B&R supplies standard and checked system connections in the form of the APROL connections. IN the scope of APROL R 4.0, the 'INA connection' which was known up-to-now and the new 'ANSL connection' have been combined to the 'BuR Gateway connection'. These can be combined to one entry because the configuration of the connections is identical. The engineering is made easier and more efficient in this way.
Illustration 3: BuR Gateway connection
It is also possible to choose between INA and ANSL in the configuration of the 'PDA connection'.
Illustration 4: PDA connection
An existing PDA connection can be selected in the in the '-pda' option combo box of the driver configuration of the InaDriver and AnslDriver, in the CC modules. Upgrade notes 1-15
This connection must be created and saved beforehand, so that it can be assigned here.
Illustration 5: Use of the '-pda' option in the CC modules
1.10.28.1 Change of EventDriver '-useLinkDir' option The name of the directory where the configuration file Link.cfg is stored must be specified with the '-useLinkDir' option of the EventDriver. This name must correspond to the 'controller names' entered in the connection editor! The '.' value used up-to-now is not allowed for the '-useLinkDir' option as of APROL R 4.0. Please control the EventDriver configuration in the runtime and gateway systems.
No erroneous configurations of the drivers are detected in the APROL systems when the project is built. Errors are marked when the editor is opened. It is only possible tio reactivate after the errors have been corrected.
1.10.29 Provision of further system variables In the scope of the multi-runtime system development, new system variables have been introduced for information about the system and self-diagnosis which could only be detected via UCB blocks up-to-now. New system variables are available for the following areas: Analysis of the system load of individual processes
Differentiation of configured and actual data
Diagnosis of the trend recording
Diagnosis of the ChronoPlex mechanism and analysis of the data rate for all forwardings
1.10.30 Handling hyper macro-intern variables If blocks for global variables are used in a hyper macro, substitution identifiers can be used in the instance names of AprFuIn and. AprFuOut in order to generate the PV names.
A3 Upgrade Notes 1-16 APROL As of R 4.0, a substitution above and beyond a nested hyper macro level is also possible. This affects the '$ notation', '< > notation' and '@ substitution' types. The identifiers of subordinate hyper macros are listed in the parameter list of all higher- level hyper macros. The setting of the parameters of default values for substitution is now possible in the context of the CAE library.
There are examples for each method of substitution in the B&R 'SamplesProject'. Directory: 'System / Visualization' Process graphic: 'PbSubstitutions'
1.10.30.1 Re-definition of library fonts within a project The library block font definitions that are used can be redefined individually in the CAE project as of APROL R 4.0. The project-specific redefinition of the fonts takes place in the same way as the well-known redefinition of the color dynamization. These fonts can be overwritten with the definitions from the project-specific font selection list using [Redefine the library fonts] in the 'Engineering Options' tab, in the CAE project properties. In doing so, a project-specific replacement list is generated to change the display of the text used and (new) widgets in the graphic blocks in the visualization. The fonts of the graphic blocks in the library are not changed.
1.10.31 Re-definition of the image container of libraries within a project Apart from the project-specific redefinition of the color dynamization and fonts, the images in the image container can now be redefined for display in a certain project. The images can be overwritten with the definitions from a custom project-specific image selection list using [Redefine library image container] in the 'Engineering Options' tab, in the CAE project properties. In doing so, a project-specific replacement list is generated to change the display of the image used in the graphic blocks and faceplates in the visualization. The image containers of the libraries are not changed.
1.10.32 Extension of the language switching The translations can now be made for the target language in the context of a CAE library. The supported languages which are to be translated can be selected in the properties dialog of the CAE library and project, in the 'Localization' tab. The translations can be made in the TranslationManager with the 'Translation for localization' function.
Upgrade notes 1-17
It is possible to decide if the translation is allowed to be changed or not in the project when the translations are being done in the library, so that translations which have changed after an update are also shown in the project context. 1) as the source language, The source language English (001) has been specified because in order to achieve a uniform translation, the source language of all libraries and the respective project must be the same. 2) Only the languages which are intended for translation should be selected in the master data of the CAE libraries and project.
1.10.33 Simplified input of process variables and their respective Iosys connection Together with the introduction of multi-runtime systems in APROL, the syntax of the Iosys tolls has been extended. The instance name of the APROL system can now also be specified for the options '-iosys' and '-mask'. These tools are only allowed to be used by an experienced user. They do not replace the normal operation via the GUI applications and are not allowed to be used for a normal process control.
Detailed information can be found in manual 'D1 System Manual', chapter Extension of all Iosys tools for multi-runtime systems.
A3 Upgrade Notes 1-18 1.11 New features after updating to APROL R 3.6-10 Amongst various corrections, the following additions are contained in APROL R 3.6-10:
1.11.1 Controller AR-OS versions The new AR-OS versions K0309 (Default) and P0402 (Default for Atom processors) are available in the scope of APROL R 3.6-10. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version V0308 is also supplied. The import of older AR upgrade files that are not intended for this release is no longer possible because of extensions in the AR structure! Only AR upgrade files with the internal AR structure '3.6-05' are supported. When upgrading an ARwin (AR010) controller, it is necessary that the settings for 'Memory size used for Automation Runtime' and 'Memory size used for RAM-Disk' are changed to the values (minimum size) '160000' for Automation Runtime and '70000' for the RAM-Disk. These values can be changed in the 'System' tab with 'ARwin Configuration' in 'Start/Programs/B&R Automation/AR010/AR010 Configuration'. When changing the AR on the controller types X20CP1485 and X20CP3485 as of AR E0309, it is recommended to exchange the AR only in BOOT mode, or to update direct via Flash card.
The Automation Studio for the controller hardware configuration is supplied in the version 3.0.90.27_SP09 in APROL R 3.6-10.
1.11.2 Substitution of the 'rint' function The standard Automation Studio C function 'rint' for rounding integer values is no longer available as of APROL R 3.6. This C function for B&R controllers has been substituted by the new function 'AprolMathAnsi_rint' , which has an identical function. It is contained in the 'AprolStandard.br' library.
The header file 'AprolMathAnsi.h' must be included as follows to be able to use the 'AprolMathAnsi_rint' function:
#include
All places where the 'rint' function has been used in the source code must be replaced with the 'AprolMathAnsi_rint' function.
1.11.3 Change of the AR structure from '3.6-06' to '3.6-08' The AR structure must be changed as of APROL R 3.6-08 because of the incompatibility of the IEC compiler with that used in previous APROL releases (extension of the structure Upgrade notes 1-19
'SFCStepCTyp'). This means that the AR upgrades from older releases can no longer be used. To ensure this, and to give the opportunity of importing new AR upgrades in an APROL R 3.6-08 or R 3.6-09, the AR structure has been changed from '3.6-06' to '3.6-08'. The standard library has been adjusted for this purpose. It only allows the import of AR upgrades which have the AR structure '3.6-08'.
1.11.4 Use of an APC 910 / HP-Desktop 8300Elite-CMT The graphic card which is installed per default in the APC 910 and HP-Desktop 8300Elite-CMT is not capable of running the X server of the current AutoYaST DVD V3.6-090. The X server runs on the computer workplace and offers its (graphical) services to the X clients. It contains the graphic card driver and the driver for keyboard, mouse, and other input devices (such as graphic tablets) and communicates with the X client via inter- process communication.
In order to be able to use APROL R 3.6-10 on an APC 910 or HP-Desktop 8300Elite-CMT, a graphic card which has been tested and released for use by B&R must be installed in addition to the on-board graphic card which already exists. The on-board graphic card must also be switched off explicitly in the BIOS for the APC 910.
1.11.5 New features in the energy monitoring reports B&R already offered an 'out-of-the-box' solution for energy monitoring with 'APROL EnMon' as of APROL R 3.6-09. The energy monitoring reports allow a comfortable system query which can be divided into a cost and analysis report.
New features in the energy monitoring reports as of APROL R 3.6-10: Provision of simultaneous comparison reports (Energy Consumption Comparison) The new report allows comparing the consumption with previous periods. The display types 'Tabular report' and 'Trend diagram' are available for this purpose. Provision of a report for heating degree day Heating degree day is used to calculate the demand for energy needed to heat a building during the heating period. It is the calculation of a room temperature and the outside temperature for the heating of a certain period and thus a helps to calculate the future heating costs. CSV export: Adoption of the filter settings The filter settings are recorded in the header of the CSV file during an export.
A3 Upgrade Notes 1-20
Illustration 6: Comparison report
1.11.6 Hardware PV global volatile Hardware PVs are now registered as 'global volatile' per default, so that an old value (not 0) is not set during a warm restart before the task is running and the outputs are calculated, and is then finally reset. The old behavior ('global remanent') is reactivated by setting the environment variable 'BuR_CreateIoGlobalRemanent'.
1.11.7 Update of the CAE database If the Apache server has been configured so that the HTTPS protocol is used instead of the HTTP protocol then the update of the engineering environment (after an APROL system software update) must be carried out with the 'CaeUpdate' program and the '-http' option. The update is then carried out as usual. On the console after an update, but before the start of the CaeManager: CaeUpdate -http
Upgrade notes 1-21
1.12 New features after updating to APROL R 3.6-09 Amongst various corrections, the following additions are contained in APROL R 3.6-09:
1.12.1 Controller AR-OS versions The new AR-OS versions G0309 (Default) and L0402 (Default for Atom processors) are available in the scope of APROL R 3.6-09. These are used as default versions (depending on the hardware) when a new controller is created. The AR-OS version V0308 is also supplied.
The Automation Studio for the controller hardware configuration is supplied in the version 3.0.90.23_SP05 in APROL R 3.6-09.
1.12.2 Support of Intel Atom CPUs It is now possible to configure the new Intel Atom CPUs for the B&R X20 series in the scope of the AS hardware configuration. This concerns the following CPUs:
X20CP1583 to X20CP1586 X20CP3583 to X20CP3586
The creation of CF cards for these CPUs is possible. The AR-OS version L0402 must be installed in order to use the Intel Atom CPUs.
1.12.3 Usage of the VMware workstation version 9.0.0 The VMware workstation has been updated to the version 9.0.0. The version 9.0.0 contains many bug fixes and correction of security issues. Detail information: http://www.vmware.com/support/ws90/doc/workstation-90-release- notes.html
1.12.3.1 Specifics for using a virtual engineering environment in a VMware work-station It has been possible, since the VMware version 8.0.1, to use an APROL engineering system in a VMware.
Upgrade notes 1-1
If the APROL engineering system is within a virtual environment, the following must be noted: 1) After the installation of the AutoYaST DVD, APROL is not allowed to be
installed directly afterwards. It is necessary to update the VMware tools in the guest system. Thus, please select the 'Continue without installation' option in the dialog and confirm this choice.
2) It is absolutely necessary to install the actual version of the VMware tools for the virtual engineering system. The installation and configuration of the VMware tools is described in the official VMware documentation. http://vmware-tools-installation-configuration_DE.pdf
3) After a successful installation of the VMware tools, start the APROL installation by entering 'AprolInstall' in the command line.
A new license key is supplied optionally in order to license the VMware work-station 9.0.0. The 'AprolDowngradeVMware' script is delivered in order to be able to work with an existing VMware 8.0.1 or VMware 7.0.0 license after an upgrade. The script uninstalls the VMware workstation version 9.0.0 and then installs the version 8.0.1 or 7.0.0 by using the '-downgrade VM8 \ VM7' launching option. The 'license-ws-80-e1-201010' license file must exist in '/etc/vmware' for the version 8.0.1. The old 'license-ws-70-e1-200904' license file must exist in the '/home/
1.12.4 Manual setting of the link of the used PAL modules after an AR upgrade As of APROL R 3.6-09, no PAL modules are contained in the new AR-OS version after upgrading the AR-OS version of the controller.
If PAL modules are being used, the necessary links to the PAL modules must be created manually in the Linux file system directory of the new AR-OS version after it has been upgraded. The links for the 'pal.h', 'pal.br' and 'libpal.a' modules are affected.
The link for the 'pal.h' module, which was used in the existing AR-OS up-to-now, must be created manually with the Linux command 'ln -s' in the directory: /opt/aprol/AS/
A3 Upgrade Notes 1-2
Illustration 7: Existing link in an older AR-OS version
The link for the 'pal.br' module must be created manually as described before in the directory: /opt/aprol/AS/
The link for the 'libpal.a' library must be created manually as described before in the directory: /opt/aprol/AS/
1.12.5 Adoption of module dependencies is possible for B&R libraries As of APROL R 3.6-09, the dependencies for libraries and system modules can be edited in the properties of CAE libraries of the type 'APROL (B&R)'.
The adoption of the dependencies from older AR-OS versions was locked for B&R CAE libraries up-to-now.
Upgrade notes 1-3
Illustration 8: Adoption of module dependencies for B&R CAE libraries is possible
Another mechanism will be made available for the future planned APROL R 3.8-xx.
1.12.6 Integration of the EnergyMonitoring report B&R offers an 'out-of-the-box' solution for energy monitoring with 'APROL EnMon' in APROL R 3.6-09. A system environment is provided to measure, record, and evaluate all relevant energy consumption and offers good support in the iterative process of continuous improvements. The APROL system environment ensures a maximum flexibility with a minimal engineering effort. The EnergyMonitoring reports are available as standard system queries. They can be opened via the 'Reports / EnergyMonitoring Reports' KDE menu, or via the 'Report overview' in the 'APROL Solution' section.
A3 Upgrade Notes 1-4
Illustration 9: Report selection
Illustration 10: EnergyMonitoring report (Area report)
In the scope of authentication for web-based access, the opening of the EnergyMonitoring report can be configured explicitly in the 'Project properties / Runtime (1/2)' tab.
Upgrade notes 1-5
Illustration 11: Authentication for web-based access to the EnergyMonitoring report
If the authentication is not used, the application rights which are configured in the OperatorManager are not checked.
1.12.7 Additions to the SFC transition diagnosis The graphic transition diagnosis is a comfortable tool for analyzing a transition that does not switch. The graphic transition diagnosis has been extended with the following comfortable functionality as of APROL R 3.6-09: The corresponding transition is marked in the SFC chart with a blue frame when the mouse is placed over the 'SFC Transition Diagnosis' dialog. It is thus ensured that the respective transition can be identified if several 'SFC Transition Diagnosis' dialogs are open at the same time.
Illustration 12: Unmistakable identification of the transition when several dialogs are open
1.12.8 Clean-up directory before import The content of a target path of an import is deleted before an import into the CAE project as of APROL R 3.6-09 in order to guarantee a consistent state of changed and generically created project parts during a re-import. The function can only be used with directories in the context of a CAE project. The deletion of entire directories instead of proceeding with existing project part versions should be used when the data has been generated externally or the re-import
contains changes in the directory structure.
The 'Set the marking for 'Clean-up before import'' checkbox can be activated in the 'Properties' dialog of the directory.
A3 Upgrade Notes 1-6 A selected directory can also be marked with the 'File / Import / Set the Marking for 'Clean-up before import'' menu.
Illustration 13: Setting the marking for 'Clean-up before import'
After the marking has been carried out, the deletion must also be confirmed.
Illustration 14: Security query before setting the marking for 'Clean-up before import'
In the future APROL release 3.8, the use of the function will only be allowed with an allocated 'Clean-up before import' project right. The marking takes effect recursively for all of the project parts and directories that are contained. The contained directories and project parts are labeled with an 'eraser' icon to show they have been marked.
Illustration 15: Marking of the directories and project parts to be deleted
Upgrade notes 1-7
The re-import should always be carried out in the root directory of the CAE project, because data which were previously exported contain the complete project path.
Detailed information about the workflow
The deletion of project parts takes place by moving them to the trash bin. An attempt is then made to delete all of the project parts in the trash permanently from the database. This cannot be carried out for project parts which have external references pointing to them.
The re-import takes place afterwards. Project parts which have a replacement in the import are then also deleted from the trash.
Finally, the project parts for which there were no replacements in the import are marked with a CAE advice, as well as the 'Active' / 'Current' versions of the project parts lying outside of the path to be deleted and still refer to the non-re-imported or deleted project parts. These markings allow the user to trace the project parts that need an adjustment to the state of the newly imported project parts.
If the adjustments have been made by the user, the markings are removed from the edited project parts after they have been successfully recompiled. If all of the project parts have been corrected, the 'obsolete' project parts can be finally removed from the trash.
1.12.9 Automatic detection of the system directories is no longer supported As of APROL R 3.6-09, deviations from the standard directory
/home/
Non-standard home directories which have eventually been created by a user must be adjusted!
1.12.10 Extended configuration possibilities for the APROL shift logbook The well-known APROL Shift logbook is implemented as a web application, meaning that it can be called up in any web browser platform after a successful authentication (configurable) and is independent of the operating system. It offers the possibility to record any special events and all measures introduced by operators. The information gained can be shared by all other employees, making the complete exchange of experiences possible.
As of APROL R 3.6-09, the operation of and the structural possibilities in the shift logbook have been revised.
A3 Upgrade Notes 1-8 The 'Category view' which offered a flat structure of all thematic groups up-to-now can now be displayed as a 'Theme tree'. This theme tree can be expanded and collapsed; Answers can be entered directly for certain themes/sub-themes. A direct reference to the original entry and all respective answers is ensured in this way. The configuration possibilities in the XML file have been extended with the following aspects: Existing XML files can of course still be used, and can be extended with the new aspects as desired.
Configuration of form objects: Apart from pure text fields, form objects can now be defined as shift logbook fields. 'Checkboxes', 'Selection boxes', 'Radio Buttons', 'Text input field' a grouping can be specified for all form objects. Furthermore, longer description texts can be configured for display in tool tips.
Configuration of the size of the response dialog Setting the edit-ability of fields when responding to existing entries Setting the adoption of values when responding to existing entries Setting the time sorting
The default behavior for edit-ability / content of fields has changed. Up-to-now, fields were basically editable and not preset. As of APROL R 3.6-09, these properties are inherited from the upper-level entry. This behavior can also be configured.
Illustration 16: Structured display in the form of a topic tree
To define your own categories or form objects, a copy of the existing XML file shiftlog.xml in the directory /opt/aprol/doc/clt/
Upgrade notes 1-9
Illustration 17: Additional configuration possibilities
1.12.10.1 Overview of the new configuration possibilities
Aspect: Configuration:
Checkbox: Example configuration: id='my_sap1' edit='true' pre='true' /> Explanation: Tag id Customer fields must begin with the prefix my_. This entry is mandatory. This value is the attribute name of the ChronoLog identifier Description If a value is specified, this string is displayed as a tool tip above the identifier. edit = (true|false) default is false Setting the edit-ability of fields when responding to existing entries pre = (true|false) default is true Setting the adoption of values when responding to existing entries. A3 Upgrade Notes 1-10 Aspect: Configuration: Selection box: Example configuration: Explanation: Tag Attribute: desc This entry is mandatory. This value is the text of the field identifier in the graphic user interface. id Customer fields must begin with the prefix my_. This entry is mandatory. This value is the attribute name of the ChronoLog identifier Description If a value is specified, this string is displayed as a tool tip above the identifier. edit = (true|false) default is false Setting the edit-ability of fields when responding to existing entries. pre = (true|false) default is true Setting the adoption of values when responding to existing entries. Selection options: The individual options must be bracketed in the Attribute: value This entry is mandatory. This value takes the attribute when the option is selected and is written under the attribute in the ChronoLog data record, which is defined in the Explanation: Tag id Customer fields must begin with the prefix my_. This entry is mandatory. This value is the attribute name of the ChronoLog identifier. Description If a value is specified, this string is displayed as a tool tip above the identifier. edit = (true|false) default is false Setting the edit-ability of fields when responding to existing entries. pre = (true|false) default is true Setting the adoption of values when responding to existing entries. Selection options: The individual options must be bracketed in the Attribute value This entry is mandatory. This value takes the attribute when the option is selected and is written under the attribute in the ChronoLog data record, which is defined in the A3 Upgrade Notes 1-12 Aspect: Configuration: Text entry fields: Example configuration: Explanation: Tag Attribute desc This entry is mandatory. This value is the text of the field identifier in the graphic user interface. id Customer fields must begin with the prefix my_. This entry is mandatory. This value is the attribute name of the ChronoLog identifier. Description If a value is specified, this string is displayed as a tool tip above the identifier. edit = (true|false) default is false Setting the edit-ability of fields when responding to existing entries. pre = (true|false) default is true Setting the adoption of values when responding to existing entries. Size of the response dialog: Example configuration: Explanation: Tag Attribute: width height Upgrade notes 1-13 Aspect: Configuration: Setting the time sorting: Example configuration: Explanation: Tag Attribute: newontop = (true | false ) This attribute always shows new entries at the first position of a branch. Default value when the attribute is not set is newontop = False. A3 Upgrade Notes 1-14 1.13 New features after updating to APROL R 3.6-08 Amongst various corrections, the following additions are contained in APROL R 3.6-08: 1.13.1 Controller AR-OS versions The AR-OS versions V0308 and D0309 (Default AR-OS version) are supplied for Intel platform controllers in APROL R 3.6-08. The Automation Studio for the controller hardware configuration is supplied in the version 3.0.90.21_SP003 in APROL R 3.6-08. 1.13.2 Update to the current AutoYaST version As of APROL R 3.6-08, the actual enhancements of the SLES 11 SP2 are made available with the new AutoYaST DVD V3.6-080. Due to the resolution of many package dependencies, B&R provides the 'AprolPrepareUpgradeAutoYaST' script that carries out the necessary conflict resolution by uninstalling the obsolete packages and installs those that are necessary. The update to the current AutoYaST version is to be carried out as follows: Step Description 1 Log in on a console as the LINUX super user 'root'. 2 Mount the AutoYaST DVD with the LINUX 'mount' command: e.g.: mount -t iso9660 Upgrade notes 1-1 Step Description 3 Execute the AprolPrepareUpgradeAutoYaST script: / 4 Unmount the medium that was previously mounted with the LINUX 'umount' command: umount / A detailed description can be found in the APROL documentation 'A2 Getting Started', chapter Updating the operating system (SLES) from the AutoYaST installation DVD. A3 Upgrade Notes 1-2 Step Description 7 The kernel modules from APROL must be uninstalled, because the AutoYaST installs a new kernel and the kernel modules from APROL (e.g. 'pb_init', 'ProfiBoard', 'aprolArcNet') cannot run with the new kernel. The correct APROL kernel modules are installed later with the APROL system software. Uninstall the APROL kernel modules in the following dialog with the corresponding topmost radio. Confirm the choice with [OK - Try again]. 8 Automatic package changes (for the resolution of dependencies) are listed in the following dialogs. Confirm the changes with [Continue]. 9 The installation of the AutoYaST DVD is then carried out as usual. 10 The computer must be rebooted after the AutoYaST update, because the kernel has been updated. 1.13.3 Consistency check of project part names The APROL validators offer a syntax check for all interactive inputs. Possible length limits are also checked during the input. An incorrect entry is identified immediately and rejected by the APROL system. As of APROL R 3.6-08, the name of project parts are checked for possible inconsistencies when they are imported (The check is the same as that of the validator when creating a project part). A corresponding dialog is shown if a name is not allowed during the import process, and a CAE advice is created for the imported project part. The project part can then be furnished with a valid name. Upgrade notes 1-3 Illustration 18: Import process with invalid project part names Illustration 19: Entry of a CAE advice The project part can still be activated, even though it does not have a correct project part name, by setting the 'Reduced plausibility check' option in the respective project or library properties. It is not possible to compile this project part.. Graphic blocks are an exception and can be compiled with the 'Reduced plausibility check' option. If the project option is not set, no activation or compilation can be carried out. It is possible to deactivate the new plausibility checks that have been introduced with a major APROL release update (not upgrade!) with the previously mentioned option. This avoids generating errors for project parts where the configurations are recognized as being erroneous. The check will be made more rigorous in a future APROL release, so that an activation / compilation cannot be carried out even though the project or library option is activated. A3 Upgrade Notes 1-4 1.13.4 Problems when using the visualization 'TextView' element The following problems arise when using the 'TextView' element and showing a *.mjpg data stream (e.g. from a close circuit monitor) or content that refreshes automatically. There is an increase of the memory needs, because of a memory leak in the 'gecko' rendering engine that is in use. The refresh may freeze after certain periods of time. In most cases, the refreshing of the HTML pages continues after the mouse pointer is moved over the widget. 1.13.5 Warning due to obsolete directory The following warnings may be output when an AS project is compiled in Automation Studio, because of obsolete directories that are not part of an AS project If these directories are not needed, they should be removed in the Windows environment before the AS project is compiled in Automation Studio and they are adopted in the CaeManager. These warnings are also shown in the APROL environment after the configuration has been adopted. Illustration 20: Warning due to obsolete directory 1.13.6 Renewed password entry for existing users in the customer-specific MySQL databases The passwords of existing customer-specific MySQL databases (not the MySQL database of the parameter management) must be newly allocated, because of an incompatibility of the PHP version 5.3 with the old MySQL password format. If the PHP version 5.3 is used for processing MySQL data (e.g. for the reporting), the existing users passwords must be newly entered in the customer-specific MySQL databases. Upgrade notes 1-5 The new, secure password format is changed automatically for all users in the MySQL parameter management database in the scope of the APROL installation. 1.13.7 Update step for the SFC function blocks and programs Because of a change in the internal data structure, all SFC function blocks and programs are automatically adjusted to the new structure after updating to APROL R 3.6-08. This does not apply to the import mechanism. After importing an SFC program or SFC-Function block from an older APROL release, the project part must be opened once and re-saved. This is the only way to achieve an error-free compilation. 1.13.8 Maximum length for transition names Debug variables for transitions diagnosis are created according to the pattern 'zzSFCDbg_ 1.13.9 Locking of the control of an SFC with concurrent access When the Controlled-Mode is switched on in an SFC that is being controlled by another user / operator via 'Controlled-Mode', a confirmation is requested for adopting the control. If the adoption of control is confirmed by the user / operator, the user / operator that had the control up-to-now has it revoked and this process is recorded in the AuditTrail. This check takes place across the entire system, i.e. a concurrent access from an operator station and the debugging in engineering leads to a query of the user / operator that wants to adopt the control. The fact that the SFC is in a state of being controlled by another user / operator is marked with a background color that can be configured. If the SFC is controlled by your own CFCViewer or CaeManager in debug mode, it is indicated by another color in order to make a differentiation. This background color can also be set in the project properties. 1.13.10 Use of the 'AsBrMath' library instead of 'AsMath' The 'math.h' library is included per default in the APROL libraries. If the 'AsMath' library is included additionally, this leads to a double declaration of methods with different data types. The return value of atan2, for example, is a 'double' in 'math.h', and a 'float' in 'AsMath'. A3 Upgrade Notes 1-6 The 'AsBrMath' library contains an identical scope of functions as in the 'AsMath'; the methods have the additional prefix of 'brm' (e.g. 'cosh' becomes 'brmcosh'). The 'AsBrMath' libraray must be used in order to be able to use the functions of the 'AsMath' library in ST / SFC. Illustration 21: Use of the AsBrMath library For this purpose, enter 'asbrmath' in snall letters in the 'Additional libraries' field. (Library properties / 'AR-OS Versions (Controller)' tab / [Dependencies] ) AsBrMath must also be added to the list of module dependencies with the [System modules] button. Upgrade notes 1-7 1.14 New features after updating to APROL R 3.6-07 Amongst various corrections, the following additions are contained in APROL R 3.6-07: 1.14.1 Optional installation of the PHP version 5.3 If the PHP 5.3 functionality is needed in the context of R 3.6-07, it is possible to optionally install PHP version 5.3 in the scope of the AutoYaST installation. This new version and its functionalities can thus be tested in the context of the R 3.6-07 as there may be a possible change of the PHP version in a future APROL release. The PHP version 5.2 is installed per default in APROL R 3.6-07. Step Description 1 Open the 'SUSE menu / System / Administrator Settings (YaST)' menu item in the KDE menu. The YaST Control Center is started after entering the password of the Linux super user 'root'. 1a The DVD drive must eventually be added and activated with 'Software / Software Repositories' in YaST2. 2 Choose the 'Install or delete software' point in YaST2, in 'Software'. In the following dialog, the 'Schemes' point must be selected in the 'Display' drop- down menu. All of the schemes are displayed in the list shown. 3 In order to install the PHP 5.3 packages, select the 'Install' menu item in the context menu (Right mouse button) of the corresponding scheme 'Scheme'. The scheme is then marked with a green checkmark. Upgrade notes 1-1 Step Description 4 The de-installation of the PHP 5.2 packages must be selected with the topmost radio button in the following dialog, because of existing conflicts with the PHP 5.2 packages. Confirm the choice with [OK - Try again]. 5 Another conflict resolution must be made by selecting the topmost radio button in another dialog, depending on if the platform is 32 or 64 bit. Confirm the choice again with [OK - Try again]. 6 Select the 'Update if newer version available' item from the 'Package / All packages' menu. The respective packages of MySQL are installed on APROL systems where an installation of MySQL is not necessary and are then uninstalled during the installation of the APROL system software. The MySQL packages should therefore be un-selected. 7 The update can then be started with the [Adopt] button. A3 Upgrade Notes 1-2 Step Description 8 Automatic package changes (for the resolution of dependencies) are listed in the following dialog. Confirm the changes with [Continue]. 9 When the update ends, exit the YaST Control Center and remove the DVD from the drive. 10 The AprolConfigApache script must be executed with the -configure option after the installation of PHP 5.3 (or PHP 5.2), i.e. after any change of the PHP version, because an internal adjustment must be made in the configuration file of the Apache web server when a versio is changed. ApacheConfigApache --configure The execution must be carried out as the Linux super user 'root'. 1.14.2 Controller AR-OS versions The AR-OS versions V0308, and C0309 (Default AR-OS version) are supplied for Intel platform controllers in the current APROL release. The Automation Studio for the controller hardware configuration is supplied in the version 3.0.90.20_SP02 in APROL R 3.6-07. The current SafeDESIGNER version 2.83.18.25732 is supplied for the SafeLOGIC configuration. Please note that all installed versions of a SafeDESIGNER series (E.g. SD 2.81, SD 2.82) are uninstalled as of the SafeDESIGNER 2.83.x, so that only one version of the SafeDESIGNER exists.. 1.14.3 Opening and saving all SFC programs and function blocks After an update from APROL R 3.6-04, all SFC programs in which the logging has been activated must be opened once and saved because of changes in the logging function. An adjustment of the function calls that are necessary for the logging takes place then. After an update from APROL R 3.6-04, an APROL R 3.6-05, or an APROL R 3.6-07, all SFC function blocks must be opened once and saved because of changes in the logging Upgrade notes 1-3 function and sequential control of SFC function blocks. The necessary function calls are then adjusted for the logging, as well as the internal representation of the SFC function blocks. All configured ST and SFC programs and function blocks must be opened once and re-saved. 1.14.4 Corrections to the UcbServer In certain situations in a redundancy environment, it may come about that the UcbServer remains in a 'stopped' state after having stopped it (explicit stopping of the UcbServer with the StartManager, stopping the UcbServer via console, stopping the APROL system) and a download was not possible. The status of the process redundancy is now detected correctly and the UcbServer is stopped securely after this correction. 1.14.5 Change to VMware version 8.0.1 The VMware Workstation version 8.0.1 is installed per default together with the APROL R 3.6-07 system software because the company VMware Inc. has discontinued the VMware Workstation version 7.x. A VMware Workstation 7.x can still be used for existing projects if there is a VMware Workstation license for the version 7.x by using the 'AprolDowngradeVMware' script. The script uninstalls the VMware version 8.0.1 and then installs the VMware version 7.x. A downgrade to the VMware version 7.x can take place after the APROL system software has been installed. Step Description 1 Start a console or an xterm. 2 Log in as the Linux super user 'root'. A3 Upgrade Notes 1-4 Step Description 3 Then check if all requirements have been met for a downgrade. For this, call the script 'AprolDowngradeVMware' with the '-checkDowngrade' option. 1. The following is output If there is no license in the /home/ meeting1:/# meeting1:/# AprolDowngradeVMware -checkDowngrade Check requirements for downgrade process: - VMware 8.0.1.528992 is installed - VMware 7.0.0-203739 installer exists - Engineering (engin): VMware 7.0.0 license does not exist A downgrade to VMware 7.0.0-203739 is possible, but one or more engineering system has not the correct VMware license! meeting1:/# Please note: Each engineering system must be licensed for the VMware Workstation version 7.x. There is only a licensing for the server when using the VMware version 8.0.1. 3 2. The following is output if a downgrade is not necessary because a VMware version 7.x already exists: meeting1:/# meeting1:/# AprolDowngradeVMware -checkDowngrade Check requirements for downgrade process: - VMware 8.0.1.528992 is not installed - VMware 7.0.0-203739 installer exists - Engineering (engin): VMware 7.0.0 license exists A downgrade to VMware 7.0.0-203739 is not possible, because requirements are not met! meeting1:/# Upgrade notes 1-5 Step Description 3. The following is output if all requirements for a downlgrade have been met: meeting1:/# meeting1:/# AprolDowngradeVMware -checkDowngrade Check requirements for downgrade process: - VMware 8.0.1.528992 is installed - VMware 7.0.0-203739 installer exists - Engineering (engin): VMware 7.0.0 license exists A downgrade to VMware 7.0.0-203739 is possible! meeting1:/# 3b If you want to reset to the VMware version 8.0.1 at a later stage, check to see if all requirements for an upgrade have been met: For this, call the script 'AprolDowngradeVMware' with the '-checkReset' option. The following is output if all requirements for a reset to VMware version 8.0.1 have been met: meeting1:/# meeting1:/# AprolDowngradeVMware -checkReset Check requirements for downgrade process: - VMware 7.0.0-203739 is installed - VMware 8.0.1.528992 installer exists - VMware 8.0.1 license exists An upgrade to VMware 8.0.1.528992 is possible! meeting1:/# 4 Carry out a downgrade of the VMware version: Execute the script as follows: 'AprolDowngradeVMware -downgrade' A3 Upgrade Notes 1-6 Step Description 5 Select 'Yes' to answer the query about retaining the VMware configuration files. The network settings and the licensing are lost if 'No' is selected. B&R recommends that you preserve the configuration files. The uninstallation of the VMware version 8.0.1. is then carried out. You can confirm the successful uninstallation with the [Close] button. 6 Then accept the license conditions of the VMware version 7.x. Upgrade notes 1-7 Step Description 7 The following dialog box appears after a successful installation: You can confirm the successful installation with the [Close] button. This ends the downgrade process of the VMware. Detailed information about licensing the VMware can be found in the APROL documentation "E1 Controller & I/O", chapter Licensing the VMware. 1.14.5.1 Changing the port for the HTTPS communication with the VMware workstation If the VMware Workstation version 8.0.1 is installed for the very first time, the VMware EULA is output on the console after the APROL system software has been installed. At this point, a query is made about the port which should be used for the HTTPS communication with the VMware workstation. The port 443 is suggested per default. A free port must be entered here, e.g. port 444, because the default port 443 suggested by the VMware 8.0 is already being used by APROL (for the encrypted access to the web applications). Information about the free ports/ports being used by APROL can be found in the 'APROL System Diagnostics Manager / Port Status' 1.14.5.2 Administration of the network interface The network interface must be explicitly administered both in the 'normal' VMware 8.x installation and in an upgrade from VMware version 7.x to version 8.0. A3 Upgrade Notes 1-8 Illustration 22: Network settings in the VMware Select 'Work Network' entry for this purpose. A security message may be output in certain situations and the Windows firewall impedes the necessary programs in their communication. Illustration 23: Windows firewall message In this case, the communication must be explicitly allowed with 'Allow access'. Otherwise, a communication between the necessary programs cannot be guaranteed. Upgrade notes 1-9 1.15 New features after updating to APROL R 3.6-06 Amongst various corrections, the following additions are contained in APROL R 3.6-06: 1.15.1 Controller AR-OS versions The AR-OS versions H0307, and V0308 (Default AR-OS version) are supplied for Intel platform controllers in the current APROL release. The Automation Studio for the controller hardware configuration is supplied in the version 3.00.90.18 in APROL R 3.6-06. 1.15.2 Extended logging of interactions in alarm handling Acknowledgement of alarms The acknowledgement of one or more alarms in the AlarmMonitor is logged in AuditTrail as of APROL R 3.6-06. The previous format, which only contains the operator information, is still supported. Locking and unlocking of alarms The 'QUITTEXT' input on the 'AprCcAlarm' block in existing CAE projects / libraries that use the alarm acknowledgement via logic can be configured with the above mentioned extended information. In this case, attention must be paid to the specified format! Upgrade notes 1-1 1.16 New features after updating to APROL R 3.6-05 Amongst various corrections, the following additions are contained in APROL R 3.6-05: 1.16.1 Controller AR-OS versions The AR-OS versions H0307, and M0308 (Default AR-OS version) are supplied for Intel platform controllers in the current APROL release. 1.16.2 Adjustment of the SFC logging function Due to a change in the SFC logging function, an adjustment of the necessary function calls for the logging has been made. All configured ST and SFC programs and function blocks must be opened once and re-saved. 1.16.3 New system variables for warning about not enough free hard-disk space Parallel to the warning about a large CPU / memory load (IdleStateWarning / FreeMemoryWarning), system variables have been made available in the current APROL release to warn about insufficient hard-disk space. If the free hard-disk space goes below a configured threshold, then the system variable is set and an entry is made every minute in the APROL system messages. The 'root' partition, the 'APROL_DATA' partition, and the optionally configurable partitions 1 to 4 are monitored. A threshold can be specified for each of these partitions. All APROL systems must be re-activated in order for this change to take effect. The new system variables can then be configured in the engineering. Please check the threshold that is to be set for each partition. 1.16.4 Automatic configuration of the EventDriver Adjustments have been made to the 'APROL system' project part in order to detect and show the values of the '-ipPrimary' and '-nodePrimary' options during an automatic configuration of the EventDriver. All of the 'APROL system' project parts of the type 'runtime' and 'gateway' must be recompiled if the automatic configuration is being used. Upgrade notes 1-1 1.17 New features after updating to APROL R 3.6-04 Amongst various corrections, the following additions are contained in APROL R 3.6-04: 1.17.1 Controller AR-OS and Visual Components versions The AR-OS versions V0306, F0307, and I0308 (Default AR-OS version) are supplied for Intel platform controllers in the current APROL release. The Visual Components (VC) version 3.91.6 is supplied in the Automation Studio (AS). At least the AR-OS version I0308 must be installed on a controller in order to be able to use SFC programs or SFC function blocks in a CFC program or for the use of the VC visualization. It is not possible to use older AR-OS versions (< AR-OS I0308) when using SFC code on the controllers because of extensions in the Automation Runtime. - If the usage of the 'Default AR-OS' has not been configured then an explicit conversion to one of the new AR-OS versions is to be carried out. If VC is being used after updating to Automation Studio 3.0.90.09 then the old VC version (at the moment 3.91.4) must be changed explicitly to the current VC version (3.91.6) in the AS, in 'Project / Change Runtime Versions'. Subsequently, a 'build all' must be carried out so that this version is also used in the project. The Automation Studio for the controller hardware configuration is supplied in the version 3.00.90.09 in APROL R 3.6-04. The current SafeDESIGNER version 2.81.18.25274_R15 is supplied for the SafeLOGIC configuration. 1.17.2 Configuration of a cluster for the process bus If the process bus is different to the control bus in a redundancy system, it is necessary to configure a process bus cluster for the logging of the course of an SFC. Upgrade notes 1-1 A runtime cluster name (process bus) and runtime cluster IP (process bus) must be specified in AprolConfig, in the 'Heartbeat' aspect. The cluster IP must be an address that is not already allocated in the process bus network segment. The cluster IP (process bus) is always active on the computer where the Iosys is running (actual master). The cluster entries that have been made must also be configured and checked for the process bus in the 'control computer' project part. - Section 'Master data': Configure 'Process bus cluster name' and 'Process buss cluster IP' fields - Section 'Resources': Check the specification and allocation of the 'Network resources' The entries made with 'AprolConfig' must also be checked in the 'APROL system' project part. - Section 'Master data': Check the configuration of the 'Network usage' 1.17.3 Re-saving existing SFC function blocks All SFC function blocks must be re-saved once because of internal optimizations. It is only then possible to carry out a build of the tasks that use SFC blocks. Existing SFC function blocks must be re-saved once again. 1.17.4 Use of an LDAP server for authentication In the scope of optionally using an LDAP server for the authentication of a user or operator, the 'First name' and 'Surname' attributes are now mandatory fields in the APROL user management. If an LDAP server is used for authentication, it must be ensured that no user (user management) or operator (OperatorManager) have identical first AND surnames. A3 Upgrade Notes 1-2 1.18 New features after updating to APROL R 3.6-03 Amongst various corrections, the following additions are contained in APROL R 3.6-03: 1.18.1 Controller AR-OS versions The AR-OS versions E0307 (Default AR-OS version) and V0306 are supplied for Intel platform controllers in the current APROL release. The Automation Studio for the controller hardware configuration is supplied in the version 3.00.81.24_SP03 in APROL R 3.6-03. The current SafeDESIGNER version 2.80.17.25187 is supplied for the SafeLOGIC configuration. 1.18.2 Use of the process graphic preview If the 'Process graphic preview' function was used in the CaeManager in the previous APROL R 3.6-02, the preview can eventually not be shown after the update to APROL R 3.6-03. The reason for this is the system internal change of the graphic format from V14 to V15. In this case, delete the /home/ system>/ENGIN/PROJECTS/__CHECK__ 1.18.3 Configuration of a guaranteed instance name As of APROL R 3.6, a 'guaranteed instance length' can be entered in the master data of a hyper macro in the CAE library. This guaranteed instance length specifies the number of characters for the instance of the CFCs summed with the number of characters for the instance name of the hyper macro. The user is then informed, when placing the hyper macro at a later stage, how many characters are allowed to be used for the hyper macro instance without an error occurring during the checking and compilation of the CFC. A check is made to see if the configured 'Guaranteed length' is valid when a hyper macro is checked and compiled. Upgrade notes 1-1 A guaranteed instance length of 10 characters is allocated per default when an existing hyper macro is opened. This should be adjusted to a suitable length by the user. The maximum possible instance length is shown in the log output window when a CFC is compiled. The log output window only remains open after a successful compilation when the user option 'Productivity / Suppress messages after successful compilation' is not set. 1.18.4 Display of the database connections The 'Help / APROL Info Database Connections' dialog contains a detailed overview of all relevant applications which access the database. As of APROL R 3.6-03, the access of the LoginServer, OperatorManager, and the CaeBackup to the CAE database are also listed in addition to that of the CaeManager and DownloadManager in the engineering environment. 1.18.5 Necessary adjustments to existing SFCs from the Automation Studio In preparation for the future forcing of transitions in APROL, the transitions must now be named explicitly in the SFC. Because of this, please note that existing Automation Studio SFCs can no longer be adopted if an adjustment has not been made. All transitions in an SFC must have unique names allocated before an 'SFC' project part is activated. 1.18.6 Discontinuation of the ChronoChartPrinter and the 'old' Iosys web interface The 'ChronoChartPrinter' application and the 'old' Iosys web interface have been discontinued and are no longer supported as of the planned APROL R 3.8. The time-controlled output of printouts to a printer via an entry in the crontab can be replaced with a TrigReport block, which calls a corresponding ChronoLog template. Please use the Iosys HTTP interface as an alternative to the Iosys web interface. 1.18.7 Provision of a KDE 'Service' configuration Gateway or runtime systems without an integrated operator system can be run in Linux run level 3 (without a graphical user interface). A special KDE 'Service' configuration is provided in this release in order to be able to use a graphical user interface for administration duties in these systems, e.g. to install a patch. The KDE menu encompasses, amongst others, the StartManager application, with which an APROL patch can be installed, the SUSE tools, the APROL reports, the A3 Upgrade Notes 1-2 IosDiagnosticManager, and the ControllerManager. The graphic user interface can also be opened in Linux run level 3 with the 'AprolStartServiceX' script. Please start AprolConfig as the Linux super user 'root' on all control computers that have these gateway and runtime systems installed, and carry out a re- activation of all affected APROL systems. Please open all 'APROL system' project parts in existing projects that contain the configuration of a gateway or runtime system without any integrated operator station, and then re-save the updated version in your project. 1.18.8 Change of the unit and IEC type of system variables for memory evaluation The data type of system variables for disk-space evaluation has been extended from 'DINT' to 'LREAL', and the unit from KByte to MByte, in order to be able to display modern hard-disks in a correct manner. For a uniform evaluation, these changes have been carried out both for hard-disk monitoring and also for the monitoring of the load on the working memory. It is still possible to quantify the 'KBytes' by evaluating the places after the decimal point. The following system variables have been adjusted: FreePartition1Space APROLDATASp FreePartition2Space ace FreePartition3Space Partition1Space FreePartition4Space Partition2Space FreeRootDiskSpace Partition3Space FreeAPROLDATASpace Partition4Space RootDiskSpace UsedChronoLogDiskSpac FreeMemory, e FreeRssMemory, UsedChronoPlexForwardi FreeSwapMemor ngBuffer y, TotalMemory, UsedAPROLDATASpace TotalSwapMemo UsedPartition1Space ry, UsedMemory, UsedPartition2Space UsedRssMemory UsedPartition3Space , UsedPartition4Space UsedSwapMemo UsedRootDiskSpace ry UsedVncRecorderSpace App If a system and self-diagnosis is carried out with the CAE blocks from the 'SysMon' CAE library then no adjustments are necessary. Upgrade notes 1-3 1) After an update, all APROL systems must be reactivated and newly compiled before a build of the CAE project takes place, in order to create the correct system variables. 2) If the system variables are being used in a CAE project, they must be re-placed in the respective CFCs. 3) If global variables that refer to changed system variables are being used in hyper macros or CFCs then they must also be changed. 4) There may be changes in the logic because of the change of data type and size. 1.18.9 New status monitoring of the 'LSTRING_TO_ Due to this, the height of the block is changed and may also cause overlapping with connection lines or other blocks that have already been placed. After an update, and if there is an error during a new build, the effected instances of the blocks must be moved and the effected CFCs / hyper macros must be saved compiled. 1.18.10 Access of the TrendViewer configuration files The behavior of the dialog for loading and saving TrendViewer configurations and layouts in the runtime environment has changed. It is now no longer possible to access directories outside of the respective standard configuration directory. A3 Upgrade Notes 1-4 If it is necessary to access a directory that is outside, e.g. in existing projects where configuration files are stored on the network, then it must be mounted in the standard configuration directory with the 'mount' command on all of the operator stations. The standard configuration directory is: '/home/ 1.18.11 Simplification of the system 'Strict check of parameter values (Engineering)' project option This option is obsolete, meaning that parameters in the engineering environment are always checked for plausibility. The strict check of the parameters in runtime can still be switched off because the detection and setting of the optimal value of parameter sets, which is mostly necessary in the start-up phase of a plant (commissioning), violates the limits defined in engineering temporarily. The input and loading of such data into runtime should be possible in order not to impede the workflow. Icon info The meaning of all icons is now explained in the tool tip of the respective context of the function, so that 'Icon Info' via the 'Help' menu is obsolete. Database consistency check This check, which was called up explicitly, has been removed because it only checked for the consistency of the internal instance management that is now ensured with internal mechanisms. Upgrade notes 1-5 1.19 New features after updating to APROL R 3.6-02 Amongst various corrections, the following additions are contained in APROL R 3.6-02: 1.19.1 Controller AR-OS versions The AR-OS version V0306 (Default AR-OS version) is supplied in the current APROL release for Intel platform controllers, as in the in the scope of the APROL R 3.6-01. The Automation Studio for controller hardware configuration is delivered in APROL R 3.6-02 in the current version 3.00.81.19. Please note that this B&R version is not released officially in a German version. 1.19.2 Current AutoYaST DVD The new AutoYaST DVD version 3.6-02 is delivered within the scope of APROL R 3.6-02. The installation of the new AutoYaST DVD V 3.6-02 is mandatory for the operation of the current APROL release. 1.19.3 Use of Windows 7 for the AS hardware configuration As of APROL R 3.6-02, the existing Windows XP operating system that was used for the hardware configuration with Automation Studio has been replaced by the current Windows 7. The Automation Studio must be installed once in the VMware after updating the APROL system software. The Windows 7 license key that is delivered with APROL R 3.6 must be used to license and activate the Windows 7 environment. The Windows XP image that has been used up to now remains in the /home/ Upgrade notes 1-1 1.19.4 Simplifications in the coupling type editor for couplings and driver configurations The coupling type editor (previously 'Rule editor') that is used for creating and testing custom- made connections has been simplified in its handling and has been extended with functions for a better tracking: The following benefits for you result from this: Enlargement of the working surface due to an improved geometry management: The following information can now be shown simultaneously: Rules for the connection / data for a test connection / configuration preview Optimization in the workflow via better orientation: E.g. Automatic display of the corresponding rule definitions when selecting an entry in the test connection, E.g. Automatic display of the corresponding entry in the test connection after selecting an entry in the rule definition, E.g. Automatic jump to the first rule definition for a selected area in the 'Pre-build configuration view' Greater overview when importing The compatibility to existing rules is of course guaranteed. Details can be found in the APROL documentation 'D3 Gateway Editor'. 1.19.5 Download status for Flash cards The download status is now recorded separately for downloads to a controller and control computer, and for the creation of Flash cards. It is possible to toggle the display of the download status with a button in the CaeManager between the status of the connected targets (controller and control computer) and the status of the created Flash cards. A3 Upgrade Notes 1-2 Illustration 24: Display of the creation status of the Flash cards The most important additional information, which is also stored on the Flash card, is shown in a tool tip for the Flash cards that have been created in the CaeManager. The actualization of the download status for Flash cards must be confirmed with an additional dialog after creating the Flash cards with the DownloadManager. In this way, it is possible to decide if a Flash card should only be created for testing purposes, or if the creation status in engineering should be refreshed. Illustration 25: Adoption of the download status 1.19.6 System variables for the download status In APROL R 3.6-02, new system variables have been made available for the evaluation of the download status of servers and operator stations: DownloadState DownloadTargetName LastDownloadStartTime It is possible to detect if a download is actually being carried out, which target the download has, and when the last download was made, for each computer that physically exists when using the new system variables in the logic (e.g. on a controller). The variables are written to a remanence file of the Iosys when they have been placed in a CFC and a 'Build' is carried out, and they are available as remanent variables after a successful download. Upgrade notes 1-3 It is thus ensured that the variables are still available when all of the variable providers and clients are terminated. The new system variables are also evaluated in the hyper macros of the 'SysMon' CAE library. Illustration 26: Applicatory evaluation of the download status, and via 'SysMon' library 1.19.7 Extensions in the process graphic editor Display of selected objects: The graphic objects that are displayed as movable in the process graphic, by placing a graphic block (graphic macros) or creating a direct dynamization, can be selected individually or via multi-select in the process graphic editor ('Preview' tab). The selected graphic parts are marked as follows in the Preview tab of the 'Process graphic' project part: Objects from CFC graphic blocks = blue Objects from the direct dynamization = green Graphic objects that were created directly in the process graphic can only be edited in the DisplayEditor. Tracing the objects The objects that are placed on the process graphic and originate from a direct dynamization are highlighted after having selecting them and switching to the 'I/O Mapping' tab. Also, the blocks that are selected in the I/O mapping are selected and marked in color in the process graphic after switching to the 'Preview' tab in the process graphic. Details can be found in the APROL documentation 'B2 Project Engineering', chapter Direct process graphic dynamization. A3 Upgrade Notes 1-4 1.19.8 Improved navigation in the CaeManager Overview dialog for multi-select actions: The procedure of carrying out an action on several project parts at once has been finalized in the CaeManager. All the project parts that are affected are listed in this additional dialog before the action is carried out. Furthermore, project parts that are faded out in the CAE navigation, because of the user options, are colored 'blue' in the overview. Project parts that could be hidden are those that are scalable, or cancelled library blocks, for example. Project parts that cannot be considered for the action because of the current rights allocation are colored 'red'. If desired, this confirmation dialog cab be suppressed and re-activated via the 'Editing a filtered amount of project parts' checkbox in 'Extras / User Options', in the Confirmations tab.. Extended possibilities for confirming project part versions: It is now possible to confirm project part versions that belong to a complete download state, or versions that have only been compiled. Illustration 27: Confirming all compiled versions It is thus possible to confirm the download status of the entire CAE project, or only that of the compiled version of a directory, via the 'Edit / Confirm' menu or the context menu. The possibility to confirm any one of the versions is still also available. If a confirmed version is re-confirmed, the new confirmation text is pended to the old one. Upgrade notes 1-5 1.19.9 Optimization in the CFC editor Further comfortable functions have been made available in APROL R 3.6-02 in order to raise the efficiency of creating or expanding CFCs. Tool tips for logical connection lines: A tool tip has been placed on the logical signal lines in the CFC for quick and easy signal identification. The tool tip contains the IEC type and the signal source (including I/O type, name, and description). It is possible to jump directly to the signal source via the 'Connections / Center Signal Source' context menu. The tool tip also obtains the number of targets (Target of the connection). These can be jumped to via the connection's property dialog. Moving connection segments: The automatic routing can be reduced to the next but one supporting point of the selected connection when moving connection segments. Thus, not all connections are completely re-routed and existing complex bus structures are preserved. Block instance search in a CFC A search dialog, with which it is possible to search for block instances by their instance name, description or type, is opened with the 'Search for block instance' context menu in the CFC editor. The selected section of the CFC editor is moved to the position of the block and the block is highlighted by selecting the block in the dialog. The dialog can be left open during the subsequent CFC editing. A3 Upgrade Notes 1-6 Illustration 28: Comfortable search for block instances 1.19.10 Renaming block instances in CFCs and hyper macros As of APROL R 3.6-01 it was possible to rename block pins and hyper macro constants in library blocks, in all of the existing versions, with the AprolCaeRename service script. As of APROL R 3.6-02, it is possible to change block instances in hyper macros and CFCs, whilst retaining the project information in the respective hyper macros, when using the '-instance' option. The renaming of block pins is a database-global action and has an effect on all projects in the CAE database. An exclusive access to the database is necessary for this. Therefore, no other applications are allowed to access the CAE database when the script is being executed. Details can be found in the APROL documentation "B2 Project Engineering", chapter Renaming of block pins and block instances via service script. 1.19.11 Plant-specific debug connections The configuration of a 'Plant-specific debugging connection' supports the following scenarios: The operation of one CAE project, in an identical version, on serveral plants. A productive plant that was created with an identical project state must be reachable from an engineering / runtime test system. By entering 'Plant-specific debug connections' in the 'Project properties' (Engineering Options tab), the engineering system is made aware of the corresponding alternative runtime servers with their host names or an IP addresses. Upgrade notes 1-7 In order to carry out a debugging over one of these connections, the connection must be activated in the CaeManager, in 'Extras / Plant-specific Debug Connections'. From this point on, each debug session (CFC, SFC, process graphic editor) is established with this connection. The following points must be ensured for a correct debugging: The alternative plant must have an identical project state to the current engineering. It must be possible to reach the correct runtime systems via the configured host names / IP addresses When plants have been configured for redundancy, the master / slave connection combination must be configured correctly. If another connection other than that in the current engineering is used during an active debug session, the entire CaeManager frame is colored to signalize this special state. 1.19.12 Historical recording and evaluation of the limit inputs of a trend block As of APROL R 3.6-02, trend block limit inputs that are configured dynamically are recorded by the TrendServer and made available to the TrendViewer for an extended qualitative evaluation of the course of a trend. For dynamically configured limit values, there is an additional possibility in the visual properties of a trend slot to activate the limit values and to use dynamic limits. If the limit display is activated, the historical limit value is faded in as an additional trend, whereby the color and pattern can be allocated freely for each limit value that is exceeded of fallen short of. If only constant values are defined in the limit inputs then these are not recorded and are shown as usual with constant lines in the trend diagram. A3 Upgrade Notes 1-8 Illustration 29: Historical evaluation of the limit inputs of a trend block 1.19.13 Value change with the multiple choice of trend slots In order to change several related process trends in the Y scaling and / or the time axis, they can be marked with multi-select and adjusted via 'Edit'. It is thus possible to evaluate several reference curves in one work step. If there are different property values in the selection then the respective fields in the dialog are colored and left empty. It is possible to align the selected trends by entering a new value here. All changes to the properties are immediately visible in the TrendViewer and can be revoked with discard or cancel. Upgrade notes 1-9 Illustration 30: Value change with the multiple choice of trend slots A3 Upgrade Notes 1-10 1.20 New features after updating to APROL R 3.6-01 Amongst various corrections, the following additions are contained in APROL R 3.6-01: 1.20.1 Actualized controller AR-OS versions The AR-OS version V0306 (Default AR-OS version) is supplied in the scope of APROL R 3.6 for Intel platform controllers. As of APROL R 3.6-01, the current Automation Studio for controller hardware configuration is delivered in the version 3.00.81.18. 1.20.2 Changed download behavior of the controller variables All of the tasks that have changed are analyzed before a download when using an AR-OS B0306 or newer. These changes affect both controller global variables, and task-local variables in overload mode or CopyMode-EI mode. In the case of a partial initialization, a query is made before the download starts if the download should take place via CopyMode-EI mode with partial initialization, or via overload mode with a total initialization of all variables. This decision is then valid for all affected tasks. 1.20.3 Changed settings for the controller encoding Up to now, the controller encoding settings had to be made explicitly for each driver instance. As of APROL R 3.6-01, the default value for the encoding can be globally set in the '- stringEncoding' driver option in the CC modules. The controller encoding must be checked and set once in the CaeManager menu item 'Extras / Global Engineering Options'. It is recommended to set all of the drivers in existing projects to the automatic encoding setting. 1.20.4 Reactivation of the APROL systems The new system variables for detecting the download status have now been made available permanently and independent of any started DownloadManager instances. Upgrade notes 1-1 The following variables for monitoring the partitions have also been introduced in APROL R 3.6-01: It is necessary to reactivate each APROL system, so that the variables are made available within the CAE project. This must be carried out before a 'Build' of the CAE Project. 1.20.5 Import / Export of hyper macros, CFCs and process graphics The internal database format for hyper macros, CFCs, and process graphics has been changed in order to ensure their uniqueness. It is therefore not possible to import the above mentioned project parts from an R 3.6-00 (or older) into the current APROL R 3.6-01. A3 Upgrade Notes 1-2 1.21 New features after updating to APROL R 3.6-00 Amongst various corrections, the following additions are contained in APROL R 3.6-00: 1.21.1 Actualized controller AR operating system The AR-OS version E0306 (Default AR-OS version) is supplied in the scope of APROL R 3.6 for Intel platform controllers. As of APROL R 3.6, the current Automation Studio for controller hardware configuration is delivered in the version 3.00.81.15. 1.21.2 Current AutoYaST DVD The new AutoYaST DVD version 3.6-00 is delivered within the scope of APROL R 3.6. 1.21.3 Installation of the APROL system software Because the scope of the APROL system software has now risen above that of one DVD, now two DVDs are necessary for the installation of the system software. Both of the DVDs are always necessary for the installation of an engineering or runtime system. 1.21.4 Problems when using the Intel graphic chip set with SLES 11 There may be problems with the monitor display in connection with the kernel module driver from SLES 11 on APROL servers that have an Intel graphic chip set. This can be recognized in the consoles F1-n with an extreme flickering and a very low resolution. There may also be display problems in the graphical X environment Because of this, it is recommended to replace the kernel mode driver that is installed automatically on these computers via AutoYaST with the 'INTEL Legacy driver' that is also supplied on the AutoYaST DVD. Proceed as follows in order to fix the error: Step Description 1 After installing the APROL system software, the 'sax2' must be started in the Linux run level 3. 2 Input the following command: sax2 -m 0=intellegacy 3 Carry out the desired graphic configuration and save it. 4 Perform a reboot of the computer. Upgrade notes 1-1 1.21.5 Change of the Python version in SLES 11 and the resulting adjustments APROL R 3.6 is supplied to you with the newest SUSE Linux Enterprise Server 11 (SLES 11). The following adjustments are necessary and recommended because of the new Python version 2.6. Recommendations and information can be found in the official Python documentation: http://docs.python.org/whatsnew/2.5.html#porting-to-python-2-5 http://docs.python.org/whatsnew/2.6.html#porting-to-python-2-6 1.21.5.1 Necessary adjustments Replacement of the string exceptions: All of the places where raise "txt" is used, or raise is used with another string variable, lead to a TypeError exception. These are replaced with raise Exception("txt") Removed Python modules: The following modules have been removed in Python 2.6 from Python 2.4: gopherlib, rgbimg, regex, regsub, statcache, tzparse, whrandom It is not possible to give general basic guidelines for all modules for the replacement of code that the modules use. Adjustment of the Python code for UCB blocks If UCB blocks with Python code have been created in customer libraries, an adjustment of the code may be necessary because of the change to the Python version 2.6. Information about Python functions that are no longer supported are logged automatically in the error output of the corresponding UCB block. The output of the error channel for the UCB script that belongs to a UCB block are logged in the /home/ Thus, it must be checked that the error file (*.err) has the length '0' after the script has been executed. A3 Upgrade Notes 1-2 1.21.5.2 Recommended adjustments Discontinued Python modules: The following modules have been cancelled from Python 2.4 to Python 2.6: md5, sha, audiodev, bgenlocations, buildtools, bundlebuilder, Canvas, compiler, dircache, dl, fpformat, gensuitemodule, ihooks, imageop, imgfile, linuxaudiodev, mhlib, mimetools, multifile, new, pure, statvfs, sunaudiodev, test\.testall, toaiff, MimeWriter, mimefy, posixfile, popen2, sets The md5 module should be replaced with the hashlib module Replace import md5 with import hashlib Replace m=md5.new(string) with m=hashlib.md5(string) It is not possible to give general basic guidelines for all modules for the replacement of code that the modules use. Syntax change in exception handling: Exception instance for a single exception class: Old syntax: except ExceptionClassA, exp: New syntax: except ExceptionClassA as exp: Exception instance for several exception classes (when several exception classes are processed in the same way) Old syntax: except (ExceptionClassA, ExceptionClassB), exp: New syntax: except ExceptionClassA, ExceptionClassB as exp: Old and new syntax are valid in Python 2.6 Only the old syntax is valid in the Python version 2.4 (used in APROL R 3.4). 1.21.6 Removal of cancelled 'Control computer (R 3.2 mode)' Before updating to APROL R 3.6, all cancelled 'Control computer (R 3.2 mode)' project parts must be removed completely from the CAE project (including from the CaeManager trash can). If this does not happen then an upgrade to APROL R 3.6 is refused! The update of the CAE database to R 3.6 is terminated with an error message. 1.21.7 'Supervised' flag for newly created controllers If a new controller is created in APROL R 3.6 then it is set automatically into 'Service mode' when a card is removed from it. As of APROL R 3.6, the 'Supervised' flag of each card is set to 'ON' per default. The 'Supervised' flag of each module in Automation Studio must be set explicitly to the value 'OFF' in order to ensure that the newly created controller does not go into 'Service mode'. Now proceed for this as follows: Upgrade notes 1-3 Step Description 1 Select the module that is to be configured in the 'physical view' in Automation Studio , and select the 'Open I/O Configuration' item in the context menu. 2 Select the 'General / Module supervised' entry and set the value 'OFF' with the combo box. Illustration 31: Configuration of the 'Supervised' flag A change in the default behavior is not possible! 1.21.8 Discontinued 'Controller (R 3.2 mode)' The cancelled 'Controller (R 3.2 mode)' can still be generated ('Build' process) within the scope of existing projects, but has limited editing possibilities and does not support the main additions in controller handling. no support of the AS 3.0 code generation, No use of an AR-OS version larger or the same as AR 3.0, no use of the Service Diagnostics Manager, allocation of Powerlink slaves on a Powerlink master module is no longer possible, No 'Build (target)' possible, i.e. a rebuild of the entire project is necessary in order to generate. 1.21.9 No support of the VMware version 7.0 on an APC 620 An operation of the VMware version 7.0 is not possible on an APC 620 because the version 7.0 only supports processors with PAE (Physical Address Extension). A3 Upgrade Notes 1-4 It is generally not recommended to use an APC 620 as an engineering server because of performance reasons. 1.21.10 Uniform nomenclature for control computer driver launching options The launching options for the APROL process control system drivers have been adjusted to a new, uniform and self-explaining nomenclature within the scope of APROL R 3.6. The adjustment takes place automatically in the scope of the CAE database update. If a driver is called up actively in an existing project (e.g. in a script) then these scripts must be adjusted to the new nomenclature. Application Option name (old) Option name (new) AprolReduWatch -conn -connTime AprolReduWatch -ping -pingTimeout ControllerManager -no_splash -noSplash CustomerApplication -terminate_exitcode -exitCodeOnTermination dcsDriver -controllerStringEncoding -stringEncoding dcsDriver -restartTimeout -connectTimeout dcsEventDriver -n -name dcsEventDriver -controllerIpAddr -ip dcsEventDriver -controllerPort -port Dispatcher -cfg -cfgFile Dispatcher -controller -driverName DisplayCenter -no_splash -noSplash DownloadManager -no_splash -noSplash EventDriver -controller -ctrlInstance EventDriver -controllerPort -port EventDriver -controllerStringEncoding -stringEncoding EventDriver -restartTime -connectTimeout InaDriver -controller -ctrlInstance InaDriver -controllerStringEncoding -stringEncoding InaDriver -restartDelay -connectTimeout IosXfer_e -connect_at_start -connectAtStart IosXfer_e -file -cfgFile MbpDriver -appName -appName MbpDriver -controller -driverName MbpDriver -controllerStringEncoding -stringEncoding MbpDriver -restartDelay -restartDelay Upgrade notes 1-5 MbpDriver -restartTimeout -connectTimeout ParameterCenter -no_splash -noSplash ProfiboardDriver -n -name ProfiboardDriver -controller -ctrlInstance ProfiboardDriver -controllerStringEncoding -stringEncoding ProfiboardDriver -reduCheckTime -connectTimeout ProfiboardDriver -restartTime -restartDelay RK512Driver -addr -ip RK512Driver -controller -driverName RK512Driver -controllerStringEncoding -stringEncoding simaticDriver -cfg -cfgFile simaticDriver -ipMasterAddr -ipMaster simaticDriver -ipSlaveAddr -ipSlave simaticDriver -controller -driverName simaticDriver -controllerStringEncoding -stringEncoding StartManager -no_splash -noSplash TiDriver -l -logFile TiDriver -n -name TiDriver -controllerName -driverName TiDriver -controllerStringEncoding -stringEncoding TiDriver -restartTime -connectTimeout TrendViewer -cnf -cfgFile TrendViewer -no_splash -noSplash wdpfDriver -n -name wdpfDriver -restartTime -connectTimeout 1.21.11 Renaming of the CaeViewer in CFCViewer The 'CaeViewer' application has been renamed to 'CFCViewer'. After upgrading to APROL R 3.6, it is necessary to configure a new instance of the 'CFCViewer' application in the 'APROL system' project part, in the 'System monitoring' section. If a 'CaeViewer' application is called up actively (i.e. outside of the CAE) in existing CAE projects (e.g. in scripts), then these scripts must be adjusted to the new application name. A3 Upgrade Notes 1-6 Illustration 32: Configuration of the CFCViewer 1.21.12 New UcbServer launching option The UcbServer has obtained an additional mandatory '-maxExecTime' option, which specifies the maximum execution time for UCB scripts. The following adjustments are therefore not necessary when upgrading from an APROL R 3.4-07. The signal handling after a download (SIGUSR2), or stopping (SIGTERM) the UcbServer must definitely be taken into account and captured in the program code of all UCB blocks. After an upgrade to APROL R 3.6-00, the new '-maxExecTime' option must be chosen once in all 'APROL system' project parts, in existing CAE projects, and provided with an acceptable value such as the default value. UCB scripts that appear to have a longer execution time (and are logged in the APROL system messages) must be adjusted with respect to their execution time. The '-init', '-deinit', and 'run' sections of the UCB scripts must be extended with respect to this. Details can be found in the APROL documentation 'B3 CAE Library Engineering', chapter The UCB mechanism. 1.21.13 Changes in the 'SysMon' CAE library Due to a change in the internal 'CcInst' variable, the followings steps are to be carried out when upgrading to APROL R 3.6. The necessary configuration takes place in the 'Block properties', in the 'Internal variables' tab. If the 'MonCc01' and 'MonCcTask01' hyper macros are being used in the logic of existing CAE projects, the instance name of the control computer must me entered, including the '_M' suffix. Upgrade notes 1-7 If the 'MonCtrlCpu01' hyper macro is being used in existing projects then the '_M' suffix must be removed from the instance name of the control computer. 1.21.14 Configuration of an empty string as default value As of APROL R 3.6, it is basically possible to pre-allocate an empty string as a default value to a block input of the type 'SSTRING' or 'LSTRING' in the library engineering. Furthermore, default values form the CAE library can be overwritten with an empty string acting as a constant when creating instances of blocks in a CFC or process graphic (in the direct visualization). Default values that have been configured in the CAE library and that are overwritten in the CAE project are marked with a separate icon. Illustration 33: Removal of a locally changed value 1.21.15 Extended system variables for "SystemType" and "APROLDATASpace" A new 'SystemType' system variable has been added for the system and self-diagnosis. The new 'SystemType' variable can adopt the following values: 1 = Runtime system 2 = Operator system 3 = Runtime system with integrated operator system 4 = Gateway system The type of configured APROL system can be detected during runtime with this system variable. A3 Upgrade Notes 1-8 As the APROL AutoYaST installation no longer intends a separate 'home' partition, the previously existing variables have been replaced with variables for the 'APROL_DATA' partition that can be configured optionally. If the 'home' partition information is still needed in a CAE project, it can be obtained via the freely configurable partition variables (Partition1Space to Partition4Space). Obsolete variables: FreeHomeDiskSpace, HomeDiskSpace, UsedHomeDiskSpace New Variables: FreeAPROLDATASpace, APROLDATASpace, UsedAPROLDATASpace After an upgrade, all APROL systems must be reactivated and newly compiled before a build of the CAE project takes place, in order to create the correct system variables. If the old system variables are being used in the project, they must be replaced or removed in the respective CFC. 1.21.16 Removal of discontinued blocks from the 'APROL' CAE library Some of the blocks in the APROL library that have been marked as 'cancelled' for a number of major releases can now no longer be used. An error message is output for instances that are still placed. After upgrading the system software to R 3.6, and before updating the CAE database, the discontinued blocks for which there is no substitute must be moved to a separate 'SavedBlocks' library with the 'AprolSaveObsoleteBlocks' script. When used, the 'AprolSaveObsoleteBlocks' script must definitely be executed before the CAE database is updated to the APROL R 3.6. Subsequently, a build (library) must be carried out. The 'AprolExchangeObsoleteBlocks' script can be used for discontinued blocks that have a substitute. All of the placed instances of the cancelled blocks in the project are exchanged for the stipulated substitute blocks automatically. If the scripts are executed after each other, the 'AprolExchangeObsoleteBlocks' script must be executed before the 'AprolSaveObsoleteBlocks' script. old block Substitute block AprFbAlarmSel AprFbAlarmSel2 AprFbAlarmSel4 AprFbAlarmSel8 Upgrade notes 1-9 old block Substitute block AprFbAlarmSel16 AprFuGetLSB_BYTE AprFuGetLsbBYTE AprFuGetLSB_WORD AprFuGetLsbWORD AprFuGetLSB_DWORD AprFuGetLsbDWORD AprFuGetLSB_LWORD AprFuGetLsbLWORD AprFuGetMSB_BYTE AprFuGetMsbBYTE AprFuGetMSB_WORD AprFuGetMsbWORD AprFuGetMSB_DWORD AprFuGetMsbDWORD AprFuGetMSB_LWORD AprFuGetMsbLWORD AprFbPicConBool AprFbPicConBOOL AprFbPicConString AprFbPicConSTRING If the old CAE blocks are being used in the project, they must be replaced or removed in the respective CFC. 1.21.17 Typecasting of the CFCs for controller and control computer tasks The following types of usage can be chosen when creating a CFC: Controller task with optional control computer task part Only control computer task A3 Upgrade Notes 1-10 Illustration 34: Allocation of the task in the CFC properties The 'Complex CFC creation with multiple task allocation' that has been offered for choice up to now will no longer be offered in favor of a better signal tracing and a clear debugging. CFCs, which have already been created as a complex CFC with multiple task allocation, and have then been switched to another CFC type, can be switched back to a "Complex CFC with multiple task allocation" again at any time. If the creation of a complex CFC with multiple task allocation is necessary in certain cases, this function can be set explicitly with the help of the B&R support. 1.21.18 Import of existing Python modules As of APROL R 3.6, the support of Python modules that are in the file system has been dropped. Modules that have been used up to now must be imported into one of the respective new project parts, depending upon the usage. For this purpose, create the respective project part and choose the "Import" menu item in the context of the program code. The Python module that is to be imported can be chosen in the file system with a file choice dialog. The program code is imported after the choice that has been made is confirmed with the [Open] button. Upgrade notes 1-11 Illustration 35: Import of existing Python module from the file system Afterwards, it is necessary to delete the following directories from the file system: /home/ Illustration 36: Message for the import of old Python modules into the new project parts A CAE message that points out an obsolete directory is additionally entered in the 'APROL system' project part. Subsequently, existing allocations for all "APROL system" project parts must be adjusted from the old Python modules to the new Python control modules. The configuration change must also be made for each of the DisplayCenter and LoginServer APROL application's "-pythonModule" option. The prerequisite for a possible allocation is a previous activation of the 'Python control module' project part in the CAE project. A3 Upgrade Notes 1-12 Illustration 37: Allocation of the control module in the scope of the CC configuration In contrast to the already existent "Python module" project part in the context of the CAE libraries, the modules of the tree new project parts are created with their instance names, and not with their project part name. Please note that modules with the same instance names cannot be activated at the same time! The new Python modules are stored in the following directories in the runtime environment after the download: Module Directory Python modules (Process graphic) / 1.21.19 Renaming of the 'STRING' data type to 'SSTRING' The 'STRING' data type that has been used up to now has been renamed to 'SSTRING' in APROL R 3.6. Due to the AS 3.0 code generation in APROL R 3.6, it may come to differences between the same-named 'STRING' data type in Automation Studio (freely configurable length) and the data type in the APROL environment (fixed string length up to now). Upgrade notes 1-13 The controller address database (dbk) for 'Controllers (R 3.2 mode)' should be deleted after upgrading to APROL R 3.6, so it can be ensured that the available global memory area has the same size after the data type change. The controller address database for 'Controller (R 3.2 mode)' can be found in the directory home/ The APROL project rule editor that is used for creating custom made system connections has been adjusted to the new 'SSTRING' data type in APROL R 3.6. The internal change in configuration is to be taken into account when using custom made drivers, which are based on the APROL project rule editor, and these drivers are to be eventually adjusted. A change to the 'type view' and a multiple choice of all controllers allows a quick and comfortable compilation of several project parts. 1.21.20 Use of the AS 3.0 code generation The 'Stricter plausibility check for AS 3.0 code generation' is set per default for all CAE libraries and projects in APROL R 3.6. You are made aware of invalid identifiers, which must be corrected for AS 3.0 compatibility before the controller is put into operation, when the CAE block is compiled (or during a 'Build (Library)'). If it is necessary to switch on the AS 2.x code generation for the new 'Controller' project parts, this can be done in special cases with the help of the B&R support. The old code generation is still used for the discontinued 'Controller (R 3.2 mode)' controllers. A list of the key words can be found in the APROL validator help page. This can be opened in the CaeManager via the 'Help / APROL Info validators' menu. Select the validators that are marked with 'intensified' and open the respective HTML page via double-click. ST and AWL: ABS, ACOS, ACTION, ADD, ADR, AND, ANDN, ASIN, ASR, AT, ATAN, BIT_CLR, BIT_SET, BIT_TST, BY, CAL, CALC, CALCN, CASE, CONSTANT, CONVERSION, COS, DIV, DO, EDGE, EDGENEG, EDGEPOS, ELSE, ELSIF, END_ACTION, END_CASE, END_FOR, END_FUNCTION, END_FUNCTION_BLOCK, END_IF, END_PROGRAM, END_REPEAT, END_VAR, END_WHILE, EQ, EXIT, EXP, EXPT, FOR, FUNCTION, FUNCTION_BLOCK, GE, GT, IF, JMP, JMPC, JMPCN, LD, LDN, LE, LIMIT, LN, LOG, LT, MAX, MIN, MOD, MOVE, MUL, MUX, NE, NOT, OR, ORN, PERSISTENT, PROGRAM, R, READ_ONLY, READ_WRITE, REPEAT, RET, RETAIN, RETC, RETCN, RETURN, ROL, ROR, S, SEL, SHL, SHR, SIN, SIZEOF, SQRT, ST, STN, SUB, TAN, THEN, TO, TRUNC, UNTIL, VAR, VAR_ACCESS, VAR_CONFIG, VAR_GLOBAL, VAR_IN_OUT, VAR_INPUT, VAR_OUTPUT, WHILE, XOR, XORN IEC types: A3 Upgrade Notes 1-14 ANY, ANY_BIT, ANY_DATE, ANY_INT, ANY_NUM, ANY_NUMORBIT, ANY_REAL, BOOL, BYTE, DATE, DATE_AND_TIME, DINT, DREAL, DT, DWORD, INT, LINT, LREAL, LSTRING, LWORD, REAL, SINT, SSTRING, TIME, TIME_OF_DAY, TOD, UDINT, UINT, ULINT, USINT, WORD Automation Basic: ACCESS, BIT, DOWNTO, ELSEACTION, ENDACTION, ENDCASE, ENDIF, ENDLOOP, ENDSELECT, EXITIF, FLOAT, FUB, GOTO, INT16, INT32, INT8, LONG, LOOP, LSL, LSR, NEXT, POINTER, SELECT, STATE 1.21.21 New location of the TrendServer As of APROL R 3.6, the recording location of the TrendServer trend data has been adjusted to the well-known recording location for historical data. The TrendServer logging now takes place in the directory: /home/aprolsys/APROL_DATA/chronotrend/ Additional 'runtimesystem' and 'project' CGI parameters are now necessary in the URL when accessing trend data via the web. All application queries must be adjusted to the new parameters. The old code generation is still used for the discontinued 'Controller (R 3.2 mode)' controllers. 1.21.22 DTD for TrendViewer configurations A DTD file has been made available in /opt/aprol/cnf/TrendViewer/TrendViewerConfig.dtd for the validation of the TrendViewer's configuration files. All of the TrendViewer configuration files are now checked with this DTD in order to guarantee that there are no errors in the configuration. If the TrendViewer configuration does not contain a DTD reference (because it has been created in APROL < R 3.6) then only a warning is generated at present, in which the user is requested to re-save and thus update the configuration. The following head entry is added automatically to the configuration file when saving: Upgrade notes 1-15 1.21.22.1 Update mechanism for existing records Existing trend records (meaning all TRD containers) are shifted automatically from the /home/ The following characteristics are to be taken into account: If a separate partition has been created for the APROL_DATA directory then an additional dialog explicitly points out this state. Please note that in this case, a move of the directory takes up more time! The data are subsequently available for a query. 1.21.23 Adoption of values in the DisplayCenter via confirmation with [Enter] key The adoption of values in the DisplayCenter via [Enter] key can be switched off as needed in the project properties, 'Runtime option' tab. Up to now, the adoption of the value in the DisplayCenter took place after a change in the focus. The 'Adoption of values in the DisplayCenter via confirmation with [Enter] key' option is activated per default. If this option is activated then each value input into a widget of the type "InputOutputBox", as well as in a control of the type "InputLine" is to be confirmed with the [Enter] key. Otherwise, the value is automatically adopted when a focus change occurs. Illustration 38: Adoption of values in the DisplayCenter via confirmation with [Enter] key A3 Upgrade Notes 1-16 1.21.24 Clear marking of the CiR status As of APROL R 3.4-03, the actually set state for CiR (Configuration in Run) in Automation Studio is marked in the CaeManager, in the hardware editor of the respective controller. In order to considerably increase the clarity and system security, the mode that has been set in Automation Studio is marked with descriptive tool tips as of APROL R 3.6. Illustration 39: Clear marking of the CiR status The icons signalize the following states: CiR active CiR deactivated CiR unknown When using the CiR mode, all of the changes to the controller hardware that would make a controller warm-start necessary are suppressed for security reasons. Only changes in the hardware, or operation mode, that do not result in a controller restart can be made as long as the CiR mode has been activated in Automation Studio. Thus for example, an expansion of a DP network is no longer possible with an activated CiR mode, as a restart is necessary for this. 1.21.25 Firefox as new standard browser Firefox is available, as of APROL R 3.6, as the standard browser for displaying the APROL documentation and the web based reports. The default behavior of opening a new browser window in the APROL Firefox has been changed. A new tab is now opened per default (instead of a window). The settings that have been made by the user are not overwritten after updating the APROL system software. Upgrade notes 1-17 1.21.26 Handling the VMware images Basically you have the following possibilities in the scope of the upgrade to APROL R 3.6 for using the VMware images Backup of the VMware image in the scope of APROL R 3.4 (recommended) a) Upgrade of the system software to APROL R 3.6 including new installation of the VMware version 7.0 b) Restoration of the VMware image backup from APROL R 3.4 c) No actions to be taken with respect to Windows licensing d) If the restored VMware is <= version 6.5, an update of the VMware tools is definitely mandatory. Details can be found in the following chapter! Advantage: A new licensing of Windows is not necessary Use of a new VMware image a) Upgrade of the system software to APROL R 3.6 including new installation of the VMware version 7.0 b) Use of the newly installed VMware image c) Windows licensing is necessary d) No further actions with respect to the VMware tools Disadvantage: A new licensing of Windows is necessary. 1.21.26.1 Procedure for updating the VMware tools Now proceed for this as follows: Step: Description: 1 A test license for the VMware 7.0 is installed in this engineering environment (Engineering system) during the CAE update. This license is to be exchanged immediately after the update with the delivered VMware license. Details about licensing can be found in the APROL documentation "E1 Controller & I/O", chapter Licensing the VMware. 2 Call up the 'Extras/Configure Windows XP (VMware)' menu item in the CaeManager. 3 After Windows has started, a necessary update of the VMware tools is signalized by a yellow triangle on the VMware tools icon (in the info area of the Windows status bar). The 'VMware tools properties' dialog is opened with a double-click on the yellow triangle. Confirm the [Update tools]´button in this dialog, in the 'Options' tab. A3 Upgrade Notes 1-18 Step: Description: 4 A VM reboot is necessary after the update has been carried out successfully. Confirm executing the reboot in the 'VMware tolls Setup' dialog with [Yes]. 5 Log into the Windows environment as the 'APROL' user after the reboot. 6 A new snapshot can be created afterwards in the context of the CaeManager. Thereafter, the VMware can be used as normal. These steps must definitely be carried out before a controller is opened for the first time. The necessary steps are shown in the following overview: Illustration 40: Updating the VMware tools 1.21.27 Use of the entire 32 characters for naming hardware I/Os When configuring project variables in a controller's I/O mapping in APROL R 3.6, the entire length of 32 characters is available for naming hardware I/Os for SG4 controllers. Due to the changed code generation, an HA_, RV_ and as the case may be ST_ variable are no longer registered for an I/O in the system, but a globally-remanent structure-PV is created that has the name of the I/O. This structure PV contains the 'ha', 'rv', and as the case may be 'st' elements, whereby the structure elements adopt the function of the previously individual variables. ('IO.ha' intead of , 'HA_IO', and so on.) Necessary adjustments in CAE: Upgrade notes 1-19 After each time that the data storage has changed, and thus the data structure, it is necessary to reactivate and compile every controller, RIO, CAN, and Powerlink station one time. Subsequently, it is necessary to carry out a 'Build all' of the CAE project. All of the configurations and access points to these Iosys PVs externally from the CAE must be adjusted accordingly. The following list is not necessarily complete: TrendViewer configurations, Report queries using PV names, Alarm list-engineering (BALARMP - configuration), Evaluation of the dependent border PVs of a graphic block ('ibdep' attribute) Customer-specific brpvlist - control file (brpvlist.cfg), manually created gateway configurations in which direct hardware I/O variables are used, Scripts that parse and evaluate the generated configurations, e.g. for drivers or remanence. 1.21.28 Classification of a function block's local variables In the scope of the integration of Automation Studio (AS) in APROL, a 'category' has been introduced to the list of local variables in order to have a greater choice. This allows access to the local variables of the type 'structure'. There are three categories available: Type Description IEC type for choosing the basic IEC types such as BOOL, INT, etc. IEC FB for choosing and instancing IEC function blocks, such as function blocks from Automation Studio IEC Structure for choosing and instancing variables that have an IEC structure type, i.e. variables that are adopted from the AS code The instancing of function blocks from AS has been moved to a separate list. A combination of the variable definitions will take place in a later APROL release. A3 Upgrade Notes 1-20 1.22 New features after updating to APROL R_3.4-08 Amongst various corrections, the following additions are contained in APROL R 3.4-08: 1.22.1 Actualized controller AR version The AR version B0296, as well as the AR version G0296 (Default AR version) are supplied in the scope of APROL R 3.4-08 for Intel platform controllers. As of APROL R 3.4-08, the Automation Studio for the controller hardware configuration is delivered in the version 3.0.80.25. 1.22.2 Preparatory measures for connecting several AlarmServers to one AlarmMonitor As of the planned APROL R 3.6, there is the possibility of setting up a central overview of the alarm events from different automation areas. In APROL R 3.6 you have the possibility to display and acknowledge the alarm events from several APROL systems together in one AlarmMonitor. The AlarmServer in this APROL R 3.4-08 has been prepared for this planned functionality. 1.22.3 Extensions in the OperatorManager APROL offers a clear and complete management of operators and groups in a single screen, with the OperatorManager. The user-friendliness has been improved in the context of APROL R 3.4-08, amongst others with the following functionality: Multiple selection with the following actions: Adding / removing allocations, deleting, restoring, importing / exporting and printing 1.22.4 Usage of the VMware version 6.5 When updating an engineering system to the current APROL R 3.4-08, a check is carried out to see if a VMware version 6.5.0 is already installed. If this is the case then this version is retained, and the configuration can be continued with the existing VMware license. If an update of the VMware is desired, a separate VMware 7.0 license must be purchased. In this case, the old VMware version must de-installed (as the Linux super user) before the APROL system software update with the 'rpm -e VMware-Workstation-6.5.0' command. Upgrade notes 1-1 Then the new VMware 7.0 is installed automatically during the APROL R 3.4-08 update. Eventual UTF-8 error messages,'UnicodeDecodeError: ascii codec can't decode byte xxx ...' , that are output by the VMware installer of the company VMware.inc during the installation of the VMware version 7.0 can be ignored. A correction is first possible in a later VMware version. Only the VMware 7.0 version can be used with a newly installed APROL computer! A downgrade to the version 6.5.0 is not supported 1.22.5 Specifics after updating to VMware version 7.0 If an upgrade to the VMware 7.0 has been carried out then the following information must definitely be observed: After the automatic update of the VMware during the APROL installation, the VMware tools that are in the virtual machine (Windows XP) must be updated. Now proceed for this as follows: Step: Description: 1 A test license for the VMware 7.0 is installed in this engineering environment (Engineering system) during the CAE update. This license is to be exchanged immediately after the update with the delivered VMware license. Details about licensing can be found in the APROL documentation "E1 Controller & I/O", chapter Licensing the VMware. 2 Call up the 'Extras/Configure Windows XP (VMware)' menu item in the CaeManager. 3 After Windows has started, a necessary update of the VMware tools is signalized by a yellow triangle on the VMware tools icon (in the info area of the Windows status bar). The 'VMware tools properties' dialog is opened with a double-click on the yellow triangle. Confirm the [Update tools]´button in this dialog, in the 'Options' tab. 4 A VM reboot is necessary after the update has been carried out successfully. Confirm executing the reboot in the 'VMware tolls Setup' dialog with [Yes]. 5 Log into the Windows environment as the 'APROL' user after the reboot. 6 A new snapshot can be created afterwards in the context of the CaeManager. Thereafter, the VMware can be used as normal. These steps must definitely be carried out before a controller is opened for the first time. The necessary steps are shown in the following overview: A3 Upgrade Notes 1-2 Illustration 41: Updating the VMware tools 1.22.6 Optional use of the 'License Protection Hardware Key' Additionally to the existing web based licensing since APROL R 3.4-04, you have the possibility, as of APROL R 3.4-08, to optionally use the so called 'License Protection Hardware Key'. The APROL system licensing can take place via the additional use of a 'License Protection Hardware Key' (for use on a USB port) and allows the creation of a 'mobile license'. The installation of the AutoYaST-DVD with minimum version 3.4-12, which contains the 'aksusbd-suse' package, is necessary in order to license via 'License Protection Hardware Key' The installation of the AutoYaST version R 3.4-11 that is delivered as standard with APROL R 3.4-07 is sufficient when using the web based licensing. Detailed information can be found in the APROL documentation 'A2 Getting Started', chapter Optional use of the 'License Protection Hardware Key'. 1.22.7 Checking of the password security As of R 3.4-08 APROL supports a security check during the allocation of passwords. When entering or changing the password in the user's master data (User management) and the operator (OperatorManager), apart from the password length the password that has been entered is checked according to the following criteria: Number of different characters Upgrade notes 1-3 Check for existing entries in the /etc/passwd file Existing entries in the /etc/passwd file (E.g. names) are not allowed to be part of the new password. Comparison with supplied dictionary entries The new password cannot be used when it is in the dictionary or it can be derived from a dictionary entry (E.g. written backwards). If one criterion is not met then this state is pointed out with a tooltip on the corresponding APROL validator. Project-spanning settings for the password security can be made in the CAE project's properties, 'Global options' tab. There, the checking of the before mentioned criteria, as well as the minimum and maximum length of the passwords can be configured for all existing projects in the CAE database. Changes in the project properties of a CAE project thus have an effect on all CAE project in the database. If the 'Extended checking of the password security' option is activated then a password is only accepted when the check criteria have been met. Password that already been entered are not tested, and can still be used. Illustration 42: Project-spanning settings for password security A3 Upgrade Notes 1-4 1.23 New features after updating to APROL R_3.4-07 Amongst various corrections, the following additions are contained in APROL R 3.4-07: 1.23.1 Actualized controller AR version The new AR versions B0296 (Default AR version) and U0295 are available in the scope of APROL R 3.4-07. As of APROL R 3.4-07, the Automation Studio for the controller hardware configuration is delivered in the version 3.0.80.22. The installation of the supplied 2.70.80.2452 version is necessary for the SafeLOGIC configuration via SafeDESIGNER. It is necessary that at least the AR version B0296 is used for this. 1.23.2 Special points for the AutoYaST DVD update An error-free update of the AutoYaST DVD is prevented due to a bug in the java-1_4_2-sun- plugin SuSE Linux package. This is why it is necessary to manually de-install two Linux packages before the update to AutoYaST version 3.4-11. When updating an existing APROL AutoYaST version 3.4-xx to the current version 3.4-11, the java-1_4_2-sun and java-1_4_2-sun-plugin Linux packages must be de-installed with the following Linux command: rpm -e java-1_4_2-sun java-1_4_2-sun-plugin You need the rights of the Linux super user 'root' in order to do this. Alternatively, the deletion of the before mentioned packages can be carried out automatically with a B&R script on the AutoYaST DVD version 3.4-11. After having mounted the AutoYaST DVD, execute the AprolPrepareAutoYaST script as the Linux super user 'root' in the /scripts/ directory. Then the packages that have been mentioned are automatically de-installed. Subsequently, an error-free update to AutoYaST version 3.4-11 can take place. 1.23.3 New UcbServer launching option The UcbServer has obtained an additional '-maxExecTime' option in the scope of APROL R 3.4-07. The value range lies between 0 ... 10s, the default value is 8s. In normal operation, the execution time of the UCB block (i.e. the UCB script) is monitored by the UcbServer and violations are registered by entries in the APROL system messages. Furthermore, the block's "UcbStatus" system pin is set to an extended error value. Upgrade notes 1-1 When the UcbServer is being shut down, the UCB scripts that have not terminated themselves within the intended time are terminated by the UcbServer after the period that is set in the '- maxExecTime Details can be found in the APROL documentation "B3 CAE Library Engineering", chapter Creation of the UCB script. After an update to R 3.4-07 the new '-maxExecTime' option must be chosen once in all 'APROL system' project parts in existing CAE projects and provided with an acceptable value, eventually with the default value. UCB scripts that show to have a longer execution time (APROL system messages) must be adjusted with respect to their execution time. The "-init", "-deinit", and "run" sections of the UCB scripts must be extended with respect to this. 1.23.4 Stricter plausibility control for AS 3.0 code generation In the future APROL R 3.6, only the AS 3.0 code generation will be possible for all CAE libraries and projects. After updating to APROL R 3.4-07, the "Stricter plausibility check for AS 3.0 code generation" (Project properties, 'Engineering options' tab) is also activated per default in existing projects. Due to this, un-allowed identifiers (E.g. pin names) are marked as not permitted when they are entered or during the compilation. The option is automatically set when opening the 'Project properties' dialog. These changes must be explicitly confirmed by the user. The changed option is pointed out when you open the CAE project! 1.23.5 Substitution of PVs in the Gateway Editor As of APROL R 3.4-07 it is possible to carry out any number of self-defined substitutions when substituting PV, e.g. when copying gateway connections. The order of execution of the substitutions can now be selected freely. A3 Upgrade Notes 1-2 The substitution is no longer connected to the copying of a connection, but can additionally be called as a separate functionality of existing connections, or with a multiple selection of PVs. Illustration 43: Opening the PV substitution One or more strings are suggested automatically for the substitution when the substitution dialog is opened. These suggestions are orientated on the same text pattern of the variables chosen for substitution. Apart from the name of the PV it is now possible to substitute the description in the set language environment. Illustration 44: PV substitution 1.23.6 Import/export of the I/O mapping of all of a controller's modules As of APROL R 3.4-07, an import/export functionality is supported for the I/O mapping of all of a controller's modules. Upgrade notes 1-3 After choosing the 'Export des I/O-Mappings' menu item ('Hardware configuration' tab, 'Module configuration' entry), a directory called /home/ The import files in the before mentioned directory have the nomenclature ' Illustration 45: Import/export of the I/O mapping of all of a controller's modules The import takes place in the same way. The allocation of the individual controller modules takes place, per slot, according to the names of the import files. The well-known functionality of allocating the same channel when card descriptions do not match, and a matching message, is still carried out. 1.23.7 Dynamic assignment of a file or URL for the 'TextView' visualization element As of APROL R 3.4-07, the known 'TextView' visualization element for showing a file or URL also allows you to allocate a local or global variable for a file/URL in the DisplayEditor as well as the existing method of a fixed configuration. It is thus possible to allocate the URL dynamically during runtime. If the URL is only to be shown 'locally in the DisplayCenter' then the Python API service functions are to be used. It is thus ensured that these graphic block instances (and so the URL) are not displayed on all operator stations. A3 Upgrade Notes 1-4 1.23.8 Multiple-choice in the OperatorManager APROL offers a clear and complete management of operators and groups in a single screen, with the OperatorManager. You stipulate the operation possibilities of individual operators in the process control system with the allocated groups and the rights that have been configured therein. The quick allocation of rights takes place via a drag & drop between the groups and operators. As of APROL R 3.4-07, the multiple-choice of groups or operators is supported. It is so possible to assign several groups to one operator or several operators to one group. The 'Delete' and 'Export' functionalities will also be available for multiple selections in the future APROL R 3.6. Upgrade notes 1-5 1.24 New features after updating to APROL R_3.4-06 Amongst various corrections, the following additions are contained in APROL R 3.4-06: 1.24.1 Actualized controller AR version The new AR versions Q0295 and U0295 (Default AR version) are available in the scope of APROL R 3.4-06. As of APROL R 3.4-06, the Automation Studio for the controller hardware configuration is delivered in the version 3.0.80.19. 1.24.2 Additions in the licensing mechanism As of APROL R 3.4-06, a new licensing can be carried out when an APROL license already exists. You thus have the possibility, for example, of replacing a pure runtime license to a runtime-engineering license. You can license all of the APROL releases, which have been made public up to a maximum of 18 months after the delivery date of your release, with the serial number you have. The time span between delivery and release date is checked in regular intervals. If a release is installed from which the time span is exceeded, then it is pointed out that a new licensing must be carried out. If it is not possible to internally determine the a delivery date (via SAP license database) at the time of licensing then, as of APROL R 3.4-06, the license date is used as the start point for the before mentioned period instead. 1.24.3 Overlapping order of placed image macros As of APROL R 3.4-06, when you are creating a process diagram you have the possibility to retrospectively stipulate the desired overlapping order for image macros that have already been placed. The overlapping order at runtime can be stipulated with the [Shift picture block back] and [Pull picture block forward] context menu items of a picture macro. Upgrade notes 1-1 Illustration 46: Stipulating the overlapping order of a placed picture macro 1.24.4 Performance increase when checking the APROL installation The creation of the CheckInstallation report for a consistency check of the existing APROL installation has been revised for the modules and libraries that are to be checked as of APROL R 3.4-06, so that a gain in the performance could be reached during the installation from APROL, and with the report display. The cyclic check (cron job) was optimized to that affect, so that a heavy system load is avoided. The load of an APROL computer during the checking procedure could be greatly reduced by this. 1.24.5 New options for the RK512 driver Two new options have been made available for the RK512 driver. This deals with extended options, which are not necessary in the scope of a standard RK512 driver connection. Option: Description -noExpectWriteResponses The driver should not wait for "Write" responses from the communication partner. - noSendWriteResponses The driver should not send a "Response" to a "Write request" from the communication partner. Please use this option solely for debugging purposes when the mentioned behavior is demanded by the system configuration. A3 Upgrade Notes 1-2 1.24.6 Adjustment of the status variables for the monitoring of the cross driver The configuration of the controller cross communication takes place with the ApDrvCross controller driver in the CaeManager. The nomenclature of the status variables for monitoring the cross driver have been changed in APROL R 3.4-06. When using the 'MonCtrlDrvCrs01' block, from the 'SysMon' library, for monitoring the cross driver then all of the variables in the controller's controller-controller coupling must be re-created due to the changed nomenclature. Illustration 47: Change of the nomenclature for 'AprDrvCross' status variables 1.24.7 Actualized firmware version for DP master cards APROL supports the use of the DP master cards EX450-66.1 and 3IF766.9. As of APROL R 3.2-06, the actualized firmware version V1.210 is recommended for theses DP master cards. The hardware can also be started with an outdated firmware version, but a correct operation cannot be guaranteed. The current firmware files are in the directory /opt/aprol/BR_ARs/Firmware/ Please note that a firmware update is solely to be carried out with the B&R Fieldbus Configurator and a serial connection (in the Windows operating system). Upgrade notes 1-3 1.24.8 Adjustments for the InaDriver As of APROL R 3.4-06, the InaDriver delivers information from the CPU services about the state of a controller's CPU, which can be visualized with the system and self diagnostics. Furthermore, the InaDriver's status variables were extended as of APROL R 3.4-06. Additionally to the existing status variables, all of the status variables that were present up to now are also available in APROL R 3.4-06 with a changed nomenclature. Example: Old nomenclature: 'DRIVER_ The original InaDriver's status variables will no longer be available in a future APROL R 3.6. An adjustment to the new nomenclature can already be made in the context of APROL R 3.4- 06 when these "old" status variables are being used in existing CAE projects. Details can be found in the APROL documentation"F1 Drivers for B&R Connections", chapter Status variables of the InaDriver. 1.24.9 New menu navigation in the APROL installation As of APROL R 3.4-06, in the scope of the APROL installation, you have the possibility of choosing between a full installation and a custom installation. Furthermore, you have the possibility to carry out an installation in "AUTO mode" or via "manual package choice". The "AUTO mode" allows an installation without any further user interaction. Individual software packages can be excluded from, or added to the installation via "selective package choice". You do not change the selection of the computer type by adding or removing individual packages! For example, it is thus possible to exclude driver packages that are not used from the pre- selection. Details can be found in the APROL documentation "A2 Getting Started", chapter APROL installation and update. A3 Upgrade Notes 1-4 1.25 New features after updating to APROL R 3.4-05 Amongst various corrections, the following additions are contained in APROL R 3.4-05: 1.25.1 Actualized controller AR version The new AR version Q0295 has been made available in the scope of APROL R 3.4-05. The default AR version is still the version N0295, so that a controller AR upgrade is not necessary from an APROL R 3.4-04 project state. 1.25.2 Special procedure when installing the AutoYast DVD An updated AutoYaST DVD (version 3.4-06) is delivered with APROL R 3.4-05. Special procedures are necessary for the installation of the new AutoYast DVD due to a restructuring of the OpenOffice packets. The following steps are to be carried out only once during the installation of the current AutoYast DVD (version 3.4-06): No other medium or network drive is allowed to be mounted during the installation of the AutoYast DVD. Step Description 1 Insert the AutoYaST DVD into the DVD drive. 2 Open the "SUSE menu / System / Administrator Settings (YaST)" menu item in the KDE menu. The YaST Control Center is started after subsequently entering the password from the Linux super user "root". 2a Eventually, you must add, and activate, the DVD drive with "Installation source". If there is already an entry for the DVD drive it may be necessary to refresh the data that has already been read. For this purpose, press the [Edit] button and confirm the then following dialog with [OK]. Thereafter, the warning message "Validation check failed" appears. Confirm the question "Use anyway", and thus the warning message with [Yes]. Note: In the scope of the validity check, the check sum of the internal SUSE file content is compared to the B&R modified content file. Because the content file has been modified by B&R for the composition of the AutoYaST DVD, a warning message is shown that can be ignored. Use the [Finish] button to return back the YaST control center. 3 The update is started by selecting "Software Management" menu item in the Upgrade notes 1-1 Step Description YaST Control Center. During the first installation of AutoYaST, the software license agreement for SLES 10 should be acknowledged and approved with the respective radio button in the "License agreement" dialog that follows thereafter. Confirm the selection by clicking on [Continue]. 4 Go to the "Package/All packages" menu and select "Update if newer version available". The number of packages that are to be updated are shown in a separate dialog. Confirm this dialog box with [Continue]. 5 Choose the "Patterns" entry in the "Filter" drop-down list and then select the "Base Technologies / APROL base system" pattern. 6 The packages are sorted according to the criteria "alphabetic / non-installed packages" by double-clicking the top left column heading in the right window. 7 All of the packages that have not already been selected are to be selected with the context menu ("Install" menu item). Scroll down the packet view and additionally mark the "libtheora" package to be actualized ("Actualize" via context menu item). The "libtheora" package has a "yellow lock" symbol and red letters. A3 Upgrade Notes 1-2 Step Description 8 Then press the [Check] button. 9 Then, in the following "Dependencies conflict" warning, the "Delete OpenOffice_org-*" radio button must be activated in each "Conflict solution" section. The "Delete aprolbase" radio button must also be chosen in the "aprolbase" section. Subsequently press the [OK - Check again] button. 10 The "APROL AutoYaST" entry is to be selected and confirmed with [OK - Check again] in the newly opened "Dependencies conflict" warning. Information is given about the solution of all package dependencies with a subsequent dialog. 11 Choose the "Search" entry in the "Filter" combo-box and enter the term "OpenOffice". Start the search procedure with the [Search] button. Upgrade notes 1-3 Step Description 12 3 OpenOffice packages, which have a "blue tick", are contained in the package list. The packages are marked for deletion with a "trash" icon by clicking on the three "ticks". Confirm the operation with the [Accept] button. 13 The installation of the packages takes place after the following "Changed packages" dialog is confirmed with [Continue]. 14 Close YaST after the installation of the packages. A3 Upgrade Notes 1-4 1.26 New features after updating to APROL R 3.4-04 Amongst various corrections, the following additions are contained in APROL R 3.4-04: 1.26.1 Actualized controller AR version The actualized AR version P0295 is supplied within the scope of APROL R 3.4-04. The default AR version is still the version N0295, so that a controller AR upgrade is not necessary for an existing APROL R 3.4-03. 1.26.2 Web based licensing procedure As of APROL R 3.4-04, the known licensing via dongle is replaced with the web based licensing procedure. Before a "build all", all of the project parts of the type "APROL system" and "Control computer (R 3.2 mode)" that exist in the project must be deactivated once and subsequently activated again due to the provision of new system variables for the web based licensing procedure, and the possibility to configure several operator systems on one control computer, after updating to APROL R 3.4-04. A reactivation of the project parts is not allowed to take place! Subsequently, the "Build all" that is necessary after an update can be carried out. If the system and self-monitoring is configured with a custom-made logic then the old system variables must be swapped and the logic adjusted before the "Build all". This step is not necessary when using the "SysMon" library! Details about the web based licensing procedure can be found in the APROL documentation "A2 Getting Started", chapter System licensing. All of the APROL computers should be licensed with the new web based procedure after a successful update. As long as no licensing has taken place after the installation of the APROL system software, the APROL computer is in "Evaluation mode" (corresponding to the previous "Demo mode"). The evaluation period is 90 days, of which you are made aware of in regular intervals (every 60 minutes). The web based licensing procedure offers you the following advantages: no additional hardware necessary, no dongle swap necessary for an APROL release change Upgrade notes 1-1 B&R delivers a unique serial number for each APROL license. The 11 digit B&R serial numbers allocated to the product are noted on the supplied license certificate and are managed by B&R together with the respective delivery date in a central license database. All of the APROL releases, which have been made public up to a maximum of 18 months after the delivery date of your release, can be presently licensed with this serial number. An internal check takes place between the delivery and release date each time that the APROL system is started. There are the following licensing possibilities: Automatic licensing (online): An internet connection is established to the database after entering the B&R serial number. The requirement for an automatic licensing is that there is an internet connection on the computer with the APROL release that is to be licensed. Manual licensing (offline): A system code is output on the APROL computer after entering the B&R serial number. This code must be subsequently input on the B&R homepage "www.br- automation.com" ("Service / Software registration" menu item, "Continue manual registration" link) via a computer with an internet connection. The activation code that is generated there must be subsequently entered in the APROL license dialog. The dialog on the APROL computer is not allowed to be closed in the meantime, because a new system code is generated when it is opened again. 1.26.3 Cancellation of "control computer (R 3.2 mode)" project part The extended "Control computer" and "APROL system" project parts are available since APROL R 3.4-03. The following benefits are available to you since then: These project parts are now separately configured due to a complete distinction between "Control computer" and "APROL system", and can now be flexibly allocated to each other. A simple relocation of a system to another hardware (control computer), and the relevant change between referenced project parts is possible without the loss of configuration data. APROL A pre-configuration of hardware is also possible without an system. As of the future APROL R 3.6, the old "Control computer (R 3.2 mode)" project part is no longer supported. A3 Upgrade Notes 1-2 The conversion to the new "APROL system" and "Control computer" project parts should be carried out now in order to guarantee an future upgrade to APROL R 3.6. Please ensure that all of the cancelled "Control computer (R 3.2 mode)" project parts are deleted both in the logical view and the trash can before you carry out an upgrade to a future APROL release. Otherwise an upgrade is suppressed. 1.26.4 Use of the AS 3.0 code generation in the future APROL R 3.6 In the future APROL R3.6, the "Stricter plausibility control for AS 3.0 code generation" will be activated per default for all CAE libraries and projects. The stricter plausibility check can be configured via the CAE project's and the CAE linrary's properties("Engineering options" tab). Furthermore, the AS 3.0 code generation will be activated per default for all controllers (not controller (R 3.2 mode)) in the future APROL R 3.6. It is possible to switch to the AS 2.x code generation in special circumstances. In the context of APROL R 3.4-04 and in preparation of the future APROL R 3.6, it is already possible to change to the AS 3.0 code generation without any problem. 1. Change the old "Controller (R 3.2 mode)" project parts in APROL R 3.4-04 with the new "Controller" project part. 2. Already activate the "Stricter plausibility control for AS 3.0 code generation" in the properties of the CAE project, as well as the CAE libraries ("Engineering options" tab). 1.26.5 Importing CAE blocks As of APROL R 3.4-02, a comfortable import and export functionality for all project parts in the context of the CAE libraries is supported. You thus have the possibility to export individual library blocks, block groups, or complete CAE libraries in the format of the CAE database, and import these in another CAE library - e.g. in another engineering environment. As of APROL R 3.4-04, it is also possible to import into a CAE library with a different name. If the import file contains several libraries, one of the desired libraries can be chosen via choice dialog, so that the block import can continue. If a CAE library with the same name is in the file it is pre-selected due to security reasons. When importing hyper macros, the dependencies of the blocks being used are taken into account so that these blocks, which are necessary for running the hyper macro, are automatically imported together. Upgrade notes 1-3 Illustration 48: Import of blocks from CAE libraries with different names 1.26.6 Improved system monitoring If several APROL systems, which serve as a target system for the same CAE project, are configured on one control computer then a multiple writing of the system variables from several SysInfo processes is suppressed as of APROL R 3.4-04. One SysInfo process adopts the process control and writes the system variables. 1.26.7 Additional saving of the TrendViewer configuration as generated project state As of APROL R 3.4-04, the TrendViewer additionally saves configurations and layout in the directory for the generated project state. With this, there is the possibility to directly transfer the changes made in the TrendViewer configurations and layouts to the runtime system via download - without the necessary build process. When opening the TrendViewer in the engineering environment, the configuration and layout are saved, additionally to the normal storage location /home/ /home/[Engineering system]/ENGIN/PROJECTS/ A3 Upgrade Notes 1-4 With this, the GENERATED/ If the GENERATED directory does not exist, i.e. a "Build all" has not been carried out, an error message is output in the CaeManager that makes you aware of the necessary build process. 1.26.8 Quicker activation of several connectors The multiple activation of connectors in APROL R 3.4-04 completes the comfortable and quick editing of connectors in the I/O choice dialog. Connectors with the "Current" status can be selected in the I/O choice dialog and activated at the same time with the "Activate connectors" menu item. Illustration 49: Multiple activation of connectors Upgrade notes 1-5 1.27 New features after updating to APROL R 3.4-03 Amongst various corrections, the following additions are contained in APROL R 3.4-03: 1.27.1 Actualized controller AR version The actualized AR version N0295 (default AR) is supplied within the scope of APROL R 3.4- 03. The following steps must be carried out when updating to the actualized AR versions: It is necessary to open the controller in the CaeManager, and to start the hardware configuration via AS. The AR exchange can be carried out in the context of Automation Studio (via "Project / Change Runtime Version" menu item). The controller in the CaeManager is to be re-saved and compiled after having been saved and successfully rebuilt in Automation Studio. Please note that an AR change on the controller leads to a cold restart, and can therefore only be carried out during a system standstill. 1.27.2 Simplified configuration of the control computer task The self-ID has been dropped during the control computer task configuration. Because the task name must be unique within a project, the CC task configuration could be simplified to that effect. The syntax of the control computer task's system variables has also been simplified with regard to this. Apart from the self-ID being dropped, the prefix up to now has been changed from "Pcc_" to "CCT_". A mixed operation of the old (Pcc_ Furthermore, additional system variables have been made available for cycle time evaluation. The cycle times and the guaranteed remaining time must be configured in the dialog for task configuration in the APROL system. As of APROL R 3.4-03, the control computer task in the Linux process list is listed without the self-ID entry and with a changed 'CCT_ Please note that, due to the simplified CC task configuration, the following described steps must definitely be carried out in the engineering and runtime systems: ToDo - Engineering system: In existing projects, it is necessary to control the CC task configuration once in the project parts 'APROL system' and 'Control computer (R 3.2 mode)', and to save these once again. After the creation of a new version, the project parts are to be activated and compiled. Upgrade notes 1-1 The system variables for monitoring the CC task that have been placed on a CFC's input border are to be exchanged for the system variables with the new syntax. Old: " ToDo - Runtime system: Both the master and the slave must be shut down before a download can take place in a redundancy system. It must be ensured that the state of the APROL software on both redundancy partners is the same. Additionally, no CC task process is allowed to be started on any server before a download takes place. 1.27.3 Change of the validator for host names As of APROL R 3.4-03, an APROL validator ensures that the configuration of host names can only be made in small letters. A unique addressing of the computer name is guaranteed with this. ToDo: Host names that have been in capital letters up to now must be changed in existing CAE projects and adjusted to the changed validator. Furthermore, the computer configuration via YaST must be checked and adjusted if necessary to the consistent form of writing in small letters. The host names for existing runtime and operator systems that are in the global.conf file in the /home/aprolsys/APROL/cnf/global/ directory must also be checked and changed if necessary. The computer name must be adjusted in all .rhosts files (directory /home/ A3 Upgrade Notes 1-2 1.27.4 Stricter plausibility control for AS 3.0 code generation As of R 3.4, APROL already supports a stricter plausibility control of the identifiers that you have used up to now, in preparation for future support of the AS 3.0 code generation. You are explicitly made aware of necessary changes to faulty identifiers with error messages during a 'Build', or when compiling. The stricter plausibility check can be configured via the CAE project's and the CAE linrary's properties("Engineering options" tab). As some identifiers (e.g. pin names) are excluded for the future use of the AS 3.0 code generation, this plausibility control is activated by default when creating a new CAE project, whereby identifiers are marked as invalid by APROL validators during their input or during the compilation. Therefore in the context of APROL R 3.4-03, you should activate this plausibility check for existing CAE libraries and projects. ToDo: If you use the intensified plausibility check and are made aware of faulty identifiers (pin names) in the scope of a Build, the following steps are necessary: - Adjustment of the affected block with respect to the identifiers that have been criticized, - Execution of an error-free 'Build' of the CAE library, - Check and eventual adjustment of the operator rights on block pins, - Adjustment of constants in blocks, hyper macros, and CFCs, which are not automatically created by substitution (e.g. with @HWINST@), - Execution of a 'Build all (project)' to newly order the controller's global memory (controller address database) (Attention: the "Allow changes in structure definition" checkbox must be activated!) - Check and eventual adjustment of the trend system's configurations. the "Allow changes in structure definition" checkbox must be activated!) - Check and eventual adjustment of the trend system's configurations. An overview of the necessary adjustments that must be made when changing identifiers that have been critisized can be found in the APROL documentation "B3 CAE Library Engineering", chapter Necessary adjustments after changing the pin name. Illustration 50: Activation of the intensified plausibility control Upgrade notes 1-3 1.27.5 Dynamic configurability of the AprCcTrend block's MIN and MAX pins As of APROL R 3.4-03, the MIN and MAX inputs of the AprCcTrend block can be configured dynamically. As of APROL R 3.4-03 the actual values of the connected variables are used in the trend configuration. If the MIN and MAX inputs are being written to from variables in existing projects, or customer libraries, then these configurations must be checked and eventually adjusted. 1.27.6 Additional plausibility checks in the parameter management When configuring equipment parts and parameter set templates, the validators in APROL R 3.4-03 for checking the configured parameter values, as well as the minimum and maximum limits, have been optimized. An accidental definition of parameters without an actual parameter value is visually marked. Simultaneously, saving incomplete data as well as activating incomplete data records is suppressed due to security reasons. The plausibility check for checking the configured minimum and maximum limits can be project- globally deactivated via the project properties (Engineering options and Runtime options tab), in so far as this is especially necessary for start-up purposes. You can thereby stipulate separately for the engineering and runtime system if the parameter value's defined limits should be taken into account within the scope of the plausibility check. The plausibility check should basically be left in an activated state! 1.27.7 Changed identifiers for process variables on the controller For the usage of the AS 3.0 code generation, the identifiers for process variables (which stipulate the scope of application of the process variables on the controller) used in the C code have been changed as follows: Identifier (old) Identifier (new) _LOCAL _LOCAL_VOLATILE _REMANENT _LOCAL_REMANENT _ACTUAL _GLOBAL_VOLATILE _GLOBAL _GLOBAL_REMANENT If these identifiers are being used in existing projects (e.g. in scripts) then these applications must be adjusted to the new identifiers. 1.27.8 Simplified handling of images As of APROL R 3.4-03, the images that are to be embedded in the graphic in the DisplayEditor can be comfortably chosen from the project or library local image container. A3 Upgrade Notes 1-4 The container can be opened and filled in the properties of the CAE library and project, in the context of the DisplayEditor, or when allocating the image via pin type choice. Details can be found in the APROL documentation "B3 CAE Library Engineering", chapter Simplified handling of images in image containers. In existing CAE projects, the images can be comfortably and directly dragged & dropped from the file system (Konqueror's image view) into the container - and vice versa. It is not mandatory to switch to the new form of data storage, i.e. the linking of images from the file system is still supported due to compatibility reasons, although it is not recommended. 1.27.9 Special features when using the visualization elements "InputOutputBox" and "Slider" A valid value range for user inputs can be specified for these visualization elements with the configuration "Value range beginning" and "Value range end". In case the input (control value) is configured as a "local PV", the following must be noted with respect to that: If the input limits of a control value variable with "local PV" (Python variable) should take effect, then this control value variable must be initialized in the Python code at the first possible place, i.e. in the main level, and before each further agreement (e.g. hanging of hooks). block.local. As Python variables are type-free, it is only possible to detect the thought data type with an initialization during the start-up of the block, and the desired value range monitoring from the visualization element (widget) is activated. 1.27.10 Functionally typified block pins Through the functional typecasting of certain block pins it is possible to perform a semantic check of the value present on the pin. As of APROL R 3.4-03, apart from its syntax, the meaning of the data is checked in certain cases within the scope of the plausibility check. Because of this typecasting, it is possible to stipulate a selective choice of discrete data or values on the block. Upgrade notes 1-5 Illustration 51: Functionally typified block pins When creating your own CAE blocks, the pre-defined pin types can be allocated to the block pin, or hyper macro pin. The IEC type, as well as all further attributes automatically result from the allocated pin type. 1.27.11 New configurations editor for control computer and APROL system As of APROL R 3.4-03, there are two new configuration editors available for the Control Computer and APROL system project parts. A complete division between control computer and APROL system has been achieved with the introduction of the new control computer and APROL system project parts, and the replacement of the old control computer (R 3.2 mode). These are now separately configured and flexibly allocated to each other. The discontinued "Control computer (R 3.2 mode)" project part must be changed to the new project part in existing CAE projects. An allocation of several APROL systems to one control computer will be possible in the future, as well as vice versa, allocating several control computers to one APROL system. Changes to identically configured systems now only have to be made in one place. The same applies to control computers that have several systems allocated to themselves: Multiple configurations are no longer necessary. Details can be found in the APROL documentation "B2 Project Engineering", chapter Control computer and APROL system. 1.27.12 Optimized CC module options for the DisplayCenter The DisplayCenter launching options have been optimized: Affected options are: -filterLockedAlarms -setTDisplayDecPos This "-setTDisplayDecPos" option only has an affect on the discontinued "Input" visualization element (widget)! This option has been cancelled, and will no longer be supported. A3 Upgrade Notes 1-6 1.27.13 Simplification when using the VM for the AS configuration The VMware is delivered with a preinstalled Windows XP Professional operating system. This must be licensed and activated with the delivered customer product key, only one time upon using it for the first time. Automation Studio and the B&R SafeDESIGNER are automatically installed when using the hardware configuration for the first time via the controller editor. An actualized version of Automation Studio is provided in the scope of APROL R 3.4-03. Thus, a new installation, or upgrade, of the Automation Studio system software is necessary. ToDo: Subsequently, the one time licensing of Automation Studio (or the B&R SafeDESIGNER) is to be carried out with the delivered serial numbers. when starting the hardware configuration for the first time after an AS upgrade, it is absolutely necessary to save the Automation Studio project for each controller, and to generate it, without carrying out any changes in the AS project. Subsequently, the AS configuration is to be adopted in the APROL system environment. Details can be found in the APROL documentation "E1 Controller & I/O", chapter Licensing VMware / Windows / Automation Studio. 1.27.14 Special features when installing the APROL system software Integrity check of the installation medium: The APROL System Software DVD contains the individual system software packages in RMP format. An MD5 checksum is additionally stored on the installation medium for each RPM, and is checked within the scope of the installation. After choosing the installation mode "Automatic / manual installation", the integrity check must be started with a separate dialog. Illustration 52: RPM packet integrity check The integrity check should be carried out at any rate. Special features of the VMware EULA: Please note during the Automatic installation (as well as the Manual installation) that it is additionally necessary to manually confirm the "VMware EULA" when the VMware version 6.5.0 has not been installed up to then. Upgrade notes 1-7 1.27.15 Discontinuation of the AprUcSMS block The functionality of the "AprUcSMS" block (of the APROL CAE library) can no longer be supported as the GSM services of the telecommunication providers are no longer available. Thus, this CAE block has been discontinued as of APROL R 3.4-03, and will no longer be available in future APROL releases. A3 Upgrade Notes 1-8 1.28 New features after updating to APROL R 3.4-02 Amongst various corrections, the following additions are contained in APROL R 3.4-02: Controller OS versions: The OS version D0295 (default OS) is supplied within the scope of APROL R 3.4-02. Transfer of the time stamp from the controller to the control computer in UTC: The EventDriver and the dcsEventDriver have been adapted for the use of UTC (Universal Time Coordinated) on the controller. Now UTC is used instead of LocalTime when transferring time stamps from the controller to the control computer with this driver. This is to be noted when using the affected time stamp in a project. KDE configuration: In the scope of APROL R 3.4-02, the B&R pre-defined KDE configurations for the operator system have been condensed and further optimized. After upgrading or updating the APROL system software to APROL R 3.4-02, the existing KDE configurations must be explicitly replaced by the new KDE configurations. Choose "Properties" in the context menu for the operator system in the DownloadManager in order to do this. Activate the "Reset KDE menu configuration with the next download" checkbox, and confirm the procedure with [OK]. After a successful download, the current KDE configurations are available on the operator system that has been chosen. Automatic insertion of the ApDrvCross driver As of APROL R 3.4-02, in order to securely design and simplify a controller's configuration, the ApDrvCross cross-communication driver is automatically inserted when creating a new controller. In the scope of the configuration, the cross-communication must merely be configured within the controller-controller connection. In order that the ApDrvCross driver is automatically added to all of the existing configured controllers after updating the APROL system software, it is necessary to open the controllers in the CPU view once, and to subsequently to save them. After a subsequent build of the configuration, all of the necessary dependencies have been met for a download. Upgrade notes 1-1 1.29 New features after updating to APROL R 3.4-01 Amongst various corrections, the following additions are contained in APROL R 3.4-01: The actualized OS version D0295 (default OS) is supplied within the scope of APROL R 3.4-01. The "SysMon" library for system and self diagnosis has been furthermore completed in build R 3.4-01. Upgrade notes 1-1 1.30 Important notes for upgrading to APROL R 3.4 Accompanying the upgrade to APROL R 3.4, an operating system change to SUSE Linux Enterprise Server 10 (SLES 10) is necessary. Carry out an extensive backup before the installation of APROL R 3.4. The hard disk is formatted in the process of installing the new operating system. It is necessary to convert all controllers to the new OS AR-I/O! The actualized OS version C0295 (default OS) is supplied within the scope of APROL R 3.4. All controllers are to be opened and switched to the current OS version. Please note that when changing from an OS version smaller than AR 0280 (FlexIQ) to the current OS version, all of the Powerlink racks must be saved once, so that the automatic conversion to the new I/O system takes place. When creating a new controller, the default values of the Sysconf are to be checked with regard to the system's requirements, and adjusted if necessary. These settings are also to be checked, and adjusted if necessary, during the migration of a "Controller R 3.2 mode" to the new "Controller" project part. 1.30.1 Selective remanence as an attribute of block pins In APROL R 3.4, the block-global remanence has been replaced by a selective remanence of the output pins as well as the local variables. If default values have already been configured for local variables in remanent blocks in existing projects, then the remanence of these variables is deactivated in favor of the default values when the CAE project is upgraded. In order to obtain a more effective usage of the remanent memory area, especially on the controller, all of the blocks should be checked with regard to their remanence, and an unnecessary remanence of block pins or local variables should be turned off. In the course of that, a renaming took place for the If the remanent data from an existing project should be adopted in the actual APROL release, then both of the files (in the /home/runtime system/RUNTIME/ directory) must be changed to the new nomenclature before the first start and download. 1.30.2 Replacement of the TrendData application The TrendData application as basis for the web based TrendReports is replaced with the TrendViewer in APROL R 3.4. A3 Upgrade Notes 1-2 When the TrendData is currently being used in existing projects (e.g. in UCB scripts), these TrendData calls are to be replaced with equivalent ChronoLog calls. Details concerning the calls can be found in chapter TrendData alternative solutions in the appendix of manual "A2 Getting Started". 1.30.3 Replacement of the "SYSTEM", "SYSTEM_RIO", and "SysMon_2005" libraries Please check your system and self diagnosis, and adapt them to the extended functionalities in the new "SysMon" library if necessary! The B&R libraries "SYSTEM" and "SYSTEM_RIO" are discontinued in APROL R 3.4. The "SysMon2005" CAE library has been automatically replaced with the new "SysMon" CAE library. If blocks from the "SYSTEM" or "SYSTEM_RIO" libraries are in use then these are set to "obsolete", and the respective library obtains the "Customer" status. All of the blocks that are not in use are deleted. If no block of these CAE libraries is used in existing projects, the corresponding CAE library is deleted. The "SysFuAlaString01" block from the "SYSTEM" library is automatically exchanged with the "AprFbPrintf04" block from the "APROL" library. It is at any rate recommended that blocks that have been used from the "SYSTEM" library are to be exchanged with substitute types with the same function from the new "SysMon" library. A listing of the automatically exchanged blocks can be found in chapter Substitute blocks for CAE libraries SYSTEM and SysMon2005 in the appendix of manual "A2 Getting Started". 1.30.4 Changed data storage for all I/Os A substantially reduced memory load when operating the CaeManager and a much better performance has been achieved in APROL R 3.4, due to a new structure in the data storage for all I/Os, as well as system internal optimization. With extensive plausibility checks, one is made aware of possible inconsistencies in very detailed CAE messages. 1.30.5 Checking of rights allocated to users and operators The rights management for the engineering system has been replaced by the new user management. The user "Startup" (Password: admin) serves for the primary configuration of the engineering system after the installation of the APROL system software, and is created in addition to the user "root" (original password: .root). The user "root" can now be deleted in the context of APROL R 3.4. Existing "Designer configurations" are adopted as "User configurations". Existing "Profiles" in the OperatorManager are adopted as "Groups". Upgrade notes 1-3 Newly added rights receive the "tri-state" status in the user management as well as in the OperatorManager, and are handled as set. If at least one user, or template, has the "Tristate" status because of the upgrade then the user management is automatically started when the CaeManager is started. The configured rights are to be properly checked after an upgrade to APROL R 3.4, and eventually modified. Especially the rights with "tri-state" are to be observed, and the desired settings are to be made here. APROL A detailed description about the user management can be found in the documentation "B1 Engineering Environment", chapter User management. 1.30.6 New IEC data type LSTRING APROL supports the use of strings that are longer than 64 bytes, by providing the additional IEC type LSTRING. This new IEC type can solely be used for logic on the control computer. In existing CAE libraries, the input pins of graphic blocks and UCB blocks that have used the IEC type STRING up to now, are automatically converted to the LSTRING. The connection of block pins of the IEC type "STRING" has been drastically simplified due to the implicit IEC type conversion (STRING --> LSTRING). Custom made UCB blocks must be checked with respect to the processing of extremely long character strings. 1.30.7 Simplified CFC creation In order to reduce the complexity in project engineering, as well as the simplification of the debugging, CFCs can now be created in a simplified manner. When creating simplified CFCs you can order either . exactly one controller task and eventually a control computer task,or - exactly one control computer task When creating a new CFC the "Simplified CFC creation for controller task with optional control computer task part" setting is activated. This setting can be changed when creating a new CFC. For the purpose of an increased efficiency these modifications together with the task allocation that has been made are adopted for all further CFCs that are created until the CaeManager is terminated. The default settings are re-done only when the CaeManager is restarted. The already known behavior is possible by choosing the "Complex CFC creation with multiple task allocation" option. A choice can be made, toggling between the target systems controller and control computer, for the processing of functions and function blocks with the block properties. A3 Upgrade Notes 1-4 1.30.8 KDE configurations Available for the runtime system and operator stations are the KDE configurations "Basic", as well as "Standard", which corresponds to the functionality of the cancelled "BurProfessional" configuration. The choice of the KDE configuration is solely carried out via AprolConfig. The configuration chosen with AprolConfig is loaded when logging into an operator or runtime system. The creation of custom KDE configurations is no longer supported. When creating a new operator or runtime system, a choice can be made between the "Basic" and "Standard" KDE configurations. The new allocation of a KDE configuration ("Basic" or "Standard") is possible via AprolConfig - changestartupkde, and takes effect with a new login into the APROL system. The changes made with AprolConfig -changestartupkde take effect for this system after logging out and subsequently logging back into the APROL system. Please note that all local and remote computer access to the APROL system must be terminated so that the new configuration can take effect. If local changes have been made to the KDE configuration, the chosen settings (via AprolConfig) can be restored with the DownloadManager. For this purpose choose the "Properties" menu item in the shortcut menu, and activate the "Reset the KDE configuration for the next download" checkbox. The checkbox is automatically deactivated after a successful download. 1.30.9 SNTP configuration via the controller's OS As of APROL R 3.4, the SNTP time synchronization is a part of the basic functionality of the controller operating system. Thus, the no longer needed ApDrvNTP, ApCnfNTP and timezone modules have been dropped. In existing projects, the ApDrvNTP module must be removed from the controller's module list. Furthermore, the configuration of the SNTP server is to be carried out in the controller's Sysconf. The broadcast address is automatically detected by the operating system as of APROL R 3.4. In this context, the "Broadcast address" entry in the "Ethernet settings" dialog has been dropped. The modules ApDrvNTP, ApCnfNTP, and timezone are to be removed from the controller. Furthermore, the SNTP configuration is to be carried out in the "Ethernet settings" dialog of the controller, in the SNTP settings tab. 1.30.10 Simplification of the control computer configuration A simplified and comfortable configuration of the CC modules is possible within the scope of the control computer configuration. The control computer configuration is to be checked and newly saved. Upgrade notes 1-5 1.30.11 Checking the visualization The "UnixCommand" control that was discontinued as of APROL R 3.0, as well as the "LEDButton" widget, and "Switch" have been dropped in release 3.4. When in use, the "UnixCommand" control is to be replaced with the corresponding Python code solution, and the "LEDButton" and "Switch" widgets with the new interactive graphic elements in APROL R 3.4. 1.30.12 Extended project properties The engineering options in APROL R 3.4 have been extended in the "Project properties" dialog in order increase the efficiency during project engineering. After a successful upgrade to release 3.4, this dialog is automatically opened when a project is opened in the CaeManager. The engineering options in the "Project properties" dialog are to be checked, eventually modified and confirmed, after an upgrade to APROL R 3.4. 1.30.13 Name change of system variables Due to changes in instance handling, the names (i.e. the syntax) of system variables for control computers have changed. In existing projects using system variables in blocks for the creation of global variables, the nomenclature of the system variables must be manually adjusted to the new nomenclature, as an automatic system tracing is not possible. 1.30.14 Activation of the control computer before the upgrade to APROL R 3.4 Before the upgrade to APROL R 3.4, all control computers must be activated so that the allocated system variables are not converted into template variables. With a conversion to template variables, the allocation of the variables used in the CFC with the respective control computer is lost. 1.30.15 Replacement of the ApEx450Gw.br module The ApEx450Gw.br module is no longer supported as of APROL R 3.4, and is replaced by the ApDrvEthDp.br module. The ApDrvEthDp.br module serves for the analysis of a DP network with Windows based applications via TCP/IP. The old ApEx450Gw.br module must be removed from the CPU's module list, if it is present in existing projects. Subsequently, the ApDrvEthDp.br module must be configured in the gateway editor. A3 Upgrade Notes 1-6 Upgrade notes 1-7 1.31 New features after updating to APROL R 3.2-04 Apart from various corrections, the following enhancement has been made in the current APROL R 3.2-04. APROL Further information about the new functionalities in R 3.2-04 can be found in the APROL documentation "A1 Release Notes". 1.31.1 Exchange of CPUs in the project part "controller" The controllers from the Motorola platform (SG3 targets) will no longer be supported as of the projected APROL R 3.4! In preparation of the cancellation of the SG3 targets it is possible to quickly and comfortably exchange Motorola CPUs that have been placed in existing projects with an additional dialog in the context of APROL R 3.2-04. CPUs can now be exchanged, whilst retaining most of the relevant information, in the controller project part via the "Exchange CPU" shortcut menu for a controller's CPU. Only available SG4 targets are offered in a choice dialog, which can be placed directly due to the width. Subsequently, at least the following settings must be checked, and modified if necessary in the "CPU properties" dialog: the version of the controller's operating system all of the system configuration's (sysconf) settings, especially the Ethernet and interfaces for the project and APROL connections Removal of data or operating system modules that are no longer needed Adding necessary data or operating system modules Settings of the task classes Allocation of the individual tasks to the task classes The "CPU properties" dialog is automatically opened for this purpose! It is absolutely necessary to recompile all of this hardware's plans and tasks! If the space is not available for a CPU with a greater width, it is necessary to move modules that have already been placed to the backplane module. The exchange is not reversible, meaning that it is not possible to re-place a Motorola CPU! A3 Upgrade Notes 1-8 1.32 New features after updating to APROL R 3.2-03 APROL Further information about the new functionalities in R 3.2-03 can be found in the APROL documentation "A1 Release Notes". Apart from various corrections, the following new updates and changes are covered in APROL R 3.2-03. 1.32.1 Actualized controller OS version In the scope of APROL R 3.2-03, the actualized OS versions U0290 (default OS) and V0292 are supplied for the SG4 targets (AR-I/O). 1.32.2 Sysconf switch for increased performance and reduced memory requirements As of the OS version U0290 there is a separate switch available in the system configuration (sysconf) to increase performance when downloading a task, and to reduce the memory requirements of the controller. The switch is automatically set as of APROL release R 3.2-03 for U0290 OS versions and higher. The switch is activated per default when creating a new controller, or when changing an OS to a version greater than, or the same as, U0290. If the OS version U0290 has already been used on controllers in existing projects, then the following manual adjustments are necessary after an update of the APROL system software: Call up the sysconf (via the "Properties"shortcut menu of the CPU) Choose the "OTHER" tab Please choose the "Other" entry, and insert a new node with the description "OPTIONS" (via "Add node" shortcut menu). Please note the correct syntax! Create a new data entry (via "Add data" shortcut menu) in the "OPTIONS" node that you have created. The data entry that you have created must have the name "LNDisableGlobalRefCnt", as well as the type "ui4", and the value "1". Please save the system configuration (sysconf), and subsequently generate the hardware. Upgrade notes 1-1 Illustration 53: New switch "LNDisableGlobalRefCnt" in the system configuration 1.32.3 Changed mechanism for the creation of backup files As of APROL R 3.2-01, the data archives ( If older CaeBackup files should be restored after an update to APROL R 3.2-03, then the data archive and check file must be packed into a TAR file (without compression) with the name Please note the detailed information, including the examples, about creating and extracting TAR files in manual "A2 Getting Started", chapter TAR archives with MD5 check sum. 1.32.4 Actualized firmware version for DP master card APROL supports the use of the DP master cards EX450-66.2 and 3IF766.9. As of APROL R 3.2-03, the actualized firmware version V1.208 is recommended for the EX450-66.2 card. A list of the recognized DP master cards, as well as their firmware is entered into the system logbook from the APROL ApDrvDp driver. The logbook can be shown with the help of the ControllerManager. As long as the DP master card uses an older firmware version as the recommended version, this is explicitly entered into the system logbook. A3 Upgrade Notes 1-2 The hardware is also started with an outdated firmware version. Even so, a correct operation is not ensured. The current firmware files are in the directory /opt/aprol/BR_ARs/Firmware/EX450/. Please note that a firmware update is solely to be carried out with the B&R Fieldbus Configurator (in the Windows operating system). 1.32.5 Updated B&R hardware catalogue for the controller configuration In order to support the new B&R controller functions, the actual hardware catalogue has been incorporated into APROL R 3.2-03. With this, for example, the extended output format configuration is available for the temperature module 3AT660.6. So that the current configuration is compared with the new hardware catalogue, the configuration must be checked and newly saved in certain special modules. It must be observed, due to the configuration change, that a warm start must be carried out on the respective controllers. The configuration must be checked and saved for the following modules: Series 2005: 3AT660.6 Series 2003: 7AI261.7, 7AI294.7, 7AI354.70, 7AI774.70, 7AM351.70, 7AT324.7, 7AT351.7, 7AT352.70, 7AT664.70, 7DI435.7, 7DI439.72, 7DI439.7, 7DI645.7, 7DM435.7, 7DM436.72, 7DM465.7, 7DO720.7, 7DO721.7, 7DO722.7, 7MM424.70-1 Upgrade notes 1-3 1.33 New features after updating to APROL R 3.2-02 APROL Further information about the new functionalities in R 3.2-02 can be found in the APROL documentation "A1 Release Notes". Apart from a further increase in performance and various corrections, the following updates and changes are contained in APROL R 3.2-02. 1.33.1 AR-I/O operating system S0290 as new default OS version for SG4 targets When creating a controller, the OS version S0290 (AR-I/O) is used as the default operating system. All existing controllers, which have been configured with the OS choice "Default operating system", are re-configured to the new OS version, after a query, when opening them for the first time. If use of the new I/O system is not desired, the OS version used up to now must be explicitly chosen during the query. Please note that the OS version S0290 solely supports the new I/O system (AR-I/O). Furthermore in the scope of APROL R 3.2-02, the actualized OS version A0274 (FlexIQ system) is made available. ToDo: When adopting the new "Default OS version", the I/O configurations must be adjusted with respect to the new I/O system. If the OS version used up to now (based on the old I/O system) should still be used, the controller must be explicitly set when it is opened for the first time. The new I/O system must now be chosen during the creation of a new controller. 1.33.2 Support for the IF766 as an additional DP master card As of APROL R 3.2-02, apart from the 3EX450-66.2, the B&R module 3IF766.9 is supported as a further DP master card. The ApDrvDp driver is necessary in the scope of a Profibus DP configuration, in order that the communication with the DP master cards is possible. Please note the changed behavior of the driver ApDrvDp as of APROL R 3.2-02. The driver now executes the orders from a DP master card per task cycle. If the refresh rate was 10 ms up to now, as of APROL R 3.2-02 the refresh take place according to Upgrade notes 1-1 1.33.3 Deactivation of the I/O shoveler in service mode When a system error occurs on the controller, or with an explicit setting in the ControllerManager, the controller is put into the service mode. If the controller is in service mode, the outputs should not be updated. As of the OS version S0290, the I/O shoveler can be explicitly deactivated in service mode via the system configuration (sysconf). The shoveling of I/Os can be suppressed with the "DisableMappingInService" attribute in the sysconf, found in the BOOTPROPERTIES tab. When the switch is set to the value "0", the outputs are re-supplied with the global PVs values. By setting the switch to the value "1", the refreshing is suppressed. With this, the outputs are set to the current actual process value. The shoveling of I/Os in service mode is deactivated per default as of APROL R 3.2-02. ToDo: The sysconf settings must be checked with respect to this after updating to APROL R 3.2-02. You must make sure that the "DisableMappingInService" attribute has been set to the value "1". Illustration 54: "DisableMappingService" attribute 1.33.4 Prevention of unnecessary write jobs for SG4 CPUs The "AprolTimeDelta" library's system internal process variable sharedMemId, which is available in each task, has been renamed to PCC_sharedMemId in the scope of APROL R 3.2-02. Due to the renaming of the PV - and the associated filter mechanism - it is prevented that the system internal PV is taken over by the InaDriver, and therefore can be written, or over-written. ToDo: As the process variables caught by the filtering now correspond to the nomenclature, it must be made sure that the necessary "PCC_* -" entry is contained in filter file that you may have modified. A3 Upgrade Notes 1-2 The user specific filter file is to be stored in the /home/ 1.33.5 Increased system stability via evaluation of the AprolLoader status Higher system stability is provided with APROL R 3.2-02. By evaluating the AprolLoader interface, a download is suppressed during the starting and stopping of an APROL system, and critical system states are thereby avoided. Also, you receive additional information in the StartManager and DownloadManager. The connection status, as well as the state of the AprolLoader there, is now displayed for all of the target systems. Due to the extensive expansions, the current communication protocol is no longer compatible with previous APROL releases / builds. From an APROL system where R 3.2-02 is installed, applications can no longer be started via the StartManager on systems with an older release / build, as no communication is possible. Examples: - Engineering system, APROL R 3.2-02 -->runtime system with R 3.2-01 or older - Runtime server, APROL R 3.2-02 -->redundancy partner with R 3.2-01 or older are not allowed. The same applies if the case is reversed. An APROL system with R 3.2-02 cannot be accessed via the StartManager on an APROL system with an older release / build of the system software. If an update has not been carried out on all of the systems, then instead start the respective application locally on the respective system with the StartManager. 1.33.6 Simplified configuration of the control computer task The two-staged procedure for the configuration of a control computer task has been replaced with a comfortable, clear, and intuitive configuration dialog in the scope of APROL R 3.2-02. All necessary configurations take place completely in one dialog, which can be accessed in the control computer's project part via the [control computer tasks] button. A subsequent configuration in the scope of the CC modules is no longer necessary. The number of tasks that can be activated simultaneously is still limited to a maximum of 20 tasks. The value range for the cycle time can be between 200 and 3000 ms. 500 ms is set as default value when a task is created. ToDo: After an update to APROL R 3.2-02, the configuration of the control computer tasks in existing projects must be checked, and eventually adjusted. Upgrade notes 1-3 Illustration 55: New dialog for the configuration of the control computer task 1.33.7 Provision of Python service functions The Python API has been extended with the following service functions in APROL R 3.2-02. DC.provide_service( The newly added service functions can be used for example to detect the exact process graphic ID, and are therefore the basis for the realization of the "Picture in picture" functionality of the APROL system software. A detailed description can be found in the APROL documentation "D2 System API", chapter Addressing via the widget ID. 1.33.8 Updates in the gateway-editor The following updates have been made in the gateway-editor's user guidance in the scope of APROL R 3.2-02. A3 Upgrade Notes 1-4 Plausibility check for the coupling configuration Errors in the configuration (e.g. missing mandatory fields) are noted in the configuration preview, and during saving or checking. These errors are displayed as CAE warnings or CAE errors in the context of the project part, so that they can also be identified as CAE errors or warnings in the project view. These messages can be explicitly ignored, to make test configurations possible. Furthermore, the errors are shown straight away in the gateway-editor's structure tree, in which they can be navigated to in a simple manner via tracking button for correction purposes. Display in full screen mode As of APROL R 3.2-02, the gateway-editor has a full-screen mode, which supports a separate complete screen window for the creation of a connection configuration. Description text can be defined in your project rules for optional fields, which are displayed "grey" by the subsequent connection creation, and point out a possible entry. A generically created value, e.g. as result of the entry of a superior structure (Group information), is displayed in the typical color for links ("blue"). 1.33.9 Check-box for reduced plausibility check The newly added plausibility checks during the checking and compilation of project parts, in the scope of an update (not upgrade!) from an APROL basic release (e.g. update from APROL R 3.2-00 to APROL R 3.2-02), can be explicitly deactivated as of APROL R 3.2-02. With this, there is a suppression of the newly added checks that take place after an update, that the project parts are directly entered as errors for the configurations that have been detected as having them. For this purpose the "reduced plausibility check" check-box in the "Properties" dialog (tab "Project options") can be set. This behavior can also be activated in the CAE libraries, in the "Properties" dialog (tab "CAE data"). The "reduced plausibility check" check-box is not activated per default, and is automatically deactivated after an update to a new release because of security reasons. 1.33.10 Logging of the quantity structure for Iosys variables As of APROL R 3.2-02, the following information is logged in the APROL system messages when writing remanent variables in the remanence file: the current number of variables in the process database, the amount of remanent data, as well as the necessary time to write the data An increased time (>1-2 seconds) to write the remanent data indicates an unacceptably high load upon the sever! Upgrade notes 1-5 The remanent data are written cyclically every 15 minutes, as well as when the Iosys is terminated. 1.33.11 Patch information when checking the installation Differences to the original state of a main APROL release, or build, which have been caused due to a subsequent installation are detected with the installation check (Check Installation), and clearly displayed in HTML format. As of APROL R 3.2-02, the applications, libraries, or packets that have been actualized in the scope of a patch installation are explicitly shown. Illustration 56: Patch information when checking the installation 1.33.12 Notes about the XML configuration of the alarm line In the scope of configuring the AlarmMonitor, as of APROL R 3.2-02, the alarm events for locked alarms can be explicitly marked with an icon. If you would like to use this functionality in the configuration files that you have created yourself, you can do this by using the new key word "LOCKED". Details can be found in the APROL documentation "D1 System Manual", chapter Configuration of the AlarmMonitor via XML. A3 Upgrade Notes 1-6 1.34 New features after updating to APROL R 3.2-01 APROL Notes about the new functionalities in R 3.2-01 can be found in manual "A1 Release notes". Apart from various bug fixes, the following new updates and changes are covered in APROL R 3.2-01. 1.34.1 New controller OS version for SG4 targets In the scope of APROL R 3.2-01, the updated OS version O0290 is supplied for the SG4 targets (Intel platform). 1.34.2 Use of the MD5 check sum with TAR archives As of APROL R 3.2-01, the data archives ( Upgrade notes 1-1 1.35 Important information for an upgrade to APROL R 3.2 An upgrade to APROL R 3.2 can be carried out as of APROL R 3.0-06. There are preparatory measures that are to be carried out in the context of APROL R 3.0-xx. Therefore, read the following upgrade notes carefully before an upgrade to APROL R 3.2. Thereby, special attention should be paid to the preparatory measures for the Combination of project parts, as well as the Backup of the cancelled blocks without replacement block. A necessary operating system change to NOVELL openSUSE 10.2 is associated with the upgrade to APROL R 3.2. Due to this, the following benefits are available to you: Support of the newest and most powerful hardware through the use of the current LINUX kernel 2.6.18.2 Use of further KDE functionalities due to the newest KDE version. ToDo: As the installation of APROL R 3.2 is tied to a change of operating system it is absolutely necessary to make a careful backup of the current projects. The hard disk is formatted in the process of installing the new operating system. Therefore, the necessary steps should only be carried out by the system administrator, or the project manager. The following steps are to be carried out, amongst others, before the installation of the operating system: Record all important data for the re-installation such as IP addresses, computer names, modem connections, etc. Make a note of all of the LINUX login names as well as the passwords for subsequent restoring purposes. Use the CaeManager functionality "Database backup" (menu "Extras/Database backup") to backup the engineering environment, the user specific data, and the directories. The file customerBackup.inc must be correspondingly administered in order to guarantee the backup of user specific data, and directories. The file can be found in the directory /home/ Upgrade notes 1-1 When access to already recorded historical data is desired after an upgrade, then the system internal, and the user specific ChronoLog containers in directory /home/aprolsys/APROL_DATA/chronolog should be saved. The backup must take place with an APROL system that has been halted! Furthermore, the trend data in directory /home/ An external medium (e.g. DVD) should be created from the backup files (TAR archive), or moved via file transfer to another computer, before the installation of the operating system! 1.35.1 Combination of project parts With APROL R 3.2, the explicit separation of the project parts graphic block/graphic macro, and static/dynamic process graphic is abolished in order to increase the productivity of the engineering phase. The editing in the CaeManager has changed in as much as that the DisplayEditor to edit the graphic macros is called directly from the project part "Graphic block". Editing the static part of the process graphic is called parallel to this in the context of the "Process graphic" project part. The conversion of existing projects takes place automatically. The internal steps are explained here for a better understanding: The corresponding block, to which the graphic macro was allocated, is detected for all of the graphic blocks. Finally, the graphic part of these graphic macros is copied into the respective graphic block, as well as all graphic macro descriptions, links, and images are inserted into the description, link and image lists of the graphic block. Also, the comment pages are merged. Here, the following rules apply: The activated version of the graphic macro is allocated to the graphic block. The current version is used when no activated version of the graphic macro exists. If there are other versions of the graphic macro, apart from the activated version, then the current version (when activated version is not the same as current version), or the modified version are exported to the directory /home/ The allocated documentation text is saved thereby in a /DOC directory. If there are any graphic macros that were not allocated to a graphic block, then these are also exported as a graphic template. During the conversion, the corresponding graphic macro description is used for graphic blocks whose short description was empty. A3 Upgrade Notes 1-2 ToDo: Before the conversion, it is possible if need be in APROL R 3.0 to create an additional graphic block for all unassigned but necessary graphic macros, so that the parts of the graphic macros are not exported as graphic templates, but remain in the project database as new graphic blocks. The graphic macro description is then automatically entered as the graphic block description. The same rules apply to the combination of the static and dynamic process graphics, whereby there are no documentation parts to take into account. 1.35.2 Backup of the cancelled blocks without replacement block As of APROL R 3.2, the already discontinued CAE library "IEC61131" has received the status "cancelled", and in favor of the library "IEC61131_3" has been moved into the CaeManager trash can. ToDo: The following is to be taken into account in the context of APROL R 3.0: It is necessary in the scope of APROL R 3.0 to swap the cancelled blocks (DINT_TO_TIME, DT_TO_TD, TIME_TO_DINT, DELAY, RS) for which there is no direct substitution, with blocks of the CAE library "IEC61131_3". Alternatively the versions that are in use, and that are activated, of the five before mentioned blocks can be explicitly stored in a library with the name "SavedBlocks" by calling up the script AprolSaveObsoleteBlocks. Apart from the five above mentioned blocks, the script AprolSaveObsoleteBlocks also considers blocks for which there is no direct substitute in the CAE libraries "APROL", and "STANDARD". The complete listing of all of the saved blocks can be found in chapter List of the blocks saved via AprolSaveObsoleteBlocks, in the appendix of manual "A2 Getting Started". Please note: It must be observed that the use of the script AprolSaveObsoleteBlocks must definitely be carried out before an update of the CAE database to APROL R 3.2 takes place. Finally the library must be generated in the context of your CAE project. 1.35.3 Plausibility check for the naming of CAE libraries In the scope of the CAE database update after an upgrade of the APROL system software, an additional plausibility check ensures that a name conflicts do not take place between libraries of the type "APROL (B&R)", and type "Customer" or "Partner". The update process cannot be continued when a library type "Customer" / "Partner" has the same name as a library type "APROL (B&R)". A corresponding error message is output in this case with a reference to the effected library. The occurrence of open references, and a faulty import of engineering data into the "new" CAE database is thereby prevented with this plausibility check. Upgrade notes 1-3 The update process must be cancelled to clear up the name conflict. For this purpose, the CaeManager must be started from the console with the option "-noUpdate". After the effected library has been renamed, the CaeManager must be closed, and the update process restarted by launching the CaeManager again. 1.35.4 Changed behavior by activation of the default OS for CAE libraries After an update, or upgrade in prior APROL releases, the new default OS for "Customer" libraries was activated. Dependant upon the current projects, the new default settings must be corrected to avoid error output during the generation of CAE libraries. As of APROL R 3.2, the following rules apply for the allocation of the default OS: If the OS version that has been used up-to-date is still supported, then this OS version is solely activated after the upgrade. If none of the activated OS versions that have been used are supported, then the corresponding default OS version for an Intel, or Motorola platform is activated after the upgrade. The settings for the dependencies of the OS versions activated up to now can be adopted in the library's properties dialog. For this purpose choose the [Dependencies] button in the tab OS versions (Controller). After selection of the last activated OS in Version, the settings are shown and can be adopted for the new OS with [Adopt changes]. If no OS version has been activated for a platform up to now, then no OS version is activated after the upgrade. We recommend you to always use the newest OS version to guarantee an optimal system support. 1.35.5 Special features during the configuration of a second Ethernet interface for SG4 targets When configuring a second Ethernet interface for SG4 targets, the INA port number of the second interface must deviate from the port number of the first interface (e.g.: 11159, and 11160). These port numbers must be the same as the port numbers that are set in the InaDriver's configuration (option "-socket", and "-socket_r") in the scope of the control computer's CC modules! As of OS version T0273, the INA communication with two different network cards with the same INA port number is not allowed. ToDo: It must be made sure that a value is entered for the parameter "socket_r" during the configuration of a process bus redundancy. The above mentioned dependencies are to be taken into account. A3 Upgrade Notes 1-4 1.35.6 Additional plausibility check for multiple connections with the same myNode Multiple connections with the same myNode (virtual node number) are prevented through an additional plausibility check when using the current SG4 OS versions. Through this, the INA communication via Ethernet is made stable. As of APROL R 3.2, a CPU logbook entry is generated with a connection attempt to a myNode already in use. A response about the communication is not possible at the moment. If in doubt, try accessing with another myNode. The CPU check encompasses all INA Ethernet connections (Controller cross-connection via Ethernet, ControllerLoader, ControllerManager, InaDriver, etc.). 1.35.7 New TrendViewer for the graphical representation of the course of the processes As of APROL R 3.2, with the new TrendViewer you have a powerful and comfortable tool available for the graphical display of the course of the processes. The configuration of the TrendViewer, and the TrendServer should be checked in the scope of the CAE project start-up. Record gaps due to invalid values are not recorded per default by the TrendServer, and therefore not shown in the TrendViewer. If the display of invalid values is desired then you have the possibility to configure the TrendServer accordingly. For this purpose the option -store_invalidations must be activated in the CC modules for the TrendServer. Recording gaps are then displayed in the TrendViewer as an uninterrupted line in the diagram. 1.35.8 Conversion of the old TrendViewer configurations In the scope of the upgrade to APROL R 3.2, B&R supplies the script AprolUpdateTrendViewerConfig, to convert present configuration files from the old TrendViewer for the new TrendViewer. A TrendViewer configuration contains the choice of trends for the diagram, as well as the set Y axis scaling range of each trend, and eventually the unit changed by the user. Old layout files are not converted. This means that the configurations converted from the old TrendViewer do not contain layout sections. The display takes place with the layout that is already set in the TrendViewer at the time of loading the configuration (e.g. Color of curves, diagram background color). ToDo: Upgrade notes 1-5 The script AprolUpdateTrendViewerConfig must be started using the engineering systems Linux login. During the update, the configuration files of all present projects or the configuration files explicitly named in the command line option are converted. The following table contains an overview of the necessary steps: The "old" trend composition must be saved in the context of APROL R 3.0, and after a successful upgrade to APROL R 3.2 copied into the directory /home/ It must be possible to access the runtime database in the directory /home/ The old configuration files can be found in the directory /home/ A3 Upgrade Notes 1-6 Illustration 57: Overview of the old TrendViewer configuration update The converted TrendViewer configurations are made up of content of the old configurations, and information from the runtime database. Each trend's master data, group, unit, measurement range beginning and end, as well as the diagram's title are taken from the old configuration. The additional trend master data, description, measurement number, filter tolerance and filter type are inserted from the runtime database. The values for the scaling, and the axes labeling, are pre-assigned using this information by the update script, according to the explained scheme. If no information in the runtime database is available for a trend, for example if the block has been deleted in the meantime, then a warning message is output. The information from the runtime database is then missing in the resulting entry in the new configuration. There are the following possibilities to change the layout of the converted configurations: Customizing the layout file default.tvc that is loaded per default when starting the TrendViewer. Starting the TrendViewer with the command line option -layout plus the desired layout file. By manually loading a layout after the TrendViewer has been started. In each of the before mentioned cases, the current layout is adopted in the configuration file when saving the configuration from the TrendViewer Proceed as follows in order to give the converted configuration files that are already in the project engineering a special layout: Start the TrendViewer in APROL R 3.2 in the engineering environment (with the KDE menu "APROL / TrendViewerConfig"), and load the converted configuration files. Thereafter, the layout can be modified accordingly. Finally, the configuration should be newly saved. It now contains the layout that was set. Upgrade notes 1-7 1.35.9 Replacement of the Ult1mo fonts The Ult1mo family fonts available up to now in the scope of APROL are no longer available as of APROL R 3.2, and the associated operating system NOVELL openSUSE 10.2. The fonts, which are no longer available are exchanged as follows in the B&R libraries, and the demo project that is in the distribution. Ult1mo Arial -->Albany AMT, Ult1mo Courier New-->Cumberland AMT. Now, the dialog "Font properties" (menu "Extras / fonts / edit font list") in the DisplayEditor shows not only the chosen, but also the currently used font. ToDo: The familiar display of the visualization is guaranteed when upgrading an existing project from APROL R 2.4 to the current R 3.2. When upgrading from APROL R 3.0 to the current R 3.2, the text objects in the visualization (using the Ult1mo Arial font up to now) must be checked for their size. B&R supplies the script AprolUpdateFonts in order to automatically substitute the Ult1mo fonts that are no longer delivered in any existing projects. The script is in the directory /opt/aprol/scripts/, and must be executed with the engineering system Linux login. It carries out a substitution of the fonts in the following directories: /home/ 1.35.10 Additional plausibility check during checking and compiling The already implemented plausibility controls, as well as the error messages when checking process graphics, and the generation of CC tasks has been intensified in APROL R 3.2. Inconsistencies in engineering can be quickly and specifically pointed out. When checking in APROL R 3.2, graphic macros that have been placed and which cannot be assigned to the graphic block stored in the CFC (e.g. due to the renaming of the graphic block instance) force a cancellation with the output of an error message. A warning is output when generating the respective control computer task. If hyper macro constants cannot be assigned (e.g. when renaming a graphic block instance, or a block's pin) then a checking, or compiling of the CFC where the hyper macro is stored is cancelled with an error message. There is the possibility, as of APROL R 3.2, to carry out a check all of the process graphics with an additional radio button in the recompilation dialog in the context of a CAE project. A3 Upgrade Notes 1-8 Illustration 58: Checking all of the process graphics in a CAE project The checking of all process graphics takes place when recompiling all charts, or with a selective recompilation within the context of a CAE project or a control computer. As of APROL R 3.2, there is the possibility of activating additional validator checks when checking, or compiling a CFC (or hyper macro). The validator check encompasses: The instance of a CFC, The instance of a process graphic, Block instance in the CFC, Block instance in the hyper macro, Pin name of the block, PV name on the chart input / output. If an error is encountered, then an error is output during the checking / compilation, and a CAE message is reserved for the corresponding project part. The extended validator check can be activated in the CaeManager with the menu "Extras/options", tab Productivity. 1.35.11 RemoteCompiling configuration APROL R 3.2 supports the configuration of a computer group for the purpose of RemoteCompiling during generation of libraries, and control computer / controller tasks. The one-time configuration of the scheduler (engineering system), as well as the involved operator stations, must be carried out with the script AprolConfig for their use of RemoteCompiling. Details about the configuration can be found in manual "A2 Getting Started", chapter RemoteCompiling. 1.35.12 Replacement of the external library documentation with As-Built documentation The choice for the creation and the integration of a library documentation that was present up until now ("As built documentation" or "external HTML sides") is no longer supported in the scope of APROL R 3.2. Upgrade notes 1-9 The corresponding radio button for the entry of an external HTML side in the context of blocks, or CAE library's properties dialog, has been removed. Links to other HTML sides can be inserted upon the creation of the As built documentation. Pointers to existing documentation in HTML format is thereby possible. Details can be found in manual 'B4 Project & Library documentation', chapter Creating links in the library documentation. 1.35.13 Encoding entry for Python modules With NOVELL openSUSE 10.2, the execution of Python modules (global LoginServer modules in the DisplayCenter) is terminated when the file contains a character that does not belong to ASCII code, and the encoding is not explicitly stated. This already happens, for example, with an umlaut in a comment line. It is therefore mandatory to stipulate the encoding in the header for all Python modules: # -*- coding: utf-8 -*- All of the project specific Python modules must be correspondingly modified by an upgrade to APROL R 3.2. 1.35.14 Adaptation of the KDE configuration The default KDE configurations that are delivered (for the engineering system, as well as the predefined and stepped configurations for the operating system) have been revised and have been adapted to the currently distributed NOVELL openSUSE version 10.2. The following settings are used per default for all KDE configurations in the KDE control center. De-activation of the menu shadows in the "Display / style" entry, Effects tab. Due to compatibility reason with the current NOVELL openSUSE 10.2 distribution, we recommend that you also de-activate the check box "Menu shadows" when creating individual KDE configurations. Please check if the existing hardware (printer, sound card, etc.) has been identified and configured correctly after the installation of the AutoYaST DVD. If you would like to use your own acoustic signals then the following should be observed on an APROL server that does not have a sound card that is physically present. It is absolutely necessary to configure a "virtual" sound card with YaST2 due to compatibility reasons with the current NOVELL openSUSE 10.2 distribution. A3 Upgrade Notes 1-10 1.35.15 Creation of the physical view independent of the identification system As of APROL R 3.2, the use of an identification system as basis for the creation of a physical view has been removed. In order to guarantee an efficient engineering, the creation of a physical view tree according to your own rules is possible. The following criteria should be observed when creating your physical view. The physical view levels can be freely named. The entries are checked according to APROL validators for syntax errors, and possible length limits. A physical view cannot be changed as long as it is allocated to a project part. The controller's physical view must refer to the penultimate level, as the last physical view level is allocated to the CPU! Upgrade notes 1-11 1.36 New features after updating to APROL R 3.0-07 Apart from various bug fixes the following new updates and changes are covered in APROL R 3.0-07. 1.36.1 Display of record gaps in the trend system As of APROL R 3.0-07, the TrendServer does not record gaps per default during trend data acquisition. If the display of gaps, due to invalid process values, is desired then you have the possibility to configure the TrendServer accordingly. For this purpose the option -store_invalidations must be activated in the CaeManager, in the CC modules for the TrendServer. with regard to this, the option -ignore_gaps has been removed from the TrendViewer. 1.36.2 Starting several instances with the same Self ID Up to now, for parallel operation of several instance of the DisplayCenter it was necessary to save several instances in the configuration of the control computer with a different Self ID, and to call them up with the respective parameter -self 1.36.3 Conversion of files from latin1 to UTF-8 All of the characters must be converted into UTF-8 format when converting existing projects to APROL R 3.x. Apart from the script AprolConvertFilesToUtf8 available in APROL R 3.0-00, B&R have supplied another script AprolConvertFilesNamesToUtf8 with which one file, or all files in one directory, can be converted from Latin1 to UTF-8. The new script expects one file name, or one directory name as an option. Upgrade notes 1-1 1.37 New features after updating to APROL R 3.0-06 Apart from various bug fixes the following new updates and changes are covered in APROL R 3.0-06: 1.37.1 Additional consistency check with the Profibus DP configuration The configuration of a DP master connection takes place with the help of the B&R Fieldbus Configurator. In order to make sure that configurations made in this way are capable of running in an APROL environment, the DP master which is used on the controller must have an 'at least' firmware version. As of APROL R 3.0-06, the driver ApDrvDp (SG4-Targets) writes a record in the logbook for all DP masters, which are detected and supported. The logbook entry contains the slot number and the necessary firmware version, as well as the installed version. If a firmware upgrade is necessary, then it is explicitly pointed out here. The start-up of the DP bus is not prevented by the use of a false firmware version. Even so, a correct operation is not ensured. 1.37.2 Determining the download order in a redundancy system To begin with, when downloading to a redundancy runtime system, there should be a download to the current master (process controller), and finally a download to the current slave (non process controller). This has the advantage that after a complete download of a redundancy system, all client processes (driver) are running on the process controlling server. This avoids that a communication takes place between the process data base (Iosys) and the client processes over the network. For this purpose, the detection of the redundancy status in the DownloadManager has been optimized in APROL R 3.0-06. The DownloadManager then establishes the communication to the AprolLoader of each runtime server. With this connection, the current redundancy status can be determined, and finally the download order set. If needed, an automatic re-sorting of the download job list in the DownloadManager takes place. A necessary change in the download order takes place one time when inserting the runtime system in the download list, and if the redundancy state has changed, then once more before the start of the download. The functionality must be explicitly activated, or de-activated by calling the menu (or using the toolbar) "Downloads / Defining master after download". If there is no connection to the AprolLoader, then a download to this system must be separately confirmed. This should only be done in certain cases (e.g. during an initial start-up), as the redundancy state of the equipment is not clear. Upgrade notes 1-1 1.37.3 Automatic Start of the virtual keyboard for touch screen operation The use of the virtual keyboard for operation after a keyboard failure, or for systems without a physical keyboard (e.g. touch screen monitors) has been greatly simplified in the scope of APROL R 3.0-06. The virtual keyboard is automatically started in the APROL application as soon as an entry field gets the focus (e.g. through clicking). For this purpose, the environment variable USE_TOUCHSCREEN must be set. The variable can be set for example in the file .APROLSystemSettings in the home directory of an operator system, to make it available for all of the operator system’s applications. With web based queries, the virtual keyboard must be activated with the relevant icon one time for each operator station When using the icon in the web queries, the status session- spanning is saved on the client computer. The setting takes place permanently. Illustration 59: Call up of the virtual keyboard in the APROL system messages After activating the virtual keyboard, the relevant icon has a colored cover (green). The virtual keyboard is automatically started as soon as an entry field gets the focus (e.g. through clicking). The virtual keyboard for web applications is independent of the environment variable USE_TOUCHSCREEN. The virtual keyboard is always started by the web server on "Display 0.0". This is specially to be observed when carrying out a web query in a VNC session. When creating the KDE configuration for the operator system, it is compulsory to observe that a locking of the operator station is not possible. After locking the APROL session via the KDE menu "Lock session" on a touch screen, with no keyboard connected, it is not possible to log in again! The virtual keyboard is not displayed. Also, the locking of the screen within the scope of the screen-saver should not be possible. Details for this can be found in chapter Creating a customer specific KDE configuration in the APROL documentation B5 Download & Debugging. A3 Upgrade Notes 1-2 1.37.4 Extended support from the Modbus controller driver The Modbus controller driver has been extended in the ASCII mode. The configuration of the driver (Gateway rule) has been adjusted accordingly. After an update to R 3.0-06, there is the following warning message when compiling an existing Modbus coupling: Illustration 60: Warning message with incomplete configuration In order to get rid of the existing Modbus conflicts, the protocol mode of the respective connections must be explicitly set to RTU or ASCII. The field "Data bits" must also be set to 7 (ASCII), or 8 (RTU/ASCII). If the warning message is ignored, then the driver runs unchanged (RTU mode, 8 data bits) despite an incomplete configuration. RTU is entered as default value when configuring new Modbus couplings. A mixed RTU/ASCII operation is not possible. Furthermore, Modbus slaves with up to 65536 registers are supported. Upgrade notes 1-3 1.38 New features after updating to APROL R 3.0-05 Apart from various bug fixes the following new updates and changes are covered in APROL R 3.0-05. Supply of updated OS versions: In the scope of APROL R 3.0-05, the updated OS versions R0273 (default) and G0286 are supplied for the SG4 targets (Intel platform). 1.38.1 Download without restart of the visualization As of APROL R 3.0-05, the operator can explicitly decide if a DisplayCenter restart should happen after a download has taken place, or if after an update of the database with simple, non- practice relevant limitations, operation should continue. Note the listed limitations in manual "C1 Interactive Process Control", chapter Avoiding a restart after a download. If a restart of the application is suppressed, then it is still possible to work with the existing alarm filter settings, meaning that the existing filter settings are not reset after a download. The changes that have been made to the "alarm groups" in the CAE, without having a DisplayCenter restart, are also considered within the scope of the filtering. In the case of newly added alarm groups, these are switched to active per default. The option "downloadRestart" remains unaffected by this change. That means that when the dialog concerning the download that was carried out is not acknowledged, before the waiting time for a restart, which is defined in this option, then a restart is automatically executed. Use of this option with operator stations, which are not manned, means that the restart of the visualization components of the DisplayCenter take place in the absence of the operator. Further changes in the DisplayCenter. The functionality "Acknowledge warning tone" in the DisplayCenter, can be called in the current release with the function key [F12], in additional to the shortcut [Ctrl] + [Shift] + B. 1.38.2 Upgrades in the controller management Service mode in the controller manager The maintenance and diagnostic possibilities in the ControllerManager have been extended for the service mode, similar to the status display in Automation Studio. When a system error occurs on the controller, or with an explicit setting in the ControllerManager, the controller is put into the service mode. The requirements for an explicit setting in the ControllerManager is that the operator profiles have been given the corresponding rights to reset the controller. The Watch function for the controller's process variables is supported in service mode. Upgrade notes 1-1 Delivery of map files for traceback of errors in case of a malfunction: As of APROL R 3.0-05, Map files (e.g. ApDrvNTP.out.map) are delivered with all of the B&R driver modules that are available. When controller crashes occur, the map files can be used for diagnostic purposes with the use of the backtrace mechanism. The map files refer to the function names, as well as the next known place in the source code, which probably caused the crash. Map files are not supplied for operating systems, or data modules. 1.38.3 Automatic CPU platform recognition with the InaDriver Up to now, information about the CPU platform (Motorola or Intel) has normally been taken from the file ControllerManagerConfig.xml when a connection to the controller is made with the InaDriver. As of APROL R 3.0-05, there is an automatic recognition of the CPU by the InaDriver. 1.38.4 Output language code in python In the python API, the module DC has been extended with the function language_code( ), for the DisplayCenter. The function delivers the 3 digit language code that was set at the beginning of the application. Additional information can be found in the APROL documentation "D2 System API". 1.38.5 Assignment of BOOL variables in the EventDriver The ApEvtLink library is used in the APROL system to transfer event variables from external tasks (Automation-Studio) to the control system, whereby external time stamps are transferred. The configuration of variables with the GatewayEditor is set with the entry VARIABLEN_TYP, how the variable is interpreted by the control computer driver, or on which Iosys data type it should be displayed. Up to now, the following 4 byte data types are supported: FLOAT, INT32, UINT32, DATE. As of APROL R 3.0-05, it is possible to allocate variables of the type BOOL - e.g. for alarm processing. The value transfer, even with BOOL variables, takes place as a 4 byte INTEGER Details can be found in theAPROL documentation"F1 Drivers for B&R Connections", chapter EventDriver. A3 Upgrade Notes 1-2 1.38.6 Fallback mechanism for use of fonts Upon the creation of the visualization in the DisplayEditor, it could happen that the chosen font is not installed, or cannot be used due to a false naming. If this problem occurs, then a fallback mechanism takes effect, and automatically chooses an available and most suitable font. As of APROL R 3.0-05, the font that is actually used is displayed in the DisplayEditor, so that this can be explicitly used by selecting it in the font list. Upgrade notes 1-3 1.39 New features after updating to APROL R 3.0-04 Apart from various bug fixes the following new features are available in APROL R 3.0-04: Changed behaviour when restoring a backed up engineering environment: In the CaeManager, using the "Extras / Database backup" menu item, it is possible to save the engineering system's data. Data which has been saved in this way can be restored at a later stage (Menu item "Extras / Database restore"). Due to the fact that no generated data is contained in the backup, it is absolutely necessary to carry out a recompile after the restoration. After restoring a backup, there must be a total generation. Part generation is not possible at this moment Make sure that the customerBackup.inc file has been kept up to date by yourself, so that all of the customer specific data is additionally backed up. Details can be found in chapter Automatic backup of the engineering system in the "A1 Release Notes R 3.0" documentation. Additionally saving the controller address database during a backup As of the current APROL release, in the scope of the CAE database backup in the CaeManager, the directory dbk also basically saved. When restoring the CAE database (Menu item "Extras / Database restore"), one is explicitly asked if the restore should be carried out including or excluding the directory dbk. In both cases it is necessary to do a final recompilation! Please note that the restoration of the controller address database should solely take place with an unchanged state of engineering. Otherwise overlapping of addresses on the controller could arise, and lead to an unreproducible behaviour on the system. In case the directory dbk is not used within the scope of a restore, the notes about downloading in the manual "B2 Project engineering", chapter Reorganizing the memory for the controller's global variables must be observed. As of R 3.0-04 it is neccessary to install the dongle driver on the windows computer for APROL licencing in a VMware environment on a windows based host computer. The installation files needed for the driver installation are supplied on the APROL system software DVD. Details about the procedure can be taken from manual "A2 Getting Started", chapter Important notes about APROL licensing in a VMware environment. In the scope of APROL R 3.0-04, the OS version N 273 (FlexIQ) is available for the SG4 range of controllers. Upgrade notes 1-1 1.40 Important information concerning the update to APROL R 3.0-03 A. Change from synchronous call to an asynchronous call from function blocks in the OS-library AsHW. Some of the function blocks (FUBs) have been changed from a synchronous call to an asynchronous call within the scope of changes to the OS-library AsHW. Please use the B&R system module documentation to check the correct usage of function calls in your own FUBs. A different behavior can only occur when the calls in the past were not asynchronous. ToDo: To that effect, please check your calls if they deliver the correct status with ERR_FUB_BUSY. The transfer structure can only be overwritten when the FUB is not active (enable is 0, and status not equal ERR_FUB_BUSY). The FUB should be called up cyclically, until the status output is no longer set to ERR_FUB_BUSY. Only then are the output values in a valid state! Use of link nodes within the scope of code generation: Link nodes are now also created for non-configured I/Os. This means that the status variables, for later use of the hyper macro in the SysMon2005 library do not have to be explicitly created in the I/O dialog. For example, when using status variables for non-I/O-modules (e.g. CPU temperature). A link node is a connection point with a defined name. In a link node, links (connections) are assigned between I/O data points or PVs. C. Cancellation of external CAE library documentation as of APROL R 3.2 As of the projected APROL R 3.2, external, custom made libraries will no longer be supported in the usual manner, in favor of the automatic As-Built-Documentation. The documentation of individual function blocks is no longer shown in the context of the function block, as a matter of simplification, the automatic As-Built-Documentation is solely used. ToDo: Older HTML documentations can already be entered as a link in a library context, in its master data description. With this, the creation of a search index for the search machine of your own library documentation has been taken into consideration. Upgrade notes 1-1 1.41 New features after updating to R 3.0-03 Apart from various bug fixes the following new features are available in APROL R 3.0-03: Actualized OS version for SG4 targets: In the scope of APROL R3.0-03, an actualized OS version V0273 has been made available for the SG4 targets of the B&R 2005 series. The following steps must be carried out when updating to the actualized OS version V0273. It is necessary to open the CPU from each and every controller in the CaeManager, and to check the system configuration (sysconf) of each CPU. Subsequently, each controller must be newly saved and compiled. Please note that a OS change of the controller can therefore only be carried out during a system standstill. Automatic inserting of the B&R profiler module: In the previous build R 3.0-02 it was necessary to insert the required B&R system module as a project module, in order to obtain the profiling functionality. The relevant module prfmod$e is now added automatically. Additions in Controller Management: - Configuration possibility of up to 3 DNS server addresses in the system configuration sysconf of the controller (only SG4 targets) - Scanning of the controllerNodes in order to check conflicts in the node's address allocation - Handling of the log book according to OS version Depending on the OS version, the old or the new log book is called up, and if need be individual log books. - Backtrace evaluation with display of all available information. - Saving the log book in Automation Studio compliant XML format (as of OS V0285) for a later analysis in Automation Studio Incremented trend evaluation: Using the ChronoLog mechanism (with the help of an additional ChronoLog macro) it is possible to acquire trend data in set time frame. The last valid value as well as the linearly interpolated value are delivered for the fixed time points. For corresponding details, please see the documentation D2 System API. Checking the APROL-Installation: A new query has been made available in order to be able to exactly assess the state of the installation on an APROL computer – not least, in the case of system diagnostics from B&R-System Support -, that displays all of the versions of the installed programs, libraries, scripts, and RPM packets. Especially with later installations for a fixed APROL release, the difference between the original and current status can be established quickly, and displayed clearly in HTML form. Upgrade notes 1-1 Completion of the CAE libraries "APROL" and "SYSTEM" The delivered B&R-CAE-Library "APROL" has been expanded with several CAE function blocks for the current R 3.0-03. In the "SYSTEM" library, the AprCcAlarmBasic function blocks which are in use have been swapped for the AprCcAlarm function blocks. New layout of the APROL Documentation: The documentation which is delivered on the system software DVD has become a new layout that gives major advantages in handling and navigation. E.g.: Use of frame technology for faster navigating, allocation of differentiated icons for further links (e.g. direct link to the documentation start side), adoption of chapter numbers in the online documentation, larger area for relevant information, etc.. A3 Upgrade Notes 1-2 1.42 Important information concerning the update to APROL R 3.0-02 Starting with APROL R 3.0-02, operating system V0271 is no longer delivered for Intel platform controllers (SG4 targets) – replaced by an optimized version (V0273). Due to substantial changes in operating systems please consider that an upgrade/update of runtime systems may only be executed when plants are at a standstill! Within APROL R 3.0-02, you will be provided new default OS versions for the B&R controllers – V0239 (m68k) and V0273 (ix86). The new operating system V0285, which is the first one to support the B&R Automation Runtime I/O Management (AR I/0), will also be delivered. Details can be found in the chapter New features after updating to R 3.0-02. For existing projects, the following steps must be taken when updating to R 3.0-02! ToDo: The following steps must be taken when changing operating systems: SG4 target controllers: Assignment of the new OS version (V0273 or V0285) and adjustments to the sysconf. Upon changing to the new OS-Version it is necessary to pay urgent attention to the information in chapter Specifics concerning changing of OS version for SG4 targets, applying to current projects, as well as SG4 controllers which have already been configured. Customer libraries: Activation of the new OS version (V0273 or V0285) followed by generation of the customer libraries. When downloading to the controller, the OS version assigned in project engineering and the OS version on the controller are compared, and then the operating system is changed automatically. When updating the operating system, remanent data on the controller is lost! If changes are made to the configuration, a controller restart is absolutely necessary! Upgrade notes 1-1 1.43 New features after updating to R 3.0-02 | . 1.43.1 Preparing OS version V0285 for SG4 targets With the provision of OS version V0285, you will now be able to use all of the B&R Automation Runtime I/O Management (AR I/O) features together with the APROL system software: This has the following advantages: Support of all B&R module operating states Complete support of configuration and status I/O Direct inverting of hardware I/O Configuration of substitute values for hardware I/O Use of simple configuration dialog boxes Complex modules can be configured without extra programming Fastest response times Lower system load Note the information about switching to a new I/O system in chapter Important information concerning the update to APROL R 3.0-02. Switching to the new I/O system (AR I/O) via OS switching: The following possibilities are available when switching over: As long as a controller is not yet connected, a checkbox in the "Rack properties" dialog box can be switched to the new I/O system. This checkbox is no longer available after switching over. The I/O system is shown instead. In the Rack view, the "Rack properties" dialog box can be opened using this icon! If a controller is then connected, only the modules that support the new I/O system (SG4) are shown in the module selection. Therefore, the selection of the operating systems for the controller is also limited to ones that support the new I/O system (operating system versions V0285 and up). Upgrade notes 1-1 If a controller is connected, switching to the new I/O system using the operating system selection option. The checkbox in the Rack properties dialog box is not available; the current I/O system is shown there. Selecting an operating system (>V0285) initiates switching to the new I/O system. The dialog box for selecting the operating system can be accessed in the "Module view" tab for the CPU using the "Operating system" menu item in the shortcut menu. Switching to the new I/O system is not reversible, i.e. switching back is not possible! In both cases, switching over includes converting the I/O configuration to the new I/O system. Before converting, verification takes place to determine if all requirements for successful conversion are met. If this is not the case, the system will not be switched over. After switching to AR I/O, a smooth downloading of new controller logic can be limited in special cases! Before using AR I/O (OS version V0285), please contact customer support to get detailed information about the possible limitations with regard to your system configuration. 1.43.1.1 Guidelines for changed module configuration with AR I/O The configuration of the I/O modules has changed as compared to operating systems mentioned and result in the loss of the configured "values" or I/O variables. 1.43.2 Importing the APROL SSL CA certificate With release APROL R 3.0-02, a new SSL CA certificate is being delivered that is used as a signature for all APROL server certificates. With these server certificates, the SSL connections are encoded and signed for web queries (e.g. reports). A3 Upgrade Notes 1-2 The new CA certificate, also called certificate from the certificate authority or certificate from the SSL subscriber (Konqueror), is – unlike older APROL releases – identical on all APROL servers. ToDo: After completing the update to APROL R 3.0-02, the new CA certificate should be imported into the web browser that is being used. Afterwards, all SSL access to the APROL server starting with release R 3.0-02 will take place without requiring confirmation. The import is to be carried out once on each APROL system from any APROL server with Release 3.0-02 installed. For web-based access on Windows computers, it's necessary to import the new CA certificate into the web browser being used there. 1.43.2.1 Importing the certificate in Konqueror: Open the following URL in Konqueror http:// The CA certificate "Process Automation – APROL Root CA" is self-signed. Corresponding warnings can be ignored. 1.43.2.2 Importing the certificate in Internet Explorer First, enter the URL http:// Illustration 61: Upgrade notes 1-3 In the "Certificate" dialog box, the certificate import wizard must be started using the [Install Certificate] button. The information dialog box shown is confirmed by clicking on [Next>]. Illustration 62: Installing a certificate Then select the option "Automatically select the certificate store ...". Confirm the selection by clicking on [Next>]. In the next dialog box shown, you can complete the import by clicking on [Finish]. Illustration 63: Automatically select the certificate store Other warnings can then be ignored. The request to install the certificate must be answered with "Yes"! 1.43.2.3 Importing the certificate in Mozilla Firefox After opening the URL http:// A3 Upgrade Notes 1-4 Illustration 64: Using the [View] button, you can check the details about the certificate to be imported. Acknowledge importing the certificate with [OK]. Illustration 65: Viewing the certificate to be imported With all web browsers, there may be earlier imported CA certificates that must be removed! Upgrade notes 1-5 1.43.3 Init and exit code for function blocks Starting with APROL R 3.0-02, it's possible to enclose the init or exit code in a separate initialization or deinitialization area outside the actual program code when creating function blocks. For this purpose, you are provided the "Init Code" or "Exit Code" tabs when creating function blocks. In function blocks you have created yourself, check if functions are used that can only called in the Init or Exit area. Pay special attention when using of the "TMP_alloc" function! While executing the init code the current values of input / output variables (block pins) are not available. This restriction is not valid for constants! The program part that is entered in the "Init code" tab, or "Exit code", must be ended with return 0. The return value that is forseen for future expansions is of the type INT, and is not evaluated at present. 1.43.4 Security and transparency when handling the B&R controller The following functions, provided for the first time in APROL R 3.0-02, provide an even higher level of security and transparency when carrying out engineering tasks with B&R controllers: Starting with APROL R 3.0-02, the target memory on the controller is checked when downloading to SG4 targets. Only USERROM, SYSROM or DRAM memory areas are valid possibilities for the target memory. Status monitoring of the INA connection represents another security aspect during download. The ControllerManager and ControllerLoader monitor the status of the INA connection during the download procedure and indicate the loss of a connection if this occurs. Starting with APROL R 3.0-02, detailed information about the supported OS versions for B&R controllers can be found on an additional help page. In the CaeManager, an overview of all supported OS versions and the corresponding default operating system are shown after opening the "Help/APROL Controller OS Info" menu. After selecting an OS version entry, detailed revision information about the individual operating system versions will be output. A3 Upgrade Notes 1-6 1.43.5 Change to the interface name in the configuration for a DP master connection When using the new I/O system (AR I/O) for SG4 targets (OS Version > V0285), the interface name must be adjusted to the new format manually for an existing DP master connection (OS Version < V0285). Within the framework of the CPU configuration, the interface name must be changed manually from the previous format The subslot name is no longer required starting with OS Version V0285! After saving, the hardware must be activated / compiled and generated. 1.43.6 Support of the new IF761 and IF762 interface modules for SG4 targets For the configuration of a DP slave connection, two new interface modules IF761 and IF762 have been made available for Intel platform controllers. The re-building of the DP-Slave-Driver "ApDrvDpSl", and the support of the IF76x cards means that the IF661-library is no longer needed for SG4 targets, instead the AsL2DP-library should be used. ToDo: If the ApDrvDpSl-driver is already in use in the CAE, it is necessary to delete this module one time from the CPU and install it again, so that the AsL2DP-system library is inserted into the CPU. This does not result in changes to the configuration of the connection. This change applys only to Intel-CPUs. The configuration within the project rules for the IF661 and IF761/IF762 is identical. 1.43.7 Special features for an OS change of SG4 targets From the APROL-Release 3.0-02 onwards, the following mechanism will be used for transferring the settings, when an OS-Change for an SG4- Target takes place. If the OS-Change takes place with different OS-Generations (e.g. V2.67 V2.73 or V2.73 V2.85), then the Default-Sysconf is transferred to the project for that CPU- Type, and extended only for the projected Ethernet settings. Due to technical reasons it is not possible to transfer all of the other settings, therefore these settings must be entered once more. Upgrade notes 1-7 If the OS-Change takes place between two similar OS- Generations (e.g. V2.72 V2.73 or F2.73 H2.73 ), then all of the Sysconf- Settings are preserved However, there is a missing Default- Setting in the actual H2.73, which has to be edited: "EXCEPTIONS, DoTrace, ui4, 1". In this way, debugging information is saved if an error occurs (page fault or cycle time violation). They can then be loaded onto the controller via FTP and used for error analysis. Proceed as follows: In the CPU view, open the Sysconf, go to the "OTHER" tab and create an "EXCEPTION" node. Within this Node, a data point with the name “DoTrace”, the type “ui4”, and the value “l”, must be created. When creating new CPUs, this setting is already present! After having accepted the sysconf, all settings should be checked again. This procedure should be carried out for each individual CPU. 1.43.8 Preparation of the current B&R hardware catalog With the delivery of R 3.0-02, the most current B&R controller product range is available for the configuration of your system. ToDo: The current B&R hardware catalog has now been implemented; therefore, it is absolutely necessary to open the dialog box for the "configuration of the I/O module" once for each I/O module and to confirm updating the configuration information by pressing the [OK] button before generating the controller hardware. This guarantees the validity of the I/O configuration due to the newly added plausibility control (e.g. the existence of a measurement range when using analog signals). After saving, the hardware must be activated / compiled and generated. Also the configuration of the I/O modules DM455, DO435 and AT300 must be checked. 1.43.9 Changes to the IEC61131 library Release 3.0-02 introduces a revised IEC61131_3 library. It contains countless new blocks and functions such as "multiple" blocks with a flexible number of inputs as well as revised versions of earlier blocks. To guarantee the exact same logic when updating a project, the older familiar IEC61131 library is provided with unmodified block versions. All of the components included have been cancelled, but are still operable. Standardized blocks generally refer to replacement types in the new IEC61131_3 library. For the same reason, the hyper macros from B&R libraries are still based on the older block versions. In the new IEC61131_3 library, the outputs of the DINT_TO_TIME, DT_TO_TOD and TIME_TO_DINT blocks from the "Conversions" group have been corrected according to the data type convention for TOD and TIME ([s] to [ms]). In addition, the DELAY block in the "AnalogSignalProcessing" group has been adapted to IEC-61131-3, making it incompatible with the older block version from the IEC 61131 library. The RS block in the IEC61131_3 library has a shifted pin-out for the inputs in contrast to the older version from IEC61131. A3 Upgrade Notes 1-8 ToDo: To guarantee that existing project plans continue to work correctly, B&R recommends not immediately replacing blocks from the older IEC61131 library with the newer, revised versions in IEC61131_3 if you want to quickly update your release. However, this should be done as quickly as possible e.g. the next time the system is shut down. APROL provides the AprolExchangeDiscontinuedBlocks script for this. It exchanges all of the cancelled blocks in CFCs and hyper macros with their replacements. The verbose level, which allows a larger "extent" for the output of the AprolExchangeDiscontinuedBlocks script, can be activated using the call option - - verbose. When using the option - -checksubstitute, the CAE database is checked for required replacements. when doing this, the database is not changed. The resulting outputs for the AprolExchangeDiscontinuedBlocks script for required replacements can be redirected to a text file with the Linux command ">File_name". The new function "Replace all cancelled blocks" provides better control when a CFC or hyper macro is open. There are no replacement types for non-standard blocks. They must be removed from the application by making engineering changes. Once the newer block versions are applied, you need to check whether the project chart / hyper macro still works correctly. Special attention should be given to the following: - Possible loss of remanent data - Check of default values if block inputs are not connected. - Changes to the data structure of blocks may require the dbk directory to be deleted! 1.43.10 Forced use of scaling blocks For the shifting, scaling, and rotational animations, it's generally necessary to use a scaling block (AprCcPicScale) due to the new expanded value range for a correct and complete engineering. This also applies to all values input from the visualization (e.g. text input for a variable, scaling input, etc.). If scaling blocks were not used for the animations above, modified bases may occur in the animation in some circumstances. ToDo: The consequent use of the AprCcPicScale scaling block from "APROL " CAE-library is therefore compulsory. In order to be able to initiate actual projects quickly, the environment-variable INCORRECT_PISCALE_USAGE=y can be set. Please note that this environment-variable is omitted in the following APROL release. An adjustment of your engineering – with the correct usage of the scaling block – will be compulsory at the latest with the next release. Upgrade notes 1-9 1.43.11 Increased efficiency for the configuration . 1.43.11.1 Replacement of cancelled blocks The cancellation of some CAE library function blocks allows interactive or fully automatic replacement of older function blocks with newer, optimized function blocks that handle the same functions. The B&R library included in APROL R 3.0-02 has become more extensive. It may be useful to cancel implementing self-made library function blocks and replace them with tested B&R library function blocks that handle the same functions. Under the "Master data" tab for the respective function block, the "Cancelled" flag can be used to specify the required setting. Additionally, you can specify if an error message should be output and defined a possible replacement function block under the entry for the library. If used in a CFC or hyper macro, cancelled function blocks can be replaced both interactively (see following description) and also automatically and globally. Interactive replacement: Using the "Replace discontinued blocks" menu item in the shortcut menu for the CFC, you can replace the selected function block, all function blocks of the selected type, all cancelled blocks The following is true when replacing a function block: There are no other function blocks or connections permitted in this area of the CFC. Otherwise replacing is not possible. If possible, connections that are not pin-compatible are disconnected and placed as lugs. If the new function block is thinner than the function block being replaced, corresponding connection lines are added to the function block output. If the new function block is wider than the function block being replaced, corresponding connection lines on the function block output are shortened as long as the connection lines are running horizontally. Other connection lines are places as lugs on the input bar of the new function block. If connection lines are deleted, they are all listed in a dialog box. 1.43.12 Using multiple function blocks Multiple function blocks were implemented in the B&R CAE libraries in order to make is easier and faster to select the library function blocks when creating programming logic. A3 Upgrade Notes 1-10 For example, all AND gates of the same type that only have a different number of inputs (AND_BOOL_2, AND_BOOL_3, AND_BOOL_4, AND_BOOL_8, AND_BOOL_16) have been replaced by a multiple function block starting with APROL R 3.0-02. Similar to this example, this type of reduction was implemented for all function blocks if possible. In the CAE library and in the logic diagram, multiple functions blocks are shown with a blue triangle on the lower right edge of the function block. The number of pins used for multiple function blocks can be varied by simply increasing or reducing their size (dragging the button of the function block). Here, as when replacing function blocks, the function block constants must be checked after changes are made to the function block! 1.43.13 As-built documentation for the CAE libraries Starting with APROL R 3.0-02, the B&R CAE libraries are delivered with as-built documentation. These online help files, which are created using modern web technologies, can be opened like any other help file. When creating custom libraries, a radio button found under the "Master data" tab for the function block can be used to select the use of external HTML pages or create as-built documentation. The "As-built documentation" flag enables six other tabs (under the "Documentation" tab) where the function block documentation can be entered in the following areas. Apart from the freely defined links, graphics can also be used. The illustrations should be in PNG-format. Other formats will automatically be converted into this format. The file size of the graphic which is to be linked (after eventual converting) is not allowed to exceed 100KB in PNG-format. 1.43.14 Using extended text attributes when creating visualization application The handling of text objects when creating visualization applications has completely changed starting with the current APROL release. This provides additional possibilities for displaying objects (e.g. centering) and handling texts. Upgrade notes 1-11 Older text objects are still compatible and are converted to new text objects automatically when editing them. No additional work is required for updating! To create a text object, open the "Tools / Draw / Bound Text" menu item in the DisplayEditor. Then use the mouse to select the text cell area (bounded area). The upper area of the resulting input and configuration dialog box can be used to enter the desired text. The middle area of the dialog box is used to define the geometry of the text string for the text cell (cell alignment). In addition, an interval to the vertical borders can be defined (in pixels). The following attributes are available in addition to Font selection: The line break attribute defines the display of a text line if its length exceeds the available horizontal space in the text cell. If a line break is active, if needed, a line break is placed automatically by converting spaces in the display. On the other hand, disabling this attribute converts existing 'Line feed' characters to spaces. If the 'Don't truncate' attribute is set, a string is allowed to exceed the borders of the text cell. It is then displayed beyond the border in both the horizontal and vertical directions (for multiple lines). If the line break attribute is activated at the same time, it has priority. The dynamic border attribute creates a text cell that automatically adjusts to the size of the entered text. Setting this attribute clears the line break attribute, and vice versa. The Do not rotate text attribute can prevent text from being rotated. Further details can be found in the APROL documentation "B2 Project Engineering", chapter Extended attributes for text objects. 1.43.15 Marking if compilation/generation is required for project elements When recompiling your project, you have the possibility to make the setting "Only compile and generate changed function charts and task in this project" in the Recompile dialog box. As of APROL R 3.0, the project parts affected by this recompile procedure are marked automatically – in order to increase clarity. The Reload icon is shown for CFCs that must be compiled because components have been changed and hardware that must be generated because CFCs have been changed. The CFC is marked after it is activated, and the hardware that must be generated is marked after compilation of the changed CFC. The markings are stored in the respective versions of the corresponding project elements, as with CAE messages, and shown throughout the project views. If the guidelines are not followed in the CaeManager (i.e. required compilation and generation are not carried out), this information will be provided again explicitly when downloading via the DownloadManager. A3 Upgrade Notes 1-12 1.43.16 DisplayEditor configuration file In the DisplayEditor, it's possible to configure and save toolbars and shortcuts for each designer to quickly open up menus. The designer-specific changes made are stored in the file 1.43.17 Change to the ChronoLog directory The directory structure for the ChronoLog container has changed in APROL R 3.0-02: The log container was moved from the directory /home/aprolsys/chronolog to the new directory /home/aprolsys/APROL_DATA/chronolog. In future APROL releases, further directories in which data is recorded during runtime are held in the new APROL_DATA directory. Moving existing logs and adjusting all relevant configurations takes place automatically when updating to APROL R 3.0-02. ToDo: If custom scripts are used that access the log path or set the environmental variable ARKPATH, they must be adjusted accordingly. The same is true for custom modifications to the web server configuration (apache2.conf). Upgrade notes 1-13 1.44 Important information concerning the update to APROL R 3.0-01 Exporting runtime parameter sets: Because the format of the (mySQL) database for the ParameterCenter was changed, the following steps must be taken before updating from APROL R 3.0-00 to APROL R 3.0-01. The necessary steps only need to be carried out when updating from APROL R3.0-00 to APROL R 3.0-01! The following steps must be carried out as soon as you have created the parameter sets in the runtime system in APROL R 3.0-00! Before updating the APROL system software, all parameter sets created in the runtime system (Status - R 3.0-00) must be exported using the export function in the ParameterCenter. Then update the APROL system software to Build R 3.0-01. After successfully updating to this build, import all (previously exported) runtime parameter sets using the new import function. Block changes in the library IEC61131 The outputs of the DT_TO_TOD and TIME_TO_DINT blocks from the "Conversions" group have been corrected according to the data type convention for TOD and TIME ([s] to [ms]). For safety reasons related to existing projects both blocks are delivered in an inactivated form. ToDo In order to recover operability of projects using the mentioned blocks, the former block version 3.0 can be activated. Nonetheless all projects should be switched to the new corrected version 3.1 as soon as possible. Changing the IEC type DT from long to double (for the control computer) The IEC data type DT was changed from long to double for the control computer. Now, higher resolutions than one second are possible for this IEC type on the control computer. If the values of corresponding, remanent process variables (only CC side) should still be available after restarting, the remanent data must be converted during runtime! When updating to APROL R. 3.0-01, the program AprolConvertDtToDouble is provided for this conversion. The program AprolConvertDtToDouble is part of the utilities package. For the conversion, it is necessary that the APROL system is in Run level 1 (only Iosys for the runtime system may be started). Additionally, access to the PDL database (pdldb) must be possible. It can be found in the engineering environment in folder home/ server>: Upgrade notes 1-1 The script can be started in the runtime environment using the option "--runtime". The engineering system must be able to be accessed during conversion! Please use the following overview when carrying out the necessary steps: Step Description 1 APROLupdate of the engineering environment 2 Recompile the project 3 Save the remanent database (see above) on the runtime computer 4 APROLupdate of the runtime computer 5 APROLsystem must be set to Run level 1 6 Start the conversion script (AprolConvertDtToDouble) in the runtime environment 7 Download (download source: engineering system) Mandatory entry of the domain names for the logging server and cluster name According to general Web standards, a "certificate" is sent from the Web server to the client (browser) for each SSL connection (https:..) for APROL reporting and accessing the documentation. This certificate is used to identify the server for the client and represents a type of ID. This should guarantee that the data being transferred is really coming from the Web server that was contacted. For this reason, the certificate contains the name of the Web server. The certificate also must be signed by a "Certification Authority", CA for short. The browser accepts this certificate without question if three criteria are fulfilled: The certificate is for a valid timeframe. (from ... to) The name of the contacted Web server matches the name of the Web server listed in the certificate. (including the domain name) The certificate is signed by a "trustworthy certification authority". The certificate is made for the server's fully qualified domain name (including domain), therefore the name of the logging server must include the domain in the configuration. After an update to APROL R 3.0-01, we highly recommend that you enter the domain names for (an existing) control computer and then save it again. For each addition control computer configuration, the domain names must be entered (mandatory field)! If a redundant system is being used, it is necessary to enter the name of the cluster including domain when configuring the APROL cluster (via AprolConfigHeartbeat script) starting with APROL R 3.0-01. When resolving names via /etc/hosts, this file must be adjusted on all computers that access the Web if necessary! Certificates for SSL signatures (CA certificates) can be downloaded using the URL https:// A3 Upgrade Notes 1-2 1.45 New features after updating to APROL R 3.0-01 . 1.45.1 Support of systems with 64-bit architecture As of now, APROL is also available in a 64-bit version. The APROL system software now provides all of the advantages of 64-bit architecture after selecting the 64-bit capable operating system on the AutoYaST DVD. 1.45.2 Updated physical view dialog box The physical view dialog box now contains two different was of displaying the physical view. To improve orientation, the entire physical view can be called up in a structured tree, or the hardware can be shown in a flat view without taking any structure elements into consideration. 1.45.3 Cancellation of special layer for controls and widgets The special layer for controls and widgets has been cancelled. Now, they can be placed in any layer. This improves functional or topical grouping of all graphic elements for the visualization using layers in the engineering system. 1.45.4 Preparation of the S5/S7 driver for B&R controllers APROL supports, starting with R 3.0-01, a TCP/IP- based connection driver for the SG4 controller from the B&R 2005 series used to connect a Simatic S5 or S7 controller. The configuration can be made easily using the APROL Gateway Editor. Detailed information can be found in the F1 Drivers for B&R Connections documentation. 1.45.5 Easy login for WEB reports Intelligent data handling for individual sessions make logging in for WEB reports easier and more secure. In this way, for example, a mandatory logout can be carried out for inactive sessions by configuring an operator idle time, which increases security. 1.45.6 Standardized time navigation for WEB reports All Web reports that include a time-based scan of data sets that are not time-incremented have a standardized user interface for detailed time navigation. In this way, searching the data is supported by intuitive and uniform menu items. Direct selection of time spans has been updated to include an easy-to-use, calendar-based quick selection system. Upgrade notes 1-1 1.45.7 Defined display of small objects when zooming out of process graphics The DisplayCenter has a new option "-minVisibleSize" that can be used to globally define if very small graphic objects are to be suppressed on the display. In this way, process graphics that have multiple pages and are therefore over-sized remain clearly visible when zooming out because extremely small graphic objects that can no longer be read or interpreted after zooming out are no longer displayed. 1.45.8 Redundant connection of B&R controllers to APROL Communication using the APROL standard driver to SG4 controllers from the B&R 2005 series can now be set up with a redundant connection using a 3IF781 insert card. In this way, the INA, event and cross-communication drivers can only communicate with the controllers via separate sub-networks by configuring an additional alternative route. 1.45.9 New search engine for documentation The search engine used previously for documentation was replaced by a more powerful, fully UNICODE capable search engine. It automatically indexes the complete APROL product documentation, the documentation for the hardware catalog and the library function blocks, as well as the documentation for all of your projects during generation and therefore guarantees a uniform search index for runtime and operator computers as well as engineering machines. Manually creating a search index is now no longer necessary. 1.45.10 Additional help dialog boxes for IEC types and DEFINES To speed up engineering, two additional dialog boxes were added in the "Help" menu. "IEC type help" provides you with an overview of the IEC types that are available and their length on the control computer and on controllers. There is also another menu item that provides information about preset Defines to make it easier to create your own function blocks. 1.45.11 New import/export functions in the ParameterCenter Starting with R 3.0-01, the ParameterCenter provides the function "Export all RUNTIME parameter sets" in the "File" menu and also in the shortcut menu for the individual parameter sets. Now, all existing runtime parameter sets can be easily exported into individual XML files exported in a single step and imported later. 1.45.12 System pin as function block pin attribute To safeguard APROL-specific pins on certain control computer function blocks, these pins are now protected with the attribute system_pin. This guarantees that system pins that are directly linked with system properties for the APROL system are not "accidentally" modified so that the configuration can no longer be correctly handled by the corresponding server processes. A3 Upgrade Notes 1-2 1.45.13 Updated function block documentation In preparation for the as-built documentation, there is now a new tab for function block documentation data acquisition so that structured function block documentation can be entered for library function blocks. In addition to the known description, there are now also texts for "Introduction", "Limitations" and "Commissioning guidelines," which are shown directly in the documentation that is automatically created. For flexible handling of your documentation, use HTML as display description. The effects on the representation can be seen directly using a preview function. 1.46 Starting the Engineering system after an update An update of the /opt/aprol directory means that the modifications actually done during the update have to be applied to the existing APROL systems. These modifications will not take effect until your current Engineering system has also been accordingly updated. 1.46.1 Engineering system update Additional update steps are automatically made to the Engineering system after the CaeManager is started. They concern the CAE database (caedb). Prerequisite for this is that the "CAE database: View" user right is granted. How to do this is self-explanatory. Messages in the scope of the CAE update are saved in the sysconfig.clc ChronoLog container. They can be called up in the /home/aprolsys/APROL_DATA/chronolog/ directory with the following command: ChronoLog sysconfig.clc --id=CAEUPDATE:* Filtering is possible in the following manner: ChronoLog sysconfig.clc --id=CAEUPDATE: Upgrade notes 1-3 1.46.1.1 Procedure for updating the Engineering system If, after starting the CaeManager, the system determines that the Engineering system database (caedb) has an older time stamp or version number than the database delivered with APROL, the user is offered an update for his engineering environment. The files and directories as well as the caedb database are updated in the engineering environment. For security reasons, all data affected by the update procedure are first automatically saved, so that in the unexpected even of a failed update it is possible to restore the original state without any problems! The backup files are created using the current time stamp and saved next to the original files. The following example shows the procedure for creating copies: When performing an update on Jan 10th, 2000 at 15:03 local time, the database files "caedb.tree" and "caedb.link" are copied and filed under "caedb.20000110_150300.tree" and "caedb.20000110_ 150300.link" respectively. Before performing these steps, you can define whether any less recent back-up files should be deleted. This is recommended because the high quantity of filed data can quickly take up available hard-disc space. The database is opened locally (i.e. without accessing the database server) in order to perform a risk-free and complete update of the database. The current conditions are automatically checked before the actual update because it is required that no additional user can access the database during the updating process. If this requirement is not met, the user is notified and the system waits until the condition is met. Due to the fact that a number of time-consuming database operations are performed during the update procedure, this process may take up some time deepening on the size of the database. Once the update procedure is complete, any errors which may have occurred are displayed in the dialog box. In this case, an easy option for restoring the original status is available by copying back the data, which was saved earlier together with the time stamp. The version number and time of update can be viewed later in the CaeManager in the menu "Help / Database Info". It is absolutely necessary to carry out the following items after the Engineering system is updated: Regenerate your own individual libraries. Recompile all projects to be downloaded. Download the project to the Runtime or Operator system and the controllers. 1.47 Implementing UNICODE into existing projects It is mandatory that parts of this task be handled in R 2.4-04! It is described in manual "A2 Getting Started", chapter APROL delivery contents, that APROL processes UNICODE in the files, i.e. is UNICODE compatible. It is described in manual "A2 Getting Started", chapter APROL delivery contents, that APROL processes UNICODE in the files, i.e. is UNICODE compatible. To simplify matters, the contents of the CAE database (caedb) are made UNICODE-capable, not the individual projects themselves. caedb contains all of the projects as well as all libraries. A3 Upgrade Notes 1-4 Important note about using partner libraries If you used libaries of type Partner in R 2.4-04 and secured them with a password, the following information must be observed. Before saving your Partner libraries (see Step 1 in the following table) that are secured with a password, these passwords must be deleted or removed for security reasons. After the update to R 3.0, you can enter new passwords or reassign the old ones. The following table provides a description of the procedure to be used to make caedb UNICODE-capable: Step Description 1 In APROL R2.4-04, the CaeManager must be used to back up the data of the Engineering system (Extras / Database backup menu item). In this procedure, make sure that the customerBackup.inc file has been maintained in such as way that all of the engineering data necessary to generate a Runtime system is backed up as well. 2 The Linux 9.3 SUSE distribution version must be reinstalled from the AutoYaST installation DVD. Then APROL R 3.0 must be installed from the System Software DVD. Finally, you will need to basicly configuration the Engineering system with the same name as used under R 2.4-04. Also see manual "A2 Getting Started", chapter: Basic configuration of an Engineering and Runtime system. 3 In the "empty" Engineering system, use the CaeManager's Extras / Database restore function to restore the Engineering data backed up in R 2.4-04 to the new Engineering system (R 3.0). It is not possible to restart the CaeManager after restoring since the restored database isn't UNICODE-capable and its structure doesn't fit with R 3.0. 4 Use the AprolUpdateEngin_R30 script to convert caedb to UTF-8. If this step is completed without errors, all of the projects contained in caedb can be edited with CaeManager. 5 Since the database has been converted to UTF-8 with the scrip mentioned above, the converted caedb is updated to R 3.0 after the CaeManager is started. 6 The links for BurBasic, BurStandard, and BurProfessional must be deleted from the /home/ 1.47.1 Converting CAE files to UTF-8 The following project-specific files in the file system must be made UNICODE-capable (i.e. converted to UTF-8) "manually" as needed with the AprolConvertFilesToUtf8 script before engineering can resume in R 3.0: cnf/DisplayCenter/user/ Upgrade notes 1-5 In this regard, also be aware of the changes in the AlarmMonitor configuration: The new alarm and message system and event display (Item E) in the chapter Engineering(-System) von R 2.4-04 auf R 3.0 . cnf/DisplayEditor/dynamic.list cnf/DisplayEditor/colors/color. 1.47.2 Converting the Web area to UTF-8 All project-specific HTML pages must be processed with the AprolConvertToUtf8 script. The header of each of these HTML pages must contain the encoding entry. This is the fourth line down in the following example. Example: The pages can usually be found in the following directories: PROJECTS/ 1.48 Adapting an R 2.4-04 Engineering system to R 3.0 The following overview provides a summary of the things you need to do to adapt existing projects to APROL R 3.0 after an update. In addition, this section will briefly illustrate a number of important advantages which will result from these adjustments. Adjustments that are functionally necessary are differentiated from adjustments that are not functionally necessary but recommended. Measures that are functionally necessary are indicated in the table with (!). A3 Upgrade Notes 1-6 A) Installing the new SUSE 9.3 distribution with the set package selection Using the new Linux 2.6.11 kernel allows the newest and most modern hardware to be supported. The new KDE version provides improved KDE functionality. Prerequisite for internationalizing APROL included (UNICODE capability). Note: After installing Linux with the AutoYaST installation DVD, the System Software DVD should be kept ready for use. ToDo !: Saving your engineering in the Engineering system. Linux must be reinstalled with the AutoYaST installation DVD before APROL R 3.0 is installed. B) Providing new APROL libraries Function blocks are divided into one library with IEC 61131 function blocks and an APROL library with function blocks to handle special operations and functions of the APROL process control system. The existing configuration with function blocks from the discontinued libraries will continue to be used. Note: The existing STANDARD library has been discontinued. It is no longer possible to place function blocks from this library in APROL R 3.0. On validated system, the existing function blocks from the STANDARD library are not exchanged automatically during an update. This exchange (i.e. conversion) can be done separately with the AprolExchangeDiscontinuedBlocks script. ToDo: If desired, the function blocks in your existing project from the STANDARD library can be replaced with the function blocks from the IEC 61131 and APROL libraries. Information regarding how STANDARD function blocks have been split up can be found on the documentation overview page of the APROL libraries. Select the library properties from the Properties shortcut menu item after selecting the corresponding library. The Help button will take you to the documentation overview page. After selecting the respective tab for the respective library (APROL or IEC 61131), the Substitution list link will take you to the desired information. C) Internationalizing APROL (Using UNICODE (UTF-8)) Installing the APROL Language DVD allows all APROL systems to be translated into any language with any character set. The only thing necessary is the translation itself; all other adjustments are made by the system itself. Upgrade notes 1-7 ToDo: Install the APROL Language DVD. D) Checking the engineering with APROL validators Checking the syntax of all information entered prevents errors. Easy identification of false entries with the context-sensitive help. Easy and early detection of all faulty configurations with plausibility checks. ToDo !: Check your entire engineering work and entries with syntax in mind. The syntax you use will be checked by the validators. E) The new alarm and message system and event display Checking the syntax of all information entered prevents errors. Easy identification of false entries with the context-sensitive help. Note: To use the new AlarmSpooler, the following file needs to: $HOME/ENGIN/PROJECTS/ A3 Upgrade Notes 1-8 The AlarmServer no longer supports the reset_ack option. The CC module configuration must be adapted accordingly. The behavior of the "old" alarm function blocks BALARM_PRO and BALARM_EXT has also changed accordingly as well. Additional information regarding alarm function blocks can be found under Item G in this section. The output pin ISQUIT (previously AQUIT) from the now current AprCcAlarm alarm functon block is now set to low as soon as the respective alarm event occurs again. If your reset_ack functionality should continue to work as usual, you will have to do some reengineering. If the function block is set to Mode 1, the system acknowledges the alarm. The operator can never acknowledge this alarm! Information about reengineering can be found under: Note about reset_ack Keywords for the Note about reset_ack: If reset_ack wasn't set globally, the AQUIT output behaved according to the purple diagram (AQUIT2) in Figure 22. If reset_ack was set globally, the AQUIT output behaved according to the green diagram (AQUIT1) in Figure 22. The common handling of project parts whose logic is designed with switches and others whose logic is designed without switches was only possible with a lot of effort. The switch has now been removed in the new AlarmServer and the behavior now corresponds to the purple (AQUIT2) curve. With this, a uniform and expected behaviour is guaranteed. In APROL R 3.0, the alarm function blocks behave as they did in earlier versions without setting reset_ack! Upgrade notes 1-9 Illustration 66: reset_ack diagram If it becomes absolutely necessary to get the old behavior with a set switch, there is an applicative way to form the removed reset_ack switch. The effect of reset_ack When acknowledging, the ISQUIT output of the BALARM_EXT function block (AQUIT from the old BALARM_PRO function block) becomes a logical 1 and keeps this state until the next time the alarm occurs. The newly active alarm sets ISQUIT (or AQUIT) back to 0. Setting reset_ack allows the behavior to be modified as follows: The AQUIT output simultaneously follows each status change of an alarm. In practice this means: If an outstanding alarm is acknowledged, the AQUIT output was reset with the GONE status change. If the alarm is acknowledged only after it's gone, the signal is reset when the alarm occurs again (like without a set switch). Reproducing the old AQUIT output Create the following function block: Illustration 67: Function block for reproducing reset_ack This function block contains the following code: A3 Upgrade Notes 1-10 if ( ISQUIT != Old_IsQuit ) { if ( ISQUIT ) { AQUIT = 1; } Old_IsQuit = ISQUIT; } if ( ACTIVE != Old_Active ) { if ( Old_Active ) { AQUIT = 0; } else { if ( AQUIT ) { AQUIT = 0; } } Old_Active = ACTIVE; } Old_IsQuit and Old_Active are local PVs of type BOOL with an initialization value of 0. The ACTIVE and ISQUIT inputs are connected to the BALARM_EXT outputs of the same name. The AQUIT output corresponds to the BALARM_PRO pin with the same name and acts according to the set reset_ack switch. F) UNICODE capability in new UCB blocks and Python applications Note: The UCB function blocks supplied by B&R in the libraries, and possible Python applications in the graphic blocks, correspond to the UTF-8 syntax. Converting the UCB function blocks and scripts present in your caedb to UTF-8 takes place automatically by executing the AprolUpdateEngin_R30 script. An additional conversion only has to take place for scripts in the file system. In addition to the UTF-8 conversion, all Python scripts need to be changed (as described under ToDo). These changes generally need to be noted if you want to create new UCB function blocks or scripts. ToDo !: Each script (shell, Python, etc.) must have after the first line. If you are programming graphic blocks with Python and editing strings on the pins, you have to note the UFT-8 encoding here as well: Reading in a string: var = os.environ["IN"]; must be followed by var = unicode( var,"utf-8"); or in var = unicode( os.environ["IN"], "utf-8"); are changed. Reading out a string: print "OUT = " + var; must be changed to print "OUT = " + var.encode("utf-8"); Upgrade notes 1-11 G) Alarm function blocks for the new alarm and message system The BALARM_PRO function block has been gone since R 2.4 and replaced by BALARM_EXT. Both of these function blocks have now been replaced with the new AprCcAlarm function block in the APROL CAE library. You can continue using the old function blocks, but they should be replaced relatively soon. The following pin names have been adjusted in the course of this changeover: Old pin name New pin name AON ON AMODE MODE APRIO PRIO ALA2PIC PICTURE TXTPARx AVALUEx SCHEME Dropped QUIT (IN) New pin QUITTEXT (IN) New pin QUIT ISQUIT (OUT) The value for alarm logging now uses the ANY data type, which allows text values for alarms and constants to be recorded now as well. ToDo !: Since the SCHEME pin is no longer used, the printer configuration needs to be revised. Now that the ISQUIT (previously QUIT) output pin has unambiguous way of working, you have to do some reengineering if RESET_ACK was used with the AlarmServer. Exchange the BALARM_PRO function block with AprCcAlarm, revise the engineering, and consequent preparation of APROL R 3.0. H) Providing the SG4 OS version V0271 and the new hardware catalog Most current FlexIO operating system for the SG4 platform. Known bugs corrected. Support of new HWCs with the preparation for AR I/O. ToDo !: For all SG4 target controllers, the new default V0271 OS must be used. Check the I/O configuration in all of the controllers since the channel assignments (name instead of number) and channel configurations (measuring ranges) have changed with the use of the new HWC. A3 Upgrade Notes 1-12 After the controllers have been revised in their engineering, they need to be enabled and compiled. I) Providing the SG4 OS version V0280 New operating system for the SG4 targets with the AR I/O system. Support for new configuration properties (like in Automation Studio) for I/O modules in APROL. Support for diagnostic functions for I/O modules. ToDo !: Carry out the update to the new V0280 OS for all SG4 target controllers that will be using AR I/O. Configure the I/O module underneath the Module Properties item. Check the I/O configuration since the channel assignments (name instead of number) and channel configurations (measuring ranges) have changed with the use of the new HWCs. After the controllers have been revised in their engineering, they need to be enabled and compiled J) Scripts for APROL / standardization In the course of developing R 3.0, the name specifications for APROL scripts was standardized. General prefix: Aprol Subdivided by function into: Config, Update, Report, Select, Start, Install, Create Because of this, the names of almost all of the scripts have changed. Function: Config (affects the configuration) General: AprolConfig Function: Update (affects the start of an update) General: AprolReport Function: Start (affects the start of an application) General: AprolStart Function: Create (affects e.g. the creation of a system) General: AprolCreate Special: AprolPrintScreenshot in AprolPrintScreenShot AprolBackupEnginContent ShowAprolSystems ToDo !: Check your scripts for use in UCB functions. Check the script names for use in the DisplayCenter toolbar. Check your global or centralized Python files for the use of these scripts. Check the script names in the corresponding system launches. K) Checking all files (used from MS Windows) for UTF-8 conformity Note: The majority of files taken from MS Windows do not conform to the UTF-8 standard. These have to be converted. If this is the case for you, use the iconv command in Linux. iconv -f WINDOWS-1252 -t utf-8 L) Deleting old communication function blocks The devil automatically detects physical view transfers to function switch plans. The designer no longer needs to make the entry for physical view transfers. Support for diagnostic functions for I/O modules. Note: Old projects converted from APROL 1.5 (APROL i) may still include these old communication function blocks in some circumstances. They were discontinued in R 2.0. These communication function blocks are no longer supported in APROL R 3.0 and are reported as errors. ToDo !: All plans in projects engineered with the versions of APROL mentioned above must be checked for this function blocks. A3 Upgrade Notes 1-14 Configure the I/O module underneath the Module Properties item. Check the I/O configuration since the channel assignments (name instead of number) and channel configurations (measuring ranges) have changed with the use of the new HWCs. After deleting, the resulting lugs must all be connected. M) Adapting the graphics format (static process graphics, graphic blocks) The graphics format has been expanded to include V10. It now contains new functions. Note: APROL graphics that are in caedb are converted automatically by the CaeManager during its first start in APROL R 3.0. Graphics that are held as templates in the file system (GRAPHIC_TEMPLATES) must be converted separately. Before being converted, these graphics must contain V9 graphics format from R2.4-04 that has been current until now. Attention: When imported or loaded, pictures or templates are checked for the correct format and whether they are UNICODE-capable. If this check comes up negative, these graphics are not imported and an error message is output. ToDo !: These files need to be converted to UNICODE using the AprolConvertFileToUtf8 script. The graphics must be brought over to V10 format using the AprolConvertGrafikToV10 script. N) Changing the trend widget for a dynamized (animated) display of trends in process graphics The trend time Y of 1 variable (Trend) and trend time Y of 4 variables (TrendMulti) widgets have been replaced by the powerful Online trend of several variables (OnlineTrend) widget. During a database update (after the upgrade to R 3.0), the trend widgets mentioned above are automatically replaced by the new trend widget (OnlineTrend). At the same time, configuration parameters are set according to the new trend widget. ToDo !: The configuration parameters must be checked and set according to the engineering. Example: Scaling can now be done in three different ways: automatically, manually, and dynamically. Scaling is done by the widget itself. If there is a static scaling in the image macros, or in the static process graphics, they need to be removed. Upgrade notes 1-15 If the PIC_SCALE function block (now in APROL/ControlComputerFunctions/AprCcPicScale) lies on the connection line to the trend's graphic block (input pins for the individual trends), this results in it being overwritten by the AprCcPicScale function block configuration when the scaling is configured automatically. 1.49 Converting a system's runtime data to UTF-8 1.49.1 Parameter data conversion In order to integrate the existing parameter data in APROL R 3.0, it is absolutely necessary to save this data in APROL R 2.4, and after upgrading to APROL R 3.0-01, or higher, to import it as UTF-8 conform. The two scripts AprolExportParameterMgmt_24 and AprolImportParameterMgmt_R30 are available for this purpose. Export the parameter data in APROL R 2.4 with the script AprolExportParameterMgmt_R24 or alternatively via AprolImportParameterMgmt_R30: Carry out the following steps only on the master when a MYSQL database that is set up for redundancy. Log into the APROL system that has the MYSQL database as root. Make sure that the MYSQL database is running. Export the parameter data with the command AprolExportParameterMgmt_R24.py -- export= In order to guarantee a smooth conversion, carry out the upgrade to APROL R 3.0- 01 or higher. UTF-8 conversion and parameter data import into APROL R 3.0 via AprolImportParameterMgmt_R30: Carry out the following steps only on the master when a MYSQL database that is set up for redundancy. Make sure that a replication is set up and running between master and slave. A3 Upgrade Notes 1-16 Log into the APROL system that has the MYSQL database as root. Make sure that the MYSQL database is running. Copy the saved TAR archive to the server Import the parameter data with the command AprolImportParameterMgmt_R30.py -- import= 1.49.2 Backup historical data These steps only have to be carried out before updating the Runtime system if it is desired that the historical logging and alarm data are transferred to APROL R 3.0. If historical TREND data should be applied, it's required that it be migrated to the new ChronoLog trend format with the MigrateOldTrendDatabase script! Additional information can be found in the Trend Migration R 2.4-04 manual. 1.49.2.1 Backing up Runtimes system data in R 2.4-04 This step must be carried out by the root user on the server in R 2.4-04! Backing up the Runtime system in APROL R 2.4-04 is done using the AprolBackupRuntime_R24 script. This script stores all of the alarm, trend, and logging data needed for the lazy Runtime system in a TAR archive. Command: AprolBackupRuntime_R24 –path /tmp –system Backing up ChronoLog data The following ChronoLog identifiers are backed up: USERACTION: in the audittrail.txt file M1: in the fast.txt file M2: in the slow.txt file If additional ChronoLog identifiers should be backed up, they have to be entered in the ADD_CLC_IDENT environment variable in the form CHRONOLOGCONTAINERNAME- CHRONOLOGIDENTIFIER. Example: export ADD_CLC_IDENT="customer-CUSTOMER1 customer2-CUSTOMER2" This backs up all entries with CUSTOMER1:* in the file customer.txt and CUSTOMER2:* in the file customer2.txt. Upgrade notes 1-17 All ChronoLog containers in the Web server's ARCPATH are searched. An additional path can be specified in ADD_ARKPATH. Backing up alarm data The alarm data from the Runtime system being backed up is included in the backup. The Runtime system environment is analyzed during this procedure. A correct RAIMA environment is absolutely required! Backing up ChronoTrend data All trend data on the Runtime system that can be reached via the ARKPATH is backed up. 1.49.2.2 APROL R 3.0 – Installing the runtime server Install the Linux 9.3 SUSE distribution version from the AutoYaST installation DVD. Install APROL R 3.0 from the System Software DVD. Basic configuration of the Runtime systems with the same name used in APROL R 2.4-04. 1.49.2.3 Backing up Runtime system data in R 3.0 This step must be carried out by the root user on the prepared server in R 3.0! Bring in and convert the backed up runtime data with the AprolRestoreRuntime_R24 script. This copies the TAR archive created above to a directory (e.g. /tmp) and launches the script. Command: AprolRestoreRuntime_R24 -backupfile /tmp/ A3 Upgrade Notes 1-18 A3-2 Appendix . 2.1 Revision history Manual version Date Change Author / checked by: 3.09 23.09.2014 Limitations dropped. Use of the RN APROL event-link mechanism on MHa a redundant controller and Rotary switch setting for controllers 22.09.2014 New chapter Changes in the RN 'MonCtrlCpuRed01' hyper macro EM 24.09.2014 New chapter New features after KSc updating to APROL R 4.0-08 3.08 20.08.2014 New chapter New features after KSc updating to APROL R 4.0-07 JR Update of chapter Limitations in the current APROL release 3.07 02.07.2014 New chapter New features after KSc updating to APROL R 4.0-06 3.06 13.06.2014 Update chapter Access of RN Historical Data via SQL 05.06.2014 Update of Controller AR-OS KSc versions 26.05.2014 New chapter Selecting an APROL RN system in the ParameterCenter MHe 22.05.2014 New chapter New features after KSc updating to APROL R 4.0-05 IS 3.05 05.05.2014 New chapter 'Self ID for embedded KSc applications' MG 30.04.2014 New chapter Communication with a KSc redundant controller via ANSL New chapter Replacement of APROL-specific constants from the 'runtime' AS library Appendix 2-1 Manual version Date Change Author / checked by: 29.04.2014 Chapters Diagnosis of the buffering RN, KSc of logging data, Configuration HSc, EL, MHa redundanter Controller and Use of PROFIBUS I/Os in redundant controllers dropped (limitations lifted). 25.04.2014 New AR-OS version H0406 KSc 24.04.2014 New chapter New features after KSc updating to APROL R 4.0-04 3.04 16.04.2014 Chapter AutoYaST DVD V4.0-030 RN update MS 04.04.2014 Chapter Activating SFCs dropped KSc 3.03 31.03.2014 New chapter Diagnosis of the KSc buffering of logging data SO, HSc 3.02 07.03.2014 New chapter New features after KSc updating to APROL R 4.0-02 3.01 06.02.2014 New chapter New features after KSc updating to APROL R 4.0-01 MHe 3.00 26.11.2013 Formatting to DIN A4 & fonts RN 18.11.13 Update of chapter Controller AR- KSc OS versions 14.11.2013 Extension of chapter New features KSc after updating to APROL R 4.0-00 MHE, JO, GW 02.10.2013 New chapter BuR Gateway RN connection 29.07.2013 New chapter Controller AR-OS RN versions 26.03.2013 Change of minimum release to KSc R 3.6-06 19.03.2013 New chapter Update to the current RN AutoYaST version 21.09.2012 New chapter Minimum release for RN an upgrade to APROL R 4.0-00 04.09.2012 Revision of terms (APROL KSc system/CC-Account) 14.05.2012 Introduction of chapter KSc New chapter New features after updating to APROL R 3.6-08 22.03.2012 New chapter New features after KSc updating to APROL R 4.0-00 24.01.2012 New chapter New features after KSc updating to APROL R 3.6-07 2.12 23.01.2012 New chapter New features after KSc updating to APROL R 3.6-07 A3 Upgrade Notes 2-2 Manual version Date Change Author / checked by: 2.11 21.10.2011 New chapter New features after KSc updating to APROL R 3.6-06 2.10 07.07.2011 Update of chapter New features KSc, RN after updating to APROL R 3.6-05 2.09 06.04.2011 Update of chapter Controller AR- KSc, RN OS versions 2.08 28.03.2011 Update of chapter New features KSc after updating to APROL R 3.6-04 18.02.2011 Extension of chapter Change of the RN unit and IEC type of system IS variables for memory evaluation with FreeAPROLDATASpace 2.07 15.02.2011 Update of chapter New features KSc after updating to APROL R 3.6-03 2.06 09.02.2011 New chapter Use of the process KSc graphic preview AT 07.02.2011 New features after updating to KSc APROL R 3.6-03 JRu 2.05 24.09.2010 New features after updating to KSc APROL R 3.6-02 JRu, MT 12.08.2010 Revision of terms: ST, SFC, CFC RN 2.04 05.08.2010 New features after updating to KSc APROL R 3.6-01 JR, AT 2.03 07.07.2010 Update of chapter New features KSc after updating to APROL R 3.6 ELa 2.02 01.07.2010 Update of chapter New features KSc after updating to APROL R 3.6 MT, PS 2.01 12.05.2010 Revision of chapter New features RN / KSc after updating to APROL R 3.6 AT 2.00 18.09.2009 New features after updating to KSc APROL R 3.6 EM, RS, DD 1.01 20.02.2009 New features after updating to KSc APROL R 3.4-04 1.00 23.01.2009 New features after updating to KSc, RN APROL R 3.4-03 File name of this documentation: APROL_R40_A3_UpgradeNotes_001.pdf Appendix 2-3 2.2 Document information Document version: ManVersion 3.09 Document date: ManDatum 23.09.2014 A3 Upgrade Notes 2-4 Appendix 2-1
tag. Tag
tag in 'die'. Radio button: Example configuration: