Starting and configuring CoolMaster EDGE

When logging into the device user get to the main config screen:

 

1. Lines

Set line configuration as required for the systems that are connected on each specific line.

Following line properties are available:

• Name – the name of this line as indicated on the devices labels - L1, L2, L3, L8 (USB), L9 (USB-C)
• Type – The type of the line. Once type is selected, all type related parameters are shown (different parameters are available for the different line types).

Following types are available to select:

• BACnet MSTP – set line to RS485 with BACnet MSTP.
  • Baud Rate – communication rate on the line: 9600 or 38400 
  • Polarity – define if it is Normal (A/B) or inversed (B/A)
  • Vendor ID –1164 (read only) – CoolAutomation’s BACnet vendor ID assigned by ASHRA . Used in the Vendor ID property.
  • Model Name – CoolMasterEDGE (read only). The BACet model name property.
  • Device ID - The BACnet Device ID (instance number) property. Can be configured following BACnet standard guidelines. Default is 123.
  • MSTP MAC – the address of the CoolMaster EDGE device on the MSTP network.
• Modbus RTU - set line to RS485 with Modbus RTU.
  • Power Meter Model – select from the list the power meter that you are connecting with. Only pre-integrated power meters can be selected.
  • Baud Rate – communication rate on the line: 9600, 19200, 38400, 57600,115200 
  • Polarity – define if it is Normal (A/B) or inversed (B/A)
• Midea V5 (MDV5) - set line to RS485 connecting to Midea VRF V5 Series
• Midea V8 (MDV8) - set line to RS485 connecting to Midea VRF V8 Series
• Samsung  - set line to RS485 connecting to Samsung VRF . Advanced configurations:
  • Master – when another central controller is connected on the same line, the EDGE device should be set to “Off”. otherwise “On”
  • Polarity – define if it is Normal (A/B) or inversed (B/A)
• CoolPlug - set line to RS485, for connecting specifically with wired CoolPlug 
• Simulation (SIM) - set line as simulation of controlling a VRF system
  • Number of IDUs - only for Simulation line type. Set the number of Units to simulate on the VRF line.
• Unused – line is not in use
• Daikin – (only available on line 2) connect to Daikin D3-Net communication line
  • Termination 120 Ohm
• Mitsubishi Electric (ME)
  • Termination 120 Ohm
• Toshiba TCC (TOTCC)
• Gree (GMV5)

 

2. Network

• Mode – Static or DHCP
• When Static is selected, you must define the IP address, Network mask, Gateway and (optional) DNS servers

 

3. GPIO

Allows connecting to digital output sources for centrally override controls of the device in some scenarios (e.g. connect with fire doors activation and shut down all ventilations)

Select between All units ON or All units Off  and set Normally On/Off State.

 

4. BACNET/IP

Allow setting the EDGE device as a BACnet IP client to discover 3rd party BACnet devices. Communication will run over the Ethernet IP port specific line.

You can enable or disable EDGE device BACnet IP interface

• Vendor ID –1164 (read only) – CoolAutomation’s BACnet vendor ID assigned by ASHRA . Used in the Vendor ID property.
• Device ID - The BACnet Device ID (instance number) property. Can be configured following BACnet standard guidelines. Default is 123
• Device Network - The BACnet IP network #.  Can be configured from 1 to 65,534.  Default is 1.
• BIP Port - The UDP communication port to use for BACnet IP communication.  
• RW Interval
• WHOIS interval - the frequency that Who-Is discovery messages are automatically broadcasted in milliseconds.  Default is 6,000.
• BBMD Address - The destination IP address to use for BBMD
• BBMD Port - UDP communication port to use for the BBMD destination address

 

5. Settings

• Time Management – In most installations, the device will get its time from the network clock (NTP). In cases where NTP is not available, it is possible to set the time manually.
  • The time is required to run local schedules and logic based on time.
  • If the device is connected to the cloud it will take its time from the cloud network.
• To create BACnet device as a unit you can enable BACnet server: 
  

6. Terminal

Opens a terminal console where the user can configure the device using the terminal commands. 

The EDGE device with its advanced processing and storage, allows unique capabilities when installed in an environment with unstable internet connection. 

The following are the main functions available when using the CoolMaster EDGE: 

1. Local Data Buffering

The EDGE device can handle network disconnect periods without losing data on the local network or direct local interfaces.

 The mechanism keeps all the collected data on the Micro SD card for the period of network disconnect. Once network connection is back, the data is pulled up to the cloud and synched with the previous data for later retrieval. 

The SD-Card that is included with the box can hold at least 48 hours of data. Depending on the number of connected units, the storage period may be longer. 

Backfilling of data to the cloud may take a few hours, and highly correlated with internet stability, network topology, firewalls and the amount of data to be synched. 

 Note: this capability will only work if Micro SD card is installed and formatted by CoolAutomation specs. By default, the device is shipped from the factory with the SD Card installed and ready to use.

2. Local Control Application

The EDGE device hosts a web server that allows servicing local browsers directly, even if there is no connection to the Internet. This allows easy control, schedules and basic settings of HVAC units over the LAN, for places without internet access at all, or with unstable networks. 

When controlling units from the local applications (Mobile or desktop browser), all activity is being kept and synch to the cloud (if accessible and registered) for later auditing and tracking of system health.

The local application works separate from the cloud-based applications and automatically synchs when there is a cloud connection.

If a control is pushed from the Cloud App and from the local app, the last command received on the device will be executed.  

Note: Be aware of potential overrides between cloud and local apps and grant access smartly to avoid conflicts. 

1. Logging in to the local Application

• Browser desktop: http://<device IP address>/control (e.g. http://192.168.1.2/control)

• Default user credentials are the device SN & PIN, that can be found on the label at the back of the device.

  

2. Local Control Capabilities

The following control functions are available through the Local app and are synchronized also with the cloud Apps:

• Control commands – On/Off, Setpoint, Mode, Fan Speed, Louver 
• Schedules

3. Local User Management 

The default user of the local device is an admin user. 

This Admin user cannot be deleted. He can add more local users – all have same access rights (admin) but can be assigned with different username & password.  

On User management tab click “Create User” to add a new user:

Note: The local users are not synchronized with the Cloud App users.

4. Local Unit Settings

 In Unit Settings tab, users can change the names of units connected on the EDGE device.  Click the Edit Names button, make changes to unit names and save your changes.

 All changes will be synchronized with the cloud app names if the device is registered and connected to the cloud. 

 Note: if changes are made on both the cloud app and local app, the last change will be assumed. Avoid conflicts by setting proper access rights to these settings in the cloud and the local app.

5. Local Group Management

In Group Management tab, users can define new groups, edit groups and change group names.

The local Group Management only relates to groups where all units of the group are on this same EDGE device. If there are groups on the cloud with a mix of units from the EDGE device and other devices, these groups will not be shown on the EDGE local control, to avoid conflicts in user permissions.

6. Local Advanced Control Settings

 In Advanced Control tab, admin user can manage some advanced control logic through the Local app.

 Refer to CoolAutomation Professional app user guide for a more detailed description of these advanced control settings.

• Setback - allows setting setback schedules for energy savings.

Configuration setting of changeover is synched between cloud and local applications when network connection is available

• WRC restriction - allow disabling some of the changes done from the local Wall Remote Controller (WRC). The WRC restriction setting doesn’t restrict the change of the setting in the Thermostat; however, it enforces the setting by identifying that a change was done via the Thermostat and rolling back the thermostat setting to the state it was prior to the change.

• Auto Changeover - allows configuring auto changeover rules for heat pump systems.  

Settings of systems (grouping units into systems) is made on the cloud site management.

Important note: Setting auto changeover rules assumes the user is aware of the heat pump systems. Setting auto changeover on partial units of a system may result in a fail execution and changeover will not be executed as expected.

Configuration setting of changeover is synched between cloud and local applications when a network connection is available.

• App Control – allows configuring which controls will be available through the application (local or/and cloud) for each unit. 

Configuration setting of app controls is synched between cloud and local applications when network connection is available.

3. Local logic on the device

The EDGE device has a powerful processor that allows running advanced automation logic without relying on the continuous internet connection.

Once a automation logic is defined on the Applications (Professional App advanced logic, or local app advanced controls) it is then stored on the device local memory, and will execute regardless of the device internet connection status.

The following logic are set to run locally:

• Schedules – can be set on the cloud Apps (Control, Professional) and synched with the device, or can be defined on the local Control App. If defined on the cloud it will be synched to the device and then run locally. If defined on the local App, it will be synched up to the cloud when there is a network connection. If no network connection is available – schedule can still be set and run on the local device.
• Interlocks, Anomaly rules – Can only be set on the cloud application, pushed to the device and run locally. Monitoring of activity will be available only on the Professional App tools (audit, unit diag) and only when cloud connection is available. If there was a network disconnect while actions took place, they will be logged locally and synched to the cloud for logging and trending.

Note: only rules where ALL units/sensors are connected to the same device will be pushed to the device.

All activity during disconnection period is logged locally and pushed* up to the cloud when the network reconnects for future auditing.

Note: The size of logs kept on the device depends on local SD-card capacity. At least 48 hours will be stored on the provided SD-Card. Above this size, it depends on the exact site setup.

Functions that are pushed from cloud and work on device but are not reflected on local App:

• Interlocks

When synch is in progress between local and cloud Apps, a synch icon is shown on both sides if user is browsing the relevant screen. 

4. Connecting BACnet Clients

The EDGE device allows connection of local BACnet controllers, over BACnet IP or BACnet MSTP. To start integration, follow the BACnet configuration steps as outlined in device configuration section above.

For mapping a new BACnet device, log in to the cloud Professional app and follow the below steps

Note: the BACnet mapping and settings of controls mandates an active subscription to the Professional App on the site where the EDGE device is connected. 

1. BACnet Device Mapping 

1. Go to BACnet Mapping tab (Site Management ->BACnet Mapping)
2. BACnet Mapping main screen shows a list of all devices that were discovered on the site by any of the connected EDGE devices on the site.

Note: the list will also show BACnet devices that were added in the past and now disconnected highlighted in light red. You can remove them by clicking the Delete option (through the 3 dot icon)

3.   When entering the BACnet Mapping tab, a discovery process starts automatically (devices on connected BACnet networks, not the whole objects discovery)
4. To start a BACnet object mapping process for a device, click the 3 dots icon for a specific device and select Object Mapping.

5. When the Object Mapping screen opens, an object discovery process starts automatically. This process can take a few minutes. While discovery is in progress, the indication (Discovery in progress) is shown. This process can take up to 10 minutes. 

6. Users can set the name for how device will appear in the application (this does not change the device name on the BACnet network)  with the App Device Name fields
7. You can navigate between the list of all objects and the list of only the objects that you already mapped by clicking on the All Objects/Mapped toggle.
8. The mapping is made in “Templates”. User can use an existing template that is already available on the site or create a new template using the “Mapping template” button. A new or existing template must be selected before any objects can be mapped, 

9. Mapping of objects – you can select which of the device objects you want to map into the application. 
10. To map an object, double click the object line. The map object pop up will open and you can make the related settings for this specific object.
    
    Different BACnet object types have different settings available. 
    
    You can set the Name (to be shown in the application), text enumerations (for Multi Value object types), set the allowable range for writing to analog values , define if this object should trigger an alert in the app, set priority for BACnet write communication.
    
     
    1. To have the setting available for external BACnet-based systems check the “Set as Universal Unit Point” field. 
       
    2. To have the unit visible for external BACnet-based systems check the “Map to universal AC unit” field.
       
        
11. If setting an object as error, the app will also allow you to set the value for cleared alert. The default clear value is 0. If an object is defined as error, when error occurs, it will trigger an error on the application and will be added as an alert in the Alert Log and also users can configure to receive notifications for this error in the professional App.
12. Up to 20* objects per device can be mapped. If you reached 20 object and want to delete one mapped object and replace with another, use the trash icon on the objects list.
13. When objects mapping is completed, click save to save all changes to the template.
14. Click ‘back’ to return to the main device mapping screen. By default, your new template will be selected for the BACnet device. 
15. To set (or select a different) a mapping template, use the dropdown arrow in the device ‘Mapping’ column.

2. BACnet UI Template 

1. Setting a UI Template - UI template allows you to define a basic layout of main controls and monitoring information in the Control Tab for the mapped BACnet device. Click the 3 dot menu for the BACnet device and select ‘Control UI’ . This will open the Control UI template creation wizard

2. Select a background image (static) for the control UI when this BACnet device is show on the App Control Tab.

Maximum image size is 2MB . It is recommended to use an image with aspect ratio of 9:10 to assure it renders well later in the application Control page.

3.  Select the parameter template you want to use for setting on the UI Control template. The list will include all object templates that were created for this site.

4. Drag and drop parameters from the left side into the image canvas.
5. Once s parameter (object) is set on the canvas, you can set its configuration using the right pane of pop up. You can set name for the parameter label, set where to place the label, set text size and color and (depending on the Object type)  set the control type to be used on the screen.

Following Control types are available:

• Textual Value – read only representation of the actual object value
• Toggle
• On/Off button – for binary objects with ability to set on/off
• List – for Multi Value objects. Will open a dropdown of all options to select from
• Up/Down Arrows – for numerical values where user can set the value up or down in steps.

Note: the up down value settings is directly correlated with the setting of the object mapping. User must properly set the upper and lower value limit, and also the steps of value changes (e.g. for room setpoint, can set upper to 75, lower to 65, steps to 1F). 

6. After completion and saving of the Control UI template, you can select this template and apply it to your device in the BACnet Mapping screen. Use the device line ‘Control UI’ column to get the dropdown of available templates and select your template.

Note: Object Mapping and Control UI templates are associated with a device’s BACnet vendor and model.  Templates created for one device can be applied to other BACnet devices with the same vendor and model information.

7. Connecting the BACnet device to the App and start monitoring the data points – click the 3 dot menu on the device line and select Bind. the status of the device will turn green and show “Bound to App”

8. After device is “Bound to App”, all objects are monitored continuously and pushed up to the cloud application.
9. Available functions for BACnet mapped devices when using the cloud application:
   1. Control Tab – control and monitor the device in real time. By default, all BACnet units are mapped into a group called “All BACnet devices”. User can map them to other groups.
   2. When selecting a BACnet unit on the control tab it will show the Control UI template with the latest values as read from the BACnet device.
   3. Unit Diagnostics – monitor all historic object values and correlate them over time. All mapped BACnet points are available for trending on the graph.
   4. Alert log see alerts on BACnet device disconnect, or on Errors on this BACnet device. Errors on the BACnet object can be mapped using the BACnet mapping process. 
   5. Interlock – create complex rules that include conditions and actions on the parameters from the BACnet devices by selecting the source as BACnet device and the relevant device in the list.
10. To disconnect a BACnet device from the App, go to the BACnet devices list (BACnet Mapping main screen) and on the ‘3 dot menu’ click “Unbind”. This will stop collecting data for this BACnet device. 
11. BACnet devices that are not detected on the line (cable disconnect, device was disconnected, other reason) – the BACnet device row will be marked in red and a ‘Disconnect’ symbol will be shown next to the device name.
12. To remove a device from the site list – use the ‘Delete’ option in the ‘3 dot menu’

Note: The Disconnect option is only available if the device is not communicating on the BACnet line. Otherwise this device will keep coming up when discovering the line using the Discovery button.

5. Connect Modbus Power meters

To connect power meters (for PPD or other needs), use the config app to set the related line (L1, L2 or L3) to Modbus RTU and then select the specific Power meter model that is connected on that linethe baud rate and polarity.

The current implementation only supports a single power meter type on the same RS485 line. You can connect several meters of the same type, but make sure they have unique IDs.

Power meter can be used as source for PPD calculation or viewed in control app (to monitor consumption), Unit diagnostics and interlocks. All these functions mandate subscription to professional app.

6. GPIO

Connect IO devices to the EDGE and use these inputs as sensor inputs for triggering actions and interlocking. 

The EDGE device can connect 2 x I/O devices, each one can be of the following type:

• Digital (Binary) Input (0-5V) – monitor a sensor with 0/1 states, with setting option for Normally Open (N.O) or Normally Close (N.C).

The following automation procedures are also available using these inputs if selected Action on the device configuration. The logic is executed on the local device and does not require cloud connection.

• Action (Turn all indoor units OFF) 
• Action (Turn all indoor units ON)

After configuring the GPIO, you will be able to see the devices as Auxiliary devices box in the Site Management under the EDGE device. You can enter the Aux box and then see them as sensors.

The GPIO ‘sensors’ can be seen on the control tab (open/close states), unit diagnostics (External sources), interlocks (Input device)