HMS KNX, Intesis User Manual

KNX (TP-1) Interface for HITACHI VRF Air Conditioning

USER MANUAL

Issue date: 07/2020 r1.3 ENGLISH

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

2 / 60

Important User Information

Disclaimer

The information in this document is for informational purposes only. Please inform HMS Industrial Networks of any inaccuracies or omissions found in this document. HMS Industrial Networks disclaims any responsibility or liability for any errors that may appear in this document.

HMS Industrial Networks reserves the right to modify its products in line with its policy of continuous product development. The information in this document shall therefore not be construed as a commitment on the part of HMS Industrial Networks and is subject to change without notice. HMS Industrial Networks makes no commitment to update or keep current the information in this document.

The data, examples and illustrations found in this document are included for illustrative purposes and are only intended to help improve understanding of the functionality and handling of the product. In view of the wide range of possible applications of the product, and because of the many variables and requirements associated with any particular implementation, HMS Industrial Networks cannot assume responsibility or liability for actual use based on the data, examples or illustrations included in this document nor for any damages incurred during installation of the product. Those responsible for the use of the product must acquire sufficient knowledge in order to ensure that the product is used correctly in their specific application and that the application meets all performance and safety requirements including any applicable laws, regulations, codes and standards. Further, HMS Industrial Networks will under no circumstances assume liability or responsibility for any problems that may arise as a result from the use of undocumented features or functional side effects found outside the documented scope of the product. The effects caused by any direct or indirect use of such aspects of the product are undefined and may include e.g. compatibility issues and stability issues.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

3 / 60

KNX (TP-1) Interface for HITACHI VRF Air Conditioning

ORDER CODE

LEGACY ORDER CODE

INKNXHIT001R000

HI-RC-KNX-1i

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

4 / 60

INDEX

1. Presentation .................................................................................................... 6

2. Connection ...................................................................................................... 7

2.1 INKNXHIT001R000 without Hitachi Remote Controller ........................................ 7

2.2 INKNXHIT001R000 with Hitachi Remote Controller ............................................ 7

3. Configuration and setup .................................................................................... 9

4. ETS Parameters ............................................................................................. 10

4.1 General dialog ............................................................................................ 11

4.1.1 INKNXHIT001R000 is master in AB bus .................................................... 11

4.1.2 Send READs for Control_ objects on bus recovery ..................................... 11

4.1.3 Scene to load on bus recovery / startup ................................................... 11

4.1.4 Disallow control from remote controller .................................................... 12

4.1.5 Enable func “Control_ Lock Control Obj” ................................................... 12

4.1.6 Enable use of objects for Filter ................................................................ 13

4.1.7 Enable func “Operating Time Counter” ..................................................... 13

4.1.8 Enable object “Error Code [2byte]” .......................................................... 14

4.1.9 Enable object “Error Text Code [14byte]” ................................................. 14

4.2 Mode Configuration dialog ............................................................................ 15

4.2.1 When Mode is AUTO Status_ objs report actual operating status

(HEAT/COOL/..) ................................................................................................. 15

4.2.2 Enable use of Heat / Cool bit-type obj ...................................................... 15

4.2.3 Enable PID-Compat. Scaling Mode Objects ............................................... 16

4.2.4 Enable use of +/- object for Mode ........................................................... 17

4.2.5 Enable use of bit-type Mode objects (for control) ...................................... 17

4.2.6 Enable use of bit-type Mode objects (for status)........................................ 17

4.2.7 Enable use of Text object for Mode .......................................................... 18

4.3 Special Modes Configuration dialog ................................................................ 18

4.3.1 Enable use of POWER mode .................................................................... 19

4.3.2 Enable use of ECONOMY mode ................................................................ 20

4.3.3 Enable use of ADDITIONAL HEATING mode .............................................. 20

4.3.4 Enable use of ADDITIONAL COOLING mode .............................................. 21

4.4 Fan Speed Configuration dialog ..................................................................... 22

4.4.1 Available fan speeds in Indoor Unit .......................................................... 22

4.4.2 Indoor unit has AUTO fan speed .............................................................. 23

4.4.3 DPT object type for fanspeed .................................................................. 23

4.4.4 Enable use of +/- object for Fan Speed .................................................... 24

4.4.5 Enable use of bit-type Fan Speed objects (for Control) ............................... 25

4.4.6 Enable use of bit-type Fan Speed objects (for Status) ................................ 25

4.4.7 Enable use of Text object for Fan Speed ................................................... 25

4.5 Vanes Up-Down Configuration dialog ............................................................. 26

4.5.1 Indoor unit has U-D Vanes ..................................................................... 26

4.5.2 Available positions in Indoor Unit ............................................................ 27

4.5.3 DPT object type for Vanes Up-Down ........................................................ 27

4.5.4 Enable use of +/- object for Vanes U-D .................................................... 28

4.5.5 Enable use of bit-type Vane U-D objects (for Control) ................................ 29

4.5.6 Enable use of bit-type Vane U-D objects (for Status) ................................. 29

4.5.7 Enable “Vanes U-D Swing” objects (for Control and Status) ........................ 30

4.5.8 Enable use of Text object for Vane U-D .................................................... 30

4.6 Temperature Configuration dialog.................................................................. 31

4.6.1 Periodic sending of “Status_ AC Setp” ...................................................... 31

4.6.2 Transmission of “Status_ AC Reference Temp” .......................................... 32

4.6.3 Enable use of +/- object for Setpoint Temp .............................................. 32

4.6.4 Enable limits on Control_ Setpoint obj ..................................................... 32

4.6.5 Ambient temp. ref. is provided from KNX ................................................. 33

4.7 Scene Configuration dialog ........................................................................... 34

4.7.1 Enable use of scenes ............................................................................. 34

4.7.2 Scenes can be stored from KNX bus ........................................................ 35

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

5 / 60

4.7.3 Enable use of bit objects for scene execution ............................................ 35

4.7.4 Scene “x” preset ................................................................................... 36

4.8 Switch-Off Timeouts Configuration dialog ....................................................... 37

4.8.1 Enable use of Open Window / Switch off timeout function .......................... 37

4.8.2 Enable use of Occupancy function ........................................................... 39

4.8.3 Enable use of SLEEP timeout .................................................................. 41

4.9 Binary Input “x” Configuration dialog ............................................................. 42

4.9.1 Enable use of Input “x” .......................................................................... 42

4.9.2 Contact type ......................................................................................... 42

4.9.3 Debounce time ..................................................................................... 42

4.9.4 Disabling function.................................................................................. 42

4.9.5 Function ............................................................................................... 43

5. Specifications ................................................................................................. 51

6. AC Unit Types compatibility. ............................................................................ 52

7. Error Codes ................................................................................................... 53

Appendix A – Communication Objects Table ................................................................ 54

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

6 / 60

1. Presentation

INKNXHIT001R000 allows a complete and natural integration of HITACHI air conditioners with KNX control systems.

Compatible with VRF air conditioners commercialized

by HITACHI.

Main features:

• Reduced dimensions, quick installation.

• Multiple objects for control and status (bit, byte, characters…) with KNX standard

datapoint types.

• Status objects for every control available.

• Timeout for Open Window and Occupancy. Sleep function also available.

• Control of the AC unit based in the ambient temperature read by the own AC unit, or in

the ambient temperature read by any KNX thermostat.

• AC unit can be controlled simultaneously by the wired remote control of the AC unit and

by KNX.

• Direct connection to the AC indoor unit.

• Total Control and Monitoring of the AC unit from KNX, including monitoring of AC unit’s

state of internal variables, running hours counter (for filter maintenance control), and error indication and error code.

• Up to 5 scenes can be saved and executed from KNX, fixing the desired combination of

Operation Mode, Set Temperature, Fan Speed, Vane Position and Remote Controller Lock in any moment by using a simple switching.

• Four potential-free binary inputs provide the possibility to integrate many types of

external devices. Configurable from ETS too, they can be used for switching, dimming, shutter/blind control, and more.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

7 / 60

2. Connection

Connection of the INKNXHIT001R000 to the AC indoor unit

2.1 INKNXHIT001R000 without Hitachi Remote Controller

The INKNXHIT001R000 can be connected directly to the AB bus of the indoor unit (no Hitachi remote controller -RC from now on- also connected in the AB bus). If this is the case, INKNXHIT001R000 must be configured as master (using the ETS software), see connection diagram below.

2.2 INKNXHIT001R000 with Hitachi Remote Controller

If a Hitachi remote controller (RC) is present and connected to the AB bus, connect the gateway as Slave in parallel with the wired remote controllers (controller acts as Master).

• Wired remote control available.

Disconnect mains power from the AC unit and use a 2-wire cable with a diameter of

0.75mm2 to 1.25mm2 for the connection of INKNXHIT001R000, Hitachi remote controller and its corresponding indoor unit. Screw the suitably peeled cable ends in the corresponding AB terminals of each device, as summarized in the Figure 2.2.

Maximum AB bus length is 500 meter. HITACHI RC and INKNXHIT001R000 are no polarity dependent.

Connection of the INKNXHIT001R000 to the KNX bus:

Disconnect power of the KNX bus. Connect the INKNXHIT001R000 to the KNX TP-1 (EIB) bus using the KNX standard connector (red/grey) of the INKNXHIT001R000, respect polarity.

Reconnect power of the KNX bus, and mains power of the AC unit.

Connection diagrams:

INKNXHIT001R000 without HITACHI RC

B A

Connection to AB bus. Two wire cable.

KNX TP-1 (EIB) bus

AC Indoor Unit

Max.500 m

Internal electronic control

AC Unit

A B



KNX

COM

IN4

IN3

IN2

IN1

Binary inputs for potential-free contacts.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

8 / 60

INKNXHIT001R000 with HITACHI RC

Figure 2.2 INKNXHIT001R000 connection diagrams

Max. 500 m

Connection to AB bus. Two wire cable.

KNX TP-1 (EIB) bus

A B

Remote Controller

AC Unit

A B



KNX

COM

IN4

IN3

IN2

IN1

HITACHI

A B

AC Indoor Unit

Internal electronic control

Binary inputs for potential-free contacts.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

9 / 60

3. Configuration and setup

This is a fully compatible KNX device which must be configured and setup using standard KNX tool ETS.

ETS database for this device can be downloaded from:

https://intesis.com/products/ac-interfaces/hitachi-gateways/hitachi-knx-inputs-vrf-hi-rc-knx-1i

Please consult the README.txt file, located inside the downloaded zip file, to find instructions on how to install the database.

Important: Do not forget to select the correct settings of AC indoor unit being

connected to the INKNXHIT001R000. This is in "Parameters" of the device in ETS.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

10 / 60

4. ETS Parameters

When imported to the ETS software for the first time, the gateway shows the following default parameter configuration:

Figure 4.1 Default parameter configuration

With this configuration it’s possible to send On/Off (Control_ On/Off), change the AC Mode (Control_ Mode), the Fan Speed (Control_ Fan Speed), the Vane Position (Control_ Vanes U-D) and also the Setpoint Temperature (Control_ Setpoint Temperature). The Status_ objects, for the mentioned Control_ objects, are also available to use if needed. Also objects Status_ AC Reference Temp and Status_ Error/Alarm are shown.

Figure 4.2 Default communication objects

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

11 / 60

4.1 General dialog

Inside this parameter’s dialog it is possible to activate or change the parameters shown in the Figure 4.1.

The first field shows the URL where to download the database and the user manual for the product.

4.1.1 INKNXHIT001R000 is master in AB bus

This parameter changes the gateway’s behavior, being able to program it as master or slave in AB bus.

o If set to “no”, the gateway will work as a slave and it will be necessary to have a Hitachi

remote controller configured as a master.

o If set to “yes” the gateway will be master of the bus. It is not necessary to have any

Hitachi remote controller in this case but, if there are, they must be configured as slave. The next parameter is also shown when selecting INKNXHIT001R000 as master in AB bus:

Figure 4.3 Parameter detail

4.1.2 Send READs for Control_ objects on bus recovery

When this parameter is enabled, INKNXHIT001R000 will send READ telegrams for the group addresses associated on its Control_ objects on bus recovery or application reset/start-up.

o If set to “no” the gateway will not perform any action. o If set to “yes” all Control_ objects with both Transmit (T) and Update (U) flags enabled

will send READs and their values will be updated with the response when received.

Figure 4.4 Parameter detail

➢ Delay before sending READs (sec):

With this parameter, a delay can be configured between 0 and 30 seconds for the READs sent by the Control_ objects. This is to give time enough to other KNX devices on the bus to start-up before sending the READs.

4.1.3 Scene to load on bus recovery / startup

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

12 / 60

This parameter executes a selected scene on bus recovery or startup, only if the selected scene has an enabled preset or values previously saved from KNX bus (see Scene Configuration dialog).

If the gateway is disconnected from the indoor unit the scene will not be applied, even when connecting to the indoor unit again.

Figure 4.5 Parameter detail

4.1.4 Disallow control from remote controller

This parameter allows:

1- Having the remote controller always locked, or 2- Decide through a new communication object if the RC is locked or not.

o If set to “yes” all the actions performed through the remote controller will be disabled. o If set to “no” the remote controller will work as usually. It also appears a new

parameter and the communication object Control_ Lock Remote Control.

Figure 4.6 Communication object and parameter detail

➢ Enable comm obj “Ctrl_ Remote Lock”:

If set to “no” the object will not be shown.

If set to “yes” the Control_ Lock Remote Control object will appear.

• When a “1” value is sent to this communication object, the remote controller

is locked. To be unlocked a “0” value must be sent. The gateway remembers the last value received even if a KNX bus reset/failure happens.

Important: If an initial scene is enabled and it has as Value for Remote Lock

(unchanged) or unlocked, this would unlock the remote controller because the initial scene has priority over the Control_ Lock Remote Control communication object.

4.1.5 Enable func “Control_ Lock Control Obj”

This parameter shows/hide the Control_ Lock Control Obj communication object which, depending on the sent value, locks or unlocks ALL the Control_ communication objects except itself.

o If set to “no” the object will not be shown.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

13 / 60

o If set to “yes” the Control_ Lock Control Objects object will appear.

• When a “1” value is sent to this communication object, all the Control_

objects will be locked. To unlock a “0” value must be sent, as the gateway remembers the last value received even if a KNX bus reset/failure happens.

4.1.6 Enable use of objects for Filter

This parameter shows/hides Control_ Reset Filter and Status_ Filter Status that lets reset the filter status and also monitor if there is a filter alarm.

o If set to “no” the object will not be shown. o If set to “yes” Control_ Reset Filter and Status_ Filter Status objects will appear.

• When a “0” value is shown in the Status_ object, it indicates no filter alarm.

When a “1” value is shown in the Status_ object, it indicates that the filter is full. Once the filter has been cleaned, alarm should be reset sending a “1” value to the Control_ Reset Filter object.

4.1.7 Enable func “Operating Time Counter”

This parameter shows/hides the Status_ Operation Sec Counter communication object which counts the number of operating seconds for the INKNXHIT001R000.

o If set to “no” the object will not be shown. o If set to “yes” the Status_ Operation Time Counter object will appear. It also appears a

new parameter.

• This object can be read and sends its status every time a whole functioning

hour (3600s) is counted. The gateway keeps that count in memory and the status is sent also after a KNX bus reset/failure. Although this object is marked as a Status_ object it also can be written to update the counter when needed. To reset the counter should be written a “0” value.

Important: This object comes by default without the write (W) flag

activated. If is necessary to write on it, this flag must be activated.

Important: This object will also return its status, every time a value is

written, only if it’s different from the existing one.

Important: If the stored value is 0 hours, the gateway will not send the

status to KNX.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

14 / 60

➢ Enable func “Operating Hours Counter”:

If set to “no” the object will not be shown.

If set to “yes” the Control_ Operation Hour Counter object will appear.

• It provides same functionality as Status_ Operating Sec Counter but provides

information in hours instead of seconds.

Important: This object comes by default without the write (W) flag

activated. If is necessary to write on it, this flag must be activated.

Important: This object will also return its status, every time a value is

written, only if it’s different from the existing one.

Important: If the stored value is 0 hours, the gateway will not send the

status to KNX.

4.1.8 Enable object “Error Code [2byte]”

This parameter shows/hides the Status_ Error Code communication object which shows the indoor unit errors, if occurred, in numeric format.

o If set to “no” the object will not be shown. o If set to “yes” the Status_ Error Code [2byte] object will appear.

• This object can be read and also sends the indoor unit error, if occurred, in

numeric format. If a “0” value is shown that means no error.

4.1.9 Enable object “Error Text Code [14byte]”

This parameter shows/hides the Status_ Error Text Code communication object which shows the indoor unit errors, if occurred, in text format.

o If set to “no” the object will not be shown. o If set to “yes” the Status_ Error Text Code object will appear.

• This object can be read and also sends the indoor unit error, if occurred, in

text format. The errors shown have the same format as at the remote

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

15 / 60

controller and at the error list from the indoor unit manufacturer. If the object’s value is empty that means no error.

4.2 Mode Configuration dialog

Figure 4.7 Default Mode Configuration dialog

All the parameters in this section are related with the different mode properties and communication objects.

The byte-type communication object for Mode works with the DTP_20.105. Auto mode will be enabled with a “0” value, Heat mode with a “1” value, Cool mode with a “3” value, Fan mode with a “9” value and Dry mode with a “14” value.

4.2.1 When Mode is AUTO Status_ objs report actual operating status (HEAT/COOL/..)

When set to “no” (default) Status_ objects for operating mode will report ‘AUTO’ as operating mode while indoor unit is in AUTO mode.

If set to “yes”, Status_ objects for operating mode will report actual operating mode of the whole system (‘HEAT’ or ‘COOL’), according to status reported by the indoor unit.

4.2.2 Enable use of Heat / Cool bit-type obj

This parameter shows/hides the Control_ and Status_ Mode Cool/Heat communication objects.

o If set to “no” the objects will not be shown.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

16 / 60

o If set to “yes” the Control_ and Status_ Mode Cool/Heat objects will appear.

• When a “1” value is sent to the Control_ communication object, Heat mode

will be enabled in the indoor unit, and the Status_ object will return this value.

• When a “0” value is sent to the Control_ communication object, Cool mode

will be enabled in the indoor unit, and the Status_ object will return this value.

4.2.3 Enable PID-Compat. Scaling Mode Objects

This parameter shows/hides the Control_ Mode Cool & On and Control_ Mode Heat & On communication objects.

o If set to “no” the objects will not be shown. o If set to “yes” the Control_ Mode Cool & On and Control_ Mode Heat & On objects will

appear.

• These objects provide compatibility with those KNX thermostats that control

the demand of heating or cooling by using scaling (percentage) objects. In these thermostats, the percentage demand is meant to be applied on a fluid valve of the heating / cooling system.

• INKNXHIT001R000 device does not provide individual control on the internal

parts of the indoor unit (as can be its compressor, refrigerant valves, etc). Rather, it provides the same level of control as a (user) remote controller.

• Objects “Control_ Mode Cool & On” and “Control_ Mode Heat & On” intend to

bring compatibility between thermostats oriented to the control of custom heating / cooling systems and ready-made AC indoor units, by applying the following logic:

• Whenever a non-zero value (>0%) is received at “Control_ Mode Cool

& On”, indoor unit will switch On in COOL mode.

• Whenever a non-zero value (>0%) is received at “Control_ Mode Heat

& On”, indoor unit will switch On in HEAT mode.

• Lastest updated object will define the operating mode

• Indoor unit will switch off only when both objects become zero (0%) –

or when an OFF is requested at object “0. On/Off [DPT_1.001 - 1bit]”

Important: These objects function is only to send On/Off and Cool/Heat to the indoor

unit. The PID (Inverter system) is calculated by the indoor unit itself. Please consider introducing an appropriate PID configuration to the external KNX thermostat to not interfere the indoor unit PID.

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

17 / 60

4.2.4 Enable use of +/- object for Mode

This parameter shows/hides the Control_ Mode -/+ communication object which lets change the indoor unit mode by using two different datapoint types.

o If set to “no” the object will not be shown. o If set to “yes” the Control_ Mode -/+ object and a new parameter will appear.

Figure 4.8 Parameter detail

➢ DPT type for +/- Mode Object

This parameter lets choose between the datapoints 0-Up / 1-Down [DPT_1.008] and 0-Decrease / 1-Increase [DPT_1.007] for the Control_ Mode -/+ object.

The sequence followed when using this object is shown below:

Important: Read the documentation of your indoor unit to check if it has AUTO

mode available.

4.2.5 Enable use of bit-type Mode objects (for control)

This parameter shows/hides the bit-type Control_ Mode objects.

o If set to “no” the objects will not be shown. o If set to “yes” the Control_ Mode objects for Auto, Heat, Cool, Fan and Dry will appear.

To activate a mode by using these objects a “1” value has to be sent.

4.2.6 Enable use of bit-type Mode objects (for status)

▪ Up / Increase

▪ Down / Decrease

DRY

AUTO

HEAT

COOL

FAN

Intesis

KNX – Hitachi

User's manual r1.3 EN

This information is subject to change without notice

URL https://www.intesis.com

18 / 60

This parameter shows/hides the bit-type Status_ Mode objects.

o If set to “no” the objects will not be shown. o If set to “yes” the Status_ Mode objects for Auto, Heat, Cool, Fan and Dry will appear.

When enabled, a mode will return a “1” through its bit-type object.

4.2.7 Enable use of Text object for Mode

This parameter shows/hides the Status_ Mode Text communication object.

o If set to “no” the object will not be shown. o If set to “yes” the Status_ Mode Text object will appear. Also, in the parameters, will be

shown five text fields, one for each mode, that will let modify the text string displayed by the Status_ Mode Text when changing mode.

Figure 4.9 Parameter detail

4.3 Special Modes Configuration dialog

Figure 4.10 Default Special Modes Configuration dialog

The Special Modes can be parameterized through the ETS parameters dialog, and they can be used to give extra functionality.

+ 42 hidden pages

HMS KNX, Intesis User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual