Author: Ethan Wilke

• CFC Editor
  • Fixes the issue of Scaled Integer declarations not shown in the list of the symbols valid for assignment to Process Variable settings of an object. For example, the settings of Wild Process Variable of Ratio Station CFB.
  • Resolves the issue of CFC Diagrams not registered with the project they belong to.
• Declarations Editor
  • Addresses an issue of an internal symbol $DP_VERSION showing in the drop-down list of symbols that can be used for a symbol setting for which a valid assignment is either an integer literal or an integer constant declaration.
• Solutions Management
  • Fixes error “The file cannot be added. A duplicate object has been detected” shown to user when a unit is removed and then re-added as an existing item in the same application session.
  • Fixes error “Object reference is not set to an instance of an object” shown when user executes command “Generate Reports” on an object file node that is shown under the Compile folder of the project in Solution Explorer, but the object file is missing in the file system.
• Other
  • Added support for expiration dates past 12/2021. Click here for more information.

Solutions

• Debug
  • Fixes the Connect Error “Object reference not set to an instance of an object” received when going into Debug mode in a project using SFC compiled in a software version prior to 2.3.0.
• Project Upgrade
  • Fixes issue of incremental download being disabled when the customer upgrades from software version prior to 2.2.0 to software version 2.2.1 or newer, and opens a project compiled in a software version prior to 2.2.0.
  • Resolves issue of redundant checking for required project upgrade during project load, when the project has already been checked and found not to need the required upgrade.

Features

• The Step and Transition label numbers in Sequential Function Charts can be renumbered to more closely match the graphical order that determines their actual order of execution.
• Groups of PCS Tag attributes can be selected at the same time.
• Help articles have been added for Cyclic Function Blocks.
• Help buttons that display Help articles for each selected CFB type have been added in the CFB editor.

Solutions

• CFC Editor
  • The use of a recipe element in a CFB setting, that prevents compile, is now flagged as an error in the CFC Editor.
  • Removes internal symbols from the drop-down list of options of a CFB setting.
  • Fixes an issue of a CFC edit causing an application lock up or a crash when user responds with a “Yes” to the “This file has been modified outside the editor. Do you want to reload it?” prompt.
  • Boolean literals TRUE and FALSE are no longer allowed for use on symbol settings.
• Configuration Editor
  • Addresses an issue of compiler errors being shown for the errors in configuration settings that existed before user had changed the controller type and no longer exist in the current configuration.
• Cross Reference
  • Removes CFC file names from the “Find what:” drop-down list of symbols of Cross Reference window.
• Demo Mode
  • Fixes an issue of application closing when user opens a project created by fully licensed software in the unlicensed software.
  • Fixes an issue of application closing when user opens a project created by unlicensed software in the fully licensed software.
• Full Compile
  • Fixes an issue of incorrectly generated code for a Rate Limiter symbol when a Rate Limiter uses:
    • An Analog Output for its Output setting, and
    • A symbol of one of these types for its Input setting: Scaled Integer, Analog Output, Word Input, Word Output, BCD Input, or BCD Output.
  • Loading a program that was compiled and download in software releases prior to 2.3.0 and contained a Rate Limiter symbol that meets these the above criteria will result in project upgrade.
  • Fixes an issue of incorrectly generated code for an Output Limiter symbol when an Output Limiter uses:
    • An Analog Output for its Output setting, and
    • A symbol of one of these types for its Input setting: Scaled Integer, Analog Output, Word Input, Word Output, BCD Input, or BCD Output.
  • Loading a program that was compiled and download in software releases prior to 2.3.0 and contained an Output Limiter symbol that meets these criteria will result in project upgrade.
  • Fixes an issue of incorrectly generated code for an Outswitch Select symbol when an Outswitch Select uses:
    • An Analog Output for any of its Output settings, and
    • A symbol of one of these types for its Input setting: Scaled Integer, Analog Output, Word Input, Word Output, BCD Input, or BCD Output.
  • Loading a program that was compiled and download in software releases prior to 2.3.0 and contained an Outswitch Select symbol that meets these criteria will result in project upgrade.
  • Fixes an issue of incorrectly generated code for an Correlated Lookup Table symbol when an Correlated Lookup Table uses:
    • An Analog Output for its Output setting, and
    • A symbol of one of these types for its Input setting: Scaled Integer, Analog Output, Word Input, Word Output, BCD Input, or BCD Output.
  • Loading a program that was compiled and download in software releases prior to 2.3.0 and contained an Correlated Lookup Table symbol that meets these criteria will result in project upgrade.
  • Fixes an issue of internal NNL extensions of locally-declared variables (.NNL.TRIGGER, .NNL.TIMED, .NNL.ECODE, .NNL.EVENT, .NNL.ERS, .NNL.FIN, .NNL.$NL_SFINT, .NNL.IID, .NNL.SNUM, .NNL. INIT, .NNL.ENABLE.TRIGGER) being permitted in a setting of a symbol.
• PCS
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for PCS tags of Input and Output settings of a Subtractor CFB.
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for a PCS tag of an Output setting of a Derivative CFB.
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for a PCS tag of an Output setting of a Divider CFB.
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for VALUE PCS tag attribute of PCS Tags of Process Variable and Time Constant settings of a First Order Lag CFB.
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for VALUE PCS tag attributes of PCS Tags of Lead and Lag Time Constants settings of a First Order Lead Lag CFB.
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for a PCS tag of an Input settings of an Inswitch Select CFB.
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for VALUE PCS tag attributes of PCS Tags of Input settings, Output setting, and Enable Flag of Input settings of a Low Select CFB.
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for VALUE PCS tag attributes of PCS Tags of Input and Output settings of a Math CFB.
  • Fixes an issue in Install.tag file, where a wrong initial value was generated for VALUE PCS tag attributes of PCS tags of symbol settings that use WX/WY address locations.
  • Fixes an issue in Install.tag file, where a PCS tag UNITS attribute of an Output setting of a Summer CFB was missing.
  • Fixes an issue in Install.tag file, where a wrong value was used for Series 505 S-memory addresses of the PCS tags of Analog Alarm extensions.
  • Adds the name of the symbol and its extension to the PCS Attributes dialog.
  • Removes a header line (Record, GroupNumber,Description) from install.tag file when none of the Process Groups has a non-blank description.
  • Removes a header line (Record, Recipe,Component,Tag,Attribute) from install.tag file when there is no recipe in the program that has been marked for PCS.
• Project Upgrade
  • Resolves an issue of Download incremental changes only option not available on a project upgraded to the current software version.
    Resolves an issue of incremental object files generated by compiling in the previous software versions being lost due the project upgrade to the current software version.
•  Report
  • Adds unit descriptions to the Configuration report, Units to Compile section.

Features

• Added a Syntax Check option for 545, 555, 575, and CTI 2500 Series controllers, which allows users to check a program for errors that would prevent the controller from entering Run mode.

Solutions

• Full Download
  • Added the transitions in PLC mode (from Run to Hold, from Hold to Run, from Run to Program, or from Program to Run), that occur during full or incremental download of the program, to the download report.
•  Import
  • Fixed an issue of Value of Lag Time Constant setting of a First Order Lead Lag object not being imported.
  • Fixed an issue of Controller Name – when set to default in APT (Controller Type) – not being imported and left blank.
  • Resolved an issue of Process Groups not being imported.
  • Addressed an issue in PCS tag description, where backslash and/or double quotes entered by a user in PCS tag editor were removed from PCS tag description in install.tag file.
  • Addressed an issue of PCS tag Deadband imported value being inconsistent with a value entered by user in APT (double precision).
• Incremental Compile
  • Resolved an issue of user being unable to do an Incremental Compile after adding an I/O module unused in the program. Prior to this fix, if the only change in a previously compiled program was an addition of an I/O module, and user attempted to do an incremental compile, the software would cancel an incremental compile with the error message “The compiled program is up to date.”
•  PCS
  • Addressed an issue in Install.tag file, where a PCS tag attribute of a recipe is missing an address.
  • Addressed an issue in Install.tag file, where a wrong type of address (V address) was used in a PCS tag OUT attribute generated for the Output setting of a PID Loop. With this fix, a LMN type of address associated with TOUT extension is used in the PCS tag OUT attribute of a PID Loop.
  • Addressed an issue in Install.tag file, where a wrong type of address (V address) was used in a PCS tag VALUE attribute generated for the Output setting of a Inswitch Select CFB. With this fix, a WY type of address associated with OUTPT extension is used in the PCS tag VALUE attribute of an Inswitch Select CFB.
  • Addressed an issue in Install.tag file, where a wrong type of address (V address) was used in a PCS tag VALUE attribute generated for the Output setting of an Output Limiter CFB. With this fix, a WY type of address associated with OUTPT extension is used in the PCS tag VALUE attribute of an Output Limiter CFB.
  • Addressed an issue in Install.tag file, where a wrong type of address (V address) was used in a PCS tag VALUE attribute generated for the Output setting of an Rate Limiter CFB. With this fix, a WY type of address associated with OUTPT extension is used in the PCS tag VALUE attribute of a Rate Limiter CFB.
  • Fixed an issue in Install.tag file, where an entire address, including an address type was used for Loop addresses of PCS tag attributes. APT drops the address type (keeping address values only) of the following L-addresses: LCFH, LCFL, LMX, LERR, LSPH, LSPL, LTS in the PCS tag attributes. With this fix, L-Addresses types are omitted, and only address values are used in PCS tag attributes.
  • Resolved the issue in Install.tag file, where Controller Type name was used when Controller Name is left blank (default). With this fix, FTSolution matches an APT in leaving the Controller name blank in Install.tag file, if the Controller name is left blank in the project’s Configuration file.
  • Addressed an issue of HLIM (High Output Limit setting) and LLIM (Low Output Limit setting) extensions being shown in the PCS tag editor of a Feedforward Output Adjust CFB, when APT would not allow tagging of these extensions.
  • Fixed an issue in Install.tag file, where an entire Loop V-flags address, including the address type -LVF -was used in an address of a PCS tag attribute. APT drops the address type of an LVF address in the PCS tag attributes, replacing it with LSTATUS followed by the address value. With this fix, FTSolution matches APT in replacing the LVF address type with LSTATUS followed by the actual address value in a PCS tag attribute.
  • Addressed an issue in Install.tag file, where a wrong type of address (V address) was used in a PCS tag PV attribute generated for the Process Variable setting of a Resistance Temperature Detector I/O symbol. With this fix, a WX type of address associated with RAW extension is used in the PCS tag PV attribute of a Resistance Temperature Detector I/O symbol.
  • Addressed an issue in Install.tag file, where a wrong type of address (V address) was used in a PCS tag VALUE attribute generated for the Calculated Variable Value attribute of Out 1 setting (OUTPUT1 extension) and the Calculated Variable Value attribute of Out 2 setting (OUTPUT2 extension) of a Split Range CFB. With this fix, a WY type of address associated with OUTPUT1 and OUTPUT2 extensions are used in the PCS tag VALUE attributes of a Split Range CFB.
  • Fixed an issue in Install.tag file, where a description of a process group was missing quotation characters, making it different from what had been entered by user.
  • Resolved an issue in Install.tag file, where PCS tag TEXT_1 attribute of Text Declarations and Text Array Declarations was missing.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag PV attribute of an Analog Input I/O symbol.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag OUT attribute of an Analog Output I/O symbol.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of a Steady State Gain setting (GAIN extension) of a Dead Time Compensator CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of Lead Time Constant and Lag Time Constant settings (TAU1 and TLEAD extensions) of a First Order Lead Lag CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of Output settings (OUT extension) of an Integrator CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of Input and Output settings of a Math CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of Setpoint setting of a Motor Position Control CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag STATUS attribute of Output setting of a Proportional Time Control CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag CHANGE (Deadband) attribute of a Real declaration.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag PV attribute of the Module Address setting of a Resistance Temperature Detector I/O symbol.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of the ‘As the input changes’ setting of a Scale CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag Output Value (OUT) attribute of the STATUS extension of a Scaled Integer.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of the First Time Constant setting (TAU1 extension) and Second Time Constant setting (TAU2 extension) of a Second Order Lag CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of the Lead Time Constant setting (TLEAD extension), First Time Constant setting (TAU1 extension) and Second Time Constant setting (TAU2 extension) of a Second Order Lead Lag CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag VALUE attribute of the Out 1 setting (OUTPUT extension) of a Split Range CFB.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag PV attribute of the Module Address setting (RAW extension) of a Thermocouple I/O symbol.
  • Resolved an issue in Install.tag file, where a wrong initial value was used in the PCS tag STATUS attribute of Output setting (DOUT extension) of a Valve Sequencer CFB.
  • Fixed an issue in Install.tag file, where PCS tag UNITS attributes of OUT, INPUT, IOUTPUT, and IINPUT extensions associated with Input and Output settings of a Correlated Lookup Table CFB were missing.
  • Fixed an issue in Install.tag file where a PCS tag UNITS attribute of IINPUT extension of Dead Time Delay, Integrator, First Order Lag and Second Order Lag CFBs was missing.
  • Fixed an issue in Install.tag file, where a PCS tag UNITS attribute of an Output setting of a Derivative CFB was missing.
  • Fixed an issue in Install.tag file, where PCS tag UNITS attributes of Input and Output settings of a Divider CFB was missing.
  • Fixed an issue in Install.tag file, where PCS tag UNITS attribute of Output settings of a First Order Lag CFB was missing.
  • Fixed an issue in Install.tag file, where PCS tag UNITS attribute of Output settings of an Integrator CFB was missing.
  • Fixed an issue in Install.tag file, where PCS tag UNITS attribute of Output settings of a Divider CFB was missing.
  • Fixed an issue in Install.tag file, where PCS tag UNITS attribute of a CFB setting, that uses an element of an Array that has an assigned Engineering Units value, was missing.
  • Fixed an issue in Install.tag file, where a PCS tag was generated for an INPUT extension (Process Variable setting) of a Dead Time Delay CFB, when APT does not generate it.
  • Fixed an issue in Install.tag file, where a PCS tag was generated for an INPUT extension (Process Variable setting) of a Derivative CFB, while APT would not generate it.
  • Fixed an issue in Install.tag file, where a PCS tag was generated for an Input setting of a First Order Lag CFB, when APT does not generate it.
  • Fixed an issue in Install.tag file, where a PCS tag was generated for an Input and Output settings of a First Order Lead Lag CFB, when APT does not generate it.
  • Fixed an issue in Install.tag file, where a PCS tag was generated for an Input and Gain settings (INPUT, IINPUT and TAU1 extensions) of an Integrator CFB, when APT does not generate it.
  • Fixed an issue in Install.tag file, where a PCS tag was generated for Input setting (IINPUT extension) and Output settings (OUT extension) of a Second Order Lag CFB, when APT does not generate it.
  • Fixed an issue in Install.tag file, where a PCS tag was generated for Input setting (INPUT extension) of a Second Order Lead Lag CFB, when APT does not generate it.
  • Addressed an issue where both, OUTPUT and IOUTPUT extensions of a Valve Sequencer could be tagged, regardless of the type of the actual variable used in the assignment of the Output Name setting of the Valve Sequencer CFB. APT allows only one of the OUTPUT and IOUTPUT extensions to be tagged.
  • Resolved an issue of AutoLog status being enabled for VALUE PCS tag attribute of a Process Variable setting (IINPUT extension), Dead Time setting (DTIME extension), and TAU1 extension of a Dead Time Delay.
  • Resolved an issue of AutoLog and Upload statuses being enabled for PCS tag VALUE attributes of a Dead Time settings (DMODE extension) of a Dual Mode, while APT disables them.
  • Resolved an issue of AutoLog and Upload statuses being enabled for PCS tag attributes of Feedforward Output Adjust , while APT disables them.
  • Resolved an issue of AutoLog status being enabled for PCS tag VALUE attributes of a Time Constant settings (TAU1 extension) of a First Order Lag, while APT disables them.
  • Resolved an issue of AutoLog status being enabled for PCS tag VALUE attributes of a Dead Time setting (DTIME extension) of a First Order Lead Lag, while APT disables them.
  • Resolved an issue of AutoLog and Upload statuses being enabled for PCS tag attributes of Calculated Variable Value attribute, Input setting of High Select, while APT disables them.
  • Resolved an issue of AutoLog status being enabled for PCS tag attributes of Calculated Variable Value attribute, Input setting of Math CFB, while APT disables them.
  • Resolved an issue of AutoLog status being enabled for PCS tag VALUE attributes of a Real Array element, while APT disables them.
  • Addressed an issue of inconsistent PCS attribute names of Cylinders, Motors, Presses, and Valves, where Control attribute was in some cases spelled as Ctrl, and Command was in some cases spelled as Cmd.
  • Addressed an issue of wrong PCS attribute names of Motors and Valves, where Motor Stop Command Timeout was incorrectly called Motor Close Command Timeout, and Motor Start/Run Command Timeout was incorrectly called Motor Open Command Timeout.
  • Addressed an issue of wrong PCS attribute names of a Three Position / Type 1 Batch Press, where Motor Stop Command Timeout was incorrectly called Valve Close Command Timeout, and Motor Start/Run Command Timeout was incorrectly called Valve Open Command Timeout.
  • Addressed an issue of wrong PCS attribute names of a Three Position / Type 1 Batch Valve, where:
    • Motor Stop Command Timeout was incorrectly called Valve Close Command Timeout
    • Motor Start/Run Command Timeout was incorrectly called Valve Open Command Timeout
    • Motor Feedback Override Control was incorrectly called Valve Setpoint Control
    • Motor Setpoint Control was incorrectly called Valve Mode Control,
    • Motor Mode Control was incorrectly called Valve Status
    • Motor Status was incorrectly called Valve Feedback Override Control
  • Addressed an issue of wrong PCS attribute names of a Three Position / Type 2 Batch Press, where Motor Stop Command Timeout was incorrectly called Valve Close Command Timeout, and Motor Start/Run Command Timeout was incorrectly called Valve Open Command Timeout.
  • Addressed an issue of wrong PCS attribute names of a Three Position / Type 2 Batch Valve, where:
    • Motor Stop Command Timeout was incorrectly called Valve Close Command Timeout
    • Motor Start/Run Command Timeout was incorrectly called Valve Open Command Timeout
    • Motor Feedback Override Control was incorrectly called Valve Setpoint Control
    • Motor Setpoint Control was incorrectly called Valve Mode Control
      Motor Mode Control was incorrectly called Valve Status
    • Motor Status was incorrectly called Valve Feedback Override Control
  • Addressed an issue where AutoLog of Output Range and AutoLog of Low Range of a Scaled Integer PCS Tag could be selected by user (APT only allows selecting AutoLog of High Range), that resulted in H_RANGE and L_RANGE PCS tag attributes showing twice in Install.tag file.
  • Fixed an issue in Install.tag file, where fractions were used instead of integer numbers for Close Command Timeout (TIMEOUT_1) and Open Command Timeout (TIMEOUT_2) PCS tag attributes of a Motor Position Control CFB.
  • Fixed an issue in Install.tag file, where fractions were used instead of integer numbers for Close Command Timeout (TIMEOUT_1) and Open Command Timeout (TIMEOUT_2) PCS tag attributes of a Single Drive / Dual Feedback Valve Device.
  • Fixed an issue in Install.tag file, where fractions were used instead of integer numbers for Close Command Timeout (TIMEOUT_1) and Open Command Timeout (TIMEOUT_2) PCS tag attributes of a Single Drive / Null Feedback Valve Device.
  • Fixed an issue in Install.tag file, where fractions were used instead of integer numbers for Close Command Timeout (TIMEOUT_1) and Open Command Timeout (TIMEOUT_2) PCS tag attributes of a Three Position Batch Valve / Type 1 Valve Device.
  • Resolved an issue where INPUT extension (Input Name setting) of a Threshold Select CFB could be tagged in APT, but not in FTSolution.

Solutions

• 505 I/O
  • In FTSolution, to insert a module that is defaulted to occupy multiple slots into a specific slot, the target slot must have the required number of consecutive slots to be unoccupied. Prior to this release, an attempt to insert a module that required more than one slot into a slot with one or more of the required consecutive slots already used, would fail with the following error: “Module to large for slot location”. With this fix, if a module’s default slot count is greater than the slots available at the slot location, the software will automatically reduce the slot count to allow the module to fit, and notify the user with this message: “Slot size reduced in order to fit.”
• Full Compile
  • Previously, if customer changed the Process Variable of an Analog Alarm, Dual Mode, Ratio Station, Dead Time Compensator, PID Loop, or an On/Off continuous function block to use .IIN extension, FTSolution displayed the following error in the Settings Editor: “Validation error in object objectname, setting Process Variable…”. An attempt to compile the program would result in a compile error with the same error message. With the fix to this error, FTSolution no longer generates an error when a Process Variable of an Analog Alarm, Dual Mode, Ratio Station, Dead Time Compensator, PID Loop, or On/Off object is set to use .IIN extension.
•  Import
  • APT allows either “N” or “FALSE” as a value for Manual set PCS Tag option to indicate that Manual set is off, while FTSolution only accepted “N”. As a result, any PCS Tag in which Manual set was set to “FALSE” in APT, was imported into FTSolution as “on”, instead “off”.
•  PCS
  • Removed an extra PCS tag parameter , unit name, from the PCS tag line in PCS tag file.
  • Removed from a PCS tag file an extra PCS tag  attribute line – UNITS (Engineering Units) – generated for an array element.
  • Added to PCS tag file a Ratio Station PCS tag  Engineering Units (UNITS) attribute line.
  • Added to PCS tag file a Feedforward Setpoint Adjust PCS tag  Engineering Units (UNITS) attribute line.
  • Added to PCS tag file a Feedforward Output Adjust PCS tag  Engineering Units (UNITS) attribute line.
  • Added to PCS tag file a Dual Mode PCS tag  Engineering Units (UNITS) attribute line.
  • Added to PCS tag file a Dead Time Compensator PCS tag  Engineering Units (UNITS) attribute line.
  • Added to PCS tag file a PID Loop PCS tag  Engineering Units (UNITS) attribute line.
  • Added to PCS tag file a Dead Time Compensator PCS tag  Engineering Units (UNITS) attribute line.
    Added to PCS tag file an Analog Alarm PCS tag  Engineering Units (UNITS) attribute line.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines of PCS tags generated for Input and Output settings of a Scale.
  • Added to PCS tag file an Engineering Units (UNITS) PCS tag  attribute line generated for a PCS Tag of an On/Off that uses Analog Input for its Process Variable setting.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input settings of a Low Select.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Low Select when its Output setting is set to an Analog Alarm.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines to PCS tags generated for Input settings of a Threshold Select.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Outswitch Select.
  • Added to PCS tag file an Engineering Units (UNITS) attribute line generated for PCS Tag of Input setting of an Inswitch Select.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Median Select.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a High Select.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of an Average Select.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines to PCS tags generated for Summer’s Input and Output settings.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Subtractor.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Multiplier.
  • Added to PCS tag file an Engineering Units (UNITS) attribute line generated for PCS Tag of Output setting of a Divider.
  • Added to PCS tag file an Engineering Units (UNITS) attribute line generated for PCS Tag of Input setting of a Square.
  • Added to PCS tag file an Engineering Units (UNITS) attribute line generated for PCS Tag of Output setting of a Square Root.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Absolute Value.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Process Variable and Output settings of a First Order Lead Lag.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Process Variable and Output settings of a First Order Lag.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Process Variable and Output settings of a Second Order Lead Lag.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Process Variable and Output settings of a Second Order Lag.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Valve Sequencer.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Split Range.
  • Added to PCS tag file an Engineering Units (UNITS) attribute line generated for PCS Tag of Input setting of a Proportional Time Control.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Position Feedback and Setpoint settings of a Motor Position Control.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Output Limiter.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Rate Limiter.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Integrator.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Process Variable and Output settings of a Derivative.
  • Added to PCS tag file an Engineering Units (UNITS) attribute lines generated for PCS Tags of Input and Output settings of a Dead Time Delay.
  • Added to PCS tag file an Engineering Units (UNITS) attribute line generated for PCS Tag of Monitored Variable setting of an Anti-Reset Windup Protection Select.
  • Added to PCS tag file an Engineering Units (UNITS) attribute line generated for PCS Tag of Monitored Variable setting of an Anti-Reset Windup Protection Constraint.
  • Removed from a PCS tag file a Recipe line generated for a Recipe without tagged elements.
  • Removed from a PCS tag file an Engineering Units (UNITS) attribute line generated for an array element that has blank Engineering Units.
  • Actual value of Process Variable Low Range setting is now used instead of 0 in Initial Value of a PV attribute line generated for an Analog Alarm.
  • Actual value of Process Variable Low Range setting is now used instead of 0 in Initial Value of a PV attribute line generated for an PID Loop.
  • Actual values of Process Variable Low Alarm, Low Low Alarm, High Alarm, High High Alarm, and Rate of Change Alarm settings are used now (instead of 0) for the Initial Values of L_ALM, LL_ALM, H_ALM, HH_ALM, and ROC_ALM attribute lines of a PCS Tag of a PID Loop.
  • Actual values of Tuning Parameters Derivative Time, Integral Time and Proportional Gain settings are used now (instead of 0) for the Initial Values of RATE, RESET, and GAIN attribute lines of a PCS Tag of a PID Loop.
  • Actual values of Process Setpoint Yellow (Low) Deviation Alarm and Orange (High) Deviation Alarm settings are used now (instead of 0) for the Initial Values of L_DEV and H_DEV attribute lines of a PCS Tag of a PID Loop.
  • Actual values of Process Variable Low Alarm, Low Low Alarm, High Alarm, High High Alarm, and Rate of Change Alarm settings are used now (instead of 0) for the Initial Values of L_ALM, LL_ALM, H_ALM, HH_ALM, and ROC_ALM attribute lines of a PCS Tag of an Analog Alarm.
  • Actual value of Process Setpoint, Minimum Setpoint setting is used now (instead of 0) for the Initial Value of TARGET attribute line of a PCS Tag of an Analog Alarm.
  • Actual values of Process Variable Low Range, Low Alarm, Low Low Alarm, High Alarm, High High Alarm, and Rate of Change Alarm settings are used now (instead of 0) for the Initial Values of PV, L_ALM, LL_ALM, H_ALM, HH_ALM, and ROC_ALM attribute lines of a PCS Tag of an On/Off.
  • Actual values of Process Setpoint Yellow (Low) Deviation Alarm and Orange (High) Deviation Alarm settings are used now (instead of 0) for the Initial Values of L_DEV and H_DEV attribute lines of a PCS Tag of an On/Off.
  • Actual value of Timeout Preset setting is used now (instead of 0) for the Initial Value of CURRENT attribute line of a PCS Tag of a Fast Timer.
  • Actual value of Timeout Preset setting is used now (instead of 0) for the Initial Value of CURRENT attribute line of a PCS Tag of a Slow Timer.
  • Actual values of Process Minimum Setpoint and Process Variable Low Range settings are used now (instead of 0) for the Initial Values of PV and SP attribute lines of a PCS Tag generated for a Ratio Station.
  • Actual value of Process Variable Low Range setting is used now (instead of 0) for the Initial Value of PV attribute line of a PCS Tag of an Analog Alarm.
  • Actual value of Process Variable Low Range setting is used now (instead of 0) for the Initial Value of PV attribute line of a PCS Tag of a PID Loop.
  • Actual value of Process Variable Low Range setting is used now (instead of 0) for the Initial Value of PV attribute line of a PCS Tag of an On/Off.
  • Actual value of Process Variable Low Range setting is used now (instead of 0) for the Initial Value of PV attribute line of a PCS Tag of an Analog Input.
  • Actual values of Process Variable Low Range and Process Minimum Setpoint settings are used now (instead of 0) for the Initial Values of PV and SP attribute lines of a PCS Tag of a Feedforward Setpoint Adjust.
  • Actual values of Process Variable Low Range and Process Minimum Setpoint settings are used now (instead of 0) for the Initial Values of PV and SP attribute lines of a PCS Tag of a Feedforward Output Adjust.
  • Actual value of Process Variable Low Range setting is used now (instead of 0) for the Initial Values of PV attribute line of a PCS Tag of a Dual Mode.
  • Actual value of Process Variable Low Range and Process Minimum Setpoint settings is used now (instead of 0) for the Initial Values of PV and SP attribute lines of a PCS Tag of a Dead Time Compensator.
  • In APT, an Initial Value of a PCS Tag Deadband (CHANGE) attribute is given a double precision value, while FTSolution used single precision.

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.

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.