Foreign IP connections no longer require a username and password to be entered when defining a site.The Memory usage being reported on the Device Status page is now correct.Corrected an issue where samples could be missed if there are non-sequential sequence numbers across day-buckets.Corrected an issue where some Trend Logs collected by the CopperCube would not be transmitted to the Kaizen Vault.In cases where device backups cannot be saved (password protection, etc.), an empty backup.Data from eBMGR devices will now be archived properly.The archiver will now properly collect Trend Log data for Trend Logs that do not support the Log Interval property.A number of changes were made to reduce the chance of incomplete objects being archived and sent to CopperTree Vault.Issues with collecting complete sets of object properties have been corrected.The CopperCube will now automatically exclude attempting to collect data from OWS, Historian, enteliWEB, and other CopperCubes.These are related to specific scenarios and not a general issue. Fixed a number of bugs where Trend Logs would not be collected properly.Issues Fixed in CopperCube 1.06 Infrastructure The Help documentation has been updated to include information on how to set up a CopperCube to begin collecting data.More severe error messages will be kept longer. Error logs will be auto-pruned depending on the severity.The Diagnostics logs have been updated to provide more relevant information.The content of the Diagnostics Log page can be filtered based on.Error Log page has been renamed to Diagnostics Logs.Additional detailed information is also included.Total number of Trend Logs, Trend Logs being archived and in Error on each device.Connection test information including status and last test timeī.Number of Trend Logs that are being archived.Number of Trend Logs discovered on the site.It contains the following informationĪ.Status of each of the different sites the CopperCube is collecting data from. A new Sites & Device Status page has been created.A request may be made to send the full recorded history of the Trend Log data for selected TLs to either the Kaizen Vault or SQL connector.The Status and Usage Summary data will be updated every 5 seconds.New information on each trend log is available in the Trend Log management table:.License Size (maximum number of Trend Logs that are allowed to be collected).Number of Trend Logs that are being collected.Total Trend Logs that are known about by the CopperCube.Status and Usage Summary has been updated to now include:.Multiple Trend Logs can be simultaneously configured with the same common settings.The Trend Log Management user interface has been redesigned to allow custom configuration of Trend Log collection parameters.The Trend Log Management page now includes instructions on how to select Trend Logs for archiving.This can be modified in the Settings > Sites and Device Ranges page. COV Min Buffer Size configuration default has been set to 20.This option is available on the Settings > Data Destinations page. Auto Archive Trend Logs functionality is now available.Site and Device Ranges setup has been collected into one page for easier configuration and examination of the settings.This will provide a more accurate result. Internet Latency information has been replaced with Uplink Status information.The Device Status page will now automatically update every 15 seconds.This functionality is accessed through the Settings > Backup and Restore page. The backup data can then be restored to the same or a different CopperCube. New Backup/Restore functionality has been introduced to allow the backup of CopperCube data and settings to an external USB device.Heartbeat information is being transmitted in HTTPS protocol.Trend Log and other data are transmitted using a secure SSL protocol.This information will be reflected in the Kaizen Device Monitoring features. Heartbeat information being sent from the CopperCube to the CopperTree Vault has been updated to include the Site list, device ranges, and latency.If selected, the user will no longer have to specifically identify which new Trend Logs will be archived by the CopperCube. A new option to automatically collect new Trend Logs has been implemented.Please see Kba0007 for details Infrastructure *Ports* The internet ports used by the CopperCube have changed. This version also fixes some minor issues within the CopperCube V1.04The CopperCube 1.06 has been released the. The CopperCube firmware V1.06 provides a more friendly user interface and add some new features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |