Copyright (©) 2002-2007, Jemmac Software Ltd
--------------------------------- ST 4.2 - released 13th July 2007 --------------------------------- Summary: NetAPI network time outs, stQuickTrend, revised Auto scale logic. For a more comprehensive review of the enhancements in this release see the New Features section of the online help (see: http://www.sapphiretrend.com/NewFeatures). Enhancements ------------ stPro 0630: The Auto pen scaling logic has been revised to use the Standard Deviation of the data values. This should reduce the chances of pens set to Auto scale mode going off scale when new data arrives, or when the plot is zoomed or panned. 0629: A much tighter tolerance of 5% is now applied to pens that are in Auto scale, and for whom the value is flat lining. Previously a range of 50% was used, which often biased the Group scales if such pens were included in a group. 0626: A new User Preference has been added called "Display Value Suffix". This allows the user to optionally 'hide' the value suffixes used to delimit Uncertain and Interpolated data when connected directly to an HDA OPC Server. 0623: The default User Preference have been changed to use Arial font. The palette entries for "Window" and "Off-scan" have also been revised. 0619: Uncertain qualities are now displayed with a good line style. The value is delimited with a 'U' to indicate that the OPCServer has marked the data as Uncertain. 0614: stPro now logs the release and build versions in its log files to aid remote debugging. 0612: The HDA Item Property OPCHDA_STEPPED is now used to determine whether to draw a Stepped or Interpolated trend line for direct HDA OPC connections. This produces a genuine step whereas pervious releases used a ramped line to depict the change. stQuickTrend New Product introduced for V4-2. Sapphire Collector 0149: Added a new Performance item called process.privbytes (Private Bytes) to display the amount of memory allocated to the Collector that is not available for use by other processes. 0142: Revised the memory management strategy to age mapped memory based on when it was last referenced and un-map accordingly. This will mean that the Collector tends to run with minimal memory requirements rather then at the maximum as was previously the case. 0138: The Collector now logs messages to the stManager Summary tab when an OPC Server returns an OPC Group refresh rate that does not match the rate requested. 0134: Added a new Collector summary statistic for 'uptime'. The value can also be trended as a performance item called process.uptime. 0133: The Collector can now optionally use the OPC GetStatus method when detecting OPCServer failover. The setting is on a per DL basis. 0132: The Collector now uses a timeout in all Network API calls when communicating with the Sapphire clients reducing the chances of a Collector failure locking a Sapphire client. 0131: The user can now define that items should be automatically downgraded From Auto to Manual resolution mode if Automatic resolution fails. 0129: OPC reads can now be broken into 'chunks' to reduce the loading on poorly performing OPCServers. 0128: The user can now specify whether items that have been marked as invalid by the OPCServer should be automatically turned offline by the Collector. 0125: The resolution logic has been revised to search for the Description and Engineering Units if they are not defined in the standard OPC item properties. The locations and Item properties to use can also be configured by the user via the registry. stManager 0167: The DL tab now has Simple and Advanced views to hide the more complex setup options unless the are required. 0166: A conversion function has been added to convert the common OPC error codes to more meaningful text strings. 0165: The number of OPC items to read in a single call can now be set on a per DL basis. 0164: The user can now disable the logic to automatically turn invalid items offline on a per DL basis. 0163: The Auditing tab now has an option to display the current log file. Note, this is only available when the stManager is running on the same node as the Collector. stTabularHistory 0089: It is no longer necessary to have a valid connection in order to be able to load a Tabular HIstory file. 0086: The logic employed when using Scientific notation has been revised to make better use of the available display space. stOCX 0062: A timeout is now employed on all NetAPI messages to reduce the changes of the OCX being 'hung' when not receiving a timely response from the Collector. This guards against both lock ups in the Collector and also more general TCP/IP network performance issues. 0061: A common timeout has been implemented where multiple instances of stOCX are using the same IO thread. This occurs where the OCXs are being hosted within a common container where each OCX is using the same data source. Installshield 0049: There is now an option to install without automatically starting the Sapphire Collector. 0046: Added the desktop and menu options for stQuickTrend. Bug fixes --------- stPro 0644: Fixed a potential crash when using 'Copy to all' for pen scales when the source pen is linked to another pen. 0643: Addressed a potential crash when browsing for connections and hitting the cancel button whilst the registry browse was still in progress. 0642: Duplicate entries in CSV file loads caused the data and item names to become misaligned in the resulting trend. 0641 The CSV file load logic now assigns the filename only to the Data Location field for the items being loaded. Previous releases used the fully qualified file name which resulted in very long item names, which were then difficult to work with within stPro. 0639: Plot rendering issue whereby plot size changes could cause the time axis and the plot to to become unsynchronised. 0638 Fixed a rendering problem when closing the Tools->Edit Data Source dialog when editing the details of a Sapphire Collector. 0637: stPro was not correctly reporting errors returned when saving export definition files. Preceding releases incorrectly reported that "The operation completed successfully. Do you wish to overwrite?". 0632: Fixed a potential stack dump when unmapping pens from a sequence where other pens were linked to the pens being removed. 0631: Addressed a problem where trending a pen whose values are always Nan, and which was in Auto scaling mode would force the scales for all 'Auto' pens to be recalculated each time data was fetched. 0627 The Pen ordering was incorrect for Stacked Graph styles where more than two pens were mapped. 0625: It was possible for stPro to hang on file load when loading a session with a reference to a locally registered OPCServer. 0622: The transition from bad to good data was not being properly positioned when in stepped mode. 0616: The Automation Interface IsValidItem method had transposed the return codes for a 'bad item' and an item that is 'still being checked'. 0617: The pen Filter was not working for Virtual Items. 0615: It was possible to crash stPro by closing the print preview window. Sapphire Collector 0148 On startup a failure to add the first item for a DL within an SDP could cause all of the items for the DL to not be managed correctly. Attempts to plot these points would then cause the trends to stop updating. 0147 The Item status was not being correctly set when trying to add items to a group for an OPCServer that was unreachable as the host node was not running. This could cause trends to ‘stick’ whilst waiting for netwrok timeouts to occur. 0146: The Collector was incorrectly purging the log files back to the default version limit of 10 files. 0145: DLs configured to use GetStatus checking can cause subsequent read items calls to be made without first adding the necessary items into the OPC server’s group 0144: Fix for LocateFreeBlock not always ensuring the total amount of space required is released when it is necessary to first free space before returning a block 0143: Fixed a memory leak caused by nightly tag dump processing 0141: Addressed a possible deadlock when trying to resize an SDP. 0140: The Collector was not reporting errors creating export definition files correctly. 0139: It was possible for the Collector to crash if it opened an unitialised SDP file. 0137: The Collector was incorrectly requesting an update frequency of 1 second for Cache reads, regardless of the actual frequency specified for the items in the OPC group. 0136: Fixed problem where the Collector was incorrectly using memory that had failed to pin, when returning data to stPro. 0135: The DL item counts were incorrect for items that have 'yet to be added' to an OPCServer group. 0130: Fixed a problem preventing items added via a dialog from being automatically resolved. 0127: Fixed a audit line which was incorrectly reporting using a null pointer. 0126: Addressed a problem where on rare occasions data collection could be performed twice (or more) for a single timestamp. stTabularHistory 0090: Addressed a possible lock up when loading a Tabular History file that does not have a Collector defined. 0088: The IsValidItem API had transposed the return codes for 'bad item' and an item that is 'still being checked'. stTHOCX 0010: The IsValidItem API had transposed the return codes for 'bad item' and an item that is 'still being checked'. stOCX 0060: The IsValidItem API had transposed the return codes for 'bad item' and an item that is 'still being checked'. Installshield 0048: The OPCServer install choice did not enabkle the next button. 0047: Corrected the conditional delivery of the OPC Foundation merge module so that it is always installed. |