Resources|Blog|FTSolution for APT|FTSolution for APT v2.2.0 Release Notes

Posted: 11/26/2019

Features

  • Line numbers are now shown in the source Code Behind.
  • Added new reports including:
    • 505 and Profibus I/O Modules – lists information on both 505 and Profibus I/O
      • The 505 report includes information about all configured Channels, Bases, Slots and Positions
      • The Profibus report includes information on all configured Profibus Slaves
    • Sequential Function Chart (SFC)  – includes lists of all Steps and Transitions, their SFC cell locations, and their source Code Behind
    • Continuous Function Chart (CFC) – lists all Cyclic Function Blocks (CFB) with their Names, Type, Description, Inputs, Outputs, and source Code Behind
    • Subroutine Table – lists subroutines, including their Names, Types, Descriptions, Inputs, Outputs, and source Code Behind settings for each CFB
    • Recipe Template – includes the list of Recipe Templates and their recipe elements
    • Configuration – lists all program configuration settings
    • Process Groups – lists all Process Groups
    • Watch – lists Watch File settings, like address, Scope and Format
    • Communication Setup – lists the Communication Settings

Solutions

  • Configuration Editor
    • Fixed ‘There was an error generating the XML document’ error preventing user from saving a configuration file when configured for SIMATIC 560, 565 or 565P controller type.
    • Required Applications, Optional Applications and Mode-Locked Applications settings of SIMATIC 575 controller type configuration no longer accept an invalid input. If any characters other than letters are entered into any of Applications Dependencies settings, ‘Enter the appropriate application letters next to each other, without spaces’ error will be shown to user.
    • The SIMATIC 555 controller configuration Special Memory setting ‒ that previously allowed values up to 1,949,696 ‒ has been changed not to accept a value greater than 999,999. The CTI 2500 controller configuration Special Memory setting ‒ that previously allowed values up to 974,848  ‒ has been changed not to accept a value greater than 999,999. If user enters a value greater than 999,999 into Special Memory configuration setting of either SIMATIC 555 or CTI 2500 controller, ‘Reserved S-Memory must be 0 – 999,999 words.’ error will be shown to user.
    • The SIMATIC 545 controller configuration Special Memory setting ‒ that previously allowed values up to 1,032,192 ‒ has been changed not to accept a value greater than 999,999. The SIMATIC 575 controller configuration Special Memory setting ‒ that previously allowed values up to 417,792 ‒ has been changed not to accept a value greater than 942,080. If user enters a value greater than 999,999 into Special Memory configuration setting of SIMATIC 545 controller, ‘Reserved S-Memory must be 0 – 999,999 words.’ error will be shown to user. If user enters a value greater than 942,080 into Special Memory configuration setting of SIMATIC 575 controller, ‘Reserved S-Memory must be 0 – 942,080 words.’ error will be shown to user.
    • The Reserved Locations Role Swap setting of SIMATIC 560 controller configuration ‒ that previously allowed values up to 32,768 ‒ has been changed not to accept a value greater than 16,384. If user enters a value outside of 0…16,384 range into Reserved Locations Role Swap setting of SIMATIC 560 controller configuration, ‘Reserved role swaps must be 0 – 16,384.’ error will be shown to user.
    • Fixed the error of Reserved Locations Role Swap setting not showing in SIMATIC 565, 545 and 565 controller type configurations.
    • Changed the default value for Reserved Locations Report By Exception setting from 0 to 20: the minimum amount of memory (Kbytes) needed.
    • The SIMATIC 545 controller configuration Reserved Locations Report By Exception setting ‒ that previously allowed values up to 384 ‒ has been changed not to accept a value greater than 192. The SIMATIC 555 controller configuration Reserved Locations Report By Exception setting ‒ that previously allowed values up to 1,920 ‒ has been changed not to accept a value greater than 384. The SIMATIC 575 controller configuration Reserved Locations Report By Exception setting ‒ that previously allowed values up to 2,048 ‒ has been changed not to accept a value greater than 320. If user enters a value greater than 192 into Reserved Locations Report By Exception configuration setting of SIMATIC 545 controller, ‘Reserved RBE must be between 0 KB and the controller’s memory size.’ error will be shown to user. If user enters a value greater than 384 into Reserved Locations Report By Exception configuration setting of SIMATIC 555 controller, ‘Reserved RBE must be between 0 KB and the controller’s memory size.’ error will be shown to user. If user enters a value greater than 320 into Reserved Locations Report By Exception configuration setting of SIMATIC 575 controller, ‘Reserved RBE must be between 0 KB and the controller’s memory size.’ error will be shown to user.
    • Fixed errors in upper limits of Reserved Locations Nonretentive Control Relays values of SIMATIC 560T or 565P controller configurations:
      • When Number of RCC Cards is set to 1, the Nonretentive Control Relays setting value ‒ that previously allowed values up to 47,615  ‒ has been changed not to accept a value greater than 47,616.
      • When Number of RCC Cards is set to 2, the Nonretentive Control Relays setting value ‒ that previously allowed values up to 49,151  ‒ has been changed not to accept a value greater than 49,152.
      • When Number of RCC Cards is set to 3, the Nonretentive Control Relays setting value ‒ that previously allowed values up to 50,687  ‒ has been changed not to accept a value greater than 50,688.
      • When Number of RCC Cards is set to 4, the Nonretentive Control Relays setting value ‒ that previously allowed values up to 52,223  ‒ has been changed not to accept a value greater than 52,224.
    • Fixed errors in upper and lower limits of Reserved Locations Retentive Control Relays values of SIMATIC 560, 560T, 565, 565P, or 565T controller configurations:
      • When Number of RCC Cards is set to 1, the Retentive Control Relays setting value ‒ that previously allowed any values up to 999,999  ‒ has been changed not to accept a value greater than 512.
      • When Number of RCC Cards is set to 2, the Retentive Control Relays setting value ‒ that previously allowed values up to 999,999  ‒ has been changed not to accept a value greater than 1,024.
      • When Number of RCC Cards is set to 3, the Retentive Control Relays setting value ‒ that previously allowed values up to 999,999  ‒ has been changed not to accept a value greater than 1,536.
      • When Number of RCC Cards is set to 4, the Retentive Control Relays setting value ‒ that previously allowed values up to 999,999  ‒ has been changed not to accept a value greater than 2,048.
    • The Reserved Locations U-Memory setting of SIMATIC 575 controller configuration ‒ that previously allowed values up to 417,792 ‒ has been changed not to accept a value greater than 942,080. The error message for U-Memory value outside of allowed range ‒ that previously reported an error in S-Memory, instead of U-Memory: ‘Reserved S-Memory must be 0 – 417,792 words.’ ‒ has been changed to ‘Reserved U-Memory must be 0 – 942,080’.
    • The SIMATIC 575 controller configuration Reserved Locations Ladder setting ‒ that previously allowed values up to 139,264  ‒ has been changed not to accept a value greater than 314,368. If user enters a value greater than 314,368 into Reserved Locations Ladder configuration setting of SIMATIC 575controller, ‘Reserved ladder  must be 0 – 314,368 words.’ error will be shown to user.
    • The SIMATIC 575 controller configuration Reserved Locations Variable setting ‒ that previously allowed values up to 418,304  ‒ has been changed not to accept a value greater than 942,592. If user enters a value greater than 942,592 into Reserved Locations Variable configuration setting of SIMATIC 575controller, ‘Reserved ladder  must be 0 – 942,592 words.’ error will be shown to user.
    • The SIMATIC 575 controller configuration Reserved Locations Constant setting ‒ that previously allowed values up to 942,080  ‒ has been changed not to accept a value greater than 974,848. If user enters a value greater than 974,848 into Reserved Locations Constant configuration setting of SIMATIC 575 controller, ‘Reserved ladder  must be 0 – 974,848 words.’ error will be shown to user.
    • Fixed the error of allowing negative values in Reserved Locations Retentive and Nonretentive Control Relays settings.
  •  Debug
    • .CLS extension of VSS Valve device set to Energize to Close is no longer missing from the device’s Monitor.
  • Full Compile
    • Fixed the “Unable to create memory configuration, S memory is larger than configured” error shown when user compiles a project in which a configuration has been changed from the controller type that allowed Special Memory setting (but the value of the setting exceeds maximum allowed), to the controller in which Special Memory does not apply.
    • Internal compiler error “Index was outside the bounds of the array” is no longer showing when user compiles a project in which the number of RCC cards is configured to exceed maximum allowed, 4.
    • Internal compiler error “The U-Memory file name does not exist” is no longer showing when user compiles a project in which a configuration has been changed from the controller type that allowed U-Memory setting (but the value of the setting is either a file with an invalid extension, .rec, or a name of non-existing file), to the controller in which U-Memory does not apply.
    • Internal compiler error “Arithmetic operation resulted in an overflow” is no longer showing when user compiles a project in which the number of RCC cards is configured to less than minimum allowed, 1.
    • Compiler error “Unable to resolve the symbol reference” is no longer given when compiling a project which contains symbols that match in name, but not in scope.
    • Fixed the error of generating non-retentive addresses for Safe-State SFC Steps.
    • Fixed the error of generating non-real addresses for real temporary variables.
    • Fixed rounding error when calculating a result of mathematical expression that includes division.
    • Fixed the error of generating C-type addresses instead of V-type addresses for SFC Steps marked with Pragma(“SF”) and including MATH INIT section.
  •  PCS
    • Deadband, Low range and High range settings are no longer invisible in Mark PCS Tags dialog.
  • Profibus I/O
    • The Host Type of Profibus I/O Master in 505 IO Modules.amod project file is now showing the actual controller type and release, as set in project configuration, while before it was always showing “555-1104”.
  •  Report
    • Fixed the error “Sequence contains no elements” showing when generating reports on a project folder that contains no files.
  • Solutions Management
    • Fixed the error of software crashing when editing a source file in a project that has been renamed while the source file was open.
    • Fixed “Sequence contains more than one element” error shown when user compiles a project in which a unit has been removed and then re-added as an existing item in the same application session.
    • Fixed “A generic error occurred in GDI+” error shown when user deletes a large (80 or more) number of files at once.
    • Fixed “The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters” error shown when user adds, removes and then re-adds a unit as an existing item, without closing or saving the project in between.
    • Fixed “The document ‘unit master file’ path is already open as a project or a solution and cannot be opened in an editor at this time” error shown when user removes and then re-adds a unit as an existing item, without closing or saving the project in between.
    • Fixed “Cannot add file – a duplicate object has been detected” error shown when user excludes from the project  and then re-adds as an existing item an SFC, CFC, Subroutine or Recipe Template as an existing item in the same application session.
    • Fixed the following errors resulting from the renaming of a project: the project name being unchanged in project configuration and not available for use in the project’s source code behind files.
    • Fixed the error resulting from the renaming of a project that project files are prompted to be saved in the old, before the rename (and no longer existing) project’s local directory.
    • Fixed the error of project name in project configuration being changed to the name of the project’s unit when that unit has been renamed.
    • The user is now able to rename a unit of a project that has been renamed. The folder with the old unit name – that was left in the project directory – is now deleted as a result of successful rename of the unit.
    • A CFC or SFC can now be renamed by the user, without corrupting solution.
    • A Subroutine can now be renamed by the user, without corrupting solution.
    • Fixed the error of software crashing when user loads FTVersionTrak-controlled solution, in which the user previously chose to rename a repository-controlled project, but cancelled the operation in the Check Out dialog.

Contact Sales