| Info |
|---|
Information about eACM Security can be found: SEC |
| Table of Contents |
|---|
Releases In Active Maintenance
*Use the "shift" key to sort by multiple columns.
Release | Application | Text | Affects Published Output | Addresses Security Vulnerability |
|---|---|---|---|---|
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 | Adds |
the ability to select one or more cells within a single column in the multi-edit table and modify all selected items at once. | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Moved Data Viewer logging out of info.log to aid in troubleshooting | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 | Adds |
an error message on the site when PostgreSQL is offline | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Creating new metadata properties with default values will update existing tags | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Applications now restart after a .deb upgrade or upon running the restart script | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 | Adds |
the ability to Get Data and make Demand requests from the Data Explorer Tree view | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
- The ability to delete objects from the tree when the objects is selected and the delete key is pressed.
- The ability to drag and drop objects in the tree.
- The ability to reorder tabs in App Manager.
- The ability to save by clicking Enter.
- The ability to open the properties for an object in the tree by holding the "Ctrl" key and clicking on the object.
- The ability to restart an app (Edge ACM, Priority Forward, etc) by the keyboard shortcut Ctrl + R.
- The ability to add objects to the tree directly from the Object view.
Various usability improvements | ||||
eACM 3.6.6.0 | App Manager 3.6.5.0 | AAM now supports folders. | ||
eACM 3.6.6.0 | App Manager 3. |
6.5.0 |
Node settings are now restored when importing a JSON configuration for a node | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Double-clicking on a node in AAM for the first time will sync it | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
The Web UI now provides access to remote Edge servers. | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Adds ability to set default node name to device IP via defaults.ini | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Child Object Tools moved from the General tab to a new tab to reduce clutter | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Corrects an issue where excel imports ignored items with invalid parent references. Invalid parent references now get set to an existing valid item in the imported data. | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Adds visible border around group option lists to better detect top and bottom of scrollable areas | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Apps now have an collapsible icon on page load that displays only when they have child config objects | ||
eACM 3. |
6. |
6.0 | App Manager 3. |
6.5.0 |
Corrects an issue in the Data Viewer that caused date/time values to be displayed a month earlier than they actually are | ||
eACM 3. |
6. |
6.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.
- 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.
- Sets the device limit to 1.
- Sets the maximum number of tags for the device to 100.
Adds a script to remotely reboot edge devices.
Out of Maintenance Releases
...
Release
...
Category
...
Text
...
App Manager 3.6.5.0 | Corrects bug with AppManager's MQTT broker not connecting | |||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Corrects an issue where some commands would display the wrong action in the request tracker | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Corrects an issue that caused Priorities in Tag Trigger conditions to be out of order | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Third party frontend web app security fixes
| X | |
eACM 3.6.6.0 | App Manager 3.6.5.0 | Corrects an issue that prevented reading request errors when the error count was larger than 3 | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | If Verbose Logging is enabled and the app crashes, create a crash dump file | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Menus in trees are now more responsive in smaller displays | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Rows in array properties, like Meters, can now be displayed as a single form view in place for better editing | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Adds explicit versioning for AUTOSOL shared library files that ship with eACM | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Corrects table sorting for Boolean properties | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Allows pre-built Container installs to use Ping | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | App Manager now shows the path to the item opened in the config tab | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Service changes (Start/Stopped) from a user in the configuration site are now logged | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Licenses are now validated on upload | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Adds collapse button for the App Manager Requests/Logger panel. | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Corrects an issue where a restart would incorrectly set the status of an app in App Manager. | ||
eACM 3.6.6.0 | App Manager 3.6.5.0 | Disabled automatic handling of duplicate nodes by AAM | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Updated Edge ACM Validation. Devices that can have meters now support a combination of meters and tag groups to start. | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Provides the ability to establish a specific start time with an interval for polling. | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | License Validation issues/errors are now presented in error messages from Edge Manager | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Adds DNP3 protocol to eACM | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Adds DF1 protocol to eACM | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Adds EFM support for Totalflow protocol to eACM | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Changes logging for new protocols (ROC, DNP3, etc.) such that each object logs to its own file | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects memory leaks if license file is missing and a request file is created | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Edge DNP3 protocol fixed to update item value and quality correctly after a write. | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | The SecondsSinceComplete correctly increments by 1 every second until there's a successful poll, then it resets back to 0 | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | LastPollSuccessTime will not be updated for a Modbus device in edge on a failed poll | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects problem with DNP3 tags that use indexes | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | A description field has been added to the objects in eACM | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Edge ACM will not fall behind the expected polling interval | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects issue with bit access output being type int32 rather than Boolean | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects issue where, sporadically, writes to Modbus registers would use offset from base rather than full register value when using custom register sets | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Removes segmentation fault on shutdown if duplicate connections contain a duplicate IP address. Logs an error if duplicate IP addresses exist in the connections | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects issue that would cause Edge ACM to slowly reply to the stop command | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects eACM connection so that if the socket reports an internal error the socket close operation is thread safe and no longer crashes intermittently | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects eACM to open the connection whenever a Demand Poll is executed when Release When Done is configured | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects ROC protocol and TimeSync library so that eACM no longer halts on newer versions of Ubuntu/Debian when it tries to load the system timezone database. | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects issue where errors would be logged when using "Release When Done" option on Connection Settings objects | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Allows ROC devices to publish certain tags with an integer date as human-readable string | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | 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 | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Adds extra information to Modbus RX error logs so that developers have more information to fix when they arise | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects the order of the protocol options for a ROC device, so that the user is modifying the correct settings | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects Issues with Demo Mode | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects issue that incorrectly tried to convert floating point NaN value to JSON | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Sanitizes the names of objects before creating a log file with that object's name | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Adds connection specific logging options to eACM and correct other logging issues | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | CIP Messages now contain vendor information | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects issue with polling String tags in CIP protocol | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Edge ACM now only releases the connection when the shared device user count of that connection drops to 0 instead of releasing the connection when the first device user reports bad communications | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Corrects issue where only one CIP string tag would update if multiple string tags, in the same tag group, shared the same register | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Users can create virtual tags, and read and write them through ZeroMQ ipc sockets | ||
eACM 3.6.6.0 | Edge ACM 3.3.0.0 | Calculation Tag objects have been added to eACM. Currently, the calculation tag operation is limited to averaging data from a selected register over a unique interval. Any data polled on the register during this interval will be included in an average value calculation. All good quality polls collected during the interval are included in the calculation, and bad quality polls are ignored from the calculation. | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | MQTT Backfill data is now stored using a SQLite database.
| ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Provides the ability to establish a specific start time for publishing MQTT messages | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Implements the new property Publish group ID for EFM Data | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Adds the ability to set a custom write topic on JSON publishers | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Updated labels on publish schedules to clarify settings | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Adds option to Sparkplug publisher objects that will sync current metric timestamps to the payload timestamp in DBIRTH messages | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | The JSON Device Publisher and JSON Tag Publisher now support the ability to format the Timestamp as a Date/Time string combination | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Corrects issue where two updates would come back for a tag that was written to | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Corrects issue where entire device could be marked as offline when just a few tags failed to poll | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Misconfigured trigger conditions are now logged with more detail | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Corrects issue where MQTT would not subscribe to topics if it did not cleanly connect | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Corrects the MQTT app so that Batch records publish correctly | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Allows tag updates that were not published to be backfilled into a database, allowing them to be published in the future | ||
eACM 3.6.6.0 | Edge MQTT Publisher 2.7.0.0 | Removed timestamps from tags with null values | ||
eACM 3.6.6.0 | File Handler 1.4.1.0 | File Handler now operates without an additional license | ||
eACM 3.6.6.0 | asiBridge | Corrects issue where Bridge could crash when writing to edge nodes that do not have Aliased enabled | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds a user interface for managing metadata properties for a tag. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Disabled objects in the tree will now be represented by a different icon to show they are disabled. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds the ability to sort children tables. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds the property description as a tool tip for the column headers in the multi-edit table. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Removes the square icon from a column header if the column is not expandable. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds a setting to the dashboard that enables the user to hide and display apps. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds multiple hot keys and short cuts to the user interface:
| ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds the ability to view App Manager in "Dark Mode". This can be set under "Personalization" in the "Account" settings. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds the ability to import individual objects | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds the ability to import objects that are deeper than the root level. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Updates the name of the web browser tab to match the node name. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Improves Excel imports with nested references. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds the ability to export all objects within an App to Excel. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Logs all changes made to objects in the objects.log file accessible from the Log Files tab. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds the ability to view an object's change log by clicking the "View Logs" option in the right-click menu. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds a logger for Edge nodes that allows for viewing changes in real-time. | ||
eACM 3.5.5.0 | CPU Statistics 1.0.0.0 | Adds 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.0 | Edge ACM 3.1.0.0 | A 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.0 | Edge ACM 3.1.0.0 | A "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.0 | Edge 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.0 | Edge ACM 3.1.0.0 | Adds a 'demo mode' to eACM, which runs for a limited time (2 hours) and with limited functionality. The limited functionality is as follows:
| ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Adds 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.0 | Edge MQTT Publisher 2.4.0.0 | Adds 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.0 | Edge MQTT Publisher 2.4.0.0 | Provides 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.0 | Edge MQTT Publisher 2.4.0.0 | Adds the ability to set the QoS per tag group. | ||
eACM 3.5.5.0 | Edge MQTT Publisher 2.4.0.0 | Adds the ability to assign redundant brokers to publisher objects. | ||
eACM 3.5.5.0 | Installer | Adds a "defaults.ini" file in which default values for node names and broker connection settings can be stored. | ||
eACM 3.5.5.0 | Installer | AppManager can now be installed on Debian 12. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Modifies the timestamp format in the Data Viewer to "mm/dd/yyyy HH:MM:SS:fff". | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Adds a full App view, allowing all device data to be visible in one table. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Corrects an issue that prevented module updates or a restarts in the Software Update page from showing notification or statuses. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Corrects a performance issue with large amount of objects in the explorer view. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Corrects an issue that prevented web urls from formatting correctly in a Node's info tab. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Corrects an issue that caused tags to be displayed in the tree. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Prevents an issue that prevented tags from importing when the tag group IDs were too short. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | eEFM can be collected and published in containerized environments. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Corrects an issue when selecting 2bytes as the addressing type on Modbus device objects. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Prevents an issue with multiple remote commands from being sent to a node. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Corrects an issue where changes to a file property would not mark an item as changed. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Corrects 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.0 | App Manager 3.5.5.0 | Moves the log files to the correct directory. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | AAM 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.0 | App Manager 3.5.5.0 | Modifies AAM so it will handle Edge nodes that were created by duplicating a node. | ||
eACM 3.5.5.0 | App Manager 3.5.5.0 | Provides the ability to manually generate an Edge Node's Node Id, Related App Id and Object Ids. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | eACM and MQTT will use the configuration setting in config.ini as the EFM database connection string for records and reporting. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Improves the error messages logged when reading files from an outside source, such as when a license file is malformed. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Prevents a memory leak in GE SRTP protocol. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Corrects an error that could occur when a TCP connection is used with newer protocols. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Corrects an issue that caused an unnecessary delay in polling after a communication timeout. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Prevents the ROC protocol from casting written values to integers before being sent to the ROC device. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | DDEATH 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 MQTT | X | |
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Corrects an issue with eACM license validation between installations. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Corrects 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.0 | Edge ACM 3.1.0.0 | Replaces the tacopie TCP Client/Server library with Boost.Asio. tacopie has reached its end of maintenance. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Corrects an issue that caused the ROC protocol response timeout setting to be ignored. | ||
eACM 3.5.5.0 | Edge ACM 3.1.0.0 | Improves polling performance for the ROC protocol. | ||
eACM 3.5.5.0 | Edge MQTT Publisher 2.4.0.0 | Corrects an issue that caused some data to be missing from one publisher when more than one publisher was enabled. | X | |
eACM 3.5.5.0 | Edge MQTT Publisher 2.4.0.0 | Corrects the Node.bdSeq tag value to increment by 1 on each MQTT connect. | ||
eACM 3.5.5.0 | Edge MQTT Publisher 2.4.0.0 | Lowers the CPU consumption of MQTT. | ||
eACM 3.5.5.0 | Edge MQTT Publisher 2.4.0.0 | The 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.0 | Edge MQTT Publisher 2.4.0.0 | Modifies 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.0 | File Handler 1.3.1.3 | Adds text file support to File Handler. | ||
eACM 3.5.5.0 | Installer | The installer will now install the correct version of the software according to the given OS configurations. | X | |
eACM 3.5.5.0 | OPC UA 1.4.0.0 | Removes the "License" tab from the OPC UA application as one is not required. | ||
eACM 3.4.5.0 | Edge ACM 3.0.0.0 | Users can select between eACM maintaining a connection to a port or releasing that connection after a device has stopped polling. | ||
eACM 3.4.5.0 | Edge ACM 3.0.0.0 | Adds the ability to poll EFM data via the ROC Protocol. | ||
eACM 3.4.5.0 | Edge MQTT Publisher 2.3.0.0 | Adds a command to connect with encrypted brokers | ||
eACM 3.4.5.0 | App Manager 3.4.5.0 | Corrects an issue where moving an item in the tree would not display the item location correctly. | ||
eACM 3.4.5.0 | App Manager 3.4.5.0 | Corrects an issue that allowed circular references in the tree, thus hiding objects from displaying. | ||
eACM 3.4.5.0 | App Manager 3.4.5.0 | Corrects issue with displaying 0/False tag values in Data Viewer | ||
eACM 3.4.5.0 | App Manager 3.4.5.0 | Corrects 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.0 | asiBridge | Bridge can process backfill data in birth messages. | ||
eACM 3.4.5.0 | Edge ACM 3.0.0.0 | Modbus 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.0 | Edge ACM 3.0.0.0 | Corrects an issue that prevented the Edge ACM license request from being downloaded correctly. | ||
eACM 3.4.5.0 | Edge ACM 3.0.0.0 | Schedule objects have been replaced by Interval objects | ||
eACM 3.4.5.0 | Edge ACM 3.0.0.0 | Corrects 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.0 | Edge ACM 3.0.0.0 | Adds 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.0 | Edge MQTT Publisher 2.3.0.0 | Corrects 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.0 | AUTOSOL App Manager 3.0.4.0 | Corrects an issue with the save function shortcut. | ||
eACM 3.0.4.0 | AUTOSOL App Manager 3.0.4.0 | Corrects an issue that could cause tag groups to be unlinked from device objects after an import of tags. | ||
eACM 3.0.4.0 | AUTOSOL Bridge 2.1.1.2 | Prevents unknown characters from being added to end of STATE messages. | ||
eACM 3.0.4.0 | AUTOSOL Bridge 2.1.1.2 | Corrects a timestamp issue with asiBridge commands | ||
eACM 3.0.4.0 | Client Scripts | Adds a script to remotely reboot edge devices. | ||
eACM 3.0.4.0 | Client Scripts | Adds a script for remote collection of logs from field devices. | ||
eACM 3.0.4.0 | Client Scripts | Adds a script to remotely start the core apps on multiple devices. | ||
eACM 3.0.4.0 | Client Scripts | Adds a script to resolve duplicate Node IDs caused by cloning Edge systems. | ||
eACM 3.0.4.0 | Client Scripts | Corrects an issue that prevented apps from restarting after an import script completes. | ||
eACM 3.0.4.0 | Client Scripts | Improves logging when an import script starts or stops an app. | ||
eACM 3.0.4.0 | eACM 3.0.4.0 | Edge ACM is now available for ARM32, ARM64 and AMD32 | ||
eACM 3.0.4.0 | Edge ACM 2.2.0.0 | Adds 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.0 | Edge ACM 2.2.0.0 | Modifies SparkplugB Aliases so that they are incremental. e.g. [0,1,2,3,...] rather than [0,3,5,6,...]. | ||
eACM 3.0.4.0 | Edge ACM 2.2.0.0 | Adds 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.0 | Edge ACM 2.2.0.0 | Provides 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.0 | Edge ACM 2.2.0.0 | Adds an option to the Edge ACM properties tab to validate a license that has been uploaded through the UI. | ||
eACM 3.0.4.0 | Edge ACM 2.2.0.0 | Adds 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.0 | Edge ACM 2.2.0.0 | Adds 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.0 | Edge ACM 2.2.0.0 | Tag 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.0 | Edge ACM 2.2.0.0 | Active tags will be updated to show bad quality when Edge ACMis stopped. | ||
eACM 3.0.4.0 | Edge ACM 2.2.0.0 | Corrects 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.0 | Edge ACM 2.2.0.0 | If 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.0 | Edge MQTT Publisher 2.0.0.0 | Adds the ability to compress Sparkplug B Payloads. | ||
eACM 3.0.4.0 | Edge MQTT Publisher 2.0.0.0 | Adds 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.0 | Edge MQTT Publisher 2.0.0.0 | Adds Publishing Schedules to allow specific data to be published through certain MQTT publishers. | ||
eACM 3.0.4.0 | Edge MQTT Publisher 2.0.0.0 | Adds 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.0 | Edge MQTT Publisher 2.0.0.0 | When MQTT is stopped, a DDEATH will be published for every connected device that was being published. | ||
eACM 3.0.4.0 | Edge MQTT Publisher 2.0.0.0 | Corrects an issue that prevented MQTT from stopping when not connected to a data source. | ||
eACM 3.0.4.0 | Edge MQTT Publisher 2.0.0.0 | Enhanced checks around handling STATE messages in Sparkplug B publisher | ||
eACM 3.0.4.0 | File Handler 1.0.1.0 | Adds 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.0 | File Handler 1.0.1.0 | Provides 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.0 | Priority Forward 2.0.0.1 | Corrects an issue that prevented the application from starting/restarting. |