...
Release | Category | Type | Text | Affects Published Output | Addresses Security Vulnerability | |
|---|---|---|---|---|---|---|
| 9.1.2 | Alias Groups/Items | Issue | Corrects an issue that caused items within an alias group to be internally advised and ready for MQTT publishing by a copied device object, even when the alias group did not have MQTT publishing enabled. | |||
| 9.1.2 | API | Issue | 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.2 | asiDATA | Issue | Corrects an error that could occur while saving objects if asiData was disconnected from the SQL Server when using the SQL Driver MSOLEDBSQL version 18.6 or later. The error messages in ACM addressed by this fix include: "Could not find prepared statement with handle #" and "Procedure {procedurename} has too many arguments specified". | |||
| 9.1.2 | asiDATA | Issue | Corrects an issue that caused an invalid timestamp to occur on Leap Day. | |||
| 9.1.2 | Base Connection | Issue | Corrects the failure retry count of polls that occur after a priority interruption. | |||
| 9.1.2 | BSAP Protocol | Issue | Corrects an issue that caused BSAP Devices to fail to retrieve history over ethernet connections. | |||
| 9.1.2 | Bulk Manager | Issue | Changes the Bulk Manager so that a file that failed to import due to the process being selected as the "DEADLOCK victim" will stay in the import folder. | |||
| 9.1.2 | Bulk Manager | Issue | Improves the log messages to contain more details if a SQL failure occurs. | |||
| 9.1.2 | Client Application | Issue | Changes the labels in the Publisher CSV from "Publish Report Records" to "Publish All Report Records" and "Publish Prove Report Records" to "Publish Prove Records". | |||
| 9.1.2 | Client Application | Issue | Restores the User Preference Activate Alias Tags on Status Tab "Only when Alias Group tags are active" option. | |||
| 9.1.2 | Client Application | Issue | Removes the unused 'Alarm Service' fields from the ACM Connect to Server Options. | |||
| 9.1.2 | Client Application | Issue | Increases the character limit of the "Provider String" field to 512 characters for the EFMDB and DB output types. | |||
| 9.1.2 | Client Application | Issue | Changes the default button on the "Delete Objects" dialog to "Cancel". | |||
| 9.1.2 | Client Application | Issue | Prevents spaces from being saved at the beginning or end of the Connect String field. | |||
| 9.1.2 | Client Application | Issue | Corrects sorting for datetime columns in the Dashboard. | |||
| 9.1.2 | Client Application | Issue | Prevents the Config Client from disconnecting from the server when using special characters in the search tool. | |||
| 9.1.2 | Client Application | Issue | Corrects an issue that could leave items advised and polling when switching between different alias groups on the Status tab of a device configuration form. | |||
| 9.1.2 | Client Application | Issue | Corrects an issue that caused the search to only find matching objects if those objects had a description. | |||
| 9.1.2 | Client Application | Issue | Corrects an issue that caused the search functionality to fail to find matches when there was a leading or trailing space in the search criteria. | |||
| 9.1.2 | Configuration Database | Issue | Updates the asi_spFrequentalarmandEventReport stored procedure to use the alarmLimitEvent parameter. | |||
| 9.1.2 | Configuration Database | Issue | Adds the table 'EdgeEFMConfigurationErrors' to the ACM database to record errors that may occur when publishing EFM data from the Edge. These errors will be visible in the 'Error Log Report Last X Days' report. | |||
| 9.1.2 | Configuration Database | Issue | Updates variables in two stored procedures, asi_spResetPublisherPosition_Filter and asi_spResetPublisherPosition, from INT to BIGINT to allow for very large archive sequence IDs. | |||
| 9.1.2 | Configuration Database | Issue | Modifies the "Publish a Device" command on the Publisher Command tab to publish all records, regardless of filter settings. Previously if the filter was for meters only, it would log "No records published for ObjectId = ### as it is not contained in the filter". This is a database update to the asi_spInsertPublishObjects4 stored procedure. *Effect on published output: When using the "Publish a Device" command from a publisher, all records will be published for that device regardless of filter settings. | X | ||
| 9.1.2 | ControlLogix Protocol | Issue | Corrects an issue that prevented the LastPollSuccessTime from updating correctly due to CIP Forward Open errors. | X|||
| 9.1.2 | DNP3 Protocol | Issue | Modifies the Move and Reset commands for alarm and event pointers so that they will execute as long as any meter is assigned. | |||
| 9.1.2 | DNP3 Protocol | Issue | Corrects the DNP3 meter type and calculation method mapping. Previously 'AGA3-2013' was published as 'AGA3-1992' and 'API 12.2 Volumetric' was published as 'Linear Mass'. Meter Types 'Ultrasonic' and 'Positive Displacement' were previously empty in published output. *Effect on published output: The correct calculation method and meter type will now be published. | X | ||
| 9.1.2 | DNP3 Protocol | Issue | Prevents an OPC Client from activating DNP3 internal items. | X|||
| 9.1.2 | DNP3 Protocol | Issue | Corrects the Gain/Offset scaling in the DNP3 FBx protocol. *Effect on published output: When set in the Archive Field Configuration, the published raw values will be scaled according to the Gain/Offset Scaling formula ItemName{SG:Gain:Offset}. | X | ||
| 9.1.2 | ExportMDB | Issue | Prevents ACM from replacing an existing Access database backup file with an empty one if asiData cannot connect to SQL Server. | |||
| 9.1.2 | GE SRTP Protocol | Issue | Extends the write message to include more than one item write in the same protocol message. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Corrects an issue that could cause multiple items to be associated with an RD message when the server was starting. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Corrects an issue that caused a Call-in message to be ignored if a low priority write was currently queued. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Corrects an issue that caused items that were reported as invalid by the RTU to be added back to poll messages. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Corrects an issue that prevented an item write from being sent to device if the write happened during an active poll session. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Corrects an issue that could prevent the driver from sending the log on sequence to the RTU if the last poll cycle ended in comm failure. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Corrects an issue that caused an incorrect leading/trailing timestamp indicator to be published for Mini-AT, Mini-Max, AccuTest and TurboCorrector devices. *Effect on published output: The correct leading/trailing timestamp indicator will be published. | X | ||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Decodes G items (1600-1699) for the Mercury EC350 series. *Effect on published output: The correct value for G items will be published. | X | ||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Modifies the 'First Collection Limit' so that the most recent alarm and event Archive records are published instead of the oldest. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Corrects an issue that caused all alarms in the alarm buffer of a Mini-AT to be published on every history upload. *Effect on published output: Only the expected alarms will be published when using the RL command to upload alarms. | X | ||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Modifies the protocol to perform a primary path test before switching from the secondary connection to the primary connection. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Prevents the driver from collecting records that are out of the request range. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Prevents a possible invalid value from appearing in the PGASOutputOptions property. | |||
| 9.1.2 | Honeywell - Mercury Protocol | Issue | Corrects an issue that prevented the Mercury Call-in Schedule from saving the Start, Length, and Interval values. | |||
| 9.1.2 | Importer/Exporter | Issue | Prevents ACM from updating references when the "Cancel" button is clicked from the Import form. | |||
| 9.1.2 | Importer/Exporter | Issue | Prevents an error from occurring when importing a "Connect String" that had a space at the end of the value. | |||
| 9.1.2 | Importer/Exporter | Issue | Corrects an issue encountered while importing Alias Groups with empty record values that prevents the entire Alias Group from getting imported. | |||
| 9.1.2 | Item Server | Issue | Reduces nuisance log messages that appeared while the ItemServer waited for asiDATA to start. Now the service will wait until asiDATA is running before attempting the IPC connection. | |||
| 9.1.2 | Item Server | Issue | Corrects an issue that caused MinutesSinceComplete to be incorrectly calculated immediately after DST. | |||
| 9.1.2 | Kinder Morgan Modbus | Issue | Improves the handling of unexpected sequence number and archive reset conditions. | |||
| 9.1.2 | Logging | Issue | Adds additional information to the logger if asiLogger is unable to retrieve the local time and fails to generate a new file at midnight. | |||
| 9.1.2 | Modbus Protocol | Issue | Adds missing Modbus Protocol token values for meter configuration records. *Effect on published output: The published output will no longer be missing token values. | X | ||
| 9.1.2 | MQTT | Issue | Corrects an issue that sent erroneous DDEATH messages to the MQTT broker when the interval on an alias group changed. | |||
| 9.1.2 | MQTT | Issue | Corrects an issue that caused a partially configured broker to require an ItemServer restart before being able to complete the configuration. | |||
| 9.1.2 | OPC UA | Issue | Corrects the data type of the initial value update for archive 'Move' and 'Reset' items. | |||
| 9.1.2 | OPC UA | Issue | Prevents inactive OPC UA items from getting an internal update. | |||
| 9.1.2 | OPC UA | Issue | Corrects an issue that could prevent items in a new Alias Group from being updated if that contained invalid item names. | |||
| 9.1.2 | OPC UA | Issue | Sets the status of a node that represents an ACM item to 'UncertainLastUsableValue' when all monitored items are removed from the node. | |||
| 9.1.2 | OPC UA | Issue | Corrects an issue that prevented a monitored item from being created on an address space node that has a bad status. | |||
| 9.1.2 | OPC UA | Issue | Corrects an issue that caused the 'Restart OPC UA Service' message to be shown when only log flags were changed on the OPC UA configuration dialog. | |||
| 9.1.2 | Prosoft Modbus | Issue | Modifies the driver to evaluate the contract hour unit and convert the value accordingly. *Effect on published output: The contract hour will be converted using the correct contract hour unit. | X | ||
| 9.1.2 | Publishing | Issue | In the CFX publishers, if the meter contents change from liquid to gas or vice versa, the CFX file will be renamed to include the current timestamp and a new file will be generated. Previously the publisher would fail. *Effect on published output: While the data within the CFX file will not change, the file name may change if a meter's content changes from Liquid to Gas or vice versa. | X | ||
| 9.1.2 | Publishing | Issue | Corrects an issue that allowed duplicate periodic records to be published to CFX7 and CFX8 files. *Effect on published output: Duplicate periodic records will no longer be published to CFX. | X | ||
| 9.1.2 | ROC Protocol | Issue | Removes the "Combine data from all segments into the same archive record" option from non-800 RTUs as it is not applicable. Previously, if used erroneously, it could result in a crash. | |||
| 9.1.2 | ROC Protocol | Issue | Corrects an issue that caused the driver to retrieve all batch records instead of the Batch Archive Limit value. | |||
| 9.1.2 | ROC Protocol | Issue | Corrects an issue where the tag modifier <TJULIAN> was not functional for 4 byte Julian dates. | |||
| 9.1.2 | Server Monitor | Issue | Corrects an issue that caused the Database Statistics form to return the error message: "Keyword not supported: 'provider' not allowed.". | |||
| 9.1.2 | Server Monitor | Issue | Updates the support package creator to provide more information regarding what can be included and provide more options to configure the contents. | |||
| 9.1.2 | Server Monitor | Issue | Corrects an issue that caused the wrong "History Deletion Frequency" option to be displayed during create/update database operations via ACM Monitor. | |||
| 9.1.2 | Server Monitor | Issue | Modifies the database form in ACM Monitor so that the "Create/Update Database" button cannot be clicked until a provider is selected. | |||
| 9.1.2 | Totalflow Protocol | Issue | Corrects an issue that prevented Totalflow extended items such as Move Daily and Move event from reverting back to their default value in UA Clients. | |||
| 9.1.2 | Totalflow Protocol | Issue | Includes the orifice plate reference temperature value in the meter configuration records for orifice meters using the AGA3-2013 calculation method. Previously it output 'empty/null'. *Effect on published output: The orifice plate reference temperature will be published orifice meters using the AGA3-2013 calculation method. | X | ||
| 9.1.2 | Totalflow Protocol | Issue | Includes additional diagnostic logging when the "Enable message tracing for more logging information" option is selected. | |||
| 9.1.2 | Totalflow Protocol | Issue | Corrects an error that could use the wrong 'remote meter index' when sending GC data to device. | |||
| ACM 9.1 | Protocols: ROC Protocol | Feature | Adds a new option to the "Device" tab labeled "Device is an FB107 with firmware version 2.0 or higher" that must be checked to collect history on FB107 devices with Firmware 2.0+. | |||
| ACM 9.1 | Protocols: ROC Protocol | Feature | Adds an option to the "Device" tab labeled "Collect history on a ROC with no configured meters (non-RocPlus)" to collect history from devices with no meters assigned. This feature is not intended for use with the ROC800 series. *Effect On Published Output: When the new option is selected, history will be published for devices with no meters configured. | |||
| ACM 9.1 | Protocols: ROC Protocol | Feature | Adds support for Vinson Haul Logs, Vinson Cyclic Logs and Vinson Gas Lift Logs in 107, 80X and 800L series ROC devices. | |||
| ACM 9.1 | Protocols: ROC Protocol | Feature | Adds an option "Store events only with associated meters" to only publish calibration events with their associated meters. *Effect On Published Output: If the option is turned on, calibration events in ROC800 will only be published to the associated meters. | X | ||
| ACM 9.1 | Protocols: ROC Protocol | Feature | Adds the ability to configure, by meter, which TLPs are written to on GC Write activities. | |||
| ACM 9.1 | Protocols: SCADAPack Protocol | Feature | Adds an option to the "Archive Collection" tab labeled "Publish Density to Observed Density with Liquid Meters". *Effect On Published Output: If the new option is checked, the Density value will be published to Observed Density for Liquid Meters. | X | ||
| ACM 9.1 | Protocols: SCADAPack Protocol | Feature | Upgrades the SCADAPack driver to support 20 meters. | |||
| ACM 9.1 | Protocols: Totalflow Protocol | Feature | Adds "Attached to Stream", "Stream Id" and "Fixed Analysis on Error" as Meter Characteristics that can be published. The fields for these characteristics can be set on the Archive Collection tab. *Effect On Published Output: If configured, "Attached to Stream", "Stream Id" and "Fixed Analysis on Error" will be included in the published output. | X | ||
| ACM 9.1 | Protocols: Weatherford Protocol | Feature | Updates 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.1 | Reports | Feature | Adds the ability to send scheduled reports to multiple individual emails without the need for a group email account. Email addresses must be separated by a comma. | |||
| ACM 9.1 | Security | Feature | Adds the ability to configure, in seconds, the inactivity timeout period. The new option, "Inactivity Timeout" is on the "Security Tab" and only applies when "Enable ROC Login" is checked. | |||
| ACM 9.1 | Server Monitor | Feature | Adds a new column in ACM Monitor Status view showing the Startup Type (i.e. Manual, Automatic or Disabled) for each process. | |||
| ACM 9.1 | Server Monitor | Feature | Provides the ability to change the Startup Type for all ACM processes within the ACM Monitor Status View tab. | |||
| ACM 9.1 | Alias Groups/Items | Issue | Corrects ACM to use only the $Server alias group if one is assigned. If an alias group is not assigned to the $Server object, ACM will use the device specific alias groups. | |||
| ACM 9.1 | API | Issue | Modifies the API to enforce validation of maximum/minimum values. | |||
| ACM 9.1 | API | Issue | Corrects an issue connecting to ACM when the API is loaded by an unmanaged process. | |||
| ACM 9.1 | asiBridge | Issue | Corrects the Quality of Service used by asiBRIDGE when it publishes MQTT messages. | |||
| ACM 9.1 | Client Application | Issue | Modifies the "Copy" functionality so that when copying a device, the meter references will not be copied. This prevents multiple devices polling data for the same meters. | |||
| ACM 9.1 | Client Application | Issue | Corrects the tool tip message for the Details tab User01 property. | |||
| ACM 9.1 | Client Application | Issue | Corrects an issue that caused the Configuration Manager to disconnect from asiData when searching for certain special characters (e.g parantheses). | |||
| ACM 9.1 | Client Application | Issue | Corrects an issue in the Scheduled Report form that caused fields using tokens to be reset. | |||
| ACM 9.1 | Client Application | Issue | Corrects an issue that prevented the object tree from reloading when selecting multiple objects via the search tool. | |||
| ACM 9.1 | Client Application | Issue | Adds the $Server and $Perf objects to the object tree in "Type View" and "Category View". | |||
| ACM 9.1 | Configuration Database | Issue | Corrects casing in asi_spInvokeArchiveSnapshot and asi_spGetPublisherFilterObjects to prevent errors on SQL Servers with extremely strict case defaults. | |||
| ACM 9.1 | Configuration Database | Issue | Increases the size of variables in asi_spGetPublisherFilteredObjects to handle very large filters. | |||
| ACM 9.1 | Configuration Database | Issue | Corrects 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.1 | Configuration Database | Issue | The script to update the database to version 42 will rebuild the Referenced Objects list which is used by the Orphaned Objects report. A manual update script is also available if this needs to occur in a database earlier than version 42. | |||
| ACM 9.1 | GC Write Service | Issue | Corrects the use of the tab delimiter and adds validation for delimiters in the GC Write File Service. | |||
| ACM 9.1 | General | Issue | Corrects an issue that caused ACM to wait for an OPC Sync Read request to complete when the target device object had been disabled. | |||
| ACM 9.1 | General | Issue | 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.1 | General | Issue | Corrects an issue that could cause an invalid timestamp in an OPC data change update. | |||
| ACM 9.1 | Importer/Exporter | Issue | Excludes missing Alias Group references from exported configuration data and ignores missing Alias Group references during configuration import. | |||
| ACM 9.1 | Importer/Exporter | Issue | Modifies the import process so it will update all references after an import. | |||
| ACM 9.1 | Installer | Issue | Modifies the ACM Crash Dump Configuration so that it will change when the ACM Data Directory is changed. | |||
| ACM 9.1 | Kinder Morgan Modbus | Issue | Corrects an issue related to archive sequence number resets in Kinder Morgan Modbus. | |||
| ACM 9.1 | OPC Items | Issue | Corrects Communication Statistics counter values. | |||
| ACM 9.1 | OPC Items | Issue | Corrects an error that cleared the item's last value when quality was "Last Known Value". | |||
| ACM 9.1 | OPC UA | Issue | 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.1 | OPC UA | Issue | Adds functionality to allow the OPC UA server to start asiData when a client app connects. | |||
| ACM 9.1 | OPC UA | Issue | Corrects an issue that rejected items with square brackets around the device object name. | |||
| ACM 9.1 | OPC UA | Issue | Corrects an issue that caused multiple address space nodes to be created for the same item if a client did not include the namespace index in the item name. | |||
| ACM 9.1 | OPC UA | Issue | Corrects an error that resulted in an "out of bounds" error message when a client reinitialized a monitored item list. Corrects an issue that prevented monitored items from updating for nodes of data type 'signed byte'. Corrects an error that could return a "Service Fault - BadNotSupported" error message when creating a second monitored item for a node with data type 'signed byte'. | |||
| ACM 9.1 | OPC UA | Issue | Corrects an issue that prevented monitored items from being created in the Server address namespace. | |||
| ACM 9.1 | OPC UA | Issue | 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.1 | Protocols: Base Protocol | Issue | Removes a duplicate warning message in log files about Item Data and Item Update that appeared when a demand timed out. | |||
| ACM 9.1 | Protocols: Base Protocol | Issue | Adds validation to the device "Connect String" property to disallow non-numeric characters in the IP Port number. | |||
| ACM 9.1 | Protocols: Base Protocol | Issue | Corrects an issue that prevented the Archive Limits "Limit First Collection" settings from being applied when assigning an Archive Limit object after having collected history and reset the pointer. | |||
| ACM 9.1 | Protocols: Benchmark Protocol | Issue | Corrects an issue that incorrectly processed a sub-command 11 when a field item data index was present in the item. | |||
| ACM 9.1 | Protocols: DNP3 Protocol | Issue | Adds support for Vinson Transactional Logs. | |||
| ACM 9.1 | Protocols: DNP3 Protocol | Issue | Corrects an issue that prevented the "Use meter config from device" option from being used during publishing. *Effect On Published Output: The correct meter configuration will be published based on the "Use meter config from device" checkbox. | X | ||
| ACM 9.1 | Protocols: DNP3 Protocol | Issue | Corrects an issue that could prevent meter configuration file items from being read after re-checking the "Use meter config from device" option. This could occur when going from using the meter config from the device, to using the advanced meter config, and back again while the meter configuration file from the first setting was still valid. | |||
| ACM 9.1 | Protocols: DNP3 Protocol | Issue | 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.1 | Protocols: FlowX Protocol | Issue | Corrects the history map validation to treat records with the same EFMID, MeterID and Period as duplicates. | |||
| ACM 9.1 | Protocols: GE SRTP Protocol | Issue | Prevents a memory leak in the GE SRTP protocol. | |||
| ACM 9.1 | Protocols: GE SRTP Protocol | Issue | Modifies the GE SRTP driver so a "No meter assigned for device" message will not appear when polling a device for which you are not collecting history. | |||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | Corrects an issue that prevented audit trail items set to register address 255 from being published when the field was configured in a configurable archive as a 'Value' field. Effect On Published Output: Audit trail items set to address 255 will now be published if configured as a 'Value' field in the configurable archive object record set. | X | ||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | Corrects the AlarmType register value for all available Mercury registers to display all digits. | |||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | Removes 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.1 | Protocols: Honeywell - Mercury Protocol | Issue | Adds the alarm description in the alarm record output for non EC350 devices. *Effect On Published Output: Alarm descriptions will be published for non-EFM alarms. | X | ||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | Modifies the driver so the demand item will be updated during a cry out after triggering a continuous scan. | |||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | 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.1 | Protocols: Honeywell - Mercury Protocol | Issue | Corrects an issue that could prevent a meter's configuration from being uploaded if the sign-on sequence failed during a history upload and a retry is attempted by ACM. | |||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | Corrects an issue that could cause the polling sequence to an RTU to get out of sync with the RTU resulting in an Invalid Command Error response during sign-on sequence. | |||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | A Time Sync operation will now cause the Call-in Schedule to be set on the RTU when the protocol option "Set call-in schedule after regular polls" is enabled. | |||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | Corrects an issue that caused the RTU call-in to not be acknowledged when no device protocol call-in options were enabled. | |||
| ACM 9.1 | Protocols: Honeywell - Mercury Protocol | Issue | 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.1 | Protocols: Honeywell - Mercury Protocol | Issue | Removes the "Change Access" capability for Honeywell Mercury EC350 & ERX350 as it is unsupported by these devices. | |||
| ACM 9.1 | Protocols: Micro MP3 Protocol | Issue | Corrects an issue that prevented the "Contract Hour" from being polled correctly which resulted in the value always being 0 on the Archive Management tab. *Effect On Published Output: Contract hour is now polled correctly and published for Micro MP3 devices. | X | ||
| ACM 9.1 | Protocols: Modbus Protocol | Issue | Corrects an error that occurred when writing to array item using common Modbus item modifier 'IS'. | |||
| ACM 9.1 | Protocols: Omni Modbus Protocol | Issue | Prevents a Viscosity event in Omni 7000 devices from returning an abnormal code. | |||
| ACM 9.1 | Protocols: Omni Modbus Protocol | Issue | 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.1 | Protocols: Omni Modbus Protocol | Issue | Corrects an issue that could cause an exception while processing an Omni 3000/7000 alarm record. | |||
| ACM 9.1 | Protocols: Possibly multiple protocols | Issue | Adds all Batch Record field identifiers and Liquid Product field identifiers to the selection list in the Archive Field Configuration Record Collection form. | |||
| ACM 9.1 | Protocols: ROC Protocol | Issue | Adds DATABASE.TOTAL_YD back to the OPC browsing list. | |||
| ACM 9.1 | Protocols: ROC Protocol | Issue | Corrects an issue that caused the GCWrite to write to incorrect TLPs if the GCWrite was executed before ROC meter configuration was read. | |||
| ACM 9.1 | Protocols: ROC Protocol | Issue | Corrects an issue that occasionally prevented the driver from determining the appropriate series when the "Do not switch ROC automatically series" was unchecked. | |||
| ACM 9.1 | Protocols: ROC Protocol | Issue | Corrects an issue that left an invalid item in the poll message after an "Invalid TLP" error code. | |||
| ACM 9.1 | Protocols: ROC Protocol | Issue | Corrects an issue where ROC FB103's were being polled as 503's resulting in missing values and no extended records. *Effect On Published Output: Corrects an issue where ROC FB103's were being polled as 503's resulting in missing values and no extended records. | X | ||
| ACM 9.1 | Protocols: ROC Protocol | Issue | Prevents the option group from scrolling when clicking on an option while the form is not maximized. | |||
| ACM 9.1 | Protocols: ROC Protocol | Issue | Adds a field to the "Device" tab labeled "Schedule Reinitialization" to schedule the Reinitialize command. | |||
| ACM 9.1 | Protocols: ROC Protocol | Issue | 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.1 | Protocols: SCADAPack Protocol | Issue | Corrects an issue that prevented the Scadapack driver from updating the status of a GC Write request if the request failed due to a Comm error. | |||
| ACM 9.1 | Protocols: SCADAPack Protocol | Issue | 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.1 | Protocols: Siemens Protocol | Issue | Corrects an issue with Byte Bit offsets that caused returned and written values to be off by one index. | |||
| ACM 9.1 | Protocols: Totalflow Protocol | Issue | Corrects an issue where a time sync and history request will fail due to having the same priority schedule. | |||
| ACM 9.1 | Protocols: Totalflow Protocol | Issue | 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.1 | Protocols: Totalflow Protocol | Issue | 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.1 | Protocols: Totalflow Protocol | Issue | Adds 'Double' data type support for Totaflow register read and write. | |||
| ACM 9.1 | Protocols: Weatherford Protocol | Issue | 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.1 | Protocols: Weatherford Protocol | Issue | Corrects 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.1 | Publishing | Issue | Increases 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.1 | Publishing | Issue | Adds logging to the Database output type to show if a transaction was committed or rolled back to show the transaction completed. | |||
| ACM 9.1 | Publishing | Issue | Adds the field name and unit of measure to the message that is logged when the publisher cannot validate an event. | |||
| ACM 9.1 | Publishing | Issue | Corrects the error that resulted in an "Implicit conversion from data type datetime to real is not allowed." message when publishing a sample date to the FLOWCAL Transaction Queue. *Effect On Published Output: The sample date value from a DNP3 FBx device can now be published. | X | ||
| ACM 9.1 | Publishing | Issue | 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.1 | Publishing | Issue | Prevents a string value from being published as the Contract Hour if an alphabetic character is entered for Contract Hour in the Advanced Meter Config. *Effect On Published Output: The FLOWCAL Transaction Queue will publish a number entered in the Contract Hour of the Advanced Meter Config, and will publish nothing if an alphabetic character is entered. | X | ||
| ACM 9.1 | Publishing | Issue | Adds a fixed/live temperature indicator as TEMP_SOURCE and a fixed/live pressure indicator as SP_SOURCE to the meter characteristics for the PGAS XML publisher. *Effect On Published Output: The PGAS XML output will include fixed/live temperature and fixed/live pressure flags in the meter characteristics element if the protocol driver provides them. | X | ||
| ACM 9.1 | Publishing | Issue | 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.1 | Publishing | Issue | The User01, User02, User03, External GC Reference and External Meter Reference properties will now have values in the published output. | |||
| ACM 9.1 | Reports | Issue | Prevents extraneous logs from being written when saving edits to scheduled reports. | |||
| ACM 9.1 | Reports | Issue | Corrects an issue in the Scheduled Reports that caused the $$CurrentDay$$ or $$CurrentHour$$ tokens to be incorrectly calculated in Throughput reports. | |||
| ACM 9.1 | Reports | Issue | Corrects an issue in the Scheduled Reports form that prevented the Save button from being enabled after editing the connection. | |||
| ACM 9.1 | Reports | Issue | Modifies the "Configuration Changes for a Device" report to filter to only Device type objects. | |||
| ACM 9.1 | Reports | Issue | Adds a new report titled "Configuration Changes for an Object" to search for configuration changes for any object type. | |||
| ACM 9.1 | Reports | Issue | Adds support for all of the following report formats to both manually run reports and scheduled reports: CSV, HTML, PDF, XLS, XLSX, & TEXT. | |||
| ACM 9.1 | Reports | Issue | 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.1 | Server Monitor | Issue | Adds the newest Microsoft OLE DB Driver 19 to the available database providers in ACM Monitor. This provides additional encryption options for the connection. More information can be found in the User Guide. | |||
| ACM 9.1 | Server Monitor | Issue | Adds a button to view the connection string. | |||
| ACM 9.1 | Server Monitor | Issue | Modifies the History Deletion value displayed in the Task Summary field when creating a new ACM database to show HH:MM. | |||
| ACM 9.1 | Server Monitor | Issue | Corrects the Write Timeout property of "Gas Analysis Writes Retry" to accept values in the range of 30 to 600 seconds. | |||
| ACM 9.1 | Server Monitor | Issue | Modifies the password requirements for the database user in ACM Monitor to prevent semi-colons. | |||
ACM 9.0.1 | ACM Server | Issue | 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.1 | General | Issue | Corrects a memory leak that occurs when logging "data sent to client" on items in the OPC UA interface. | |||
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. | YES | ||
ACM 9.0.1 | Protocols: Base Protocol | Issue | Correctly updates PctBadTries and PctGoodTries if the connection fails before the message can be sent. | |||
ACM 9.0.1 | Protocols: Base Protocol | Issue | Correctly updates the port PollAttempts counter when an external interruption occurrs. | |||
ACM 9.0.1 | Protocols: Base Protocol | Issue | Prevents queuing an additional demand after Demand is poked to trigger a continuous scan during cry out. | |||
ACM 9.0.1 | Protocols: Base Protocol | Issue | Corrects an issue that prevented the PctGoodTries and PctBadTries statistic items from being correctly updated when a connection was dropped before a message could be sent. | |||
ACM 9.0.1 | Protocols: BSAP 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 selected. | |||
ACM 9.0.1 | Protocols: BSAP Protocol | Issue | 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 | Protocols: DNP3 Protocol | Issue | 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 | 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: DNP3 Protocol | Issue | 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: DNP3 Protocol | Issue | Corrects an issue so that alias items are added correctly via browsing in an OPC client. | |||
ACM 9.0.1 | Protocols: DNP3 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 | ||
ACM 9.0.1 | Protocols: DNP3 Protocol | Issue | Changes the dropdown list that selects the meter run into a numeric updown control in the Meter Runs tab. | |||
ACM 9.0.1 | Protocols: Flow Automation 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 checked. | |||
ACM 9.0.1 | Protocols: Honeywell - Mercury Protocol | Issue | Corrects a potential memory leak. | |||
ACM 9.0.1 | Protocols: Honeywell - Mercury 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 | ||
ACM 9.0.1 | Protocols: Modbus 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. | |||
ACM 9.0.1 | Protocols: Omni Modbus Protocol | Issue | Corrects an issue that prevented subsequent archives from being requested after processing the GC archive for Archive 1. | |||
ACM 9.0.1 | Protocols: Omni Modbus 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. | |||
ACM 9.0.1 | Protocols: ROC Protocol | Issue | Corrects an issue in detecting the ROC model type that prevented ROC history collection settings from updating properly. | |||
ACM 9.0.1 | Protocols: Totalflow Protocol | Issue | Corrects an issue that prevented LastHourlyRecord/1 from being initialized correctly with the latest hourly record time stamp. | |||
ACM 9.0.1 | Protocols: Totalflow Protocol | Issue | Corrects an issue that occurred when the field device handles a request for a history record at the "maximum position" by returning more than one record. | |||
ACM 9.0.1 | Protocols: Totalflow Protocol | Issue | 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: Totalflow Protocol | Issue | Corrects an issue that prevented the daily record from being collected when using the "number of days" method in the DB2 protocol. | |||
ACM 9.0.1 | 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 | ||
ACM 9.0.1 | Publishing | 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' element. | |||
ACM 9.0.1 | Publishing | Issue | Prevents the asiPublish process from hanging when asiData is being shut down. | |||
ACM 9.0.1 | Publishing | Issue | Corrects an issue that stopped publishing to the FLOWCAL Transaction Queue when a record had an invalid future timestamp. | |||
ACM 9.0.1 | Reports | Issue | Logs the query of a scheduled report when the "Report Logging" option is enabled. | |||
ACM 9.0.1 | Reports | Issue | Corrects an issue that prevented users from requested unlimited records when running reports. | |||
ACM 9.0.1 | Server Monitor | 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 exist. | |||
| ACM 9.0.1 | Server Monitor | Issue | Prevents 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 | Tools | 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. | |||
ACM 9.0 | ACM Server | Issue | Resolves issues related to OPC client browsing when clients use absolute browse paths instead of relative browsing. | |||
ACM 9.0 | ACM Server | Issue | 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 | API | Issue | Corrects an issue in the API which reported that "Server" objects are creatable. | |||
ACM 9.0 | Client Application | Feature | Adds the Object ID and Description to the search results form. | |||
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 items. | |||
ACM 9.0 | Client Application | Feature | Provides the ability to assign multiple alias groups to devices and views. | |||
ACM 9.0 | Client Application | Feature | Adds the ability to assign an Interval to Alias Groups. | |||
ACM 9.0 | Client Application | Feature | 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 database. | |||
ACM 9.0 | Client Application | Issue | 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 | Issue | Corrects various forms throughout ACM where fields and buttons were enabled when they shouldn't have been. | |||
ACM 9.0 | Client Application | Issue | The Add/Select object window will now retain its size when closed and reopened. | |||
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 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 entered. | |||
ACM 9.0 | Client Application | Issue | Corrects the tab order on the "Database" tab of the configuration form of the $Server object. | |||
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 configured. | |||
ACM 9.0 | Client Application | Issue | Displays a new error message when an object name contains a carriage return in the name. | |||
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 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 |
...