HMS Intesis KNX Mitsubishi Electric CC User manual

Gateway for integration of Mitsubishi Electric City Multi air conditioning
systems to KNX home automation systems
USER MANUAL
Issue date: 05/2019 r1.1 ENGLISH

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
2 / 32
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.

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
3 / 32
Gateway for integration of Mitsubishi Electric City Multi air
conditioning systems into KNX home automation systems.
ORDER CODE
LEGACY ORDER CODE
INKNXMIT015C000
ME-AC-KNX-15
INKNXMIT100C000
ME-AC-KNX-100

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
4 / 32
INDEX
1Description ............................................................................................................................................................5
Introduction....................................................................................................................................................5
Functionality ..................................................................................................................................................6
Capacity of INKNXMIT---C000......................................................................................................................6
2KNX System..........................................................................................................................................................7
Description.....................................................................................................................................................7
Points definition.............................................................................................................................................7
3Connections ..........................................................................................................................................................9
Power device...............................................................................................................................................10
Connect to Mitsubishi’s Centralized Controller(s). ......................................................................................10
Connection to KNX......................................................................................................................................10
Connect to PC (Configuration tool) .............................................................................................................10
4Set-up process and troubleshooting ...................................................................................................................11
Pre-requisites ..............................................................................................................................................11
Intesis MAPS. Configuration & monitoring tool for Intesis ..........................................................................11
4.2.1 Introduction..........................................................................................................................................11
4.2.2 Connection...........................................................................................................................................11
4.2.3 Configuration tab .................................................................................................................................12
4.2.3.1 KNX Configuration........................................................................................................................12
4.2.3.2 Mitsubishi Electric Configuration..................................................................................................15
4.2.4 Signals.................................................................................................................................................20
4.2.5 Sending the configuration to Intesis ....................................................................................................20
4.2.6 Diagnostic............................................................................................................................................21
Set-up procedure.........................................................................................................................................22
5Electrical & Mechanical Features........................................................................................................................23
6Dimensions .........................................................................................................................................................24
7Appendix A –Communication Objects Table .....................................................................................................25

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
5 / 32
1 Description
Introduction
This document describes the integration of Mitsubishi Electric’s City Multi series air conditioning systems into KNX
compatible devices and systems using the Intesis KNX to Mitsubishi Electric’s Centralized Controller communication
gateway.
The aim of this integration is to monitor and control your Mitsubishi Elecitric City Multi air conditioning system, from
your KNX TP-1 installation. To do it so, Intesis performs as a one more KNX device, sending and receiving telegrams
to group addresses in the KNX network.
This integration requires the Mitsubishi Electric City Multi AC system to be equipped with a Mitsubishi Electric’s
Centralized Controller for MNET (G-50A, GB-50A, AG-150A, EB-50, EW-50 or AE200 and newer). This Centralized
Controller offers the signals of the City Multi AC system through XML protocol at its Ethernet port, which is accessed
by the Intesis. Every Centralized Controller from Mitsubishi Electric allows access to the signals of up to 50 City Multi
indoor units groups, no matter the number of outdoor units installed. In the Centralized Controller, the control unit is
the group, each of which can have from 1 to 16 associated indoor units.
MNET’s Centralized Controller is offered by Mitsubishi Electric. Each different model has different features (some
incorporate just a blind cover, others have a keyboard and an LCD panel). Mitsubishi Electric’s Expansion Controllers
can be connected to the MNET Centralized Controller in order to extend support to more than 50 indoor unit groups
(50 additional groups for each Expansion Controller). Expansion Controllers in MNET system is also supported by
Intesis.
Intesis needs to be configured using Intesis MAPS software configuration tool. In the software, KNX and MNET’s
Centralized Controller parameters must be selected and downloaded to the Intesis.
Up to 15 indoor unit groups (1 Centralized Controller) or 100 indoor unit groups (2 Centralized Controllers) are
supported, depending on the version of the gateway.
This document assumes the user is familiar with KNX and Mitsubishi Electric technologies and technical terms.
Integration of Mitsubishi's Centralized Controller into
KNX home automation systems
Mitsuibishi Electric’s M-NET
KNX TP-1
USB
configuration
TCP/IP XML
Ethernet TCP
Ethernet
configuration
NOTE: Please take into acount that most Mitsubishi Electric Centralized Controllers
require a software license, PC-Monitoring license (SW-Mon), that must be purchased
together with the controller in order that the XML interface is active and can be used by
the Intesis.
!

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
6 / 32
Functionality
IntesisTM continuously polls (reads) all the signals of the Centralized Controller groups and maintains their values
updated in the KNX group objects of the gateway interface. Corresponding WRITE telegram is sent to associated
group address when change of value is detected (or during first update).
When a WRITE telegram is received from KNX in a gateway group address associated to a writeable group object
(flag W enabled), the corresponding command is sent to the City Multi associated signal
In the continuous polling process of the Centrallized Controller, if there is no answer, it is indicated with a virtual
signal of communication error for the Centrallized Controller. In the same way, there is a communication error virtual
signal for each of the City Multi groups; normally it will be activated when this group is not configured/active in the
Centrallized Controller.
The IP address and communication parameters (polling cadence, connection timeout, …) of every Centrallized
Controller must be also configured using Intesis MAPS configuration tool, as well as KNX interface objects and
communication parameters.
From the configuration tool, it is also possible to scan the Centrallized Controller for available groups and thereafter
add them in the configuration, so that they are continuously polled.
Capacity of INKNXMIT---C000
Intesis capacity is listed below:
Element
Max.
Notes
Number of MNET Centralized
Controllers
2
Number of independent centralized controllers (if expansion
controllers are present, each expansion controller counts as
a single centralized controller)
Number of City Multi groups
100
50 groups for each centralized controller are supported
Max number of group objects
per group
90
Number of available group objects will vary according to unit
type
Max number of group objects
per Centralized Controller
4514
14 global group objects (error signaling & batch control) + 90
group object/MNET group x 50 MNET groups
Max number of KNX group
addresses
9000
Maximum number of different KNX group addresses that can
be defined.
Max number of associations
18000
Maximum number of KNX associtations (between a group
object and a group address) supported.
There are 2 different models of IntesisTM KNX –Mitsubishi Electric Centralized Controller with different capacity every
one of them. The table above shows the capacity for the top model (with maximum capacity).
The 2 different models allow integrating respectively: 1 or 2 Centralized Controllers.
Their order codes are:
•INKNXMIT015C000. Model supporting up to 15 City Multi groups.
•INKNXMIT100C000. Model supporting up to 100 City Multi groups.

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
7 / 32
2 KNX System
In this section, a common description for all Intesis KNX series gateways is given, from the point of view of KNX
system which is called from now on internal system. Connection with the Mitsubishi Electric’s Centralized Controller
is also called from now on external system.
Description
Intesis KNX connects directly to the KNX TP-1 bus and performs as one more device into the KNX system, with the
same configuration and operational characteristics as other KNX devices.
Internally, the circuit part connected to the KNX bus is opto-isolated from the rest of the electronics.
Intesis KNX receives, manages and sends all the telegrams related to its configuration to the KNX bus.
On receiving WRITE telegrams of KNX group addresses associated to communication objects, the corresponding
messages are sent to the external system (Mitsubishi Electric’s Centralized Controller).
When a change in a signal of the external system is detected, a WRITE telegram is sent to the KNX bus (addressed
with the group address associated to the corresponding group object), in order to maintain both systems synchronised
in every moment.
The status of the KNX bus is checked continuously and, if a bus drop-down is detected, for example due to failure in
the bus power supply, after the KNX bus is restored again, Intesis will send READ telegrams to group addresses of
all communication objects marked with flag ‘Ri’. The behaviour of each individual point into Intesis is determined by
the flags configured for the communication object. See details below.
Points definition
Every group object in configuration has following KNX properties:
Property
Description
Description
Descriptive information about the communication object or signal.
Object
function
Information on range of values for the group object.
DPT
Datapoint type. It is the KNX data type used to encode the signal's value. It will depend
on the type of signal associated in the external system in every case.
Group
It is the KNX group to which the point is associated. It is also the group to which the
read (R), write (W), transmit (T), update (U) and read on init (Ri) flags are applied. It is
the sending group.
Listening
addresses
They are the addresses that can write on the group object, apart of the main group
address.
R
Read. If this flag is activated, READ telegrams of this group address will be accepted.
Ri
Read on Init. If this flag is activated, the object will trigger corresponding READ request
(on associated group address) on initialization.
W
Write. If this flag is activated, WRITE telegrams on this group object will be accepted.
T
Transmit. If this flag is activated, when the group object value changes, due to a change
in the external system, a WRITE telegram of the associated group address will be sent
to the KNX bus.
U
Update. If this flag is activated, UPDATE telegrams (response to READ telegrams) on
this group object will be accepted.
Active
If activated, the point will be active in Intesis, if not, the behaviour will be as if the point
is not defined. This allows deactivating points without the need of delete them for
possible future use.

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
8 / 32
These properties are common for all Intesis KNX series gateways. Although each integration may have specific
properties according to the type of signals of the external system.
See list of communication objects, according to unit type in section 7

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
9 / 32
3 Connections
Find below information regarding the Intesis connections available.
Power Supply
Must use NEC Class 2 or Limited Power Source
(LPS) and SELV rated power supply.
If using DC power supply:
Respect polarity applied of terminals (+) and
(-). Be sure the voltage applied is within the
range admitted (check table below). The
power supply can be connected to earth but
only through the negative terminal, never
through the positive terminal.
If using AC power supply:
Make sure the voltage applied is the value
admitted (24 Vac). Do not connect any of the
terminals of the AC power supply to earth,
and make sure the same power supply is not
supplying any other device.
Ethernet / Mitsubishi C. Controller
Connect the cable coming from the IP network to the
connector ETH of the gateway. Use an Ethernet
CAT5 cable. If communicating through the LAN of the
building, contact the network administrator and make
sure traffic on the port used is allowed through all the
LAN path (check the gateway user manual for more
information). DHCP is enabled by default. When
disabled, default IP is 192.168.100.246.
Figure 3.1 Gateway’s connections
PortA / KNX
Connect the KNX TP1 bus to connectors A3 (+) and A4 (-) of gateway’s PortA. Respect the polarity.
PortB / Not used
Console Port
Connect a mini-type B USB cable from your computer to the gateway to allow communication between the
Configuration Software and the gateway. Remember that Ethernet connection is also allowed. Check the user manual
for more information.
USB
Connect a USB storage device (not a HDD) if required. Check the user manual for more information.
Ensure proper space for all connectors when mounted (see section 66).

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
10 / 32
Power device
The first step to perform is to power up the device. To do so, a power supply working with any of the voltage range
allowed is needed (check section 5). Once connected the ON led will turn on.
Connect to Mitsubishi’s Centralized Controller(s).
Connect the communication cable coming from the network hub, switch or direct from the Centralized Controller to
the Ethernet port (Figure 3.1) of the gateway. The cable to be used shall be a straight Ethernet UTP/FTP CAT5 cable.
In case there is no response from Mitsubishi Centralized Controller to the frames sent by gateway, check that it is
operative and reachable from the network connection used by the gateway. Check the gateway’s Ethernet interface
sending Pings to its IP address using a PC connected to the same Ethernet IP network. If the problem persists
communicating through the LAN of the building, contact the network administrator and make sure traffic on the port
used is allowed through all the LAN path.
Intesis Modbus Server –Mitsubishi Centralized Controller comes with DHCP functionality enabled by default.
Connection to KNX
Connect the KNX TP1 bus to connectors A3 (+) and A4 (-) of gateway’s PortA. Respect the polarity.
Connect to PC (Configuration tool)
This action allows the user to have access to configuration and monitoring of the device. Two methods to connect to
the PC can be used:
•Ethernet: Using the Ethernet port of the Intesis.
•USB cable: To connect the device to the PC, the USB cable supplied should be plugged to the USB Console
port.

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
11 / 32
4 Set-up process and troubleshooting
Pre-requisites
It is necessary to have a KNX installation, device or interface operative and well connected to the corresponding KNX
port of Intesis. It is also required to have a Mitsubishi Centralized Controller with Ethernet connected to the gateway.
Connectors, connection cables, PC for the Configuration Tool and other auxiliary material, if needed, are not supplied
by Intesis for this standard integration.
Items supplied with this product for this integration are:
•Intesis gateway.
•Link to download the configuration tool.
•USB Console cable to communicate with Intesis.
•Product documentation.
Intesis MAPS. Configuration & monitoring tool for Intesis
4.2.1 Introduction
Intesis MAPS is a WindowsTM compatible software developed specifically to monitor and configure Intesis new
generation gateways.
The installation procedure and main functions for KNX series devices are explained in the Intesis MAPS KNX User
Manual. This document can be downloaded from the link indicated in the installation sheet supplied with the Intesis
device or in the product website at www.intesis.com
In this section, only the specific case of Mitsubishi Electric’s Centralized Controller to KNX will be covered.
Please check the Intesis MAPS user manual for specific information about the different parameters and how to
configure them.
4.2.2 Connection
To configure the Intesis connection parameters press on the Connection button in the menu bar.
Figure 4.1 MAPS connection

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
12 / 32
4.2.3 Configuration tab
Select the Configuration tab to configure thegateway parameters. Three subsets of information are shown in this
window: General (Gateway general parameters), KNX (KNX interface configuration) and Mitsubishi Electric
(Centralized Controller/s interface parameters).
Figure 4.2 Intesis MAPS configuration tab
General tab is explained in Intesis MAPS user manual for Intesis Modbus Server Series.
4.2.3.1 KNX Configuration
Set parameters of KNX interface of Intesis.
Figure 4.3 Intesis MAPS KNX configuration tab
1. Device configuration
1.1.Physical Address. KNX physical address of the device in the network
1.2.Extended Addresses. Enables usage of KNX Extended addresses (rangefrom 16/0/0 to 32/7/255).

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
13 / 32
2. Operating Mode. Settings related to KNX interface for control and feedback of Mitsubishi unit’s operating
mode.
2.1. KNX DPT for HVAC operation mode comm object. Base DPT. Base DPT to use for control/monitor
the operating mode. Following DPT types are offered:
oDPT_20.105. DPT_HVACContrMode: 0-Auto, 1-Heat, 3-Cool, 9-Fan, 14-Dry
oDPT_5.x (non-standarized): 0-Auto, 1-Heat, 2-Dry, 3-Fan, 4-Cool, 5-Setback (if enabled)
2.2. KNX DPT for HVAC operation mode comm object. Extra DPT. Additional DPT to use for
control/monitor the operating mode.
oDPT_1.100. DPT_Heat/Cool: 0-Cool, 1-Heat.
oDPT_5.001. DPT_Scaling: Enables objects “Control_ Heat Mode & On” and “Control_ Cool Mode &
On” at IC/FU unit types. Their type is DPT_Scaling (0..100%), and their ending is to be able to control
parameters On/Off, Cool/Heat indoor unit from a single percentage object. They are meant to provide
compatibility with certain thermostats oriented to the operation of valves for Heating/Cooling.
Whenever a value > 0% is received at each of these two objects, the corresponding operating mode
and ON operation is sent to the indoor unit. Whenever both values are 0%, indoor unit is set to OFF
2.3. Setback mode. Enables objects for control/monitoring of Setback mode (applicable to IC/FU units).
2.4. Use of 1-bit Operating Modes. 1-bit Control Objects. Enables a bit-type object for the control of each
operating mode.
2.5. Use of 1-bit Operating Modes. 1-bit Status Objects. Enables a bit-type object for monitoring each
operating mode.
3. Temperature Sensor.
3.1. Ambient temperature provided from KNX. Enables object Control_ KNX ambient temperature.
4. Fan Speed. Settings related to KNX interface for control and feedback of Mitsubishi unit’s fan speed.
4.1. Auto Fan Speed. Configures availability of Auto Fan Speed control/monitoring objects. Necessary if
your indoor unit has auto fan speed.
NOTE: Mitsubishi Centralized Controller does not accept, by itself, that an ambient temperature for
control of operation of the indoor unit is provided. To allow regulation of indoor unit according to a
temperature reference from KNX, what Intesis does is passing a different temperature setpoint to
the indoor unit than the one required by the user. The passed setpoint is such that the difference
‘Ambient temperature reported by MNET – AC setpoint’ is equal to ‘Ambient temperature reported
by KNX –AC setpoint required by KNX’, using the following formula:
“AC Setp. Temp” = “AC Ret. Temp” - (“KNX Amb. Temp.” - “KNX Setp. Temp”)
Where:
▪AC Setp. Temp: AC indoor unit setpoint temperature
▪AC Ret. Temp: AC indoor unit return temperature
▪KNX Amb. Temp.: Ambient temperature provided from KNX
▪KNX Setp. Temp: Setpoint temperature provided from KNX
Consequently, when using this feature (Ambient temp provided from KNX), setpoint at AC and
setpoint in KNX will not necessarily be the same (actually, user will not be able to operate setpoint
from Mitsubishi System controllers - Centralized Controller screen or remote controller).
!

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
14 / 32
4.2. KNX DPT for Fan Speed comm objects. DPT_5.001, DPT_Scaling. Control/monitoring of Fan Speed
is performed by means of scaling (percentage) objects. Thresholds for control object and values for status
object will vary according to number of fanspeeds of the unit (number of fanspeeds of each unit is configured
in Mitsubishi Electric configuration tab).
4.2. KNX DPT for Fan Speed comm objects. DPT_5.010, DPT_Value_1_Ucount. Control/monitoring of
Fan Speed is performed by means of enumerated values.
4.3. KNX DPT for Fan Speed comm objects. DPT_5.010, DPT_Value_1_Ucount. Control/monitoring of
Fan Speed is performed by means of enumerated values.
4.4. Use of 1-bit Fan Speed. 1-bit Control Objects. Enables a bit-type object for control of fan speed.
4.5. Use of 1-bit Fan Speed. 1-bit Status Objects. Enables a bit-type object for monitoring of each fan
speed.
5. Vane Position. Settings related to KNX interface for control and feedback of Mitsubishi unit’s vane position.
5.1. Auto & Swing Vanes. Configures availability of Auto Vanes and Swing vanes control/monitoring objects.
5.2. KNX DPT for Vane Position comm objects. DPT_5.001, DPT_Scaling. Control/monitoring of Vane
Position is performed by means of scaling (percentage) objects.
5.3. KNX DPT for Vane Position comm objects. DPT_5.010, DPT_Value_1_Ucount. Control/monitoring
of Fan Speed is performed by means of enumerated values.
5.4. Use of 1-bit Vane Position. 1-bit Control Objects. Enables a bit-type object for controlof vane position.
5.5. Use of 1-bit Vane Position. 1-bit Status Objects. Enables a bit-type object for monitoring of each vane
position.

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
15 / 32
4.2.3.2 Mitsubishi Electric Configuration
Set parameters for connection with Mitsubishi Electric’s Centralized Controller.
Figure 4.4 Intesis MAPS Mitsubishi Electric configuration tab
Up to two Centralized Controller’s can be configured (depending on the Intesis version). Each Centralized controller
must be configured with the following parameters:
1. IP: IP Address of the Centralized Controller.
2. Description: Text description for the Centralized Controller
3. Controller type: Select if Centralized Controller has direct connection, or it is an Expansion Controller.
Possible values are:
▪Controller Direct Connection
▪Expansion Controller 1
▪Expansion Controller 2
▪Expansion Controller 3
4. Centralized Controller Model: Select the Centralized Controled model. Possible values are:
▪AG-150A, GB-50ADA or older
▪EB-50GU
▪AE-200, EW-50 or newer
5. Old Model Compatibility: Set up if EB-50GU or AE-200 (or newer) Centralized Controller has been setup
in ‘Old Compatibility’ mode.
For each Centralized Controller, it must also be selected the groups that will be monitored/controlled using Intesis.
You can do it manually in ‘Controllers Configuration’ section, by unfolding the corresponding ‘Centralized Controller’
in the list of controllers.
You can also scan for available groups under the IP of the Centralized Controller:

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
16 / 32
Figure 4.5 Selection of active groups in Centralized Controller
By pressing the ‘Scan’ button, ‘Discover Controller Groups’ window will appear:
Figure 4.6 Discover control groups window
By pressing ‘Scan’ button, configured Centralized Controller will be scanned for available control groups. Error
window will appear if there is a problem in the connection with the Centralized Controller (Ethernet cable not
connected, wrong IP address for Centralized Controller, PC Monitoring license in Centralized Controller is not active,
…).
A progress bar will appear during the scan, which will take a few seconds (up to 1 or 2 minutes). After scan is
completed, detected groups will be shown in the ‘Available Groups’ area, as follows:

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
17 / 32
Figure 4.7 Scan results window
From available groups, mark the checkbox under column ‘Add’ to select these groups as active and configured in the
Centralized Controller.
By pressing the ‘Save’ button, information will be passed to previous ‘Controllers Configuration’ window in MAPS.
‘Discover Control Groups’ also allows to Export Controller Configuration (see corresponding button in Figure 4.7),
which will generate a text file with the active groups in the controller, for documentation and support purposes.
Once the list of active groups is filled, parameters for each group must be configured. For doing so, select each group
in the list:
Figure 4.8 Scan results window
Parameters that must be configured for each group are the following:
1. Description: Text description for the control Group

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
18 / 32
2. Unit Type: Possible values are:
Number
Model
Description
Availability: SCAN only or both
(manual selection + SCAN)
0
IC
Air conditioning indoor unit (VRF, M-
series, P-series and K-control unit)
Both
1
KIC
Indoor unit (K-control unit)
SCAN only
2
AIC
Indoor unit (P-Series)
SCAN only
3
LC
Lossnay
Both
4
FU
Outdoor-Air Processing unit
Both
5
BU
Air to Water Booster unit
Both
6
WH
Air to Water HEX unit
Both
7
CEh
Heat Pump
Both
8
DC
DiDo controller
SCAN only
9
AHC
ALL HVAC CONTROOLER
SCAN only
10
RC
ME remote controller (old type) /
Simple Remote Controller(old type)
SCAN only
11
ME
ME remote controller (new type)
SCAN only
12
RC
Simple Remote Controller (new type)
SCAN only
13
URC
New Remote Controller
SCAN only
14
EGW
EB-50
SCAN only
15
TR
AG-150,GB-50,G-5
SCAN only
16
AN
OnOff remote controller
SCAN only
17
GR
Group rermote controller
SCAN only
18
SR
System remote controller
SCAN only
19
ST
Schedule remote controller
SCAN only
20
SC
other controller
SCAN only
21
-
SCAN only
22
NONE
SCAN only
3. Setpoint type: Select if unit supports different setpoints according to operation mode, or it supports single
setpoint.
4. URC Controller: Select if unit has URC controller
Please note that the scan is taking the configiguration of “Unit Type”, “Num of Fan Speeds” and “URC Controller”
automatically so you might not need to modify these parameters after performing a scan.
Finally, in addition to Centralized Controller parameters, and parameters for each corresponding group, there is a set
of advanced global parameters defining the communication of the Intesis with the centralized controller. These are
following:

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
19 / 32
Figure 4.9 Advanced Parameters for communication with Centralized Controllers
For them, the default values should be correct for most installations. They might need adjusting in particular cases
where there are particular requirements in the communication. Their function is following:
1. Polling Period: Time in milliseconds between each request sent to the Centralized Controller
2. Answer Timeout: Time in seconds that Intesis will wait for a response from Centralized Controller after
sending a single request for information through TCP/IP.
3. Controller Connection Timeout: After Intesis starts TCP/IP socket connection, time that the Intesis will wait
for the Centralized Controller to accept the socket request. For each individual request, Intesis starts a new
socket connection.

IntesisTM KNX –Mitsubishi Electric CC User Manual r1.1 EN
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
20 / 32
4.2.4 Signals
All available registers, its corresponding description and other main parmaters are listed in the signals tab.
Figure 4.10 Intesis MAPS Signals tab
4.2.5 Sending the configuration to Intesis
When the configuration is finished, follow steps to program the gateway.
1.- Click on Save button to save the project to the project folder on your hard disk (more information in Intesis
MAPS User Manual).
2.- You will be prompted to generate the configuration file to be sent to the gateway.
a.- If Yes is selected, the file containing the configuration for the gateway will be generated and saved
also into the project folder.
b.- If NO is selected, remember that the binary file with the project needs to be generated before the
Intesis starts to work as expected.
3.- Press the Send button to send the binary file to the Intesis device. The process of file transmission can
be monitored in the Intesis Communication Console window. Intesis will reboot automatically once the new
configuration is loaded.
Figure 4.11 Intesis MAPS Receive/Send tab
After any configuration change, do not forget to send the configuration file to the Intesis using the
button “Send”.