Author: Ethan Wilke

FTSolution for APT v2.2.1 Compile Information

After installing FTSolution for APT 2.2.1, upon opening a solution/project that was compiled (full/incremental) with a prior version, the compiled object file will be automatically checked and updated, if necessary, with the compile structures that fix the issues outlined below. For programs that have been fully or incrementally downloaded using a version prior to 2.2.1, an incremental download will be required after the object file upgrade is finished. A full download is recommended when possible but not required.
Error in Define Loop Most/Least Sign Instruction
dw %%LCFH  { Loop Most Sign.  C-Flags Word. }dw %%LCFL  { Loop Least Sign. C-Flags Word. }

This instruction is used to define PID Loops and  Analog  Alarms.
An incorrect value has been used for Loop Most Sign (C-Flags Word) and Loop Least Sign (C-Flags Word) used for defining PID Lops and Analog Alarms.
The Define Loop Most/Least Sign instruction has been generated incorrectly by compiling in software version prior to 2.2.1for the following CFB types:
    • A Feedforward Output Adjust CFB, if its Process Variable has been assigned a variable.
    • A On/Off CFB, if its Process Variable has been assigned a variable.
      • A Dual Mode CFB, if either
      • A Bipolar Scaled Integer variable has been assigned to its Output Name attribute.
    • Its Process Variable has been assigned a variable.
    • A Dead Time Compensator CFB, if either
      • A Bipolar or 20% Offset Scaled Integer variable has been assigned to its Output Name attribute.
      • Its Process Variable has been assigned a variable.
  • A Feedforward Setpoint Adjust CFB, if either
    • A Bipolar or 20% Offset Scaled Integer variable has been assigned to its Output Name attribute.
    • Its Process Variable has been assigned a variable.
  • A PID Loop CFB, if either
    • A Bipolar or 20% Offset Scaled Integer variable has been assigned to its Output Name attribute.
    • A Bipolar or 20% Offset Scaled Integer variable has been assigned to its Process Variable.
Error in Define Loop Process Variable High/Low Limit Instruction
dw %%LPVH  { Loop Process Variable High Limit. }
dw %%LPVL  { Loop Process Variable Low Limit. }
This instruction is used to define PID Loops and  Analog  Alarms.
The Define Loop Process Variable Low/High Limit instruction has been generated incorrectly by compiling in software version prior to 2.2.1 for Ratio Station CFB when:

  • A Scaled Integer is used as Process Variable of Ratio Station, an incorrect value was used for Loop Process Variable Low Limit.
  • A Process Variable of Ratio Station is set to a Scaled Integer, an incorrect value was used for Loop Process Variable High Limit.
Error in Unscale Instruction
unscale (parameter1, parameter2, parameter3,  parameter4, parameter5);
This instruction is used to Scale to Engineering Units.
The Unscale instruction has been generated incorrectly by compiling in software version prior to 2.2.1 for:

  • A Feedforward Output Adjust CFB, if its Output has been assigned to a Bipolar or 20% Offset Scaled Integer.

FTSolution for APT v2.2.1 Release Notes

Compile Information

Solutions

  • Configuration Editor
    • The Reserved Locations Role Swap setting of the SIMATIC 560 and SIMATIC 565 controller configurations  ‒ that previously allowed values up to 32,768 ‒ has been changed to not accept a value greater than 16,384. If a user enters into the Reserved Locations Role Swap configuration setting of SIMATIC 560/565 controller a value greater than 16,384, the ‘Reserved role swaps  must be 0 – 16,384.’ error will be shown to the user.
    • In programs configured for CTI 2500 controller type, the maximum number of words allowed for Special Memory Reserved Locations was 999,999, when it should have been  1,949,696. If user enters a value greater than 1,949,696 into the Reserved Locations Special Memory configuration setting of CTI 2500 controller, ‘Reserved S-Memory  must be 0 – 1,949,696 words.’ error will be shown.
    • In programs configured for SIMATIC 555 controller type, the maximum number of words allowed for Special Memory Reserved Locations was 999,999, when it should have been  1,949,696. If user enters a value greater than 1,949,696 into the Reserved Locations Special Memory configuration setting of CTI 2500 controller, ‘Reserved S-Memory  must be 0 – 1,949,696 words.’ error will be shown.
    • In programs configured for SIMATIC 545 controller type, the maximum number of words allowed for Special Memory Reserved Locations was 999,999, when it should have been  1,032,192. If user enters a value greater than 1,032,192 into the Reserved Locations Special Memory configuration setting of CTI 2500 controller, ‘Reserved S-Memory  must be 0 – 1,032,192 words.’ error will be shown.
    • In configurations of the controller types that include Report by Exception settings, its minimum value has been changed from 20 to 0. With this change, user no longer will receive an error “Reserved RBE must be between 0 KB and the controller’s memory size”, if the configured memory size is less than 20 KB.
    • In programs configured for CTI 2500 C400 ≥ 8.01 controller type, Nonretentive Control Relays Reserved Locations setting  has been changed to not accept a negative value. If user enters a negative value into the Reserved Locations Nonretentive Control Relays configuration setting of the CTI 2500 C400 ≥ 8.01 controller, ‘Reserved nonretentive CRs must be 0 – 28,672.’ error will be shown to user.
  • Full Compile
    • Fixed the error of incorrect instructions being generated for Ratio Station, Dual Mode, Dead Time Compensator, Feedforward Output Adjust, and On/Off, when Process Variable is set to Analog Input that has No Scaling checked.
    • Fixed the error of Sub Type of a Scaled Integer not being assigned correctly in UNSCALE instruction generated for Feed Forward Output Adjust CFB with the Process Variable being set to a Scaled Integer declaration of either Bipolar or 20% Offset.
    • When a Scaled Integer is used as Process Variable of Ratio Station, an incorrect value was used for Loop Process Variable Low Limit.
    • When Process Variable of Ratio Station is set to a Scaled Integer, an incorrect value was used for Loop Process Variable High Limit.
    • An internal compiler error “No active default available for extension” will no longer be shown when user compiles a project in which a declaration of type Flag is set to have an invalid (for example, negative) value. With this fix, the error reported to the user includes the name and type of the declaration. Double click on the error will open the Declaration file containing the declaration with an invalid value reported in the error.
    • An incorrect value has been used for Loop Most Sign (C-Flags Word) and Loop Least Sign (C-Flags Word) used for defining PID Lops and Analog Alarms. The value of the Loop Most Sign has been fixed for On/Off, Dead Time Compensator, Dual Mode, Feed Forward Output Adjust, Feed Forward Setpoint Adjust when the Process Variable is set to a Scaled Integer of Sub Type 20%. The value of the Loop Least Sign has been fixed for On/Off and Dual Mode, when the Process Variable is set to a Scaled Integer of Sub Type Bipolar.
    • The “Invalid Mix of RLL and SF code” compiler error has been updated to include the name of the SFC block in which an invalid mix of RLL and SF code has been found, as well its first line number inside the code behind SFC file containing the block. With this fix, if user double-clicks on the error message, the SFC code behind source file containing the error will be open and the focus will be placed on the first source line of the code block causing the error.
  • I/O Symbol Editor
    • Only V type of address is permitted for the Reserved Address of Analog Input. Previously,
      • If user entered a WX address into Reserved Address of Analog Input and compile a program, the “Error validating address %WX: Unknown counter type WX.” error was shown. However, if the value of Reserved Address was left blank, or user entered any address other than V, the error stating  “Expected: V address or WX address.” was shown to the user.
      • When user compiled the program with WX type of address entered into Reserved Address, the compilation failed with error “Validation error objectname, setting “Reserved Address”: Error validating address %WX: Unknown counter type WX.”
    • The error has been corrected to state that only V addresses are allowed for the Reserved Address of Analog Input : “Expected: V address.”
  •  Import
    • Active Math CFBs can be tagged in APT, but no tags are generated for them. In FTSolution, Active Math CFBs cannot be tagged, however, the tags of Active Math CFBs has been imported from APT, causing compiler errors. With the fix to this defect, the tags of Active Math CFBs are no longer imported from APT.
    • Previously, the controller name has been left blank when importing an APT program. Controller name is now imported from APT.
  •  PCS
    • Previously, the Low Range and High Range values of a Process Variable were ignored in generation of tag records of tag files (Install.tag and Append.tag), and 0 value was used for Initial Value instead. The error was found in the CFBs of the following types: On/Off, Analog Alarm, Dual Mode, Dead Time Compensator, PID, Ratio Station, Feed Forward Setpoint Adjust, and Feed Forward Output Adjust. With the fix to this defect, the Low Range and High Range values of a Process Variable are now used for the Initial Value of the tag.
  • Profibus I/O
    • User will no longer experience an application crash when selecting to View Parameters of a Smart Connect Secondary Slot.
  •  Report
    • Only programs configured for SIMATIC 575 controller type show Application ID setting, however, previously, a Configuration report generated for a program configured for any controller type included the Application ID setting. With the fix to this error, Configuration report generated for SIMATIC 575 controller type only will include the Application ID setting.
    • Previously, in a  program configured for a controller type that does not include Scan Type and/or Total Scan Time settings, these settings were included in Configuration report. With the fix to this error, Configuration report includes Scan Type and/or Total Scan Time settings only if the program for which the Configuration report is generated, is configured for a controller type that includes these settings.
    • Previously, the Profibus I/O Detailed Report did not include odd-numbered I/O Module Slots. With the fix to this error, all Slots are included in the report.

FTSolution for APT V2.2.1 Release

FasTrak SoftWorks, Inc. is pleased to announce the release of FTSolution for APT V2.2.1. FTSolution for APT is a Microsoft Windows-based direct replacement for Siemens-obsoleted DOS APT software designed to extend the life of Siemens and CTI 2500 Series PLCs and APT programs.

FTSolution for APT V2.2.1 incorporates:

  • Ability to display line numbers in the source Code Behind
  • New reports for:
    • 505 and Profibus I/O Modules
    • Sequential Function Chart (SFC)
    • Continuous Function Chart (CFC)
    • Subroutine Table
    • Recipe Template
    • Configuration
    • Process Groups
    • Watch
    • Communication Setup
  • Other performance improvements

View release details

Purchase FTSolution for APT to take full advantage of this, and future, enhancements. Purchase includes a warranty offering 12 months of free updates and technical support.

FTSolution for APT v2.2.0 Release Notes

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.

FTVersionTrak for APT v2.1.0 Release Notes

Features

  • The Comments of the most recent file versions now appear in the File list.
  • Updating Folders and Files lists is greatly improved.
  • The FTVersionTrak comparison feature compares and reports on the selected Project folders and files only. Other folders and files are excluded from this operation.

Solutions

  • Application Window
    • Added a warning to user about missing email address of  SMTP Server Sender: “SMTP Sender User Email Account is blank. Email notifications will not be sent or received”. The warning is shown when a user with a repository permission to configure SMTP Server opens Email Setup dialog.
    • Fixed an error of new name of an email template not being saved, when user makes no other changes to the email template, besides renaming.
    • Corrected the display of a user name in a warning shown when a user that has no repository email account opens Attach/Detach Notifications to a folder dialog.
    • Updated the error shown to user when saving an email account with an empty email address to be more specific: “Could not save Email Account. Email Address must be in the format of “jsmith@example.com”. It must be less than 256 characters. It may not contain any of the following characters:\\ / : * ? ‘ ” <> | ~ { } [ ] ;”
  • File System Operations
    • Fixed the error of working directory being incorrectly set for the subfolders of a folder for which a specific local path has been set as a working directory.
    • Fixed an error of allowing user to create a repository folder with a name that contains  @ symbol or an apostrophe. If user selects such a name for a repository folder, the following error will be shown:  “Invalid repository folder name. The name contains invalid characters.  The following characters are considered invalid: @ \ / : * ? ‘ ” <> | ~ { } [ ] ;”
  •  Help
    • Fixed “DataGridViewComboBoxCell value is not valid” error when using a deleted device in MBX Bridge Mapping.
    • Fixed an error of not giving a user an option to close the Network Setup dialog without saving when the changes to Network Setup made by a user are invalid.
    • Fixed “User does not have permission to perform this action” error received when repository SQL user with the permissions to manage repository permissions of other users updates repository permissions of another repository user.
    • Added an error to be shown when a user makes an invalid change to Display Name in Email Settings of Repository User/Group dialog: “Display Name is in an invalid format. It must begin with the letter and may contain spaces, digits, hyphens, commas, dots and underscores”.
    • Added an error to be shown when a user makes an invalid change to Email Address in Email Settings of Repository User/Group dialog: “Email Address is in an invalid format. Email Address must be in the format of “jsmith@example.com”. It must be less than 256 characters. It may not contain any of the following characters:\\ / : * ? ‘ ” <> | ~ { } [ ] ;”
  • Scheduled Tasks
    • Fixed an error of Check Out, Undo Check Out, and Check In operations on shared repository files being incorrectly reported in the operation results dialog as skipped.
    • Fixed an error of Get operation on shared repository file to retrieve a local copy from only the first of its repository locations.
    • Fixed “Cannot retrieve the selected items” error shown when multiple repository files from different repository locations are selected in Search Results window for Get operation, and a repository folder of any of the selected repository files has no working directory.
    • Fixed an error of prompting user during Get operation to create a local directory for deleted repository folders.

FTVersionTrak V2.1.0 Release

FasTrak SoftWorks, Inc. is pleased to announce the release of FTVersionTrak V2.1.0.

Designed with the industrial user in mind, FTVersionTrak secures the files essential to your manufacturing or business process, safeguarding them from unauthorized access, accidental deletion, or loss. FTVersionTrak makes it easy to:

  • Streamline file managment
  • Simply file sharing
  • Easily control file access and track changes
  • Quickly indentify differences between PLC programs
  • Automatically back up PLC program files

New in FTVersionTrak V2.1.0:

  • The Comments of the most recent file versions now appear in the File list
  • Updating Folders and Files lists is greatly improved
  • Other performance improvements

View release details

FTVersionTrak protects your vital PLC ladder programs and integrates version control into your programming and troubleshooting practices.

PLC WorkShop Suite for 505 V5.10 Release

FasTrak SoftWorks, Inc. is committed to the long-term development, service, and support of programming software for Simatic 505 and CTI 2500 Series PLCs. Our commitment includes the release of new product versions, the continued development of PLC WorkShop for 505, continued improvement to the CTI 2500 Series line of PLCs beyond the capability of the the original Siemens 505 PLCs, and an experienced technical support staff. We are pleased to announce the release of PLC WorkShop Suite for 505 V5.10 incorporating:

  • Ability to print in color
  • Other performance improvements

With the full benefit of offline program simulation and the security of version control, PLC WorkShop Suite for 505 provides the tools and support you need to preserve your 505 programs, extend the 505 platform for years to come, and maintain production uptime.

View release details

FTVersionTrak for APT v2.0.0 Release Notes

Features

  • Integration with FTSolution
    • Solutions can be unbound from repositories.
  • Scheduled Tasks
    • More detail is included in the Scheduled Task report.
  • SQL Server
    • Added support for SQL Server 2014 and 2016.
  • Version Control Operations
    • File history can be extracted from history to a local file system working directory.

Solutions

  • File System Operations
    • Improved support to destroy folders.
    • Folders can be created when multiple instances of FTVersionTrak are running on the same computer.
  • Integration with FTSolution
    • Check in operation supports check out fields that are required but hidden when the Show Check In Options on the Tools menu is unchecked.
    • Projects or units that are renamed in FTSolution are also renamed in FTVersionTrak Repositories.
    • Renamed SFCs in FTSolution retain their original diagrams and code-behind logic in FTVersionTrak repositories.
    • Renamed CFCs in FTSolution retain their original diagrams and code-behind logic in FTVersionTrak repositories.
    • Renaming SFCs with the name of a previously deleted SFC is allowed.
    • Renaming a project or unit in FTSolution, when the Disable Rename Repository File When Working Offline option is selected, is allowed.
    • Renaming a solution in FTSolution is allowed.
    • Checking in a renamed Solution displays the Check In dialog.
    • When binding a solution without specifying a working directory, a working directory is automatically assigned and version control operations are available.
  • Multiple File Units
    • Electronic signatures for folders is supported.
    • Directory units are correctly checked back into their original folders.
  •  Reports
    • The number of reports that can be generated for a solution is now unlimited.
  • Repository Security
    • The security privileges to create and view file version states have been coordinated.
    • Adding administrator and power editor users to SQL repositories is not limited.
  • Scheduled Tasks
    • Users can stop any scheduled task that they create.
  • SQL Server
    • Repositories can be created under SQL 2014 and SQL 2016.
    • Browsing for repositories created with SQL 2014 and SQL 2016 is supported in 64-bit operating systems.
  • Version Control Operations
    • Labeling folders is supported.
    • The Sign In dialog remains open if an incorrect username/password combination is entered which allows another combination to be entered.
    • When performing a recursive check out on a folder, the warning about overwriting files in the working folder appears only for files that are not already checked out.
    • Changes to the Require All Signatures setting are retained.
    • The Checkout Results dialog appears after check out operations, regardless of whether local working copies are overwritten or retained.
    • Clearer notification is provided when attempting to edit comments in previously destroyed file versions.

FTSolution for APT v2.1.1 Release Notes

Solutions

  • Debug
    • EXTENDED extension of a Cylinder Device is now displayed correctly in Debug Mode, in Monitor: the name has been changed from EXTENDEND to EXTENDED, and the displayed value of this extension is no longer blank.
    • In Monitor, object extensions that have not been assigned PLC addresses are no longer displayed in the Monitor.
    • Value of CMMD extension of a VSD Valve is now available on monitor in Debug Mode.
    • IIN (unscaled raw WX) extension of a PID is now displayed on Monitor in Debug Mode.
    • REQUEST extensions (Open, Close, Lock, Unlock, Start, Stop, Hold, Continue, Extend, Retract ) have been added to Monitors of Devices.
    • Fixed ‘Unable to cast object type’ error on attempt a Compile/Download/Enter Debug/Exit Debug command when the currently selected item in Solution Explorer is located within a unit.
  • Full Download
    • Download errors generated from a previous attempt to download are now cleared off by the following successful download.
  • Incremental Compile
    • Incremental compile of a program is no longer allowed unless the user has previously downloaded the full compile of the program.
  •  PCS
    • PCS tag description is now the default description of the tagged object.
  •  Report
    • Download report now includes the information regarding PLC transitioning to Edit/Run mode.
  • Solutions Management
    • An existing project or unit can no longer be added to a unit.
    • Fixed the error of compile/download generated files reported missing from the project after they have been regenerated by a compile/download.
    • Fixed misspelling in warning shown when renaming currently open in editor new SFC/CFC.
    • Compile, Debug, and Download commands are now available on Unit items in Solution Explorer.
    • Fixed failure to load a project when the object file was corrupt or when the project was compiled using a version prior to 1.1.0. The problem exhibited as a project unavailable in Solution Explorer between versions 1.3.6 through 2.1.0, with a possible crash in version 2.1.0.

FTSolution for APT V2.1.1 Release

FasTrak SoftWorks, Inc. is pleased to announce the release of FTSolution for APT V2.1.1. A direct replacement for Siemens-obsoleted DOS APT software, FTSolution for APT extends the life of Siemens or CTI 2500 Series PLCs and APT programs with a complete line of software products and services:

  • Microsoft Windows-based APT replacement
  • PLC hardware debugger
  • Offline PLC program simulator
  • Program version control manager
  • Extensive start-up assistance
  • On- or off-site training classes
  • Personalized technical support

FTSolution for APT V2.1.1 incorporates:

  • 4 new reports including:
    • I/O Symbol Table
    • Device Table
    • Declarations Table
    • Recipes Table
  • An update to the Download report to include any change of the CPU operational mode while downloading a project
  • A new setting in the Configuration Editor that will automatically create a Hardware Debugger file when a project is compiled
  • A progress bar that indicates the progress of the solution being loaded
  • Automatic loading of the last-opened solution when FTSolution is launched
  • Other performance improvements

View release details

Purchase FTSolution for APT to take full advantage of this, and future, enhancements. Purchase includes a warranty offering 12 months of free updates and technical support.

FTVersionTrak V2.0.0 Release

FasTrak SoftWorks, Inc. is pleased to announce the release of FTVersionTrak V2.0.0.

Designed with the industrial user in mind, FTVersionTrak secures the files essential to your manufacturing or business process, safeguarding them from unauthorized access, accidental deletion, or loss. FTVersionTrak makes it easy to:

  • Streamline file managment
  • Simply file sharing
  • Easily control file access and track changes
  • Quickly indentify differences between PLC programs
  • Automatically back up PLC program files

New in FTVersionTrak V2.0.0:

  • Support for SQL Server 2014 and 2016
  • Expanded information in the Scheduled Task report
  • Ability to extract the history of a file from a repository to a local directory
  • Ability to extract the history of a range of file versions from a repository to a local directory
  • Other performance improvements

View release details

FTVersionTrak protects your vital PLC ladder programs and integrates version control into your programming and troubleshooting practices.

FTSolution for APT v2.1.0 Release Notes

Features

  • Added four new reports including:
    • I/O Symbol Table – lists the I/O Symbol Names and the direct addresses to which they are assigned
    • Device Table – lists Device names, types, and descriptions
    • Declarations Table – lists Declarations, their type, descriptions, and direct addresses if they are assigned
    • Recipes Table – lists Recipes by name, and the Recipe Templates from which they are derived
  • A new setting in the Configuration Editor automatically creates a Hardware Debugger file when a Project is compiled. If desired, this default setting can be overridden at the time of compilation.
  • Any change of the CPU operational mode while downloading a Project is identified in the Download Report. This listing documents actions such as stopping the processor to accept a forced compile of a Project.
  • A progress bar has been added to indicate the progress of the solution being loaded.
  • The last-opened Solution automatically loads the next time FTSolution is launched.

Solutions

  • Cross Reference
    • Application no longer crashes when user repeatedly presses Find button without waiting for the result of finding cross references to show up.
    • User can now cancel Find Cross References operation.
  •  Report
    • Cross References report is no longer added to the project Reports folder, whether it was generated for the Cross References search in Program-Level, or unit level. With this fix, if user selects to search for Cross References in the entire program (Program-Level option of Look in control of Cross References window), and chooses to generate a report for the search results – the report will be added under project Report folder. If, however, user selects to search for Cross References in a specific unit and chooses to generate a report for the search results – the report will be added under the unit Report folder.
    • With this fix, a Report node for a report file overriding a report with the same name that exists locally, but was excluded from the project, is no longer added under a Miscellaneous folder node. It is now added to the appropriate Report folder node (program/unit).

FTVersionTrak for APT v1.9.4 Release Notes

Solutions

  • Compare FTSolution for APT Files
    • Subroutine Parameter comparisons are displayed with improved custom color options.
  • Integration with FTSolution for APT
    • The Get, Undo, Check In, and Check Out operations can be performed on groups of user-selected files.
    • Solutions that include Miscellaneous Folders are fully supported.
    • Check In and Check Out dialogs appear when required fields are specified.
  • File System Operations
    • Working Directories that are mapped to subfolders are fully supported.
  • Repository Options
    • Formatted Templates are now more clearly identified.
  • Repository Search
    • Searches can be performed in Repositories that contain thousands of folders.
  • Scheduled Tasks
    • Scheduled Tasks are now removed in a safer two-step Delete-then-Destroy process.
    • Passwords longer than 15 characters are now supported.
    • Scheduled tasks that are Deleted but not yet Destroyed cannot be renamed.
    • New Tasks replace Deleted Tasks when given the same name.
    • Clearer notifications are generated for Scheduled Tasks when there are no differences between the most recent file version and the PLC program.
    • Any existing Scheduled Task settings can be revised.
  • User Interface
    • The Activity Log now uses a Progress Bar to indicate the status of the report preparation.
    • The Search feature provides a more responsive Progress Bar that indicates the status of the operation.
    • Opening Repositories now displays a more responsive Progress Bar that indicates the status of the operation.

FTVersionTrak for APT v1.9.3 Release Notes

Solutions

  • Connection
    • A single verification is required when declining to update Repositories created by previous releases of FTVersionTrak.
  • Files System Operations
    • Root directories can be set as Working Directories for folders.
    • Each Repository folder and subfolder can be assigned unique working directories.
  • Integration with FTSolution
    • New files added to a Solution remain are not automatically checked out after they are checked in.
    • New files can be bound to a Solution into folders that were originally empty.
    • Multiple performance improvements were made to responsiveness of the FTVersionTrak toolbar, and when binding Solutions to Repositories.
    • The correct number of files is reported in the Repository Properties.
    • Items that are deleted but not destroyed cannot be renamed.
    • Checked out files are automatically checked in when binding a Solution to another Repository.
    • Read/Write status is restored to files in Solutions that are unbound from Repositories.
    • New files now can be directly added to Repositories and checked in.
      Repositories can be configured to require entry of Folder Comments when any new folders are added.
    • Properties can be viewed when comparing Projects.
    • Checking in files to a Solution that was deleted from its Repository restores the Solution to the Repository.
    • Check Out Comments can be displayed for any item, including Solutions, Projects, and Units.
    • The Refresh feature in FTVersionTrak correctly displays recently added Solutions from FTSolution for APT.
    • Repository Properties window properly closes.
    • Required Comment field message wording is clarified.
    • When configured, signatures are required for Properties and Comments only when they are edited.
    • Solutions must be rebounded to or unbounded from its Repository if the Solution was deleted from its Repository it was open in FTSolution.
    • The file status of checked-in Subroutines is now set to “Current”.
  • Repository Options
    • Folder history is now retained after the Activity Log is purged.
    • Activity Log entries can be purged, and the number of days to keep log entries can be adjusted without causing deletion errors.
    • When configured, users must enter a comment when checking in files.
    • The Comment field in the label dialog is resizable.
  • Repository Security
    • When configured, a signature is required when revising Repository group owners.
  • Scheduled Tasks
    • Successfully executed Scheduled Tasks are reported correctly.
    • When configured, Scheduled Tasks that detect no differences between the current PLC program and its most recent file in the Repository will email appropriate message.
  • Version Control Operations
    • Electronic signatures are accepted when checking out folders.
    • Electronic signatures are not required when viewing unedited comments.
    • Dialog that confirms deleted or destroyed files closes automatically.
    • A warning dialog appears when checking out a file that will be copied over an edited working copy.

FTSolution for APT v2.0.1 Release Notes

Solutions

  • Compile Report
    • Fixed incorrectly reported count of Y addresses used as CR (when none was used) in summary of memory requirements of Compile Report.
  • Configuration Editor
    • Fixed incorrect errors displayed in the Configuration Editor regarding non-Retentive and Retentive Reserved Locations. The errors now display the correct non-Retentive and Retentive Reserved Locations allowed ranges.
  • Cross Reference
    • Search for references to all symbols (“*”) no longer results in crash in a large program.
    • Cross Reference no longer displays the full local file path of the project file containing the reference. The project relative path will now be displayed.
  • Declaration Editor
    • Previously, renaming a Declaration file and adding a Declaration would cause “The operation could not be completed. The parameter is incorrect.” error on the save of the Declaration file. Once the file was reopened, the added Declaration wouldn’t be in the file, and a Declaration with the same name could not be re-added. This release corrects this behavior such that renaming a Declaration file followed by adding a declaration and saving the renamed file will complete without error and without the added declaration going missing.
  • Full Compile
    • Subroutine recursive calls exceeding 4 levels deep is no longer allowed, consistent with APT. If recursive calls deeper than 4 levels is detected, the (incremental or full) compilation will fail with an error message.
    • User is no longer required to have at least one reserved location from non-retentive C addresses in order to set user-assigned address for Boolean for Retentive C.
    • User will no longer get Potential PCS\PLC Mismatch warning whenever compiling a program with a user-assigned tagged Declaration unless the address of the PCS Tag has changed from the last compile.
  • Incremental Compile
    • When the program was downloaded incrementally after it had been compiled incrementally more than once since the last download, the order of the downloaded commands required the PLC switch between Edit and Run multiple times. Incremental download commands generated by an Incremental Compile are now optimized to avoid multiple PLC transitions from Run to Edit and Edit to Run.
    • Incremental Compile no longer fails when a unit is renamed.
    • Incremental compile validation will no longer fail with error “Conflict between Y and CRs: unable to do an incremental compile” when Y addresses have not been allocated as CR addresses.
  • Incremental Download
    • Fixed “Unknown network error (Cannot Display Network)” when downloading to the 505 simulator.
  •  Report
    • Download Reports now include Communication Type (TCP/IP address or COM port number) information.
    • When generating multiple Cross Reference reports from the same open Cross Reference window, Cross Reference report files were added under the Miscellaneous Files solution folder, instead of adding those files under the project’s Report folder. This release fixes this behavior by adding Cross Reference report files under the projects Report folder.
    • Fixed an error of Boolean type shown in Address-to-Symbol and Symbol-to-Address reports shown as Bool, as well as Boolean. It will show as Bool from now on.
    • The user was not given the option to provide a different filename for a report after being alerted that a file with the same name exists and they decline overriding the existing file. This release fixes this behavior by keeping the Select Report(s) To Generate dialog open, to allow the user to provide a different report filename.
  • Solutions Management
    • Commands for Compile, Download, Debug and Exit Debug were only available if a Project node or Compile node was selected in Solution Explorer. These commands are now available regardless of which project node is selected.
    • Compiler-generated file, CompiledPCSTags, is no longer shown on the solution tree.
  • Version Control Integration
    • Check In of a Declaration table file no longer results in Check Out of a Solution file.
    • Adding an I/O symbol in the I/O Module Editor required the user to manually Check Out the I/O Symbols file. This release adds support to automatically check out and update the I/O Symbols file when adding an I/O symbol in I/O Module Editor.
    • Changes to Process Groups required the user to manually check out the Process Groups file. This release adds support to automatically check out the Process Groups file whenever Process Groups are edited.
    • Changes to communication setup required the user to manually check out the Communication Setup file. This release adds support to automatically check out the Communication Setup file whenever this file edited.
    • Changes to the Object File Report required the user to manually Check Out the Object File Report. This release adds support to automatically check out the Object File Report upon making changes to it by the compiler.
    • Changes to the Download Report required the user to manually Check Out the Download Report. Changes to the Cross Reference Report required the user to manually Check Out the Cross Reference Report. This release adds support to automatically check out the Download Report Report and/or the Cross Reference Report upon making changes to either file.

FTSolution for APT v2.0.0 Release Notes

Features

  • Five object code reports are available after successful project compilation. These reports include:
    • Address to Symbol report alphabetically lists all used direct addresses with their associated Symbol, Symbol Type, and project scope.
    • Symbol to Address report alphabetically lists all Symbols with their associated direct address and Symbol Type grouped by project scope.
    • SFC Cross Reference report lists the main SFC with its related safe-state and subordinate SFCs.
    • SFC Steps and Transitions report lists all Steps and Transitions, with their associated direct control relay addresses.
    • SFC/CFC Math report lists all SFC and CFC Math blocks, with their corresponding addresses and related Special Function programs.

Solutions

  • Application Interface
    • Find Address operation used to be disabled unless the Project is selected. In this software release, Find Address context menu and toolbar options are available to user upon selecting any file or folder within a project.
    • Renaming Communication Setup file is not allowed. However, in prior software releases, renaming Communication Setup file was enabled, but failed without any message to the user. In current software release, renaming Communication Setup file is disabled.
    • For FTSolution files that can be renamed, if the new name included a hyphen or a space, the renaming would fail with no message to the user. In current software release, user is allowed to include spaces and/or hyphens in the new file names.
    • Renaming 505 IO Modules file is not allowed. However, in prior software releases, renaming 505 IO Modules file was enabled, but failed without any message to the user. In current software release, renaming 505 IO Modules file is disabled.
  • CFC Designer
    • Removed Maximum Deviation setting from High, Low and Median Select CFC commands. This setting is not available on these commands.
  • Compile Report
    • Incremental Compile Report now indicates for which incremental compile version it has been generated: “Report generated for compile version #…”
  • Cross Reference
    • Fixed “Sequence contains no elements” compiler error when user attempts to search for cross references in a project that has not been configured yet.
    • Fixed “Sequence contains no elements” compiler error when user attempts to search for cross references in a project that has not been compiled yet.
  • Full Compile
    • Fixed the error of Install.tag missing recipe tags, when generated by Compile with Translate option set to Yes.
    • Using a unit extension when the unit is not included in compile will now generate a compilation error instead of stopping the compile with a fatal error.
    • Fixed an error of Low Select CFC command having an invalid .OUT extension when the output of Low Select is an Analog Output.
    • Removed unused SFS(s) created for an Inswitch Select which only needs an RLL Subroutine.
    • Fixed mismatch between declared array size and the number of array values generated. This mismatch was causing a fatal internal compiler error in prior releases.
    • In full compile, update addresses of PCS-tagged objects if the reserved locations have changed. At the start of the compile, user is warned that translated addresses will be changed. Upon successful compilation, this warning is also written to the compile report.
    • Improved HMI read efficiency by allocating addresses of aliases of tagged objects extensions before non-tagged extensions.
    • Fixed “Out of Retentive CRs” error when doing a full compile of a project.
    • Fixed “Could not find file …\Compile.arpt” compile error.
  • Full Download
    • Removed link to Validation Services.
  • Incremental Compile
    • Create Hardware Debugger File build option, previously only enabled for full compile, is now available for incremental compile.
    • Fixed the error of running out of timers/counters on incremental compile.
    • Deleting an object after compiling, and then adding a new object with the same name as object that has been deleted in the same scope no longer generates an internal compiler error on incremental compile.
    • Fixed an error of incremental compile running infinitely when the number of networks in the program is exceedingly large (in the program in which the defect was found – over 71K).
    • Fixed an error in downloading the wrong opcodes for the new or modified CFC commands.
    • Deleting the most recent incremental object file no longer causes a fatal internal compiler error.
  •  PCS
    • When High Select CFB is marked for PCS tagging, extensions .IN1 and .OUTPUT are now available for marking and are no longer missing.
  • Profibus I/O
    • Fixed error of “Freeze/Sync” and “Lock/Unlock” bits being swapped in the slave parameter byte in the Profibus configuration sent to the CPU.
  • Recipe Template Editor
    • Cross References now can be launched when a Recipe Template is selected. In previous software version, when a Recipe Template was selected, selecting Cross References from a toolbar or a context menu option had no effect.
  • Solutions Management
    • Fixed the “Object reference not set to an instance of an object” error when trying to open a program in software version 1.3.6 that was compiled in software version prior to 1.3.6.
    • Fixed an error of being unable of open a project if the object file has been deleted outside the FTSolution IDE.
  • Version Control Integration
    • Fixed “Write access to object file denied” error on successful download, if the program is controlled by FTVersionTrak repository and an object file is checked in prior to the download operation.
    • Downloaded Program file Object.adpo is no longer generated by successful download, nor is it tracked by a repository.

FTVersionTrak for APT v1.9.2 Release Notes

Solutions

  • Compare FTSolution Files
    • Subroutine, CFC, and SFC comparisons are improved.
    • Complete repository file paths and version numbers are displayed when comparing repository files.
    • Differences in Subroutine parameter headers are highlighted to improve their visibility.
    • The result messages are clarified when comparing empty Subroutines.
    • Using the filter settings to compare Identical, Different, First In, and Second In files no longer clears data from the displayed results.
    • Differences in Subroutine code behind logic are correctly compared and displayed.
  • Integration with FTSolution
    • Units are deleted from the repository when they are deleted from within FTSolution.
    • Multiple versions of Install.tag files are now correctly compared.
      Every file within an FTSolution object is correctly checked in as individual files.
    • Object files that are created after full compilations are not edited after subsequent incremental compiles.
    • Object files that are created after incremental compilations are correctly checked in as files within their project.
    • The multiple files within Subroutines are now correctly compared.
      Correct check-in dates are recorded when multiple Subroutine files are checked in.
    • Binding solutions to repositories is streamlined, requiring less user interaction.
    • Folders containing new files can be checked in separately without requiring the entire project to be checked in.
  • Version Control Operations
    •  New local folders into which working copies of checked-out files are placed can be created during check out.

FTSolution for APT v1.3.6 SP1 Release Notes

Solutions

  • Fixed “Object reference not set to an instance of an object” error. This error occurred when user compiled a program in software version 1.3.4 and attempted to open it in software version 1.3.6.

FTSolution for APT v1.3.6 Release Notes

Solutions

  • Cross Reference
    • Fixed error of showing a reference to user-assigned PLC Address of a declaration that used to have user-assigned PLC Address but has been changed since to use Automatic PLC addressing.
    • Fixed misspelled name of Module Address setting to Thermocouple.
  • Declaration Editor
    • Y addresses cannot be reserved. The software no longer allows using Y addresses as reserved address of a Flag declaration.
  • Full Compile
    • Fixed an error of Compile Report not showing all the units included in compile.
    • Fixed internal (“Object reference not set to an instance of an object”) compiler error for installations that use Dutch Netherlands Language regional setting.
    • Fixed errors in reserving PCS addresses causing some PCS reserved addresses to be overwritten.
    • Fixed error reserving insufficient amount of user-assigned memory causing addresses to be overwritten.
    • Fixed error of Install/Append PCS tag files missing tags of objects in program units.
    • When user increases Reserved Locations, the addresses of PCS tagged objects will change. Added Compile Report warning that notifies user in case of increased Reserved Locations that PCS Tag addresses have been changed.
    • Added a warning to the user that software versions earlier than 1.3.6 will no longer be able to download object files created by software version 1.3.6 or greater.
    • Due to above fixes to calculations of user-reserved locations and compiler-reserved locations for PCS tags, checks were added to prevent download and/or incremental compile of the programs that may have erroneous address calculations. If a program has been compiled in a software version 1.3.5 or earlier, and it has PCS tags or user-reserved locations, then:
      • The user will get a warning recommending a full compile every time the user opens the solution containing such program, until the program is fully compiled in software version 1.3.6 or greater.
      • The user will be prevented from downloading such program and will get an error requesting full compile.
      • If the user attempts to incrementally compile such program, the compile will fail and the user will get an error requesting full compile.

The errors and the warnings will no longer appear once the program has been successfully recompiled fully.

  • Full Download
    • Fixed the internal (“Specified argument was out of range of valid values”) error when attempting to download in a software version earlier than 1.3.6 a program that has been compiled in a software version 1.3.6 or greater.
    • Fixed internal (“Object reference not set to an instance of an object”) error when downloading in software version 1.3.6 a program that has been compiled in software version earlier than 1.3.6.
  • Incremental Compile
    • Fixed internal (“Unable to write to the file”) compiler error.
  • Version Control Integration
    • Fixed defect preventing compile from writing to Append.tag and/or Install.tag files that are currently checked-in.
    • Fixed defect preventing compile from updating a project’s object file that is currently checked-in.

FTVersionTrak for APT v1.9.1 Release Notes

Solutions

  • Installation of SQL 2008 is now optional.
  • When installing FTVersionTrak, previous installations are now recognized.
  • Fixed an error of being unable to integrate with FTSolution for APT due to missing install dependencies of integration projects.
  • User now has the option to check in files that were deleted in FTSolution.
  • Fixed “There is already an open DataReader associated with this Comand which must be closed first” error.
  • The correct version number of FTVersionTrak displays when opening FTVersionTrak from FTSolution.

FTSolution for APT v1.3.5 Release Notes

Solutions

  • Full Compile
    • Fixed real literal translation error from source to assembly.
    • Fixed the error of failing compilation due to not detecting resolution failure of variable identifier symbols used as setting values.
    • Fixed the error of failing compilation due to missing checks on recipe values and settings.
    • Provided a compilation error instead of failing compilation when symbols referenced as recipe values are not marked as constants.
    • Fixed a code generation error for the Clear Temporary Outputs instruction.
    • Fixed error during running compiler optimization to replace integer-type symbolic constants with their literal values when user-assigned addressing is used for the referenced symbolic constant.
    • Fixed error during running compiler optimization to replace real-type symbolic constants with their literal values when user-assigned addressing is used for the referenced symbolic constant.
    • Fixed incorrect type assignment of integer-type scalar recipe extensions.
    • Fixed an error of a missed update of array size in Declaration Table editor, causing compilation to fail due to declarations failing validation.
    • Provided array variable names and array sizes when an array size mismatch error is detected in an assignment statement.
  • Cross Reference
    • Fixed “Invalid symbol entered” error not cleared when user replaces an invalid symbol/address name entered in “Find what” text box with a valid symbol/address name.
    • When user searches for a symbol, the references of this symbol no longer include the references of symbol(s) used in its settings or extensions.
    • Cross references are now shown in sorted order. The sorting is by “Found In” first, “Line #” second, and “Description” last.
    • Reduced Cross References tool window loading time.
    • Fixed “Value cannot be null. Parameter name: source” error when launching Cross Reference tool window.
    • User may now double click anywhere in a cross reference to navigate to the reference source location.
    • Added Setting Name to the Descriptions of Device cross references.
    • Fixed error of auto-complete not working for unit symbol names and extensions.
    • Fixed error of not finding references to Recipe Template.
  •  Debug
    • Fixed Illegal Task code error when writing to Status Words.
  • Declaration Editor
    • Fixed error of allowing symbol names to be the same as floating point numbers.
    • Fixed error of Declaration files not being recognized as modified and therefore saved when user assigns a symbol name to an array element.
    • Declaration Editor now detects and reports an error of a symbol assigned to an element of an array that is marked as constant. This error used to not be detected until compile time.

FTSolution for APT v1.3.5 RC1 Release Notes

FTSolution for APT v1.3.5 RC1 is a limited release.

Solutions

  • Full Compile
    • Fixed System Out of Memory Exception error.
    • Fixed the error in calculating One Shot and Shift Register numbers when offset by the Configuration’s Reserved location.
  • Incremental Compile
    • Fixed System Out of Memory Exception error.
    • Fixed the error of assigning One Shot and Shift Register box instructions incorrectly.
  • Cross Reference
    • Fixed the error of being unable to find references to Program’s extensions.
    • Fixed the error of being unable to find references to extensions of a unit.
    • Fixed the error of showing references to an object when searching for references to a non-existing extension or setting of an object.
    • Fixed the error of user being unable to re-order the columns in the cross references view.
    • Fixed the error of no type shown for references to a direct address.
    • Added missing Cross Reference icon for toolbar.