Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Adds additional items for the AutoTune/AutoRecovery command for read and writeXXasiBridgeCorrects Quality of Service used by asiBRIDGE when it publishes MQTT messages. Increases the size of variables in asi_spGetPublisherFilteredObjects to handle very large filters.YESXXXXXXXXXXYESPublishing the asiPublish process from hanging when asiData is being shut down.1Server MonitorPrevents an exception in the Server Monitor that could occur when retrieving ACM license request information when FIPS is enabled in the Group Policy

Release

Category

Type

Text

Affects Published Output

Addresses Security Vulnerability
ACM 9.1.1Bulk Manager2Alias Groups/ItemsIssueCorrects an issue after upgrading to 9.1.0 that prevented asiBulkMgr from starting until the database connection had been modified in ACM Monitor.ACM 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.12Client ApplicationAPIIssuePrevents 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.ACM Corrects an issue that caused the AutoSol.ACM.Config.Client file to not be found when developing using the API in an ASP.NET environment.

9.1.12Client ApplicationasiDATAIssuePrevents the Dashboard grid from flickering when sorting a large number of records.ACM 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.12Client ApplicationasiDATAIssueRemoves the option to select an Alias Group object in the "Status" panel of port objects.ACM Corrects an issue that caused an invalid timestamp to occur on Leap Day.

9.1.12Client ApplicationBase ConnectionIssueMasks the password in the "Provider String" fields on the Database and AUTOSOL EFM Database objects "Database" tabs.ACM Corrects the failure retry count of polls that occur after a priority interruption.

9.1.12Client ApplicationIssueMasks the "Password" field in the "Security" section of the Totalflow "Device" tab.ACM BSAP ProtocolIssueCorrects an issue that caused BSAP Devices to fail to retrieve history over ethernet connections.

9.1.12Client ApplicationBulk ManagerIssueImproves the loading performance of the Dashboard.ACM 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.|Improves the log messages to contain more details if a SQL failure occurs.

9.1.12Client ApplicationIssueCorrects 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.ACM 9.1.1Configuration DatabaseIssueDeprecated Alias Group properties will be added to the database cleanup script.ACM 9.1.1Connections: TCPIP ConnectionIssueDuring a primary path test, ACM will no longer attempt to connect to the primary port if it was closed with a 'Close Port' command.ACM 9.1.1GC Write ServiceIssueAdds more details for file parsing errors to aid in troubleshooting processing issues.ACM 9.1.1GeneralIssuePrevents loss of data when ACM cannot read the configuration from the database during startup.ACM 9.1.1GeneralIssueCorrects the missing log messages for 'Data sent to client' when the client is an OPC UA client.ACM 9.1.1InstallerIssueCorrects an issue that caused the 64-bit version of ACM to be installed in C:\Program Files(x86) instead of C:\Program Files.ACM 9.1.1InstallerIssueCorrects an issue that may cause the ACM installer to erroneously report that a previous version of ACM is already installed.ACM 9.1.1Kinder Morgan ModbusIssueCorrects an issue related to archive sequence number resets.ACM 9.1.1MQTTChanges 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.2Client ApplicationIssueRestores the User Preference Activate Alias Tags on Status Tab "Only when Alias Group tags are active" option.

9.1.2Client ApplicationIssueRemoves the unused 'Alarm Service' fields from the ACM Connect to Server Options.

9.1.2Client ApplicationIssueIncreases the character limit of the "Provider String" field to 512 characters for the EFMDB and DB output types.

9.1.2Client ApplicationIssueChanges the default button on the "Delete Objects" dialog to "Cancel".

9.1.2Client ApplicationIssuePrevents spaces from being saved at the beginning or end of the Connect String field.

9.1.2Client ApplicationIssueCorrects sorting for datetime columns in the Dashboard.

9.1.2Client ApplicationIssuePrevents the Config Client from disconnecting from the server when using special characters in the search tool. 

9.1.2Client ApplicationIssueCorrects 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.2Client ApplicationIssueCorrects an issue that caused asiData to crash when restarting asiItemServer.ACM the search to only find matching objects if those objects had a description.

9.1.12MQTTClient ApplicationIssueAdds configurable logging detail modes for connections, device and item activity between ACM and MQTT broker publishing to aid in troubleshooting.ACM 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.12OPC UAConfiguration DatabaseIssueCorrects the data type of the initial value update for archive 'Move' and 'Reset' items in the Totalflow protocol.ACM Updates the asi_spFrequentalarmandEventReport stored procedure to use the alarmLimitEvent parameter.

9.1.12OPC UAConfiguration DatabaseIssueIncorporates OPC Foundation stack version 1.4.371.96 which includes resolutions for security issues CVE-2023-27321 and CVE-2023-31048Adds 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.
 YES
ACM 9.1.2Configuration DatabaseIssueUpdates variables in two stored procedures, asi_spResetPublisherPosition_Filter and asi_spResetPublisherPosition, from INT to BIGINT to allow for very large archive sequence IDs.

9.1Protocols: Base Protocol.2Configuration DatabaseIssuePrevents 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.ACM 9.1.1Protocols: BSAP ProtocolIssuePrevents a memory leak that may occur when using Accol or Signal files for item names.ACM 9.1.1Protocols: BSAP ProtocolIssueCorrects 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.XACM 9.1.1Protocols: FlowX ProtocolIssuePrevents repeat error log messages for duplicate tag names when configuring a FlowX History Map object.ACM 9.1.1Protocols: GE SRTP ProtocolIssuePrevents a memory leak that occurs when the GESRTP Protocol validates received responses.ACM 9.1.1Protocols: Honeywell - Mercury ProtocolIssueCorrects an issue that created duplicate EFM meter configuration fields. *Effect On Published Output: ACM will no longer publish duplicate EFM meter configuration fields.XACM 9.1.1Protocols: Honeywell - Mercury ProtocolIssueCorrects 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.XACM 9.1.1Protocols: Honeywell - Mercury ProtocolIssueCorrects 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.ACM 9.1.1Protocols: Modbus ProtocolIssuePrevents a memory leak that could occur when retrieving history in the Modbus Enron and Modbus SCADAPack protocols.ACM 9.1.1Protocols: Omni Modbus ProtocolIssueCorrects a polling error that occurred when using the "Modicon Compatible" option on the Modbus OMNI 7000 "OMNI" tab.ACM 9.1.1Protocols: ROC ProtocolIssueCorrects 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+.XACM 9.1.1Protocols: SCADAPack ProtocolIssueCorrects the Data Resolution value published to CFX files. *Effect On Published Output: The correct Data Resolution value will be published to CFX files.XACM 9.1.1Protocols: SCADAPack ProtocolIssueCorrects 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.XACM 9.1.1Protocols: SCADAPack ProtocolIssuePrevents 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.XACM 9.1.1Protocols: SCADAPack ProtocolIssueAdds initial support for new Scadapack 470i and 474i controllers.ACM 9.1.1Protocols: Totalflow ProtocolIssueUses 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.XACM 9.1.1Protocols: Totalflow ProtocolIssueTurbine 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.XACM 9.1.1Protocols: Totalflow ProtocolIssueCorrects 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.XACM 9.1.1Protocols: Totalflow ProtocolIssueCorrects a memory leak that occurs during history collection if at least one debounce meter and input is assigned.ACM 9.1.1PublishingIssuePrevents a memory leak in the publisher process if a referenced token string cannot be identified.ACM 9.1.1PublishingIssueCorrects a memory leak when using the right-click configuration tree menu option to re-publish history for a device.ACM 9.1.1Server MonitorIssueAdds 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.ACM 9.1.1Server MonitorIssueProvides 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.ACM 9.1.1GeneralIssuePrevents a memory leak that could occur when the asiData service is stopped.ACM 9.1.1GeneralIssuePrevents a memory leak that could occur when configuring View objects.ACM 9.1.1Server MonitorIssueUpdates 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.ACM 9.1.1Server MonitorIssueAdds the license information to the "View Client/Server Info" form in ACM Configuration.ACM 9.1.1Siemens S7 ProtocolIssueCorrects an issue with non bit offset writes that was causing the device to return an error.ACM 9.1.1Siemens S7 ProtocolIssueCorrects an issue that prevented some error messages from being logged when the Enhanced logging option was not selected.ACM 9.1Client ApplicationFeatureAdds a new "right-click" menu option labeled "Navigate To Object" to an object tab that will locate the opened object in the configuration tree. ACM 9.1Client ApplicationFeatureAdds a row number to the Dashboard grid. ACM 9.1Connections: UDP BSAP ConnectionFeatureModifies ACM to ignore the UDP error code 'WSAECONNRESET' in UDP BSAP. ACM 9.1GeneralFeatureAdds 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. ACM 9.1Mobile PortalFeatureAUTOSOL has released the Mobile Portal. ACM 9.1OPC UAFeatureAdds 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 GuideACM 9.1OPC UAFeatureAdds support for writing to array type items in ACM. ACM 9.1OPC UAFeatureAdds configurable server properties MaxNodesPerWrite and MaxMonitoredItemsPerCall. ACM 9.1OPC UAFeatureIntegrates the OPC UA .NET Standard Stack Version 1.4.370.12 from OPC Foundation which fixes the following cybersecurity vulnerability: CVE-2022-33916. YESACM 9.1Protocols: ControlLogix ProtocolFeatureUpdates the driver so it can communicate with a device running ControlLogix firmware Rev34. ACM 9.1Protocols: DNP3 ProtocolFeatureAdds a modifier &SECONDS to the DNP3 FBx protocol to return seconds elapsed since January 1st, 2000 at 12:00:00 AM. ACM 9.1Protocols: DNP3 ProtocolFeatureAdds 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.XACM 9.1Protocols: DNP3 ProtocolFeatureAdds the fields KFactor13 - KFactor20 and Frequency13 - Frequency20 to the publisher and the Meter Configuration object. ACM 9.1Protocols: DNP3 ProtocolFeatureAdds the field VersionNumber to the Meter Configuration object. ACM 9.1Protocols: DNP3 ProtocolFeaturePublishes 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.XACM 9.1Protocols: E-Lite Modbus ProtocolFeatureAdds 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. ACM 9.1Protocols: Honeywell - Mercury ProtocolFeatureAdds 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. ACM 9.1Protocols: Honeywell - Mercury ProtocolFeatureAdds a new feature to allow a time sync to be performed on RTU call-in. ACM 9.1Protocols: Kimray ProtocolFeatureModifies 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.2ControlLogix ProtocolIssueCorrects an issue that prevented the LastPollSuccessTime from updating correctly due to CIP Forward Open errors.X
9.1.2DNP3 ProtocolIssueModifies the Move and Reset commands for alarm and event pointers so that they will execute as long as any meter is assigned.

9.1.2DNP3 ProtocolIssueCorrects 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.2DNP3 ProtocolIssuePrevents an OPC Client from activating DNP3 internal items.X
9.1.2DNP3 ProtocolIssueCorrects 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.2ExportMDBIssuePrevents ACM from replacing an existing Access database backup file with an empty one if asiData cannot connect to SQL Server.

9.1.2GE SRTP ProtocolIssueExtends the write message to include more than one item write in the same protocol message.

9.1.2Honeywell - Mercury ProtocolIssueCorrects an issue that could cause multiple items to be associated with an RD message when the server was starting.

9.1.2Honeywell - Mercury ProtocolIssueCorrects an issue that caused a Call-in message to be ignored if a low priority write was currently queued.X
9.1.2Honeywell - Mercury ProtocolIssueCorrects an issue that caused items that were reported as invalid by the RTU to be added back to poll messages.X
9.1.2Honeywell - Mercury ProtocolIssueCorrects an issue that prevented an item write from being sent to device if the write happened during an active poll session.X
9.1.2Honeywell - Mercury ProtocolIssueCorrects 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.X
9.1.2Honeywell - Mercury ProtocolIssueCorrects 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.2Honeywell - Mercury ProtocolIssueDecodes 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.2Honeywell - Mercury ProtocolIssueModifies the 'First Collection Limit' so that the most recent alarm and event Archive records are published instead of the oldest. X
9.1.2Honeywell - Mercury ProtocolIssueCorrects 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.2Honeywell - Mercury ProtocolIssueModifies the protocol to perform a primary path test before switching from the secondary connection to the primary connection.

9.1.2Honeywell - Mercury ProtocolIssuePrevents the driver from collecting records that are out of the request range.

9.1.2Honeywell - Mercury ProtocolIssuePrevents a possible invalid value from appearing in the PGASOutputOptions property. 

9.1.2Honeywell - Mercury ProtocolIssueCorrects an issue that prevented the Mercury Call-in Schedule from saving the Start, Length, and Interval values.

9.1.2Importer/ExporterIssuePrevents ACM from updating references when the "Cancel" button is clicked from the Import form.

9.1.2Importer/ExporterIssuePrevents an error from occurring when importing a "Connect String" that had a space at the end of the value.

9.1.2Importer/ExporterIssueCorrects an issue encountered while importing Alias Groups with empty record values that prevents the entire Alias Group from getting imported.

9.1.2Item ServerIssueReduces 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.2Item ServerIssueCorrects an issue that caused MinutesSinceComplete to be incorrectly calculated immediately after DST.

9.1.2Kinder Morgan ModbusIssueImproves the handling of unexpected sequence number and archive reset conditions.

9.1.2LoggingIssueAdds 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.2Modbus ProtocolIssueAdds 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.2MQTTIssueCorrects an issue that sent erroneous DDEATH messages to the MQTT broker when the interval on an alias group changed.

9.1.2MQTTIssueCorrects an issue that caused a partially configured broker to require an ItemServer restart before being able to complete the configuration.

9.1.2OPC UAIssueCorrects the data type of the initial value update for archive 'Move' and 'Reset' items.

9.1.2OPC UAIssuePrevents inactive OPC UA items from getting an internal update.

9.1.2OPC UAIssueCorrects an issue that could prevent items in a new Alias Group from being updated if that contained invalid item names.|Sets the status of a node that represents an ACM item to 'UncertainLastUsableValue' when all monitored items are removed from the node.

9.1.2OPC UAIssueCorrects an issue that prevented a monitored item from being created on an address space node that has a bad status.

9.1.2OPC UAIssueCorrects 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.2Prosoft ModbusIssueModifies 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.2PublishingIssueIn 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.2PublishingIssueCorrects 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.2ROC ProtocolIssueRemoves 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.X
9.1.2ROC ProtocolIssueCorrects an issue that caused the driver to retrieve all batch records instead of the Batch Archive Limit value.

9.1.2ROC ProtocolIssueCorrects an issue where the tag modifier <TJULIAN> was not functional for 4 byte Julian dates.

9.1.2Server MonitorIssueCorrects an issue that caused the Database Statistics form to return the error message: "Keyword not supported: 'provider' not allowed.".X
9.1.2Server MonitorIssueUpdates the support package creator to provide more information regarding what can be included and provide more options to configure the contents.

9.1.2Server MonitorIssueCorrects an issue that caused the wrong "History Deletion Frequency" option to be displayed during create/update database operations via ACM Monitor.

9.1.2Server MonitorIssueModifies the database form in ACM Monitor so that the "Create/Update Database" button cannot be clicked until a provider is selected.

9.1.2Totalflow ProtocolIssueCorrects 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.2Totalflow ProtocolIssueIncludes 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 orifice meters using the AGA3-2013 calculation method.X
9.1.2Totalflow ProtocolIssueIncludes additional diagnostic logging when the "Enable message tracing for more logging information" option is selected.

9.1.2Totalflow ProtocolIssueCorrects an error that could use the wrong 'remote meter index' when sending GC data to device.X
ACM 9.1Protocols: ROC ProtocolFeatureAdds 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+. 

ACM 9.1Protocols: ROC ProtocolFeatureAdds 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
ACM 9.1Protocols: ROC ProtocolFeatureAdds support for Vinson Haul Logs, Vinson Cyclic Logs and Vinson Gas Lift Logs in 107, 80X and 800L series ROC devices

ACM 9.1Protocols: ROC ProtocolFeatureAdds more details to the logging information when the "Log EFM Upload Progress" option on the "Device" tab is checked. 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
ACM 9.1Protocols: ROC ProtocolFeatureAdds 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.90the ability to configure, by meter, which TLPs are written to on GC Write activities

ACM 9.1Protocols: ROC SCADAPack ProtocolFeatureAdds the Software Version to the meter configuration collectionan option to the "Archive Collection" tab labeled "Publish Density to Observed Density with Liquid Meters". *Effect On Published Output: The Software Version will now be populated in CFX outputIf the new option is checked, the Density value will be published to Observed Density for Liquid Meters.X
ACM 9.1Protocols: ROC SCADAPack ProtocolFeatureAdds 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+Upgrades the SCADAPack driver to support 20 meters

ACM 9.1Protocols: ROC Totalflow ProtocolFeatureAdds 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"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: When the new option is selected, history will be published for devices with no meters configuredIf configured, "Attached to Stream", "Stream Id" and "Fixed Analysis on Error" will be included in the published output.X
ACM 9.1Protocols: ROC ProtocolWeatherford ProtocolFeatureUpdates the driver so that an OPC Sync Read of a card buffer array item will cause an immediate upload of that card buffer. 

ACM 9.1ReportsFeatureAdds support for Vinson Haul Logs, Vinson Cyclic Logs and Vinson Gas Lift Logs in 107, 80X and 800L series ROC devicesthe 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

ACM 9.1Protocols: ROC ProtocolSecurityFeatureAdds 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.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. 

ACM 9.1Protocols: ROC ProtocolServer MonitorFeatureAdds the ability to configure, by meter, which TLPs are written to on GC Write activitiesa new column in ACM Monitor Status view showing the Startup Type (i.e. Manual, Automatic or Disabled) for each process

ACM 9.1Protocols: SCADAPack ProtocolServer MonitorFeatureAdds 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.Provides the ability to change the Startup Type for all ACM processes within the ACM Monitor Status View tab. 

ACM 9.1Alias Groups/ItemsIssueCorrects 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. 

ACM 9.1Protocols: SCADAPack ProtocolFeatureUpgrades the SCADAPack driver to support 20 metersAPIIssueModifies the API to enforce validation of maximum/minimum values

ACM 9.1Protocols: Totalflow ProtocolFeatureAdds "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.XAPIIssueCorrects an issue connecting to ACM when the API is loaded by an unmanaged process. 

ACM 9.1Protocols: Weatherford ProtocolFeatureUpdates the driver so that an OPC Sync Read of a card buffer array item will cause an immediate upload of that card bufferasiBridgeIssueCorrects the Quality of Service used by asiBRIDGE when it publishes MQTT messages

ACM 9.1ReportsClient ApplicationFeatureIssueAdds 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 commaModifies 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

ACM 9.1SecurityClient ApplicationFeatureIssueAdds 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.Corrects the tool tip message for the Details tab User01 property. 

ACM 9.1Server MonitorClient ApplicationFeatureAdds a new column in ACM Monitor Status view showing the Startup Type (i.e. Manual, Automatic or Disabled) for each processIssueCorrects an issue that caused the Configuration Manager to disconnect from asiData when searching for certain special characters (e.g parantheses)

ACM 9.1Server MonitorClient ApplicationFeatureProvides the ability to change the Startup Type for all ACM processes within the ACM Monitor Status View tabIssueCorrects an issue in the Scheduled Report form that caused fields using tokens to be reset

ACM 9.1Alias Groups/ItemsClient ApplicationIssueCorrects 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 groupsan issue that prevented  the object tree from reloading when selecting multiple objects via the search tool

ACM 9.1APIClient ApplicationIssueModifies the API to enforce validation of maximum/minimum valuesAdds the $Server and $Perf objects to the object tree in "Type View" and "Category View"

ACM 9.1APIConfiguration DatabaseIssueCorrects an issue connecting to ACM when the API is loaded by an unmanaged processcasing in asi_spInvokeArchiveSnapshot and asi_spGetPublisherFilterObjects to prevent errors on SQL Servers with extremely strict case defaults

ACM 9.1Configuration DatabaseIssueIncreases the size of variables in asi_spGetPublisherFilteredObjects to handle very large filters.

ACM 9.1Client ApplicationConfiguration DatabaseIssueModifies 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 metersCorrects an issue in the stored procedure asi_spInvokeArchiveSnapshots that could cause the Archive Management grid to display an incorrect Contract Hour for various protocols

ACM 9.1Client ApplicationConfiguration DatabaseIssueCorrects the tool tip message for the Details tab User01 propertyThe 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

ACM 9.1Client ApplicationGC Write ServiceIssueCorrects an issue that caused the Configuration Manager to disconnect from asiData when searching for certain special characters (e.g parantheses).the use of the tab delimiter and adds validation for delimiters in the GC Write File Service. 

ACM 9.1Client ApplicationGeneralIssueCorrects an issue in the Scheduled Report form that caused fields using tokens to be reset. ACM 9.1Client ApplicationIssueCorrects an issue that prevented  the object tree from reloading when selecting multiple objects via the search toolACM to wait for an OPC Sync Read request to complete when the target device object had been disabled

ACM 9.1Client ApplicationGeneralIssueAdds the $Server and $Perf objects to the object tree in "Type View" and "Category View". Changes the default DCOM authentication level from 'Connect' to 'Packet Integrity'. An override is available and instructions are found in the ACM and Windows DCOM Hardening section of the user guide.
YES
ACM 9.1Configuration DatabaseGeneralIssueCorrects casing in asi_spInvokeArchiveSnapshot and asi_spGetPublisherFilterObjects to prevent errors on SQL Servers with extremely strict case defaultsan issue that could cause an invalid timestamp in an OPC data change update

ACM 9.1Configuration DatabaseIssueImporter/ExporterIssueExcludes missing Alias Group references from exported configuration data and ignores missing Alias Group references during configuration import. 

ACM 9.1Configuration DatabaseImporter/ExporterIssueCorrects an issue in the stored procedure asi_spInvokeArchiveSnapshots that could cause the Archive Management grid to display an incorrect Contract Hour for various protocolsModifies the import process so it will update all references after an import

ACM 9.1Configuration DatabaseInstallerIssueThe 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. Modifies the ACM Crash Dump Configuration so that it will change when the ACM Data Directory is changed. 

ACM 9.1GC Write ServiceKinder Morgan ModbusIssueCorrects the use of the tab delimiter and adds validation for delimiters in the GC Write File Servicean issue related to archive sequence number resets in Kinder Morgan Modbus

ACM 9.1GeneralOPC ItemsIssueCorrects an issue that caused ACM to wait for an OPC Sync Read request to complete when the target device object had been disabledCommunication Statistics counter values. 

ACM 9.1OPC ItemsIssueCorrects an error that cleared the item's last value when quality was "Last Known Value"

ACM 9.1GeneralOPC UAIssueChanges the default DCOM authentication level from 'Connect' to 'Packet Integrity'. An override is available and instructions are found in the ACM and Windows DCOM Hardening section of the user guide.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". 

ACM 9.1GeneralOPC UAIssueCorrects an issue that could cause an invalid timestamp in an OPC data change updateAdds functionality to allow the OPC UA server to start asiData when a client app connects

ACM 9.1Importer/ExporterIssueExcludes missing Alias Group references from exported configuration data and ignores missing Alias Group references during configuration importOPC UAIssueCorrects an issue that rejected items with square brackets around the device object name

ACM 9.1Importer/ExporterOPC UAIssueModifies the import process so it will update all references after an importCorrects 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

ACM 9.1InstallerOPC UAIssueModifies the ACM Crash Dump Configuration so that it will change when the ACM Data Directory is changed. ACM 9.1Kinder Morgan ModbusIssueCorrects an issue related to archive sequence number resets in Kinder Morgan Modbus. ACM 9.1OPC ItemsIssueCorrects Communication Statistics counter valuesCorrects 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'

ACM 9.1OPC ItemsUAIssueCorrects an error that cleared the item's last value when quality was "Last Known Value"issue that prevented monitored items from being created in the Server address namespace

ACM 9.1OPC UAIssueAdds 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"Corrects issue that could cause items to not be added to ACM but be active in the client application when the 'Only connect to asiData when there are active client sessions' property is enabled

ACM 9.1OPC UAIssueAdds functionality to allow the OPC UA server to start asiData when a client app connectsProtocols: Base ProtocolIssueRemoves a duplicate warning message in log files about Item Data and Item Update that appeared when a demand timed out

ACM 9.1OPC UAIssueCorrects an issue that rejected items with square brackets around the device object nameProtocols: Base ProtocolIssueAdds validation to the device "Connect String" property to disallow non-numeric characters in the IP Port number

ACM 9.1OPC UAProtocols: Base ProtocolIssueCorrects 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 nameprevented the Archive Limits "Limit First Collection" settings from being applied when assigning an Archive Limit object after having collected history and reset the pointer

ACM 9.1OPC UAProtocols: Benchmark ProtocolIssueCorrects 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'issue that incorrectly processed a sub-command 11 when a field item data index was present in the item. 

ACM 9.1Protocols: DNP3 ProtocolIssueAdds support for Vinson Transactional Logs

ACM 9.1OPC UAProtocols: DNP3 ProtocolIssueCorrects an issue that prevented monitored items from being created in the Server address namespace. 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
ACM 9.1OPC UAProtocols: DNP3 ProtocolIssueCorrects an issue that could cause items to not be added to ACM but be active in the client application when the 'Only connect to asiData when there are active client sessions' property is enabledprevent 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

ACM 9.1Protocols: Base DNP3 ProtocolIssueRemoves a duplicate warning message in log files about Item Data and Item Update that appeared when a demand timed out. ACM 9.1Protocols: Base ProtocolIssueAdds validation to the device "Connect String" property to disallow non-numeric characters in the IP Port number. 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
ACM 9.1Protocols: Base FlowX ProtocolIssueCorrects 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 pointerhistory map validation to treat records with the same EFMID, MeterID and Period as duplicates

ACM 9.1Protocols: Benchmark GE SRTP ProtocolIssueCorrects an issue that incorrectly processed a sub-command 11 when a field item data index was present in the itemPrevents a memory leak in the GE SRTP protocol

ACM 9.1Protocols: DNP3 GE SRTP ProtocolIssueAdds support for Vinson Transactional LogsModifies 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

ACM 9.1Protocols: DNP3 Honeywell - Mercury ProtocolIssueCorrects an issue that prevented the "Use meter config from device" option from being used during publishing. *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: The correct meter configuration will be published based on the "Use meter config from device" checkboxAudit trail items set to address 255 will now be published if configured as a 'Value' field in the configurable archive object record set.X
ACM 9.1Protocols: DNP3 Honeywell - Mercury ProtocolIssueCorrects 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. the AlarmType register value for all available Mercury registers to display all digits. 

ACM 9.1Protocols: Honeywell - Mercury ProtocolIssueRemoves the extraneous 'Field5' field from the Alarm Record. *Effect On Published Output: Field5 will no longer be included in the published output.X
ACM 9.1Protocols: DNP3 Honeywell - Mercury ProtocolIssueACM 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 valuesAdds the alarm description in the alarm record output for non EC350 devices. *Effect On Published Output: Corrects publishing incorrect information to meter configuration records, and not retrieving available history recordsAlarm descriptions will be published for non-EFM alarms.X
ACM 9.1Protocols: FlowX Honeywell - Mercury ProtocolIssueCorrects the history map validation to treat records with the same EFMID, MeterID and Period as duplicatesModifies the driver so the demand item will be updated during a cry out after triggering a continuous scan

ACM 9.1Protocols: GE SRTP Honeywell - Mercury ProtocolIssuePrevents a memory leak in the GE SRTP 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
ACM 9.1Protocols: GE SRTP Honeywell - Mercury ProtocolIssueModifies 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 historyCorrects 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

ACM 9.1Protocols: Honeywell - Mercury ProtocolIssueCorrects 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.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. 

ACM 9.1Protocols: Honeywell - Mercury ProtocolIssueCorrects the AlarmType register value for all available Mercury registers to display all digitsA 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

ACM 9.1Protocols: Honeywell - Mercury ProtocolIssueRemoves the extraneous 'Field5' field from the Alarm Record. *Effect On Published Output: Field5 will no longer be included in the published output.Corrects an issue that caused the RTU call-in to not be acknowledged when no device protocol call-in options were enabled. 

ACM 9.1Protocols: Honeywell - Mercury ProtocolIssueAdds 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.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. 

ACM 9.1Protocols: Honeywell - Mercury ProtocolIssueModifies the driver so the demand item will be updated during a cry out after triggering a continuous scanRemoves the "Change Access" capability for Honeywell Mercury EC350 & ERX350 as it is unsupported by these devices

ACM 9.1Protocols: Honeywell - Mercury Micro MP3 ProtocolIssueCorrectly assign units for items 910 and 911 in Audit Trail record when used as meter1Corrects 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: The correct unit will be published for 910 and 911 if the Audit Trail record is used as meter 1Contract hour is now polled correctly and published for Micro MP3 devices.X
ACM 9.1Protocols: Honeywell - Mercury Modbus ProtocolIssueCorrects 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 ACMerror that occurred when writing to array item using common Modbus item modifier 'IS'

ACM 9.1Protocols: Honeywell - Mercury Omni Modbus ProtocolIssueCorrects 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. Prevents a Viscosity event in Omni 7000 devices from returning an abnormal code. 

ACM 9.1Protocols: Honeywell - Mercury Omni Modbus ProtocolIssueA 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. 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
ACM 9.1Protocols: Honeywell - Mercury Omni Modbus ProtocolIssueCorrects an issue that caused the RTU call-in to not be acknowledged when no device protocol call-in options were enabled.could cause an exception while processing an Omni 3000/7000 alarm record. 

ACM 9.1Protocols: Honeywell - Mercury ProtocolPossibly multiple protocolsIssueCorrects 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 enabledAdds all Batch Record field identifiers and Liquid Product field identifiers to the selection list in the Archive Field Configuration Record Collection form

ACM 9.1Protocols: Honeywell - Mercury ROC ProtocolIssueRemoves the "Change Access" capability for Honeywell Mercury EC350 & ERX350 as it is unsupported by these devicesAdds DATABASE.TOTAL_YD back to the OPC browsing list

ACM 9.1Protocols: Micro MP3 ROC ProtocolIssueCorrects 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.caused the GCWrite to write to incorrect TLPs if the GCWrite was executed before ROC meter configuration was read. 

ACM 9.1Protocols: Modbus ROC ProtocolIssueCorrects an error that occurred when writing to array item using common Modbus item modifier 'IS'issue that occasionally prevented the driver from determining the appropriate series when the "Do not switch ROC automatically series" was unchecked

ACM 9.1Protocols: Omni Modbus ROC ProtocolIssuePrevents a Viscosity event in Omni 7000 devices from returning an abnormal Corrects an issue that left an invalid item in the poll message after an "Invalid TLP" error code. 

ACM 9.1Protocols: Omni Modbus ROC ProtocolIssueAdds 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 metersCorrects 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
ACM 9.1Protocols: Omni Modbus ROC ProtocolIssueCorrects an issue that could cause an exception while processing an Omni 3000/7000 alarm recordPrevents the option group from scrolling when clicking on an option while the form is not maximized

ACM 9.1Protocols: Possibly multiple protocolsROC ProtocolIssueAdds all Batch Record field identifiers and Liquid Product field identifiers to the selection list in the Archive Field Configuration Record Collection forma field to the "Device" tab labeled "Schedule Reinitialization" to schedule the Reinitialize command

ACM 9.1Protocols: ROC ProtocolIssueAdds DATABASE.TOTAL_YD back to the OPC browsing list. 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. 

ACM 9.1Protocols: ROC SCADAPack ProtocolIssueCorrects an issue that caused the GCWrite to write to incorrect TLPs if the GCWrite was executed before ROC meter configuration was readprevented the Scadapack driver from updating the status of a GC Write request if the request failed due to a Comm error

ACM 9.1Protocols: ROC SCADAPack ProtocolIssueCorrects an issue that occasionally prevented the driver from determining the appropriate series when the "Do not switch ROC automatically series" was unchecked. 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
ACM 9.1Protocols: ROC Siemens ProtocolIssueCorrects an issue that left an invalid item in the poll message after an "Invalid TLP" error codewith Byte Bit offsets that caused returned and written values to be off by one index

ACM 9.1Protocols: ROC Totalflow ProtocolIssueCorrects 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.XACM 9.1Protocols: ROC ProtocolIssuePrevents the option group from scrolling when clicking on an option while the form is not maximizeda time sync and history request will fail due to having the same priority schedule

ACM 9.1Protocols: ROC Totalflow ProtocolIssueAdds a field to the "Device" tab labeled "Schedule Reinitialization" to schedule the Reinitialize command. 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
ACM 9.1Protocols: ROC Totalflow ProtocolIssueUpdates 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. 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
ACM 9.1Protocols: SCADAPack Totalflow ProtocolIssueCorrects an issue that prevented the Scadapack driver from updating the status of a GC Write request if the request failed due to a Comm errorAdds 'Double' data type support for Totaflow register read and write

ACM 9.1Protocols: SCADAPack Weatherford ProtocolIssuePrevents 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.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. 

ACM 9.1Protocols: Siemens Weatherford ProtocolIssueCorrects an issue with Byte Bit offsets that caused returned and written values to be off by one indexthat could cause the event directory upload to never cease running if the event buffer on the controller was completely full

ACM 9.1Protocols: Totalflow ProtocolIssueCorrects an issue where a time sync and history request will fail due to having the same priority schedulePublishingIssueIncreases the size of the variables in asi_spgetPublisherFilteredObjects to varchar(max) to process very 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

ACM 9.1Protocols: Totalflow ProtocolPublishingIssueModifies 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.Adds logging to the Database output type to show if a transaction was committed or rolled back to show the transaction completed. 

ACM 9.1PublishingIssueAdds the field name and unit of measure to the message that is logged when the publisher cannot validate an event. 

ACM 9.1Protocols: Totalflow ProtocolPublishingIssueCorrects the driver so it will not collect duplicate Alarm Records during log period collectionerror 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: Duplicate alarm records will not The sample date value from a DNP3 FBx device can now be published.X
ACM 9.1Protocols: Totalflow ProtocolPublishingIssueAdds 'Double' data type support for Totaflow register read and write. ACM 9.1Protocols: Weatherford ProtocolIssueCorrects an issue that could cause ACM to stop running if the driver received an unexpected response packet to an FC16EX card buffer upload request. ACM 9.1Protocols: Weatherford ProtocolIssueCorrects an issue that could cause the event directory upload to never cease running if the event buffer on the controller was completely full. ACM 9.1PublishingIssueIncreases the size of the variables in asi_spgetPublisherFilteredObjects to varchar(max) to process very 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. 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
ACM 9.1PublishingIssuePrevents 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
ACM 9.1PublishingIssueAdds logging to the Database output type to show if a transaction was committed or rolled back to show the transaction completed. 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
ACM 9.1PublishingIssueAdds the field name and unit of measure to the message that is logged when the publisher cannot validate an event. 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
ACM 9.1PublishingIssueCorrects 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.The User01, User02, User03, External GC Reference and External Meter Reference properties will now have values in the published output. 

ACM 9.1ReportsIssuePrevents extraneous logs from being written when saving edits to scheduled reports. 

ACM 9.1ReportsIssueCorrects an issue in the Scheduled Reports that caused the $$CurrentDay$$ or $$CurrentHour$$ tokens to be incorrectly calculated in Throughput reports. 

ACM 9.1PublishingReportsIssueCorrects 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.an issue in the Scheduled Reports form that prevented the Save button from being enabled after editing the connection. 

ACM 9.1ReportsIssueModifies the "Configuration Changes for a Device" report to filter to only Device type objects. 

ACM 9.1PublishingReportsIssuePrevents 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.Adds a new report titled "Configuration Changes for an Object" to search for configuration changes for any object type. 

ACM 9.1ReportsIssueAdds support for all of the following report formats to both manually run reports and scheduled reports:  CSV, HTML, PDF, XLS, XLSX, & TEXT. 

ACM 9.1PublishingReportsIssueAdds 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.Corrects the Scheduled Report form for the Missing Daily Archive Records to show the saved start and end date parameters when editing the form. 

ACM 9.1PublishingServer MonitorIssueIncludes 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.XAdds 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. 

ACM 9.1PublishingServer MonitorIssueThe User01, User02, User03, External GC Reference and External Meter Reference properties will now have values in the published outputAdds a button to view the connection string

ACM 9.1ReportsServer MonitorIssuePrevents extraneous logs from being written when saving edits to scheduled reportsModifies the History Deletion value displayed in the Task Summary field when creating a new ACM database to show HH:MM

ACM 9.1ReportsServer MonitorIssueCorrects an issue in the Scheduled Reports that caused the $$CurrentDay$$ or $$CurrentHour$$ tokens to be incorrectly calculated in Throughput reportsthe Write Timeout property of "Gas Analysis Writes Retry" to accept values in the range of 30 to 600 seconds

ACM 9.1ReportsServer MonitorIssueCorrects an issue in the Scheduled Reports form that prevented the Save button from being enabled after editing the connectionModifies the password requirements for the database user in ACM Monitor to prevent semi-colons

ACM 9.0.1

Reports

ACM Server

Issue

Modifies the "Configuration Changes for a Device" report to filter to only Device type objects. ACM 9.1ReportsIssueAdds a new report titled "Configuration Changes for an Object" to search for configuration changes for any object type. ACM 9.1ReportsIssueAdds support for all of the following report formats to both manually run reports and scheduled reports:  CSV, HTML, PDF, XLS, XLSX, & TEXT. ACM 9.1ReportsIssueCorrects the Scheduled Report form for the Missing Daily Archive Records to show the saved start and end date parameters when editing the form. ACM 9.1Server MonitorIssueAdds 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. ACM 9.1Server MonitorIssueAdds a button to view the connection string. ACM 9.1Server MonitorIssueModifies the History Deletion value displayed in the Task Summary field when creating a new ACM database to show HH:MM. ACM 9.1Server MonitorIssueCorrects the Write Timeout property of "Gas Analysis Writes Retry" to accept values in the range of 30 to 600 seconds. ACM 9.1Server MonitorIssueModifies the password requirements for the database user in ACM Monitor to prevent semi-colons. 

Corrects an issue that prevented encrypted channel communication between an ACM client and server when the client and server components are on different computers.



ACM 9.0.1

Bulk Manager

Issue

No longer moves Import files to the Import Failed folder after a SQL Timeout.  Instead they will remain in the Import folder.



ACM 9.0.1

Client Application

Issue

Corrects an issue in the "Password" and "Register Block Read Path" textboxes that did not allow user to enter a value properly.



ACM 9.0.1

Client Application

Issue

Removes the "Retrieve History", "Delete History for Device" and "Republish Device Records" commands from the right-click menu of Real-Time Only devices.



ACM 9.0.1

Client Application

Issue

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.



ACM 9.0.1

Client Application

Issue

Prevents the Edit Multiple Objects grid from re-sorting the data while a user is typing a value into a cell.



ACM 9.0.1

Client Application

Issue

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.



ACM 9.0.1

Configuration Database

Issue

Corrects an issue in SQLUpdate_39.sql that prevented the ACM database from upgrading to DBVersion 39 and above where the default collation on the SQL Server is SQL_Latin1_General_CP850_BIN.



ACM 9.0.1

Configuration Database

Issue

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.



ACM 9.0.1ACM Server

General

Issue

Corrects an issue that prevented encrypted channel communication between an ACM client and server when the client and server components are on different computersa memory leak that occurs when logging "data sent to client" on items in the OPC UA interface.



ACM 9.0.1

Bulk ManagerOPC UA

Issue

No longer moves Import files to the Import Failed folder after a SQL Timeout.  Instead they will remain in the Import folder.

ACM 9.0.1

Client Application

Issue

Corrects an issue in the "Password" and "Register Block Read Path" textboxes that did not allow user to enter a value properly.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.


YES

ACM 9.0.1

Client ApplicationProtocols: Base Protocol

IssueRemoves the "Retrieve History", "Delete History for Device" and "Republish Device Records" commands from the right-click menu of Real-Time Only devices

Correctly updates PctBadTries and PctGoodTries if the connection fails before the message can be sent.



ACM 9.0.1

Client ApplicationProtocols: Base Protocol

IssueCorrects an issue when creating a new Port Object that prevented the Port Type from being changed after canceling out of the folder location screen

Correctly updates the port PollAttempts counter when an external interruption occurrs.



ACM 9.0.1

Client ApplicationProtocols: Base Protocol

Issue

Prevents the Edit Multiple Objects grid from re-sorting the data while a user is typing a value into a cellqueuing an additional demand after Demand is poked to trigger a continuous scan during cry out.



ACM 9.0.1

Client ApplicationProtocols: Base Protocol

Issue

Corrects an issue that caused prevented the Logger and Queue tabs to go blank when a large number of object tabs were open in multiple ACM ClientsPctGoodTries and PctBadTries statistic items from being correctly updated when a connection was dropped before a message could be sent.



ACM 9.0.1

Configuration DatabaseProtocols: BSAP Protocol

Issue

Corrects an issue in SQLUpdate_39.sql that prevented the ACM database from upgrading to DBVersion 39 and above where the default collation on the SQL Server is SQL_Latin1_General_CP850_BINthat caused the driver to ignore the previous position and retrieve all history when the "Disable duplicate record deletion" option was selected.



ACM 9.0.1

Configuration DatabaseProtocols: BSAP Protocol

IssueIncreases

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.Prevents a crash from occurring when the Field Configuration has not been assigned and the device could not be reached.



ACM 9.0.1

Protocols: DNP3 Protocol

Issue

Adds support for new objects, parameters, measurements, units and error codes in Emerson FBx firmware release version 2.9. 

X


ACM 9.0.1

GeneralProtocols: DNP3 Protocol

IssueCorrects a memory leak that occurs when logging "data sent to client" on items in the OPC UA interface.

Handles alarm and event records that occur when the device is configured for BSAP Combined Event Log. *Effect on published output: Correctly publishes alarm and event records.

X


ACM 9.0.1

OPC UA

Issue

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.

Protocols: DNP3 Protocol

Issue

Uses meter config file from device to publish string events as well as FLOWCAL events to non-Generic meters. 

X


ACM 9.0.1

Protocols: Base DNP3 Protocol

IssueCorrectly updates PctBadTries and PctGoodTries if the connection fails before the message can

be sent.In cases where this can be detected before polling, does not try to retrieve records from empty or unconfigured archives.

X


ACM 9.0.1

Protocols: Base DNP3 Protocol

IssueCorrectly updates the port PollAttempts counter when an external interruption occurrs

Corrects an issue so that alias items are added correctly via browsing in an OPC client.



ACM 9.0.1

Protocols: Base DNP3 Protocol

IssuePrevents queuing an additional demand after Demand is poked to trigger a continuous scan during cry out.

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


ACM 9.0.1

Protocols: Base DNP3 Protocol

IssueCorrects

an issue that prevented the PctGoodTries and PctBadTries statistic items from being correctly updated when a connection was dropped before a message could be sentChanges the dropdown list that selects the meter run into a numeric updown control in the Meter Runs tab.



ACM 9.0.1

Protocols: BSAP Flow Automation Protocol

Issue

Corrects an issue that caused the driver to ignore the previous position and retrieve all history when the "Disable duplicate record deletion" option was selectedYesterdayFlowTime and YesterFlowEnergy to be incorrectly retrieved when the "Retrieve yesterday flow time or energy using history message" option was checked.



ACM 9.0.1

Protocols: BSAP Honeywell - Mercury Protocol

IssuePrevents

a crash from occurring when the Field Configuration has not been assigned and the device could not be reachedCorrects a potential memory leak.



ACM 9.0.1

Protocols: DNP3 Honeywell - Mercury Protocol

Issue

Adds support for new objects, parameters, measurements, units and error codes in Emerson FBx firmware release version 2.9. 

X

ACM 9.0.1

Protocols: DNP3 Protocol

Issue

Handles alarm and event records that occur when the device is configured for BSAP Combined Event LogCorrects 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: Correctly publishes alarm and event recordsFor ER type devices, the Units for Temperature and Pressure fields will now be published.

X


ACM 9.0.1

Protocols: DNP3 Modbus Protocol

Issue

Uses meter config file from device to publish string events as well as FLOWCAL events to non-Generic meters. 

X

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.



ACM 9.0.1

Protocols: DNP3 Omni Modbus Protocol

Issue

In cases where this can be detected before polling, does not try to retrieve records from empty or unconfigured archives.

X

Corrects an issue that prevented subsequent archives from being requested after processing the GC archive for Archive 1.



ACM 9.0.1

Protocols: DNP3 Omni Modbus Protocol

IssueCorrects an issue so that alias items are added correctly via browsing in an OPC client

Prevents a crash from occurring when polling raw data upload.



ACM 9.0.1

Protocols: DNP3 ROC Protocol

Issue

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

No longer updates the item quality when the "test" of the primary connection fails when using the Auto Recover feature.



ACM 9.0.1

Protocols: DNP3 ROC Protocol

IssueChanges

the dropdown list that selects the meter run into a numeric updown control in the Meter Runs tabDisplays the correct log message type in the logger when the "Items in message" log option is enabled.



ACM 9.0.1

Protocols: Flow Automation ROC Protocol

Issue

Corrects an issue that caused YesterdayFlowTime and YesterFlowEnergy to be incorrectly retrieved when the "Retrieve yesterday flow time or energy using history message" option was checkedin detecting the ROC model type that prevented ROC history collection settings from updating properly.



ACM 9.0.1

Protocols: Honeywell - Mercury ProtocolTotalflow Protocol

Issue

Corrects a potential memory leakan issue that prevented LastHourlyRecord/1 from being initialized correctly with the latest hourly record time stamp.



ACM 9.0.1

Protocols: Honeywell - Mercury Totalflow Protocol

Issue

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

occurred when the field device handles a request for a history record at the "maximum position" by returning more than one record.



ACM 9.0.1

Protocols: Modbus Totalflow Protocol

Issue

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.

Prevents a poll on the primary connection from switching to the secondary connection when an item with the secondary connection specifier failed to poll.



ACM 9.0.1

Protocols: Omni Modbus Totalflow Protocol

Issue

Corrects an issue that prevented subsequent archives from being requested after processing the GC archive for Archive 1the daily record from being collected when using the "number of days" method in the DB2 protocol.



ACM 9.0.1

Protocols: Omni Modbus Weatherford Protocol

Issue

Prevents a crash from occurring when polling raw data upload.

ACM 9.0.1

Protocols: ROC Protocol

Issue

No longer updates the item quality when the "test" of the primary connection fails when using the Auto Recover feature.

ACM 9.0.1

Protocols: ROC Protocol

Issue

Displays the correct log message type in the logger when the "Items in message" log option is enabled.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


ACM 9.0.1

Protocols: ROC ProtocolPublishing

Issue

Corrects an issue in detecting the ROC model type that prevented ROC history collection settings from updating properly.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


ACM 9.0.1

Protocols: Totalflow ProtocolPublishing

Issue

Corrects an issue that prevented LastHourlyRecord/1 from being initialized correctly with the latest hourly record time stampa PGAS XML publishing issue that created an unnecessary transaction with an empty 'METER' element.



ACM 9.0.1

Protocols: Totalflow ProtocolPublishing

IssueCorrects 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

Prevents the asiPublish process from hanging when asiData is being shut down.



ACM 9.0.1

Protocols: Totalflow ProtocolPublishing

IssuePrevents

a poll on the primary connection from switching to the secondary connection when an item with the secondary connection specifier failed to pollCorrects an issue that stopped publishing to the FLOWCAL Transaction Queue when a record had an invalid future timestamp.



ACM 9.0.1

Protocols: Totalflow ProtocolReports

Issue

Corrects an issue that prevented the daily record from being collected when using the "number of days" method in the DB2 protocolLogs the query of a scheduled report when the "Report Logging" option is enabled.



ACM 9.0.1

Reports

Protocols: Weatherford Protocol

Issue

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

users from requested unlimited records when running reports.



ACM 9.0.1

PublishingServer Monitor

Issue

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

ACM 9.0.1

Publishing

Issue

Corrects a PGAS XML publishing issue that created an unnecessary transaction with an empty 'METER' elementin 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.



ACM 9.0.1Server MonitorIssuePrevents an exception in the Server Monitor that could occur when retrieving ACM license request information when FIPS is enabled in the Group Policy.

ACM 9.0.1

PublishingTools

Issue

Corrects an issue that stopped publishing to the FLOWCAL Transaction Queue when a record had an invalid future timestampcould cause one OPC item to replace a previous OPC item in the ACM memory. This only affects the 64-bit version of ACM.



ACM 9.0.1

ReportsACM Server

IssueLogs the query of a scheduled report when the "Report Logging" option is enabled

Resolves issues related to OPC client browsing when clients use absolute browse paths instead of relative browsing.



ACM 9.0.1

ReportsACM Server

IssueCorrects an issue that prevented users from requested unlimited records when running reports

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.



ACM 9.0.1

Server MonitorAPI

Issue

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 existAPI which reported that "Server" objects are creatable.



ACM 9.0

Client Application

Issue

Feature

Adds the Object ID and Description to the search results form.



ACM 9.0.1

ToolsClient Application

Issue

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.Feature

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.



ACM 9.0ACM Server

Client Application

Issue

Resolves issues related to OPC client browsing when clients use absolute browse paths instead of relative browsing.Feature

Provides the ability to assign multiple alias groups to devices and views.  



ACM 9.0ACM Server

Client Application

IssueFeature

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.the ability to assign an Interval to Alias Groups.



ACM 9.0

APIClient Application

Issue

Corrects an issue in the API which reported that "Server" objects are creatableFeature

Adds the feature to drop down boxes on the Reports tab to automatically filter results while typing.



ACM 9.0

Client Application

Feature

Adds the Object ID and Description to the search results formIssue

Corrects an issue that occasionally caused an incorrect command name to be logged in the database.



ACM 9.0

Client Application

Feature

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 itemsIssue

Corrects the message regarding the maximum number of archive records that can be published from 1000 to 5000 to match the actual functionality.



ACM 9.0

Client Application

Feature

Provides the ability to assign multiple alias groups to devices and views.  Issue

Corrects various forms throughout ACM where fields and buttons were enabled when they shouldn't have been.



ACM 9.0

Client Application

Feature

Adds the ability to assign an Interval to Alias GroupsIssue

The Add/Select object window will now retain its size when closed and reopened.



ACM 9.0

Client ApplicationFeature

Adds the feature to drop down boxes on the Reports tab to automatically filter results while typing.

ACM 9.0

Client Application

Issue

Corrects an issue that occasionally caused an incorrect command name to be logged in the databasewhich 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.



ACM 9.0

Client Application

IssueCorrects the message regarding the maximum number of archive records that can be published from 1000 to 5000 to match the actual functionality

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.



ACM 9.0

Client Application

Issue

Corrects various forms throughout ACM where fields and buttons were enabled when they shouldn't have beenthe tab order on the "Database" tab of the configuration form of the $Server object.



ACM 9.0

Client Application

IssueThe Add/Select object window will now retain its size when closed and reopened

Prevents ACM Configuration from attempting to use an http port when connecting to ACM if one has not been configured.



ACM 9.0

Client Application

Issue

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.

ACM Displays a new error message when an object name contains a carriage return in the name.



ACM 9.0

Client Application

Issue

Prevents invalid data from being saved by disabling the Save button when text is deleted from a required field and when invalid data is enteredConfiguration Database

Issue

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.



ACM 9.0

Client ApplicationConfiguration Server

Issue

Corrects the tab order on the "Database" tab of the configuration form of the $Server objectChanges the default value for deleting old history to "Disabled".



ACM 9.0

Client Application

Issue

Prevents ACM Configuration from attempting to use an http port when connecting to ACM if one has not been configuredFeature

Protocols: SCADAPack Protocol

Adds support for SCADAPack x70 series RTUs.



ACM 9.0

Client Application

Issue

Displays a new error message when an object name contains a carriage return in the nameFeature

Protocols: SCADAPack Protocol

Adds support for RealFlo 7.0.



ACM 9.0

Configuration Database

Issue

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.

ACM 9.0

Configuration Server

Issue

Changes the default value for deleting old history to "Disabled".

ACM 9.0

Feature

Protocols: SCADAPack Protocol

Adds support for SCADAPack x70 series RTUs.

ACM 9.0

Feature

Protocols: SCADAPack Protocol

Adds support for RealFlo 7.0.

ACM 9.0

Feature

Protocols: SCADAPack Protocol

Adds support for AGA3-2013.

ACM 9.0

Issue

Configuration Database

Removes the logic from the Feature

Protocols: SCADAPack Protocol

Adds support for AGA3-2013.



ACM 9.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".



ACM 9.0

Issue

Configuration Database

Modifies the Meter Historization process stored procedure to improve processing speed.



ACM 9.0

Issue

Configuration Database

Deletes Meter Record History rows (in tblMeterRecordsHistory) for meters that do not exist in the ACM configuration.



ACM 9.0

Logging

Issue

Corrects an issue that caused messages to be split into multiple lines in the log file.



ACM 9.0

OPC Items

Issue

Corrects an issue that prevented Detail Items from displaying correctly in an OPC browse.



ACM 9.0

Protocols: Base Protocol

Issue

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.



ACM 9.0

Protocols: Base Protocol

Issue

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.



ACM 9.0

Protocols: Benchmark Protocol

Issue

Corrects an issue related to writing to multiple items at once that could cause asiData to crash.



ACM 9.0

Protocols: BSAP Protocol

Feature

Adds ControlWave signal items to RBE polls.



ACM 9.0

Protocols: BSAP Protocol

Issue

Corrects an issue that prevented the item value from saving for upload pointer and time sync item reads.



ACM 9.0

Protocols: ControlLogix Protocol

Issue

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.



ACM 9.0

Protocols: DNP3 Protocol

Feature

Implements items to log FBx meter configuration file data.  These items are: LogMeterFileDP/{meter number}, LogMeterFileLinear/{meter number}, LogMeterFileLiquid/{meter number} and LogMeterFileList.



ACM 9.0

Protocols: DNP3 Protocol

Feature

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


ACM 9.0

Protocols: DNP3 Protocol

Feature

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 event and alarm records. *Read the meter list and meter config files from the device to determine which items to read and publish as meter configuration 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


ACM 9.0

Protocols: DNP3 Protocol

Issue

Corrects problems with poll cycle interrupts and DNP3 message sequences that shouldn't be interrupted.



ACM 9.0

Protocols: Flow Automation Protocol

Issue

Corrects an issue that caused duplicate factor events to be published to the FLOWCAL Transaction Queue, which caused the publisher to fail.



ACM 9.0

Protocols: Honeywell - Mercury Protocol

Feature

Adds support for using configurable archive records.



ACM 9.0

Protocols: Honeywell - Mercury Protocol

Feature

Adds OPC item "MoveAudit" that provides the ability to move each Audit pointer to the desired date and time.



ACM 9.0

Protocols: Honeywell - Mercury Protocol

Feature

Adds OPC item "ChangeACS" in order for the user to change the access code.  This is only supported for non-350 series controllers.



ACM 9.0

Protocols: Honeywell - Mercury Protocol

Issue

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.



ACM 9.0

Protocols: Honeywell - Mercury Protocol

Issue

Corrects an issue that could cause an access violation error when certain noise bytes are received in a poll response.



ACM 9.0

Protocols: Honeywell - Mercury Protocol

Issue

Adds a new informational message when time synchronization is completed.



ACM 9.0

Protocols: Micro MP3 Protocol

Feature

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

ACM 9.0

Protocols: NGCTT Protocol

Issue

Corrects an issue that caused history polling to terminate when 10 04 bytes were returned from a device in the middle of polling.

ACM 9.0

Protocols: ROC Protocol

Feature

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

ACM 9.0

Protocols: ROC Protocol

Feature

Adds the ability to process ROC 800 Liquid meter data in the GC Write service.

ACM 9.0

Protocols: ROC Protocol

Feature

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

ACM 9.0

Protocols: ROC Protocol

Feature

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

ACM 9.0

Protocols: ROC Protocol

Feature

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

ACM 9.0

Protocols: ROC Protocol

Feature

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

ACM 9.0

Protocols: ROC Protocol

Feature

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

ACM 9.0

Protocols: ROC Protocol

Feature

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

ACM 9.0

Protocols: ROC Protocol

Issue

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

ACM 9.0

Protocols: ROC Protocol

Issue

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

ACM 9.0

Protocols: ROC Protocol

Issue

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.

ACM 9.0

Protocols: Romet-Adem Protocol

Issue

Corrects an issue that could cause incorrect meter configuration values when using the RD command to read register values after a timeout occurs.

ACM 9.0

Protocols: SCADAPack Protocol

Issue

Corrects an issue that caused GC Write to fail for gas coriolis meter runs on controllers running RealFlo 6.95 or greater.

ACM 9.0

Protocols: SCADAPack Protocol

Issue

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

ACM 9.0

Protocols: SCADAPack Protocol

Issue

Modifies the driver to use the correct registers for reading and writing heating value and gas density value.

ACM 9.0

Protocols: Scancom Protocol

Issue

Corrects an issue that prevented "Trusted Log In" from being enabled once it had been disabled.

ACM 9.0

Protocols: Scancom Protocol

Issue

Changes the "Read Only" state on FRDM items to reflect Barton documentation.

ACM 9.0

Protocols: Scancom Protocol

Issue

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.

ACM 9.0

Protocols: Teledyne CA Protocol

Issue

Corrects an issue in the driver that could prevent items of higher cards and points from being polled, which resulted in invalid item values.

ACM 9.0

Protocols: Totalflow Protocol

Issue

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

ACM 9.0

Protocols: Totalflow Protocol

Issue

Adds the Trend Record Type to the trends tab form view. It previously only existed in the Property Grid view.

ACM 9.0

Protocols: Weatherford Protocol

Feature

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.

ACM 9.0

Protocols: Weatherford Protocol

Feature

Optimizes the performance for OPC synchronous read from device requests.

ACM 9.0

Protocols: Weatherford Protocol

Issue

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.

ACM 9.0

Publishing

Feature

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

ACM 9.0

Publishing

Feature

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

ACM 9.0

Publishing

Issue

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

ACM 9.0

Publishing

Issue

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

ACM 9.0

Publishing

Issue

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

ACM 9.0

Reports

Issue

Optimizes the performance of retrieving and displaying report data.

ACM 9.0

Reports

Issue

Changes the heading of the 'Date' column in the Configuration Change Reports to 'Date (UTC)'.

ACM 9.0

Reports

Issue

Corrects an issue that could cause a scheduled report to run at least once a minute  - ignoring the "sync time".

ACM 9.0

Server Monitor

Issue

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.

ACM 9.0

Server Monitor

Issue

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.

ACM 8.2.1

ACM Server

Issue

Corrects a property load error that can occur when processes ACM relies upon aren't available.

ACM 8.2.1

Client Application

Issue

Corrects an issue that prevented using the "Edit Multiple" feature to edit the Protocol Options on multiple New Honeywell Mercury devices.

ACM 8.2.1

Client Application

Issue

Removes erroneous log messages that were displayed when writing to an item with "ReadUserOnly" disabled.

ACM 8.2.1

Client Application

Issue

Corrects the tool tip message for the Details tab User01 property.

ACM 8.2.1

Client Application

Issue

Corrects the checkbox list initial focus issue on multiple tabbed pages

ACM 8.2.1

Client Application

Issue

The date-time parameters in reports will now correctly display the saved date and time when editing a scheduled report.

ACM 8.2.1

Configuration Database

Issue

Improves performance of the Archive Management/Gap Detection Process.

ACM 8.2.1

Configuration Database

Issue

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.

ACM 8.2.1

Configuration Database

Issue

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.

ACM 8.2.1

Configuration Database

Issue

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.

ACM 8.2.1

Configuration Database

Issue

Adds a table to the ACM Database for keeping track of database version history.

ACM 8.2.1

Configuration Database

Issue

Provides a script to create all expected but missing indexes on ACM tables.

ACM 8.2.1

Configuration Database

Issue

Modifies the stored procedure that is responsible for deleting archive records to make it more efficient.

ACM 8.2.1

Connection: Base Connection

Issue

Increases the Connection Settings Reply Timeout maximum value from two minutes to three minutes.

ACM 8.2.1

Connection: Serial Connection

Issue

Corrects an issue that prevented saving configuration changes in Serial Ports.

ACM 8.2.1

Connection: TCP Listen Connection

Issue

Corrects a crash in connection modules that occurred during poll interruption.

ACM 8.2.1

GC Write Service

Issue

Corrects an issue to prevent GC Write Requests from getting stuck after 32,767 retries when using "slow mode".

ACM 8.2.1

General

Issue

Corrects the OPC item ->Server/CfgCount value update when multiple ACMConfig Clients are connected.

ACM 8.2.1

General

Issue

Corrects an issue that allowed Async Writes from an OPC client when they should have been blocked.

ACM 8.2.1

General

Issue

Corrects an issue that could cause the initial OPC refresh to fail when used by a managed language client.

ACM 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.

ACM 8.2.1

Issue

Configuration Database

Modifies the meter historization process to only keep unique meter FieldData

ACM 8.2.1

Issue

Protocols: Honeywell - Mercury Protocol

Corrects an issue that resulted in response packet noise byte characters being included in the CRC calculation.

ACM 8.2.1

Issue

Protocols: Honeywell - Mercury Protocol

Corrects an issue that could result in a failed EFM upload completing with a Successful Poll result.

ACM 8.2.1

Logging

Issue

Corrects a crash in asiLOGSERVER service.

ACM 8.2.1

Protocols: Benchmark Protocol

Issue

Corrects an issue that caused asiData to hang when uploading history from a Benchmark device if the server did not have DST setup.

ACM 8.2.1

Protocols: ControlLogix Protocol

Issue

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.

ACM 8.2.1

Protocols: ControlLogix Protocol

Issue

Corrects an issue where invalid messages present in the buffer could cause validation logic to hang up the polling engine.

ACM 8.2.1

Protocols: ControlLogix Protocol

Issue

Lowers the Timeout Multiplier for CIP connections to help avoid running out of connection resources during rapid polling schedules.

ACM 8.2.1

Protocols: ControlLogix Protocol

Issue

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.

ACM 8.2.1

Protocols: Enron Modbus Protocol

Issue

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.

ACM 8.2.1

Protocols: Flow Automation Protocol

Issue

Modifies the driver to output the correct meter configuration record for Coastal Flow device type.

ACM 8.2.1

Protocols: FlowX Protocol

Issue

Provides missing device destination IP and Port as part of requested message to meet possible firewall rules.

ACM 8.2.1

Protocols: FlowX Protocol

Issue

Corrects an issue that could prevent history collection when not using an alarm map.

ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

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.

ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

Modifies the driver to correctly handle an error returned during an ACK or NAK request so that a poll cycle retry will be triggered.

ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

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

ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

Corrects an issue that prevented messages from being consolidated after items were removed.

ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

Corrects an issue when writing TS, GCWrite and NextCallinSchedule that prevented the write message from using the configured access code.

ACM 8.2.1

Protocols: Modbus Protocol

Issue

Corrects an error that prevented using the modbus "block read" item.

ACM 8.2.1

Protocols: ROC Protocol

Issue

Corrects a logger warning message which resulted when some ROC configurations published meter configuration information.

ACM 8.2.1

Protocols: Scancom Protocol

Issue

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

ACM 8.2.1

Protocols: Scancom Protocol

Issue

Corrects an issue with Demand GC message not correctly building for Adept 4.0 message format.

ACM 8.2.1

Protocols: Scancom Protocol

Issue

Corrects OPC validation of hardware items so that they will will not be added if parameter and slot are not entered correctly.

ACM 8.2.1

Protocols: Scancom Protocol

Issue

Modifies the driver so that items not updated due to an error with an item id in a read are now marked as invalid.

ACM 8.2.1

Protocols: Siemens S7 Protocol

Issue

Adds configuration settings to directly control TSAP values on S7-200 model connections.

ACM 8.2.1

Protocols: Totalflow Protocol

Issue

Corrects the log messages displayed when executing the "Retrieve Meter config during next history poll" and "Reset History (LogPeriod/Daily/Event) Pointer" commands.

ACM 8.2.1

Protocols: Totalflow Protocol

Issue

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

ACM 8.2.1

Publishing

Issue

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

ACM 8.2

ACM Server

Feature

Adds new security options to control access to ACM from the desktop configuration program and from the mobile app. This also includes an option to control whether administrator accounts have access to ACM. Note that with these new settings, it is possible to leave the server in a state where no one has permission to change any configuration, or even access the server.

ACM 8.2

ACM Server

Issue

Adds the ability to delete history on a hourly interval.  This option is found in the Manage Database wizard of ACM Monitor.

ACM 8.2

ACM Server

Issue

Corrects an issue that prevented items in the "Alias" branch from displaying correctly when browsing ACM from Ignition.

ACM 8.2

Archive Management

Issue

Adds validation to the Missing Hourly and Daily calculation for Archive Management to handle a scenario in which the same meter is being used on multiple devices

ACM 8.2

Client Application

Issue

Modifies the ACM security login to accept ".\" in the user object's domain name.

ACM 8.2

Client Application

Issue

Corrects error that occurs when changing the ROC Max Message Length property using the multi editor.

ACM 8.2

Client Application

Issue

Modifies the Alias Group validation to prevent empty alias and item names from being saved.

ACM 8.2

Configuration Database

Issue

Corrects an issue that could cause replication to fail if the tblMeterRecordsHistory is being replicated.

ACM 8.2

Connection: TCP Listen Connection

Feature

Adds a property to the TCP Listen connection object to configure an initial data timeout after an incoming socket connection is accepted.

ACM 8.2

Connection: TCP Listen Connection

Feature

Adds a new option "Delay polling on same connection" to the TCP Listen connection to delay polling a device if it uses the same connection as another device that is currently polling, even if there is a session available. This will prevent multiple conflicting connections to the same IP address and Port.

ACM 8.2

Connection: TCP Listen Connection

Issue

Prevents a TCPIP Listen connection attempt from lasting more than two minutes.

ACM 8.2

Connection: TCPIP Connection

Issue

Prevents a TCPIP connection attempt from lasting more than two minutes.

ACM 8.2

GC Write Service

Feature

Adds support for a comma separated list to be used as the Area ID in queries against the Flowcal database for GC Writes. This allows multiple Areas to use the same ACM Server for GC Writes.

ACM 8.2

General

Issue

Corrects an issue that prevented items in the $Perf object from being validated and added from OPC clients.

ACM 8.2

Logging

Feature

Adds the assembly version number to the source column in the Log Viewer.

ACM 8.2

OPC Client

Issue

Standardizes the initialization of writeable Extended items to "Good" quality.

ACM 8.2

OPC Client

Issue

Modifies the OPC test client to allow for a value to be written to an item more than once, even if the value didn't change.

ACM 8.2

Protocols: Base Protocol

Feature

Adds the device detail tab fields as OPC Items.

ACM 8.2

Protocols: BSAP Protocol

Feature

Adds the ability for a user to separately configure whether Serial or Ethernet protocol is used on the primary and/or secondary connections.

ACM 8.2

Protocols: BSAP Protocol

Feature

Adds support for array items to meter configuration polling.

ACM 8.2

Protocols: BSAP Protocol

Feature

Adds a configuration item token number to each meter run.  This number will be used to replace a token in the items for the meter configuration reads and GC writes, so that a single Meter Configuration or Gas Chromatograph object can be used for multiple meter runs.

ACM 8.2

Protocols: BSAP Protocol

Issue

Adds support for user strings and user doubles to GC write.

ACM 8.2

Protocols: DF1 Protocol

Issue

In situations where two responses are in the buffer at the same time, the driver will move over the first packet and validate the second one as the response to process.

ACM 8.2

Protocols: DNP3 Protocol

Feature

Adds a rule option in the Meter Configuration object for yes/no fields and RelativeDensitySaturationCondition. Makes FactorFwv and FwvFactorUsed fields interchangeable. *Effect on published output: When a Meter Configuration object (the Advanced Configuration assigned to the Meter object) is used to publish meter configuration data, the fields below now use predefined constants for the "Constant" and "Rule" options.  For the CSV publisher, that means that these values will be published as the text strings "Yes"/"No" (or "Wet"/"Dry"/"AsDelivered" for RelativeDensitySaturationCondition) if translation is used, and as numeric codes if translation is not used.  For the XML publisher, all of the fields below will be now published within the <Common> node, rather than the <Extended> node as some of them were before: FlowingPressureEffectEnabled, Live Analysis, Live BTU, Live Gravity, Live Temperature, HasDefaultTemperature, UseRTD, FwvFactorUsed, FwvsFactorUsed, HasRTD, TemperatureCompensated, PressureCompensated, FactorFa, FactorFb, FactorFg, FactorFpv, FactorFr, FactorFt, FactorFwv, FactorY, RelativeDensitySaturationCondition

X

ACM 8.2

Protocols: DNP3 Protocol

Feature

Adds support for new objects, parameters, measurements, and units in Emerson FBx firmware release 02.04.01.09.

ACM 8.2

Protocols: DNP3 Protocol

Feature

Adds support for new objects, parameters, measurements, and units in Emerson FBx firmware release 02.05.01.10.

ACM 8.2

Protocols: DNP3 Protocol

Feature

Adds support for new objects, parameters, measurements, and units in Emerson FBx firmware release 02.07.00.80. *Effect on published output: Corrects viscosity unit name from pound-feet per second (wrong) to pounds mass per foot-second (right according to CFX5 documentation), changes DPCalibrationRangeHigh to match DPCalibrationLow, and fixes unit ID issue with ENUM16 and BIN* data types.

X

ACM 8.2

Protocols: DNP3 Protocol

Issue

Adds FBx to ACM unit mappings that were left out of previous updates. *Effect on published output: History fields may be published with new unit types.

X

ACM 8.2

Protocols: DNP3 Protocol

Issue

Converts new DNP3 FBx unit types for use in the ACM publishers.

ACM 8.2

Protocols: Flow Automation Protocol

Feature

Adds history collection support for the Flow Automation Williams Gas load. *Effect on published output: The CFX publisher will now show valid data for GC data in the meter configuration section where previously it was invalid.

X

ACM 8.2

Protocols: Flow Automation Protocol

Feature

Adds read and write item support for function types Plunger Lift (config and instantaneous) and Drip Control for Flow Automation devices with the Coastal Flow load.

ACM 8.2

Protocols: Flow Automation Protocol

Issue

Corrects a GC Write issue in the Williams Gas Load that could cause the GC Write to fail after reading partial GC items.

ACM 8.2

Protocols: FlowX Protocol

Feature

Adds a new command that allows for copying an existing tag file from a configured device.

ACM 8.2

Protocols: FlowX Protocol

Issue

Adds validation to the Flow-X History Map to prevent duplicate Field Identifiers from being used.

ACM 8.2

Protocols: Hex Repeater Protocol

Issue

Corrects an issue that prevented writes to device configuration items unless the ACM license has the 'history' feature enabled.

ACM 8.2

Protocols: Micro MP3 Protocol

Feature

Adds support for Dynamic Flow Computer's MicroMP3 Liquid Flow Computer using the Modbus/MicroMP3 protocol.  - MicroMP3 supports both the truck ticket mode and the full six meter flow computer mode.  - MicroMP3 provides the ability to retrieve and publish daily and monthly batch report records.  - MicroMP3 allows for time synchronization. *Effect on published output: This release adds support for Dynamic Flow Computer's MicroMP3 Liquid Flow Computer using the Modbus/MicroMP3 protocol.

X

ACM 8.2

Protocols: ROC Protocol

Feature

Adds more units for ROC meter configuration such as differential pressure units, uncorrected volume units to the CFX Output. *Effect on published output: For ROC meter configuration, more units (such as differential pressure units, uncorrected volume units) will be output.

X

ACM 8.2

Protocols: ROC Protocol

Feature

Adds a new option "Combine data from all segments into the same archive records" to combine a meter's data from different segments into the same record. *Effect on published output: If the new option "Combine data from all segments into the same archive records" is selected and the user has a meter mapped with fields in different segments, then the fields will be combined into the same record.

X

ACM 8.2

Protocols: ROC Protocol

Feature

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

ACM 8.2

Protocols: ROC Protocol

Feature

Adds the ability to set a ROC device date/time to any value required via new Extended OPC tag ClockSet.

ACM 8.2

Protocols: ROC Protocol

Issue

Corrects an issue where some history point mappings could lead to sporadic partial history records. *Effect on published output: This corrects an issue where some history point mappings can lead to sporadic partial history records.

X

ACM 8.2

Protocols: ROC Protocol

Issue

Corrects an issue where configuring a "First Collection Count" of 0 caused no records to be retrieved.  Instead, a limit of 0 is now treated as if no limit is defined and all available records will be collected. *Effect on published output: When the archive limit is set to zero, all records will be returned.

X

ACM 8.2

Protocols: ROC Protocol

Issue

Corrects an issue where external mapping with an EFM ID of UNKNOWN produced unexpected results. *Effect on published output: Corrects an issue where an external mapping with the ACM field identifier "Unknown" could cause incorrect results in published history records.

X

ACM 8.2

Protocols: Romet-Adem Protocol

Issue

Corrects an issue in referenced object text boxes that caused names to be truncated in the display.

ACM 8.2

Protocols: SCADAPack Protocol

Feature

Adds the ability to upload batch history records. *Effect on published output: Historical batch records can now be published.

X

ACM 8.2

Protocols: Teledyne CA Protocol

Feature

Adds the ability to retrieve a specific bit address and width from Analog, Greycode and Digital items.

ACM 8.2

Protocols: Totalflow Protocol

Feature

Adds 'TIMESTAMP' and 'TIMESTAMPUTC' modifiers for app.array.index items to provide date/time in local and UTC timestamp format.

ACM 8.2

Publishing

Feature

Adds non-configuration and DPTransducerRangeLow events for CFX7/CFX8. *Effect on published output: Some events that were not previously published as CFX events now will be.

X

ACM 8.2

Publishing

Feature

Provides an option to adjust the timestamp of gas quality records published through the PGAS XML output object. *Effect on published output: The timestamp of gas quality records will be published according to the PGAS XML setting.

X

ACM 8.2

Publishing

Feature

Adds the ability to use tokens in the form $$Fieldn$$ (where 'n' represents the one-based index of a field in a history record) in a path or file name of the CSV publisher. *Effect on published output: When the new token is used in a path or file name of the CSV publisher, the CSV output will be split into multiple files and/or folders according to the field value.

X

ACM 8.2

Publishing

Feature

Improves error messages generated by the PGAS XML publisher by providing more detail in the logged message.

ACM 8.2

Publishing

Issue

Adds Flow Time to the CFX8 batch records. *Effect on published output: Flow Time will now be included in CFX8 batch records.

X

ACM 8.2

Server Monitor

Feature

Adds the ability to save a custom database connection setting in the ACM Monitor.

ACM 8.2

Server Monitor

Feature

Adds the ability to run individual SQL scripts via the ACM Monitor Database Wizard.

ACM 8.2

Server Object Model

Issue

Modifies the client application to display the "Out of Sync" message on an open form if that object was modified during an import.

ACM 8.1.1

Alias Groups/Items

Issue

Corrects an issue causing the AliasName field in tblItems to be cleared out.  ACM will now only update the AliasName field in the tblItems if a non-null value comes in.

ACM 8.1.1

Archive Management

Issue

Modified Archive Management to allow Station Meters to be included in the results.

ACM 8.1.1

Client Application

Issue

Corrects the Server Monitor property grids to display updated values when the "Reset" button is clicked.

ACM 8.1.1

Client Application

Issue

Improved load time when switching between modes in the tree view.

ACM 8.1.1

Client Application

Issue

Modified the Reporting tab to prevent null values from being selected for dates and numeric fields.  Improved the error messages for the Publisher Filter Report.

ACM 8.1.1

Client Application

Issue

Prevents crash when adding Alias Group or View objects while security is enabled.

ACM 8.1.1

Client Application

Issue

Corrects an issue that prevented editing of the search criteria in the main ACM search bar.

ACM 8.1.1

Client Application

Issue

Corrects an issue that could cause unhandled exceptions in the Role form.

ACM 8.1.1

Configuration Database

Issue

Corrects a error that could prevent persistent data from loading due to conversion from the data storage format to the native format required by OPC items.

ACM 8.1.1

Configuration Database

Issue

Modified the tblItems table definition to make the ID column a BIGINT

ACM 8.1.1

Configuration Database

Issue

Prevents a device's item data from entering persistent storage after the device has been deleted.

ACM 8.1.1

Configuration Server

Issue

If the ConfigServer fails to load objects from database due to a missing stored procedure,  ACM will prompt to verify the ACM database is up to date.

ACM 8.1.1

General

Issue

Corrects for $Server.PctProcessMemory item having a negative number.

ACM 8.1.1

Importer/Exporter

Issue

Resolved a potential error when exporting from the Primary and Secondary views in the tree.

ACM 8.1.1

Logging

Issue

Corrects an issue that occasionally prevented a port's Queue Viewer from showing data.

ACM 8.1.1

Protocols: Base Protocol

Issue

Corrects an error that prevented some OPC client read requests from completing successfully. Requests to read 'from device' could use a truncated handle in the 64-bit version of ACM.

ACM 8.1.1

Protocols: Base Protocol

Issue

Corrects an issue causing the demand poll to be stuck on the primary connection.  This issue appeared if the primary was demanded while getting time outs and switched to secondary before demand was performed.

ACM 8.1.1

Protocols: Benchmark Protocol

Issue

Benchmark will send an ACK before interruption. Allow the low command items with different intervals to be added in the same request as interval 1 with medium priority except for the low command items with additional extensions.

ACM 8.1.1

Protocols: ControlLogix Protocol

Issue

Corrects an issue causing ACM to crash due to the driver attempting to process message responses that do not match the current message being validated.

ACM 8.1.1

Protocols: ControlLogix Protocol

Issue

Corrects an issue in the ControlLogix Time Sync function that showed an invalid error message in the logs.

ACM 8.1.1

Protocols: Enron Modbus Protocol

Issue

Adds a new GC option titled "Require a GC record to each periodic record." to enforce the history record output only when matching GC records are found. *Effect on published output: When this option is enabled no history will be output if the GC collection fails while collecting the same time stamped history records.

X

ACM 8.1.1

Protocols: Enron Modbus Protocol

Issue

Corrects an issue where the GC archive is not requested for a meter with an index greater than two, even when configured. *Effect on published output: The new DLL will allow GC to be output with Enron Modbus meters that have an index greater than two.

X

ACM 8.1.1

Protocols: Enron Modbus Protocol

Issue

Corrects an issue preventing a new advanced meter configuration from being applied after switching from an old object.

ACM 8.1.1

Protocols: Enron Modbus Protocol

Issue

Cleaned up the log messages when clearing additional GC records.

ACM 8.1.1

Protocols: FlowX Protocol

Issue

Corrects an issue in the Flow-X driver that prevented items with an interval specified from being polled.

ACM 8.1.1

Protocols: GE SRTP Protocol

Issue

Corrects an issue that caused boolean and bit registers from showing the correct value in some OPC client applications.

ACM 8.1.1

Protocols: Honeywell - Mercury Protocol

Issue

Corrects issue with certain Extended items that could cause ACM to become unresponsive when the item is deleted in the client application.

ACM 8.1.1

Protocols: Mercury Protocol

Issue

Corrects an issue that would cause the GC Write download to abort if a component value was missing from the input file. Added a new option to specify that only the first three gas quality components will be published or downloaded with a GC write, even if the RTU supports twenty-two components.

ACM 8.1.1

Protocols: Mercury Protocol

Issue

Corrects an issue that prevented New Mercury Archive Objects from showing references when executing "Get References to Object".

ACM 8.1.1

Protocols: Modbus Protocol

Issue

Corrects an issue that sometimes prevented the Advance Meter Configuration option from overriding the default value during publishing. *Effect on published output: If available, the Advanced Meter Config value will be published in place of the device value instead of adding the override as an additional field.

X

ACM 8.1.1

Protocols: Omni Modbus Protocol

Issue

Adds the ability for the OMNI 7000 to use external maps for Raw archives.

ACM 8.1.1

Protocols: Omni Modbus Protocol

Issue

Corrects an issue that caused the OMNI 7000 to loop infinitely when liquid meters could not be read due to incorrect register set settings.

ACM 8.1.1

Protocols: ROC Protocol

Feature

Changes the message received when K-Factor is not read from the Pulse Input Module from an Error to a Warning.

ACM 8.1.1

Protocols: ROC Protocol

Feature

Modified the ROC user form to obscure the device password if one is entered.

ACM 8.1.1

Protocols: ROC Protocol

Issue

Adds OPC tag modifiers "LastHourlyRecord/Station" and "LastDailyRecord/Station" for ROC 80x devices.

ACM 8.1.1

Protocols: ROC Protocol

Issue

Adds validation to verify that meters assigned to a device are still valid meters in ACM before polling.

ACM 8.1.1

Protocols: Romet-Adem Protocol

Issue

Corrects an issue with the new Honeywell Mercury protocol that could cause logging on to a Mercury Modem to fail. Corrects an issue with the new Honeywell Mercury protocol that caused the meter configuration upload to abort if the RTU returned an error response to the RD command. Corrects an issue with the new Honeywell Mercury protocol that caused AGA8 items to be attempted to be read even when the firmware version did not support them. Corrects an issue with the Romet-Adem protocol that could cause logging on to a Mercury Modem to fail.

ACM 8.1.1

Protocols: Romet-Adem Protocol

Issue

Corrects an issue that could cause the RE event command to fail on some Mercury devices.

ACM 8.1.1

Protocols: Romet-Adem Protocol

Issue

Corrects an issue that could cause audit records not to publish because of missing meter configuration record. *Effect on published output: All audit records will now be published.

X

ACM 8.1.1

Protocols: SCADAPack Protocol

Issue

Corrects an issue causing the Scadapack history command to loop indefinitely if Command 1 was returned "Not Ready" and the command retry count was not set to zero.

ACM 8.1.1

Protocols: Siemens S7 Protocol

Issue

Corrects an issue with the Integer item modifier to correctly assign a conical data type of Signed Integer (VT_I2).

ACM 8.1.1

Protocols: Siemens S7 Protocol

Issue

Corrects an issue with "4 byte" data type writes going out as L/H WORD order.  Corrects an issue where "Real" data types were returned as UI4 unsigned values.

ACM 8.1.1

Protocols: Totalflow Protocol

Issue

Corrects an issue caused by a split log period record missing its matching GC record. *Effect on published output: This update corrects an issue that prevented GC trend data from merging with periodic data when a split periodic record was found.

X

ACM 8.1.1

Protocols: Totalflow Protocol

Issue

Corrects the assignment of 'Live Temperature' in the meter characteristics of EFM published outputs for Totalflow devices. *Effect on published output: Correctly assign 'Live Temperature' in the meter characteristics of EFM published outputs for Totalflow devices.

X

ACM 8.1.1

Publishing

Issue

The alarm description (if present) will be included in the FLOWCAL Transaction Queue alarm record output 'string_value' column. *Effect on published output: The alarm description (if present) will be included in the FLOWCAL Transaction Queue alarm record output 'string_value' column.

X

ACM 8.1.1

Reports

Issue

Corrects an issue that prevented Throughput Reports from returning records.records can now be published.

X


ACM 9.0

Protocols: NGCTT Protocol

Issue

Corrects an issue that caused history polling to terminate when 10 04 bytes were returned from a device in the middle of polling.



ACM 9.0

Protocols: ROC Protocol

Feature

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


ACM 9.0

Protocols: ROC Protocol

Feature

Adds the ability to process ROC 800 Liquid meter data in the GC Write service.



ACM 9.0

Protocols: ROC Protocol

Feature

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


ACM 9.0

Protocols: ROC Protocol

Feature

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


ACM 9.0

Protocols: ROC Protocol

Feature

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


ACM 9.0

Protocols: ROC Protocol

Feature

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


ACM 9.0

Protocols: ROC Protocol

Feature

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


ACM 9.0

Protocols: ROC Protocol

Feature

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


ACM 9.0

Protocols: ROC Protocol

Issue

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


ACM 9.0

Protocols: ROC Protocol

Issue

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


ACM 9.0

Protocols: ROC Protocol

Issue

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.



ACM 9.0

Protocols: Romet-Adem Protocol

Issue

Corrects an issue that could cause incorrect meter configuration values when using the RD command to read register values after a timeout occurs.



ACM 9.0

Protocols: SCADAPack Protocol

Issue

Corrects an issue that caused GC Write to fail for gas coriolis meter runs on controllers running RealFlo 6.95 or greater.



ACM 9.0

Protocols: SCADAPack Protocol

Issue

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


ACM 9.0

Protocols: SCADAPack Protocol

Issue

Modifies the driver to use the correct registers for reading and writing heating value and gas density value.



ACM 9.0

Protocols: Scancom Protocol

Issue

Corrects an issue that prevented "Trusted Log In" from being enabled once it had been disabled.



ACM 9.0

Protocols: Scancom Protocol

Issue

Changes the "Read Only" state on FRDM items to reflect Barton documentation.



ACM 9.0

Protocols: Scancom Protocol

Issue

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.



ACM 9.0

Protocols: Teledyne CA Protocol

Issue

Corrects an issue in the driver that could prevent items of higher cards and points from being polled, which resulted in invalid item values.



ACM 9.0

Protocols: Totalflow Protocol

Issue

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


ACM 9.0

Protocols: Totalflow Protocol

Issue

Adds the Trend Record Type to the trends tab form view. It previously only existed in the Property Grid view.



ACM 9.0

Protocols: Weatherford Protocol

Feature

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.



ACM 9.0

Protocols: Weatherford Protocol

Feature

Optimizes the performance for OPC synchronous read from device requests.



ACM 9.0

Protocols: Weatherford Protocol

Issue

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.



ACM 9.0

Publishing

Feature

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


ACM 9.0

Publishing

Feature

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


ACM 9.0

Publishing

Issue

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


ACM 9.0

Publishing

Issue

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


ACM 9.0

Publishing

Issue

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


ACM 9.0

Reports

Issue

Optimizes the performance of retrieving and displaying report data.



ACM 9.0

Reports

Issue

Changes the heading of the 'Date' column in the Configuration Change Reports to 'Date (UTC)'.



ACM 9.0

Reports

Issue

Corrects an issue that could cause a scheduled report to run at least once a minute  - ignoring the "sync time".



ACM 9.0

Server Monitor

Issue

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.



ACM 9.0

Server Monitor

Issue

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.



ACM 8.2.1

ACM Server

Issue

Corrects a property load error that can occur when processes ACM relies upon aren't available.



ACM 8.2.1

Client Application

Issue

Corrects an issue that prevented using the "Edit Multiple" feature to edit the Protocol Options on multiple New Honeywell Mercury devices.



ACM 8.2.1

Client Application

Issue

Removes erroneous log messages that were displayed when writing to an item with "ReadUserOnly" disabled.



ACM 8.2.1

Client Application

Issue

Corrects the tool tip message for the Details tab User01 property.



ACM 8.2.1

Client Application

Issue

Corrects the checkbox list initial focus issue on multiple tabbed pages



ACM 8.2.1

Client Application

Issue

The date-time parameters in reports will now correctly display the saved date and time when editing a scheduled report.



ACM 8.2.1

Configuration Database

Issue

Improves performance of the Archive Management/Gap Detection Process.



ACM 8.2.1

Configuration Database

Issue

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.



ACM 8.2.1

Configuration Database

Issue

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.



ACM 8.2.1

Configuration Database

Issue

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.



ACM 8.2.1

Configuration Database

Issue

Adds a table to the ACM Database for keeping track of database version history.



ACM 8.2.1

Configuration Database

Issue

Provides a script to create all expected but missing indexes on ACM tables.



ACM 8.2.1

Configuration Database

Issue

Modifies the stored procedure that is responsible for deleting archive records to make it more efficient.



ACM 8.2.1

Connection: Base Connection

Issue

Increases the Connection Settings Reply Timeout maximum value from two minutes to three minutes.



ACM 8.2.1

Connection: Serial Connection

Issue

Corrects an issue that prevented saving configuration changes in Serial Ports.



ACM 8.2.1

Connection: TCP Listen Connection

Issue

Corrects a crash in connection modules that occurred during poll interruption.



ACM 8.2.1

GC Write Service

Issue

Corrects an issue to prevent GC Write Requests from getting stuck after 32,767 retries when using "slow mode".



ACM 8.2.1

General

Issue

Corrects the OPC item ->Server/CfgCount value update when multiple ACMConfig Clients are connected.



ACM 8.2.1

General

Issue

Corrects an issue that allowed Async Writes from an OPC client when they should have been blocked.



ACM 8.2.1

General

Issue

Corrects an issue that could cause the initial OPC refresh to fail when used by a managed language client.



ACM 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.



ACM 8.2.1

Issue

Configuration Database

Modifies the meter historization process to only keep unique meter FieldData



ACM 8.2.1

Issue

Protocols: Honeywell - Mercury Protocol

Corrects an issue that resulted in response packet noise byte characters being included in the CRC calculation.



ACM 8.2.1

Issue

Protocols: Honeywell - Mercury Protocol

Corrects an issue that could result in a failed EFM upload completing with a Successful Poll result.



ACM 8.2.1

Logging

Issue

Corrects a crash in asiLOGSERVER service.



ACM 8.2.1

Protocols: Benchmark Protocol

Issue

Corrects an issue that caused asiData to hang when uploading history from a Benchmark device if the server did not have DST setup.



ACM 8.2.1

Protocols: ControlLogix Protocol

Issue

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.



ACM 8.2.1

Protocols: ControlLogix Protocol

Issue

Corrects an issue where invalid messages present in the buffer could cause validation logic to hang up the polling engine.



ACM 8.2.1

Protocols: ControlLogix Protocol

Issue

Lowers the Timeout Multiplier for CIP connections to help avoid running out of connection resources during rapid polling schedules.



ACM 8.2.1

Protocols: ControlLogix Protocol

Issue

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.



ACM 8.2.1

Protocols: Enron Modbus Protocol

Issue

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.



ACM 8.2.1

Protocols: Flow Automation Protocol

Issue

Modifies the driver to output the correct meter configuration record for Coastal Flow device type.



ACM 8.2.1

Protocols: FlowX Protocol

Issue

Provides missing device destination IP and Port as part of requested message to meet possible firewall rules.



ACM 8.2.1

Protocols: FlowX Protocol

Issue

Corrects an issue that could prevent history collection when not using an alarm map.



ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

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.



ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

Modifies the driver to correctly handle an error returned during an ACK or NAK request so that a poll cycle retry will be triggered.



ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

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


ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

Corrects an issue that prevented messages from being consolidated after items were removed.



ACM 8.2.1

Protocols: Honeywell - Mercury Protocol

Issue

Corrects an issue when writing TS, GCWrite and NextCallinSchedule that prevented the write message from using the configured access code.



ACM 8.2.1

Protocols: Modbus Protocol

Issue

Corrects an error that prevented using the modbus "block read" item.



ACM 8.2.1

Protocols: ROC Protocol

Issue

Corrects a logger warning message which resulted when some ROC configurations published meter configuration information.



ACM 8.2.1

Protocols: Scancom Protocol

Issue

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


ACM 8.2.1

Protocols: Scancom Protocol

Issue

Corrects an issue with Demand GC message not correctly building for Adept 4.0 message format.



ACM 8.2.1

Protocols: Scancom Protocol

Issue

Corrects OPC validation of hardware items so that they will will not be added if parameter and slot are not entered correctly.



ACM 8.2.1

Protocols: Scancom Protocol

Issue

Modifies the driver so that items not updated due to an error with an item id in a read are now marked as invalid.



ACM 8.2.1

Protocols: Siemens S7 Protocol

Issue

Adds configuration settings to directly control TSAP values on S7-200 model connections.



ACM 8.2.1

Protocols: Totalflow Protocol

Issue

Corrects the log messages displayed when executing the "Retrieve Meter config during next history poll" and "Reset History (LogPeriod/Daily/Event) Pointer" commands.



ACM 8.2.1

Protocols: Totalflow Protocol

Issue

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


ACM 8.2.1

Publishing

Issue

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