Intesis
TM
KNX
– Mitsubishi Heavy Industries AC
User’s Manual r1.2 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
8 / 26
KNX interface of Intesis
TM
Description
Intesis
TM
KNX - Mitsubishi Heavy Industries supports the KNX TP-1 (EIB) physical layer, as
defined in the KNX standard. It behaves as
another
device of the KNX system, with the
same configuration and functional characteristics as other KNX devices.
KNX TP-1 (EIB) bus provides a 30V DC current, which can even directly power certain low-
consumption KNX devices. Intesis
TM
does not drain any significant current from the KNX bus
- it has a separate own power supply. Another important electrical aspect is that the KNX
TP-1 (EIB) port of Intesis
TM
is optically isolated (~2500Vrms AC) from all its other ports
(EIA232, EIA485, Ethernet) and power supply.
At a logical level, all KNX devices feature an interface of communication objects, by which
their functionality is abstracted. As a basic example, a KNX interface of an AC indoor unit
would typically consist of an interface of datapoints such as “On/Off”, “Setpoint
temperature”, “Operating mode”, etc.
Associations between communication objects from different KNX devices are actually done
by means of so-called group addresses.
KNX telegrams within a working KNX installation are always addressed to a certain KNX
group address. Typically, whenever a communication object on a KNX device changes its
value, the new value is updated to the bus, by sending a “write” telegram addressed to its
associated group address. The rest of KNX devices in the installation that have a
communication object associated to this group address will act accordingly on reception of
the new value.
Other operations are possible. KNX devices can also decide to read the current value of the
communication objects, by sending a “read” telegram to a certain group address (previously
known to be associated to the targeted comm. object). This operation is performed by many
devices on bus start-up or recovery
–
in this way, the device gets the latest value of the
group addresses it has associated right from its start-up.
Each datapoint defined in Intesis
TM
KNX configuration needs at least a single KNX group
address associated with it. This group address will be used either for sending updates
to
KNX of the datapoint value (that have been generated on the other MHI interface of the
Intesis
TM
), or receiving updates
from
KNX of the datapoint value (that will be propagated to
the MHI side in this case)
From the point of view of KNX functionality, each datapoint of Intesis
TM
can hold following
group address associations:
•
A single KNX group address with which update/write telegrams will be sent,
whenever the datapoint changes (as a result of a change coming from the other
interface of Intesis
TM
, MHI in this case).
•
One or more KNX group addresses from which this datapoint of Intesis
TM
will be
updated/written from the KNX installation (resulting in a change to the other side of
Intesis
TM
, MHI in this case).
A single KNX group address from which Intesis
TM
will read the object value on KNX bus
recovery / Intesis
TM
start-up.
