LEFMLink 2G Version 1.2.27

Uninstall any previous versions before installing.  If there is a "drive" in addition to C: on the target system, 
  a the folder "LEFMLink2G Data" may be installed on that drive.  If so, this folder needs to be moved to the C:\ drive, 
  or the program will not run.  It is expected that this issue has been fixed for Version 1.2.14.  For Windows 7, 
  see "Other known issues" below for important information.

For Simulation mode, three files are required:  a datalog file (.csv) without a header and a matching
  setup (.cal) file, and a patch file with register values that aren't contained within the csv, nor 
  cal files.  This file will be of the form NonCalNonLogSimData MM DD YYYY 123456.ini, where MM is the month,
  DD is the day, YYYY is the year, and 123456 is the time on the day this file was created.  This file
  will be created and written to the same directory (C:\Program Files\Cameron\ModWorXPro\build files) in
  which the ModWorXPro.exe resides.  Each of these will need to be selected after clicking Ctrl-S and enabling
  Simulation at the Connection Setttings screen.

For simulation, the functions (like many of those found on the screens beneath the "Tasks" and "Tools" menus)
  that write to holding registers will not work.

Modbus TCP should work for all but pre-Heme Analog Input and Analog Output screen.

USB Serial adapters -- some are known to have issues.  Usually B&B Electronics adapters have been pretty
  stable.

EXpress Connect and auto datalogging are only available in serial mode, not Modbus/TCP.

To Express Connect and automatically start datalogging, when you get to the Connection Settings screen, check
  the "Use these setting to automatically connect next time" box, and then check the "Datalog automatically on startup"
  box.  Then when you set up datalogging, 2G will use that path and the setting on the Connection Settings screen to 
  automatically connect and start datalogging.  Do not alter anything or click any buttons at startup when autologging,
  until 2G is data logging, unless you want to take it out of autologging mode.  To do that, uncheck the "Datalog 
  automatically on startup" box, and then uncheck the "Use these setting to automatically connect next time" box
  on the Connection Settings screen.  Be quick, you have 5 seconds to do that.

Alternatively, auto datalogging can be enabled or disabled in the ModWorXPro.ini file (be careful altering this file,
  improper alteration can cause the program to malfunction).  The following three lines dictate weather and how auto
  datalogging is executed:
    AutoLogFileDir=
    Automatic=
    DataLogOnStartup=
  ModWorXPro.ini should be located in "C:\LEFMLink2G Data\ModWorXPro\build files" directory.  This is the file
  that should be modified if manually modifying configuration parameters.  There is also a copy (for reference)
  in "C:\Program Files\Cameron\ModWorXPro\build files" directory on Windows XP, and 
  "C:\Program Files (x86)\Cameron\ModWorXPro\build files" directory on at least some Windows 7 systems.
  Always make sure the terminate backslash "\" is in the "AutoLogFileDir=" line.  A 1 after "Automatic=" and
  "DataLogOnStartup=" will enable autoconnect and auto datalogging.  A 0 will disable.  For instance,
    AutoLogFileDir=C:\
    Automatic=1
    DataLogOnStartup=1
  will enable express connect and auto datalogging into the C:\ root directory.  
  Caution:  changing connection settings in this file, such as baud rate, are not as obvious as they may seem.

There are three lines in the ModWorXPro.ini file that select a different html file for either 200MU code, 639 code, 
  or Gas Meter code:
    'MainScreenHTML=LEFMLinkDeviceMainDisplay200MU.htm
    MainScreenHTML=LEFMLinkDeviceMainDisplay.htm
    'MainScreenHTML=LEFMLinkDeviceMainDisplayGas.htm
  The three lines above select for 639 code.  The apostrophe at the beginning of the other two lines makes those
  two lines comments.  Only one of these three lines should ever be uncommented at any time.  To use for Gas, 
  do as such:
    'MainScreenHTML=LEFMLinkDeviceMainDisplay200MU.htm
    'MainScreenHTML=LEFMLinkDeviceMainDisplay.htm
    MainScreenHTML=LEFMLinkDeviceMainDisplayGas.htm
  To use for 200MU code, do as such:
    MainScreenHTML=LEFMLinkDeviceMainDisplay200MU.htm
    'MainScreenHTML=LEFMLinkDeviceMainDisplay.htm
    'MainScreenHTML=LEFMLinkDeviceMainDisplayGas.htm

What has changed since Version 1.2.26

-Bug fix for range check error.

What has changed since Version 1.2.25B

-Support for G3 SW000110.

What has changed since Version 1.2.24

-Support for G3 SW000088.

What has changed since Version 1.2.23

- Bug fixes for path status, set time, Signal Diagnostics red/green alarm indicators paths 1-4, and "sticky" alarms
  for G3 (SW000070 and SW000082).

What has changed since Version 1.2.21

- Fixes to Modbus/TCP login for G3.
- Support for SW000082.
- Removal of Test/Echo screen for G3.

What has changed since Version 1.2.20

- Installation files cleanup.

What has changed since Version 1.2.19

- Fix for software hanging on certain virtual com port implementations
- Additional Modbus/TCP improvements for G3 liquid.
- G2 Modbus/TCP bug fixes

What has changed since Version 1.2.18

- Modbus/TCP improvements for G3 liquid.

What has changed since Version 1.2.16

- Support for G3 liquid (SW000062 and SW000056).

What has changed since Version 1.2.15

- Fixes for not correctly logging Receive Period, Fluid Temperature, Echo Path Dn dB, and Echo Path Up dB when
  communicating to 101A639 firmware via Modbus/TCP.

What has changed since Version 1.2.14

- Fixes to Gas Path Triggering "Log All Waveforms" function.

What has changed since Version 1.2.13

- It is expected that the "LEFMLink2G Data" directory will always be installed on the C:\ drive.
- For 101A960 firmware the Data Logging option in the menu under Tasks has been disabled, as that's specific to
  liquid.
- Updated hardware and software manuals for gas and liquid.
- Modified "Simulate 8 Path Heme.cal" to add VOSUNITS, register 166, for use in simulation.
- Increment totalizers for gas in simulation mode.
- Fix trend screen standard deviation.

What has changed since Version 1.2.12

- Append Tag number and serial number to the end of the header string, when include the header string in the 
  log file.
- Added two Data Quality values for 101A639 code for each path to the log.
- Bug fixes to waveform table value remants remaining from previous waveforms.

What has changed since 1.2.11:

- Bug fixes for AckAlarm and Units for 101A960 firmware.

What has changed since 1.2.10:

- Tab-delimited logging support for 101A639 firmware.
- Bug fix where a system that did not have a serial port, but was trying to operate using Modbus/TCP, but wouldn't run.
- ACK Alarm support for 101A960 firmware.
- In log file, for 101A639 firmware, relabeled "Density Input" to "Turbulence."
- For 101A960 firmware, ignoring zeroing the first 5 values in the waveform to help with scaling.
- Support for MPa units (from register 102) for 101A960 firmware.
- Support for Plane Balance Ratio and Asymmetry Ratio for 101A960 firmware.
- Register 784 and 785 support for flow units and totalizer units for 101A960 code.
- Display both positive and negative totalizers on the main page for 101A960 firmware.
- Removal of ability to reset totalizers for 101A960 Gas firmware.
- Support for 10-digit long integer totalizers for 101A960 Gas firmware.

What has changed since 1.2.9:

- Fixed bug in Analog Input RTD cold fluid calculation
- Fixed bug associated with SOS cross-check registers and logging for Gas (101A960) firmware.
- Fixed bug where "Save Table to File - Dn" button on the Path Triggering screen incorrectly saved Up values

What has changed since 1.2.8:

- Fixed a bug that could cause Range Check Errors when using in Modbus/TCP mode.
- Fixed a bug where the wrong values were being read for Velocity Profile from the compare file for Health Audit.
- Modified Analog Input RTD calculation to incorporate cold water situation.
- Added SOS cross-check registers and logging for Gas (101A960) firmware.
- Inside Diameter and SOS Units fixes for Gas (101A960) simulation mode.
- Tab delimited logging for Gas (101A960).  *.txt files are tab delimited, *.csv are comma-separated.
- Support for tab delimited log files for Gas (101A960) also added for simulation mode, health 
  report, and waveforms.
- Fixed a bug where selecting a specific number of samples to log only worked half of the time.
- On first run of the software, a checkbox asking "Disable Data Logging?" will be visible.  This is the only time
  this question will be presented.  If the user never intends to datalog with 2G, check this box and datalogging
  will be permanently disabled.  Leave unchecked and datalogging will be permissible.  After this first run, it
  can be changed only by appending "EnableDataLogging=1" to enable datalogging or "EnableDataLogging=0" to disable 
  datalogging, at the end of the "[Connection] section in the ModWorXPro.ini file, located in the 
  "C:\LEFMLink2G Data\ModWorXPro\build files" directory.
- Waveform displays on the Path Triggering screen should be more stable for 101A960 firmware.
- Fix to "Set Time" where sometimes feedback to time change not provided.
- Fix for presentation error for Gain Split alarms, where it was being displayed as a TP Tdown alarm.  

What has changed since 1.2.7 to 1.2.8:

- ModWorXPro.ini and other files are additionally now located in "C:\LEFMLink2G Data\ModWorXPro\build files" directory.  This
  should eliminate or reduce the need to change User Account Control (UAC) settings on Windows 7 and Windows Vista computers.
- Removal of screens/fields for 101A960, that are not pertinent to 101A960.
- Addition of ReceivePeriod for datalog for 101A639 code.
- Screen aesthetics changes.
- Fixes to entering password.
- Improved 101A960 simulation.
- DIP switch positions added to Signal Diagnostics screen.
- Addition of second Analog Output for 101A639 code, version 08.03.01 and later.
- Updates to Meter Configuration Settings


What has changed since 1.2.6 to 1.2.7:

- Option to include Impedances in datalog file.
- "Menu Configuration Settings" under Tools, instead of "Holding Registers Explanations" under Help.
- Units for 101A960

What has changed since 1.2.5 to 1.2.6:

- Simulation now works without needing an a COM port.
- When running in Modbus TCP, a serial COM Port (of some type) should no longer need to be present. 
- In simulation mode, should be able to access all screens without having a working serial port.  
  Functionality will be limited.
- In simulation mode, should be fewer instances where the software may crash by clicking on an unsupported button.
- Added FRViewer.exe to the "build files" directory.  Install and run this program to view .fp3 files
  outside of 2G.
- Under Help | View Register Explanations, you can see explanations for the holding registers and the
  values for those registers at the time it's loaded (only available for serial, not Modbus TCP).
- Screen freezing when exiting Path Triggering screen should be resolved.
- Ability to express connect and automatically start logging has been added.
- SNR values are now displayed as integers on paths 5-8.
- Actual units added for A/I scaling window, rather than "eng value."
- Cursor defaults to password box for setup download window.
- Exit button on Path Triggering has been moved.
- Ability to do custom data logs -- note that these logs will be incompatible for use in simulation mode.
- Additional datalogging functionality.
- Fixes so gas simulation works -- note that not all values can be reproduced for gas, as the datalog does not
  have all of the data required.
- 200MU code should only show the one path if IR registers 1114 - 1116 indicate that.
- For multi-day datalogs, a "-YYMMDD" will be appended to the name for days subsequent to the first day of logging,
  instead of -2, -3, etc.

What has changed from 1.2.2 to 1.2.3:

- Added State Vector Quality fields to Signal Diagnostics screen.
- Text field showing the IP address of the connected meter when in Modbus/TCP mode.

What has changed from 1.2.0 to 1.2.2:

- Support for firmware 639 version 08.01.01 new fields (Refraction_R and Refraction_CF)
- Support for 200MU code.

What has changed since for 1.2.0:

- Support for firmware 639 version 08.01.01 new fields (Refraction_R and Refraction_CF)
- Modbus TCP Master support
- Additional fields added to datalog.
- Data logging splits files for each calendar day
- Fix for Access violation at address 0066D73F in module ModWorXPro.exe. Read of address 00001088.
- Support for multiple instances running concurrently.
- Support for 200MU-107.

Fixes:

- Various bug fixes.
- Most issues with Password entry.
- Checksum for Modbus/TCP now displayed

Other known issues:

- Recording all waveform data in gas mode crashes the program.
- Windows 7:  It's possible with versions prior to 1.2.8 in Windows 7 that running 2G will utilize copies of 
  ModWorXPro.ini, ModWorXPro.exe and possibly other files that the OS keeps in a virtual store.  This can cause 
  problems if manually altering ModWorXPro.ini or uninstalling an old installation and installing a new one, or even 
  reinstalling a current one.  These files may be found in a folder something like 
  "C:\Users\<username>\AppData\Local\VirtualStore\Program Files (x86)\Cameron\ModWorXPro\build files"
  If using Windows 7, after uninstalling LEFMLink 2G, do a C:\ hard drive search for ModWorXPro.ini and 
  ModWorXPro.exe and delete any that exist.  And then you may reinstall after doing this.  It's possible
  other files may need to be deleted, but these are the most critical.
  With Windows 7 computers, the OS doesnt like programs changing files that are in Program Files folders, 
  which 2G does, so the OS creates copies in the VirtualStore directory that it changes and keeps track of.  
  Everything generally works fine until you want to change one of those files (namely ModWorXPro.ini) directly.  
  You change the file, but Windows 7 still has the program using the file in its VirtualStore, which will 
  differ from the one in C:\Program Files (x86)\Cameron\ModWorXPro\build files.  Until changed in a future 
  release, a way around this is to type UAC in the Search programs and files box, and then select 
  Change User Account Control settings and move the scroll all the way to the bottom next to Never notify 
  and click OK.
_ In Windows 7, there may still exist some exceptional issues (namely an access violation in module CC3260MT.DLL) that
  may still arise.  Usually this can be resolved by changing the User Account Control setting to "Never notify."    
- Still no scroll bar on the Connection Settings screen
- Keep fields in the .cal files under 80 characters long
- On first use of the software, sometimes the "Connect Now" is not visible on the Connection Settings screen.
  Usually by making the window sizeable and then expanding the window downward and then maximizing, you can
  then make it visible.  On netbooks, changing the aspect ratio or resolution may be necessary, in addition.
  Alternatively, Alt-C should active the "Connect Now" button.
- Header and Append File options not accessible when using Spanish
- "Menu Configuration Settings"/"Holding Registers Explanations" only work for serial connection.
- Possible issue when entering a bad password, where it is not indicated and ModworxWriteErrors.txt written instead.