eACM Software Release Contents

Information about eACM Security can be found:  AUTOSOL Security Center

Releases In Active Maintenance

*Use the "shift" key to sort by multiple columns.

ReleaseApplicationTextAffects Published OutputAddresses Security Vulnerability
eACM 3.5.5.0App Manager 3.5.5.0Adds a user interface for managing metadata properties for a tag.

eACM 3.5.5.0App Manager 3.5.5.0Disabled objects in the tree will now be represented by a different icon to show they are disabled.

eACM 3.5.5.0App Manager 3.5.5.0Adds the ability to sort children tables.

eACM 3.5.5.0App Manager 3.5.5.0Adds the property description as a tool tip for the column headers in the multi-edit table.

eACM 3.5.5.0App Manager 3.5.5.0Removes the square icon from a column header if the column is not expandable.

eACM 3.5.5.0App Manager 3.5.5.0Adds a setting to the dashboard that enables the user to hide and display apps.

eACM 3.5.5.0App Manager 3.5.5.0Adds multiple hot keys and short cuts to the user interface:  
  1. The ability to delete objects from the tree when the objects is selected and the delete key is pressed.
  2. The ability to drag and drop objects in the tree.   
  3. The ability to reorder tabs in App Manager.
  4. The ability to save by clicking Enter.
  5. The ability to open the properties for an object in the tree by holding the "Ctrl" key and clicking on the object. 
  6. The ability to restart an app (Edge ACM, Priority Forward, etc) by the keyboard shortcut Ctrl + R. 
  7. The ability to add objects to the tree directly from the Object view.


eACM 3.5.5.0App Manager 3.5.5.0Adds the ability to view App Manager in "Dark Mode".  This can be set under "Personalization" in the "Account" settings.

eACM 3.5.5.0App Manager 3.5.5.0Adds the ability to import individual objects

eACM 3.5.5.0App Manager 3.5.5.0Adds the ability to import objects that are deeper than the root level.

eACM 3.5.5.0App Manager 3.5.5.0Updates the name of the web browser tab to match the node name.

eACM 3.5.5.0App Manager 3.5.5.0Improves Excel imports with nested references.

eACM 3.5.5.0App Manager 3.5.5.0Adds the ability to export all objects within an App to Excel.

eACM 3.5.5.0App Manager 3.5.5.0Logs all changes made to objects in the objects.log file accessible from the Log Files tab.

eACM 3.5.5.0App Manager 3.5.5.0Adds the ability to view an object's change log by clicking the "View Logs" option in the right-click menu.

eACM 3.5.5.0App Manager 3.5.5.0Adds a logger for Edge nodes that allows for viewing changes in real-time.

eACM 3.5.5.0CPU Statistics 1.0.0.0Adds a new application, "CPU Statistics" that, when enabled, polls CPU statistics such as load average and memory usage, and allows them to be published as tags through applications like MQTT Publisher.  The app is disabled by default. *Effect On Published Output: This change adds the ability to publish CPU, memory, and disk statistics through applications such as MQTT.X
eACM 3.5.5.0Edge ACM 3.1.0.0A new trigger condition called "Percent Change" has been added for Tag objects. The specified value is the percent change between the current value and the previous value of the tag. For example a value of 50 means a percent change of 50% or greater will meet the trigger condition. *Effect On Published Output:  The percent change trigger condition will look at the previous value and the current value, and if the change matches or is greater than the specified percent change value (%) the trigger condition is met.X
eACM 3.5.5.0Edge ACM 3.1.0.0A "Duration" field has now been added to triggers.  The Duration extends the time that the associated quality will be assigned to the tag once the condition is no longer met. *Effect On Published Output: Triggers can now have a duration. By default, the duration is 0 seconds, so the "Triggered" quality will last for just that poll cycle. A duration of >0 seconds, for example 10 seconds, means that the quality will extend for a total of 10 seconds after no longer meeting the triggered condition. If the triggered condition is met again within that duration, the duration is reset.  X
eACM 3.5.5.0Edge ACM 3.1.0.0

Tags with multiple Trigger conditions now follow a priority system. For example, if a tag has three trigger conditions, the first trigger listed has the highest priority, the second trigger has a lower priority than the first but a higher priority than the third, and the third trigger has the lowest priority. If multiple conditions are met at the same time, the condition with the highest priority will be followed. *Effect On Published Output: Triggers assigned to tags now have a priority system, so trigger qualities published will follow the priority system.

X
eACM 3.5.5.0Edge ACM 3.1.0.0Adds a 'demo mode' to eACM, which runs for a limited time (2 hours) and with limited functionality. The limited functionality is as follows: 
  1. When the 2 hour window runs out, the program will stop and will not auto-restart, even if that option is enabled in the browser. 
  2. Sets the device limit to 1.
  3. Sets the maximum number of tags for the device to 100.


eACM 3.5.5.0Edge ACM 3.1.0.0Adds support for adding static metadata information to tags. Metadata properties allow for users to provide additional information about tags, and which can be found in the device birth (DBIRTH) message from the Sparkplug B publisher or in a client such as Ignition. Tags can have zero to many metadata properties.

eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0Adds the ability to include the Node Name and/or the Node IP address to metrics on NBIRTH messages.  Two new settings, 'Include Node Name in the Node Birth (NBIRTH) message' and 'Include Node IP address in the Node Birth (NBIRTH) message' are available under the "Advanced Sparkplug" tab of the Sparkplug B Publishing object.

eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0Provides the ability to force backfill on every tag in the same publishing group. This happens by default for tags with backfill type 'Always', but can be extended to tags with backfill type 'When Triggered' when 'Backfill on Every Tag When Triggered' is enabled on the publish schedule object. With this option enabled, backfill data will be stored and published for 'When Triggered' tags when any tag in the tag group is in a triggered state (i.e Tag Quality > 192-Good). When no triggers are active, the 'When Triggered' tags will not store or publish backfill data.X
eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0Adds the ability to set the QoS per tag group.

eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0Adds the ability to assign redundant brokers to publisher objects.

eACM 3.5.5.0InstallerAdds a "defaults.ini" file in which default values for node names and broker connection settings can be stored.

eACM 3.5.5.0InstallerAppManager can now be installed on Debian 12.

eACM 3.5.5.0App Manager 3.5.5.0Modifies the timestamp format in the Data Viewer to "mm/dd/yyyy HH:MM:SS:fff".

eACM 3.5.5.0App Manager 3.5.5.0Adds a full App view, allowing all device data to be visible in one table.

eACM 3.5.5.0App Manager 3.5.5.0Corrects an issue that prevented module updates or a restarts in the Software Update page from showing notification or statuses.

eACM 3.5.5.0App Manager 3.5.5.0Corrects a performance issue with large amount of objects in the explorer view.

eACM 3.5.5.0App Manager 3.5.5.0Corrects an issue that prevented web urls from formatting correctly in a Node's info tab.

eACM 3.5.5.0App Manager 3.5.5.0Corrects an issue that caused tags to be displayed in the tree.

eACM 3.5.5.0App Manager 3.5.5.0Prevents an issue that prevented tags from importing when the tag group IDs were too short.

eACM 3.5.5.0App Manager 3.5.5.0eEFM can be collected and published in containerized environments.

eACM 3.5.5.0App Manager 3.5.5.0Corrects an issue when selecting 2bytes as the addressing type on Modbus device objects.

eACM 3.5.5.0App Manager 3.5.5.0Prevents an issue with multiple remote commands from being sent to a node.

eACM 3.5.5.0App Manager 3.5.5.0Corrects an issue where changes to a file property would not mark an item as changed.

eACM 3.5.5.0App Manager 3.5.5.0Corrects an issue that caused the UI to show that a Node had completed syncing when it hadn't which caused the node to load incorrectly.

eACM 3.5.5.0App Manager 3.5.5.0Moves the log files to the correct directory.

eACM 3.5.5.0App Manager 3.5.5.0AAM server config.ini is now in in the Program Data\AutoSol\AAM\ folder. * Please save your current configuration and update the ini file after the installation *

eACM 3.5.5.0App Manager 3.5.5.0Modifies AAM so it will handle Edge nodes that were created by duplicating a node.

eACM 3.5.5.0App Manager 3.5.5.0Provides the ability to manually generate an Edge Node's Node Id, Related App Id and Object Ids.

eACM 3.5.5.0Edge ACM 3.1.0.0eACM and MQTT will use the configuration setting in config.ini as the EFM database connection string for records and reporting.

eACM 3.5.5.0Edge ACM 3.1.0.0Improves the error messages logged when reading files from an outside source, such as when a license file is malformed.

eACM 3.5.5.0Edge ACM 3.1.0.0Prevents a memory leak in GE SRTP protocol.

eACM 3.5.5.0Edge ACM 3.1.0.0Corrects an error that could occur when a TCP connection is used with newer protocols.

eACM 3.5.5.0Edge ACM 3.1.0.0Corrects an issue that caused an unnecessary delay in polling after a communication timeout.

eACM 3.5.5.0Edge ACM 3.1.0.0Prevents the ROC protocol from casting written values to integers before being sent to the ROC device.

eACM 3.5.5.0Edge ACM 3.1.0.0DDEATH messages will be published for all connected devices when Edge ACM is stopped while MQTT is running. *Effect On Published Output: When Edge ACM is stopped, DDEATH messages will appear for connected devices through MQTTX
eACM 3.5.5.0Edge ACM 3.1.0.0Corrects an issue with eACM license validation between installations.

eACM 3.5.5.0Edge ACM 3.1.0.0Corrects an issue in the ROC protocol so that it correctly passes a Boolean value for the Demand item to the MQTT publisher.

eACM 3.5.5.0Edge ACM 3.1.0.0Replaces the tacopie TCP Client/Server library with Boost.Asio. tacopie has reached its end of maintenance.

eACM 3.5.5.0Edge ACM 3.1.0.0Corrects an issue that caused the ROC protocol response timeout setting to be ignored.

eACM 3.5.5.0Edge ACM 3.1.0.0Improves polling performance for the ROC protocol.

eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0Corrects an issue that caused some data to be missing from one publisher when more than one publisher was enabled.X
eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0Corrects the Node.bdSeq tag value to increment by 1 on each MQTT connect.

eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0Lowers the CPU consumption of MQTT.

eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0The MQTT publisher app will now clear its subscription when a broker connection is dropped before re-subscribing to the topic upon reconnect.  Previously the MQTT Publisher would stop providing updates after repeated dropped broker connections.

eACM 3.5.5.0Edge MQTT Publisher 2.4.0.0Modifies the MQTT application so that it will run in Ubuntu 22 LTS or newer by making it portable across OpenSSL versions.

eACM 3.5.5.0File Handler 1.3.1.3Adds text file support to File Handler.

eACM 3.5.5.0InstallerThe installer will now install the correct version of the software according to the given OS configurations.X
eACM 3.5.5.0OPC UA 1.4.0.0Removes the "License" tab from the OPC UA application as one is not required.

eACM 3.4.5.0Edge ACM 3.0.0.0Users can select between eACM maintaining a connection to a port or releasing that connection after a device has stopped polling.

eACM 3.4.5.0Edge ACM 3.0.0.0Adds the ability to poll EFM data via the ROC Protocol.

eACM 3.4.5.0Edge MQTT Publisher 2.3.0.0Adds a command to connect with encrypted brokers

eACM 3.4.5.0App Manager 3.4.5.0Corrects an issue where moving an item in the tree would not display the item location correctly.

eACM 3.4.5.0App Manager 3.4.5.0Corrects an issue that allowed circular references in the tree, thus hiding objects from displaying.

eACM 3.4.5.0App Manager 3.4.5.0Corrects issue with displaying 0/False tag values in Data Viewer

eACM 3.4.5.0App Manager 3.4.5.0Corrects an issue with Software Updates database entries always syncing.   An uninstalled app in an edge node will now get deleted from the AAM database on sync.

eACM 3.4.5.0asiBridgeBridge can process backfill data in birth messages.

eACM 3.4.5.0Edge ACM 3.0.0.0Modbus now publishes a message in the logs indicating that there has been an error in the response message. The user/client will now be able to identify that an error has occurred without having to specifically read and manually decode a Modbus formatted response message.

eACM 3.4.5.0Edge ACM 3.0.0.0Corrects an issue that prevented the Edge ACM license request from being downloaded correctly.

eACM 3.4.5.0Edge ACM 3.0.0.0Schedule objects have been replaced by Interval objects

eACM 3.4.5.0Edge ACM 3.0.0.0Corrects issue where a device might not poll if it was assigned a connection settings object with duplicate host and port configuration

eACM 3.4.5.0Edge ACM 3.0.0.0Adds validation to tag trigger conditions and logs a warning message if multiple triggers for a single tag conflict or overlap.  E.g.  If one triggers on a value greater than 0, a second cannot trigger on a value greater than 10.

eACM 3.4.5.0Edge MQTT Publisher 2.3.0.0Corrects Writes when Sparkplug B aliases are disabled. Corrects the Every Scan option for Boolean Tags. Corrects Device Rebirth appearing twice in DBIRTH message.

eACM 3.0.4.0AUTOSOL App Manager 3.0.4.0Corrects an issue with the save function shortcut.

eACM 3.0.4.0AUTOSOL App Manager 3.0.4.0Corrects an issue that could cause tag groups to be unlinked from device objects after an import of tags.

eACM 3.0.4.0AUTOSOL Bridge 2.1.1.2Prevents unknown characters from being added to end of STATE messages.

eACM 3.0.4.0AUTOSOL Bridge 2.1.1.2Corrects a timestamp issue with asiBridge commands

eACM 3.0.4.0Client Scripts

Adds a script to remotely reboot edge devices.



eACM 3.0.4.0Client ScriptsAdds a script for remote collection of logs from field devices.

eACM 3.0.4.0Client ScriptsAdds a script to remotely start the core apps on multiple devices.

eACM 3.0.4.0Client ScriptsAdds a script to resolve duplicate Node IDs caused by cloning Edge systems.

eACM 3.0.4.0Client ScriptsCorrects an issue that prevented apps from restarting after an import script completes.

eACM 3.0.4.0Client ScriptsImproves logging when an import script starts or stops an app.

eACM 3.0.4.0eACM 3.0.4.0Edge ACM is now available for ARM32, ARM64 and AMD32

eACM 3.0.4.0Edge ACM 2.2.0.0Adds a new option, "Every Scan", to the "Deadband Type" tag. When used, the tag will be published every time, whether or not the value or quality have changed. *Effect on published output: When the "Every Scan" option is selected, the tag value be published every time, even if the value (or quality) has not changed.

eACM 3.0.4.0Edge ACM 2.2.0.0Modifies SparkplugB Aliases so that they are incremental. e.g. [0,1,2,3,...] rather than [0,3,5,6,...].

eACM 3.0.4.0Edge ACM 2.2.0.0Adds the ability to select specific comm stats and standard tags to publish with tags already assigned to a given device. This option is available on the device's "Comm Stats" tab. *Effect On Published Output: When specific comm stats and standard tags are selected, they will be published along with already assigned tags.

eACM 3.0.4.0Edge ACM 2.2.0.0Provides the ability to associate a Tag Group object with a specific MQTT publisher to publish tags via different MQTT publisher objects. A publisher schedule object must already exist in MQTT to use this feature.

eACM 3.0.4.0Edge ACM 2.2.0.0Adds an option to the Edge ACM properties tab to validate a license that has been uploaded through the UI.

eACM 3.0.4.0Edge ACM 2.2.0.0Adds an option for validating the apps license, using config.ini files in different paths, when running Edge ACM through the command line. To view the format for this option, include the flag "-h".

eACM 3.0.4.0Edge ACM 2.2.0.0Adds an option to create a new license request file when running Edge ACM through the command line. To view the format for this option, include the flag "-h".

eACM 3.0.4.0Edge ACM 2.2.0.0Tag server files that are created and required by Edge ACM(i.e. tagvaluechanges, tagmeta, tagwrite) will now automatically have the appropriate permissions.

eACM 3.0.4.0Edge ACM 2.2.0.0Active tags will be updated to show bad quality when Edge ACMis stopped.

eACM 3.0.4.0Edge ACM 2.2.0.0Corrects a bug with Tag Quality not reflecting correct quality in first reconnection DDATA message, DDATA message published before DDEATH, and some DBIRTH messages.

eACM 3.0.4.0Edge ACM 2.2.0.0If a single element in an array meets the requirements for an assigned trigger, the quality for the metric will be assigned to that trigger quality.

eACM 3.0.4.0Edge MQTT Publisher 2.0.0.0Adds the ability to compress Sparkplug B Payloads.

eACM 3.0.4.0Edge MQTT Publisher 2.0.0.0Adds a new option labeled "Publish Device Death" to the Advanced Sparkplug tab of a Sparkplug B Publisher. This option enables DDEATH messages to be published when a device is disconnected. Logs will show that a device has been disconnected whether or not this option is enabled. *Effect on Published output: When the "Publish Device Death" option is checked, DDEATH messages will be published when a device is no longer available.

eACM 3.0.4.0Edge MQTT Publisher 2.0.0.0Adds Publishing Schedules to allow specific data to be published through certain MQTT publishers.

eACM 3.0.4.0Edge MQTT Publisher 2.0.0.0Adds an option to use config.ini files in different paths when running MQTT via command line. To view the format for this option, include the flag "-h".

eACM 3.0.4.0Edge MQTT Publisher 2.0.0.0When MQTT is stopped, a DDEATH will be published for every connected device that was being published.

eACM 3.0.4.0Edge MQTT Publisher 2.0.0.0Corrects an issue that prevented MQTT from stopping when not connected to a data source.

eACM 3.0.4.0Edge MQTT Publisher 2.0.0.0Enhanced checks around handling STATE messages in Sparkplug B publisher

eACM 3.0.4.0File Handler 1.0.1.0Adds the ability to associate tag groups with different publish schedules so each tag group can be published at its own rate.

eACM 3.0.4.0File Handler 1.0.1.0Provides the ability to associate a Scanner object with a specific MQTT publisher to publish files via different MQTT publisher objects. A publisher schedule object must already exist in MQTT to use this feature.

eACM 3.0.4.0Priority Forward 2.0.0.1Corrects an issue that prevented the application from starting/restarting.

eACM 2.5.3.1AUTOSOL App Manager 2.5.3.1Adds further compression to serving of UI files

eACM 2.5.3.1AUTOSOL Bridge 2.0.0.4Corrects the display and backfill of DateTime OPC tags

eACM 2.5.3.1AUTOSOL Edge MQTT 1.3.0.2Corrects an issue preventing NDEATHs and DDEATHs from being sent on a clean shutdown

eACM 2.5.3.1AUTOSOL Edge MQTT 1.3.0.2Corrects an issue that caused the app to stop publishing when a rebirth request was received at the same moment a broker disconnect occurred.

eACM 2.5.3.1Edge ACM 2.1.0.1Adds validation to ensure no duplicate tags exist in a device across multiple tag groups

eACM 2.5.3.1Edge ACM 2.1.0.1Corrects an issue that caused an incorrect timestamp to occasionally appear in log files

eACM 2.5.3.1Edge ACM 2.1.0.1Corrects an issue where changing mac addresses would cause the current license to be invalid

eACM 2.5.3.0AUTOSOL App Manager 2.5.3.0App Manager now supports TLS MQTT for configuration

eACM 2.5.3.0AUTOSOL App Manager 2.5.3.0With this, a new file property has been implemented. You can now upload small files like certificates.

eACM 2.5.3.0AUTOSOL App Manager 2.5.3.0Future versions will implement the file property in other file related configuration settings.

eACM 2.5.3.0Azure 1.1.0.1Added ability to publish 64-bit and datetime tags

eACM 2.5.3.0Azure 1.1.0.1Updated certificates for authentication

eACM 2.5.3.0Edge ACM 2.1.0.0Added ability to publish communication statistics for end devices

eACM 2.5.3.0Edge ACM 2.1.0.0Quality update messages now sent through internal tag sockets

eACM 2.5.3.0Edge MQTT Publisher 1.3.0.0Added ability to publish data from multiple data source applications

eACM 2.5.3.0Edge MQTT Publisher 1.3.0.0Added ability to publish quality data for tags in Sparkplug B metrics

eACM 2.5.3.0Edge MQTT Publisher 1.3.0.0Added ability to send DDEATH messages when an end device is disconnected

eACM 2.5.3.0Edge MQTT Publisher 1.3.0.0MQTT Start/Stop/Restart script updated to stop the application in a safer way

eACM 2.5.3.0File Handler 1.0.0.0Allow users to publish any files over MQTT in base64 format. These can be resolved as images by some client applications or converted back to a file.

eACM 2.5.3.0File Handler 1.0.0.0Individual scanner objects each monitor a single folder for new files

eACM 2.5.3.0File Handler 1.0.0.0Files are published via the Edge MQTT Publisher app

eACM 2.5.3.0File Handler 1.0.0.0Files beyond a specified maximum are removed to avoid infinite growth from the uploading service(s)

eACM 2.4.2.1AUTOSOL Edge MQTT 1.2.0.1Corrects an issue with 8-bit signed and unsigned writes

eACM 2.4.2.1Edge ACM 2.0.0.6Corrects an issue with Modbus double and character writes on 64-bit systems

eACM 2.4.2.1Edge ACM 2.0.0.6Corrects an issue in updates after writes where value was within Deadband

eACM 2.4.2.1Edge MQTT Publisher 1.2.0.2Corrects an issue where certain configurations could lead to null DDATA messages being sent

eACM 2.4.2.1Edge MQTT Publisher 1.2.0.2Corrects metric aliasing to better fit Sparkplug B standard

eACM 2.4.2.0AUTOSOL App Manager 2.4.2.0Corrects an issue which could cause Edge ACM to fail to generate the license request file when no config data was present

eACM 2.4.2.0AUTOSOL App Manager 2.4.2.0Corrects issues with the install process on the IQ platform

eACM 2.4.2.0AUTOSOL App Manager 2.4.2.0Corrects issues with dependencies on latest cryptography module

eACM 2.4.2.0Edge ACM 2.0.0.5Adds write verification poll

eACM 2.4.2.0Edge ACM 2.0.0.5Corrects an issue where updates were not sent on return to normal quality

eACM 2.4.2.0Edge MQTT Publisher 1.2.0.0Adds the ability to publish arrays in three different formats

eACM 2.4.2.0Edge MQTT Publisher 1.2.0.0Adds the ability to send all NULL values in DBIRTH messages

eACM 2.4.2.0Edge MQTT Publisher 1.2.0.0Updates publishing to ensure backfill data is always published in chronological order

eACM 2.4.2.0Edge MQTT Publisher 1.2.0.0Corrects an issue with backfill files not being created if directory is within one step of the root folder

eACM 2.4.2.0Edge MQTT Publisher 1.2.0.0Corrects an with backfill files breaking if the tag name had a forward slash

eACM 2.4.2.0Edge MQTT Publisher 1.2.0.0Corrects an issue with backfill not working if “Serialized Publishing” was enabled

eACM 2.3.1.0AUTOSOL App Manager 2.3.1.0Tree search was added.






eACM 2.3.1.0AUTOSOL App Manager 2.3.1.0Collapse tree was added.

eACM 2.3.1.0AUTOSOL App Manager 2.3.1.0Corrects an issue with how the tree and item views scrolled and overlapped

eACM 2.3.1.0AUTOSOL App Manager 2.3.1.0Corrects issues that caused items to be orphaned after an import to a folder.

eACM 2.3.1.0Edge ACM 2.0.0.4‘Alias’ property on Tag objects changed to ‘Name'

eACM 2.3.1.0Edge ACM 2.0.0.4The Tag CSV files from previous versions will need to be manually updated so that the column header says ‘Name’ before importing into this latest version.

eACM 2.3.1.0Edge ACM 2.0.0.4Corrects an issue with Modbus RTU register set

eACM 2.3.1.0Edge ACM 2.0.0.4Corrects an issue with Custom Modbus register sets

eACM 2.3.1.0Edge ACM 2.0.0.4Corrects an issue with polling String tags from Modbus OMNI

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Implemented Verbose logging

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Adds the ability to include timestamp in current data metrics

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Corrects Sparkplug B sequencing issue that could arise when multiple devices published rapidly

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Corrects issue where backfill files were being created for tags where backfill was not enabled

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Corrects an preventing backfill files from being created if there were forward slashes in the tag name

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Corrects an issue that could cause Edge MQTT Publisher to crash if the initial values for tags was null data

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Corrects an issue where null initial tag data was being published as zeros instead of null

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Adds verification to make sure Keep Alive is never set below 5 seconds

eACM 2.3.1.0Edge MQTT Publisher 1.1.0.0Corrects an issue with Sparkplug B STATE message decoding

eACM 2.2.1.1Edge ACM 2.0.0.3Corrects an issue that prevented logs from rotating at 1mb

eACM 2.2.1.1Edge ACM 2.0.0.3Corrects an issue where the app would stop publishing when flooded with rebirth requests

eACM 2.2.1.0AUTOSOL App Manager 2.2.1.0HTTPS can now be enabled and disabled on the webserver. HTTPS is disabled by default.

eACM 2.2.1.0AUTOSOL App Manager 2.2.1.0Adds the ability to log in with a username and password. The default is admin/admin.

eACM 2.2.1.0AUTOSOL App Manager 2.2.1.0Corrects an issue with tag groups and how the file is loaded.

eACM 2.2.1.0AUTOSOL App Manager 2.2.1.0Changes the wording on the App Manager connection status for clarity.

eACM 2.1.0AUTOSOL App Manager 2.1.0AUTOSOL App Manager can now manage AUTOSOL Bridge

eACM 2.1.0AUTOSOL App Manager 2.1.0You can now delete log files from the Log Viewer page.

eACM 2.1.0AUTOSOL App Manager 2.1.0App Manager now supports configuration object commands

eACM 2.1.0Edge ACM 2.1.0Edge ACM and Edge MQTT Publisher have better start up validation in order to prevent false start ups.

eACM 2.1.0MultiplePing target (ipv4) has been implemented in Connection objects across different applications

eACM 2.0.3Edge MQTT PublisherFixed memory leak issue in Edge MQTT Publisher Sparkplug B Publisher

eACM 2.0.3Edge MQTT PublisherFixed issue in Edge MQTT Publisher where subscriptions were lost by broker after a broker restart

eACM 2.0.3Edge MQTT PublisherFixed issue in Edge MQTT Publisher where back fill to disk could corrupt a file if power loss occurs during write

eACM 2.0.0AUTOSOL App Manager 2.0.0In 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.0AUTOSOL App Manager 2.0.0Communication between the Universal and Edge Managers is now exclusively through the MQTT protocol.

eACM 2.0.0AUTOSOL App Manager 2.0.0Edge 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.0AUTOSOL App Manager 2.0.0Both 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.0AUTOSOL App Manager 2.0.0Multiple 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.0AUTOSOL App Manager 2.0.0The 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.0AUTOSOL App Manager 2.0.0System 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.0AUTOSOL App Manager 2.0.0Log Viewer now has a way to download all log files from the system in a zipped archive format.

eACM 2.0.0Azure 1.0.0Azure application has been released with version 1.0.0

eACM 2.0.0Azure 1.0.0Azure publishes Edge ACM device item updates on a report-by-exception basis to Azure IoT Hub via Device-to-Cloud telemetry

eACM 2.0.0Azure 1.0.0Azure writes to Edge ACM device items when a write request is received via Azure IoT Hub Cloud-to-Device messages

eACM 2.0.0Edge ACM 2.0.0Edge 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.0Edge MQTT Publisher 1.0.0New ability to publish as multiple nodes from single device

eACM 2.0.0Edge MQTT Publisher 1.0.0Support for MQTT TLS added

eACM 2.0.0Edge MQTT Publisher 1.0.0Support for MQTT Protocol Version 5 added

eACM 2.0.0Edge MQTT Publisher 1.0.0Added ability to set custom Client ID on broker connections

eACM 2.0.0Edge MQTT Publisher 1.0.0Advanced timing options added

eACM 2.0.0Edge MQTT Publisher 1.0.0Primary Host ID functionality added

eACM 2.0.0Edge MQTT Publisher 1.0.0Added ability to back fill data to disk upon connection loss or primary host disconnect

eACM 2.0.0Edge MQTT Publisher 1.0.0Added ability to split back fill messages with a set number of values per tag

eACM 2.0.0Edge MQTT Publisher 1.0.0Added ability to hard code a delay time between births

Out of Maintenance Releases

 Click here to expand...

Release

Category

Text

eACM 1.0.0AUTOSOL App Manager 1.0.0System information now shows the versions of the applications installed.
eACM 1.0.0AUTOSOL App Manager 1.0.0Data models now support multiple references to other data models.
eACM 1.0.0AUTOSOL App Manager 1.0.0Partial imports are now supported.
eACM 1.0.0AUTOSOL App Manager 1.0.0Preliminary backwards compatibility modifications were implemented.
eACM 1.0.0AUTOSOL App Manager 1.0.0The new import.log will show what items were modified.
eACM 1.0.0AUTOSOL App Manager 1.0.0If a data model changes, App Manager can import most of the configuration.
eACM 1.0.0AUTOSOL App Manager 1.0.0An uninstaller has been added.
eACM 1.0.0Edge ACM 1.1.0You can now download an empty CSV header file from a Tag Group in Edge ACM.
eACM 1.0.0Edge ACM 1.1.0Support for fully custom Modbus register sets has been added.
eACM 1.0.0Edge ACM 1.1.0Added 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.0Edge ACM 1.1.0Devices now support multiple tag groups.
eACM 1.0.0Priority Forward 2.0.0Priority Forward has been updated to version 2.0.0
eACM 1.0.0Priority Forward 2.0.0Connections have been renamed to Channels and now support advance settings.
eACM 1.0.0Priority Forward 2.0.0The priority client can be delayed from forwarding until after a millisecond configured timeout.
eACM 1.0.0Priority Forward 2.0.0Connection retries and retry intervals from the Priority and Secondary down to the end device are now configurable.
eACM 1.0.0Priority Forward 2.0.0Priority Forward logs are much more descriptive and useful.


For assistance, please submit a ticket via our Support Portal, email autosol.support@autosoln.com or call 281.286.6017 to speak to a support team member.