Information about eACM Security can be found: AUTOSOL Security Center
Out of Maintenance Releases
*Use the "shift" key to sort by multiple columns.
| Release | Application | Text | Affects Published Output | Addresses Security Vulnerability |
|---|---|---|---|---|
| eACM 2.2.1.0 | AUTOSOL App Manager 2.2.1.0 | HTTPS can now be enabled and disabled on the webserver. HTTPS is disabled by default. | ||
| eACM 2.2.1.0 | AUTOSOL App Manager 2.2.1.0 | Adds the ability to log in with a username and password. The default is admin/admin. | ||
| eACM 2.2.1.0 | AUTOSOL App Manager 2.2.1.0 | Corrects an issue with tag groups and how the file is loaded. | ||
| eACM 2.2.1.0 | AUTOSOL App Manager 2.2.1.0 | Changes the wording on the App Manager connection status for clarity. | ||
| eACM 2.1.0 | AUTOSOL App Manager 2.1.0 | AUTOSOL App Manager can now manage AUTOSOL Bridge | ||
| eACM 2.1.0 | AUTOSOL App Manager 2.1.0 | You can now delete log files from the Log Viewer page. | ||
| eACM 2.1.0 | AUTOSOL App Manager 2.1.0 | App Manager now supports configuration object commands | ||
| eACM 2.1.0 | Edge ACM 2.1.0 | Edge ACM and Edge MQTT Publisher have better start up validation in order to prevent false start ups. | ||
| eACM 2.1.0 | Multiple | Ping target (ipv4) has been implemented in Connection objects across different applications | ||
| eACM 2.0.3 | Edge MQTT Publisher | Fixed memory leak issue in Edge MQTT Publisher Sparkplug B Publisher | ||
| eACM 2.0.3 | Edge MQTT Publisher | Fixed issue in Edge MQTT Publisher where subscriptions were lost by broker after a broker restart | ||
| eACM 2.0.3 | Edge MQTT Publisher | Fixed issue in Edge MQTT Publisher where back fill to disk could corrupt a file if power loss occurs during write | ||
| eACM 2.0.0 | AUTOSOL App Manager 2.0.0 | In an effort to improve future development as well as bug fixes, our AUTOSOL App Manager and our Edge Managers were redesigned to use the same base code. | ||
| eACM 2.0.0 | AUTOSOL App Manager 2.0.0 | Communication between the Universal and Edge Managers is now exclusively through the MQTT protocol. | ||
| eACM 2.0.0 | AUTOSOL App Manager 2.0.0 | Edge Manager (formerly App Manager) ships with its own web configuration site which will be available for initial configuration or any other local changes. | X | |
| eACM 2.0.0 | AUTOSOL App Manager 2.0.0 | Both Managers utilize the same User Interface. The improved tree view allows you to quickly change and configure items across different nodes in your network. The UI is accessible through HTTP on any browser. | ||
| eACM 2.0.0 | AUTOSOL App Manager 2.0.0 | Multiple configuration tabs are now available. Like in other AUTOSOL products, we have now implemented tabs in our configuration interface. You will be able to quickly view and compare different items across your network of nodes. | ||
| eACM 2.0.0 | AUTOSOL App Manager 2.0.0 | The Import/Export functionality has been expanded to apply to all types of items. You can import/export a whole Node, a single App, or a single Object. | X | |
| eACM 2.0.0 | AUTOSOL App Manager 2.0.0 | System Information now displays further information about the state of the manager. You can download that information as a report file from the System Info page. | ||
| eACM 2.0.0 | AUTOSOL App Manager 2.0.0 | Log Viewer now has a way to download all log files from the system in a zipped archive format. | ||
| eACM 2.0.0 | Azure 1.0.0 | Azure application has been released with version 1.0.0 | ||
| eACM 2.0.0 | Azure 1.0.0 | Azure publishes Edge ACM device item updates on a report-by-exception basis to Azure IoT Hub via Device-to-Cloud telemetry | ||
| eACM 2.0.0 | Azure 1.0.0 | Azure writes to Edge ACM device items when a write request is received via Azure IoT Hub Cloud-to-Device messages | ||
| eACM 2.0.0 | Edge ACM 2.0.0 | Edge ACM design has changed to publish protocol data to an Internal Tag server to which Edge MQTT Publisher and Azure publishing apps can connect. | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | New ability to publish as multiple nodes from single device | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | Support for MQTT TLS added | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | Support for MQTT Protocol Version 5 added | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | Added ability to set custom Client ID on broker connections | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | Advanced timing options added | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | Primary Host ID functionality added | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | Added ability to back fill data to disk upon connection loss or primary host disconnect | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | Added ability to split back fill messages with a set number of values per tag | ||
| eACM 2.0.0 | Edge MQTT Publisher 1.0.0 | Added ability to hard code a delay time between births | ||
| eACM 1.0.0 | AUTOSOL App Manager 1.0.0 | System information now shows the versions of the applications installed. | ||
| eACM 1.0.0 | AUTOSOL App Manager 1.0.0 | Data models now support multiple references to other data models. | ||
| eACM 1.0.0 | AUTOSOL App Manager 1.0.0 | Partial imports are now supported. | ||
| eACM 1.0.0 | AUTOSOL App Manager 1.0.0 | Preliminary backwards compatibility modifications were implemented. | ||
| eACM 1.0.0 | AUTOSOL App Manager 1.0.0 | The new import.log will show what items were modified. | ||
| eACM 1.0.0 | AUTOSOL App Manager 1.0.0 | If a data model changes, App Manager can import most of the configuration. | ||
| eACM 1.0.0 | AUTOSOL App Manager 1.0.0 | An uninstaller has been added. | ||
| eACM 1.0.0 | Edge ACM 1.1.0 | You can now download an empty CSV header file from a Tag Group in Edge ACM. | ||
| eACM 1.0.0 | Edge ACM 1.1.0 | Support for fully custom Modbus register sets has been added. | ||
| eACM 1.0.0 | Edge ACM 1.1.0 | Added a schedule object that can be assigned to tag groups. NOTE: Poll Interval has been moved from the Connection Settings object to this new schedule object. | ||
| eACM 1.0.0 | Edge ACM 1.1.0 | Devices now support multiple tag groups. | ||
| eACM 1.0.0 | Priority Forward 2.0.0 | Priority Forward has been updated to version 2.0.0 | ||
| eACM 1.0.0 | Priority Forward 2.0.0 | Connections have been renamed to Channels and now support advance settings. | ||
| eACM 1.0.0 | Priority Forward 2.0.0 | The priority client can be delayed from forwarding until after a millisecond configured timeout. | ||
| eACM 1.0.0 | Priority Forward 2.0.0 | Connection retries and retry intervals from the Priority and Secondary down to the end device are now configurable. | ||
| eACM 1.0.0 | Priority Forward 2.0.0 | Priority Forward logs are much more descriptive and useful. |