ACM Software Release Contents

Information about ACM Security can be found: AUTOSOL Security Center

Releases In Active Maintenance

*Use the "shift" key to sort by multiple columns.

Release	Type	Category	Description	Affects Published Output
9.1.2	Issue	Alias Groups/Items	Corrects an issue that caused items within an alias group to be internally advised and ready for MQTT publishing by a copied device object, even when the alias group did not have MQTT publishing enabled.
9.1.2	Issue	API	Corrects an issue that prevents a solution utilizing the API in an ASP.NET environment from finding the AutoSol.ACM.Config.Client file.
9.1.2	Issue	Client Application	Restores the User Preference Activate Alias Tags on Status Tab "Only when Alias Group tags are active" option.
9.1.2	Issue	Client Application	Removes the unused 'Alarm Service' fields from the ACM Connect to Server Options.
9.1.2	Issue	Client Application	Prevents spaces from being saved at the beginning or end of the Connect String field.
9.1.2	Issue	Client Application	Increases the character limit of the "Provider String" field to 512 characters for the EFMDB and DB output types.
9.1.2	Issue	Client Application	Changes the default button on the "Delete Objects" dialog to "Cancel".
9.1.2	Issue	Client Application	Prevents the Config Client from disconnecting from the server when using special characters in the search tool.
9.1.2	Issue	Client Application	Corrects sorting for datetime columns in the Dashboard.
9.1.2	Issue	Client Application	Corrects an issue that caused the search functionality to only find matching objects if those objects with descriptions.
9.1.2	Issue	Client Application	Corrects an issue that caused the search functionality to fail to find matches when there was a leading or trailing space in the search criteria.
9.1.2	Issue	Client Application	Corrects an issue that could leave items advised and polling when switching between different alias groups on the Status tab of a device configuration form.
9.1.2	Issue	Client Application	Changes the labels in the Publisher CSV from "Publish Report Records" to "Publish All Report Records" and "Publish Prove Report Records" to "Publish Prove Records".
9.1.2	Issue	Configuration Database	Updates variables in two stored procedures, asi_spResetPublisherPosition_Filter and asi_spResetPublisherPosition, from INT to BIGINT to allow for large archive sequence IDs.
9.1.2	Issue	Configuration Database	Updates the asi_spFrequentalarmandEventReport stored procedure to use the alarmLimitEvent parameter.
9.1.2	Issue	Configuration Database	Adds the table 'EdgeEFMConfigurationErrors' to the ACM database to record errors that may occur when publishing EFM data from the Edge. These errors will be visible in the 'Error Log Report Last X Days' report.
9.1.2	Issue	Configuration Database	Modifies the "Publish a Device" command on the Publisher Command tab to publish all records, regardless of filter settings. Previously if the filter was for meters only, it would log "No records published for ObjectId = ### as it is not contained in the filter". This is a database update to the asi_spInsertPublishObjects4 stored procedure. *Effect On Published Output: When using the "Publish a Device" command from a publisher, all records will be published for that device regardless of filter settings.	X
9.1.2	Issue	Connections: Base Connection	Corrects the failure retry count of polls that occur after a priority interruption.
9.1.2	Issue	ExportMDB	Prevents ACM from replacing an existing Access database backup file with an empty one if asiData cannot connect to SQL Server.
9.1.2	Issue	General	Corrects an error that could occur while saving objects if asiData was disconnected from the SQL Server when using the SQL Driver MSOLEDBSQL version 18.6 or later. The error messages in ACM addressed by this fix include: "Could not find prepared statement with handle #" and "Procedure {procedurename} has too many arguments specified".
9.1.2	Issue	General	Corrects an issue that caused an invalid timestamp to occur on Leap Day.
9.1.2	Issue	Importer/Exporter	Prevents an error from occurring when importing a "Connect String" with a trailing space.
9.1.2	Issue	Importer/Exporter	Prevents ACM from updating references when the "Cancel" button is clicked from the Import form.
9.1.2	Issue	Importer/Exporter	Corrects an issue encountered while importing Alias Groups with empty record values which prevented the entire Alias Group from getting imported.
9.1.2	Issue	Item Server	Corrects an issue that caused MinutesSinceComplete to be incorrectly calculated immediately after DST.
9.1.2	Issue	Item Server	Reduces nuisance log messages that appeared while the ItemServer waited for asiDATA to start. Now the service will wait until asiDATA is running before attempting the IPC connection.
9.1.2	Issue	Kinder Morgan Modbus	Improves the handling of unexpected sequence number and archive reset conditions.
9.1.2	Issue	Logging	Adds additional information to the logger if asiLogger is unable to retrieve the local time and fails to generate a new file at midnight.
9.1.2	Issue	MQTT	Corrects an issue that sent erroneous DDEATH messages to the MQTT broker when the interval on an alias group changed.
9.1.2	Issue	MQTT	Corrects an issue that caused a partially configured broker to require an ItemServer restart before being able to complete the configuration.
9.1.2	Issue	OPC UA	Corrects the data type of the initial value update for archive 'Move' and 'Reset' items.
9.1.2	Issue	OPC UA	Prevents inactive OPC UA items from internal updates.
9.1.2	Issue	OPC UA	Corrects an issue that caused the 'Restart OPC UA Service' message to be shown when only log flags were changed on the OPC UA configuration dialog.
9.1.2	Issue	OPC UA	Corrects an issue that prevented a monitored item from being created on an address space node that has a bad status.
9.1.2	Issue	OPC UA	Corrects an issue where the status of a new monitored item would be set to Good when the associated node had a bad status.
9.1.2	Issue	Prosoft Modbus	Modifies the driver to evaluate the contract hour unit and convert the value accordingly. *Effect On Published Output: The contract hour will be converted using the correct contract hour unit.	X
9.1.2	Issue	Protocols: BSAP Protocol	Corrects an issue that caused BSAP Devices to fail to retrieve history over ethernet connections.
9.1.2	Issue	Protocols: ControlLogix Protocol	Corrects an issue that prevented the LastPollSuccessTime from updating correctly due to CIP Forward Open errors.
9.1.2	Issue	Protocols: DNP3 Protocol	Corrects the DNP3 meter type and calculation method mapping. Previously 'AGA3-2013' was published as 'AGA3-1992' and 'API 12.2 Volumetric' was published as 'Linear Mass'. Meter Types 'Ultrasonic' and 'Positive Displacement' were previously empty in published output. *Effect On Published Output: The correct calculation method and meter type will now be published.	X
9.1.2	Issue	Protocols: DNP3 Protocol	Modifies the Move and Reset commands for alarm and event pointers so that they will execute as long as any meter is assigned.
9.1.2	Issue	Protocols: DNP3 Protocol	Prevents an OPC Client from activating DNP3 internal items.
9.1.2	Issue	Protocols: DNP3 Protocol	Corrects the Gain/Offset scaling in the DNP3 FBx protocol. *Effect On Published Output: When set in the Archive Field Configuration, the published raw values will be scaled according to the Gain/Offset Scaling formula ItemName{SG:Gain:Offset}.	X
9.1.2	Issue	Protocols: GE SRTP Protocol	Extends the write message to include more than one item write in the same protocol message.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Modifies the protocol to perform a primary path test before switching from the secondary connection to the primary connection.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that prevented the Mercury Call-in Schedule from saving the Start, Length, and Interval values.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that caused an incorrect leading/trailing timestamp indicator to be published for Mini-AT, Mini-Max, AccuTest and TurboCorrector devices. *Effect On Published Output: The correct leading/trailing timestamp indicator will be published.	X
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Decodes G items (1600-1699) for the Mercury EC350 series. *Effect On Published Output: The correct value for G items will be published.	X
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Modifies the 'First Collection Limit' so that the most recent alarm and event Archive records are published instead of the oldest.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that caused all alarms in the alarm buffer of a Mini-AT to be published on every history upload. *Effect On Published Output: Only the expected alarms will be published when using the RL command to upload alarms.	X
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that could cause multiple items to be associated with an RD message when the server was starting.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that caused a Call-in message to be ignored if a low priority write was currently queued.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that caused items that were reported as invalid by the RTU to be added back to poll messages.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that prevented an item write from being sent to device if the write happened during an active poll session.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Prevents the driver from collecting records that are out of the request range.
9.1.2	Issue	Protocols: Modbus Protocol	Adds missing Modbus Protocol token values for meter configuration records. *Effect On Published Output: The published output will no longer be missing token values.	X
9.1.2	Issue	Protocols: ROC Protocol	Removes the "Combine data from all segments into the same archive record" option from non-800 RTUs as it is not applicable. Previously, if used erroneously, it could result in a crash.
9.1.2	Issue	Protocols: ROC Protocol	Corrects an issue that caused the driver to retrieve all batch records instead of the Batch Archive Limit value.
9.1.2	Issue	Protocols: ROC Protocol	Corrects an issue where the tag modifier <TJULIAN> was not functional for 4 byte Julian dates.
9.1.2	Issue	Protocols: Totalflow Protocol	Corrects an issue that prevented Totalflow extended items such as Move Daily and Move event from reverting back to their default value in UA Clients.
9.1.2	Issue	Protocols: Totalflow Protocol	Includes the orifice plate reference temperature value in the meter configuration records for orifice meters using the AGA3-2013 calculation method. Previously it output 'empty/null'. *Effect On Published Output: The orifice plate reference temperature will be published for orifice meters using the AGA3-2013 calculation method.	X
9.1.2	Issue	Protocols: Totalflow Protocol	Includes additional diagnostic logging when the "Enable message tracing for more logging information" option is selected.
9.1.2	Issue	Protocols: Totalflow Protocol	Corrects an error that could use the wrong 'remote meter index' when sending GC data to device.
9.1.2	Issue	Publishing	In the CFX publishers, if the meter contents change from liquid to gas or vice versa, the CFX file will be renamed to include the current timestamp and a new file will be generated. Previously the publisher would fail. *Effect On Published Output: While the data within the CFX file will not change, the file name may change if a meter's content changes from Liquid to Gas or vice versa.	X
9.1.2	Issue	Publishing	Corrects an issue that allowed duplicate periodic records to be published to CFX7 and CFX8 files. *Effect On Published Output: Duplicate periodic records will no longer be published to CFX.	X
9.1.2	Issue	Server Monitor	Modifies the database form in ACM Monitor so that the "Create/Update Database" button cannot be clicked until a provider is selected.
9.1.2	Issue	Server Monitor	Corrects an issue that caused the wrong "History Deletion Frequency" option to be displayed during create/update database operations via ACM Monitor.
9.1.2	Issue	Server Monitor	Updates the support package creator to provide more information regarding what can be included and provide more options to configure the contents.
9.1.2	Issue	Server Monitor	Corrects an issue that caused the Database Statistics form to return the error message: "Keyword not supported: 'provider' not allowed.".
9.1.2	Issue	Bulk Manager	Changes the Bulk Manager so that a file that failed to import due to the process being selected as the "DEADLOCK victim" will stay in the import folder.
9.1.2	Issue	Bulk Manager	Improves the log messages to contain more details if a SQL failure occurs.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that could prevent the driver from sending the log on sequence to the RTU if the last poll cycle ended in comm failure.
9.1.2	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that could cause a received status packet to be ignored if other protocol packets preceded it in the comm buffer, resulting in timeouts.
9.1.2	Issue	OPC UA	Corrects an issue that could prevent items in a new Alias Group from being updated if that contained invalid item names.
9.1.2	Issue	OPC UA	Sets the status of a node that represents an ACM item to 'UncertainLastUsableValue' when all monitored items are removed from the node.
9.1.1	Issue	Bulk Manager	Corrects an issue after upgrading to 9.1.0 that prevented asiBulkMgr from starting until the database connection had been modified in ACM Monitor.
9.1.1	Issue	Client Application	Prevents ACM Configuration from freezing when loading all properties for DNP3 FBx and BSAP devices. This could occur when selecting the "View All Properties" menu option in the "Type View" of the navigation tree.
9.1.1	Issue	Client Application	Prevents the Dashboard grid from flickering when sorting a large number of records.
9.1.1	Issue	Client Application	Removes the option to select an alias group object in the "Status" panel of port objects.
9.1.1	Issue	Client Application	Masks the password in the "Provider String" fields on the Database and AUTOSOL EFM Database objects "Database" tabs.
9.1.1	Issue	Client Application	Masks the "Password" field in the "Security" section of the Totalflow "Device" tab.
9.1.1	Issue	Client Application	Improves the loading performance of the Dashboard.
9.1.1	Issue	Client Application	Corrects the multi-line copy and paste capability for the "Comments" column when using multi-object edit tool. Now text with hard returns will be pasted into a single cell, and the entire cell contents, even if they include a hard return, will be copied.
9.1.1	Issue	Configuration Database	Deprecated Alias Group properties will be added to the database cleanup script.
9.1.1	Issue	Connections: TCPIP Connection	During a primary path test, ACM will no longer attempt to connect to the primary port if it was closed with a 'Close Port' command.
9.1.1	Issue	GC Write Service	Adds more details for file parsing errors to aid in troubleshooting processing issues.
9.1.1	Issue	General	Prevents loss of data when ACM cannot read the configuration from the database during startup.
9.1.1	Issue	General	Corrects the missing log messages for 'Data sent to client' when the client is an OPC UA client.
9.1.1	Issue	Installer	Corrects an issue that caused the 64-bit version of ACM to be installed in C:\Program Files(x86) instead of C:\Program Files.
9.1.1	Issue	Installer	Corrects an issue that may cause the ACM installer to erroneously report that a previous version of ACM is already installed.
9.1.1	Issue	Kinder Morgan Modbus	Corrects an issue related to archive sequence number resets.
9.1.1	Issue	MQTT	Corrects an issue that caused asiData to crash when restarting asiItemServer.
9.1.1	Issue	MQTT	Adds configurable logging detail modes for connections, device and item activity between ACM and MQTT broker publishing to aid in troubleshooting.
9.1.1	Issue	OPC UA	Corrects the data type of the initial value update for archive 'Move' and 'Reset' items in the Totalflow protocol.
9.1.1	Issue	OPC UA	Incorporates OPC Foundation stack version 1.4.371.96 which includes resolutions for security issues CVE-2023-27321 and CVE-2023-31048.	X
9.1.1	Issue	Protocols: Base Protocol	Prevents a possible memory leak that could occur while processing history records. This leak only occurred when using a configurable archive object with fields of 'string' data types marked as 'Not Used' for their attribute value with the following protocols: Enron Modbus, Kinder Morgan Modbus, ETNG Modbus, Prosoft Modbus, Benchmark, and BSAP.
9.1.1	Issue	Protocols: BSAP Protocol	Prevents a memory leak that may occur when using Accol or Signal files for item names.
9.1.1	Issue	Protocols: BSAP Protocol	Corrects an issue that caused the protocol to retrieve all history each time the "Retrieve History" command was executed. *Effect On Published Output: ACM will no longer republish all history records each time history is retrieved.	X
9.1.1	Issue	Protocols: FlowX Protocol	Prevents repeat error log messages for duplicate tag names when configuring a FlowX History Map object.
9.1.1	Issue	Protocols: GE SRTP Protocol	Prevents a memory leak that occurs when the GESRTP Protocol validates received responses.
9.1.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that created duplicate EFM meter configuration fields. *Effect On Published Output: ACM will no longer publish duplicate EFM meter configuration fields.	X
9.1.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects the temperature and pressure high/low alarm setpoint values published to the meter configuration record. *Effect On Published Output: ACM will publish the correct temperature and pressure high/low alarm setpoint values.	X
9.1.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that prevented the driver from converting values correctly when the "Publish volume and related items data and units in MCF" checkbox is checked.
9.1.1	Issue	Protocols: Modbus Protocol	Prevents a memory leak that could occur when retrieving history in the Modbus Enron and Modbus SCADAPack protocols.
9.1.1	Issue	Protocols: Omni Modbus Protocol	Corrects a polling error that occurred when using the "Modicon Compatible" option on the Modbus OMNI 7000 "OMNI" tab.
9.1.1	Issue	Protocols: ROC Protocol	Corrects an issue where the K-Factor override to use Point Type 7 did not function with the new Firmware 2.0+. *Effect On Published Output: ACM will publish the correct K-Factor for devices with the new Firmware 2.0+.	X
9.1.1	Issue	Protocols: SCADAPack Protocol	Corrects the Data Resolution value published to CFX files. *Effect On Published Output: The correct Data Resolution value will be published to CFX files.	X
9.1.1	Issue	Protocols: SCADAPack Protocol	Corrects gas Relative Density and liquid Density output values in history records. *Effect On Published Output: Publishes Relative Density for gas and Density for liquid output in history records.	X
9.1.1	Issue	Protocols: SCADAPack Protocol	Prevents ACM from publishing a partial meter configuration record if the meter configuration data cannot be fully retrieved from the device. *Effect On Published Output: ACM will not publish a partial meter configuration record if that meter configuration data cannot be fully retrieved from the device.	X
9.1.1	Issue	Protocols: SCADAPack Protocol	Adds initial support for new Scadapack 470i and 474i controllers.
9.1.1	Issue	Protocols: Totalflow Protocol	Uses the correct value for the meter serial number when the Archive Collection tab is configured to use the "ACM meter description" as the source for the meter serial number *Effect On Published Output: ACM will publish the correct value for Meter Serial number when using the "ACM Meter Description" as the source.	X
9.1.1	Issue	Protocols: Totalflow Protocol	Turbine meters will now have empty/blank values in the meter configuration record for Pipe Material, Tap Type, and Tap Location. *Effect On Published Output: The output for Turbine meters will now have empty/blank values in the meter configuration record for Pipe Material, Tap Type, and Tap Location.	X
9.1.1	Issue	Protocols: Totalflow Protocol	Corrects the AGA calculation method reported for gas coriolis Totalflow meters. *Effect On Published Output: The correct AGA calculation method will be published for gas coriolis Totalflow meters.	X
9.1.1	Issue	Protocols: Totalflow Protocol	Corrects a memory leak that occurs during history collection if at least one debounce meter and input is assigned.
9.1.1	Issue	Publishing	Prevents a memory leak in the publisher process if a referenced token string cannot be identified.
9.1.1	Issue	Publishing	Corrects a memory leak when using the right-click configuration tree menu option to re-publish history for a device.
9.1.1	Issue	Server Monitor	Adds a new "About" tab to the Server Monitor to simplify reporting information to AUTOSOL Customer support. The "About" tab displays the Server Version, Server Start Time, Windows Version and License Information. It also has buttons to open the Log File directory, the Dump File directory and the event Viewer filtered to ACM events. A fourth button creates a "Support Package" zip file that can be attached to a support ticket. The zip file contents include log files, dump files, events, a few reports and server information.
9.1.1	Issue	Server Monitor	Provides the ability to use an unsecure connection when testing the MQTT and Bridge Broker Connections. Note: This setting is not suggested for use in a production environment.
9.1.1	Issue	General	Prevents a memory leak that could occur when the asiData service is stopped.
9.1.1	Issue	General	Prevents a memory leak that could occur when configuring View objects.
9.1.1	Issue	Server Monitor	Updates the "View Client/Server Info" form in ACM Configuration and the "Server information" form in ACM Monitor to include the third digit in the version. This represents the maintenance release number of the ACM server, e.g. 9.1.1.
9.1.1	Issue	Server Monitor	Adds the license information to the "View Client/Server Info" form in ACM Configuration.
9.1.1	Issue	Siemens S7 Protocol	Corrects an issue with non bit offset writes that was causing the device to return an error.
9.1.1	Issue	Siemens S7 Protocol	Corrects an issue that prevented some error messages from being logged when the Enhanced logging option was not selected.
9.1.0	Issue	Alias Groups/Items	Corrects ACM to use only the $Server alias group if one is assigned. If an alias group is not assigned to the $Server object, ACM will use the device specific alias groups.
9.1.0	Issue	API	Modifies the API to enforce validation of maximum/minimum values.
9.1.0	Issue	API	Corrects an issue connecting to ACM when the API is loaded by an unmanaged process.
9.1.0	Issue	Archive Management	Corrects an issue that could cause the Archive Management grid to display an incorrect Contract Hour for various protocols.
9.1.0	Issue	Bridge	Corrects the "Quality of Service" used by asiBRIDGE when it publishes MQTT messages.
9.1.0	Issue	Client Application	Modifies the "Copy" functionality so that when copying a device, the meter references will not be copied. This prevents multiple devices polling data for the same meters.
9.1.0	Issue	Client Application	Corrects the tool tip message for the Details tab User01 property.
9.1.0	Issue	Client Application	Corrects an issue that caused the Configuration Manager to disconnect from asiData when searching for certain special characters (e.g parantheses).
9.1.0	Issue	Client Application	Corrects an issue in the Scheduled Report form that caused fields using tokens to be reset.
9.1.0	Issue	Client Application	Corrects an issue that prevented the object tree from reloading when selecting multiple objects via the search tool.
9.1.0	Issue	Client Application	Adds the $Server and $Perf objects to the object tree in "Type View" and "Category View".
9.1.0	Issue	Client Application	Adds more descriptive error messaging to the object name field.
9.1.0	Issue	Configuration Database	Corrects casing in sp_InvokeArchiveSnapshot and sp_GetPublisherFilterObjects to prevent errors on SQL Servers with extremely strict case defaults.
9.1.0	Issue	GC Write Service	Corrects the use of the tab delimiter and adds validation for delimiters in the GC Write File Service.
9.1.0	Issue	General	Corrects an issue that caused ACM to wait for an OPC Sync Read request to complete when the target device object had been disabled.
9.1.0	Issue	General	Changes the default DCOM authentication level from 'Connect' to 'Packet Integrity'. An override is available and instructions are found here: https://autosoln.atlassian.net/wiki/spaces/ACMDOCS/pages/2516287489/ACM+and+Windows+DCOM+Hardening.	X
9.1.0	Issue	General	Corrects an issue that could cause an invalid timestamp in an OPC data change update.
9.1.0	Issue	Importer/Exporter	Excludes missing Alias Group references from exported configuration data and ignores missing Alias Group references during configuration import.
9.1.0	Issue	Importer/Exporter	Modifies the import process so it will update all references after an import.
9.1.0	Issue	Installer	Modifies the ACM Crash Dump Configuration so that it will change when the ACM Data Directory is changed.
9.1.0	Issue	OPC Items	Corrects Communication Statistics counter values.
9.1.0	Issue	OPC Items	Corrects an error that cleared the item's last value when quality was "Last Known Value".
9.1.0	Issue	OPC UA	Corrects an issue that rejected items with square brackets around the device object name.
9.1.0	Issue	OPC UA	Corrects an issue that caused multiple address space nodes to be created for the same item if a client did not include the namespace index in the item name.
9.1.0	Issue	OPC UA	Corrects an error that resulted in an "out of bounds" error message when a client reinitialized a monitored item list. Corrects an issue that prevented monitored items from updating for nodes of data type 'signed byte'. Corrects an error that could return a "Service Fault - BadNotSupported" error message when creating a second monitored item for a node with data type 'signed byte'.
9.1.0	Issue	OPC UA	Corrects an issue that prevented monitored items from being created in the Server address namespace.
9.1.0	Issue	Protocols: Base Protocol	Removes a duplicate warning message in log files about Item Data and Item Update that appeared when a demand timed out.
9.1.0	Issue	Protocols: Base Protocol	Adds validation to the device "Connect String" property to disallow non-numeric characters in the IP Port number.
9.1.0	Issue	Protocols: Base Protocol	Corrects an issue that prevented the Archive Limits "Limit First Collection" settings from being applied when assigning an Archive Limit object after having collected history and reset the pointer.
9.1.0	Issue	Protocols: Benchmark Protocol	Corrects an issue that incorrectly processed a sub-command 11 when a field item data index was present in the item.
9.1.0	Issue	Protocols: DNP3 Protocol	Adds support for Vinson Transactional Logs.
9.1.0	Issue	Protocols: DNP3 Protocol	Corrects an issue that prevented the "Use meter config from device" option from being used during publishing. *Effect On Published Output: The correct meter configuration will be published based on the "Use meter config from device" checkbox.	X
9.1.0	Issue	Protocols: DNP3 Protocol	Corrects an issue that could prevent meter configuration file items from being read after re-checking the "Use meter config from device" option. This could occur when going from using the meter config from the device, to using the advanced meter config, and back again while the meter configuration file from the first setting was still valid.
9.1.0	Issue	Protocols: DNP3 Protocol	ACM will process records that exist in a history record file, even when the sequence number and record count are not the same as those used to open the file. The sequence and record count mismatch can occur when the device detects and removes corrupted records from the file. Corrects an issue with using the value of a DNP3 binary item as an enumeration for meter configuration record values. *Effect On Published Output: Corrects publishing incorrect information to meter configuration records, and not retrieving available history records.	X
9.1.0	Issue	Protocols: FlowX Protocol	Corrects the history map validation to treat records with the same EFMID, MeterID and Period as duplicates.
9.1.0	Issue	Protocols: GE SRTP Protocol	Prevents a memory leak in GE SRTP protocol.
9.1.0	Issue	Protocols: GE SRTP Protocol	Modifies the GE SRTP driver so a "No meter assigned for device" message will not appear when polling a device for which you are not collecting history.
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that prevented audit trail items set to register address 255 from being published when the field was configured in a configurable archive as a 'Value' field. *Effect On Published Output: Audit trail items set to address 255 will now be published if configured as a 'Value' field in the configurable archive object record set.	X
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Adds the alarm description in the alarm record output for non EC350 devices. *Effect On Published Output: alarm descriptions will be published for non-EFM alarms.	X
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Modifies the driver so the demand item will be updated during a cry out after triggering a continuous scan.
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Correctly assign units for items 910 and 911 in Audit Trail record when used as meter1. *Effect On Published Output: The correct unit will be published for 910 and 911 if the Audit Trail record is used as meter 1.	X
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that could prevent a meter's configuration from being uploaded if the sign-on sequence failed during a history upload and a retry is attempted by ACM.
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that could cause the polling sequence to an RTU to get out of sync with the RTU resulting in an Invalid Command Error response during sign-on sequence.
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Prevents a possible invalid value from appearing in the PGASOutputOptions property.
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Removes the "Change Access" capability for Honeywell Mercury EC350 & ERX350 as it is unsupported by these devices.
9.1.0	Issue	Protocols: Micro MP3 Protocol	Corrects an issue that prevented the "Contract Hour" from being polled correctly which resulted in the value always being 0 on the Archive Management tab. *Effect On Published Output: Contract hour is now polled correctly and published for Micro MP3 devices.	X
9.1.0	Issue	Protocols: Modbus Protocol	Corrects an error that occurred when writing to array item using common Modbus item modifier 'IS'.
9.1.0	Issue	Protocols: Omni Modbus Protocol	Prevents a Viscosity event in Omni 7000 devices from returning an abnormal code.
9.1.0	Issue	Protocols: Omni Modbus Protocol	Adds the Calculation Method for the Omni 7000 liquid meter to the published output. *Effect On Published Output: The Calculation Method will now be published for Omni 7000 liquid meters.	X
9.1.0	Issue	Protocols: Omni Modbus Protocol	Corrects an issue that could cause an exception while processing an Omni 3000/7000 alarm record.
9.1.0	Issue	Protocols: Possibly multiple protocols	Adds all Batch Record field identifiers and Liquid Product field identifiers to the selection list in the Archive Field Configuration Record Collection form.
9.1.0	Issue	Protocols: ROC Protocol	Adds DATABASE.TOTAL_YD back to the OPC browsing list.
9.1.0	Issue	Protocols: ROC Protocol	Corrects an issue that caused the GCWrite to write to incorrect TLPs if the GCWrite was executed before ROC meter configuration was read.
9.1.0	Issue	Protocols: ROC Protocol	Corrects an issue that occasionally prevented the driver from determining the appropriate series when the "Do not switch ROC automatically series" was unchecked.
9.1.0	Issue	Protocols: ROC Protocol	Corrects an issue that left an invalid item in the poll message after an "Invalid TLP" error code.
9.1.0	Issue	Protocols: ROC Protocol	Corrects an issue where ROC FB103's were being polled as 503's resulting in missing values and no extended records. *Effect On Published Output: Corrects an issue where ROC FB103's were being polled as 503's resulting in missing values and no extended records.	X
9.1.0	Issue	Protocols: ROC Protocol	Adds a field to the "Device" tab labeled "Schedule Reinitialization" to schedule the Reinitialize command.
9.1.0	Issue	Protocols: ROC Protocol	Updates the Internal Archive Map Details pop-up to list EFM Fields according to meter type. The button to view this list is found on the "Archive Collection" tab.
9.1.0	Issue	Protocols: SCADAPack Protocol	Corrects an issue that prevented the Scadapack driver from updating the status of a GC Write request if the request failed due to a Comm error.
9.1.0	Issue	Protocols: SCADAPack Protocol	Prevents a partial meter record from being published if it is missing a Contract Hour. *Effect On Published Output: Partial meter config records that are missing the Contract Hour will not be published.	X
9.1.0	Issue	Protocols: Siemens Protocol	Corrects an issue with Byte Bit offsets that caused returned and written values to be off by one index.
9.1.0	Issue	Protocols: Totalflow Protocol	Corrects an issue where a time sync and history request will fail due to having the same priority schedule.
9.1.0	Issue	Protocols: Totalflow Protocol	Modifies the driver to use the configuration value read from the device for the "Has Default Temperature" field instead of a fixed value. *Effect On Published Output: The meter configuration field "Has Default Value" will display the meter's configured value.	X
9.1.0	Issue	Protocols: Totalflow Protocol	Corrects the driver so it will not collect duplicate alarm Records during log period collection. *Effect On Published Output: Duplicate alarm records will not be published.	X
9.1.0	Issue	Protocols: Totalflow Protocol	Adds 'Double' data type support for Totaflow register read and write.
9.1.0	Issue	Protocols: Weatherford Protocol	Corrects an issue that could cause ACM to stop running if the driver received an unexpected response packet to an FC16EX card buffer upload request.
9.1.0	Issue	Protocols: Weatherford Protocol	Corrects an issue that could cause the event directory upload to never cease running if the event buffer on the controller was completely full.
9.1.0	Issue	Publishing	Increases the size of the variables in asi_spgetPublisherFilteredObjects to varchar(max) to process large filters. Note: After this fix, there is still a SQL Server limitation to varchar(max). If this error is still seen after DB Version 42, the filter will need to be modified.
9.1.0	Issue	Publishing	Adds logging to the Database output type to show if a transaction was committed or rolled back to show the transaction completed.
9.1.0	Issue	Publishing	Adds the field name and unit of measure to the message that is logged when the publisher cannot validate an event.
9.1.0	Issue	Publishing	Corrects the error that resulted in an "Implicit conversion from data type datetime to real is not allowed." message when publishing a sample date to the FLOWCAL Transaction Queue. *Effect On Published Output: The sample date value from a DNP3 FBx device can now be published.	X
9.1.0	Issue	Publishing	Corrects the conversion for the Meter Access Date, Cold Start Date, Warm Start Date and Sample Date which are datetime fields but stored as a 'real' value in FLOWCAL. *Effect On Published Output: The Meter Access Date, Cold Start Date, Warm Start Date and Sample Date fields may now have data where previously they were incorrect null or 0.	X
9.1.0	Issue	Publishing	Prevents a string value from being published as the Contract Hour if an alphabetic character is entered for Contract Hour in the Advanced Meter Config. *Effect On Published Output: The FLOWCAL Transaction Queue will publish a number entered in the Contract Hour of the Advanced Meter Config, and will publish nothing if an alphabetic character is entered.	X
9.1.0	Issue	Publishing	Adds a fixed/live temperature indicator as TEMP_SOURCE and a fixed/live pressure indicator as SP_SOURCE to the meter characteristics for the PGAS XML publisher. *Effect On Published Output: The PGAS XML output will include fixed/live temperature and fixed/live pressure flags in the meter characteristics element if the protocol driver provides them.	X
9.1.0	Issue	Publishing	Includes the values of the User01, User02, and User03 fields from the Details tab, as well as the External GC Reference and External Meter Reference values in the published output. *Effect On Published Output: The User01, User02, User03, External GC Reference and External Meter Reference properties will now have values in the published output.	X
9.1.0	Issue	Reports	Prevents extraneous logs from being written when saving edits to scheduled reports.
9.1.0	Issue	Reports	The script to update the database to version 42 will rebuild the Referenced Objects list which is used by the Orphaned Objects report. A manual update script is also available if this needs to occur in a database earlier than version 42.
9.1.0	Issue	Reports	Adds support for all of the following report formats to both manually run reports and scheduled reports: CSV, HTML, PDF, XLS, XLSX, & TEXT.
9.1.0	Issue	Reports	Corrects the Scheduled Report form for the Missing Daily Archive Records to show the saved start and end date parameters when editing the form.
9.1.0	Issue	Server Monitor	Modifies the History Deletion value displayed in the Task Summary field when creating a new ACM database to show HH:MM.
9.1.0	Issue	Server Monitor	Corrects the Write Timeout property of "Gas Analysis Writes Retry" to accept values in the range of 30 to 600 seconds.
9.1.0	Issue	Server Monitor	Modifies the password requirements for the database user in ACM Monitor to prevent semi-colons.
9.1.0	Feature	Client Application	Adds a new "right-click" menu option labeled "Navigate To Object" to an object tab that will locate the opened object in the configuration tree.
9.1.0	Feature	Client Application	Adds a row number to the Dashboard grid.
9.1.0	Feature	Connections: UDP BSAP Connection	Modifies ACM to ignore the UDP error code 'WSAECONNRESET' in UDP BSAP.
9.1.0	Feature	DNP3 Protocol	Adds the fields KFactor13 - KFactor20 and Frequency13 - Frequency20 to the publisher and the Meter Configuration object. *Effect On Published Output: These fields will be added to the published meter configuration record if FBx meter config files are used and contain these fields.	X
9.1.0	Feature	DNP3 Protocol	Adds the field VersionNumber to the Meter Configuration object. *Effect On Published Output: These fields will be added to the published meter configuration record if FBx meter config files are used and contain these fields.	X
9.1.0	Feature	DNP3 Protocol	Publishes the fields KFactor1 - KFactor20 and Frequency1 - Frequency20 from the meter config file read from the DNP3 FBx device. *Effect On Published Output: These fields will be added to the published meter configuration record if FBx meter config files are used and contain these fields.	X
9.1.0	Feature	General	Adds a new Sync Read Timeout property to the $Server object Server tab to establish the lengh of time (in milliseconds) the server should wait for a Sync Read to time out.
9.1.0	Feature	Mobile Portal	AUTOSOL has released the Mobile Portal.
9.1.0	Feature	OPC UA	Adds a new element to the configuration file named "TraceMasks" to control the message logging output from the OPC UA Stack. More information regarding the use of the new element can be found in Appendix B of the OPC UA User Guide: https://autosoln.atlassian.net/wiki/spaces/ACMDOCS/pages/1596359214/Appendix+B+Configuration+File
9.1.0	Feature	OPC UA	Adds support for writing to array type items in ACM.
9.1.0	Feature	OPC UA	Adds configurable server properties MaxNodesPerWrite and MaxMonitoredItemsPerCall.
9.1.0	Feature	OPC UA	Integrates the OPC UA .NET Standard Stack Version 1.4.370.12 from OPC Foundation which fixes the following cybersecurity vulnerability: CVE-2022-33916.	X
9.1.0	Feature	Protocols: ControlLogix Protocol	Updates the driver so it can communicate with a device running ControlLogix firmware Rev34.
9.1.0	Feature	Protocols: DNP3 Protocol	Adds a modifier &SECONDS to the DNP3 FBx protocol to return seconds elapsed since January 1st, 2000 at 12:00:00 AM.
9.1.0	Feature	Protocols: DNP3 Protocol	Adds a new EFM Option, "Publish all meter config fields" to the Archive Collection tab. When selected, ACM will publish all fields whether or not they have values. *Effect On Published Output: If this option is checked, all meter config fields will be published. When unchecked, only meter config fields with data will be published.	X
9.1.0	Feature	Protocols: E-Lite Modbus Protocol	Adds support for the Dynamic Flow Computer's E-Lite Protocol. This includes the ability to perform a TimeSync command, read and write to registers, and retrieve history, alarm, events and meter configuration information.
9.1.0	Feature	Protocols: Honeywell - Mercury Protocol	Adds the ability to include "zero value" bytes to the device wake-up message. The new field is labeled "Message Nulls" and is found on the Device tab and can be used to stabilize the connection before the 04 byte is sent.
9.1.0	Feature	Protocols: Honeywell - Mercury Protocol	Adds a new feature to allow a time sync to be performed on RTU call-in.
9.1.0	Feature	Protocols: Kimray Protocol	Adds additional items for the AutoTune/AutoRecovery command for read and write.
9.1.0	Feature	Protocols: ROC Protocol	Adds more details to the logging information when the "Log EFM Upload Progress" option on the "Device" tab is checked.
9.1.0	Feature	Protocols: ROC Protocol	Adds support for Emerson's new enhanced security released in the following firmware versions: FB107 version 2.0, ROC 800L version 1.70, ROC 800 version 3.90.
9.1.0	Feature	Protocols: ROC Protocol	Adds the Software Version to the meter configuration collection. *Effect On Published Output: The Software Version will now be populated in CFX output.	X
9.1.0	Feature	Protocols: ROC Protocol	Adds a new option to the "Device" tab labeled "Device is an FB107 with firmware version 2.0 or higher" that must be checked to collect history on FB107 devices with Firmware 2.0+.
9.1.0	Feature	Protocols: ROC Protocol	Adds an option to the "Device" tab labeled "Collect history on a ROC with no configured meters (non-RocPlus)" to collect history from devices with no meters assigned. This feature is not intended for use with the ROC800 series. *Effect On Published Output: When the new option is selected, history will be published for devices with no meters configured.	X
9.1.0	Feature	Protocols: ROC Protocol	Adds support for Vinson Haul Logs, Vinson Cyclic Logs and Vinson Gas Lift Logs in 107, 80X and 800L series ROC devices.
9.1.0	Feature	Protocols: ROC Protocol	Adds an option "Store events only with associated meters" to only publish calibration events with their associated meters. *Effect On Published Output: If the option is turned on, calibration events in ROC800 will only be published to the associated meters.	X
9.1.0	Feature	Protocols: ROC Protocol	Adds the ability to configure, by meter, which TLPs are written to on GC Write activities.
9.1.0	Feature	Protocols: SCADAPack Protocol	Adds an option to the "Archive Collection" tab labeled "Publish Density to Observed Density with Liquid Meters". *Effect On Published Output: If the new option is checked, the Density value will be published to Observed Density for Liquid Meters.	X
9.1.0	Feature	Protocols: SCADAPack Protocol	Upgrades the SCADAPack driver to support 20 meters.
9.1.0	Feature	Protocols: Totalflow Protocol	Adds "Attached to Stream", "Stream Id" and "Fixed Analysis on Error" as Meter Characteristics that can be published. The fields for these characteristics can be set on the Archive Collection tab. *Effect On Published Output: If configured, "Attached to Stream", "Stream Id" and "Fixed Analysis on Error" will be included in the published output.	X
9.1.0	Feature	Protocols: Weatherford Protocol	Updates the driver so that an OPC Sync Read of a card buffer array item will cause an immediate upload of that card buffer.
9.1.0	Feature	Reports	Adds the ability to send scheduled reports to multiple individual emails without the need for a group email account. Email addresses must be separated by a comma.
9.1.0	Feature	Security	Adds the ability to configure, in seconds, the inactivity timeout period. The new option, "Inactivity Timeout" is on the "Security Tab" and only applies when "Enable ROC Login" is checked.
9.1.0	Feature	Server Monitor	Adds a new column in ACM Monitor Status view showing the Startup Type (i.e. Manual, Automatic or Disabled) for each process.
9.1.0	Feature	Server Monitor	Provides the ability to change the Startup Type for all ACM processes within the ACM Monitor Status View tab.
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Corrects the alarmType register value for all available Mercury registers to display all digits. *Effect On Published Output: Field5 will no longer be included in the published output.	X
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Removes the extraneous 'Field5' field from the alarm Record. *Effect On Published Output: Field5 will no longer be included in the published output.	X
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	A Time Sync operation will now cause the Call-in Schedule to be set on the RTU when the protocol option "Set call-in schedule after regular polls" is enabled.
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that caused the RTU call-in to not be acknowledged when no device protocol call-in options were enabled.
9.1.0	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that could cause the next Call-in Schedule to not be set on the RTU when certain combinations of device protocol call-in options were enabled.
9.1.0	Issue	OPC UA	Adds an option that allows the OPC UA server to connect to and disconnect from asiData when a client app connects and disconnects. This option is on the Properties tab of the OPC UA Configuration in ACM Monitor and is labeled "Only Connect To asiData When There Are Active Client Sessions".
9.1.0	Issue	OPC UA	Adds functionality to allow the OPC UA server to start asiData when a client app connects.
9.1.0	Issue	Reports	Corrects an issue in the Scheduled Reports that caused the $$CurrentDay$$ or $$CurrentHour$$ tokens to be incorrectly calculated in Throughput reports.
9.1.0	Issue	Reports	Corrects an issue in the Scheduled Reports form that prevented the Save button from being enabled after editing the connection.
9.1.0	Issue	Reports	Modifies the "Configuration Changes for a Device" report to filter to only Device type objects.
9.1.0	Issue	Reports	Adds a new report titled "Configuration Changes for an Object" to search for configuration changes for any object type.
9.1.0	Issue	Server Monitor	Adds the newest Microsoft OLE DB Driver 19 to the available database providers in ACM Monitor. This provides additional encryption options for the connection. More information can be found in the User Guide.
9.1.0	Issue	Server Monitor	Adds a button to view the connection string.
9.0.1	Issue	ACM Server	Corrects an issue that prevented encrypted channel communication between an ACM client and server when the client and server components are on different computers.
9.0.1	Issue	ACM Server	Corrects small memory leaks in Flow Automation, Honeywell Mercury, and Totalflow protocols.
9.0.1	Issue	Archive Management	The "Device Id" column in Archive Management now shows the device's object id.
9.0.1	Issue	Bulk Manager	No longer moves Import files to the Import Failed folder after a SQL Timeout. Instead they will remain in the Import folder.
9.0.1	Issue	Client Application	Removes the "Retrieve History", "Delete History for Device" and "Republish Device Records" commands from the right-click menu of Real-Time Only devices.
9.0.1	Issue	Client Application	Corrects an issue on the "OMNI" tab of an OMNI 7000 device that prevented a user from properly typing a value into the "Password" and "Register Block Read Path" text boxes.
9.0.1	Issue	Client Application	Corrects an issue that caused the Logger and Queue tabs to go blank when a large number of object tabs were open in multiple ACM Clients.
9.0.1	Issue	Client Application	Corrects an issue when creating a new Port Object that prevented the Port Type from being changed after canceling out of the folder location screen.
9.0.1	Issue	Client Application	Prevents the Edit Multiple Objects grid from re-sorting the data while a user is typing a value into a cell.
9.0.1	Issue	Configuration Database	Corrects an issue in SQLUpdate_39.sql that prevented the ACM database from upgrading to DBVersion 39 and above on a SQL Server with the default collation set to "SQL_Latin1_General_CP850_BIN".
9.0.1	Issue	Configuration Database	Increases the size of the LastUpdateUser column in tblProperties and tblObjects, and the size of CfgUser in tblChanges, to nvarchar(100). Note: If the tables are being replicated, this will not run automatically and instead can be run via the Manual Script feature in ACM Monitor.
9.0.1	Issue	General	Corrects a memory leak that occurs when logging "data sent to client" on items in the OPC UA interface.
9.0.1	Issue	OPC UA	Integrates the OPC UA .NET Standard Stack Version 1.4.369.30 from OPC Foundation which fixes the following cybersecurity vulnerabilities: CVE-2022-29862, CVE-2022-29863, CVE-2022-29864, CVE-2022-29865, and CVE-2022-29866.	X
9.0.1	Issue	Protocols: Base Protocol	Corrects an issue that prevented the PctGoodTries and PctBadTries statistic items from being correctly updated when a connection was dropped before a message could be sent.
9.0.1	Issue	Protocols: Base Protocol	Prevents queuing an additional Demand after Demand is poked to trigger a continuous scan during cry out.
9.0.1	Issue	Protocols: BSAP Protocol	Corrects an issue that caused the driver to ignore the previous position and retrieve all history when the "Disable duplicate record deletion" option was selected.
9.0.1	Issue	Protocols: BSAP Protocol	Prevents a crash from occurring when the Field Configuration has not been assigned and the device cannot be reached.
9.0.1	Issue	Protocols: DNP3 Protocol	Corrects an issue so that alias items are added correctly via browsing in an OPC client.
9.0.1	Issue	Protocols: DNP3 Protocol	Corrects an issue that caused incorrect meter configuration values for VersionNumber, CalculationMethod and HeatingValueUnits to be published when using meter config file read from FBx device. *Effect On Published Output: The values for VersionNumber, CalculationMethod and HeatingValueUnits will be published correctly.	X
9.0.1	Issue	Protocols: DNP3 Protocol	Changes the dropdown list that selects the meter run into a numeric updown control in the Meter Runs tab.
9.0.1	Issue	Protocols: Flow Automation Protocol	Corrects an issue that caused YesterdayFlowTime and YesterdayFlowEnergy to be incorrectly retrieved when the "Retrieve yesterday flow time or energy using history message" option was checked.
9.0.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects a potential memory leak.
9.0.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that prevented the Unit types for Pressure and Temperature audit record fields from being published for an ER type device. *Effect On Published Output: For ER type devices, the Units for Temperature and Pressure fields will now be published.	X
9.0.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that could cause EFM audit records to be skipped if comm failure occurred during upload.
9.0.1	Issue	Protocols: Modbus Protocol	Corrects the default data type for BlockStart-BlockEnd values to unsigned and adds an "S" item conversion to allow values to be output as signed.
9.0.1	Issue	Protocols: Omni Modbus Protocol	Corrects an issue that prevented subsequent archives from being requested after processing the GC archive for Archive 1.
9.0.1	Issue	Protocols: Omni Modbus Protocol	Prevents a crash from occurring when polling raw data upload.
9.0.1	Issue	Protocols: ROC Protocol	Displays the correct log message type in the logger when the "Items in message" log option is enabled.
9.0.1	Issue	Protocols: ROC Protocol	No longer updates the item quality when the "test" of the primary connection fails when using the Auto Recover feature.
9.0.1	Issue	Protocols: ROC Protocol	Corrects an issue in detecting the ROC model type that prevented ROC history collection settings from updating properly.
9.0.1	Issue	Protocols: Totalflow Protocol	Corrects an issue that prevented LastHourlyRecord/1 from being initialized correctly with the latest hourly record time stamp.
9.0.1	Issue	Protocols: Totalflow Protocol	Corrects an issue that occurred when the field device handles a request for a history record at the "maximum position" by returning more than one record.
9.0.1	Issue	Protocols: Totalflow Protocol	Prevents a poll on the primary connection from switching to the secondary connection when an item with the secondary connection specifier failed to poll.
9.0.1	Issue	Protocols: Totalflow Protocol	Corrects an issue that prevented the daily record from being collected when using the "number of days" method in the DB2 protocol.
9.0.1	Issue	Protocols: Weatherford Protocol	Corrects an issue that prevented card data from publishing to a database when the number of data points in the card set exceeded the maximum column count of the table. *Effect On Published Output: When publishing card data using Function Code 25, the position/load data pair field names now starts with "Position0" and "Load0" for each individual stroke record in the card set as opposed to the field name index continuing to increment across the entire card set.	X
9.0.1	Issue	Publishing	Prevents the asiPublish process from hanging when asiData is being shut down.
9.0.1	Issue	Publishing	Corrects an issue that prevented FPV Method change events from publishing to the FLOWCAL Transaction Queue. *Effect On Published Output: Events for changing the FPV Method value will now publish correctly to the FLOWCAL Transaction Queue.	X
9.0.1	Issue	Publishing	Corrects a PGAS XML publishing issue that created an unnecessary transaction with an empty 'METER' element.
9.0.1	Issue	Publishing	Corrects an issue that stopped publishing to the FLOWCAL Transaction Queue when a record had an invalid future timestamp.
9.0.1	Issue	Reports	Logs the query of a scheduled report when the "Report Logging" option is enabled.
9.0.1	Issue	Reports	Corrects an issue that prevented users from requesting unlimited records when running reports.
9.0.1	Issue	Server Monitor	Corrects an issue in the ACM Database Safe Mode backup that caused the backup to fail if there are orphaned properties or items for a device that does not exist.
9.0.1	Issue	Server Monitor	Prevents an exception in the Server Monitor that could occur when retrieving ACM license request information when FIPS is enabled in the Group Policy.
9.0.1	Issue	Tools	Corrects an issue that could cause one OPC item to replace a previous OPC item in the ACM memory. This only affects the 64-bit version of ACM.
9.0.1	Issue	Base Protocol	Correctly updates PctBadTries and PctGoodTries if the connection fails before the message can be sent.
9.0.1	Issue	Base Protocol	Correctly updates the port PollAttempts counter when an external interruption occurrs.
9.0.1	Issue	DNP3 Protocol	Adds support for new objects, parameters, measurements, units and error codes in Emerson FBx firmware release version 2.9.
9.0.1	Issue	DNP3 Protocol	Handles alarm event records that occur when the device is configured for BSAP Combined event Log.
9.0.1	Issue	DNP3 Protocol	Uses meter config file from device to publish string events as well as FLOWCAL events to non-Generic meters.
9.0.1	Issue	DNP3 Protocol	In cases where this can be detected before polling, does not try to retrieve records from empty or unconfigured archives.
9.0.0	Issue	ACM Server	Adds information to GC Request logging to indicate where a failure occurred. GC Status updates that do not change rows will return a DB Error status.
9.0.0	Issue	ACM Server	Resolves issues related to OPC client browsing when clients use absolute browse paths instead of relative browsing.
9.0.0	Issue	API	Corrects an issue in the API which reported that "Server" objects are creatable.
9.0.0	Issue	Client Application	The Add/Select object window will now retain its size when closed and reopened.
9.0.0	Issue	Client Application	Corrects various forms throughout ACM where fields and buttons were enabled when they shouldn't have been.
9.0.0	Issue	Client Application	Corrects an issue that occasionally caused an incorrect command name to be logged in the database.
9.0.0	Issue	Client Application	Corrects the message regarding the maximum number of archive records that can be published from 1000 to 5000 to match the actual functionality.
9.0.0	Issue	Client Application	Corrects the tab order on the "Database" tab of the configuration form of the $Server object.
9.0.0	Issue	Client Application	Prevents ACM Configuration from attempting to use an http port when connecting to ACM if one has not been configured.
9.0.0	Issue	Client Application	Displays a new error message when an object name contains a carriage return in the name.
9.0.0	Issue	Client Application	Prevents invalid data from being saved by disabling the Save button when text is deleted from a required field and when invalid data is entered.
9.0.0	Issue	Client Application	Corrects an issue which caused ACM to crash after renaming a device, then renaming its meter to the same name, but saving changes to the meter before saving the device.
9.0.0	Issue	Configuration Database	Adds a setting in ACM Monitor called "Keep Meter History". By default this is set to true and ACM will continue to keep meter record history as in previous versions of ACM. If this is unselected, ACM will no longer move meter records into history, and and ACM will only have current meter records.
9.0.0	Issue	Configuration Server	Changes the default value for deleting old history to "Disabled".
9.0.0	Issue	Logging	Corrects an issue that caused messages to be split into multiple lines in the log file.
9.0.0	Issue	MQTT	Corrects an issue with Detail Items not showing up correctly in an OPC browse.
9.0.0	Issue	OPC Items	Corrects an issue that prevented Detail Items from displaying correctly in an OPC browse.
9.0.0	Issue	Protocols: Base Protocol	Changes the Quality of Extended Items to "Bad" when a device is disabled and "Good" when the device is enabled. This change affects the ROC, Totalflow, Honeywell Mercury, ControlLogix and Modbus Devices.
9.0.0	Issue	Protocols: Base Protocol	Corrects an issue that could prevent a device from returning to its regular polling schedule if its alternative schedule was disabled while the device was actively polling on that alternative schedule.
9.0.0	Issue	Protocols: Benchmark Protocol	Corrects an issue related to writing to multiple items at once that could cause asiData to crash.
9.0.0	Issue	Protocols: BSAP Protocol	Corrects an issue that prevented the item value from saving for upload pointer and time sync item reads.
9.0.0	Issue	Protocols: ControlLogix Protocol	Corrects an issue in the "Processor Slot Number" field on the device tab that allowed out of range values to be entered. The valid range is 0 to 255.
9.0.0	Issue	Protocols: DNP3 Protocol	Corrects problems with poll cycle interrupts and DNP3 message sequences that shouldn't be interrupted.
9.0.0	Issue	Protocols: Flow Automation Protocol	Corrects an issue that caused duplicate factor events to be published to the FLOWCAL Transaction Queue, which caused the publisher to fail.
9.0.0	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that caused gaps to occur in history records after an ACK message timed out. Now, instead of skipping to the next record, the driver will attempt to recollect the previous record.
9.0.0	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that could cause an access violation error when certain noise bytes are received in a poll response.
9.0.0	Issue	Protocols: Honeywell - Mercury Protocol	Adds a new informational message when time synchronization is completed.
9.0.0	Issue	Protocols: NGCTT Protocol	Corrects an issue that caused history polling to terminate when 10 04 bytes were returned from a device in the middle of polling.
9.0.0	Issue	Protocols: ROC Protocol	Corrects an issue where events would fail to poll and publish. *Effect On Published Output: Yes. Previously omitted event records may now be polled and published.	X
9.0.0	Issue	Protocols: ROC Protocol	ROC Validation of raw TLP OPC tags now takes into account the number and types of meters configured on the device before it attempts to poll them.
9.0.0	Issue	Protocols: ROC Protocol	Corrects incorrect event mapping for history segment changes in the ROC800 devices. *Effect On Published Output: ROC800 events for history segment changes are output correctly via CFX and Transaction Queue publishers.	X
9.0.0	Issue	Protocols: ROC Protocol	Corrects an issue where mapping and combining points from different segments caused partial records when the segment pointers are misaligned. *Effect On Published Output: Complete records will be published when mapping and combining points from different segments, even when the segment pointers are misaligned.	X
9.0.0	Issue	Protocols: Romet-Adem Protocol	Corrects an issue that could cause incorrect meter configuration values when using the RD command to read register values after a timeout occurs.
9.0.0	Issue	Protocols: SCADAPack Protocol	Modifies the driver to use the correct registers for reading and writing heating value and gas density value.
9.0.0	Issue	Protocols: SCADAPack Protocol	Corrects an issue that caused GC Write to fail for gas coriolis meter runs on controllers running RealFlo 6.95 or greater.
9.0.0	Issue	Protocols: SCADAPack Protocol	Corrects an issue that could cause an incorrect pipe material to be published. *Effect On Published Output: The correct value for Pipe Material will be published.	X
9.0.0	Issue	Protocols: Scancom Protocol	Corrects an issue that prevented "Trusted Log In" from being enabled once it had been disabled.
9.0.0	Issue	Protocols: Scancom Protocol	Changes the "Read Only" state on FRDM items to reflect Barton documentation.
9.0.0	Issue	Protocols: Scancom Protocol	Corrects an issue when writing to multiple items at once that caused the message to be too large for the PLC to process. This resulted in no response and communication failure.
9.0.0	Issue	Protocols: Teledyne CA Protocol	Corrects an issue in the driver that could prevent items of higher cards and points from being polled, which resulted in invalid item values.
9.0.0	Issue	Protocols: Totalflow Protocol	Adds the Trend Record Type to the trends tab form view. It previously only existed in the Property Grid view.
9.0.0	Issue	Protocols: Totalflow Protocol	Corrects an issue that caused the "Use FT" and "Use FB" event values to be incorrectly formatted when publishing to CFX or Transaction Queue. *Effect On Published Output: The "Use FT" AND "Use FB" event values will be correctly formatted when publishing to CFX or Transaction Queue.	X
9.0.0	Issue	Protocols: Weatherford Protocol	Corrects an issue that could cause card data reports to publish to the wrong file if more than one device object is configured to use the same meter object.
9.0.0	Issue	Publishing	Corrects the mapping of the SP and DP calibration values so they are output correctly in the PGAS publisher. *Effect On Published Output: The correct values for SP and DP calibration will now be output in the PGAS XML publisher.	X
9.0.0	Issue	Publishing	Corrects an issue that prevented the Contract Hour and Contract Day fields from being output to the FLOWCAL Transaction Queue. *Effect On Published Output: The Contract Hour and Contract Day will be output to FLOWCAL Transaction Queue.	X
9.0.0	Issue	Publishing	Corrects the default order of archive records in CFX outputs when publishing meters only. *Effect On Published Output: The sort order of CFX output when publishing "Meters Only" will always be by "RecordTS".	X
9.0.0	Issue	Reports	Corrects an issue that could cause a scheduled report to run at least once a minute - ignoring the "sync time".
9.0.0	Issue	Reports	Changes the heading of the 'Date' column in the Configuration Change Reports to 'Date (UTC)'.
9.0.0	Issue	Reports	Optimizes the performance of retrieving and displaying report data.
9.0.0	Issue	Server Monitor	Corrects an issue that prevented services from being started via the Server Monitor if the user for the ACM services did not already have the "Log on as a service" right.
9.0.0	Issue	Server Monitor	Provides a manual update script to change the tblItems ID column to a BIGINT if the column was not upgraded due to the table being replicated. This can only be run once the tblItems table is removed from the replicated articles.
9.0.0	Feature	Client Application	Provides the ability to assign multiple alias groups to devices and views.
9.0.0
9.0.0	Feature	Client Application	Adds the ability to assign an Interval to Alias Groups.
9.0.0	Feature	Client Application	Adds the feature to drop down boxes on the Reports tab to automatically filter results while typing.
9.0.0	Feature	Client Application	Adds a new tool that processes SCADA XML files containing Emerson DNP3 object/parameter names and provides the ability to create, update or replace ACM Alias Group items.
9.0.0	Feature	Client Application	Adds the Object ID and Description to the search results form.
9.0.0	Feature	Protocols: BSAP Protocol	Adds ControlWave signal items to RBE polls.
9.0.0	Feature	Protocols: DNP3 Protocol	Implements items to log FBx meter configuration file data. These items are: LogMeterFileDP/{meter number}, LogMeterFileLinear/{meter number}, LogMeterFileLiquid/{meter number} and LogMeterFileList.
9.0.0	Feature	Protocols: DNP3 Protocol	Adds an option "Use history points from device" to the Archive Collection tab's EFM Options to signify to ACM to use the FBx history header to publish history records. *Effect On Published Output: When the "Use history points from device" option is selected, the FBx history header will be used to publish history records.	X
9.0.0	Feature	Protocols: DNP3 Protocol	Adds an option "Use meter config from device" to the Archive Collection tab's EFM Options to signify to ACM to use the FBx meter config file to: Read the meter list and meter config files from the device to determine which items to read and publish as meter configuration records and read event and alarm records. *Effect On Published Output: When the "Use meter config from device" option is checked, published event, alarm and meter configuration records will be determined by the FBx meter config file.	X
9.0.0	Feature	Protocols: Honeywell - Mercury Protocol	Adds OPC item "MoveAudit" that provides the ability to move each Audit pointer to the desired date and time.
9.0.0	Feature	Protocols: Honeywell - Mercury Protocol	Adds OPC item "ChangeACS" in order for the user to change the access code. This is only supported for non-350 series controllers.
9.0.0	Feature	Protocols: Honeywell - Mercury Protocol	Adds support for using configurable archive records.
9.0.0	Feature	Protocols: Micro MP3 Protocol	Adds the ability to poll and publish alternative (non-truck-loading) batch records. *Effect On Published Output: Alternative (non-truck-loading) batch records can now be published.	X
9.0.0	Feature	Protocols: ROC Protocol	Adds the ability to process ROC 800 Liquid meter data in the GC Write service.
9.0.0	Feature	Protocols: ROC Protocol	Adds compressibility (Zs and Zb) to the meter configuration record for Directive 17 Compliance. *Effect On Published Output: The compressibility fields (Zs and Zb) of the meter configuration record will now be published.	X
9.0.0	Feature	Protocols: ROC Protocol	Adds support for publishing data to Flowcal Ultrasonic Diagnostic area. *Effect On Published Output: Only if customers map the new Ultrasonic EFM IDs to historized points. Existing customers will not be affected.	X
9.0.0	Feature	Protocols: ROC Protocol	Adds a new PGAS Output option labeled "Map Volume to INDEX_OFF and 0 to INDEX_ON" for PGAS output. *Effect On Published Output: If the new option is used, volume will be published to INDEX_OFF and INDEX_ON will be set to zero in the PGAS output.	X
9.0.0	Feature	Protocols: ROC Protocol	Adds the ability to collect 'Tap Type' with meter configuration in ROC800 devices. *Effect On Published Output: Publisher outputs will now include 'Tap Type' in the meter configuration.	X
9.0.0	Feature	Protocols: ROC Protocol	Adds the ability to publish Ultrasonic Data to the FLOWCAL Transaction Queue. *Effect On Published Output: Ultrasonic Data can now be published to the FLOWCAL Transaction Queue	X
9.0.0	Feature	Protocols: ROC Protocol	Adds the ability to retrieve HART tags for Process Limits for the meter configuration records of ROC 800 gas and liquid devices. The HART module in ROC FB107 and any older ROC devices (200's, 300's, 500's) is not supported. *Effect On Published Output: If configured in the device, HART tags will be used for Process Limits when publishing meter configuration records.	X
9.0.0	Feature	Protocols: ROC Protocol	Adds an option to the device tab "Use indicated volume for mass in mass meters." to control whether mass or indicated volume is published as mass for liquid mass meters. *Effect On Published Output: When the new option "Use indicated volume for mass in mass meters." is selected, indicated volume will be published as mass for liquid mass meters. If not selected, mass will be published.	X
9.0.0	Feature	Protocols: ROC Protocol	Adds support for V-Cone meters. A new tab for configuring this has been added between the "Meter Runs" and "History Segments" tabs in the ROC configuration. *Effect On Published Output: V-Cone meter data may now be published.	X
9.0.0	Feature	Protocols: Weatherford Protocol	Adds a Weatherford 8500 protocol module to communicate with Weatherford WellPilot RPOC, ePic VSD, ePic RPC, M8800, M8750, M2000, M8650, M8500, and EXS-1000 ESP. Other devices that use the same Weatherford/Baker/eProd 8500 protocol, or use protocol simulators, are also supported.
9.0.0	Feature	Protocols: Weatherford Protocol	Optimizes the performance for OPC synchronous read from device requests.
9.0.0	Feature	Publishing	Adds an option to the PGAS XML output type labeled "Create files per record type" to store meter characteristic records separately from other record types. If enabled, meter characteristics records will be stored in their own file. All other record types (volume, alarm, event and quality) will be stored together. *Effect On Published Output: If the new PGAS XML option "Create files per record type" is selected, meter characteristic records will be stored separately from other record types in PGAS XML published outputs.	X
9.0.0	Feature	Publishing	Field records of an Archive Field Configuration object can now be selectively configured to be skipped when publishing the EFM record. *Effect On Published Output: Protocols that use a configurable archive object can now be configured to selectively skip EFM record fields when publishing.	X
9.0.0	Feature	SCADAPack Protocol	Adds support for SCADAPack x70 series RTUs.
9.0.0	Feature	SCADAPack Protocol	Adds support for RealFlo 7.0.
9.0.0	Feature	SCADAPack Protocol	Adds support for AGA3-2013.
9.0.0	Issue	Configuration Database	Removes the logic from the following deprecated stored procedures: asi_spPubNewRecords, asi_spPubNewMeterRecords, asi_spGetHourlyGapsMain, asi_spGetHourlyGaps, asi_spGetHourly, asi_spGetDailyGapsMain, asi_spGetDailyGaps, asi_spGetDaily, asi_spChildObjects, asi_spDeleteOldArchiveRecords, asi_spDeleteOldArchiveRecords2. The empty stored procedures will remain in the database as replicated stored procedures cannot be "dropped".
9.0.0	Issue	Configuration Database	Modifies the Meter Historization process stored procedure to improve processing speed.
9.0.0	Issue	Configuration Database	Deletes Meter Record History rows (in tblMeterRecordsHistory) for meters that do not exist in the ACM configuration.
8.2.1	Issue	ACM Server	Corrects a property load error that can occur when processes ACM relies upon aren't available.
8.2.1	Issue	Client Application	Corrects the tool tip message for the Details tab User01 property.
8.2.1	Issue	Client Application	Corrects the checkbox list initial focus issue on multiple tabbed pages
8.2.1	Issue	Client Application	The date-time parameters in reports will now correctly display the saved date and time when editing a scheduled report.
8.2.1	Issue	Client Application	Corrects an issue that prevented using the "Edit Multiple" feature to edit the Protocol Options on multiple New Honeywell Mercury devices.
8.2.1	Issue	Client Application	Removes erroneous log messages that were displayed when writing to an item with "ReadUserOnly" disabled.
8.2.1	Issue	Configuration Database	Improves performance of the Archive Management/Gap Detection Process.
8.2.1	Issue	Configuration Database	Improves performance of resetting a publisher, both with and without a filter. Note: Will be more efficient if appropriate indexes exist on the tables. Run the manual update script to create missing indexes.
8.2.1	Issue	Configuration Database	Improves overall publishing performance. Note: Will be more efficient if appropriate indexes exist on the tables. Run the manual update script to create missing indexes.
8.2.1	Issue	Configuration Database	Adds three reports for verifying data and schema integrity. -The "Data Integrity Report" returns information regarding potential errors in the configuration. -The "Frequent alarm and event Report" returns information regarding meters with alarms and events above a given quantity . -The "Database Schema Integrity Report" returns details about the production schema that does not match the installed ACM version such as missing or mismatched indexes and triggers.
8.2.1	Issue	Configuration Database	Adds a table to the ACM Database for keeping track of database version history.
8.2.1	Issue	Configuration Database	Provides a script to create all expected but missing indexes on ACM tables.
8.2.1	Issue	Configuration Database	Modifies the stored procedure that is responsible for deleting archive records to make it more efficient.
8.2.1	Issue	Connections: Base Connection	Increases the Connection Settings Reply Timeout maximum value from two minutes to three minutes.
8.2.1	Issue	Connections: Serial Connection	Corrects an issue that prevented saving configuration changes in Serial Ports.
8.2.1	Issue	Connections: TCP Listen Connection	Corrects a crash in connection modules that occurred during poll interruption.
8.2.1	Issue	GC Write Service	Corrects an issue to prevent GC Write Requests from getting stuck after 32,767 retries when using "slow mode".
8.2.1	Issue	General	Corrects the OPC item ->Server/CfgCount value update when multiple ACMConfig Clients are connected.
8.2.1	Issue	General	Corrects an issue that allowed Async Writes from an OPC client when they should have been blocked.
8.2.1	Issue	General	Corrects an issue that could cause the initial OPC refresh to fail when used by a managed language client.
8.2.1	Issue	Logging	Corrects a crash in asiLOGSERVER service.
8.2.1	Issue	Protocols: Benchmark Protocol	Corrects an issue that caused asiData to hang when uploading history from a Benchmark device if the server did not have DST setup.
8.2.1	Issue	Protocols: ControlLogix Protocol	Adds a new option to "Invalidate read items on Forward Open failures". When selected, the driver will Invalidate read items on Forward Open connection errors that are non-recoverable, resulting in no poll messages with item value updates during that poll cycle attempt. Improved logging details for Forward Open connection errors.
8.2.1	Issue	Protocols: ControlLogix Protocol	Lowers the Timeout Multiplier for CIP connections to help avoid running out of connection resources during rapid polling schedules.
8.2.1	Issue	Protocols: ControlLogix Protocol	Corrects an issue with Bit offsets for INT data types that stopped getting read updates after being written to with the Verify Writes option enabled.
8.2.1	Issue	Protocols: ControlLogix Protocol	Corrects an issue where invalid messages present in the buffer could cause validation logic to hang up the polling engine.
8.2.1	Issue	Protocols: Enron Modbus Protocol	Corrects an issue where EFM configuration requests were being built individually, even when poll block was enabled and registers were within range. Now these will be built as combined messages for Enron, Kinder Morgan, Prosoft, Scadapack and Scanner1150 Modbus protocol.
8.2.1	Issue	Protocols: Flow Automation Protocol	Modifies the driver to output the correct meter configuration record for Coastal Flow device type.
8.2.1	Issue	Protocols: FlowX Protocol	Provides missing device destination IP and Port as part of requested message to meet possible firewall rules.
8.2.1	Issue	Protocols: FlowX Protocol	Corrects an issue that could prevent history collection when not using an alarm map.
8.2.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that prevented items from being successfully added during a restart of ACM if the device firmware did not support the new RG command.
8.2.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue that prevented messages from being consolidated after items were removed.
8.2.1	Issue	Protocols: Honeywell - Mercury Protocol	Corrects an issue when writing TS, GCWrite and NextCallinSchedule that prevented the write message from using the configured access code.
8.2.1	Issue	Protocols: Honeywell - Mercury Protocol	Modifies the driver to correctly handle an error returned during an ACK or NAK request so that a poll cycle retry will be triggered.
8.2.1	Issue	Protocols: Honeywell - Mercury Protocol	Modifies several protocols such as the new Mercury protocol and Omni protocol to update meter record time stamp after recollection. *Effect On Published Output: Meter configuration records will be republished after re-collection without requiring a restart of asiData.	X
8.2.1	Issue	Protocols: Modbus Protocol	Corrects an error that prevented using the modbus "block read" item.
8.2.1	Issue	Protocols: ROC Protocol	Corrects a logger warning message which resulted when some ROC configurations published meter configuration information.
8.2.1	Issue	Protocols: Scancom Protocol	Corrects an issue with Demand GC message not correctly building for Adept 4.0 message format.
8.2.1	Issue	Protocols: Scancom Protocol	Corrects an issue with variable length strings in EFM records that resulted in reading incorrect characters from the buffer beyond the record. *Effect On Published Output: Invalid characters from the buffer will no longer be output in a variety of record types.	X
8.2.1	Issue	Protocols: Scancom Protocol	Corrects OPC validation of hardware items so that they will will not be added if parameter and slot are not entered correctly.
8.2.1	Issue	Protocols: Scancom Protocol	Modifies the driver so that items not updated due to an error with an item id in a read are now marked as invalid.
8.2.1	Issue	Protocols: Siemens S7 Protocol	Adds configuration settings to directly control TSAP values on S7-200 model connections.
8.2.1	Issue	Protocols: Totalflow Protocol	Corrects the log messages displayed when executing the "Retrieve Meter config during next history poll" and "Reset History (LogPeriod/Daily/Event) Pointer" commands.
8.2.1	Issue	Protocols: Totalflow Protocol	Corrects an issue in the meter configuration record where multiple sets of duplicated fields were output when using the Number of Days history collection option. *Effect On Published Output: Meter Configuration records will no longer contain multiple duplicate fields.	X
8.2.1	Issue	Publishing	Corrects an issue that could cause the FlowCal Transaction Queue publisher to insert a zero into a GC or history field when the field has no value. *Effect On Published Output: Empty GC and history record fields will now be blank instead of displaying a 0 in the Flowcal Transaction Queue.	X
8.2.1	Issue	Configuration Database	Modifies the meter historization process to run in a stored procedure instead of a trigger to prevent issues with replication and clustering.
8.2.1	Issue	Configuration Database	Modifies the meter historization process to only keep unique meter FieldData
8.2.1	Issue	Honeywell - Mercury Protocol	Corrects an issue that resulted in response packet noise byte characters being included in the CRC calculation.
8.2.1	Issue	Honeywell - Mercury Protocol	Corrects an issue that could result in a failed EFM upload completing with a Successful Poll result.