ACM 8.1 Release - July 2020

 Table of Contents

New System Requirements

Beginning July 2020, ACM will only support Microsoft operating systems and servers that are also still supported by Microsoft.

Installation Notes

If you have a support agreement, the new ACM version can be downloaded by using the monthly login credentials received from your sales representative.  For more details, please contact us today.   

Components from ACM 8 cannot be combined with components from ACM 7.

OMNI 7000 Beta

ACM 8.1 includes a Beta release of the OMNI 7000 driver.  This driver:

ABB Totalflow Toolkit Version 3.12

The Totalflow driver in ACM 8.1 has been updated to use the latest functionality available in the 3.12 version of the ABB toolkit.  The driver can now be used with RMC models that support many more meters than previous models.  New functionality includes:

  • Added support for Coriolis and Ultrasonic meter types.

    Effect on Published Output

    • Published output will include the calc method in the Meter Configuration for Coriolis and Ultrasonic meter types.
    • Published output will include the Product Index in both the history record and the liquid product record.

      Added support for Coriolis and Ultrasonic meter types.

  • Added the ability for each ACM meter to collect from a specific remote device meter by configuring a specific meter index. This is in support of the ABB RMC-100.
  • Gas Analysis data can be retrieved from periodic records in enhanced meters.

    Effect on Published Output

    Gas analysis values can be published from the “extra data” associated with each log period or daily record in enhanced meters.

  • Standardized the gas analysis location and format.

    Effect on Published Output

    The history record output format has changed to standardize the location, order and content of the gas analysis fields. When configured to be included in the output, all gas analysis fields will be published. Fields without data will have an empty or 'null' value in the output record.

Other News

ACM Roadmap

  • AUTOSOL has a few exciting items in the works for 2021!
    • OPC-UA
    • Dynamic Flow Computers Micro MP3 Support
    • FLOWCAL Liquid Support
    • MQTT Publishing (Now available for Beta testing. Contact your AUTOSOL Sales Representative for more information.)
  • Beginning June 2021, ACM 7.1 Build 306 and earlier will no longer receive new updates.  Please contact support to assist you in upgrading to ACM 8 to make sure you have access to the latest features!

Important reminder regarding the Legacy Honeywell Mercury Protocol

  • Mercury devices already configured in ACM will continue to work using the legacy protocol driver, but updates will no longer be available for it after January 2021.  
  • AUTOSOL will provide assistance and a method for converting existing devices to the new protocol driver.  Contact your AUTOSOL Sales Representative or AUTOSOL Customer Support when ready.
  • AUTOSOL suggests that testing is done with the new protocol driver using devices in your system to ensure correct operation.

Features added in ACM

ACM Client General

  • Added the ability to enter multiple letters in the Multiple Objects selection box in order to more easily filter to and select the desired item.

ACM OPC Items

  • Added a "LicenseExpiration" OPC item to display the date and time at which a temporary ACM license will expire.  If the license is temporary and active, the item will display the expiration date and time and have a “Good” quality. If the license is temporary and expired, the item will display the expiration date and time and have a “Bad” quality. If the license is not temporary, the item will show 12:00:00 AM with no date and the item's quality will be “Bad”.

ACM GC Write Service

  • Modified the service to allow CSV files created for the GC Write File Service to have empty fields when a component has no value. An empty field will not be used as a value.

ACM Publishing

  • Added mapping for SP Transducer Range High to SP_HIGH_RANGE in the PGASXML publisher.

    Effect on Published Output

    When an EFM record contains SP Transducer Range High, SP_HIGH_RANGE is assigned and present in the output file.

  • Modified the PGASXML history type to convert values that are in an energy unit other than MMBTU, DTH or GJ to DTH.

    Effect on Published Output

    When an unsupported energy unit is submitted with a PGAS record, the value and unit will be converted to DTH.

ACM Server

  • Added message logging to show time spent during ACM startup.

DNP3/DNP3 FBx Protocol

  • Increased the number of station meters from 24 to 72.
  • Added new objects, parameters, measurement types, and units in support of version 02.03.01.04 (also referenced as 2.3.1.4).
  • Added the options to publish unmapped events and/or alarms to all meters.

 Flow-X Protocol

  • Added Time Synchronization.
  • Modified the driver to automatically collect tags when a command is executed if tag collection has never been performed.

Honeywell/Mercury Protocol (*New)

  • Implemented support for the Pulse Accumulator Meter Run 2.

    Effect on Published Output

    Published data may contain EFM records for Meter Run 2 for a Pulse Accumulator.

  • Implemented configurable history points.
  • Added logging to output a message each time an audit record is published.
  • Created a Station Wizard.
  • Added an option to publish the K-Factor units in “Pulses per Cubic Meter” instead of “Pulses per Cubic Foot” when the device is using cubic meters.

    Effect on Published Output

    If this option is selected, K-Factor units will not be converted to pulses per cubic feet when the device is using cubic meters.

ROC Protocol

  • Added variables Octane, Nonane and Decane to the ROC800L Internal Map.

    Effect on Published Output

    Octane, Nonane and Decane fields will be published for ROC devices.

Teledyne CA Protocol

  • Added validation to the Greycode conversion.

Issues Corrected in ACM

ACM Client General

  • Corrected an issue that prevented multi-editor filters from opening in ACM Configuration when the Server Data Path had been changed in ACM Monitor.
  • Corrected an issue where an erroneous data type could cause ACM to crash.

ACM Publishing

  • Corrected an issue that caused duplicate records to be added to the EFM Database. Instead of adding new meter records, all existing meter records will be updated if one or more matching meter records are found.

ACM Server

  • Improved the error message logged when an item with an incomplete name is added by an OPC client.
  • Corrected an issue that caused the Sinewave item to stop updating after ACM had been running for an extended period of time.
  • Improved the Archive Record deletion process to reduce the likelihood of timeouts.
  • Modified OPC item updates to use the timestamp from a remote device if the device is capable of sending a timestamp with the value.

ACM Server Monitor

  • Fixed an issue that prevented the display of Meter Resolution Mode options in the Gas Analysis Write File Service section of ACM Monitor properties.

BSAP Protocol

  • Corrected an issue that caused a “retry” message to be rejected by a device after a communication time-out.

ControlLogix

  • Corrected an issue that caused user-defined tag structures to report invalid member names resulting in those tags being excluded from tag discovery.

DF1 Protocol

  • Corrected logging for extended error messages on ethernet devices.
  • Corrected an issue with bit offsets causing a 1 to be returned instead of VARIANT_TRUE (-1).

    Effect on Published Output

    May affect published output if the previous output expected "1" or had a conversion in place to change to -1.

DNP3/DNP3 FBx Protocol

  • Corrected issues with regards to read after write verification, octet string writes, and control block select-operate writes.
  • Corrected an issue with processing upload record sequence numbers.

Flow Automation Protocol

  • Corrected an issue that caused history collection to fail due to an abnormal code returned when processing EFM configuration message response.

Flow-X Protocol

  • Corrected an issue that caused non-configured station meter data to be published.

    Effect on Published Output

    Non-configured station meter data will no longer be published.

Honeywell Mercury Protocol (*New)

  • Corrected an issue that caused time outs during Continuous Scans by preventing a Demand poll from occurring when triggered during cry-outs.
  • Corrected an issue that caused an incorrect message sequence to be sent out during call-in on a messenger modem.
  • Corrected an issue that caused the EFM upload to stop before it was complete if the last audit record in the upload resulted in a timestamp gap.
  • Corrected an issue that caused incorrect values to be published for Audit Trail volume units for non-350 series devices.

    Effect on Published Output

    Audit record volume units for non-350 series Mercury devices will now have correct values.

  • Corrected an issue that caused EFM history records to always be published with a value of 60 for the $$Record.Period$$ field.

    Effect on Published Output

    EFM history records are now published with the correct value in the $$Record.Period$$ field.

  • Corrected an issue that caused the LogTrigger column to be missing from a CSV Audit Report.

    Effect on Published Output

    The CSV audit report will contain the LogTrigger column by default. This may add an additional column to the CSV report.

  • Modified the contents of the LogTrigger column in a CSV Audit Report to contain the entire T&A value.

    Effect on Published Output

    The LogTrigger column in the CSV audit report will now contain the entire T&A field value.

  • Corrected an issue that caused some items to have an incorrect data type which could result in invalid values or statuses.
  • Corrected an issue that could cause non-time triggered audit records to be published even when the ACM device object was not configured to do so.

    Effect on Published Output

    Non time-triggered audit records will only be published if the ACM device object is configured to do so.

  • Corrected an issue that could cause too many audit configuration registers to be polled.
  • Corrected an issue that prevented an item's unit value from being published in the audit record if the item's units could not be resolved.

    Effect on Published Output

    Item unit values are now published for all items in the audit record, including the items that do not have an associated unit. This may add additional columns to a CSV report.

  • Corrected an issue that caused response packets of audit records with fewer than four item fields to be processed as an error response.
  • Corrected an issue that caused history upload to continue despite a failure to read audit configuration.
  • Known issue: Right-clicking to find references for an object referenced by a new Honeywell Mercury device object may return a message that no objects were found.

Modbus Protocol

Enron Modbus Protocol

  • Corrected an issue in the history collection that caused the wrong index to be used when using a Push Down Archive with a single record.
  • Corrected an issue that caused the first record collected to be index 0 when using the "Read from address" record range type. Instead, the current max address will be requested from the device before history collection.

OMNI Modbus Protocol

  • Corrected an issue that caused audit records with invalid timestamps to be published. Instead an error message will be logged.

    Effect on Published Output

    Audit records with invalid timestamps will no longer be published.

Scanner 1150 Protocol

  • Corrected the tool tip text for the "Retrieval Batch Size" field on the Modbus Scanner 1150 Archive Collection tab.

ROC Protocol

  • Corrected an issue causing extended protocol items such as “MoveHourly” and “RetrieveHistory” to indicate a bad or failed status after a write from an OPC client.
  • Corrected a bug that did not correctly identify a meter factor change event in a ROC 80x when the meter factor was in manual mode.
  • Corrected an issue returning a "***Requested too many events***" message when the event or alarm archive wraps around to the top.

    Effect on Published Output

    Events and alarms that were not being published due to this issue will now be published.

  • Corrected batch record processing to map the batch record to the correct meter configured in the external map when the external map is applied.

    Effect on Published Output

    The record will be output as the correct meter.

ROMET-AdEM

  • Corrected an issue that caused EFM history records to always be published with a value of 60 for the $$Record.Period$$ field.

    Effect on Published Output

    EFM history records are now published with the correct value in the $$Record.Period$$ field.

  • Corrected an issue that prevented the LogTrigger column from appearing on a CSV Audit Report.

    Effect on Published Output

    The CSV audit report will contain the LogTrigger column by default. This may add an additional column to the CSV report.

  • Modified the contents of the LogTrigger column in a CSV Audit Report to contain the entire T&A value.

    Effect on Published Output

    The LogTrigger column in the CSV audit report will now contain the entire T&A field value.

  • Corrected an issue that could cause non-time triggered audit records to be published even when the ACM device object was not configured to do so.

    Effect on Published Output

    Non time-triggered audit records will only be published if the ACM device object is configured to do so.

  • Corrected an issue that caused history upload to continue despite a failure to read audit configuration.
  • Corrected an issue that prevented the K-Factor value from being published.

    Effect on Published Output

    Non time-triggered audit records will only be published if the ACM device object is configured to do so.

Siemens S7 Protocol

  • Resolved an issue with OPC item Read/Write access showing only Writable and not Readable.

Totalflow Protocol

  • Modified the driver to stop history collection if it failed to retrieve meter configuration data unless it was successfully retrieved in a previous history collection.
  • Modified the initial OPC quality of “MoveEvent” to be “Good” to match the other "Move" items.
  • Corrected an issue that caused the "Request 3 days of history when 2 days history is needed" option to be ignored.