Author: Sarah Beackley

PLC WorkShop Suite for Siemens 505 v3.40 SP2 Release Notes

Features

  • An option supporting CAMP communications that allows quicker upload and download of program data tables.
  • CAMP is supported if 2572 is Board E, Rev 8.5 and higher.
  • CAMP is supported if 2572A is Rev 1.41 and higher.
  • File Program Compare now allows basic or comprehensive ladder logic comparison.
  • When online with a PLC that has a Fatal error, the status bar and window title bar display the fatal error and the title bar will periodically flash.
  • The Enabled/Disabled state of an SF can be toggled within the SF editor.
  • In the SF editor, the Enabled/Disabled state is now shown in the title bar.

Solutions

  • Corrected a situation where an error message about compiled statistics would appear while viewing the SF directory.
  • Corrected a situation that randomly caused an application error in searches and cross reference builds.
  • Corrected a condition in 575 where RAM was wrongly identified as EEPROM, causing “unable to write network data” error.
  • Registry usage has been revised. Shared information (security, communication, etc.) is stored in a location accessible to multiple users. Personal settings (recent files, program setup, last online connection method) are stored for each user. This means that only users who are also a Windows administrators or who have been assigned rights to the appropriate parts of the registry can add, modify and delete the shared information. The software is now able to read registry entries when the user is not an administrator.
  • Text file import error messages have been improved.
  • Timeout for online Find for 565 has been fixed.
  • Support for VMM addresses has been added to the Copy, Paste and Delete address documentation functionality.
  • Support for timer and counter addresses has been added to the Copy and Paste with rewire address documentation functionality.
  • Cross Reference setup in Print Preview now retains user’s Address/Network Mode selection.
  • Corrected text file printing of SF programs: some characters to the far right were truncated.
  • In cross reference, contacts are now represented with backward brackets for easier identification. For example: a normally closed contact is ]/[.
  • Corrected a condition where copying timers and counters from one program to another did not copy the TCC documentation with the logic.
  • Corrected an application error in Replace Table that occurred when Copy Network Headers was selected and there were multiple output coils or the output coil was changed.
  • Changed the Analog Alarm Editor to store the Alarm Clamp SP Low value correctly.
  • When deleting an alarm, pressing ESC at the warning would not cancel the deletion. Now any action other than selecting Yes cancels the deletion.
  • Corrected a ladder editing situation in which selecting F4 (append) followed by F3 (insert new row) would result in “Error while attempting to display logic.”
  • Fixed application error in Replace Table for next replace.
  • Added Cross Reference implied addresses in Special Function instructions.
  • Corrected a time-out error that occurred when loading by parts – K memory and V memory.
  • NT Audit recording has been improved to more accurately record activity.
  • Valid range for the second count in an EDRUM has been changed from 0.001 – 32.767 to 0 – 32.767
  • Corrected an application error that occurred when cancelling a transfer to online.
  • Fixed a situation where printing only V-Registers causes an application error.
  • When inserting a column while on a multi-column box instruction, the insertion now occurs before the instruction.
  • Carriage return/line feed ASCII symbols are no longer displayed in the Documentation Window or in the data window.
  • Corrected the delimiter selection in the Import Documentation. The delimiter expected was a tab even if the user selected comma, resulting in “Missing delimiter on line 1” errors.
  • Corrected a condition that sometimes caused the progress bar to stay visible after transferring logic and going online.
  • PLC Configuration now warns about reductions in the size of memory areas.
  • Fixed highlighting upon open in SF editor.
  • Improved the Activity Audit process to avoid duplicate “logic edited” records.
  • Corrected SMC instruction to allow complex inputs.
  • Fixed the print function in which documentation was printed even when not selected.
  • Corrected the inactive password timeout feature, which timed out immediately.
  • Printing now skips invalid addresses.
  • The Open dialog now refreshes when the user switches back browsing for FSS files after browsing for VP5 files.
  • If a fault exists, the software now displays “Unknown” in areas of the PLC Status dialog that references the status words.
  • Fixed reading SFP and SFS on 555 1104.
  • The Cross Reference report now prints documentation for addresses within the specified ladder range.
  • The timer for the password timeout now resets any time the User Security Options dialog is used.
  • Corrected a condition in which copying and pasting an address with the maximum tag, description, and comment lengths would cause an application error.
  • When editing documentation, the description now scrolls vertically when it contains more lines than can be displayed at once.
  • Corrected a situation in which the FasTrak security system Administrator Options/Select menu should have been disabled.
  • The User Security Options dialog will no longer accept blank passwords.
  • The activity audit text has been revised. File names appear in the original case.
  • Fixed Clear Network to correct calculation of memory sizes.
  • The Replace Table dialog now allows the DSP, DSC, DCC, TCP and TCC address types. When a real address is found and replaced, its original address type is retained.

PLC WorkShop Suite for Siemens 505 v3.40 SP1 Release Notes

Features

  • An option supporting CAMP communications that allows quicker upload and download of programs.
  • CAMP is supported if 2572 is Board E, Rev 8.5 and higher.
  • CAMP is supported if 2572A is Rev 1.41 and higher.
  • File Program Compare now allows basic or comprehensive ladder logic comparison.
  • When online with a PLC that has a Fatal error, the status bar and window title bar display the fatal error and the title bar will periodically flash.
  • The Enabled/Disabled state of an SF can be toggled within the SF editor.
  • In the SF editor, the Enabled/Disabled state is now shown in the title bar.

Solutions

  • Corrected a situation that randomly caused an application error in searches and cross reference builds.
  • Corrected a condition in 575 where RAM was wrongly identified as EEPROM, causing “unable to write network data” error.
  • Registry usage has been revised. Shared information (security, communication, etc.) is stored in a location accessible to multiple users. Personal settings (recent files, program setup, last online connection method) are stored for each user. This means that only users who are also a Windows administrators or who have been assigned rights to the appropriate parts of the registry can add, modify and delete the shared information. The software is now able to read registry entries when the user is not an administrator.
  • Text file import error messages have been improved.
  • Timeout for online Find for 565 has been fixed.
  • Support for VMM addresses has been added to the Copy, Paste and Delete address documentation functionality.
  • Cross Reference setup in Print Preview now retains user’s Address/Network Mode selection.
  • Corrected text file printing of SF programs: some characters to the far right were truncated.
  • In cross reference, contacts are now represented with backward brackets for easier identification. For example: a normally closed contact is ]/[.
  • Corrected a condition where copying timers and counters from one program to another did not copy the TCC documentation with the logic.
  • Corrected an application error in Replace Table that occurred when Copy Network Headers was selected and there were multiple output coils or the output coil was changed.
  • Changed the Analog Alarm Editor to store the Alarm Clamp SP Low value correctly.
  • When deleting an alarm, pressing ESC at the warning would not cancel the deletion. Now any action other than selecting Yes cancels the deletion.
  • Corrected a ladder editing situation in which selecting F4 (append) followed by F3 (insert new row) would result in “Error while attempting to display logic.”
  • Fixed application error in Replace Table for next replace.
  • Added Cross Reference implied addresses in Special Function instructions.
  • Corrected a time-out error that occurred when loading by parts – K memory and V memory.
  • NT Audit recording has been improved to more accurately record activity.
  • Valid range for the second count in an EDRUM has been changed from 0.001 – 32.767 to 0 – 32.767
  • Corrected an application error that occurred when cancelling a transfer to online.
  • Fixed a situation where printing only V-Registers causes an application error.
  • When inserting a column while on a multi-column box instruction, the insertion now occurs before the instruction.
  • Carriage return/line feed ASCII symbols are no longer displayed in the Documentation Window.
  • Corrected the delimiter selection in the Import Documentation. The delimiter expected was a tab even if the user selected comma, resulting in “Missing delimiter on line 1” errors.
  • Corrected a condition that sometimes caused the progress bar to stay visible after transferring logic and going online.
  • PLC Configuration now warns about reductions in the size of memory areas.
  • Fixed highlighting upon open in SF editor.
  • Improved the Activity Audit process to avoid duplicate “logic edited” records.
  • Corrected SMC instruction to allow complex inputs.
  • Fixed the print function in which documentation was printed even when not selected.
  • Corrected the inactive password timeout feature, which timed out immediately.
  • Printing now skips invalid addresses.
  • The Open dialog now refreshes when the user switches back browsing for FSS files after browsing for VP5 files.
  • If a fault exists, the software now displays “Unknown” in areas of the PLC Status dialog that references the status words.
  • Fixed reading SFP and SFS on 555 1104.
  • The Cross Reference report now prints documentation for addresses within the specified ladder range.
  • The timer for the password timeout now resets any time the User Security Options dialog is used.
  • Corrected a condition in which copying and pasting an address with the maximum tag, description, and comment lengths would cause an application error.
  • When editing documentation, the description now scrolls vertically when it contains more lines than can be displayed at once.
  • Corrected a situation in which the FasTrak security system Administrator Options/Select menu should have been disabled.
  • The activity audit text has been revised. File names appear in the original case.
  • Fixed Clear Network to correct calculation of memory sizes.

PLC WorkShop Suite for Siemens 505 v3.4 Release Notes

Features

  • Added a “Display Used/Display All” push button in the “Special Functions” dialog which toggles the contents of the Special Function Programs and Subroutines list boxes between all SFs or the used SFs only.
  • Added Password Security and Activity Auditing.
  • Added Hotkeys for the toggling of the display of documentation.
  • Add a Search & Replace Table dialog which allows up to 32 different ranges of addresses and instructions to find and replace with alternate values. This new feature is included with the original single addresses Find and replace dialog.
  • Added PLC Password Aliasing whereby the internal PLC password may be managed by an alias list.
  • Added support for use of the “Put” function for the imporation of network headers.
  • Updated the ladder compare feature.
  • Added ability to search for tags via case sensitivity.
  • Added a shortcut hotkey for turning Ladder Status on and off.
  • Added a “Print page info at” combo box to the “Page Setup” dialogs. The location (top or bottom) at which the page information (file name, date, time and page number) appears can be selected.

Solutions

  • Clarified notation used in the Search dialog between “addresses” and “registers.”
  • Corrected an error in the search within a DRUm instruction for a particular address/register.
  • Corrected an error in the Data Window for changing the value of a PID loop variable.
  • Corrected ladder status from turning off when moving out of an edit and back into Run.
  • Corrected format of imported TISoft description comments.
  • Users may now use Task COdes Per Scan for the 545-1103.
  • Corrected the use of TISoft hotkeys for One Shots and Box instruction mnemonics.
  • Added support for turning on and off Forcing on a contact with the use of the right mouse button.
  • Added a more detailed user warning when importing TISoft files whose ladder memory is greater than what is allowed for the PLC type.
  • Added a user error warning for 575 PLC type with EEPROM when displaying logic.
  • Corrected an error from the TEXT box instruction’s display of text strings greater than 40 characters from an imported logic file.
  • Corrected the display of parallel instructions within a network.
  • Corrected the merging of a ProfiBus binary file greater than 4kb.
  • Corrected problem of always printing Documentation regardless of whether it was activated or not.

PLC WorkShop Suite for Siemens 505 v3.30 SP1 Release Notes

Features

  • Support for the CP1613 (H1) communications module.
  • TCP/IP settings are now saved on a per machine basis, versus saving per user logged in.

Solutions

  • Corrected communication overrun error for H1.
  • Corrected “Append” hotkey F4; users can append new networks in the rung below the rung where the cursor is located.
  • Corrected WorkShop from crashing while performing an on-line Global Search in Address Mode.
  • Corrected default value for N for the MOVEW instruction.

PLC Workshop Suite for Siemens 505 v3.3 Release Notes

Features

  • Support for the H1 1613 communications module.
  • TCP/IP settings are now saved on a per machine basis, versus saving per user logged in.

Solutions

  • Corrected “Append” hotkey F4; users can append new networks in the rung below the rung where the cursor is located.
  • Corrected WorkShop from crashing while performing an on-line Global Search in Address Mode.
  • Corrected default value for N for the MOVEW instruction.

PLC WorkShop for Square D v6.20 Release Notes

Features

  • Added support for all versions of Microsoft Windows including 3.1, 95, 98, NT, 2000, Millennium, and XP.
  • Added support for Sylink board.
  • Added support for COM3 and COM4.

PLC WorkShop Suite for Siemens 505 v3.20 SP7 Release Notes

Features

  • New online demo mode. An online connection by direct serial connection, TCP/IP, TIWAY, FMS, or H1 allows logic programming and editing, documentation, display of status, printing, and all other online functions except Save to Disk for the first 25 logic networks.

Solutions

  • Corrected lockup when trying to access the My Documents or My Briefcase folder within Windows 2000 while running 505 WorkShop.
  • Corrected errors resulting when exiting 505 WorkShop while Status is on and active.
  • Corrected TISOFT file import error.
  • Corrected lockup editing Headers when going through Edit Documentation dialog box.
  • Corrected ability to select the print mode in the Print Cross-Reference dialog box when in Network Mode.
  • Corrected problem displaying discrete values for V and K registers in the Data Window.
  • Added LCFH and LCFL for the PACKLOOP function.

ControlShop v09/19/02 Release Notes

New Features in 505Server, v2.06

  • Added an interface to help support communication type backups within FTLogger. Also added a notification to PLCWorkShop and other clients in the event of a read failure.
  • Added more descriptive FMS error messages.

Bug Fixes in 505Server, v2.06

  • The server now accepts TCPIP addresses that contain 0.
  • The server now shuts down correctly after having been initiated by Wonderware.
  • Failure to initialize a COM port can cause an exception. This may not be detected by a release version.
  • The server no longer has to be shut down and re-started after experiencing a communications problem in FMS.
  • Fixed the deadlock sometimes experienced after having opened a COM port and receiving the error “Device is already open with different settings.”
  • No more server hang after closing a port.
  • Fixed the occassional error created by adding an OPC group.
  • Fixed a rare timing problem whereby an application error could happen when removing a packet while communicating online.

New Features in ModServer, v2.06

  • Add support for 4x bits in the form TEEEEE:BB or T:E:BB.
  • Added an interface to help support communication type backups within FTLogger. Also added a notification to PLCWorkSHop and other clients in the event of a read failure.
  • Added support for TCP/IP Dynamic Routing.

Bug Fixes in ModServer, v2.06

  • Its possible for the server to hang after closing a port.
  • Ambiguous PLC protocol errors 0xA and 0xB can have two different errors.
  • Fixed sending a Network equation of size 79 bytes to Quantum PLC.
  • Fixed communication to an E275 PLC, which while in an error state, the server get a SPF when an Attach is attempted.
  • Fixed the occassional error created by adding an OPC group.
  • Fixed a rare timing problem whereby an application error could happen when removing a packet while communicating online.

New Features in PLC5Server, v1.11

  • Added an interface to help support communication type backups within FTLogger. Also added a notification to PLCWorkSHop and other clients in the event of a read failure.

Bug Fixes in PLC5Server, v1.11

  • Fixed the possibility of the server hanging after closing a port.
  • Fixed a rare timing problem whereby an application error could happen when removing a packet while communicating online.

New Features in SLCServer, v1.11

  • Added an interface to help support communication type backups within FTLogger. Also added a notification to PLCWorkSHop and other clients in the event of a read failure.

Bug Fixes in SLCServer, v1.11

  • Fixed the possibility of the server hanging after closing a port.
  • Fixed a rare timing problem whereby an application error could happen when removing a packet while communicating online.

New Features in DemoServer, v1.11

  • Added an interface to help support communication type backups within FTLogger. Also added a notification to PLCWorkSHop and other clients in the event of a read failure.

New Features in FTAlarm, v3.00

  • Added graphics capabilities in the form of customizable alarm buttons. FTAlarm is separated into two views now; list view and graphics view.
  • Added support in the graphics view for DIB’s and Metafiles.
  • Added Undo/Redo capabilities to the graphics view.
  • Upgraded to FTServer 1.3 type library.
  • Added storage for remote and backup servers as well as backup communication types. The interface is not yet supported.

Bug Fixes in FTAlarm, v3.00

  • Fixed exceptions when displaying items such as the control in the device source config dialog.
  • Fixed exceptions when online and a loading a new configuration file from the Device Source Configuration dialog.
  • Fixed FTAlarm to be able to receive events from our newest servers.
  • Fixed a resource leak when creating a brush. This is the same bug that causes a lockup in WorkShop when a user does a large rewire or does many edits before verifying.
  • In WIN2000, when bringing up the open/save dialog, a lockup can occur if the “My Documents” or “My Briefcase” folder is selected. This is a known Microsoft problem.

New Features in FTLogger, v2.00

  • Added support for remote servers.
  • Added fault tolerance for communication types and servers.
  • Added import of Wonderware Comma Separated Value (CSV) files.
  • Converted log status window to a dockable window. This improves the interface by separating the log sheets from the log status window with “splitter ” type functionality.

Bug Fixes in FTLogger, v2.00

  • Corrected problem of two users being logged in to the same SQL database table, where client1 can get database errors after client2 connects to the database. This happens when client2 attempts to change the DATETIME field from Date/Time to Float or visa versa. This is most likely a problem because DATETIME is a primary field. Access is not a problem.
  • Corrected problem of getting duplicate row database errors from a logsheet that is using complex events.
  • Corrected problem of memory leaks and exceptions when online and attempting to modify the logging method to use complex events and there is an error with the event.
  • Corrected problem of no existing valid tables when going online with two log sheets, both logging addresses from the same device. Set up one of the sheets to log to a fixed column based database. Go offline with the log sheet that is logging to the column based database and edit the log sheet by adding an address (make sure the other log sheet is still online).
  • Corrected the exception when, after having loaded a log file with no log sheets, and previously having a log sheet up.
  • Corrected the issue of checking the span time to just before data is needed.
  • Corrected the import of Modicon documentation and converting 5-digit addresses to 6-digit.
  • Corrected the GPF when entering and then deleting a single address in a sheet.
  • Corrected the problem of when the timestamp in the log sheet is formatted to display only the date, only one log per day is permitted.
  • Corrected the problem within FTLogger when it may not be able to receive events from the newest servers making it impossible to get data values.
  • Corrected the problem of, when in Windows 2000, and when bringing up the open/save dialog, a lockup can occur if the “My Documents” or “My Briefcase” folder is selected. This is a known Microsoft problem. See knowledgebase article Q287087.
  • Corrected the problem of when attempting to open Access97 database files can sometimes bring up the error “unknown database format” when in Microsoft Access 97.
  • Corrected the problem of when changing database options from “Setup – Options” dialog will prompt the dialog that asks the user if they want to save their changes when exiting FTLogger. This implies that the changes are saved to a file when in reality they are saved to the registry when selecting “OK” from the options dialog.

New Features in FTTrend, v1.30

  • Upgraded to FTServer 1.3 type library.

Bug Fixes in FTTrend, v1.30

  • Corrected problem .CFG files created in most recent versions of FTLogger, FTDatawin, and FTAlarm are not compatible with FTTrend.
  • Corrected the problem where FTTrend may not be able to receive events from our newest servers making it impossible to get data values.
  • Corrected problem where, while in WIN2000, and when bringing up the open/save dialog, a lockup can occur if the “My Documents” or “My Briefcase” folder is selected. This is a known Microsoft problem. See knowledgebase article Q287087.

New Features in FTBatch, v1.10

  • Upgraded to FTServer 1.3 type library.

Bug Fixes in FTBatch, v1.10

  • Corrected problem where .CFG files created in most recent versions of FTLogger, FTDatawin, and FTAlarm are not compatible with FTBatch.
  • Corrected problem where, while in Windows 2000, and when bringing up the open/save dialog, a lockup can occur if the “My Documents” or “My Briefcase” folder is selected. This is a known Microsoft problem. See knowledgebase article Q287087.exceptions could occur when displaying items in the list in the device source configuration dialog.

New Features in FTDataWin, v1.31

  • Changed background colors in data sheet icons to make them more visible.
  • Upgraded to FTServer 1.3 type library.

Bug Fixes in FTDataWin, v1.31

  • Corrected problem where FTDatawin may not be able to receive events from our newest servers making it impossible to get data values.
  • Corrected problem where, while in Windows 2000, and when bringing up the open/save dialog, a lockup can occur if the “My Documents” or “My Briefcase” folder is selected. This is a known Microsoft problem. See knowledgebase article Q287087.

New Features in FT_OPCConfig, v1.02

  • Added support for Modicon TCP/IP setup 3 and 4.
  • Upgraded to FTServer 1.3 type library.

Bug Fixes in FT_OPCConfig, v1.01

  • Corrected problem where the SA85 route was not getting saved to the registry correctly. Only the first out of five values was being saved.
  • Corrected problem where exceptions could occur when displaying items in the list in the device source configuration dialog.

 

PLC WorkShop Suite for Siemens 505 v3.20 SP6 Release Notes

Features

  • Added a warning message while importing a TISoft file if number of Control Relays should be 1023 (or 511 depending on PLC type) and displayed as 32. TISoft will improperly display the number of Control Relays. User is prompted to open the file in TISoft and re-write the memory configuration (the user does not have to re-enter a value for any memory type).

Solutions

  • Corrected problem where editing documentation (CNTL-L) for a blank address, then entering an address with known existing documentation, documentation would not appear.
  • Corrected problem where printing Tags and Descriptions, only partial tags would print.
  • Corrected panel display for Run/Program for proper wording.
  • Corrected wording for a Remote Base Diagnostic error message.
  • Corrected problem in the “Find” drop-down list to correctly display last four addresses searched for.
  • Corrected problem when shading a network to copy and paste into a new network- horizontal shorts are kept.
  • Corrected problem with calculating TI_MOVE to include floating points.
  • Corrected problem with adding coils with pre-existing header documentation. When coil address is changed, existing header documentation (if any) is properly displayed.
  • Corrected problem with pasting duplicate Tags in to the Documentation window and dislaying an error message. Duplicate Tages are now checked for prior to adding them to the documentation list.
  • Corrected problem where doing a Find for output instructions (such as NOP or END) will properly display them in the their correct column.
  • Corrected problem with performing Global Find and not clearing the instruction type from a previous search.
  • Corrected problem where printing to a text file now includes Tags of less than multiple lines’ length.
  • Corrected problem where clicking on a string of text greater than 40 characters after receiving an error message. Text can now be edited to remove the extra characters.
  • Corrected problem where Read Only mode was not allowing attach Online with Doc only.
  • Corrected problem where long file and Network Headers with embedded carriage returns or line feeds will properly display.
  • Corrected problem with displaying the proper options of the Import Documentation window when selecting a particular format.
  • Corrected problem with exporting documentation to TISoft where all address types will have documentation. TISoft only imports values for C’s and Y’s; export now only will export to these value types.
  • Corrected problem where files using shared documentation would display an error during a save. Save function no longer checks for this documentation.
  • Corrected problem with importing international characters. Now supported.
  • Corrected problem when importing special function programs (SFPs) from TISoft when byte 253 was used.
  • Corrected problem when importing TISoft files and not reading a current cross-reference table. Table will now display as being not current upon import.
  • Corrected problem when importing Synonyms and Descriptors from a TISoft file. Import now terminates at the proper number of characters per the .syn file.
  • Corrected problem with memory leaks when merging U-memory.
  • Corrected problem when copying and pasting real addresses with no bits and their documentation.
  • Corrected problem when cancelling the build of the cross-reference table would disable logic Status while on-line.
  • Corrected problem when importing TISoft files that have 10 MOVE boxes in parallel.
  • Corrected problem with “Logic Store Record not found.”
  • Corrected problem with ladder memory doubling in size. Error would occur when a file is loaded on-line, then saved, then attaching again with the same file and saving by parts twice.
  • Corrected problem when undoing a network while off-line and the listbox not displaying the proper order of networks to be undone.
  • Corrected problem when editing documentation within a SFP and a real address is being used; user no longer receives “An Invalid Char was Entered.”
  • Corrected problem when deleting a network while on-line, user will be warned of a program change when exiting.
  • Corrected problem when performing a Find in a network, then in a Special Function, option for network address will not be selected but grayed out.
  • Corrected problem when using parentheses in a SF, to the left of the assignment operator; received “Invalid use of the assignment operator.”

PLC WorkShop Suite for Siemens 505 v3.20 SP5 Release Notes

Features

  • Added the ability to force NITP communications for all serial port connections, not just serial port communication through a modem.
  • Added in the Header Keyword Find when starting the find, and the focus is in an SFP, it will continue to loop around to the Ladder until all sections are searched once.

Solutions

  • Corrected problem where copying/pasting networks with rung headers into a NEW program, the headers appear in the pasted networks until they are validated. Then they disappear.
  • Corrected problem where if you enter in a tag row and description row value in program setup for ladder, and do Save As Defaults, and then do Restore Defs, the entries are swapped.
  • Corrected problem where the Program Setup dialog limited the maximum rows for description display to 5 instead of 7.
  • Corrected problem where the export dialog box for the Include group box did not always have the correct items checked or grayed, and depending on what Format was choose, the items sometimes then got reset to what should be checked and/or grayed.
  • Corrected problem where pressing Ctrl-L to edit the documentation on bit-of-word addresses, the Edit Documentation dialog opened to edit documentation on the word address.
  • Corrected problem where the ‘Header’ push button needed to be grayed when there was no address in the ‘Address’ edit box in the Edit Documentation dialog.
  • Corrected problem when attempting a ‘Save As’ to save a backup file name, although the error message which indicates backup files cannot be saved appeared, the window’s title changed to show the attempted backup file’s name.
  • Corrected problem where the Doc Window’s ‘Find’ dialog’s control settings were always set to defaults rather than retaining and setting the controls to the previous used settings.
  • Corrected problem in Header Keyword Find, where the dialog did not retain it’s proper settings when switching between Ladder and SF’s.
  • Corrected problem where in the Scale instruction in an SF, the low and high limit values must be real constants, and that error message displayed if 0 was entered for example, instead of 0.0. Rather than displaying the message, the whole number is now converted to a decimal.
  • Corrected problem where doing a Replace of an address in a SF MATH instruction, which had a length beyond one line deep, it only replaced the first occurrence.
  • Corrected problem when Online the 545-1101 with older firmware, where doing an edit in Run mode and validating, after continuing into edit mode, it would stay in Edit. Trying to put the CPU back in Run resulted in Comm Error in Hold mode. CPU had to first be put in Program Mode, and then in Run. This only happened when in Address mode.
  • Corrected problem where communicating to the PLC through the RS 232 port of the CP5434 FMS card, where the result was “Reading operational status. Received Data Length is invalid”.
  • Corrected problem where loading a file which contains Profibus I/O, online to a PLC, was not starting the I/O in Operate Mode.
  • Corrected problem where Read Only mode was not allowing attach Online with Doc only.
  • Corrected problem where in the Doc Editor, in the Tag field, the keyboard cut, copy, paste was not working, but the right mouse items worked.
  • Corrected problem where the Find/New in the Doc Editor, accepted all entries as only uppercase. This did not allow for a lowercase tag to be entered.
  • Corrected problem where the password dialog box for corporate customers was closing before the user could enter the password.
  • Corrected problem where the “Modify Doc” button in the SmarTune dialog and the “Modify Doc” menu selection and Ctrl+L keystrokes in the Data Window needed to be disabled when running in READ ONLY mode.
  • Corrected problem where in INSERT mode in the data window, if you had addresses in the window, and an insert was done over the top of them, the new addresses were displayed, but the new addresses were actually internally the same as the address where the Insert was done.

ControlShop V01/25/2002 Release Notes

New Features in 505Server, v2.04

  • Added the ability to force NITP communications for all serial port connections, not just serial port communication through a modem.

Bug Fixes in 505Server, v2.04

  • Corrected problem when using the Server for OPC the version number was not stored in the Registry.
  • Corrected problem where the port count was incremented twice during the autobaud com port opening, which resulted in the port count not fully decrementing at closing. Therefore, opening the com port subsequently, did not autobaud.

PLC WorkShop Suite for Siemens 505 v3.20 SP4 Release Notes

Solutions

  • Corrected problem where doing File Compare Online and comparing SF’s, some of the SF Headers were mismatching when they should not have.
  • Corrected problem where the Doc window “Delete” dialog did not delete the special Loop and Alarm addresses, which can be entered as REAL and INTEGER forms, such as (LKC, LKD, APVH, LPVH, etc.).
  • Corrected problem where clicking the “Next Addr” or “Prev Addr” in the edit documentation dialog, while using a special Loop or Alarm address, which can be entered as REAL and INTEGER forms, such as (LKC, LKD, APVH, LPVH, etc.), locked up the program.
  • Corrected problem where the key check checks until it finds one key with product support. It needed to go to other ports to check them all.
  • Corrected problem where the description field in the Cross Reference window was partially displaying the second line of the description.
  • Corrected problem where, when using a VMM address in an SF Math, and the address was VMMAD7B4C, the validate gave an error message. The B was being looked at as a Binary constant reference.
  • Corrected problem where the special Loop and Alarm addresses, which can be entered as REAL and INTEGER forms, such as (LKC, LKD, APVH, LPVH, etc.), could not be Imported from a delimited text file.
  • Corrected problem where a Bit-Of-Word address, such as V1.1 could not have it’s documentation edited.
  • Corrected problem where opening a file or importing a TISOFT file which had more than 32 rows of ladder in the same network, in the Windows format, would cause a GPF.
  • Corrected problem in Windows 98 with program online and in Run with status on, if a window was moved around, the window did not refresh the display properly.
  • Corrected problem where Paste with Rewire was ALWAYS rewiring with Doc included, even if it was not checked to do so.
  • Corrected problem where an error occurred doing a find after attempting to validate networks with 1 network validating and at least one does not.

PLC WorkShop Suite for Siemens 505 v3.20 SP3 Release Notes

Solutions

  • Corrected problem under Windows 98 only, where the Ladder window did not refresh properly when dragging it to a different location on the screen when Logic Status was turned on.
  • Corrected problem where the Network Header Paging setting was being performed in the print even if headers were turned off for the print.
  • Corrected problem where a GPF could occur after making approximately 128 on-screen edits due to a resurce leak.
  • Corrected problem where the PLC Operations pushbutton needed to be grayed in the PID Loop and Analog Alarm directories when running in Load Only Mode.

ControlShop v05/10/01 Release Notes

Bug Fixes in 505Server, v1.34

  • Corrected problem where VMM address types were not supported correctly as HEX address types.

New Features in FTAlarm, v2.00

  • Added Pager/Phone alarm response with text-to-speech.
  • Added ability to view alarm configuration while online.
  • Added toggle of descending and ascending sort when consecutively clicking on the sort-able columns for the alarm sheet and alarm status windows.
  • Added the ability to create a new alarm file via the “New” menu from beneath the “File” menu.
  • Added a 1000 error message limit to the modeless dialog that displays error messages while online. This was added to prevent a drain on memory.
  • Added a ‘response repeat time’ and ‘description static box’ to the Alarm Responses dialog. This replaced the feature of ‘responding to the alarm after a number of times triggered’. This affected the Print and Mail responses, where now the user can select a repeat time necessary in order for the Print or Mail to be executed.
  • Added a “wait” window with progress bar whenever shutting down FTAlarm after adding, modifying, or deleting alarm users. Encrypting users can be time consuming requiring this feature.
  • Added a user-configured message to be appended to print response status, which could serve as a set of instructions on how to handle the alarm situation.
  • Swapped locations of “Communications Type” and “Server” controls in the “AddPLC” dialog.
  • Added toolbar item for going online and offline.
  • Added automated alarm status message print based on an alarm status message count or time schedule.
  • Added separation of alarm status messages to “current alarm status” when online and “alarm status history” when offline. This prevents a slowdown when flushing the database while online and refreshing the alarm status window.
  • Added sorting menus to alarm sheet popup menu, and added sorting and refresh menus to alarm status popup menu.
  • Added toolbar item for configuring device source.
  • Added ability to sort the “prompt ack” dialog.
  • Added ability to clear alarm status messages from the database.
  • Upgraded MDAC to version 2.60.

Bug Fixes in FTAlarm, v2.00

  • Corrected problem where the splitter window did not always partition itself equally when starting up FTAlarm.
  • Corrected problem in import/export of alarms where our double quote delimiter used for simple equation constants and alarm user names posed problems when loading/saving in Excel. Now changed to single quote.
  • Corrected problem in import/export of alarms where active status always imported as TRUE.
  • Corrected problem where the timestamp incorrectly listed times from 12:00PM to 12:50PM as AM.
  • Corrected problem where address Formats for complex equations did not get verified.

New Features in FTLogger, v1.45

  • Swapped locations of “Communications Type” and “Server” controls in the “AddPLC” dialog.
  • Upgraded MDAC to version 2.60.
  • Added toolbar item for going online and offline.
  • Added toolbar item for configuring device source.
  • Decreased database access time by approximately 50% when using event ID names or spanning files.
  • Modified display and scrolling functionality in the log status window.
  • Lowered minimum periodic update rate from 100 Msec to 0 Msec.

Bug Fixes in FTLogger, v1.45

  • Corrected problem where the timestamp incorrectly listed times from 12:00PM to 12:50PM as AM.
  • Corrected problem where address Formats for complex equations did not get verified.
  • Corrected problem when receiving an error from any tab dialog within the log window setup, the dialog closed without allowing the user to fix the error.
  • Corrected problem when a complex event was set up, we could not re-edit the event and change it to a simple event expression.
  • Corrected GPF when the log sheet is set up to log via an event using a complex expression and the ‘log window setup’ tab dialog is brought up and “OK” is clicked.
  • Corrected problem where when we made changes to a complex expression or we change between complex and simple expression, the “Apply” button in the “Log Window Setup” dialog did not get enabled. Also, if we made any changes in the “Log Data” tab of the log window setup dialog, we did not get a warning that changes have been made and not saved before exiting FTLogger.

New Features in FTTrend, v1.27

  • Swapped locations of “Communications Type” and “Server” controls in the “AddPLC” dialog.
  • Upgraded MDAC to version 2.60.
  • Added toolbar item for going online and offline.
  • Added toolbar item for configuring device source.

New Features in FTBatch, v1.07

  • Swapped locations of “Communications Type” and “Server” controls in the “AddPLC” dialog.
  • Added toolbar item for going online and offline.
  • Added toolbar item for configuring device source.

New Features in FTDataWin, v1.24

  • Added toolbar item for going online and offline.
  • Added toolbar item for configuring device source.
  • Swapped locations of “Communications Type” and “Server” controls in the “AddPLC” dialog.
  • Upgraded MDAC to version 2.60.

Bug Fixes in FTDataWin, v1.24

  • Corrected problem where the timestamp incorrectly listed times from 12:00PM to 12:50PM as AM.
  • Corrected problem where address Formats for complex equations did not get verified.
  • Corrected problem when receiving an error from any tab dialog within the log window setup, the dialog closed without allowing the user to fix the error.
  • Corrected problem where when we made changes to a complex expression or we change between complex and simple expression, the “Apply” button in the “Log Window Setup” dialog did not get enabled. Also, if we made any changes in the “Log Data” tab of the log window setup dialog, we did not get a warning that changes have been made and not saved before exiting FTLogger.
  • Corrected GPF when the data sheet is set up to read via an event using a complex expression and the ‘data window setup’ tab dialog is brought up and “OK” is clicked.

ControlShop v02/22/01 Release Notes

New Features in ModServer, v1.50

  • Adding support for the Applicom PCI2000MBP board.

New Features in FTAlarm, v1.21

  • The default database update rate has been changed from every day to every 15 minutes to reduce the size of the alarm database

Solutions in FTAlarm, v1.21

  • Corrected problem where going offline or closing FTAlarm could occasionally cause lockups.

Solutions in FTBatch, v1.06

  • Corrected problem where running FTBatch continuously in online mode, eventually caused Stack Overflow.
  • Corrected problem where every server was starting when device names were added to combo boxes in the Batch setup dialogs.

ControlShop v01/25/01 Release Notes

Solutions in FTBatch, v1.05

  • Corrected problem where sometimes when opening an existing Batch Sheet, the full menu would not appear.
  • Corrected problem where the Column Number edit box and spin controls in the Column Setup dialog should not be enabled for batch sheets which are linked to an Access data base file. The column number should appear as static text for “linked” batch sheets.
  • Corrected problem when changing the order of columns for “manual” batch sheets, the data associated with the columns would not follow in the relocation.
  • Corrected problem where the user was limited to using a “trigger” PLC address only once in a batch sheet. Multiple batches within a batch sheet should be allowed to use the same address, but not the same address and trigger value.

ControlShop V01/22/01 Release Notes

Solutions in FTBatch, v1.04

  • Corrected problem where, if the selected table from the Microsoft Access file contained empty records, FTBatch would not load any other records into the batch sheet.

ControlShop v01/12/01 Release Notes

Solution in FTBatch, v1.03

  • Corrected problem when selecting a batch name field from the list of fields in the combo box, an error occurred saying that only text fields could be selected for the batch name.

ControlShop v12/22/00 Release Notes

Solution in FTBatch, v1.03

  • Corrected problem where VB clients would only work for the server that was most recently registered.

Solutions in Servers, ModServer v1.43, 505Server v1.33, PLC5Server v1.02, SLCServer v1.02, DemoServer v1.02

  • Corrected problem where an Excel or VB Demo could not be run if a different server other than the one you were using had been recently registered.

ControlShop v12/12/00 Release Notes

General Features and Overview for FTAlarm

  • FTAlarm monitors alarm conditions specified by the user across multiple devices. Alarms are entered in a spreadsheet format with up to 3150 Alarms per Alarm sheet. Triggered alarms can be logged, printed, audible wave and/or flashed to the screen. Configuring FTAlarm Communications.

New Features in FTAlarm, v1.20

  • Added support for complex expressions.
  • Added email response.
  • Added support for cut, copy, and paste of alarms in the alarm sheet.
  • Added support for importing and exporting alarms.
  • Added print of alarm configuration.
  • Added alarm status and alarm sheet sorting. Alarm status messages can be sorted online and offline by alarm tag, condition, severity or timestamp by clicking on the header control or selecting the appropriate menu item. Alarms in the alarm sheet can be sorted offline only by tag or severity when clicking on the header control or by selecting the appropriate menu item.
  • Added prevention of using a ‘.’ character in the device name because this is now used as a delimeter when entering a complex alarm equation.
  • Added prevention of using a double quote character in a user name because this is now used as a delimeter when importing and exporting alarms.
  • Added “Acknowledge All” button to the prompt acknowledge modeless dialog.
  • Changed Simple equation to match Complex equation by adding spaces and double equal (==) vs. single equal (=).
  • By request, changed the default colors for the alarm status messages.
  • When an alarm file is loaded, it will hold the path and file names for the config file (.CFG) and database file(s) (.MDB). If these files have been moved from their original location, a warning comes up allowing the user to browse for the files. We now perform a second search on the file(s) in the same directory as the file that was loaded before displaying the warning.
  • The command line option “/online” was added to be used in conjunction with a .ALM file name so that demo files can be automatically loaded in online mode.
  • The default medium low alarm color was hard to see and was therefore changed to light blue. The default communication error color (BLUE) was changed to brown so that it doesn’t match the low alarm default color.

Solutions in FTAlarm, v1.20

  • Corrected problem where loading a file while online with another file can cause an overwrite, especially if the file being loaded has more alarms than the file we are online with.
  • Corrected problem where Prev/Next Alarm was inaccessible via keyboard when Next/Prev is grayed but highlighted.
  • Corrected problem where pasting past the last row in the alarm sheet can potentially cause an exception.
  • Corrected problem where scrolling to cut by dragging mouse beyond window boundary did not work.
  • Corrected problem getting a lockup when trying to delete a device that’s being used in an alarm.
  • Corrected problem where errors returned from our server that are > 100 chars can cause an exception.
  • Corrected problem where doing apply after changing an alarm’s simple expression, disables keyboard usage in the Edit of alarm dialog.
  • Corrected problem where if we load a file into FTAlarm upon startup via the command line or double clicking in Windows Explorer, we cannot save to this file and the .cfg filename is incorrect.
  • Corrected possible overwrite when adding alarm status messages to the lower pane.
  • Corrected problem where it’s possible to get deadlock and potential database errors when going online and compacting a database while clearing out old database messages.
  • Corrected problem where alarm database warning that database already exists doesn’t display correctly in certain display modes including 800 x 600.
  • Corrected problem where F1 key does not bring up help.
  • Corrected problem where the calendar controls within the alarm status (lower pane) tab under setup options can disappear shortly after selecting them when a “flash window” response is being executed.
  • Corrected problem where if the current order or number of registered servers does not match a file that has been loaded, there could be a problem reading alarm values. i.e. the user could go online but it would appear that they are still in offline mode.
  • Corrected problem where when modifying a simple alarm operand via the edit operand dialog, the selected server in the combo box may not represent the configured server.
  • Corrected problem where if we load a file that has a server that is no longer registered, we receive an error even if no devices need to communicate to the server and we are unable to use the file.
  • Corrected problem where when the system display is set to use large fonts, the red values within the alarm equation in the upper pane can get cut off.
  • Corrected problem where using non-standard window font sizes can cause the alarm sheet rows to become crowded and possibly overlap text.

General Features and Overview for FTBatch

  • FTBatch is a stand-alone component of ControlShop. It allows multiple numeric values (called batches or recipes) to be written to one or more devices (PLCs) at a time. These values are displayed in the row and column spread sheet-like cells. Each Batch Sheet can have up to 255 rows and 255 columns. Each row of a Batch Sheet represents one batch. Each column represents one address in one device. All the values in a batch (row) are downloaded at one time. Although each can write to multiple addresses in multiple devices, each column refers to only one address in one device. These values can be entered manually or read from the numeric fields of external user-defined Access database files. The external Access files are named externalfile.MDB.
  • A Batch Sheet can communicate with multiple servers. Each server may include multiple devices. Multiple devices can be written to as long as the device belongs to a server to which the Batch Sheet window is communicating. One or more devices must be added to a server before any addresses can be added to a Batch Sheet window.

New Features in FTBatch, v1.02

  • When a batch file is loaded, it will hold the path and file names for the config file (.CFG) and doc. Database file(s) (.MDB). If these files have been moved from their original location, a warning comes up allowing the user to browse for the files. We now perform a second search on the file(s) in the same directory as the file that was loaded before displaying the warning.

Solutions in FTBatch, v1.02

  • Corrected problem where if we load a file into FTBatch upon startup via the command line or double clicking in Windows Explorer, the .cfg filename is incorrect.
  • Corrected problem where F1 key does not bring up help.
  • Corrected problem where errors returned from our server that are > 100 chars can cause an exception.
  • Corrected problem where if we load a file that has a server that is no longer registered, we receive an error even if no devices need to communicate to the server and we are unable to use the file.

New Features in FTLogger, v1.42

  • We now prevent the user from using a ‘.’ character in the device name because this is now used as a delimeter when entering a complex event.
  • Added support for complex expressions.
  • Added support for printing logged database files.
  • Added ability to allow user to limit number of status messages reported in the log status window.
  • When a logger file is loaded, it will hold the path and file names for the config file (.CFG), doc. Database file(s) (.MDB) and any log database files (.MDB). If these files have been moved from their original location, a warning comes up allowing the user to browse for the files. We now perform a second search on the file(s) in the same directory as the file that was loaded before displaying the warning.

Solutions in FTLogger, v1.42

  • Corrected problem where A stack overwrite existed regarding a message posting. This message is posted to the log status window to add a log message to the window during a logging session.
  • Corrected problem where being online in FTLogger with 505 server logbyrow.mdb. This database had three tables: device1, Remote-545, and Serial-545. Tried to create a ModServer window and connect to logbyrow. Got a warning that logbyrow was already in use. Hit No and changed to log.mdb which only had table “device1.mdb”. Tried to compact log.mdb and got a database error that said it couldn’t find “Remote-545” table.
  • Corrected problem where the popup window (via right mouse button) while in the log status window shows “options” menu but clicking on it fails to display the dialog.
  • Corrected problem where log successes are defaulted to on.
  • Corrected problem where creating a new log sheet including logging by column with a few addresses, going online to log, closing this program, and then starting a new log sheet offline using the same column database and putting in the same addresses, saving the program, then reloading the saved program and going online, the column database reports values of addresses in the event column.
  • Corrected problem where pasting past the last row in the log sheet can potentially cause an exception.
  • Corrected problem where scrolling to cut by dragging mouse beyond window boundary does not work.
  • Removed “Demo” from menu list under “Mode”, and removed “Demo” from the “Mode” combo box in new log window dialog now that we have a demo server.
  • Corrected problem where errors returned from our server that are > 100 chars can cause an exception.
  • Corrected problem where column database values were incorrect or duplicated if log was run through daylight savings time.
  • Corrected problem where text color for the second to last log status message is blue after we receive 2 more status messages than the configured max.
  • Corrected problem where if we load a file that has a server that is no longer registered, we receive an error even if no devices need to communicate to the server and we are unable to use the file.
  • Corrected problem where if we load a file into FTLogger upon startup via the command line or double clicking in Windows Explorer, we cannot save to this file and the .cfg filename is incorrect.
  • Corrected problem where using non-standard window font sizes can cause the logger sheet rows to become crowded and possibly overlap text.
  • Corrected problem where F1 key does not bring up help.

Solutions in FTTrend, v1.25

  • Corrected problem so we only display point count of active window.
  • Corrected problem to display a Y-Axis range of -1 to 1 correctly.
  • Corrected problem when two graph windows are open with the same device(s) used in each window and the windows are online, that did not allow the second window to display values correctly.
  • Corrected problem where graph font size was not being set when loading from a file.
  • Corrected problem where F1 key does not bring up help.
  • Corrected problem where a pen displayed with a device did not fit on the screen.
  • Corrected problem when adding a device online and adding a point using that device to an online graph, the point did not update correctly.

New Features in FTDataWin, v1.22

  • We now prevent the user from using a ‘.’ character in the device name because this is now used as a delimeter when entering a complex event.
  • Added support for complex expressions.
  • When a data window file is loaded, it will hold the path and file names for the config file (.CFG) and doc. Database files (.MDB). If these files have been moved from their original location, a warning comes up allowing the user to browse for the files. We now perform a second search on the file(s) in the same directory as the file that was loaded before displaying the warning.

Solutions in FTDataWin, v1.22

  • Corrected problem of memory leaks when creating or opening registry keys.
  • Corrected problem where attempting to add a device or verify an address belonging to a Server that was unable to be loaded can give an exception.
  • Corrected problem where pasting past the last row in the data sheet can potentially cause an exception.
  • Corrected problem where scrolling to cut by dragging mouse beyond window boundary does not work.
  • Corrected problem where errors returned from our server that are > 100 chars can cause an exception.
  • Corrected problem where if we load a file that has a server that is no longer registered, we receive an error even if no devices need to communicate to the server and we are unable to use the file.
  • Corrected problem where if we load a file into FTDataWin upon startup via the command line or double clicking in Windows Explorer, we cannot save to this file and the .cfg filename is incorrect.
  • Corrected problem where using non-standard window font sizes can cause the data sheet rows to become crowded and possibly overlap text.
  • Corrected problem where F1 key does not bring up help.

ControlShop v08/28/00 Release Notes

  • This latest release of ControlShop now has 2 new Clients. FTAlarm, and FTBatch. You can run these clients in demo mode.

General Features and Overview for FTAlarm

  • FTAlarm monitors alarm conditions specified by the user across multiple devices. Alarms are entered in a spreadsheet format with up to 3150 Alarms per Alarm sheet. Triggered alarms can be logged, printed, audible wave and/or flashed to the screen. Configuring FTAlarm Communications.

General Features and Overview for FTBatch

  • FTBatch is a stand-alone component of ControlShop. It allows multiple numeric values (called batches or recipes) to be written to one or more devices (PLCs) at a time. These values are displayed in the row and column spread sheet-like cells. Each Batch Sheet can have up to 255 rows and 255 columns. Each row of a Batch Sheet represents one batch. Each column represents one address in one device. All the values in a batch (row) are downloaded at one time. Although each can write to multiple addresses in multiple devices, each column refers to only one address in one device. These values can be entered manually or read from the numeric fields of external user-defined Access database files. The external Access files are named externalfile.MDB.
  • A Batch Sheet can communicate with multiple servers. Each server may include multiple devices. Multiple devices can be written to as long as the device belongs to a server to which the Batch Sheet window is communicating. One or more devices must be added to a server before any addresses can be added to a Batch Sheet window.

Bug Fixes in FTLogger, v1.41

  • Corrected problem where attempting to add a device or verify an address belonging to a Server that was unable to be loaded can give an exception.

ControlShop v08/14/00 Release Notes

Features in 505Server

  • Increased maximum communication packets per port from 256 to 4096 to allow the Logger to log up to 25,000 addresses in one log sheet using TCP/IP.

Solutions in 505Server

  • Corrected potential errors such as “invalid data sent with packet” when viewing certain addrs.
  • Corrected problem being unable to write to 32-bit non-real loop and alarm addresses using TBP protocol, and being unable to write to 32-bit non-real TCC and DSC types using NITP protocol.
  • Corrected problem where server could have reported wrong values when requesting 32-bit signed values.
  • Corrected possible GPF if modifying an existing event.
  • Corrected problem where it was possible to get an event from the server telling the client that all data in a group has been read when in fact some data may not be read yet.
  • Corrected “Server Error. Address is out of Range” when entering a Loop or Alarm value in the Data Window that is in the new limit for the 555-1105/6.

Solutions in ModServer

  • Corrected problem where TCPIP could not handle the same IP address assigned to different ports, resulting in Modbus-TCP/IP bridge not working correctly.
  • Corrected problem of only supporting a max TCPIP ports of 26 when it should have been 256.

Solutions in FTTrend, v1.24

  • Corrected GPF when zooming in less than one second.
  • Corrected menu problem when loading a file with the child window maximized.
  • Corrected problem when adding a realtime point to a first Y-axis when there is more than one Y-axis and the last point exists in the 2nd Y-axis. This did only occur when adding points Online.

Features in FTLogger, v1.40

  • Added capability to now support the use of Microsoft Access 97 files.
  • Added the ability to log to a column data base.
  • Made modification to now change the DATETIME field type to either DATETIME or FLOAT depending on the update rate.
  • We now allow setting the max size a file can reach. Additionally the user is allowed to span to a new file when this occurs.
  • Modified import where if importing doc and “Verify Doc” is checked, we may receive an error if a duplicate tag was found that was attached to a different address. The only option was to select OK and not import the duplicate tag. We now give two additional options. In addition to ignoring the duplicate tag, the user can cancel the import at this point or overwrite the existing tag with the new tag..
  • Added “Demo” mode in addition to offline and online modes which can be accessed under the main menu “Mode”. This mode is similar to offline except that random data is generated, displayed and logged for each value.
  • Added ability to do a cancel of doc import/export.
  • Added ability to overwrite doc as well as merge doc during an import of documenation.
  • Increased the ability to log up to 1500 addresses in one log sheet.
  • Added capability to now prevent the user from using the same log database file across log sheets.

Solutions in FTLogger, v1.40

  • Corrected problem being unable to import a tab separated doc file.
  • Corrected problem where comma separated files saved in excel (as .CSV) by default do not show up in the documentation import/export browse dialog.
  • Corrected problem where during an export of doc, default extensions are not getting tacked onto the filename in the “Text File” edit box if an extension is not listed.
  • Corrected error message displayed when entering an invalid value for max logger rows. The valid range read 10-1000. Now reads 5-1000.
  • Corrected item when logging values to a database, if there is a database error, not all of the values in the logsheet get updated.
  • Corrected problem where it was possible to create a log sheet without running a server, thus making it impossible to create a device for the log sheet.
  • Corrected problem where selecting “OK” from the event acknowledgement dialog could give an exception if we entered “log window setup” from the “setup” button in the new log window dialog.
  • Corrected problem where Log sheets that are iconized were not logging data to the database file.