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.
New Features in ModServer, v2.04
Added the ability to swap SA85 Paths in the Driver, so that more than 8 PLCs can be attached at the same time.
Bug Fixes in PLC5Server, v1.10
Corrected problem where the wrong message was returned for some functions when the Demo mode timer ended and the server was disabled.
Corrected problem when the status of a packet was changed between reads, a parameter indicating that data was changed, was never reset so that all following events to the client always indicated that data was changed even though it may not have changed from the previous read.
Corrected problem where the Server DLL files were not getting overwritten when installing over older versions. Also adjusted the .EXE file version to match product version in InstallShield version comparison.
Corrected problem where some data items were being updated and new updates were sent prior to all data items getting the first update. This happened when 2 or more ports were involved in the update of the data with at least one port using multiple packets. This resulted in voids in the column based database in FTLogger.
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.
Bug Fixes in SLCServer, v1.10
Corrected problem where the wrong message was returned for some functions when the Demo mode timer ended and the server was disabled.
Corrected problem when the status of a packet was changed between reads, a parameter indicating that data was changed, was never reset so that all following events to the client always indicated that data was changed even though it may not have changed from the previous read.
Corrected problem where the Server DLL files were not getting overwritten when installing over older versions. Also adjusted the .EXE file version to match product version in InstallShield version comparison.
Corrected problem where some data items were being updated and new updates were sent prior to all data items getting the first update. This happened when 2 or more ports were involved in the update of the data with at least one port using multiple packets. This resulted in voids in the column based database in FTLogger.
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.
Bug Fixes in DemoServer, v1.10
Corrected problem when the status of a packet was changed between reads, a parameter indicating that data was changed, was never reset so that all following events to the client always indicated that data was changed even though it may not have changed from the previous read.
Adjusted the .EXE file version to match product version in InstallShield version comparison.
New Features in FTAlarm, v2.21
Forced device settings version on a load of a .ALM file. This allows the Modicon server to know that this is a data acquisition client, rather than a programming client, and can be swapped out if communicating via MB+.
Bug Fixes in FTAlarm, v2.21
Corrected problem where loading a file from the command line caused an exception.
New Features in FTLogger, v1.53
Forced device settings version on a load of a .LGR file. This allows the Modicon server to know that this is a data acquisition client, rather than a programming client, and can be swapped out if communicating via MB+.
Added the ability clear out old database logs on a timed basis for both column and row databases.
Bug Fixes in FTLogger, v1.53
Corrected problem where logging to a SQL database faster than once per second could create timestamps that were off by 2 days because a SQL DateTime starts at Jan 1, 1900 while a "DATE" type starts at Dec 30, 1899 (2 days apart). We now adjust for the days discrepancy.
Corrected problem where database errors could occur when first logging to a SQL database once per second or less frequent, then changing the update rate to more frequent than once per second.
Corrected problem where "Span File By Time" check box with column based database options did not get set correctly.
Corrected problem where exceptions could occur when displaying items in the list in the device source configuration dialog.
New Features in FTTrend, v1.29
Forced device settings version on a load of a .TRN file. This allows the Modicon server to know that this is a data acquisition client, rather than a programming client, and can be swapped out if communicating via MB+.
Bug Fixes in FTTrend, v1.29
Corrected problem where exceptions could occur when displaying items in the list in the device source configuration dialog.
New Features in FTBatch, v1.09
Forced device settings version on a load of a .FTB file. This allows the Modicon server to know that this is a data acquisition client, rather than a programming client, and can be swapped out if communicating via MB+.
Added feature where the FTBatch application is split into two modes, the "Development" and "Runtime" modes. The Development mode is essentially FTBatch as it was originally written and designed. Batches are created and edited in the Development mode. The Runtime mode simply displays summary information of the batches found in a specific .FTB file and downloads event and manual batches.
Added ability where batches can be assigned a "weighted factor". This means that numeric values in individual batch sheet columns can be designated as weighted. These weighted values are multiplied by the weighted factor before being downloaded to a PLC. For example, a column has been designated as a weighted column. It's original value, which is to be downloaded to a PLC, is 25. The weighted factor for that batch is 125%. The value 25 is multiplied by 1.25 and the value 31.25 is downloaded to the PLC.
Bug Fixes in FTBatch, v1.09
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 exceptions could occur when displaying items in the list in the device source configuration dialog.
New Features in FTDataWin, v1.30
Added support for SQL Server, Oracle, and other databases.
Forced device settings version on a load of a .DWN file. This allows the Modicon server to know that this is a data acquisition client, rather than a programming client, and can be swapped out if communicating via MB+.
Bug Fixes in FTDataWin, v1.30
Corrected problem where a resource leak occurred each time colors were repainted on the window. After 128 times, it could have caused a lock up.
Corrected problem where exceptions could occur when displaying items in the list in the device source configuration dialog.
New Features in FT_OPCConfig, v1.01
Added a version number to the config settings in the registry for each device. This was necessary for the Modicon server so it would know if it can swap out MB+ lines.
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.
