Coppercube update#
Coppercube archive#

Pending Delete: The trend log is being processed, and upon completion, it will be deleted.This is an internal CopperCube error, please contact the Customer Solutions team. Error: Invalid Ref: The Trend Log Reference (“//Site/8002/TL.1”) is invalid.

Coppercube archive#

Error: Max Number of TLs: You reached the maximum number of trend log that your current CopperCube license allows you to archive.

(In order to reinitialize the TL, follow the instructions here)

Coppercube update#

Error: Failed to Initialize: The CopperCube failed to update the trend log information.

Error: Invalid Type: Undefined error, please contact the Customer Solutions team.

Error: No Monitored Object: The CopperCube failed to identify the monitored object for the trend log.

The buffer time size is calculated for each trend log by calculating: buffer size times trend log polling frequency.

For a polled Trend Log, the minimum buffer size is set up to 3600 seconds (one hour) by default.

For a COV Trend Log, the minimum buffer size is set to 20 samples by default.

Error: Buffer Too Small: The controller buffer size is too small.

By default, the maximum polling sample frequency is 86,400 seconds (minimum of one sample every day) any TL with a polling frequency of more than 1 day will not be archived by the CopperCube.

Error: Too Slow: The controller is trending samples too slow.

By default, the minimum sample polling frequency is 60 seconds (maximum of one sample every minute) any TL with a polling frequency less than 1 min will not be archived by the CopperCube.

Error: Too Fast: The controller is trending samples too fast.

Not Archived: The trend log is not archived on purpose.

This can be due to the trend no longer existing on the BAS, the site no longer existing on the Cube, the device being added to the exclusion range, or the device no longer being included in the inclusion range.

Detached: A trend log that was once archiving, but is no longer available.

Offline: The trend log is currently not available.

Archiving: The trend log is currently being archived by the CopperCube.

This status is usually not displayed because the processing time for each new trend log is really quick.

New TL: The trend log has been detected by the CopperCube and will be processed as soon as possible.

The CopperCube will update it as soon as possible.

Not Initialized: The current trend log information is out of date in the CopperCube.

Managing Historical Data: Historical data on the CopperCube can be immediately sent to the CopperCube Vault and/or the SQL Connector using this feature.įor each Trend Log, the CopperCube provides the current status depending on the state as below:.

Data Pruning (delete data older than a defined period).

Trend Log Settings: The Trend Log Settings tool provides the user the ability to apply archiving settings to the selected trend logs.

All the archived trend logs will be sent to the cloud.

Archive trend logs: The TL Management feature allows the user to archive the trend logs that are found by CopperCube.

This function is possible through this feature.

Select/unselect trend logs manually: Some users might find it useful to select/unselect trend logs manually.

Automatic Trend Log Archiving: If this feature is selected (currently on the Sites and Device Ranges page), all collected Trend Logs will be automatically archived after you add a device range.Filter trend logs: The user has the ability to filter the trend logs based on the site name, device range, trend Log range, archiving status, and trend status.The device number, monitored object, trend log number, trend log name, trend log status, trend log type, and the time before the next update can be seen for each listed trend log. View trend log information: The Trend Log Management page provides the user with a list of all the trend logs collected by CopperCube.The Trend Log Management feature includes the following: These trend logs can then be managed through the Trend Log Management feature. Once the network connection has been established between the CopperCube and the network, the CopperCube lists all the trend logs from the device ranges defined in the CopperCube UI. In the CopperCube UI, under Data, the user can select and manage the trend logs that need to be archived. The archived trend logs will then be transmitted from the CopperCube to the secure servers.

Trend Log Management feature helps the user to select the trend logs that need to be archived.

The trend logs and objects from all data acquisition device ranges are collected by the CoppeCube. The CopperCube, when connected to the BACnet, communicates with the devices (controllers) defined in the CopperCube Inclusion Range.