| Expand | ||
|---|---|---|
| ||
|
System Requirements and Updates
With this release, ACM requires .Net Framework 4.7.2.
ACM 8.0 also has the following new Operating System requirements:
- Microsoft Windows:
- 7 SP1, 8.1, and 10 (Anniversary Update or later)
- Microsoft Windows Server:
- 2008 R2 SP1, 2012, 2012 R2, 2016, and 2019
...
- Components from ACM 8.0 cannot be combined with components from ACM 7.1
- If upgrading from a 32-bit version of ACM 7.1 to the 64-bit version of ACM 8.0, ACM 7.1 must first be uninstalled.
- If upgrading from a beta version of the 64-bit ACM 7.1, it must first be uninstalled.
- For installations that make use of Safe Mode operation, ACM 8.0 uses the "Microsoft ACE OLEDB 12.0" database driver for the safe mode database. The older "Microsoft Jet OLEDB 4.0" driver is no longer supported. The ACE OLEDB 12.0 driver can be downloaded from Microsoft here.
- It is always a good idea to back up your ACM configuration database before updating. This update makes changes to the database and if for some reason the update cannot complete successfully, a backup may be required to revert to your previous version of ACM. Instructions are found in the ACM User Guide under Maintenance –> Backing up the SQL Database
...
- Dresser Micro Corrector Protocol
- Supports Dresser Micro Corrector devices with firmware version 1.99 and earlier.
- Supported Features
- Device Configuration
- OPC Items
- New Mercury Protocol (listed as Honeywell/Mercury (NEW*) in ACM)
- Supported Devices
- Honeywell Mercury Instruments EC 350 and ERX 350
- Older Mercury device types
- Supported Features
- Device Configuration
Note title Important information regarding the existing Honeywell-Mercury Protocol - Mercury devices already configured in ACM will continue to work using the existing protocol driver, but will need to be converted to the new protocol driver by the end of year 2020.
- 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.
Note title Important information regarding the initial Beta version of the new Honeywell-Mercury Protocol EC 350 devices created with the initial Beta release of the New Honeywell-Mercury Protocol driver may have the incorrect device type in this updated version. Please verify the configured device type for each EC 350 device already created in ACM.
- Supported Devices
- ROMET-AdEM Protocol
- Supports AdEM-PTZ devices
- Supported Features
- Device ConfigurationOPC Items
- Siemens S7 Protocol
- Supports 300, 400, 1200 and 1500 model devices .
- Supported Features
- Device Configuration
- OPC Items
- Teledyne CA Protocol
...
- Added an option to the Dashboard "View" drop-down to select no active view, which cancels item subscriptions.
- Added an option to the User Preferences to use the default datetime format or to establish a custom datetime format. All datetime tags shown within the client for the logged in user will follow this setting. This does not impact the datetime format on reports.
- Added a button to the Log Viewer to mimic the behavior of the keyboard short-cut Ctrl+M in order to add a mark to the log.
...
- Added a new option to control how often ACM updates values for items subscribed through the custom Item Server interface. Items can now be updated only when their value or quality changes, or they can be updated on every poll. This new option was added to the Server tab of the $Server object and is labeled "Item Update Frequency". The default is to only update when value or quality changes.
- Added the sub-option "Shutdown even when auto-poll enabled" under "Auto-Shutdown" to the $Server Object form. This was previously only visible in the property grid view.
ACM Server Monitor
- Added support in the Server Monitor for accounts with blank passwords.
- Added more information to the Server Information form regarding platform version. This is accessed via the "Status" tab of ACM Monitor.
...
- Increased the number of DNP3 FBx Station Meters to 24 and made a modification to read history using the new history commands.
- Added the ability to read DNP3 Objects by group and index to avoid a large retrieval of data for a small number of items. This is available via an Item Modifier. View the User Guide for more information regarding DNP3 Item Modifiers.
- Added the option to use the lagging/end timestamp for history in the DNP3 FBx protocol. This new option on the Archive Collection tab is labeled "Use end timestamp for history" and is not selected by default.
- Provided the capability to read user defined objects and parameters in the DNP3 FBx protocol.
- Added GC writes to the DNP3 FBx extension. Note: The items for the GC write configured in the Gas Chromatograph object must be FBx object parameters.
- Added the Class Upload Fields to the the DNP3 and DNP3 FBx forms as they both support class uploads. These fields are found on the Device tab.
- Added an option to initialize Class 1-3 items with a Class 0 poll after communication failure in the DNP3 protocol. This option is on the Device tab and labeled "Initialize class 1-3 after comm failure" and is not selected by default..
...
- Added an option to the Eagle protocol to retrieve history during a call-in to eliminate the need for a second connection to be created for history collection. This new option is on the Device tab and labeled "Retrieve history during call-in" and is not selected by default..
- Provided the ability for the "Retrieve History" and "Time Sync" OPC items to accept a -1 value.
Flow-X Protocol
- Added the ability to schedule the retrieval of new reports in the Flow-X protocol. This feature can be configured on the Archive Collection tab of the Flow-X device setup.
Modified the publisher to automatically map the Flow-X protocol Differential Pressure and Pulses to the correct fields in the CFX file based on the meter type.
Note title Effect on Published Output The Gas History Record will use the Pulse field data for Turbine meters and the DP field data for Orifice meters.
...
Added an option to the OMNI protocol to prevent DP and Pulses conflicts by automatically mapping the fields to the CFX file based on the meter type. This new option is on the Archive Collection tab and labeled "Prevent DP and Pulse value conflicts" and only necessary if the OMNI archive is configured to contain both the DP and Pulse registers. This option is not selected by default.
Note title Effect on Published Output A new option to 'Prevent DP and Pulse conflicts' will change the EFM identifier of either the DP field or the Pulse field in periodic records. Each field retains its name (for database and CSV publishers), but only one has it's EFM identifier. This prevents two fields from going to the same shared output of CFX files when a custom map is used with both DP and Pulse fields in it.
Added support for 32 OMNI products and included more registers in support of Revision 22 of the OMNI protocol.
Note title Effect on Published Output Up to 32 products can be assigned and published.
...
- Modified all port types to enforce the maximum allowed Transmit Delay of 60 seconds to prevent a very long delay period from blocking polling on the port.
- Modified ACM to prevent high CPU usage when multiple devices using the TCPPool port type come due to poll at the same time using the same phone number.
- Added a check to Serial, TCP/IP, TCPPool and TCPListen port types to monitor transmit delay time and ensure it is limited to the 60 second maximum setting.
- Fixed an issue with the Demand item getting stuck 'On' when demanding a poll on the secondary connection while a primary connection test is in progress.
ACM Database
- Corrected an issue in the Bulk Manager that caused staging tables to grow continuously with unprocessed records after timeouts.
...
Corrected an issue that caused the publisher to skip records when a column was not defined in a database.
Note title Effect on Published Output More records will be output.
Added BTU output to the FLOWCAL Online Transaction Queue.
Note title Effect on Published Output Added BTU output to the FLOWCAL Online Transaction Queue.
Corrected the PGAS Xml publisher so that volume records will only be created when "Populate Volume Record" is selected.
Note title Effect on Published Output Meter characteristic records will no longer be created alone. They will only be included when volume and/or quality records are added to the file.
- Corrected an issue when executing the "Refresh Published Reports" command for a publisher with no filter applied.
ACM Reporting
- Modified the Reporting tab to keep the same report selected when clicking back and forth between the main ACM tabs.
- Disabled the "interval" option for the weekday schedule in Scheduled reports. Also corrected the calculation for the next run date for the weekday schedule in order to properly email daily reports.
ACM Server
- Fixed a problem that caused asiDATA to send back an unscaled value for an item with scaling flags when an OPC client did a synchronous read request before ACM had polled the item.
- Modified the Server Information form to detect versions of .NET higher than .NET 4.0.
ACM Server Object
- Modified the history deletion process to keep the correct number of periodic records and to improve the speed at which records are deleted.
All Protocols
- Corrected an issue that caused messages to be sent with the wrong priority when "Poll items immediately when activated" is enabled.
Benchmark Protocol
- Corrected an issue causing the Benchmark Protocol to return the error message "Field item data is out of range".
BSAP Protocol
- Corrected an issue with certain BSAP items that caused the Status tab in the device configuration to freeze.
DF1 Protocol
- Corrected an issue in the DF1 protocol that prevented the connection from returning to the primary connection after a fail-over to the secondary connection.
- Fixed the high message count for Gas Quality write by combining write values into as few messages as possible.
- Fixed history collection, event collection and time sync for NGCTT devices.
...
- Corrected an issue preventing DNP3 from working with the Archive Manager due to the internal property names used for meter objects not following the standard naming convention for ACM.
- Corrected an issue in the DNP3 FBx protocol that caused uploads to go permanently into an unknown state after encountering a "too many open files" error.
- Corrected an issue that allowed multiple copies of the same object to be added to a poll in the DNP3 protocol.
- Corrected an issue with certain DNP3 FBx items that caused the Status tab in the device configuration to freeze.
Flow Automation Protocol
Corrected the meter configuration data for the Auto-Adjust meter in the Flow Automation native protocol.
Note title Effect on Published Output Auto-Adjust meters are now identified as a turbine meter type. The value that was used as the K Factor is now identified as the pipe diameter.
- Modified the Flow Automation protocol to compare daily records with previous records using the date and contract hour so that new records aren't erroneously ignored.
...