If word-wrap is not working: If viewing in Notepad - Format / Word Wrap If viewing on the web - Mouse right click / View Source CDI's MeterGrapher application facilitates monitoring of CDI meter flow values. The software includes extensive graphing capabilities and visual alarms showing when meter values are outside user-specified limits. Any device that uses the Modbus messaging protocol could be monitored using MeterGrapher. Non-Modbus devices can also be incorporated. New in this edition (4th April 2022) MeterGrapher Version 2.32 Positions of major Forms on screen are saved for the next session. New in this edition (9th February 2022) MeterGrapher Version 2.31 Current Directory is shown on the Main Form, left side, near the top. This is the location of the User's log files - new feature: double-click the path to open the directory in File explorer. New version of MGUsageCalcs.xlsm - date ranges updated Removal of SMS messaging: PLEASE NOTE: This feature is no longer supported, due to changing National Regulations for SMS Messaging, particularly in the USA. If you are using it already it will continue as is, but you are strongly advised to give it up. If this will cause difficulties please contact CDI Meters. Fixes to StartLog and StopLog functions New in this edition (4th August 2020) MeterGrapher Version 2.30 Bug fix - fatal error when scanning for CDI Flow / Pressure meter. New in this edition (11th January 2020) MeterGrapher Version 2.29 Averaging of logged values - in the Chart Form the number of logged values to be averaged can be specified. Averging is applied to all meters in the plot. Logging interval and the saving of log data is unaffected. On the Chart Form: New controls: Average Over edit box - specify the number of values to average over (integer > 0, < number of points in graph) Go button - click to invoke the averaging. The button is disabled (greyed) while meter values are being sampled Caption showing current averaging status Averaging works when Graphing Old Logs, and during logging. Note that during logging, averaging is only applied up to the point that the Go button was clicked. The caption shows the time up to which the averaging has been applied. The button can be clicked again subsequently. Minor bug fixes, including correction of formatting errors on the Chart Form. New in this edition (17th June 2019) MeterGrapher Version 2.28 CDI's Vortex meter added to library Meter selection listings re-ordered so CDI meters are at the top When a point in the graph is clicked its coordinates are displayed In Adapter / Meter Config an option to list COM ports in use has been added. AnswerGrapher can now write a data file back to disk. This can be used to find and correct spurious data values in log files If the user wants to correct the current log file MeterGrapher logging must be stopped, and MeterGrapher set off-line until the edit is complete. New in this edition (24th April 2018) MeterGrapher Version 2.26 Minor improvements and bug fixes Desktop shortcut added in installer StartLog.bat corrected Spreadsheets changed to deal correctly with different Regions New in this edition (30th November 2017) MeterGrapher Version 2.25 (Only released to CDI staff for testing) Changes related to MGML: Columns re-ordered to improve readability Terminology harmonised, and limitations on Param names lifted MPType gone - MPID is used as the unique identifier Units (of flow, etc.) now on all outputs Mixed units (e.g. mbra / psig) allowed - user is warned User can mix CDI meter flow units, but this is discouraged Full description of valid meters / params on Config Form Fully backward compatible Search for units assigned in a CDI Meter now in AutoScan If there is a conflict between units in a meter and Meter / Param Selection, the user is asked to correct it by changing Meter / Param Selection (MG used to change Meter / Param selection, but this proved error-prone) Other minor improvements and bug fixes New in this edition (17th April 2017) MeterGrapher Version 2.24 Correction to V2.23 (limited release). Error reading MGML files - typo - the factor for instant values is overwritten by the factor for cumulative values. Result was flow reported was a tenth of actual, usage was zero Formatting changes requested by Exair Corp Minor bug fixes and improvements: Could crash if spot-checks invoked while logging - action inhibited Picture of meter added to meter renumbering Form - for clarity Notice on Parity change Form - Only for CDI meters connected via COM or TCP using NET485 Installer would not install the .xlsm files if they already existed, so users never got updates! Installer now overwrites - warnings on the web and in the xlsm files New in this edition (26th March 2017) MeterGrapher Version 2.23 - Only released to Exair Corp for testing Correction to fault found when MG is run in Regions that use comma as the decimal seperator. New in this edition (19th March 2017) MeterGrapher Version 2.22 Revised approach to MGML - If you have been logging non-CDI meters please contact cgray@cdimeters.com - THIS IS IMPORTANT! Minor bug fixes and enhancements New in this edition (12th January 2017) MeterGrapher Version 2.21 - Only released to CDI Meters Inc for testing Better calculation of Minimum Log Interval Graph axis management - on the Meter / Param Selection Form the user can choose whether a parameter appears on the left or right axis when graphs are drawn. CDI Target meters now report scfm in the range -32767 to 32767 Where a meter reports multiple parameters, Config Autoscan now finds them all - previously it only found the first one Changes to the structure of the MGML file (only of interest to users who edit this file to add their own types of meter): Previously if two different types of meter were reporting one parameter they had to have different parameter names, hence we had flow and flows. Now the parameter names can be the same, but MG will not allow a single parameter to be logged in different units, so Flow must always be scfm (or NM3Min, etc.) If you want to log in different units, give the Parameters different names, where one is not a sub-string of the other - so Flow1 and Flow2 is fine, but Flow and Flow1 is not. Default MGML config has just CDI Thermal meter as the default (without a CDI pressure meter) New in this edition (27th November 2016) MeterGrapher Version 2.20 - Only released to CDI Meters Inc for testing Changes to accommodate negative flow values from CDI's Target meters. The MGML files (.xlsx and .txt) can now have a number format of N (in addition to F and E) to flag that the meter will return values in the range -32767 to 32767 If the number format is F flow values are 0 to 65535. The MGML files supplied with this installer have meters of type 84 with number format = N. Added Min (Minimum value logged this session) to the display of Value, Max, and Limits New in this edition (25th October 2016) MeterGrapher Version 2.19 Minor bug fixes and enhancements: Spot-check buttons disabled during spot-checks Better diagnostics during meter renumbering New in this edition (20th October 2016) MeterGrapher Version 2.18 - limited release for user testing AnswerGrapher error (caused by addition of flow units scheme) corrected How-to video added showing extension of IA table in a ConnectPort X2 gateway MGML files modified to accommodate CDI Target meters (coming soon!) Minor bug fixes and enhancements: Upper limit of flow (6000 scfm) removed Additional checks on the integrity of values returned from a meter New in this edition (17th October 2016) MeterGrapher Version 2.17 - limited release for user testing Minor bug fixes and enhancements: Error occurred when starting new log files every n hours MMRT could not cope if user chose DELETED meters Autoscan tried to connect to DELETED meters Code to inhibit repeated writing of log values when all meters showed zero - deleted Usage added to Special flow log, in a seperate file Now allows an attempt at meter renumbering for any adapter New in this edition (10th October 2016) MeterGrapher Version 2.16 - only released to one user for testing a condition I could not reproduce. Bug fix: Read time-out (RTO) for TCP adapters was inadvertantly set to zero. NET485s coped, other adapters may not. RTO harmonisation for COM and TCP started New in this edition (22nd September 2016) MeterGrapher Version 2.15 - Only released to CDI Meters Inc for testing Bug fixes related to MADiagnostic Added module to test SC Boards and Adapters. Mainly for CDI use pre-delivery, but may be useful for debugging systems in the field. New in this edition (8th August 2016) MeterGrapher Version 2.14 Bug fixes MG rejects extreme flow values – limit corrected to 6000scfm (was 600). Explanation of flow and usage added too the MG website – see table on User Docs New in this edition (8th July 2016) MeterGrapher Version 2.13 Minor improvements and bug fixes. Note that if connection to an Adapter is lost: If the connection is re-established MG continues Otherwise, MG appears to be dead, but it isn't - it just takes a long tome (around 20 seconds) to respond. User could click on Stop Logging, wait 20 seconds, then close MG (takes 20 seconds). New in this edition (8th June 2016) MeterGrapher Version 2.12 Changes to allow MG to log meters fitted with XBee ZigBee modules, connected through a Digi ConnectPort X2 connected to the MG computer via TCP/IP. Config Form: 'Configure Ethernet Adapters' changed to 'Configure NET485 Adapters'. MG tries to establish a Telnet session with any TCP/IP adapter. This will only work with a NET485. If it does not work MG writes to the diagnostic file rather than warning the user. Extra USer Input for AutoScan: Find All - Look for all meters OR Find In Config - Check connection to the meters in the current config If the meter config (as opposed to say, logging interval) changes, MG checks for meter flow units. This takes a few seconds so a flashing message has been added. Measure Meter Response Times: Now allows the user to specify how many meters to sample (was set to 3) Gives the user more control over the chosen values. Error diagnostics improved to help with ZigBee-related issues Meter Status now has different colours for meters above the high limit and below the low limit. Extreme returns from meters filtered out - nothing allowed < 0 or > 6000. Audible warnings off by default Meter Status block font larger and bold Improved error-trapping for meters or adapters not responding New in this edition (10th May 2015) MeterGrapher Version 2.11 Bug fixes - NET485 configuration and meter renumbering MeterGrapher Version 2.10 Note that the Ad suffix on version numbers and folder names has been dropped. Extensive Documentation (Website) update. Major overhaul of the Installer: Hitherto all files have been installed under Program Files. This was fine under XP, and can be made to work with Win 7/8, but it is not good practice. The new installer places files in more appropriate locations, and should work well for years to come. See the Website (User Docs / Additional Information / Location of Files) for details. The new Installer detects 'old' installations and moves existing files as required. This should be largely transparent to the User until searching for the MG data files. If the User has changed the directory used to store them (using the MG menu option) they will still be in the same place. If they are still in the default folder (Program files \ MeterGrapherAd) they will be moved to \ CDIMeters \ MeterGrapher. The MG program will know this and it will look no different to the user. As a consequence some of the shortcuts (those to files now under ) are no longer required. Uninstalling a previous version is NOT recommended. This is a small application and so takes up little disk space. The old version will not interfere with the operation of the new, and although the new Installer has been extensively tested on XP and Win 7/8 there remains a small chance that some user data gets lost in the translation. Leaving the old installation intact provides a safeguard. Code Signing: ("The process of digitally signing executables and scripts to confirm the software author and guarantee that the code has not been altered or corrupted since it was signed by use of a cryptographic hash.") The MeterGrapher program and the Installer are now Code Signed, including EV (Extended Validation), which provides even greater security and authentication. See the Website (User Docs / Additional Information / Code Signing) for details. This means that the user has assurance that the codes are 'as written' and have not been altered to introduce malignant elements. Operating Systems (XP, Win 7 and 8), recognise Code Signing and will produce few (if any) dialogs of the type 'Unknown Publisher' and 'Are you Sure ...' when installing and running the program. New in this edition (15th February 2015) MeterGrapher Version Ad2.09 (Note: This was only on limited release for testing). NET485 configuration setting revised and re-documented Ability to set parity and stop bits using COM/USB or TCP/IP. Detection and setting of flow units (scfm, Nm3/min, etc) from values embedded in the meters Excel workbooks (AnswerGrapher and MGUsageCalcs) now in Excel 2013 (*.xlsm) Minor re-formatting and bug fixes. New in this edition (06th August 2014) MeterGrapher Version Ad2.08 Further improvements to NET485 configuration settings New in this edition (27th May 2014) MeterGrapher Version Ad2.07 Note: the Parity feature (Version 2.06Test below) is not yet fully tested and implemented. This will not affect users who do not require this feature. NET485 Adapter Firmware Change: Software now detects the NET485 version and configures it accordingly, so users can have a mix of old and new adapters. If there is yet another verson released MeterGrapher will detect this and provide a useful message. Define a Start New Log Files interval. If a user has a very high logging rate the log files can become large. There has always been the facility to manually stop logging, Start New Log Files and recommence logging (files are renamed - no data is lost). The user can now define an interval at which this will be carried out automatically. Batch files for starting and stopping MeterGrapher. These have been revamped, partly to align with the previous item. Batch files are now: StartLog.bat - Initiate MeterGrapher and start logging with the current parameters. This can be added to a Start menu to recommence logging following a computer restart. StopLog.bat - Stop logging and close MeterGrapher. Note that this only works if logging is in progress. Note that these files MUST be instigated in the directory where MeterGrapher is running. If a different directory has been set up for User files then create shortcuts in that directory, do not copy the batch files. New in this edition (9th April 2014) MeterGrapher Version Ad2.06Test Function whereby the User can set a parity (Odd, Even, None) parameter and switch all attached CDI flow meters to adopt that parity. This has been requested for situations where customer sites have a policy that all devices adopt a particular parity. Invoked for COM/USB, but not yet for TCP/IP. The version is Ad2.06Test because I am unable to test it throuroughly locally and have asked CDI if they can find a suitable test-bed. New in this edition (22nd January 2013) MeterGrapher Version Ad2.05 NOTE: Unresolved issue: Some versions of Windows 7 use file virtualisation and files created when MeterGrapher runs may not be placed in the installation directory. Generally this is transparent to the user, but if you wish to use AnswerGrapher.xls or MGUsageCalcs.xls these files must be copied from the installation directory to the virtual directory. See Online Help - ADditional Information - Location of Files for details. Meter labels can now be up to 15 characters. (Don't want very large ones because they take up space in graphical displays.) As a result: Minor changes in Config Form format Meter status Form revised: Number of rows and columns calculated dynamically Column width default calculated from size of largest label Form can be resized by the user, and this adjusts the column widths Right click and hold over a cell to see the whole label (Only applicable if the user has made the form / columns narrow, and the whole label is not visible) Minor bug fixes (Startlog with no Adapters, file copy when changing dorectory, AnswerGrapher with no valid files) New in this edition (1st June 2012) MeterGrapher Version Ad2.04 Now deals correctly with regional settings that use 123.46,78 number formats. Changes to MeterGrapher, AnswerGrapher.xls and MGUsageCalcs.xls New in this edition (25th May 2012) MeterGrapher Version Ad2.03 Warning Messages - SMS and audible alarms On the Options / Warning Messages Form the user can: Click on Help to see an annotated screenshot. Designate a telephone number to recieve SMS messages, and test the link Define what type of warnings are to be sent Say that messages should be sent (user is remote from the PC) or not (user is near the PC) The system uses an SMS Gateway (BulkSMS.com). This takes the messages sent over the internet and transmits them to the designated phone. Using such a service requires no contract or set-up sees, but messages have to be paid for (See below). Each user is allocated an initial block of credits on CDI's account, so the user can try the function at no cost. Once these credits are spent the user would have to register at BulkSMS.com, purchase credits, and enter his registration details into MeterGrapher. The cost is around 0.05USD per message. The user can also select audible alarms - either voice or tone. The user will be at the computer while setting up MeterGrapher, and there will come a time when it is working satifactorily, and error messages are rare. At this point the user can invoke the messaging function or the audible alarms to attract attention when there is a problem, and so there is no need to monitor the software on-screen. Addition of a facility to read meter values from a file. For use with legacy meters that cannot be read directly, e.g. do not use the Modbus protocol. Meter data is read from OtherMeters.txt This gives a flexible, generic solution that is easy to implement and test Conceptually this file will be treated as another Adapter, allowing a wide range of MeterGrapher functionallity to be implemented. The meters will be defined in the Meter Library, allowing specification of flow units and conversion factors. NOTE: The meter type must be activated in the Meter Library, and CDI Flowmeters are not allowed in OtherMeters - this causes confusion because the software may try to read usage! Format of OtherMeters.txt: Meter Number ParamMPType Flow Value Meter Number ParamMPType Flow Value Meter Number ParamMPType Flow Value etc. Flow Value will be a positive decimal value. A negative value is interpreted as 'no data from meter' Note that the Conversion Factor supplied in the Meter Library will be applied MeterGrapher in general uses tab-delimited text files. Inclusion of the ParamMPType may be seen as inefficient, but facilitates several MeterGrapher functions: Meter selection AutoScan etc. The file is read as part of the normal MeterGrapher logging cycle. The user must ensure that the file is up to date when read. Minor enhacements: Ability to set both upper and lower axis values on the All Meters display Ability to select the size of the dots in the Meters Graph User is warned if log files are > 5 Mb New in this edition (29th January 2012) MeterGrapher Version Ad2.02 Addition of Quick Start Guide (QSG). This is invoked when MeterGrapher is started for the first time, and guides the user through the configuration set-up and on to logging initiation. A number of changes have been made to support this: By default password protection is not invoked. The use must use Options / Invoke Password. Log interval specification on the config form has been simplified. Enhanced documentation, particularly details of adapter choice (TCP or COM), and adapter set-up, including selection of IP Address. Batch files to start and stop logging are supplied. There are options to Start New Log Files, and to run minimised. Numerous minor bug fixes and enhancements. New in this edition (28th November 2011) MeterGrapher Version Ad2.01 Addition of MGUsageCalcs.xls. This imports MeterGrapher usage files and calculates usages over defined periods. Instruction for use can be found in the workbook. Comprehensive update of the web-base documentaton. Numerous minor bug fixes and enhancements. New in this edition (20th May 2011) MeterGrapher Version Ad2.00 Enhancements: User can choose the directory where MeterGrapher data files are stored. On installation all data files are loaded where the user chooses to install the software. Use Options / Select Directory. To create a new directory - just add \yournewdir in the Directory Name dialog. You will be given the option to copy files from the current location - choose Yes. Note that if you choose a diferent directory to store the files the MeterGrapher Uninstaller will not delete them - you must do this. Addition of Meter Library: MeterGrapher can now log any device that uses Modbus. The characteristics of the device must be added to the MeterGrapher Meter Library (MGML). CDI Meters Inc. maintains the MGML - if you have a device you would like added, contact CDI - the work should be complete withing 1 working day, and will be at zero cost. (NOTE: MGML provides the functionality previously embodied in a new product in development - AnyMeterGrapher - this is now scrapped.) Each entry in MGML specifies a meter type and parameter (e.g. CDI Flowmeter and Flow), together with the characteristics required to retrieve and correctly display the value. The user first specifies the meter types / params in the system (the default on software installation is CDI flow and pressure meters, so most users will not have to do anything), and then defines the meter numbers and types, as before. Some controls have moved to support this enhancement. The options to log usage, and to write the special flow output for import to Oracle are now on the Meter / Parameter Selection Form. This has resulted in a change to the data file structures, so if you have an existing installation download this new version 'on top' of the old version (do not use uninstall - all your existing data will be lost). When you run the new version it will detect the old files and update them automatically. New in this edition (16th March 2011) MeterGrapher Version Ad1.19 Enhancements: Error statistics removed from main form but still captured in diagnostic files. Meter error files (CDICE2009.txt and CDIUE2009.txt) removed. Not required now we have MADisgnostic.txt and CommsDiagnostic.txt Default meter label generated in config now has meter type as the trailing letter, so A016 becomes A016F (if it's a Flow meter). This helps with downstream processing. Number of Export files is checked, and the user is warned if the quantity is excessive. New in this edition (7th February 2011) MeterGrapher Version Ad1.18 Errors fixed: Diagnostic information showed meter errors if the Adapter lost connection during the polling of its meters. This is now corrected. General clean-up of error messaging (see also CommsDiagnostic below) Error counts and program termination: Hitherto the program allowed 1000 errors then terminated. It now allows 500 errors per hour. A limit is necessary because error messages are written to a file, and if the program got stuck in an error loop it could fill the available disk space and cause further difficulties. Note that the error count is reset when the first error occurs after the defined period. Dynamic calculation of Read Time Out and Connect Time Out (Version Ad1.13) was giving inordinately long times if the logging interval was large. Limited to a maximum of 5 seconds (If there has been no response in this time there is very probably a fault.) AnswerGrapher Users sometimes want to import logging data into Excel. A utility to aid import has been added: AnswerGrapher - this is installed in the MeterGrapher (MG) Directory. When this is initiated (user must enable macros) it shows details of the MG data files (logging period, number of meters, number of readings, logging interval). User then selects a file to import, and as well as drawing a graph the software highlights data values that are blank or extreme (More than 3 standard deviations from the mean). Counts and percentages of these values for the last file imported are shown on the DataSelection tab. This is very useful to give a quick visual impression of the data. The Version History tab gives details of the software functions and operation. CommsDiagnostic.txt This file records occasions when MeterGrapher does not receive timely information, either because it could not connect to an adapter or did not get a response from a meter. Format (file extract): Device Device Error Start Device Error End Delta (Seconds) New Logging Start A : 202.163.126.37 21/01/2011 20:38:30 21/01/2011 20:41:30 180 A037 21/01/2011 20:36:40 21/01/2011 20:41:30 290 A038 21/01/2011 20:36:40 21/01/2011 20:41:30 290 A229 23/01/2011 15:59:31 23/01/2011 16:01:06 94 Logging Period 21/01/2011 11:27:40 24/01/2011 10:22:06 255266 Column Headings: Device The meter or adapter Device Error Start Date / Time the error condition started Device Error End Date / Time the error condition ended Delta (Seconds) Duration of the error condition (Seconds) Note that records are written when the error condition ends, so entries are in this order. Additionally the logging period is written when logging stops, and is thus the last record. If a device is in error when logging stops the Device Error End field is blank, but the delta is calculated based on when logging stopped. The file is formatted for easy import to Excel for further analysis. How to use this information: The current status is displayed on the Meter Status Form. If a few meters are showing Meter Data Error then it is the meters that are at fault. If lots of meters are showing an error condition it is probably an Adapter fault. CommsDiagnostic provides an historical record. Repeated or prolonged outages of a meter or Adapter should be investigated. The file can be viewed while logging is in progress, but note that ongoing error conditions are not reported until they finish (The Meter Status Form shows current errors). CommsDiagnostic.txt is created in the MeterGrapher directory if it does not exist. Data is appended to the file with every run of Metergrapher. User may wish to delete this file periodically so it doesn't become too large. New in this edition (22nd December 2010) MeterGrapher Version Ad1.17 Enhancements affecting AMG - no impact on MeterGrapher. New in this edition (21st December 2010) MeterGrapher Version Ad1.16 Enhancement: Autodetects meter type (Flow or Pressure) during AutoScan in Config. No other checking - user must still enter correct values into the Meters Grid. New in this edition (19th December 2010) MeterGrapher Version Ad1.15 Enhancement: When logging the number of points in the graph is limited to 3000 (to prevent excessive CPU usage). When graphing old logs all points in the file are now shown on the graph (Tested up to 132,000 points) New in this edition (14th December 2010) MeterGrapher Version Ad1.14 Fault fixed: error in calculation of logging interval ahead of calculation of CTO and RTO New in this edition (14th December 2010) MeterGrapher Version Ad1.13 Enhancement: Connect Time Out and Read Time Out were fixed values - now calculated based on the number of adapters, the number of meters and the logging interval. Minor improvement to diagnosatic file writing New in this edition (6th December 2010) MeterGrapher Version Ad1.12 Errors fixed: If the CDICD2009.txt log file was very large the program failed when drawing the graph. The graph is now limited to the last 3000 points. When using Startlog.bat - no config file now trapped Initiation sequence changed so new log files are used to set up graphs. Avoids program crash when meters have been deleted. Status 'Was Out Of Limits - Now OK' not displayed if meter graph is in view New in this edition (2nd December 2010) MeterGrapher Version Ad1.11 Errors fixed: If all adapters failed to connect flow logging did not resume properly New in this edition (1st December 2010) MeterGrapher Version Ad1.10 Errors fixed: Logging was collecting the wrong meter flow values when a usage return value was delayed Log file values were not correctly written if an Adapter could not be connected MADiagnostic sometimes written to Export Folder MMRT (Measure Meter Response Times) was using the wrong Core routines Log Economy coding - wrong looping variable used Errors resulting from inability to find meter in YRecs Minor enhancements to MADiagnostic New in this edition (13th November 2010) MeterGrapher Version Ad1.09 During prolonged logging: Program was crashing - fixed CPU usage was building and meter logging was slowing down - fixed (This necessitated the removal of the 'Red Dot' indicator that a meter was out of limits on the All Meters bar graph. The same information is still avalilable on the Status Form) When User clicks Stop Log main buttons are greyed until the logging round is finished The feature that separates identical graph min/max values has been suspended Reports of errors that resulted in a user dialog (the user had to press 'OK') are now sent to the main form and the Diagnostic file, so processing can continue unattended. If 1000 errors accumulate, processing is terminated. The error count is displayed on the main form, and can be reset by the user by restarting logging. After a polling round has finished the Status form shows a countdown to when the next polling round will start Setting the Bar Graph width was wrong with high numbers of meters - fixed Maximum Meter Response Time (MMRT) does not use config values - fixed In meter renum - pinging a meter while autoscan is in progress causes an exception - fixed New in this edition (31st October 2010) MeterGrapher Version Ad1.08 Deleting Adapters or meters in Config now all works properly Graph of old log includes file name Scaling of Bar Graph improved In Config AutoScan button re-lights when scanning runs to completion Minor bug fixes New in this edition (21st October 2010) MeterGrapher Version Ad1.07 User has the choice (using Radio Buttons) to change the graph between Dots, Lines and Both. Note that joining the dots is not strictly correct - values are unknown between logged readings. However, in some cases the display is easier to interpret. Fault fixed: When the logging session starts the graph was displayed and auto-scaled. This now only occurs if the graph was not visible. (The user may have set up the graph to display a feature of interest and would not want it reset when logging recommenced) New in this edition (24th September 2010) MeterGrapher Version Ad1.06 Expansion to cover the requirements of AnyMeterGrapher (see separate documentation). No changes to standard MeterGrapher. New in this edition (18th September 2010) MeterGrapher Version Ad1.05 Faults fixed: Forgotten password feature corrected All Meters (Bar Graph Display) does not omit meters when the screen resolution is 1024 x 768. (USe right mouse drag to scroll the display) Enhancement: When the first round of logging has finished the graph of logged values is displayed for the first meter. New in this edition (18th August 2010) MeterGrapher Version Ad1.04 Fault fixed: High flow values were not logging correctly when using TCP/IP In meter renumber the initial default adapter is set (was blank) Minor bug fixes: Presssure meters using right-hand axis in graphs, recommended minimum log interval revised, in meter renumber the new meter number is checked for validity, in the config form a note on how to delete meters has been added. New in this edition (25th July 2010) MeterGrapher Version Ad1.03 Chart will scroll to keep the latest value plotted in view: If the last value plotted is in view, and the next value would be out of view, the graph will scroll To prevent scrolling pan or zoom so that the current point is out of view Graphs AutoScale when first opened The Open File dialog to graph old logs uses a Details view so the date modified is easily seen In meter renumbering the new meter number is checked to make sure it is not on the network startlog.bat corrected Improvements to web-based documentation New in this edition (16th July 2010) MeterAsker Version Ad1.02 Bugs fixed in config routine: - not working properly when a TCP adapter was changed to COM - USer could enter COM 4 (with a space). Config liked it, but chaos ensued New in this edition (25th June 2010) MeterGrapher Version Ad1.01 Log Meter Response Times confined to Set RTO module and rationalised Now allows polling of devices on a public IP Address. That address must be configured to divert messages on Port 502 (the default Modbus port) to the appropriate device. Software will not attempt to configure an adapter on a public IP Address Tab order on all forms updated. Log usage option moved into Config. Option not to create Oracle flow files added to Config. Print graph added. Simple function to print current graph on a single sheet. Allows connection to a TCP/IP adapter that has been allocated a dynamic IP address. User must know the DHCP name Various bug fixes. New in this edition (3rd June 2010) MeterGrapher Version Ad1.00 THIS VERSION IS NOT BACKWARD COMPATIBLE. IF YOU HAVE AN EXISTING VERSION THE CONFIG MUST BE REBUILT New Config file format and Config Input: Config Input: Must enter: At least one adapter Every adapter must have at least one meter Every meter must have a type (Flow ot Pressure), a number and a label Flow Units, Pressure Units, Log Economy and Log Interval are all mandatory Although the config can be saved without testing connections, connections must be tested before the config can be used. (Testing connections configures devices - this is essential before they can be used. Only required once.) Load Adapters into the Grid... Add up to 26 - can be local IP Addresses, or COM ports. Local IP Addresses are for GridConnect NET485 adapters COM ports are for B&B Electronics USTOPL4 adapters connected via USB May Test Connections at any time (provided some adapters have been entered!) MUST Test Connections at some stage, as this will configure new NET485 devices If you are not using NET485s, uncheck Configure Ethernet Adapters. You must configure these adapters yourself. Select Adapter to Process... All Adapters in the Load Adapters Grid will appear Having selected one... AutoScan will find meters on the Adapter (That's All! Meters for this Adapter must be entered manually) Add Meters for this Adapter... F/P - Flow or Pressure No. - Meter Number LLim - Lower Limit (Optional) ULim - Upper Limit (Optional) Label - Used in all outputs - All entries MUST be unique. 1 - 6 characters - As the Meter Number is typed a unique label is constructed, but the label can be changed to anything (1 - 6 characters, unique) Check / Refresh will check the grid entries and refresh the Label List Label List shows all labels. Duplicates are flagged with an asterisk, and counted (below the grid). If Duplicates is > 0 the configuration cannot be written to file. Write Config will check the validity of the values and then write to file To delete a meter blank its number in the Meters for Adapter grid. The changes will apparent when the adapter is re-selected. To delete an adapter blank its entry in the Load Adapters grid. New in this edition (17th May 2010) MeterAsker Version 3.02D New scheme for writing data to Oracle and then a revision to Oracle output format Faults corrected: In Config TCP autoscan gives inconsistent reaults Autoscan in meter renumbering (MR) inconsistent Autoscan in MR abort / restart does not start from the beginning Toggle Autoscan / Abort in MR locks up In Config using TCP do not allow remote users to update the NET485 Trap loss of ethernet connection (e.g power off NET485) In config if a meter is manually deleted from the list the types of the remaining meters is not always correct config was not trapping invalid user wait (non-integer) In config TCP autoscan results do not appear until scan finished / aborted In config when autoscanning grid is out of sync with polling In Config / TCP Set IP should try connecting to the device before setting it OK New in this edition (2nd May April 2010) MeterAsker Version 3.01D Software now traps the return of a non-numeric character from a meter. Under normal circumstances this does not happen but may occur if the meter experiences abnormal electrical conditions. The fix has been applied for COM connections but not (yet) for TCP/IP connections. If extreme logging parameters (short logging times relative to number of meters and response delays) are encountered warning messages are written to the screen and in the error log file but logging is not stopped. New in this edition (27th April 2010) MeterAsker Version 3.00D Known Issues: If logging with many meters and short log intervals having graphs on screen with many (000's) of points displayed can slow logging down. Shift (pan) the graph so older values are not displayed. Sometimes 'Set IP' times out trying to connect - try again - mostly works first time, but occasionally three goes have been required. Running on a laptop under Windows 7 got lots of CRC errors measuring response times in the Config form Addition of connection via TCP/IP using a GridConnect NET485-MB device. This is a new feature and not fully tested, although at this time no bugs are known. Wiring the NET485 - see wiringNET485.doc (Later - for now - in wiring to the NET485 device we wired A/B from the meter to B/A on the device also jumped TXDA/RXDA and TXDB/RXDB.) You must have one CDI meter that sets RS485 signal line biasing - contact CDI for details. Configuring the NET485 - see configuringNET485.doc (Later - for now - install the software and assign a static IP address). No other configuration is required - see below Running MeterAsker over TCP/IP - Having wired the device and set IP address etc. (see above) Running MeterASker will set all the other configuration values for the NET485. Run MeterAsker, choose options / config, select TCP as the Connection Method, type in the IP address and click Set IP. Detection of meter type - Flow or Pressure. This is now undertaken during MeterAsker Configuration, and is recorded in the config file. Old config files are automatically updated. Much more information available about meter response times and logging intervals. See config form Wait for Device Reply Clicking on the Meter Status Grid to show a meter graph is now reliable New in this edition (12 March 2010) MeterAsker Version 2.00D Known Issues: Possible to provoke I/O error 103 if Stop Logging coincident wil meters being polled. Ignore and carry on. On rare occasions with short log intervals can get I/O error 32 while logging. Unfortunately this stops logging. In graphs when a meter is added to the plot after logging has started its lower and upper limits extend back to zero on the X Axis. This does not affect scaling - merely cosmetic. This MeterAsker is not compatible with the current release of AnswerGrapher (Excel). New version of AnswerGrapher is in the final stages of testing and will be released shortly. Setting the width of the All Meters display needs attention. New log file formats were invoked in V1.95D. MeterAsker V2.00D will automatically update any files in the old format to the new format. The user gets a message of the form - 'nnn old log files (flow data and flow errors) have been converted to the new format.' (Note: the old flow and error files are not removed.) Details of the changes are as follows: Flow Log Files Comb Log Files Current CDIFD2009.txt CDICD2009.txt Old CDIFD20091.txt CDICD20091.txt CDIFD20092.txt CDICD20092.txt etc Changes are to file headers only - data is unchanged. Thus FlowDateTime Meter23 Meter24 becomes CombDateTime FMeter23 FMeter24 Files are still tab delimited. More robust config file updating, including more accurate retention of upper and lower limits as meter numbers are changed. Option to enter a Y axis maximum on the 'All Meters' form. A zero value (the default) causes autoscaling. This is fine most of the time, but if a meter is powered down and up it can return spurious high values, and manual scaling is desirable. A warning is displayed (on updating the config) if the chosen logging interval is shorter than the value recommended (taking in to account numbers of meters and meter response times). If a warning is displayed the panel on the config form that deals with these issues is made visible (if it wasn't already). Miscellaneous bug fixes. Note about the Log Economy feature (V1.80D 21 February 2010): This feature limits the entries in log files. If graphs are being displayed while logging all points are displayed. New in this edition (5 March 2010) MeterAsker Version 1.95D THIS VERSION IS NOT BACKWARD-COMPATIBLE WITH EARLIER VERSIONS. LOG FILE FORMATS HAVE CHANGED. UTILITIES TO CHANGE EXISTING LOG FILES TO THE NEW FORMAT WILL BE AVAILABLE SHORTLY, TOGETHER WITH A NEW ANSWERGRAPHER. Option to not log flow Integrated treatment of flow and pressure values Software detects which meters are flow and which are pressure Writing of complete log file lines to minimise log file format errors. In MeterAsker graphs: flow uses the left axis, pressure the right points are added to the graph as logging takes place The AutoScale button rescales everything Click any axis (right on the line) to rescale that alone Zero / Negative logging time: When logging rapidly (e.g. 3 meters every 500 ms) the following issues arise: logging (actually polling the meters, processing and writing the logs) is paused to respond to system messages. This is necessary (until I figure out threading!), otherwise you could do nothing else (e.g. resize a window or make selections). Hitherto the software backlogged the missing samples and tried to catch up. Now it doesn't, so negative logging times are much reduced. It is still possible to specify config values that are too severe, and the logging will stop. However, additional diagnostics are available. On the Config form, in the panel that deals with Wait For Device Reply, there is a check box called Log Meter Response Times. (Note: this is not part of the config and is not written to file. It must be checked during each session.) If this is checked the following happens: If, in the config form, the user chooses Measure in Wait for Device Reply the actual meter responses (ms) are displayed in the Main window messages area. When logging the response time of the first meter in the list is reported. If the Logging time is negative this is also reported, together with its magnitude. Generally this will be once only, while something else was going on (e.g. moving or resizing a window). However, if values persist it indicates that the logging parameters are too severe. Note that if other MeterAsker windows are busy, this slows logging! Thus if you are displaying a graph while logging, if the graph has lots (1000s) of points visible, logging is slowed. This is evident from the diagnostics described above. If you zoom in on a portion of the graph etc. things improve. Note also that turning on the diagnostics slows things down! New in this edition (21 February 2010) MeterAsker Version 1.80D Automatic program load, connection to meters and log start. In the MeterGrapher directory there is a file called StartLog.bat. Do leave this file in its current location! Call it at any time to start the logger. Additional flow data file. A new file of flow information is generated. CDIFXD2009.txt contains the same information as CDIFD2009.txt but looks like this: FlowDateTime MeterNo FlowValue 40228.755093 15 1.20 40228.755093 28 7.30 40228.755093 29 0.50 40228.755191 15 1.10 40228.755191 28 7.10 40228.755191 29 0.60 etc. The user does not need to do anything - the software detects the presence of the file and creates it if necessary. The existing scheme of log file renaming is used. Password protection. The screens to change the configuration and renumber meters are password protected. Ask CDI Meters for the default password. The user can change the password as required (having entered the current password) and there are no constraints on the password. There is a forgotten password? facility that resets the password to the default value. Note that the protection is of a commercial standard and will resist playful or curious users - a determined hacker can probably get round it! Note that the password is case-sensitive. Different intervals for data recording and level / alarm display updates. A scheme has been invoked that will ensure that 'interesting' values are logged while keeping the log files as small as possible. The logic is as follows: Is the value now polled from any meter 'very different' to the one that was last logged? If not, store the values, but don't log them If it is, log the previously stored values (which by definition are not 'very different' from the previously logged values) and the values now polled. The exact point at which things changed is thus captured. In this way periods where all readings are stable are not logged but all the readings required for diagnosis when things become unsteady are. The user chooses what constitutes 'very different' in a factor called 'Log Economy' on the Config Change screen. This is the change (%) in any meter value that will cause values to be logged. The default is zero which will log all values. 10% is recommended to try initially, but the best value will depend on the steadiness of the user's flows. New in this edition (10 February 2010) MeterAsker Version 1.70D Correction to errors in V1.60D following extensive testing New in this edition (25 January 2010) MeterAsker Version 1.60D THIS A DRAFT VERSION - IT HAS NOT BEEN COMPLETLY TESTED For Flowmeters only - User can set a lower and upper flow limit for each meter in the config section When online, software displays the status of each meter Click in the status grid to see a graph of the meter flow since the last config change. The graph has lots of functionality! New in this edition (18 January 2010) MeterAsker Version 1.50D THIS A DRAFT VERSION - IT HAS NOT BEEN COMPLETLY TESTED Deals with Flow and Pressure Meters. Writes separate log files for each type. Allows user to draw graphs of flow meter values, from current or previous configuraions Revision to meter response measurement and value setting New in this edition (04 April 2009) MeterAsker Version 1.31 Wait for device reply - advanced feature required only by users who have slow meter responses or require very small logging intervals. The software will give an error message during logging (and stop logging) if the system characteristics and parameters necessitate the use of this facility. When MeterAsker is logging, if a meter response is not received, the software will attempt to re-sample - for as long as it calculates that it has time before the next sample is due. Error preventing large log intervals (e.g. 24 hours) corrected. AnswerGrapher Version 2.2 Changes to align with MeterAsker version 3.1 - transparent to User Corrected error when Data Save Data is cancelled New in this edition (13 Feb 2009): MeterAsker Version 1.22 Compares the log files it is using to the configuration and starts new log files if the configuration, in terms of meters, does not match. Allows the user to start new log files, or continue writing to the existing ones. AnswerGrapher Version 2.0 DataSelection feature. When the Workbook is opened the available log files are examined: DataSelection lists file names, start/end dates/times, logging frequency, number of readings and the meter numbers of all flow data files. User can then select one file from this list. If the user deletes rows from a file loaded in AnswerGrapher he has the option to save the truncated text file (overwriting the old one). AnswerGrapher recognises when it is not in the same directory as when the last data file was loaded, and takes appropriate action. These features take away most of the need for the user to examine the log files. Version 1.21 New in this edition (04 Feb 2009): MeterAsker - Change MeterAsker Configuration (meter units, COM port, meter numbers, log interval) MeterAsker - Small log intervals allowed - down to fractions of a second Installer - Places files in User's chosen location, and adds short-cuts to Programs Menu New in last edition (13 Dec 2008): MeterAsker - Initiate in logging mode from the Command Line. MeterAsker - Change Meter Numbers MeterGrapher has two main components: MeterAsker polls the meters and records flow values AnswerGrapher is an Excel Workbook configured to read the recorded flow values and generate graphs. SET UP: Download MGInstall.exe from the web site (http://cdimeters.com/downloads.html) and run it. This will create a directory and copy the files, then add shortcuts to the Programs Menu, including an Uninstall shortcut. Other shortcuts are: MeterAsker.exe - does the logging. Can also set the MeterAsker configuration, and change meter numbers. AnswerGrapher.xls - is the Workbook designed to read the log files and create graphs StartLog.bat - a batch file that initiates MeterAsker in logging mode MeterGrapherReadMe.txt - this document OpenDirectory - Opens the folder where MeterGrapher is installed If downloading for the first time, install all components. If re-installing, the Excel and text files component will overwrite existing files and data may be lost. Make a back-up first. Start MeterAsker and change the configuration to match your set-up. Menu / Options / MeterAsker Config example Values are: COM3 Port scfm Flow units (scfm, Nm3min, Nm3hour) 1 Log Interval (*) 2 Meter count 13 Meter address 14 Meter address (*) Integer mins. Set to zero for Test Logging [every 10 secs for 1 - 10 meters, 20 secs for 11 - 20 meters, 30 secs for 21 - 25 meters], negative for millisecond interval [-5000 logs every 5 seconds, 200 logs every 0.2 seconds] RUNNING: Run MeterAsker.exe Menu / Line / On Line Should get messages about the status of the meter(s) or may get... SioReset error - Code = -103 Hardware Error (Connected?) - COM? (where ? is your port) ...if the software cannot understand your 485/USB setup. Check that the adaptor is connected, and check the Com port designated in the configuration. Once you have a 'Meters OK' message... Spot-Check Flow or Usage as required Reports could be: The value 'No value returned from meter' 'Data check error from meter' Start Logging Will append to existing log files or create new ones Files created are: CDIFD2009.txt - FD - Flow Data CDIFE2009.txt - FE - Flow Errors CDIUD2009.txt - UD - Usage Data CDIUE2009.txt - UE - Usage Errors If new log files are required (user's choice, change in meter configuration) existing files are renamed. Look in AnswerGrapher DataSelection to see available files. (values can be spot-checked while logging - spot checks are not written to the log) Toggle write values to screen as required At this point you can minimise MeterAsker and do other work. Stop Logging Exit MeterAsker OTHER METERASKER FACILITIES You can initiate MeterAsker in logging mode from the Command Line. This may be useful as part of a process initiated after, say, a power outage. Run StartLog.bat, or incorporate its contents into your own scheme. When StartLog.bat is run a command line window is opened. This will close when MeterAsker terminates, or can be closed by the user. MeterAsker can change the numbers of the meters on your system. Initiate the software, and after Menu Line/OnLine is selected the Options/Meter Renumber menu item is enabled. Follow the on-screen instructions. There are two options: StepWise - this guides the user through the process and invokes checks on the user's entries. FastChange - Rapid unchecked meter number changing, for use primarily in meter production. Wait for device reply (ms) i.e. Having sent a request for information to a device, how long should MeterAsker wait for a response? Now part of MeterAsker (Version 1.3) Configuration. The form (Started from Options / MeterAsker Config) now includes a Wait for device reply panel. This is an advanced feature that few users will require, so initially it is hidden. The form has a show / hide button that toggles the display. The panel includes: Config. file value Value (ms) currently in MAConfig.txt Note that old config files do not contain this value, but the software takes care of everything. If the user does not set up values a default (200ms) is used, and the config file is unaffected. If the user sets values the config file is updated. The software determines which version of the config file is in use, and acts accordingly. Measure button Click this to test meter responses. 5 samples are taken from each meter Clearly 3 meters taking a second each will need 15 seconds Progress is shown - dots appear in the Measured box The MAXIMUM value is returned Only used to calculate the Recommended Recommended Twice the Measured Only used to give an initial User value User Value User may choose any value Anything bigger than the measured will probably be OK Choosing a value smaller than the Measured is allowed, but expect a lot of error messages! The User value is the one written to the config file and used in logging Min. log interval Calculated from number of meters * User value * 2 * 1.25 The * 2 is because we measure flow and usage The * 1.25 allows for computational overhead and a little slack Only used to inform the user The user sets the required Log Interval. Clearly choosing something much smaller than the Min. log interval is asking for trouble! The software will not fail, but a lot of error messages may be returned. The Update Config button is enabled when the config has changed. (You can exit without updating) The main MeterAsker routing will insist that you Update (or exit without updating) before setting the system on line. Once on line the configuration form (if still visible) is disabled. Even if you have your own analysis software and do not intend to use AnswerGrapher (and assuming you have MS Excel), running AnswerGrapher during set-up may help with diagnostics. It is very easy to use! AnswerGrapher.xls This can be run while MeterAsker is running - it will read the file so far if logging is in progress. When starting you will be asked if you wish to Enable Macros. Yes (or none of it will work!) Go to the DataSelection sheet and choose a file to import. Check the Graph. Go to the LoadsToCalculate sheet. Specify the calculations. Press the button. Consider file management. If you rename the log files (Best to do this to the whole set!) MeterAsker will start new ones. A naming scheme for AnswerGrapher files would also be useful. LIMITATION: Maximum 25 meters. Please pass any comments to CDI Meters. Colin Gray 15th March 2009