browse

7 Minute Read

| How it works

Overview

75F® CCU to act as the front-end control for Daikin Maverick or Rebel RTU units. Using the local API connection between the CCU and the IE gateway you are now able to control DAT setpoint, schedules, Duct static pressure, & Humidity as well as report back alarm status and other points from the RTU. 

Requirements

  • Daikin IE gateway  
  • Daikin RTU with Micro Tech 3 unit controller 
  • CCU with cloud subscription connected to building Wi-Fi. 
  • IE Subscription for first 90 days is required, Annual subscription is not required 
  • IE is installed according to the IM: Found Here

mceclip0.png

  • CCU communicates with building sensors over 900 MHz mesh
  • CCU connect to IE gateway over wired ethernet connection.
  • IE Gateway connect to MicroTech3 controller in the RTU.
  • CCU communicates to 75F cloud over Building Wifi.
  • 75F Remote apps connect to the 75F cloud.

Operations

Following are the type of operation that can be performed using the Daikin IE RTU

Alarming 

CCU reads the alarm information from the IE GW and relays the same to cloud. CCU reads three separate alarm levels These alarm conditions originate in the equipment PLC and is relayed via the IE GW to the CCU. And 75F portals and apps. They return a numeric value that corresponds to a description of the alarm condition.  

  • Warning alarms are in the range of 0-99 and is mapped to 'Low' severity alerts.  These alarms do not affect unit operation 
  • Problems are in the range of 100-199 and mapped to 'Moderate' severity alerts.  These alarms limit functionality in some way on the equipment. 
  • Faults are in the range of 200-255 and mapped to 'Severe' severity alerts.  These alarms cause the equipment to shut down. 
  • In cases where only one alarm for a piece of equipment can be displayed, the ActiveAlarmEnu is displayed and represents the highest priority active alarm. This is in the range of 0 – 255 and mapped to ‘Moderate’ severity alerts.  

Occupancy 

75F communicates the CCU schedule to the IE GW. To do this 75F changes the point 'OccMode' on the IE GW. When schedule is occupied or unoccupied-conditioning is required, 'OccMode' to be changed to 'Occ' When unoccupied and no conditioning is required, 'OccMode' changed to 'Unocc'. CCU shall control the RTU occupancy by writing to “OccMode” from “unocc” (1) to “occ” (0) and back again, based on CCU and solution occupancy status. This is written every minute to the IE GW irrespective of the 'OCCSTATUS'. 

CCU reads the "OCCSTATUS" (Occupancy Status) from IE GW and relays the same value to cloud. Occupancy Status give the status of occupancy on IE GW. This value is read every 5 min by CCU. CCU and Cloud UI displays the occupancy status as read from IE GW. 

Discharge Air Temperature Control 

Cooling/Heating is achieved by writing to the point DATClgSetpoint. 75F controls the DAT setpoint by directly writing to DAT Cooling Setpoint (F) (DATClgSetpoint). This value is scaled for both heating and cooling DAT setpoint. So DATClgSetpoint can require heating or cooling and is used to heat or cool. This value is written once a minute. RTU controller does not transition to a heating mode, but activates “Min DAT” mode when necessary to maintain “DATClgSetpoint” with heat rather than cooling (this happens when control temp source is set to none).

Cooling Mode 

When there is a need for cooling, cooling is achieved when the cooling loop output is written to the DATClgSetpoint. Cooling loop output shall be 0-100% which is mapped to 70 - 55 deg F of DAT setpoint. E.g. when cooling is required and cooling loop output is 0% then value as 70 is written and when it is 100% then value as 55 is written to DATClgSetpoint. 

Heating Mode 

When there is a need for heating, heating is achieved when the heating loop output is written to DATclgSetpoint. Heating loop output shall be 0-100% which is mapped to 75 - 100 deg F of DAT setpoint. E.g. when heating is required and heating loop output is 0% then value as 75 is written and when it is 100% then value as 100 is written to DATClgSetpoint.

Fan Control 

CCU controls fan speed for both single zone and multi zone systems. the toggle to select if the system is single zone or multi-zone in the configuration page helps to achieve this. This is enabled manually by the user based on actual site configuration. At any time CCU shall write values for either single zone or multizone system points. For a single zone system CCU fan loop output shall be mapped to Fan Speed (RemoteSFCap) and for multizone system CCU fan loop output shall be mapped to duct pressure setpoint (DSPspt). 

Standalone Mode (Fail Safe) for Daikin

If you configure the unit according to the configuration below. The unit will use the RAT occupied heating and cooling setpoints in case of emergency. If the RAT drops below the occHtg setpoint or if the RAT rises above the occClg setpoint the unit will engage heating or cooling regardless of the DAT value being written by the CCU. 

Note: Typically this will occur only if there is a communication loss between the CCU and the RTU. 

Diagnosing a Communication Loss

The “System Clock" point is read by the CCU periodically and written back to the RTU as confirmation there is communication. If this point fails to read or write, then an alert will be generated.  

 

| Wiring

DaikinIEPhysical.png

| Configuration

Initial Set-up

Note : Initial configuration shall be set on the RTU before configuring CCU: (to be done by Daikin support person)

  • Set Control Mode (CtrlMode) to 'Auto' 
  • Set Control Type (CtrlType) to 'DAT' 
  • Set Control Temp Source (CtrlTempSrc) to 'RAT' 
  • Set Cooling Reset (ClgDATReset) to 'None' 
  • Set Heating Reset (HtgDATReset) to 'None'  
  • Control Temperature (OccHtg and OccClg) is set to 65 and 80F 
  • Set the Discharge Heating Setpoint (DAT Htg Spt) to 90F
  • Set Occupy Mode (OccMode) to “auto” 
  • Set Supply Air Fan Control (SFCapCtrl) to 'DSP' (Multizone)  -OR-  'speed/Net' (Single Zone RTU)   

Network Connectivity

All network settings should be factory set and no field adjustments should be required. 

  • CCU and IE Gateway is connected over an ethernet connection directly from 75F CM to Daikin IE gateway. This acts as a subnetwork.   
    • Fixed IP for Ethernet connectivity would be 172.16.0.1 (Port Eth0) Subnet 255.255.255.0 on IE GW 
    • Fixed IP for Ethernet connectivity would be 172.16.0.2 Subnet 255.255.255.0 on CCU 
  • IE Gateway connects to MicroTech3 Controller for the RTU (Port Eth1) 192.168.1.42 
  • 75F CCU then communicate to 75F cloud over building Wifi. 75F remote apps connects to the 75F cloud 
  • Cell network should be enabled for 90 days on the IE Gateway.

Configuration Parameters

From the CCU

  • Click select system profile
  • Select the DAIKIN IE RTU for system profile from the drop down.

The configuration screen displays as below.

mceclip0.png

The following table explains the various fields displayed on the page: 

Field Name

Description

IE Equipment IP Address

You can use this option to select Ip address of the IE equipment.

Multi Zone Toggle

You can use this option to toggle between a multi zone and single zone.

Cooling

You can use this option to enable the cooing control

Fan

You can use this option to enable the fan control

Heating

You can use this option to enable the Heating control

 

Once configured then you can see the information for the profile as follows.

blobid1.pngOnce the connection to the cloud is established, you can see the information in the portal as follows.

mceclip0.png

 

Previous
Next

Comments

0 comments

Please sign in to leave a comment.

Was this article helpful?

1 out of 1 found this helpful
Powered by Zendesk