hydrotel v4.0 release notes - hydrological services america · ice3 fx configuration send may cause...

1

HydroTelTM Incremental Release Notes

NOTE: iBETS refers to the Bug/Enhancement Tracking System available at http://data.hyquestsolutions.co.nz/iBETS/. Case details can be viewed, comments added and new cases raised by registered iBETS users. If you would like to become a registered iBETS user please email [email protected].

Version 4.23.0.x – 1st August 2016

General Comments

This release includes some new features and bug fixes, plus routine upgrades to the integrated third-party component libraries such as charting and reporting.

Client

New Features/Enhancements

New variant added to "Sensor String" object type for ascending datasets. iBETS 1899

Added server expiry code entry tool in Config->System->Settings form. iBETS 1898

Add an alarm trigger type to alert that a point is "flat-lining" (no change in value over time). iBETS 499 Bug Fixes

Journal entry export option exports only 100 characters of the entry text. iBETS 1869.

Intermittent exception on startup when favourite used in last session. iBETS 1874.

Display format (number of significant places) is not consistently applied. E.g. to plot Y axes and some edit fields (alarm settings). iBETS 1883.

Changing a logger's status does not get logged in the change log. iBETS 1902

iCE3 FX sensor configuration issue and also prevent zero multiplier ever being accepted. iBETS 1908

Very intermittent access violation in method SaveConfig when closing the client or “cannot perform this operation on a closed dataset” exception when starting the client. iBETS 1825

Server New Features/Enhancements

Add an alarm trigger type to alert that a point is "flat-lining" (no change in value over time). iBETS 499 Bug Fixes

If license expired, server should still able to be connected to and then report the status. iBETS 1653

Server diagnostic logging timeout not respected if debug is enabled while server running. iBETS 1747

Ensure all modified analogue output points are fully committed before being sent to a device iBETS 1909

Comms Agents Bug Fixes

iCE3 FX configuration send may cause main sensors to stop logging. iBETS 1897

Important Note: Upgrading from versions earlier than V4.22

If you are upgrading from a HydroTel™ version prior to the most recent previous release, you must incrementally upgrade the database with each of the skipped versions. This can be done by either sequentially running the upgrade installers on the HydroTel™ server machine or else executing each version’s upgrade SQL script. The HydroTel™ upgrade installer requires a database that is compliant with the previous version. Please contact HyQuest Solutions for assistance and installers / scripts before upgrading out-of-date systems.

http://data.iquest.co.nz/iBETS/

mailto:[email protected]

2

TDDataPush Agent Bug Fixes

Every event log entry is duplicated multiple times. iBETS 1871

Database query to retrieve samples silently fails if number of records in result set is high. iBETS 1911

Transfer Agent


Added support for exporting of camera images to files (new DLL). iBETS 704

SMS Agent


New SMS agent (HydHTTPSMSAgent) using web services now available. Currently supports Vodafone MultiTxt (NZ) and ESendex (Australia). iBETS 403

Utilities


Add support to HydMetServiceExport for logging activity to file. iBETS 1892

Watchdog Agent


Added support for exporting of camera images to files (new DLL). iBETS 704

Database New Features/Enhancements

Log manual and automatic SMS "GOL" requests to the comms log (linked to the logger). iBETS 1648

Provide database diagramming as part of deployed schema. Diagram scripts are located in C:\Program Files (x86)\iQuest\Updates\DBDiagrams iBETS 1179

Bug Fixes

Exception if there is a duplicate IMSI while processing the automatic update of IMSI in the SIMs table on a logger call in. iBETS 1851

System Monitor


Added check that the SQL Server Native Client is installed on the machine when the FireDAC® database settings are saved. This is vital for reliable operation and is easy to overlook on new installations.

3

Version 4.22.0.xa – 1st June 2016

General Comments

This release includes some new features and bug fixes, plus routine upgrades to the integrated third-party component libraries such as charting and reporting. The ‘a’ minor patch release includes a few small bug fixes.

Client


Configuration of batch file/command for Reporting Agent to run after creating a report. iBETS 1849.

Added checkbox to loggers form inhibit post unload actions. iBETS 1819.

Configuration of Active/Passive FTP mode for iCE3 FX and iRIS 350FX. iBETS 1856.

New user profile setting to display data referenced to daylight savings time. iBETS 528.

Added option to save FX device’s configuration as a PDF report. iBETS 752.

Added tool to check for and obtain logger firmware/software cabinet files from web repository. iBETS 1658.

Multiple barrage gates object plug-in enhanced to provide proportional control. Bug Fixes

Alarm edit form does not permit entering of negative numbers for activate or reset values. iBETS 1848.

Logger's IMEI field is not editable. iBETS 1846.

Telemetry User role not able to unload loggers or send GOL commands. iBETS 1853.

Log filters only use the first filter word and ignore any others. iBETS 1836.

Poll Groups form generated exception on opening. (Due to third party grid component change).

Intermittent exception on startup when favourite used in last session. iBETS 1874

Journal entry export option exports only 100 characters of the entry text. iBETS 1869

Can't delete user: Foreign key constraint exception. iBETS 1877

Comms log limited to 100 records even though options are set for more than this. iBETS 1873


Added function to support inhibiting of post unload actions. iBETS 1819.

New actions - UnloadCatchment and UnloadDistrict. iBETS 1860. Bug Fixes

Custom date/time format string is not applied. iBETS 1839.


UDP interface: Acks not being received by remote device, causing multiple call-ins. iBETS 1820.

Reporting Agent New Features/Enhancements

Added support to run a local batch/command file after creating a report. iBETS 1849.

Transfer Agent


New HydroTelExtern_Image plug-in to export camera images. iBETS 704.

Iridium Agent Bug Fixes

Iridium email importer may loop if email marked for deletion not removed on the mail server. iBETS 1832.

Database Bug Fixes

Unloads requested for a non-pollable (via TCP Server) device may queue multiple unnecessary “GOL” SMS messages. Stored procedure [sp_HydroTel_Sys_SendLoggerSMS] updated. iBETS 1832.

4

Version 4.21.0.x – 1st December 2015

General Comments

This release features the new HydroTel™ Web Services API component. It also includes some new features, fixes to a number of bugs and upgrades to the integrated third-party component libraries.

Client


Provide option to inhibit unloading of camera images via a particular interface. iBETS 1807.

Alarm Types configuration form reviewed and better interlocks added to prevent contention. iBETS 1765.

WUDMS journal now editable by users with Telemetry User role. iBETS 1818. Bug Fixes

Ensure a logger/device cannot be configured to have itself as its own parent. iBETS 1799.

Error in SQL query in reports editor causes a database exception. iBETS 1790.

Favourites tree does not initialise for those users without full administrator access level. iBETS 1762.

Improved custom view charting to allow moving and sizing of the chart. iBETS 1777.

Telnet Gateway Interface Params: IP address field should support non-numeric addresses. iBETS 1815.

Improved support for managing the iRIS 350FX sampler configuration. iBETS 1794.

Separate data view mode is not remembered when client is closed. iBETS 1814.

Automatic refresh of data plots / details is intermittent or stops when in custom tile view mode. iBETS 1588.

Server

Bug Fixes

Scheduled report actions do not run. iBETS 1779.

Poll groups containing parents from a parent-child relationship fail to unload the children if the parent has no associated points. iBETS 1725.

Web Services API New Features/Enhancements

New Web Services API component that provides access to HydroTel™ via JSON.

Comms Agents


Provide option to inhibit unloading of camera images via a particular interface. iBETS 1807.

Reporting Agent


Support including a custom message string or the alarm string in a Fast Report®. iBETS 1805.

FTP Agent


Added support for SFTP file transfer over SSH. iBETS 1613. Bug Fixes

Agent made no use of the 'Failed' folder if a file could not be transferred. iBETS 1816.

5

SMS Agent

Bug Fixes

SMS modem may appear locked up, but is in fact waiting for message closure command. iBETS 1817.

Transfer Agent

Bug Fixes

WRB plug-in: UTCOffset configuration parameter should support fractional offsets (e.g. +9.5) iBETS 1812.

Watchdog Agent

Bug Fixes

Watchdog should detect and handles failures on all agent threads, not just ‘Main’. iBETS 1712.

Utilities


AvgSum utility - added support for scalar averaging (e.g. for wind direction). iBETS 1813.

System Monitor


Added "Test Connection" tool to Fire DAC® database connection configuration form. iBETS 1612.

6

Version 4.20.0.x – 3rd September 2015

General Comments

This release contains includes some new features, fixes to a number of bugs and also upgrades to the integrated third-party component libraries.

Client


Added support for customisable object "views" to enhance the site level display. iBETS 1659.

Improved management of logger programming. Also the program status view for iCE3FX didn't work. iBETS 1736.

Automation->Data Transfer viewer. Improved usability to aid re-export on a per-site basis. iBETS 931. Bug Fixes

Cannot delete last sample in quarantine view. iBETS 524.

"Dial Str" text may show previous dial-up logger's details after selecting a non-dial-up logger. iBETS 1727.

Sensor String (contour plot) plot may fail with ParseNumericChar function not found. iBETS 1734.

Creating/cloning a new logger should also generate a default entry in the SIMs table. iBETS 1736.

Can't add a new trace to a favourite if a trace other than the last one was previously deleted. iBETS 1750.

Wind rose plot. Cannot print or export to clipboard. iBETS 1721.

Cloning a logger creates SIMs table entry for the logger being cloned instead of new logger. iBETS 1761.

Comms Agents

Bug Fixes

TD Server protocol may create samples in HydroTel with a quality code of 0. iBETS 1748.

RTS control timing problem with legacy radio interfaces on some USB->serial converters. iBETS 1617.

Poll groups with loggers in a parent-child relationship fail to unload. iBETS 1725.

Iridium Agent

Bug Fixes

Data can be merged between two or more sites if they call-in concurrently. iBETS 1718.

Processing incoming data via email throws repeated exceptions when processing an email containing HTML. iBETS 1692.

SMS Agent

Bug Fixes

Processing of incoming SMS text back requests may not be actioned. iBETS 1660.

Transfer Agent


Converted database connectivity to use standard registry settings rather than a UDL file. iBETS 1746.

Watchdog Agent

Bug Fixes

Watchdog may not recover from database issues, including a loss of database connectivity. iBETS 1742.

7

Version 4.19.0.x – 1st July 2015

General Comments

This release contains a range of new features including two new agents – Twitter and Hydstra Conversion. It also includes fixes to a number of bugs and upgrades to third-party components.

There is a significant change to the management of dial-up and SMS numbers for loggers. Please refer to the section at the end of these release notes. This describes the changes and also manual steps that may need to be performed after the upgrade.

Client


The selected catchment values display settings now saved when the client closed. iBETS 1708.

SMS and dial-up numbers are now managed via the Telemetry->SIMs feature. See the section at the end of these notes). iBETS 599.

Bug Fixes

Changed catchment and site view icon move to use left mouse button drag in compliance with intuitive Windows® behaviour. iBETS 1639.

Send To->Clipboard context menu for the samples grid has no effect. iBETS 1710.

Server


Support for Hydstra Conversion derivation type. Bug Fixes

User log-ons should not be captured by the change log. iBETS 1651

Comms Agents


TCP Server Comms Agent. Add support for monitoring comms interface metrics as time-series. iBETS 1609 Bug Fixes

iRIS150 Configuration send only sent sensor configs and site name. iBETS 1709

ABB/Kingfisher. Convert CELL/FAIL messages from modem to standard invalid data type (Q5). iBETS 1654

Twitter Agent


New Twitter Agent is now available. This manages the sending of tweets as an action. iBETS 750.

Hydstra Conversion Agent


New Hydstra Conversion Agent is now available. This can be used to obtain derived values using a Hydstra transformation.

Automator Agent


The specialized Automator has been converted from a desktop application to a managed service agent. This removes the need for a permanently logged-in user session to run it. It also brings it under the supervision of the Watchdog Agent and enables the status of the automator to be viewed from the client.

8

SMS and Dial-Up Number Management Change (SIMs) Important! Version 4.19 significantly changes the way dial-up and SMS numbers are stored and used. After the upgrade and before attempting to unload dial-up loggers, three manual steps should be done.

1. Go to the Telemetry->SIMs form and check all the data numbers assigned to the “SIMs”. They should contain just the basic dial up number required to reach the logger including area code WITHOUT any PABX prefix (e.g. ‘1,’) or extended dialing parameters (e.g. ‘,,,,,,,,9*’). Edit these appropriately if any residual characters remain.

2. Go to the Telemetry->Interfaces form. For each interface that is dial-up

(PSTN), check that the PABX prefix is correctly set in the Params setting. In this example a 1 followed by a pause (,) is required. Leave the field blank if the modem is on a trunk line.

3. For each dial-up logger, edit the Interface Params to leave only any extended dialing parameters if needed (e.g. ‘,,,,,,,,9*’). Otherwise, clear the Ext Dial Params field and save the settings.

This section describes the technical details of the change. In previous versions (prior to V4.19):

1. For IP loggers, the SMS number was tightly bound to the logger. The IMEI and IMSI fields were not viewable in the client and had no real function except to be queried in a report if required.

2. For dial-up loggers, a single parameters string contained all the settings. These included optional dial

prefix, the dial up number and also optional extended dial parameters. This made management difficult as none of the items were separately available in the database. PABX prefixes had to be changed on a per logger basis. This hindered switching between primary and secondary dial-up interfaces if they had different line access. E.g. One on a PABX and one on a direct trunk line.

In this version (V4.19+):

1. The SMS and/or dialup (data) numbers are both associated with a pool of SIMs, one of which is simply linked to the logger. For IP loggers, it is an actual SIM. Legacy dial-up loggers have a virtual “SIM”.

2. These SIMs can be linked to a logger or else released back to a pool of available SIMs. All changes are

logged to the Change event log for audit purposes. 3. For dial-up loggers, the optional dial prefix is now defined at the Interface level. Optional extended dial

parameters (e.g. ‘,,,,,,,,9*’) remain with the logger as they are site specific. The V4.19 upgrade attempts to populate the SIMs table with the existing SMS and/or dial up numbers from the loggers table. However, due to the variability of existing configurations, this process is likely to be incomplete. It also creates a default IMSI for each “SIM” in the form “IMSI_123” where 123 is the unique id of the logger. These can be manually edited in the SIMs form. However for any iQuest IP based devices that call-in, HydroTel will automatically update the IMSI to match the one in the logger. This change is logged in the comms log.

9

Version 4.18.0.x – 1st April 2015

General Comments

This release contains a range of new features and bug fixes. It also includes upgrades to third-party components. The FireDAC® database connectivity introduced in V4.17 for only the server has been extended to most of the core agents. The common FireDAC® database connection configuration is now done through the System Monitor.

The common FireDAC® settings are now shared by all components on each HydroTel machine. Use the “DB Config” menu option on the System Monitor to configure these. NOTE: If the machine previously hosted a V4.17 server, the settings will automatically populate the configuration form.

Client


Prompt user if Interfaces form "Pollable" flag seems inconsistent with selected interface type. iBETS 1624.

Interfaces Manager form enhanced with auto-refresh, poll button and additional statistics. iBETS 1610.

Added support for custom DLL based client forms for specialised end user applications. iBETS 1599

Displays the HydroTel system as either a live/production or a test/development instance. iBETS 1604.

New Wave View and Met View graphic plug-ins. iBETS 1621.

Upgraded site view graphical object framework to support scaling and data dependent status colours. iBETS 1618.

Added view menu options to display full analysis view or site only view in a separate form. iBETS 1644.

New view menu option to resume the last data view. iBETS 1645.

Added support for automatically running a favourite on start-up. iBETS 1645.

Extended site cloning wizard to offer assignment of the newly created site to a catchment. iBETS 1641. Bug Fixes

Unable to edit single sample value or quality if date/time remains the same. iBETS 1568

"Could not convert variant of type (Null) into type (Integer)" exception selecting some loggers. iBETS 1574.

Exception raised when cloning or inserting a logger. iBETS 1581 / 1583.

Device/protocol/interface parameter config may fail due to case sensitive LoggerTypes.PlugIn. iBETS 1594.

Change log now captures all deletions (and also some additions/changes that were missed). iBETS 399.

First WUDMS site opened caused an exception. iBETS 1611.

Disassociate Logger from Point confirmation dialog does not behave as expected. iBETS 1630.

Removed redundant program name/version edits from iQuest device params config forms. iBETS 1634 Logger firmware and software selection drop down lists now filtered by Logger Type. iBETS 1643. Occasionally could only view one SQL report per session. iBETS 1580.

Server New Features

New derivation type to merge samples from ANY input point to the output point. iBETS 1642.

All comms agents now independent of daylight saving time, even if their computer is operating in daylight savings mode. iBETS 955.

Bug Fixes

Security Group tree access update fails on second or more uses. Also some WUDMS functions fail with a similar exception. iBETS 1565

Last Sample Time should not be updated for invalid data. iBETS 1432.

Scheduled unloads of child loggers in a poll group do not correctly communicate with the parent iCE3FX if the parent has no associated points. iBETS 1484.

10

Comms Agents

New Features

Disconnection request sent to supported loggers on TCP Server interface. iBETS 1608.

Bug Fixes

Comms and TCPClientComms agents. End comms request as soon as a connection fails to be established. iBETS 1577.

Removed "Poll" functionality from TDS (Flosys) protocol as support never added to third party TDServer. iBETS 1633.

RTS control timing problem with legacy radio interfaces on some USB->serial converters. iBETS 1617.

Radio communication inter-task delay makes throughput less than optimal with some Ethernet serial device servers. iBETS 1596.

Comms agents now independent of daylight saving time, even if their computer is operating in daylight savings mode. This avoids logger clock sync issues on daylight transitions. iBETS 955.

Email Agent

Bug Fixes

An email with an invalid "To Address" causes the email agent to hang and be restarted by watchdog agent. iBETS 1366.

Serial Rx Agent

New Features

New Serial Rx Agent developed for receiving unsolicited data strings via an RS232 port. iBETS 1477.

SMS Agent

New Features

Upgraded to XE5 development environment, FireDAC® database connectivity and MarshallSoft® serial communications library. iBETS 1517

Transfer Agent

New Features

Added FixedId config option to HydroTel_ExternCSV import DLL. iBETS 1591.

Added NumHeaderRows to standard CSV import mode to ignore header rows. iBETS 1614.

New HydroTelExtern_AWAC DLL for importing NMEA data strings from AWAC text files. iBETS 1585.

System Monitor

New Features

Centralised FireDAC® database connectivity configuration for all agents. iBETS 1619.

Permanently enabled MARS for FireDAC® connections. (Shared by all components). iBETS 1632.

11

Utilities

Bug Fixes

NVP Exporter. Exclude missing records from NVP export string. iBETS 1578.

WebServer New Features

Added new tag to enable display of the CGI file version.

Bug Fixes

Alarm Types no correctly tied to Security Groups. iBETS 1272

Daylight time view of graph not working correctly. iBETS 1523.

‘DataAccess->GridAllowed’ ini file option not implemented correctly. iBETS 1497.

Installer New Features

Added local deployment folder containing current release webserver components. Added installation support for the new SerialRxAgent.

Bug Fixes

Installer did not upgrade the System Monitor’s server configuration plug-in. iBETS 1612.

12

Version 4.17.0.x – 1st December 2014

General Comments

This release contains routine enhancements and bug fixes to a number of components. It also contains a significant database connectivity enhancement to the server. As the server is the core of the system, this change improves overall speed and also database dropout resilience. The agents and utilities will be upgraded to use this technology in a future release.

There is a one-off change required to migrate the server’s database connectivity settings in this upgrade. Please refer to the section at the end of these release notes for details on carrying out this procedure.

A review has been done on the HydroTel components and their current usability/applicability.

Support for the redundant Aquitel Remote has been removed completely.

Due to a limitation with the internal fax rendering component, the Faxing Agent will not work on operating systems later than Windows Server® 2003 or Windows XP®, so is now effectively redundant.

The legacy Paging Agent will not be maintained or supported beyond this release but will still be included in the installer. iQuest recommend that consideration be given to using email to paging service.

NOTE: This release better manages HydroTel licensing for both administrators and iQuest. Support for an administrator renewable expiry code has been added to the server configuration form. A warning only to administrators that renewal is pending is displayed at log-on to the client one month or less from expiry.

Please ensure you contact iQuest for a code before upgrading your system to this version otherwise the server will fail to run until the initial expiry code is in place.

Client


Implement fetch of Program Status block from FX devices on demand. Previously only retrieved in conjunction with configuration requests. iBETS 1491

Added a separate optional “restore comment” field for inclusion in restore notification messages when COR (Comments On Restore) is enabled. If the restore comment is empty, the alarm comment will be used instead. iBETS 1464.

Added "Clear History" to grid filters and send message history lists. Invoked by right-click. iBETS 1525. Added viewer to System Status form to view reports generated by HydSystemStatus utility. iBETS 1556.

Added plain text reason for obscure error code if sending content to email recipients fails. iBETS 1431.

13

Client

Bug Fixes

Images Object display does not expand to use all available space. Image now fills the available blank space, often eliminating the need for scrollbars. iBETS 1492.

Loggers "ReadRequired" field not available for editing, but is required by Comms Agents to be true for some special device types. Checkbox is now on the Persistence tab of the loggers form. iBETS 1446.

Some SQL Reports fail due to database timeouts when the query runs successfully in SSMS. iBETS 994, but this case is actually fixed in the server (see related case iBETS 504).

Dragging object icon over the Site View tab to navigation tree causes repetitive exception. iBETS 1509.

Improve error dialog text if a grid "Send To Mail Recipient" action fails. Can appear to be a file error, but will generally be an email client (MAPI) issue. iBETS 1510.

Rare exception (cannot set focus to a disabled or invisible control). Occurred if the mouse wheel was scrolled immediately after logging on and with the mouse pointer off the client. iBETS 1282.

Schedule configuration form causes an exception when opened multiple times. iBETS 1485.

Client throws error if plot period drop down list accidentally selected while on Event Log tab. iBETS 1410.

Colours on wind rose object view are missing. iBETS 1381.

Intermittent client lockup with certain multi-trace favourites. iBETS 483.

Global favourites do not display intermittently. iBETS 520.

Deletion of items such as sites or loggers can lock the client for an extended time with no progress feedback. Progress feedback of large deletions is now provided. iBETS 1555.

Reports on the reports tree not displaying correctly. iBETS 1545.

Ensure that CSI Pakbus DLL table definitions file name (protocol parameter) is populated and unique. iBETS 618 and 1379.

Schedules outside their validity period stay highlighted in client grid, appearing as still being operational. This is actually a server change. iBETS 1390.


Database connectivity upgraded to use higher performance FireDAC libraries. iBETS 504. This change also addresses a number of database timeout cases. iBETS 994 and iBETS 1471.

Added a second "Command" action type for separate execution. The original still works as before (in-line execution where the process waits until completed before continuing). iBETS 509.

Bug Fixes

Invalid sample with datestamp = 31/12/9999 may cause repetitive errors and severely affect data processing. NOTE: This may be database related and out of the control of the server, but additional checks have been added to reject such samples should they be detected. iBETS 1262.

Alarm Type Message & Alarm Condition Comment were not being appended to alarm restore message when enabled to do so. iBETS 1387.

Scheduled polls of child loggers in group don’t correctly communicate with parent iCE3FX. iBETS 1484.

Comms Agents New Features/Enhancements

Implement fetch of ProgramStatus block from FX devices on demand. iBETS 1491.

All comms agents and DLLs upgraded to C++ Builder XE5 development environment. iBETS 1475.

14


Any DLL based protocols with SOD and/or EOD string lengths exceeding 40 characters would fail unload and/or pointer fetches. Maximum length should be 80 characters. iBETS 1488.

Pointers not updated if camera image and/or logger restart were only samples unloaded. iBETS 1495.

Special logger events e.g. restarts were duplicated in the comms section of the Event Log. iBETS 1365.

Flushing requests from the telemetry viewer may not completely remove them. iBETS 1294.

Can't delete entry from comms queue. iBETS 484.

InSitu/Troll comms DLL. Device details now logged at Debug not Information level. iBETS 1544.

Sending/retrieving configuration to iRIS150FX fails to include all registers in Misc Block 2. iBETS 1430.

Intermediate iCE3 3G / iCE3 FX configuration not retrieved if child logger is not responding. iBETS 1250

Iridium Agent New Features/Enhancements

Added support to check for and obtain data from incoming emails. iBETS 1490.

Common to all components

Changed the shared text log file naming convention to include year, month and day instead of Julian day. iBETS 1505.

Miscellaneous

HydroTel to Hydstra Model interface DLL. Would not operate on Windows 7+. Also changed DLL name from Hyd2k.dll to HydModel.dll. iBETS 801.

Data Server. Added support for heartbeat to enable Watchdog Agent to monitor health and allow control via client system status form. iBETS 1520.

Supervisor Agent. Add support for monitoring the upgraded Data Server service. iBETS 1547.

Watchdog Agent. Added support for monitoring and managing the updated HydroTel Data Server service. iBETS 1546.

15

Server Database Connectivity Change Important! Before attempting to start the HydroTel server service after the V4.17 upgrade is complete, this one-off procedure MUST be carried out.

4. FireDAC® exclusively uses the SQL Server Native Client. This MUST be installed on the server machine.

The easiest way to check for this is to double-click the HydroTel server UDL file in the HydroTel server folder and check the list of installed providers. Version 10 is required for SQL Server 2008+ or Version 11 for SQL Server 2012. Ensure the correct installer (32-bit or 64-bit is obtained). The client is available here: https://msdn.microsoft.com/en-us/data/ff658533

5. Ensure the current database connectivity settings are known. In particular, the database server name,

database name, plus user name and password for both the main server and SQL reporting connections. If unsure, these can be checked in the HydServer.udl and HydSQLReports.uld files in the Server folder.

6. Invoke the Server Configuration form from the System Monitor.

There may be a delay of several seconds before two warning dialogs appear. Firstly that the database connectivity failed and secondly, the configuration was not found and defaults are applied. Ignore these messages.

https://msdn.microsoft.com/en-us/data/ff658533

16

7. Invoke Database Connectivity by clicking the button at the bottom right of the configuration form.

8. Enter the database settings obtained earlier. NOTE: If the Server service is running under a named account rather than Local System, you may need to enable the “SSPI Authentication” checkbox and leave the user name and password edits empty. Finally, “MARS” is normally enabled for best performance.

9. Accept the new settings and the form will close.

10. Reopen the Server configuration form from the System Monitor and it should open with all the configuration displayed correctly.

11. Enable Edit mode using a HydroTel administrator log-in and enter

the license expiry code (supplied by iQuest) to complete the server configuration.

12. The HydroTel server service should now start and operate normally.

17

Version 4.16.0.x – 1st July 2014 IMPORTANT NOTE: You should backup your HydroTel database and read these release notes thoroughly before upgrading to version 4.16. There are major changes to the Loggers structure which you must be aware of.

General Comments

This release introduces major change in the Loggers tree and the way in which Loggers are unloaded when an intermediate iCE3 is present. All loggers that have an intermediate iCE3 are now shown as two separate Loggers with the iCE3 as a Parent Logger and the main logger as a Child Logger in the tree. This change is applied automatically by the database upgrade script to any Loggers that have the iCE3 field set. Changing to this structure allows for:

Easier management of the actual devices as the iCE3 and the main Logger now have their own Logger configuration form;

Ability to use the logging in the iCE3 as well as the logging in the main Logger;

Ability to have multiple Loggers connected to a single iCE3 without using Gateway features

Client


Changed Site Search Bar to search for the characters anywhere in the Site names (the wildcard * can still be used for a wildcard in the middle of a name)

Changed Loggers structure to allow for Parent iCE3 Loggers with Child Loggers.

Added icon descriptors to System Status, Loggers forms.

Added maximise button to Comms Log, Transfer Viewer and System Status forms.

Bug Fixes

Export rating curve functionality broken. iBETS 1416

PSTN Interface parameters cannot be accessed. iBETS 1419

Fixed default column widths on System Status form.

Transfer Agent Bug Fixes

Multiple point identifiers for importing not working. iBETS 1395

Comms Agent Bug Fixes

Radio Modem Interface not initialising correctly

18

Version 4.15.1.x – 7th April 2014 General Comments

Version 4.15.0.x was found to have an instability when installed in certain configurations. This version resolves those instability issues.

Version 4.15.0.x – 17th March 2014 General Comments

Most components in this scheduled HydroTel™ release have been rebuilt in the latest RAD Studio XE5 development environment. This change may alter the look of some controls slightly as they adapt to the newer operating system themes. It also incorporates all current release updates of third party code libraries. It also, as usual addresses a number of bugs from the iBETS system and adds some new features, including significant changes to the serial communications agent.

Client


Prompt the user if attempt to manually unload or sync a logger that is disabled. iBETS 1295.

Improve the use of controls (Unload, Sync etc) for loggers on a 'non-pollable' interface. iBETS 1210.

Add entry field validation - particularly ones that must match perfectly. E.g. Point Identifiers. iBETS 1320.

Added second comment to point alarm that does not get sent, but is displayed on plots. iBETS 568.

Clearly show deactivated alarms in the Point Alarms and Alarm Types configuration forms. iBETS 1330.

Logger metadata view now automatically jumps to the most recent entry’s date/time. Previously it used the current date/time which often required a manual search as these records are typically infrequent.

Importer form. Tighten logger selection to minimise chance of accidentally importing to wrong logger. iBETS 1292

Warn users if ProtocolParams field value empty or not unique for CSI-Pakbus logger types. iBETS 1354.

Optionally include the alarm comment in Notify On Restore action messages. iBETS 1309.

Create a call priority with a group. Also settable comms queue priority for the entire group. iBETS 548.

Bug Fixes

"Visible on Map Site Icon" option in the Alarm configuration doesn't work (icons always flash if any active alarm even if MapVisible disabled). iBETS 1315.

The column 'Type' in the Alarm configuration dialog truncates longer names (20 chars only). iBETS 1331.

Communications address for iRIS150 in logger configuration is always shown as zero. This control is now not visible in HydroTel as it is not a settable parameter. In iLink 2012 it is. iBETS 1232.

Unable to delete a logger if there are associated logger metadata items present. iBETS 1291.

Plot period selector behaviour fix. Prevent scrolling when mouse is no longer on the control. iBETS 1282.

Point configuration form. Object part only shown correctly if launched from Objects form. iBETS 1278.

LoggerStatus object with no points causes an AV to be thrown if site selected on the tree. iBETS 1178.

'Go to Trace Point' from alarm grid does not go to the correct point in multi-point object. iBETS 1244.

Automatic client update tool issues with standard users on Windows 7+. iBETS 1247.

Server


Include alarm comment in Notify On Restore action message. iBETS 1309.

Create a call priority with a group. Also settable comms queue priority for the entire group. iBETS 548.

Bug Fixes

"Acknowledge All" via SMS does not work. iBETS 1307.

19

Active alarms may not restore when expected if they escalate above level 1. iBETS 1335.


Separated UDP interface functionality from Comms Agent to a new UDP Comms Agent, leaving the original Comms Agent dedicated to serial port interface types.

Legacy AsyncPro serial communication component replaced with MarshallSoft® WSC library as used in iLink 2012. Applies to HydCommsAgent, which only handles serial comms (RS232, radio, dial-up etc).

Bug Fixes

Automatic clock checks / sync not consistently done for some loggers. Never for DS-CPU3. iBETS 1297.

Unloads from FX products may fail if a restart event is logged when the logger clock was invalid, even though majority of logged data is correct. (Also applied to iLink 2012). iBETS 1322.

Sensors 16-20 not updated from iRIS350FX when configuration is retrieved. iBETS 1358.

Email Agent Bug Fixes

An email with no address defined hangs agent which is restarted by watchdog agent. iBETS 1366.


Data gap may occur if exception is encountered when processing incoming data packet. iBETS 1279.

TD Data Push Agent Bug Fixes

Fixed rounding error causing 0.2 mm rain tips to be sent as 199 μm.

Automater Bug Fixes

Improve season determination based on ini file settings. Incorrectly handling year boundary. iBETS 993.

System Monitor New Features/Enhancements

Added new menu option to start or stop all HydroTel™ services at once. NOTE: This menu option is only available when ALL services are either running or stopped. iBETS 1286.

20

Version 4.14.0.x – 2nd December 2013 General Comments

This scheduled HydroTel release as usual squashes a number of bugs from the iBETS system and adds some other new features.

Client


Prevent (or at least warn about) high log level (debug/trace) settings on an interface. iBETS 1253.

Implement automated client (and help file) upgrades when a new server is deployed. (This was prepared for in V4.12 and therefore was fully available in V4.13). iBETS 588.

New Minimum Duration for alarms. This specifies the minimum time an alarm must remain active before being marked as restored.

Import Wizard. Increased import speed for some file types and general usability improved. iBETS 1242

Alarm display enhancements: o Added most recent alarm option to catchment display. o Added Custom Icon Colour to the Alarm Types. This is used on the Catchment Map display. o New Alarm History Object Plugin for display on the Site page. Shows the Alarm Date/Time and

the comment that was generated. Configurable number of days to show under miscellaneous in the user profile (Tools->My Profile)

o Added Alarm Types to the Security Groups configuration. This is used for display purposes only. It controls the display of alarms on the graphs, catchment map and alarm history plugin. By default all groups see all alarms.

o A cross can be placed on a trace showing the sample that actually triggered the alarm with the Alarm Type shown next to it. Visibility of this is controlled through the Alarm Attributes of the Point Alarm.

Bug Fixes

Sample Export to file fails if point identifier is null. iBETS 1258.

Security Group Access Tree should not be visible/editable for Administrator group. iBETS 1260

Properly implemented the Alarm Attributes on the Client Graph.


Support for iCE3 FX program management added. Bug Fixes

Comms agent(s) appear to not wait for the one minute grace period if the database is initially unavailable. iBETS 1251.


Agent may incorrectly decode data from non-FX loggers if multiple packets from different loggers received concurrently. iBETS 1270.

21

Reporting Agent Bug Fixes

Unable to process multiple reports in a timely manner and is restarted by watchdog. iBETS 1254.

Transfer Agent Bug Fixes

Repetitive error 'ImportQuality code non-numeric'. iBETS 1047.

22

Version 4.13.0.x – 17th Sept 2013 General Comments

This scheduled HydroTel release as usual resolves a number of bugs from the iBETS system and adds some other new features.

Client


Support for FX family device firmware/software file management and initiating “over-the-air” upgrades.

Support for iRIS 350FX sampler variant configuration. iBETS 868.

Import wizard supports templates to simplify reuse of file definition. iBETS 1216

Import wizard now allows for a column of Point IDs as an option in custom CSV import. iBETS 1177

Access to System Status form expanded to allow Telemetry Users to view the status. iBETS 1227.

Added optional resolution fields to journal entries and also linked journal entry to an object. iBETS 543.

Loggers form – added “Refresh Loggers Tree” right-click popup menu option. iBETS 1015

Bug Fixes

HydroTel importer doesn’t work if an identifier column is present in the file. iBETS 1180

Network Client shortcut. Very long "Target" string truncated the /host parameter. iBETS 1159.

Intermittent error "cdsInterfaces: Cannot perform this operation on a closed dataset". iBETS 1029.

Server Bug Fixes

Repeated "Field 'FirstActivateDT' not found" errors being logged in Windows Event Log. iBETS 1228.


Support for iRIS 350FX sampler configuration and lookup table retrieve/send. Also the fetch and send process is optimized to only transfer the items that have changed. iBETS 868.

Support for FX family device over-the-air firmware and/or software upgrades.

Pakbus DLL. Added support for UInt2 (type 2) and UInt4 (type 3) records. iBETS 1174.

Altered clock auto sync method to permit means of inhibiting auto-clock syncs but retaining clock reads. iBETS 1010.

Extended security role access (view only) to System Status form to aid diagnostics. iBETS 1227. Bug Fixes

CSI Pakbus DLL: IEEE floats (types 7 and 9) were limited to 6 significant places. iBETS 1220.

CSI Pakbus DLL. Problem with string fields contain ASCII control characters. Esp. CR/LF. iBETS 1160

23

SMS Agent New Features/Enhancements

Added new SMSSentMessages table to database to record SMS messages sent in a straightforward format for extracting for auditing and billing purposes.


UTC time zone adjustment for samples from FXSAT loggers not working correctly. iBETS 1224.

Utilities


HydAvgSum now supports median sample calculation. iBETS 1169

24

Version 4.12.0.x – 13th June 2013

General Comments

This scheduled HydroTel release as usual resolves a number of bugs from the iBETS system and adds some other new features. It also provides full support for the iRIS 350FX datalogger from the preliminary support included in version 4.11. The client’s import wizard form has been completely rebuilt and now supports a wide range of import file types and is more intuitive and robust than the previous import tool. See iBETS 551 and 826. All the third party component libraries used in the system have also had significant upgrades released by their vendors and these are included. The main cosmetic change that will be noted is the display style of all charts in the system with the grid axis lines and traces appearing softer. There two changes which alter the context of logger configuration items and it is very important HydroTel administrators are fully aware of these:

iBETS 982: The ‘/0’ suffix applied to point identifiers on any iQuest iRIS or standalone iCE3 logger has been removed and all affected time-series type point identifiers are changed during the upgrade process. From now on, new configurations of any iRIS or iCE3 loggers must follow this standard. E.g. A water level point on an iRIS 350X had a point identifier of ‘1/0’. The identifier is now just ‘1’.

iBETS 1129: The context of the logger “Time Offset” parameter has been changed. Previously it reflected the difference in time zone between HydroTel and the logger. Now it is the time zone offset from UTC to the logger. E.g. All loggers located in New Zealand and on New Zealand based HydroTel systems previously had a time offset of 0. They will be set to ‘UTC+12 (NZST)’. This applies to ALL logger types and the time offset values are automatically changed during the upgrade process. This is done by taking the previous time offset value and recalculating it based on HydroTel’s UTC offset. It is vital that a check is made after upgrading to HydroTel V4.12 that the logger time zone settings correctly reflect the local time zone of each logger BEFORE starting any communications agents.

Client


Import wizard form completely rebuilt. Resolves iBETS 551 and 826 plus adds significant new features.

Updated the ResetLayout” tool to completely delete all relevant registry settings, ensuring a clean default startup in the event any became corrupted. iBETS 1083.

Automated most of the required changes when converting a logger to an iRIS 350 FX. iBETS 1035.

Disabled comms cycle and cycle time edit fields on loggers form for non-pollable interfaces. iBETS 1067.

Plot audit bar enhancements. Including providing date/time selector, identifying the user who performed last audit and warning of attempt to revert datum earlier than current. iBETS 1038.

Implemented a "Get Recent Data" function - similar to "Fetch Pointers". Also involves changes to the comms agents. iBETS 1024.

Added new “Validate Missing” checkbox to Points configuration form. This enables rejection / quarantining of invalid/missing samples (quality code 5) if desired. iBETS 1000.

Added pop-up menu to the primary and secondary interface selection on the logger configuration form to allow swapping the primary and secondary interfaces completely. iBETS 851.

Colour coded the alarm types in the alarm configuration form based on their enable state. iBETS 1131.

Added RTF, Checkbox, Gradient, Barcode and Cross objects to FastReports.

25

Bug Fixes

Fixed bug in iCE³ configuration where the host port speed was set one off from what was selected in the list.

Deleting samples deleted the wrong entry. The normal navigator Delete (X) button now only allows deletion of one sample. This is to cater for an obscure limitation of the third party grid component. A new “Delete Multiple Samples” button has been provided for deleting more than one sample. iBETS 1027

Refresh button on tree menu causes Objects to lose their value on the Site page. iBETS 1116

Multiple trace button causes client to not draw graph. iBETS 1066

Deleting catchment with catchment image causes error. iBETS 1048

Intermittent exception thrown when the client is closed. Possibly only on Windows 7? iBETS 887.

Default effective time for Journal is using client time not the server time. Could cause daylight savings error. iBETS 1055.

Refreshing the site level journal view did not filter on site and showed all items. Also added option to send journal to clipboard. iBETS 1006.

iRIS350X configuration form. Communications schedule duration limited to 1440 seconds. iBETS 1132.

iRIS 350FX configuration. Scaling Calculator in mA mode appears to divide the expected multiplier by 1000. iBETS 1130.


Implemented point alarm delay feature. This prevents multiple alarms from a point where the value may fluctuate regularly, but needs to be in the alarm range continuously’ for a given time before being deemed a real alarm. E.g. low battery on a solar powered site. iBETS 248

Server now calculates and populates the "Last Data Time" value on the loggers form. Previously it was the Comms Agent which had no knowledge of data validation etc. so the time did not always reflect the true last data time in HydroTel™. iBETS 1128

Added “Validate Missing” check. This enables rejection / quarantining of invalid/missing samples (quality code 5) if desired. iBETS 1000.

Comms Agent New Features/Enhancements

Removed requirement for “COM99” style pseudo-ports for IP type interfaces. iBETS 1068.

Device firmware/software versions now requested prior to configuration fetch/send. Previously it relied on device call-ins to report the versions. iBETS 1002.

Notify to the support roster any automatic logger clock syncs triggered by the logger clock being outside the error deviation threshold. iBETS 991

Handle iRIS 350FX UTC time stamping and clock read/sync. iBETS 1062

Change context of logger time offset to be offset from UTC for all logger types. iBETS 1129.

Increment NumConnections in LoggerCommStats for IP loggers. iBETS 1032.

Removed unnecessary index (/0) from iRIS and iCE3 3G unloaded data array identifiers. iBETS 982.

Implemented a "Get Recent Data" function - similar to "Fetch Pointers". This also involved changes to the client. iBETS 1024.

CSI Pakbus protocol DLL: Logger program statistics information available as metadata. This update was added as a tool to aid determining if an issue with loggers running OS9. iBETS 825 and iBETS 1031.

Monitor Sensors protocol DLL: Sensor calibration information available as metadata. iBETS 780.

Added agent configuration option to clear queue table on start-up. Also applies to SMS, email, paging etc. iBETS 975.

SOD/EOD pointers do not update if no unloaded samples could be matched with a point. iBETS 1093. Bug Fixes

Can't send or retrieve logger configs on radio interface. iBETS 1049 (fixed in iBETS 1002 above).

Pakbus DLL. Identifier "Maint" is not being correctly processed. iBETS 1003.

Unload of corrupt image from iRIS350X causes unload to stop. iBETS 997.

26

ASCIIZ field type (11) in table data causes an unload issue. Reported symptoms include setting of SOD pointer to future date. iBETS 1021.

Couldn’t fetch/send configuration from standalone iCE3 3Gs. iBETS 1127.

"Zero sample rate for autoinsert point.." comms log message had incorrect point identifier. iBETS 990.

Last unloaded data time can be reported falsely with iCE3 3G / host datalogger scenarios. Processing of last unload time has been moved to the server and is resolved in iBETS 1128. Original case iBETS 848.

Handle sample buffer over-runs more cleanly, ensuring all available samples are processed. iBETS 1139.

Mace HVFlo DLL. Comms errors sometimes resulted in downloaded data gaps. iBETS 576

Flosys (TD Server) driver. Issue with non-minutely data time stamps causing retries. iBETS 1004

Point write will not work for loggers that operate on call-in only scheme (e.g. via TCPServer comms agent). iBETS 1148.


Added support for logged data sent by FX loggers (floating-point format). iBETS 1037.

Added support for automatic zero insertion for event rainfall. iBETS 1058.

Standardised the database interface to more closely match the comms agents. The old DataBuf table plus its associated trigger and the DataVault table are now redundant. iBETS 1089.

Reporting Agent Bug fixes

Agent not automatically restarted by the watchdog even though auto-restart enabled. iBETS 1138.

Transfer Agent Bug fixes

HydroTelExtern_Logalevel DLL very intermittently generated thousands of "Initialisation Completed" with the same timestamp in the Windows Event Log. iBETS 1088.

Transfer agent stops working but still produces heartbeat, preventing watchdog intervention. iBETS 962.

Watchdog Agent New Features/Enhancements

Logger status is now updated appropriately by the overdue data checker. This caters for non-telemetered loggers such as Iridium or filed based imports. iBETS 1019.

Provided last resort option to reboot the machine if unresolved issue(s) for extended time. iBETS 1141.

Supervisor Agent Bug fixes

Handling and reporting of events appears repetitive. Already reported persistent errors were repeated on subsequent new events. Fixed by adding tag to indicate already notified. iBETS 401.

Utilities Bug fixes

Automator. Improved determination of seasons based on ini file settings. Incorrectly handling year boundary. iBETS 993.

NVP Exporter. Add “burst mode” to catch up after comms outage. iBETS 854.

27

Version 4.11.0.x – 3rd December 2012 General Comments

This release as usual resolves a number of bugs from the iBETS system and adds some other new features.

Client


Added "Toggle Schedule" action which allows enabling or disabling of a schedule based on an alarm action, schedule action or post unload action. iBETS 606.

Added Comms Log button for the selected interface on the Telemetry Viewer. iBETS 977.

New user configurable option to include/exclude identifier in "Send To File" sample export. iBETS 949.

Active alarms for a disabled alarm and/or alarm type should not appear in the Alarms Viewer. (Was actually a server change). iBETS 961.

Comms log readability enhancement. Colour coding has been added to some comms log messages in the logger view of the comms log and also the non-IP interface view. Because the interface view in IP mode usually contains multiple loggers being processed concurrently, any attempt to sequence them is meaningless. Blue is unsolicited call-ins, green is start of request, purple is end of request and red is an error. Further feedback is welcomed and the iBETS case is being kept open. iBETS 876.

Added history to message send and log / journal filters (last 20 entries). iBETS 341. Bug Fixes

Plot alarm and statistics lines - text sometimes gets displayed outside the chart area. iBETS 208.

Cancel button on Import Wizard did not abort large imports properly. iBETS 929.

Loggers form - did not show correct logger when first opened, did not update details of selected logger. iBETS 951.

Telemetry viewer for IP Comms did not show all active processes. iBETS 838.

Error deleting a User from User/Organisation table if the user has a phone number. iBETS 964.

iCE3 3G auxiliary sensor array ids (7/0, 8/0 and 9/0) now labeled in the Sensors->Misc Settings tab of the client configuration form. iBETS 954.

Site view of objects and point data did not auto-update correctly after having been selected previously. iBETS 935.

Wind Rose plot object view improvements for large fonts and when client resized. Also now displays the current direction and speed as a title above the rose plot. iBETS 948 and 980.

Unsolicited calls sometimes reported associated with the incorrect logger. (Actually a comms agent fix) iBETS 361.

Logger name not shown as descriptor for "Unload Logger" actions in configuration grids. iBETS 995.

Send Message form. Contact methods list may have one or items inaccessible (off screen). iBETS 988.

Rerun rating - intermittent exception "cdsGeneral: Field 'RowCount' not found. iBETS 992.


Optimise communications by reducing the number of clock reads in automatic clock management mode. iBETS 947.

Modbus driver DLL. Add support for Modbus TCP/IP protocol variant and %MW style register indexing. iBETS 979.

CSI PakBus DLL now supports table fields with a dimension more than 1. iBETS 945.

Included support for 32-bit integer and IEEE float types overlayed in direct data reads from iQuest and Modbus devices. The definition uses the point identifier. iBETS 981.

28

Bug Fixes

Unsolicited calls sometimes reported associated with the incorrect logger. iBETS 361.

Telemetry viewer for IP Comms does not show all active processes. iBETS 838.

Multiple iRIS-CAM image unloads from a logger on TCP or dial-up interfaces fail. iBETS 693.

Listening TCP Server interface type had potential for "cross-talk" between separate loggers. Extremely intermittent and only affected logger types that have no address validation (e.g. CR10) and when loggers with a camera were on the same interface. iBETS 960.

iRIS-CAM image point identifier changed to avoid posting problems in the future. Identifier is now “image” rather than “63/0”. iBETS 953.

Email Agent Bug Fixes

Sent emails may be incorrectly timestamped when received. E.g. 12 hours out for NZ users. iBETS 946

SMS Agent Bug Fixes

Need to be able to use a forward slash (/) in site/point identifiers when using text back in ExtSysId mode. This was actually fixed in V4.10 but not closed off. iBETS 340.

Utilities Bug fixes

HydPointMod. Point value changes done by the Point Modifier utility did not initiate a write to a device, even though the point’s value did correctly. Also changed the log file location and naming to the HydroTel standard. iBETS 957.

Transfer Agent New Features/Enhancements

ZRXP Export DLL. New user definable setting (InvalidValue) allows propagation of samples with quality code 5 (missing / invalid) to the ZRXP recipient system. iBETS 822.

ZRXP Export DLL. Have an option to include quality code in ZRXP exports if required. This is enabled with a new user definable setting (OutputQuality) iBETS 778.

Bug Fixes

Transfer agent's import or export process could stop working but still produce a heartbeat, preventing intervention by the Watchdog Agent. iBETS 962.

Watchdog Agent Bug Fixes

Watchdog Agent configuration form: Required services - checkbox problem with components with "server" in the name. iBETS 872.

System Monitor Bug Fixes

Data Server configuration form in System Monitor threw "Path % not found" exception when logging in to use the edit function. iBETS 971.

29

Version 4.10.1.x – 1st October 2012 General Comments

This minor update expands the management of missing/invalid logged data values (iBETS 822). It also incorporates a few small enhancements and fixes since the initial V4.10.0 release.

Client


Ratings editor now shows rating points on the rating curve plot.

The site that an object is associated with can now be changed in the Objects configuration form.

New “Simple Pump” graphical client plug-in created.

Enhanced colour picker (spectrum type) for point statistics lines and plug-in band configuration forms.

Actions editor. Added new report export type (CSV) to support upgrade in Reporting Agent.

Bug Fixes

Plot alarm lines - text overlay. Residual problem after enhancements in V4.9 release. iBETS 208.

Cancel button on Import Wizard did not cancel large import batches. iBETS 929.

Import wizard logger selection grid improved and now has its search footer enabled.

Server Bug Fixes

“PointModify” action internally did not pass the point's value as a parameter. This affected the autodialler control functionality. iBETS 925.

Occasional “Non-VCL exception occurred. Scheduler will attempt to continue.” message. iBETS 670.


Campbell Scientific PakBus driver DLL. Expanded support for handling invalid values (NaN etc). These are tagged as missing/invalid quality code 5 which is now exportable through the Transfer Agent to downstream systems. iBETS 822.

Campbell array based loggers (CR10 etc) - improved record content logging for comms diagnostics.


BOM HSC format DLL. Exports now translate invalid/missing data quality (5) to BOM’s quality code 6. iBETS 822.

Halytech DLL. “Invalid” values (-99999.999) are tagged as missing/invalid quality code 5 which is now exportable through the Transfer Agent to downstream systems. iBETS 822.


Support for report exporting as CSV files to supplement the existing PDF and HTML formats.

30

Version 4.10.0.x – 3rd September 2012

General Comments

Major improvements have been made in the areas of client responsiveness. Messaging between the server and client for updated sample information and logger information has been overhauled, as has the Logger’s form where the grid has been replaced by a tree. There are significant enhancements to the automated checking of agents which rely on external modems or radio equipment. These agents (Comms, SMS, Paging, Voice and Faxing) now support the notification of unrecoverable faults that require manual intervention. The SMS agent has several enhancements added including two new text-back services and text-back help. This release also resolves a number of bugs from the iBETS system and adds some other new features.

Client


Support for inverted Y axis plotting. iBETS 608.

Cloning wizard usability improvements. iBETS 886.

iRIS 350X configuration form analogue output source selection improvement. iBETS 867.

Added MovingTotal and MovingAverage plot format options.

Added list of connected clients. Tools->Connected Clients.

Tag a quality code per user phone number for SMS submitted samples. iBETS 815.

Provide a legend/hint showing the meaning of the tree and/or grid icons on the Security Groups and Interfaces Manager forms. iBETS 849.

Removed the Unload button from the toolbar and added it to the context (pop-up) menu for the navigation tree. iBETS 144.

Warning now appears if an alarm is configured for a Rainfall Depth point but Duration is set to 0. iBETS 195.

Buttons added on Action editor forms to go direct to Rosters/Contacts/Poll Groups as necessary. iBETS 288.

New Client Connection Manager Form to show a list of all connected clients.

Added the ability to include a message with Roster, Contact or Message Direct action configurations. If this is used for an alarm action, the message will be used instead of the normal alarm message (a warning about this is displayed in the client).

Option to inhibit alarms on historic data. Pre V4.9, this was the default behaviour which was not intended. In V4.9 all alarms on old data were processed and activated. The default now is to inhibit processing of alarms on all old data (to mimic the behaviour that had occurred for a long time). iBETS 874.

Improvements to Catchment Summary view including the ability to define which object variants are included. Also supports the export of summary contents to file, printer, email or clipboard. Partial completion of iBETS 845.

Ability to test an Alarm from the Point's Alarm Configuration form. iBETS 774.

31

Bug Fixes

Adding the first new point to an object should use just the object's name by default. iBETS 893.

DIO mode selection in iRIS350X configuration is incomplete. iBETS 894.

Statistics lines form. Grid issue - corruption of the colour cell throws an error. iBETS 852

Intermediate iCE3 3G present' setting not included in the logger clone process. iBETS 898.

A full review of Actions has been undertaken. Contact and Message Direct actions now work. iBETS 421, 449.

Image Boundary on Site level overview tab now correctly adjusts when no image is present. iBETS 305.

Inserting/Editing/Deleting images on Site/Catchment/District configuration pages now works every time (was an intermittent problem). iBETS 334.

Improved charting of incrementing, averaged and totalled datasets. Partial datasets at the beginning of the graph are excluded for all and at the end of the graph are excluded for averaged and totaled datasets. Also resolved an issue where event based data that had no samples at the end of the dataset but the graph range included an end of aggregate period were being excluded as a partial set when it was actually complete. iBETS 346.

Setting the first logger in the list to use secondary interface causes HydroTel tabs to stop working. iBETS 811.

Telemetry User security group now has read only access to the loggers and schedule configurations. iBETS 806.

Users table Last Logon field not updated on user login. iBETS 830.

Plot details panel remains expanded and empty when selecting an image point after a multiple plot. iBETS 535.

Database navigators on LoggerTypes form can sometimes overlap each other. iBETS 860.


Major enhancements made to the reporting of new data and logger status changes to connected Clients.

Change to alarm processing for historic data (see note in Client features above). iBETS 874. Bug Fixes

Heartbeat output for the Data Manager now occurs during batch processing. Previously the time taken to process large batches of data meant the watchdog agent would stop the server as the Data Manager would appear to have failed.


Add quality code and metadata string passing from DLLs. Also changed sample value from float to double. iBETS 892.

Add method of detecting an ineffective comms interface due to a factor external to comms agent itself. iBETS 767.

Automatically update logger serial number from the actual device in the field. iBETS 753.

Change "Unable to locate point for id..." message from Warning to Debug log level. Trivial iBETS 903.

Time sync every time HydroTel connects to a logger nominated for forced synchronization. iBETS 817.

MACE Flo driver DLL now supports clock sync (SetClock function). iBETS 910. Bug Fixes

“Local station OUT0 relay control not working correctly” at GWRC. Caused by the comms agent not checking that the point type was an input before filing a logged sample when the identifier matched. iBETS case 470.

Automatically read clock back again after a user initiated sync clock. Did not work for some third party loggers. iBETS 653.

Email Agent New Features/Enhancements

Added function to check for (and notify of) incoming email. It also saves file attachments into defined folders. iBETS 199.

32

SMS Agent New Features/Enhancements

Define a quality code per user phone number for samples submitted via SMS. iBETS 815.

Support for multiple SMS agents to enhance bandwidth and reliability. iBETS 844.

A roster notification is sent if the SMS modem becomes unresponsive for any reason. iBETS 911.

Included "DelayedSend" flag in SMSQueue table for delayed sends. iBETS 257. Note additional work is required in the server/client to fully complete this feature. See iBETS 912.

New text-back service HydroTel System Status (service 9). iBETS 759.

Provide support for authorised users to request help for the SMS text-back services. iBETS 913.

Queued SMS messages with empty text field should be rejected. Case 914. Bug Fixes

SMS message send fails if message text length > 160 characters. This generally worked, but intermittently would fail depending on the message content. Significantly improved the handling of long messages and the event log also identifies the sending of multi-part messages correctly. iBETS 196.


Now handles multiple dataset FastReports (up to 10 to match the client).

Added sending report to Roster (configurable through the Client).


Add received byte count to logger statistics. Also update applicable Logger Status points. iBETS 875. Bug Fixes

Exception occurs when single sample packet is received. iBETS 888.

Voice Agent New Features/Enhancements

Improved attempts to recover from a modem lockup. Also added notification of unrecoverable faults to a roster. iBETS 406.


Include the actual export id string in the exception messages to aid diagnosis. iBETS 897.

BOM HSC format exports now translate invalid/missing data quality (5) to BOM’s quality code 6. Bug Fixes

Fixed processing of empty files during HydroTel™ XML Import. iBETS 683.

Watchdog Agent New Features/Enhancements

Detect overdue data that is in the future (e.g. from forecast models).. iBETS 910.

System Monitor New Features/Enhancements

Configuration dialogs now require administrator access to prevent unauthorised changes to settings. iBETS 748.

33

WebServer New Features

Improved charting of incrementing, averaged and totaled datasets. Partial datasets at the beginning of the graph are excluded for all and at the end of the graph are excluded for averaged and totaled datasets. Also resolved an issue where event based data that had no samples at the end of the dataset but the graph range included an end of aggregate period were being excluded as a partial set when it was actually complete.

Added MovingTotal and MovingAverage plot format options.

Ability to represent data in Daylight Saving time when appropriate. iBETS 528.

Added plotting of discrete data points. iBETS 766.

hydrotel v4.0 release notes - hydrological services america · ice3 fx configuration send may cause...

Documents