Frequently Asked Questions

CopperCube

What is the difference between CopperCube – Small, Medium, Large and Extra-Large?

The difference is in the maximum number of trend logs each model can store:

  • Small (S) – Up to 250 trend logs.
  • Medium (M) – Up to 1,000 trend logs.
  • Large (L) – Up to 2,500 trend logs.
  • Extra Large (XL) – Up to 5,000 trend logs.

What does the CopperCube collect?

The CopperCube collects trend logs and stores them in its internal database. These trend logs are then forwarded to the CopperTree Vault, where they can be consumed by Kaizen or other applications via CopperTree’s APIs.

Besides collecting trend logs, what else does the CopperCube collect?

The CopperCube also collects a selection of BACnet objects and their properties as well as BACnet device backups. These however are not stored inside the CopperCube but rather forwarded to the CopperTree Vault.

Does the CopperCube begin collecting all BACnet trend logs automatically?

No. The user needs to specify which trend logs will be collected and stored from a list of trend logs generated by CopperCube during its network discovery process. As of version 1.6 (May 2014) users have the choice of a) allowing the CopperCube to automatically collect all the trend logs it discovers, or b) manually specifying exactly which trend logs it shall collect.

Does the CopperCube begin collecting BACnet objects automatically?

Yes. Provided the other components of the CopperTree system, the Vault and Kaizen, have been set up – these objects are how the system determines if changes have been made to your buildings’ programming (e.g: Golden Standards).

Does the CopperCube begin collecting BACnet device backups automatically?

Yes. Provided the other components of the CopperTree system, the Vault and Kaizen, have been set up – this provides an automatic backup and disaster recovery system for your buildings’ controllers.

Can the CopperCube be connected to multiple sites?

Yes. The CopperCube can be connected to multiple sites, where a site is a BACnet network with a unique range of devices. However, only one Ethernet connection type is allowed in the CopperCube; you can have multiple Foreign IP connections. Although you can create multiple sites, you must keep in mind that if you are using one CopperCube for many sites together, then network issues like an internet outage at the CopperCube side can stop data archiving for all the sites. Therefore, it is always advisable to increase the data archiving reliability by using more CopperCubes.

Can the CopperCube connect to a third-party (non-Delta) BACnet site?

Yes, as long as it’s a BACnet network using BACnet/Ethernet, BACnet/IP, or BACnet/IP-Foreign and follows BACnet standard.

Can the CopperCube collect trend log data from a third-party (non-Delta) BACnet site?

Yes, as long as the third-party devices support standard BACnet trend log properties, and BACnet ReadRange requests.

Can the CopperCube collect non-trend log data from a third-party (non-Delta) BACnet site?

Yes. It will collect standard BACnet objects, and properties – using BACnet ReadPropertyMultiple and ReadProperty requests. 

 Caution: ReadProperty is very slow and devices that do not support ReadPropertyMultiple requests may prove to be too slow to collect in any volume.

Can the CopperCube send trend log data to a location other than the CopperTree Vault?

Yes. The optional SQL connector will route trend log data to an external SQL database for use by third-party applications.

What changes can be made to an I/O Point without disrupting the CopperCube’s archiving of that Point?

To answer that, we must consider the possible changes to the key items involved in archiving a trend log.

First, is the object being trended. It is often called the point; typically, it is an input/output object such as an AI/BI/MI or AO/BO/MO. Any property change to the point that does not break the link from the trend log (TL) to the monitored object should not disrupt the archiving of the trend log. Disruptive actions are a) deleting the point object, b) renumbering it, or c) clearing the TLs monitored object property.

Second, is the TL object & its configuration. Deleting the TL is obviously disruptive. Less obvious is reducing the TL buffer size or increasing the TL polling frequency or switching the TL type; such that the CopperCube can no longer visit the TL quickly enough to prevent missing samples. Note: these actions usually cause the controller to purge the TL contents, resulting in lost samples.

The third is the CopperCube. It identifies TLs by device, for instance. Changing any of these items (i.e. moving the TL to another controller, change the instance#) is considered a different TL, and will disrupt the archiving of the affected trend.

Fourth, in the CopperCubes prior to the 1.20 version, the TL is also identified by its site name, so changing that will also disrupt the archiving TLs.As long as the link that connects the point to the TL object, and the TL to the CopperCube, is not broken, you can expect the CopperCube to continue archiving the altered trend log.

Some common situations:

  1. Renaming a monitored object. The link between the TL and the i/o point (sensor, actuator) is not broken since the link is based on object references and so archiving is unaffected.
  2. Renaming a trend log. The link between the CopperCube and the TL object is not broken since the link is based on object references and so archiving is unaffected.
  3. Replacing a monitored object. Deleting/recreating/renumbering a point or substituting a different point, breaks the ‘monitored object’ link between the TL and point. Manually restoring the link will allow archiving to resume. However, the trend log data may no longer ‘make sense’ as the monitored point is likely some completely different measurement.
  4. Moving a trend to another controller. To CopperCube, this is a new and completely different trend. The old trend is seen to stop at the time point of the move and a new trend appears.
  5. Changing a site’s IP Address. This prevents CopperCube from reaching the trends. But once connectivity is restored, the trend logs will resume archiving. Trends are identified by site name, not by IP address. Renaming the site is equivalent to moving trend logs but on a mass scale.

Can I stitch one trend log to another? Example: if an archiving trend log is moved and selected for archiving under its new location, can its data be appended to its old data?

In theory, this is possible, but there is no means for a user to do this. It requires renaming all the old data in the Kaizen database to the trends new object reference. Something only CopperTree technical staff are in a position to do. It is a difficult operation that is best avoided by careful planning.

Is it possible to export my CopperCubes database to another CopperCube so that I can maintain a copy of the archiver database?

Yes, you can export your CopperCubes database to another CopperCube. It is also possible for CopperCube to forward ongoing copies of your data to a SQL server of your choice.

Can multiple CopperCubes operate in a parallel to provide redundant mirrored archiving?

Yes. CopperCubes are independent devices and can operate in parallel just by configuring each CopperCube to archive the same controllers’ same trends. Your network will suffer twice the traffic load. Your controllers will respond to each CopperCube separately. The Kaizen servers will receive the same data from each CopperCube and correctly merge it back together into one data set for the building.

However, keep in mind that since the data is coming from the same site and same devices and then merged back together, you are incurring a large overhead to see the same data. If you are just looking for a way to maintain a copy of your CopperCube data, an easier method is

  1. periodically backup your CopperCube, or
  2. use the SQL connector functionality and store the data in a local database server.

With the device backup feature, will I get device backups for all the controllers on site?

The CopperCube will collect backup files from ONLY those controllers that are defined in the device range settings of the CopperCube. The devices that are not included in the device range definition on the CopperCube UI are unknown to the CopperCube and hence it will not ask for device backups from those controllers.

Do I have to configure device backup settings on the CopperCube UI to enable this feature?

No. You do not have to configure device backup settings; once the Cube is connected to the network, it will automatically collect backup information from the devices defined in the device.

What happens when the network goes down and comes back up, what happens to the CopperCube missed samples?

There are two cases for this question:1) Your CopperCube is installed in the building network

  • a. the internet connection is lost:

The CopperCube will continue to collect the TLs (and samples) from controllers and will pile up in the transmission queue. As soon as the internet connection is back, CopperCube will send out the data to our Cloud server.

  • b. the BACnet network connection is lost:

The CopperCube will again collect the samples from controllers as soon as the connection is back. According to the polled frequency of each TL and the buffer size, the CopperCube can miss samples. In this case, in the log, you can see that the CopperCube missed some samples (you can find this information on the TL management page for each TL individually). But you do not receive any notification about the missed samples.2) Your CopperCube is located in your Office and you remotely collect the TL samples:

  • a. The CopperCube loses the internet connection to the site:

This is the same as above.

Kaizen Device Monitoring will always show you the TL’s current status in your CopperCube or the CopperCube status directly (offline or online). Otherwise, if the controller still has all the new samples in memory since the last time the CopperCube collected them for a particular TL, no samples will be lost. The CopperCube can collect all the new samples (from its point of view) available in the buffer for each TL.

Kaizen

I can’t see Trendlogs in my vault after setting up the CopperCube. What is wrong with my set up?

  • If you are using a CopperCube version 1.20.1360 or prior, and have just set up the CopperCube, then follow the steps below; otherwise proceed to the next step.
  1. Trend Logs collected by the CopperCube are transmitted to the cloud at the Collection Frequency defined in the TL Management page. For these TLs to be viewed in Kaizen Vault, the associated TL Objects need to arrive in Kaizen as well. By default, the Object Fetch Time in the CopperCube is 1:00 AM, and objects are collected only once every day.
  2. Therefore, if you set up the CopperCube any time after 1 AM, you need to wait until 1:00 AM the next day for the TL Objects (and Other Objects) to be sent to the cloud.
  3. If you want to be able to see the TLs right away, you need to change the Object Fetch Time to a few minutes from now, and check for the data in approximately 30 minutes [Note: This time is dependent on the number of TL objects to be collected and sent to the cloud]. For example, if your current time is 3:30 PM, you can temporarily change the Object Fetch Time to 3:35 PM. By changing the Object Fetch Time, you are forcing the CopperCube to collect Objects from the controllers and send them to Vault without waiting until 1 am the following day.
  • Check your CopperCube settings
  1. Check if Coppertree Intake Server is enabled, on the Data Destination page under the Settings tab.
  2. Check if the trend logs are selected to be archived on the Trendlog Management page (the icon under the Archive status is supposed to show a green checkmark).
  3. If you can’t see your trend logs on the Trendlog Management page, check the site information and associated device and trend log ranges.
  4. Make sure TCP outbound port 5671 is open. You can check this under the Troubleshoot page under the Help tab. The status of the port should show “OK”. If not, contact your IT department.
  5. Use the Diagnostic Logs under the Data tab to search for the errors that could have happened to your Trendlogs simply by typing your Trendlog device and number in the search field (i.e. 7900.TL7).
  6. If all of the above is set up correctly, restart the cube from the Basic Settings page.
  • Check your settings in Kaizen
  1. Check the Sitename used in Kaizen under Building Settings (Devices); this should be identical to the site name in your CopperCube.
  2. Check the device ranges in Kaizen – Kaizen device ranges should include all the CopperCube Inclusion Range devices.

For creating insights/energy meters/reports, what access level is needed to create them? And who do I ask to get higher access?

You need admin permissions in order to edit/create reports, create insights, energy meters, etc. In order to gain administrator status, you need to contact the administrator who is currently managing your client account. It could be a user from your own client account or an administrator from a parent client account.

Is there a help file or an explanation as to what the logic flow objects do?

There is documentation on the Logic Builder feature on our support site (Product Reference or How-To).

I have set up trend logs that are polling samples every 1s, could the CopperCube collect all of these samples?

The CopperCube will not archive trend logs that have a polling frequency of less than 1 minute. the CopperCube will disregard this particular Trend Log. The Kaizen’s purpose is not to generate real-time alerts, the controller should take proactive control and be able to aggregate values for further analysis.

The CopperCube can collect COV whatever the frequency between 2 samples.

What is the maximum number of samples that I can display on the vault trendlog graph?

The Vault can display 10,000 samples per Trend Log. If you display multi-trend logs, you can 10,000 samples multiple by the number of Trend Logs that you need to display. your screen resolution will be another restriction. Within a very high-resolution screen, you can display 3840 pixels in width, thus you will not be able to see more than 3840 samples.

How do I restore the Kaizen backup in my controller?

Your Kaizen backup (a zip file containing a binary dump of the device backup data) can be restored to controllers using the Kaizen Viewer installation on enteliWEB. When the Kaizen Viewer installation is installed on your enteliWEB, a Load Controller Database shortcut will appear in the Kaizen Accordion tab. From here, you can restore the backups to the controllers.

Can I access Kaizen from enteliWEB?

Yes, you can access Kaizen from enteliWEB if you have integrated Kaizen with your enteliWEB. enteliWEB version 2.2 and after allows you to download and use the Kaizen Viewer feature. Using this feature, you can access Kaizen from enteliWEB.

What should I set up first – my CopperCube or Kaizen account?

You must set up your Kaizen account before configuring the CopperCube. Once you have set up a building and mapped the CopperCube to that building, Kaizen’s database is ready to receive the data coming from the CopperCube. After this, set up your CopperCube using the same site name as used in Kaizen and the data from your site will flow right into the correct database in Kaizen. However, if you configure the CopperCube first and do not set up your Kaizen building, all the data from the building will go to the trash since no database location has been allocated for that CopperCube.

How do I change a specific Golden Standard to high (red) priority?

You can change the priority of your GS insights using the GS Configuration feature. You can access this page under Building Settings >> Golden Standard. All the object types that are being monitored by Kaizen’s analytic engine are displayed on this page.

Clicking on an object type will direct you to the Golden Standard Configurations page for that object, where all the monitored properties are listed. In order to change the priority of Manual Override property to High (red), select High priority using the drop-down menu under Priority. Ensure that the Enabled box is checked.

image_printPrint