Escolar Documentos
Profissional Documentos
Cultura Documentos
Technical Catalog
Specifications in this manual are subject to change without notice in order that
HITACHI may bring the latest innovations to their customers.
Although every effort is made to ensure that the specifications are correct, printing errors
are beyond HITACHIs control, and it will accept no responsibility for such errors.
Contents of parts
Contents of parts
General characteristics
KNX001 Installation
Operation and configuration
pag 5
1
2
3
Contents of parts
Contents
1.
General characteristics...............................................................................................9
1.1
Introduction............................................................................................................................................ 10
1.2
Operation . .............................................................................................................................................11
1.3
Limitations..............................................................................................................................................11
1.4
2.
KNX001 Installation..................................................................................................13
2.5. Operation............................................................................................................................................... 19
3.
3.1
Introduction............................................................................................................................................ 22
3.2
Projects.................................................................................................................................................. 22
3.3
3.4
Configuration of KNX001....................................................................................................................... 26
3.5
Connection settings............................................................................................................................... 27
3.6
3.7
Reminder............................................................................................................................................... 33
3.8
Restrictions............................................................................................................................................ 33
3.9
Preliminary specification........................................................................................................................ 33
pag 7
General
characteristics
1. G e n e r a l c h a r a c t e r i s t i c s
Contents
1.
General characteristics...........................................................................9
1.1
Introduction....................................................................................................................10
1.2
Operation . ....................................................................................................................11
1.3
Limitations.....................................................................................................................11
1.4
pag 9
General
characteristics
1.1 Introduction
A Hitachi Air-Conditioning system is integrated with a KNX system using CSNET WEB and the KNX001 device.
The types of machines to connect are Packaged and Chiller. It is not permitted to connect both types simultaneously. In
the case of Packaged machines up to 128 units are supported, and in the case of Chiller up to 8 machines.
These two types of machine offer a interfaces with different signals. The signals available for each machine, depending
on the model, are presented below:
Packaged
Name
Description/State
OnOff
On/Off
Mode:
Fan:
Fan speed
TempSet
Louver
Central
TIn
Inlet Temperature
TOut
Outlet Temperature
TGas
TLiquid
ErrorCode
Error code
StopCause
ValveOpen
OperCondition
Operation status
Defrost
Defrost
ExtAmbTemp
Timer
Time controlled
Communication Error
Chiller
Name
Description/State
OnOff
On/Off
Mode:
TempSet
Central
WaterTIn
WaterTOut
ErrorCode
Error code
OperCondition
Operation status
Defrost
Defrost
ExtAmbTemp
Timer
Time controlled
Communication Error
page 10
General
characteristics
1.2 Operation
Each of the previous signals must be associated with an address of Group KNX, so that the whole set behaves
as one more part of the KNX system with the same configuration and operation characteristics.
IU
IU
EIB
KNX
HGT
Configuration
Software
KNX001
EIB
Ethernet
IU
CSNET WEB
H-Link
RS232
Only during configuration
KNX001 performs continuous polling (reading) of all the signals configured in CSNET WEB and keeps their status
updated in order to serve as information to the KNX system.
When a change of status is detected in a signal, a written message is sent to the KNX bus of the associated KNX Group.
When a written message is received from the KNX bus to a KNX Group that is associated with the signal, the
corresponding message is sent immediately to CSNET WEB so that is can perform the appropriate action.
In the initial process after start-up of KNX001, a search is performed for the configured units (machines). If no unit is
detected, this is indicated by the communication error signal associated with each unit.
1.3 Limitations
Element
Maximum
Notes
No. Packaged
160
No. IU A/C
No. Chillers
No. Chillers
5920
1000
255
pag 11
General
characteristics
Description
Signal
EIS (DataPoint)
The type of KNX data item used to express the value of the signal. Depends on the type of external system
signal in each case. In some integrations it can be selected, while in others it is fixed, given the intrinsic
nature of signals.
Group
The KNX group with which the signal is associated. It is also the group to which reading (R), writing (W),
transmission (T) and updating (U) are applied. It is the sending group.
Listening
addresses
Addresses that will act on the signal apart from the Group.
Transmission. If enabled, when the value of the signal changes due to a change in the value of the external
system, a write message will be sent from the Group to the KNX bus.
Update. If enabled, on starting KNX001 or after the KNX bus falls over, read messages will be sent
to the KNX bus of the sending group. The value received will be sent to the external system as if it had
been received by written message. If U2 is selected, instead of using the address of the sending group,
the first listening address will be used.
Enable
If enabled, the signal is enabled in IntesiBox, otherwise it behaves as if the signal has not been defined
or does not exist. Permits signals to be disabled, without having to delete them.
page 12
KNX001 Installation
2. K N X 0 0 1 I n s t a l l a t i o n
Contents
2.
KNX001 Installation..............................................................................13
2.5. Operation.......................................................................................................................19
page 13
KNX001 Installation
Caution
This interface KNX001 must be installed by skilled personal (electrician, EIB installer or other skilled technician).
Do not connect voltage input to the control system before installation has been correctly completed.
Read this manual carefully before performing installation work.
Read this manual in order to configure the KNX001.
Attention
Do not install KNX001 in places... :
outdoor.
Attention
Install KNX001 away from possible sources of electromagnetic waves.
Respect local electrical standards.
Use a power circuit that is not subject to peak demands.
Ensure that there is enough free space around the KNX001 so that the heat may dissipate adequately
(refer to Installation Work).
If you install the KNX001 in vertical position, install the power supply in the lower part and the temperature control
outputs in the upper part.
Components supplied:
KNX001 device
Component names:
1. Power Supply Terminals
2. CSNET WEB Port
4
page 14
KNX001 Installation
2.3. Specifications
Cover
Dimensions
Weight
2 kg
Power Supply
Assembly
KNX Port
1 x KNX TP1 (EIB) Opto insulated. Screw type removable (2 poles) for 2.5 mm2 (12 AWG) cable
Indicators LED
1 x Power Supply.
2 x Ethernet Port activity (LNK, ACT).
Push button
1 x programming KNX.
Port type
Configuration
By RS232 port.
Firmware
Temperature range
-40C a +70C
Relative Humidity
Protection
IP20 (IEC60529).
RoHS Conformity
Certification
CE
(mm)
90
page 15
KNX001 Installation
Wall Assembly
Pull the upper plastic parts and lower plastic part outside until fixing holes are visible from front side and a click is
heard (see right figure below).
Back side view
Hang upper side of the device from the upper side of DIN profile. Using a screwdriver pull the lower plastic part (see
drawing) and push the lower side of the device against the profile.
Side view
page 16
KNX001 Installation
Servicing space
Minimum space recommended for the interface and its external connections.
(mm)
Ethernet Port
+
Power supply
KNX Port
100
PC Console
115
page 17
130
KNX001 Installation
See Note 2
Power Supply
See Note 1
Notes:
1. Use always a DC Power Supply:
Keep correctly polarity in terminals + & -. Ensure that supplied voltage are between allowed limits (9 a 30 VDC).
If power source is grounded, connect - terminal only to ground circuit, never + terminal.
If it is used a AC Current:
Ensure that power supply is 24 VAC. Do not connect any terminal to ground circuit and do not connect any other
device that could suffer any earth leakage current in their terminals.
2. CSNET WEB connection can be done directly by ethernet crossed cable CAT5 or directly from LAN installation of the
building. In the last case used non crossed ethernet CAT5 cable in order to connect KNX001. Consult to computer net
administrators for TCP connection. KNX001 is connected to CSNET WEB by port 502.
3. Use HGT software for KNX001 configuration. Check HGT user manual for details.
page 18
KNX001 Installation
2.5. Operation
Unit types to be connected to KNX001 are Packaged and Chiller. It is not allowed to connect both types simultaneously.
Maximum Packaged units supported are 128 indoor units. In case of Chiller, maximum number are 8 Chillers.
These two tipes of units require different signals in interface. Next table shows signals for each type of unit.
Packaged
Name
Description/State
OnOff
Mode
Fan
TempSet
Setting Temperature
Read/Write: 17C ~ 30C
Louver
Louver Setting
Read/Write: 8 positions: 0 ~ 7 and AUTO
Central
Central Setting
Read/Write: OnOff, Mode, TempSet, Fan
TIn
Inlet Temperature
Read: C
TOut
Outlet Temperature
Read: C
TGas
TLiquid
ErrorCode
Alarm Code
Read: 0 ~ 100
StopCause
ValveOpen
OperCondition
Defrost
Defrost
Read: On, Off
ExtAmbTemp
Ambient Temperature
Read: C
Timer
Timer disabled
Read/Write: Enabled/Disabled
Error Comunicacin
page 19
KNX001 Installation
Chiller
Name
Description/State
OnOff
Mode
TempSet
Setting Temperature
Read/Write: C
Central
Central Setting
Read/Write: Local, Remoto
WaterTin
WaterTOut
ErrorCode
Alarm Code
Read: 0 ~ 100
OperCondition
Defrost
Defrost
Read: On, Off
ExtAmbTemp
Ambient Temperature
Read: C
Timer
Timer disabled
Read/Write: Enabled/Disabled
Error Comunicacin
CSNET WEB is a device that acts as an interface or gateway between the H-Link bus and an Ethernet connection.
The H-Link bus interconnects Packaged or Chiller units with CSNET WEB. La Ethernet connection is used
by the KNX001 gateway to access the machines.
As a previous step to the configuration of KNX001, CSNET WEB must be configured, along with the machines
or a/c units themselves.
For more information refer to the CSNET WEB documentation.
page 20
Operation and
configuration
3. O p e r a t i o n a n d c o n f i g u r a t i o n
Contents
3.
3.1
Introduction....................................................................................................................22
3.2
Projects..........................................................................................................................22
3.3
3.4
Configuration of KNX001...............................................................................................26
3.5
Connection settings.......................................................................................................27
3.6
3.7
Reminder.......................................................................................................................33
3.8
Restrictions....................................................................................................................33
3.9
Preliminary specifications..............................................................................................33
page 21
Operation and
configuration
3.1 Introduction
HGT software is a tool for configuring and monitoring operation of KNX001 equipment via a serial cable an RS232 port
of the PC. It works in any Microsoft Windows operating system.
KNX001 configuration is divided in 2 parts: Connection and Signals. This information is stored in 2 or more text files.
Once the desired configuration is completed, a binary file is generated and sent to the KNX001.
It is not necessary to be connected to the KNX001 in order to configure the integration. Instead this can be done
in the office and later downloaded to the KNX001 in the installation.
Once KNX001 has a power supply and is connected with a serial cable to the PC where HGT is run, enable the
On Line checkbox. Information about the equipment will appear in the viewfinder of the Communication Console.
Once the configuration is completed, press the Send File button and the configuration will be downloaded.
After a few seconds KNX001 will restart and will use the new configuration.
The HGT software has a user interface in a number of languages. Select the most suitable language from the
Configuration menu Languages.
3.2 Projects
The first step in making a new installation is to create a new project. A new project consists of a project name, project
description (optional) and the type of Hitachi machines to be used. Either KNX001-PACKAGED or KNX001-CHILLER
can be selected.
When a new project is created, a new directory is created with the name of the project. It contains the configuration files
necessary for the KNX001.
In order to avoid overwriting the configuration of other existing projects, it is highly recommended that a new project
be created for each new installation. If a KNX001 configuration is lost, there is no way of recovering it from inside
the KNX001.
The folder where the projects are created is FolderApplication\ProjectsHGT, where FolderApplication is the folder in
which HGT is installed (by default C:\Program Files\Hitachi\HGT). Within the projects folder, a new folder is created
for each new project with the files that contain the project configuration.
When HGT is opened the project selection window appears, permitting a project to be selected or created. Two Demo
projects appear, one for each type of machine. A new project can be created empty, or a new project can be created
based on an existing one. In this case, the new project will be a copy of the original, which in certain cases may save
configuration work.
page 22
Operation and
configuration
To create a new project, select a project with the same external protocol as the one you want to use and press New.
You will be asked whether a copy of a selected project or a new one is to be created.
If you select Yes, you will be able to specify the name and description of the new project, based on the same external
protocol selected. If you select No, you will also be able to select the type of machines to use in the new project.
When you accept, a new folder will be created within the project folder, with the name of the project. If you select new
project without copying from another, the configuration by default will be that defined in the template files. Otherwise,
it will be the same as that of the copied project.
page 23
Operation and
configuration
4. Enable the checkbox off-line under the menu bar (it will change to on-line) and HGT will ask for INFO from
KNX001. If the connection is correct, KNX001 will respond with its identification (this can be supervised via
the console window of communication with KNX001, as shown in the image). This window shows information
messages where the KNX groups appear with their value when changes in their status occur.
Once connected, all HGTs supervision and monitoring options are available.
To monitor communication between KNX001 and the KNX Bus, select the menu See -> Bus -> EIB. The window
of the Communication viewfinder of KNX will be opened. This window shows in real time the communication links
with the KNX bus, along with information messages.
page 24
Operation and
configuration
To monitor communication between KNX001 and CSNET WEB, select the menu See -> Bus -> CSNET WEB.
The window of the Communication viewfinder of the external system will be opened. This window shows
in real time the communication links with the external system, along with information messages.
3
Both windows permit communications to be recorded in a text file with extension .log. This function will only be used
for the resolution of problems for technical service. To use it, enable the check box Log to File.
To supervise the status of the signals configured, select the menu See -> Signals. The window of the Signals viewfinder
will be opened. This window shows in real time the status of the signals configured. After a reset of KNX001, or after
sending a configuration file, all the signals are updated automatically. If connecting to a KNX001 that is already in
operation, you must press the button, Refresh, once only to update the status of all signals. While you maintain the
connection the signals will be kept updated.
The signals viewfinder can be used even if only one of the two systems is connected, KNX or CSNET WEB. It is very
useful for supervision and tests.
Double-clicking on any cell of a row, allows the status of a signal to be modified. If the signal has T enabled, its value
will be updated and a message will be sent to KNX with this value, in the same way as if it had been written from
CSNET WEB. If the signal has W enabled, its value will also be sent to CSNET WEB, in the same way as if it had been
written from KNX.
page 25
Operation and
configuration
This functionality is very useful for testing both the KNX system and CSNET WEB, without having to act on the real
signals of the machines.
The window has a button to copy all the content of the window, in text format separated by tabs, to the Windows
clipboard.
page 26
Operation and
configuration
1
2
3
KNX001 TCP/IP configuration
1. KNX001 IP address. It must be in the same network segment as CSNET WEB if it does not use the IP gateway.
2. Network mask. Determine the network segment.
3. If KNX001 is in another network segment different from CSNET WEB, enter the IP address of the router,
without leaving it blank.
1
2
3
KNX configuration
1. Selection of the physical address of the KNX device that KNX001 will have.
2. Indicates whether, after a reset of KNX001 or recovery of the KNX bus, read requests will be made
to the KNX bus for the group addresses with flag U or U2 enabled.
3. Indicates the time in seconds that these requests will be delayed to prevent overload in the KNX bus,
due to other KNX devices behaving in the same way.
page 27
Operation and
configuration
page 28
Operation and
configuration
8 9 10 11 12
1. Signal number. Each line of the table corresponds to a signal. Signals cannot be added or deleted, because
the signals available are fixed and can only be enabled or disabled. Serves only to number the rows.
2. Device no. in the list of devices of the Connection tab to which the signal belongs. Not editable.
3. Code. Identifies each signal. A code appears beside each name to identify it. Section 1.1 gives the meaning
of each signal. The right button makes a contextual menu appear showing all the possible codes. Not editable.
4. Long description of the signal. This description corresponds to the Code. It indicates if the signal is read R and/or
write W.
5. EIS The KNX EIS type (Data point), the format in which the signal value is transmitted. The right button makes
a contextual menu appear showing all the possible types. Not editable.
6. Group. It is the KNX group with which the signal is associated and to which reading (R), writing (W),
transmission (T) and updating (U) are applied. It is the sending group. Editable.
7. Listening addresses. KNX group addresses that will act on the signal, apart from the Group.
8. R. Read. If enabled, it will permit read messages from this Group.
9. W. Write. If enabled, it will permit write messages from this Group.
10. T. Transmission. If enabled, when the value of the signal changes due to a change in the value of the external
system, a write message will be sent from the Group to the KNX bus.
11. U. Update. If enabled, on starting KNX001 or after the KNX bus falls over, read messages will be sent
to the KNX bus of the sending group. The value received will be sent to the external system as if it had
been received by written message. If U2 is selected, instead of using the address of the sending group,
the first listening address will be used.
12. Enable. Permits the use of each signal to be enabled or not. Enabled signals must have a valid KNX configuration.
Only signals that are going to be used from KNX should be enabled.
page 29
Operation and
configuration
The R, W, T, U and Enable columns can be modified by double-clicking on the cell, marking one or more cells of
the same column and using the contextual menu with the right button, or pressing the key of the first letter of the word.
The R, W, T, U columns appear by default with a correct selection. Do not modify the selection if you are not sure
how it will affect the integration.
Some cells of column Code appear in an orange color. Using the right button of the mouse pointer to make the contextual
menu appear, permits Show/Hide the Selection or All.
If Show/Hide is selected Selection, the new signals appear or disappear. These signals are the ones called Multibit,
and have the following use. There are signals that have a limited number of possible values, for example, 0-1-2-3-4,
which can be used with EIS6 (8 bits value). However, it may be necessary or helpful to act on this from simpler objects,
such as an EIS1 switch (switching). The new signals that appear marked in yellow allow a specific value of the signal
to be acted via an EIS1.
Show/Hide Selection this can also be done by double-clicking on the orange cells.
Show/Hide All affects all the orange colored cells in the table. Although the multibit signals are shown, they will not be
used until they are enabled in the column Enable.
page 30
Operation and
configuration
The following image shows the table without pulling down to view the multibit signals.
The following image shows the table with a signal with the multibit signals option pulled down.
page 31
Operation and
configuration
The following image shows all the multibit signals pulled down.
By default, all multibit signals are shown pulled down. If they are not going to be used you can do Hide-All to have a table
with fewer signals in order to work more comfortably.
It is permitted to enable byte and multibit signals simultaneously. The bits will be updated according to the status they
represent. Only one of the multibit signals will be enabled at any time, except in the case of the Centralsignal, since
in this case various bits can be enabled simultaneously.
In the previous images the signals belonging to the Packaged type are shown. In the next image those belonging
to the Chiller type are shown.
page 32
Operation and
configuration
3.7 Reminder
If T is not enabled, changes in the external system will not be transmitted to KNX nor to its links.
If R is not enabled, signals cannot be read via Read requests from KNX.
If W is not enabled, it will not be possible to act on the signal, nor the external system, nor group links.
If U is enabled, on starting up KNX001, READ requests will be made to the KNX of the sending group.
If U2 is enabled, on starting KNX001, READ requests will be made to the KNX of the first listening address.
Groups that are defined only as links will take the EIS type from the first linked group.
The group data read from KNX as a result of READ requests between other KNX devices will be treated
as Writes on groups (standard BCU1 behavior).
Signals marked as read R must be configured: Fixed:T, Optional:R
Signals marked as write W must be configured: Fixed:W, Optional:U o U2
Signals marked as read/write RW must be configured: Fixed:W-T, Optional:R or U or U2
Types are converted automatically, i.e. if an EIS5 arrives at an EIS1 group, an EIS1=(EIS5<>0) is made,
or EIS5=EIS9 and EIS9=EIS5, EIS6=EIS5(0..255), etc.
It is recommendable that the listening addresses associated with different groups maintain the same EIS type
in all groups, otherwise unwanted conversions may occur.
A write from KNX is propagated to the external system via the group address and the listening addresses.
A write from the external system DOES NOT propagate to KNX via the listening addresses, but DOES update
the status of the local send groups that are used as listening addresses.
If a send group is used as the listening address with other local send groups, a write from the external system will
update these groups but not their listening addresses.
In case of Resetting the KNX bus, if this behavior is enabled, updating of groups marked as U or U2 is forced.
3.8 Restrictions
P/I/S, P/S group numbers are permitted, or the coded group no. directly
Repeated send groups are not permitted (Group column).
Group 0 is not permitted, This is used for signals without a send group.
Signals are not permitted if R-W-T-U is not enabled.
Empty Groups are not permitted if only W is enabled and it has listening addresses.
Repeated groups are not permitted in the same listening addresses field.
It is not permitted for a send group to be in the listening addresses (circular reference).
Listening addresses are not permitted if W is not enabled, otherwise the listening addresses will not function.
page 33
Operation and
configuration
3.10 Files
KNX001 saves the configuration of each project in the following files:
<TYPE>.INI
A text file that saves information regarding the connection and other special adjustments.
<TYPE>.DAT
A text file with values separated by tabs, with information corresponding to the signals.
<TYPE>.HGT
A binary file created from the files mentioned above. It is the one really sent to KNX001.
NOTE
Do not touch these variables if you are not sure how they work. Their maladjustment may cause KNX001 not to operate
or to operate incorrectly.
page 34