CopperCube Release Note: V1.06

Overview of CopperCube 1.06

The CopperCube firmware V1.06 provides a more friendly user interface and add some new features. This version also fixes some minor issues within the CopperCube V1.04The CopperCube 1.06 has been released the 2014-05-14.

New Features in CopperCube 1.06

 *Ports* The internet ports used by the CopperCube have changed. Please see Kba0007 for details

Infrastructure

Archiver

  • A new option to automatically collect new Trend Logs has been implemented. If selected, the user will no longer have to specifically identify which new Trend Logs will be archived by the CopperCube.

Transmission to Kaizen Vault

  • Heartbeat information being sent from the CopperCube to the CopperTree Vault has been updated to include the Site list, device ranges, and latency. This information will be reflected in the Kaizen Device Monitoring features.
  • Trend Log and other data are transmitted using a secure SSL protocol.
  • Heartbeat information is being transmitted in HTTPS protocol.

Backup/Restore

  • New Backup/Restore functionality has been introduced to allow the backup of CopperCube data and settings to an external USB device. The backup data can then be restored to the same or a different CopperCube. This functionality is accessed through the Settings > Backup and Restore page.

Web User Interface

Device Status

  • The Device Status page will now automatically update every 15 seconds.
  • Internet Latency information has been replaced with Uplink Status information. This will provide a more accurate result.

CopperCube Configuration

  • Site and Device Ranges setup has been collected into one page for easier configuration and examination of the settings.
  • Auto Archive Trend Logs functionality is now available. This option is available on the Settings > Data Destinations page.
  • COV Min Buffer Size configuration default has been set to 20. This can be modified in the Settings > Sites and Device Ranges page.

Trend Log Management

  • The Trend Log Management page now includes instructions on how to select Trend Logs for archiving.
  • The Trend Log Management user interface has been redesigned to allow custom configuration of Trend Log collection parameters. The parameters available are:
  1. Collection Frequency
  2. Prune old data
  3. Archive / do not archive
  • Multiple Trend Logs can be simultaneously configured with the same common settings.
  • Status and Usage Summary has been updated to now include:
  1. Total Trend Logs that are known about by the CopperCube
  2. Number of Trend Logs offline
  3. Number of Trend Logs in error
  4. Number of Trend Logs that are being collected
  5. License Size (maximum number of Trend Logs that are allowed to be collected)
  • New information on each trend log is available in the Trend Log management table:
  1. Monitored object
  2. Number of Trend Logs offline
  3. Log type
  4. Next Update
  5. Sample Interval
  6. Total # of Samples
  7. Collection Frequency
  8. Auto-Prune Setting
  9. Most recent errors/warnings
  • The Status and Usage Summary data will be updated every 5 seconds.
  • 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.

Sites & Device Status

  • A new Sites & Device Status page has been created. It contains the following information

A.Status of each of the different sites the CopperCube is collecting data from. The information being shown is:

  1. Connection Status
  2. Connection Type
  3. Number of Trend Logs discovered on the site
  4. Number of Trend Logs that are being archived
  5. Number of devices on the Site
  6. Connection test information including status and last test time

B. Status of each Device on the site. This will show the information:

  1. Device name, number, status, and type
  2. Total number of Trend Logs, Trend Logs being archived and in Error on each device
  3. Additional detailed information is also included.

Diagnostics Logs

  • Error Log page has been renamed to Diagnostics Logs.
  • The content of the Diagnostics Log page can be filtered based on
  1. Timestamp range
  2. Subsystem
  3. Error type
  4. A string search
  • The Diagnostics logs have been updated to provide more relevant information.
  • Error logs will be auto-pruned depending on the severity. More severe error messages will be kept longer.

Help Documentation

  • The Help documentation has been updated to include information on how to set up a CopperCube to begin collecting data.

Issues Fixed in CopperCube 1.06

Infrastructure

Archiver

  • Fixed a number of bugs where Trend Logs would not be collected properly. These are related to specific scenarios and not a general issue.
  • The CopperCube will now automatically exclude attempting to collect data from OWS, Historian, enteliWEB, and other CopperCubes.
  • Issues with collecting complete sets of object properties have been corrected.
  • A number of changes were made to reduce the chance of incomplete objects being archived and sent to CopperTree Vault.
  • The archiver will now properly collect Trend Log data for Trend Logs that do not support the Log Interval property. It will treat the TL as a COV type.
  • Data from eBMGR devices will now be archived properly.

Device Backup

  • In cases where device backups cannot be saved (password protection, etc.), an empty backup .zip file will no longer be sent.

Transmission to Kaizen Vault

  • Corrected an issue where some Trend Logs collected by the CopperCube would not be transmitted to the Kaizen Vault.

Web User Interface

API

  • Corrected an issue where samples could be missed if there are non-sequential sequence numbers across day-buckets

Device Status

  • The Memory usage being reported on the Device Status page is now correct.

CopperCube Configuration

  • Foreign IP connections no longer require a username and password to be entered when defining a site.

Known Issues

The following is a list of significant known issues.

Archiver

  • Auto-exclusion of data collection is applicable to Delta devices as these are the only model names that we are aware of. This problem may show itself again with third-party devices.
  • Collection of Trend Logs and Devices will time out if a second Ethernet site is added.
  • Archiver can lose connectivity to sites when attempting to archive historian Trend Logs.
  • Archiver can crash when modifying Allowed or Restricted list
  • ORS locked controller prevents Archiver from seeing/reading trend logs – even though ORS has all TL set to read and create permissions

Backup / Restore

  • After a database restore, opening some UI menu items will result in a database-locked exception

Web Interface

  • Basic Settings require a specific format for input values.
image_printPrint