#Coppercube and firebase how to
#Coppercube and firebase update
#Coppercube and firebase archive
#Coppercube and firebase full

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.

#Coppercube and firebase how to

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.

#Coppercube and firebase archive

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.

#Coppercube and firebase update

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. Auto resume capable, if configured.The CopperCube firmware V1.06 provides a more friendly user interface and add some new features. Generates TL Archival Buffer notificationsĭependent on host's configuration. Supports operating in redundant mode (each unit collecting the same data) and load sharing mode (each unit collecting different data).ĬopperTree Kaizen, SQL server (MySQL, MS-SQL, PostgreSQL).Ĭloud-server based auto-update. Parallel operation (multiple units on same network) Supports simultaneous data collection from multiple BACnet networks (local and remote).

Relies on host database system (MySQL, MS SQL, Backup) and/or Windows backup utilities.īuilt in backup and restore solution to external USB disk. Push data: via send to CopperTree Kaizen Vault, and send to external SQL server Pull data: via ODBC, direct SQL Queries and BACnet ReadRange services Secondary: Coppertree Kaizen and enteliWEBĬoppertree Kaizen, enteliWEB, CopperCube GUI Primary: built-in web-based GUI (configuration). BACnet Objects, BACnet Events and BACnet Controller Database backups. Either installed alongside controllers (and powered with 24 VAC) or in any location with standard wall outlet (and powered with 120/240 VAC).īACnet Trend logs, BACnet Events, BACnet Access Control Events Typically, one instance, located in a central IT location.įlexible. IT based (requires a Windows computer or Virtual Machine). User supplies host computer and host Database. If you need more clarification about any of these features, please contact us at of Product The table below outlines the differences in the feature sets offered by CopperCube and Historian.