7.4 LED error codes
KnX
error
CodeS
The table below shows error codes for the KNX bus and describes possible solutions. A common cause of a problem though may be due
to faulty wiring.
Error code
Description
Probable cause
Solutions
1
Get ETS® configuration
The KNX gateway module has not yet
received configuration from the ETS® tool.
Ensure the KNX gateway module is installed correctly and
that it has been programmed by the ETS® tool.
If the error persists, perform a hard reset on the KNX gateway
module.
See section 7.3 Resetting the KNX gateway module
for more information
2
Invalid ETS® flag
An invalid manual configuration flag has
been set on KNX group objects in ETS®.
Ensure all manual configuration flags on KNX group objects
in ETS® are correct.
Example: Activated data points which are only readable from
KNX must have READ or TRANSMIT flags set.
If many changes had been done in ETS® before the
error occured, Uponor recommends to remove all
COMMUNICATION flags from multiple group objects at once.
Then to add them one by one until the error occurs again.
See section 6 System setup for more information.
3
Incorrect ETS® actuator
configuration
A parameter setting in the ETS® for
actuator control is incorrect.
When using KNX thermostats
Ensure that all controller parameter settings, which are set
to “Use with actuator X” (where X is the controller channel
number), is referring to an actuator parameter set to
“Activated, KNX thermostat”.
When using Uponor thermostats
Ensure that all controller parameter settings, which are set
to “Use with actuator X” (where X is the controller channel
number), is referring to an actuator parameter set to
“Activated, Uponor thermostat”.
However, if several actuators are controlled by the same
Uponor thermostat, only the actuator parameter with the
lowest index number is required to be set to “Activated,
Uponor thermostat” and still maintain functionality. All
other acutator zone settings (registering a thermostat to an
acutator channel) are done at the controller in question.
4
Occupied thermostat
channel
A KNX thermostat is registered on the
same channel as an Uponor thermostat.
1. Ensure that an Uponor thermostat is not registered to a
channel used by a KNX thermostat.
2. Unregister the Uponor thermostat from the controllers or
reprogram the KNX thermostat to an unused channel in
the ETS® tool.
3. If the error persists, perform a hard reset on the KNX
gateway module.
See section 7.3 Resetting the KNX
gateway module for more information.
5
Slave channel not
available
A KNX thermostat is registered to a
channel on an unavailable slave module.
Ensure that the controller has a slave module installed (the
controller only have 6 channels by default).
If a slave module isn’t available, allocate the KNX thermostat
to another channel in the ETS®.
6
KNX Thermostat lost
A KNX thermostat has timed out. The KNX
gateway module hasn’t received data from
a KNX thermostat for at least 6 hours.
1. Ensure that the KNX thermostats are connected to the
KNX bus.
2. Ensure that the parameter settings for the KNX
thermostats in the ETS® are correct.
3. Ensure that the thermostats, if possible, are set to
send room temperature cyclically. Otherwise decrease
the temperature difference parameter which is allowed
before sending a new value via the KNX bus.
UK
CZ
DE
DK
EE
ES
FI
FR
HR
HU
IT
LT
LV
NL
NO
PL
PT
RO
RU
SE
SK
2 0
U P O N O R S M AT R I X B A S E / B A S E P R O · I N S TA L L AT I O N A N D O P E R AT I O N M A N UA L
