#Coppercube review software

This helps avoid any confusion/typo later on when someone maps this site name into Kaizen.īefore starting the import from the Historian please make sure the CopperCube is in a healthy state. Select a simple and short name with no special characters or spaces, and try to avoid using capital letters and the underscore character as much as possible. A common issue with a CopperCube/Kaizen setup is site names that don’t match between CopperCube and Kaizen.If the number of TLs found is significantly larger than that limit, it could cause a very high CPU usage and affect the CopperCube performance. Try to keep the number of TLs that are found by the CopperCube close to the maximum permitted archived TLs.To improve the functionality of your CopperCube, try to have multiple device ranges (device inclusion and exclusion range) to prevent the CopperCube from wasting resources on new TLs and Objects that are not necessary.CopperCube Sites and Device Ranges:Įxclude unnecessary devices and trend logs: Do not simply collect all devices between 1 & 4 million, and all trend logs between 1 & 4 million – just because it is easy to set up. If there are more than 50,000 objects to collect, use multiple CopperCubes as required.įor Best Practices to optimize your data collection from your controllers you can visit the page here. Ensure the Include & Exclude Device Ranges setting is used to limit the objects the CopperCube can collect to this quantity. This throttling effectively limits the cube to collecting 50,000 objects per day. If this is not true for your site, then please shift the object collection time.Īlso, be aware that the CoppeCube intentionally throttles its collection speed to limit the network load caused by this operation. By default object collection starts at 1 am, as this is generally a quiet period when the collection load imposed on the network will not adversely affect other operations.

The collection frequency cannot be changed, but the time of collection can be. Likewise, the CopperCube collects BACnet objects once daily if connected to Kaizen. It will not adjust the default setting, just ignore it in this case. If you mistakenly configure the Trend Logs (TL) so that the polling interval and buffer size result in the samples rolling over under the specified collection frequency, the CopperCube will identify this as an issue and automatically adjust the collection frequency internally to accommodate it. When connecting to enteliWEB, it will blend the latest data from the controller with the archived data from the CopperCube so if anything data collection frequency can be relaxed to reduce load. Refrain from adjusting this default faster is not necessarily better and will come at a cost. This time period was thoughtfully chosen to balance network load and timely data collection. The CopperCube collects trend log data by default on a 4-hour schedule. Optimizing Data Collection CopperCube Trendlog Management:

Press the power button once, and wait.

#Coppercube review software

This can cause software problems as processes don’t have time to terminate properly. Hold down the power button for 3 seconds will do a forced immediate shutdown.The following hardware resets are not recommended, but possible: Use the Restart and Shut Down buttons on the Basic Settings page.If necessary, the best way to restart or shutdown the CopperCube is through the GUI:

We generally do not recommend restarting or shutting down the CopperCube. Please note that unplugging the CopperCube is never recommended and could be very harmful to the software.

Print and use the onboarding forms available on the CopperCube support website before setting up the CopperCube.ĬopperCube restart and shut down procedures.

Be aware of the load the cubes will place on the site’s (BACnet) network and its BBMD device(s). If not, then pre-determine how many CopperCubes are required, and how the site is to be divided between the CopperCubes to balance the load.

Ensure the data volumes fit within the CopperCube limits.

Know which devices range map to which buildings. Get a good feel for the number of controllers, trend logs, and BACnet objects on the entire site, and within each of the buildings and device ranges. Get familiar with the site before installing the CopperCube.These recommendations are based on years of experience with BACnet communications, Delta Controls devices, and data analytics. We offer the following recommendations to help your Coppercube perform well. Troubleshooting tips for sending data from the CopperCube to Kaizen are also included in this KbA. This KbA offers general usage guidelines for the CopperCube and reviews the best practices for your CopperCube configurations to optimize data collection and get the best performance from your CopperCube.