Professional Documents
Culture Documents
Operation manual
GEA MATRIX® .LON
All-in-one solution
Product range GEA MATRIX®.LON
Group 16
Group 4
Group 1
Group 2
Group 2
Table of contents
1 Unit overview and scope of delivery................................... 5
1.1 Scope of delivery ............................................................................. 6
1.2 Using GEA MATRIX®.LON ............................................................... 6
4 MATRIX.Net network........................................................... 13
4.1 Group structure............................................................................... 13
4.2 MATRIX.Net network structure ...................................................... 17
4.3 Topologies of the MATRIX.Net network ........................................ 18
4.4 MATRIX.Net network setup ........................................................... 20
6 Commissioning ................................................................... 26
6.1 Factory presettings ......................................................................... 26
6.2 Setting bus terminations ................................................................. 26
6.3 Testing of operation ........................................................................ 26
for MATRIX.Net
Bus termination
24 V DC
Service socket
Ground
Switch for
LON® bus
GEA MATRIX®.LON
Fig. 1-1: Overview of units 3: Power supply
1: L ON®
connection 4: LED display – MATRIX.Net status
2: MATRIX.Net connection 5: LED display – LON® status
6: LON® service pushbutton
This manual must always be available at the place where the MATRIX.LON is in
use. Each person who uses or works on the MATRIX.LON must have read this
manual and and apply it in practice.
NOTE!
You will find additional information on the use of theMATRIX.LON here.
RECYCLING!
This symbol refers to the appropriate recycling of packaging materials and
expired components (separated according to potentially recyclable materials).
PERSONAL INJURY!
Here you will find special information as well as do's and don'ts regarding
prevention of injury to persons.
PERSONAL INJURY!
The MATRIX.LON must not be operated in the following environments:
– in locations where there is a risk of explosion
– in rooms containing conductive dusts
– in rooms where strong electromagnetic fields are present or
– in rooms with aggressive atmospheres (that attack plastics, for example).
3 Technical description
Group 1 Group 3
G3 G2
G4 G1
G2 G4
G1 G3 G16
G1 G4
G2 G3 G16
G1 G4
G2 G3 G16
Fig. 3-2: Example showing the integration of several MATRIX.Net devices via GEA
MATRIX®.LON modules in the LON® network
Ambient atmosphere
Allowed ambient temperature 0 °C to 45 °C
Allowed storage temperature -25 °C to 65 °C
Allowed relative humidity 15 % to 75 %, non-condensing
Electromagnetic compatibility
Electromagnetic interference (EMI) according to DIN EN 55022 / DIN EN 61000
Electromagnetic susceptibility according to DIN EN 50082 / DIN EN 61000
(EMS)
Mechanical data
External dimensions (W/H/D) approx. 106 x 90 x 58 mm
Attachment on mounting rails according to DIN EN 50022 (TS 35 x 7.5)
Weight 175 g
Casing material N185 Norly UL 94 V-0
Casing colour RAL 7035 (grey)
Protection class (according to DIN
IP 20
40050)
Position when in use the front face must not point downwards, otherwise any position may be used
Electrical data
Supply voltage 24 V DC (min. 18 V DC, max. 32 V DC)
Current/power consumption typically 45 mA / 1 VA
LON® interface Transceiver type FTT10A / FT-X1 (compatible with LPT-10)
4 MATRIX.Net network
This chapter contains information about the MATRIX.Net and how to set up the
network correctly.
The MATRIX.Net is a network that connects various components of the GEA
control system (network users) via a data bus.
All information required for control and regulation is exchanged between users
using this network.
Network users can consist of the following:
– Controllers
– Operator panels
– Global modules/central timer
– WEB interface
– Service tools
Network Group
The group address is assigned via the group address switch on the operator
panel – refer to the “Commissioning and test” chapter in the operation manual for
“GEA MATRIX® operator panels”.
The group address switch is used to assign MATRIX.V modules and software is
used to assign MATRIX.LON modules to this group – also refer to the chapter
“Commissioning” in this operation manual and in the operation manual for GEA
MATRIX® global modules. The MATRIX.Net network is connected at the operator
panel.
4.1.2 Group structure of the MATRIX 3000 system in combination with the MATRIX 2000 system
A group may be formed using the MATRIX 2000 and MATRIX 3000 systems. Fig.
4-2 shows an example of a network consisting of an operator panel,
MATRIX 2000 system, MATRIX 3000 system and various global modules.
Network Group
Fig. 4-2: Group structure with a combination of MATRIX 2000 and MATRIX 3000 controller types
4.1.3 Group structure with MATRIX 3000 and/or MATRIX 4000 system
A group may be formed using the MATRIX 3000 and MATRIX 4000 systems.
Fig. 4-3 shows an example of a network consisting of an operator panel,
MATRIX 3000 system, MATRIX 4000 system and various global modules.
Group Network
Fig. 4-3: Group structure with a combination of MATRIX 3000 and MATRIX 4000 controller types
NOTE!
The combination of units with MATRIX 3000 and units with MATRIX 2000
systems is permitted in this group set-up – See “Group structure of the MATRIX
3000 system in combination with the MATRIX 2000 system” on page 15. The
combination of units with MATRIX 4000 and units with MATRIX 2000 systems
is not possible.
Group 3 Group 1
Group 1 Group 2
NOTE!
The data transfer cable must be routed in such a way that only one side of the
respective cable shielding is applied (as shown in Fig. 4-5) – See “Shielding/
earthing” on page 20.
1 2 3 X The illustration shows a MATRIX.Net set-up with linear structure and stub line. An
operator panel connected via a stub line with several groups is shown as an
example. The maximum permissible stub line length is 25m.
4-core 2-core
2-core
Fig. 4-6: MATRIX.Net set-up with linear structure and stub line
* As it is not permissible to connect three cores, a joining terminal must be used! The intermediate terminals (STV)
mounted on the printed circuit board (if not already assigned) or terminals by others can be used for this.
NOTE!
The data transfer cable must be routed in such a way that only one side of the
respective cable shielding is applied (as shown in Fig. 4-6) – See “Shielding/
earthing” on page 20.
RECOMMENDATION
We recommend the following data transfer cables:
Manufacturer: HELUKABEL
Type: CAN-BUS flexible 2 x 2 x ... mm²
NOTE
Repeaters must be used in the network if there are more than 110 users. To
increase the length of the cable special bridges are required that decouple
telegram transfer times between the network segments.
The cross-section of the bus cable may need to be modified depending on the
cable length of the MATRIX.Net!
4.4.3 Shielding/earthing
• Mount the data transfer cable (MATRIX.Net) on one side in the GEA climate
control and air treatment units using shielding clips to ensure the best pos sible
electrical contact.
• Connect the shielding with the shielding clip to a large earth surface area!
• Both sides of the shielding should be applied in systems with a large network
scope, or if high levels of EMC interference are likely. Before doing so, it must
be ensured that no potential differentials occur.
Arrangement of the The positioning of components in the switch cabinet influences to a large extent
components the trouble-free functioning of the module.
During planning and implementation steps must be taken to ensure that power
and control components are arranged separately. Examples of power
components are:
– Contactor
– Coupler components
– Transformers
– Frequency inverters
– Converters
– DC power supply units.
In order to effectively prevent electromagnetic interference the switch cabinet
should be divided into areas with varying levels of power and interference.
Cable routing Always route power cables (cables carrying high currents – to converters,
and wiring contactors and solenoid valves for example) and control and signal cables (e.g.
cables to digital inputs) as far as possible from each other. This avoids capacitive
and inductive interference.
If cables cannot be routed separately the first priority must be to shield the cables
that cause interference.
To prevent interference:
• Avoid laying parallel sections of cables with different power ratings.
• As a basic rule, separate AC voltage cables from DC voltage cables.
• Comply with the minimum distances:
Between power cables/supply cables
... and signal cables: at least 10 cm
... and data/analogue cables: at least 30 cm
• The feed and return cables of an electric circuit should be laid side by side.
The sum of the currents is immediately reduced to zero due to the opposing
flow of current. The resulting fields are compensated.
In order to ensure that the module works properly you should always carry
7
out the 7 steps (marked) consecutively.
5.2 Installation/removal 1
The MATRIX.LON module has a casing (IP20) that is suitable for installation
in switch cabinets on a DIN mounting rail (35 mm mounting rails as per
DIN EN 50 022).
The MATRIX.LON module must not be installed with its front face pointing
downwards! All other installation positions are permitted. If the module is installed
vertically on a mounting rail it must be secured using an end bracket to prevent it
from slipping.
Fig. 5-1
5.3 Installation
DANGER FROM ELECTRICAL CURRENT!
The connection must only be carried out by qualified electricians in
accordance with this operation manual and applicable regulations (in Germany,
VDE = Association of Electrical Engineers):
In the interests of your safety disconnect all supply cables from the power
supply and take steps to ensure that it cannot be unintentionally switched back
on, ensure zero voltage; earth and short-circuit the unit and cover or isolate
adjacent live parts. Failure to comply with the above may result in severe injury
or death.
• Do not apply external voltages to the MATRIX.LON.
Number of
conductors Cross-section
Connection of... Type of terminal Type of conductor
per min. to max.
terminal
99 +24 V DC
When setting up the MATRIX.NET, only use data transfer cables that comply with
DIN 19245 T3 and EN 50170 with twisted pair cores and braided shielding.
RECOMMENDATION
We recommend the following data transfer cables:
Manufacturer: HELUKABEL
Type: CAN-BUS flexible 2 x 2 x ... mm²
98 High
For setting up the LON® network the following cable types by the manufacturer
Echelon® are recommended:
Wire Resistance Capacity
Cable types
Ø/AWG (R/km) (nF/km)
Belden 85102, single twisted pair, stranded 19/29,
A 1.3 mm/16 28 56
unshielded, 150 ºC
Belden 8471, single twisted pair, stranded 19/29,
B 1.3 mm/16 28 72
unshielded, 60 ºC
C Level IV 22 AWG, twisted pair, typically solid & unshielded 0.65 mm/22 106 49
D JY (St) 2x2x0.8 4 - wire helical twist, solid, shielded 0.8 mm/20.4 73 98
The following cable lengths can be achieved depending on the bus termination:
Topology double bus termination (linear topology) single bus termination
Cable type A B C D A B C D
Number of users (max.)
64
without additional repeaters
Transmission length (in m) 2700 2700 1400 900 500 500 500 500
Maximum distance between nodes (in m) x x x x 500 400 400 320
Isolation between network and
1000 VRMS
electronics 0 – 60 Hz (60 seconds)
NOTE!
The suitability of PC network (TIA Category 5) or ETB network cable types for
use with LON® networks is limited. If these cable types are used this reduces
the maximum cable length.
91 Bus core
NOTE!
The LON® network connections are
interchangeable.
6 Commissioning
NOTE!
Refer to “MATRIX.Net network” on page 13 for more information on this
subject.
NOTE!
If terminating resistors are required for the LON® network these must be
provided by others.
NOTE!
The states on the MATRIX.Net side can be visualised and evaluated using the
MATRIX.PC service software which also displays the variables configured on
the LON side.
The Service, Error and Run LEDs light up for 15 seconds whereby the red Error
LED is switched off every 1.5 s for 100 ms.
The LEDs display the current status again once the 15 s have elapsed.
Fig. 6-3
When the service button is pressed the MATRIX.LON sends a unique code
(Neuron® ID) to all nodes in the available network via the LON® bus. This means
that the MATRIX.LON can be identified in a LON® network.
Fig. 6-4
NOTE!
There is no risk associated with the operation of the service button – this does
not trigger a reset.
7 MATRIX.LON Plug-In
NOTE!
The MATRIX.LON plug-in will only work in conjunction with a LNSTM-based
network management tool.
A LNSTM object server will not be installed with the MATRIX.LON plug-in, which
means that this must be installed beforehand.
You should therefore only install the MATRIX.LON plug-in once you have
installed a suitable network management tool.
NOTE!
For a detailed description regarding the operation of the software, consult the
manual enclosed with the relevant network management tool.
Fig. 7-1
• Create a unit with the assistance of the network management tool and
“GEAMATRIX...” unit template.
NOTE!
Alternatively, the MATRIX.LON plug-in can be launched directly – see plug-in
help topics for further information.
Fig. 7-2
You will find detailed descriptions of the other menu items under “plug-in help
topics”.
8 Planning information
A maximum of 16 air treatment unit groups can be networked using one
MATRIX.LON module providing the requirements are straightforward.
For this 57 variables (29 inputs and 28 outputs) can be defined. 5 additional
variables, such as the time and external temperature, are permanently assigned
for administration purposes and apply equally for all groups.
A maximum of 16 MATRIX.LON modules can be used in a MATRIX.Net. Each
group may be assigned 1 MATRIX.LON module only.
NOTE!
All available network variables are listed in the following description with a short
description of their function.
For a detailed description of all variations refer to the “Plug-in help topics”.
nvi = Network Variable Input = Input variable; LON® network -> MATRIX.Net
nvo = Network Variable Output = Output variable; MATRIX.Net -> LON® network
All input variables are subject to a configurable connection monitoring. Once the
monitoring period has expired the input variable previously received is set to
invalid.
Minimum and maximum transfer times can be configured via the MATRIX.LON
plug-in for all input and output variables – see “7.5 MATRIX.LON plug-in – main
menu” on page 31.
The following profiles were used as the starting points when selecting the
variables:
NOTE!
Comprehensive status information on the MATRIX.Net units is already
contained in the nvoNetStates.
The configuration is carried out with the help of the plug-in through the
assignment of LON® NVs – such as the NVs for the Fan Coil Unit 8020 profile.
Example: above function block following respective assignment (and
resynchronise command) of 2 variables in group (sub-network) 0 of the
MATRIX.Net (…_s0).
NVi per NVo per Temp object Temp object Max. number per Required number of
sub-network sub-network NVi NVo MATRIX.LON group MATRIX.LON with 16 groups
1 1 yes yes 16 1
2 2 yes no 14 2
2 2 yes yes 13 2
3 3 yes yes 9 2
4 3 yes yes 7 3
4 4 yes no 7 3
4 4 yes yes 6 3
5 5 yes yes 5 4
...
At the layout stage it must also be considered that one network variable can also
contain several data points (see “9.2.16 nvoUnitStatus” on page 50).
8.6 Priorities
As a basic rule, the set points specified via the LON® system (building
management system) have overriding priority when compared to the set points in
the MATRIX.Net or local set points.
Local actual values on the other hand have priority over actual values supplied by
the LON® system (building management system).
The following exceptions to this should however be observed:
– The bypass function of the local operator panel overwrites the Unoccupied
command from the building management system for a specific period of time
“X” which has a default value of 120 minutes and can be configured using the
GEA MATRIX® system service tools.
– The “rapid ventilation” function of the operator panel overwrites conflicting
specifications from the building management system.
9 LON® interface
In Chapters 9.1 and 9.2 which follow the NVs (network variables) for the FCU(LT),
FCU(FB) and Temperature objects are described. A number of variables exist in
the form up to LT and up to FB.
NOTE!
For additional information refer to the plug-in help topics.
9.1.1 nviAirMixCmd
This network variable can be used to adjust the fresh air rate from the LON side.
9.1.2 nviApplicMode
This network variable can be used to specify the controller operating mode from
the LON side.
9.1.3 nviEnergyHoldOff
This network variable can be used to switch off the units from the LON side
without deactivating the frost protection. This variable is defined by two values:
“State” (status) and “Value”.
9.1.4 nviExAirFlowCmd
This refers to the return air flow set point.
9.1.5 nviExAirPressCmd
This refers to the set point for the return air duct pressure.
9.1.6 nviFanSpeedCmd
This network variable can be used to specify the set point for the fan speed by the
LON. This variable is defined by two values: “State” (status) and “Value”.
The calculated percentage value must be rounded off before addition (+0.5).
n = maximum number of fan speeds
m = fan speed to be calculated (min = 0 to max = n)
With infinitely variable motors the speed is specified directly as a percentage of
the maximum speed.
9.1.7 nviMediaTemp
This refers to the medium or inlet temperature – for heating/cooling changeover
with 2-pipe systems, for example.
9.1.8 nviOccCmd
This network variable can be used to define the occupancy status of the room
(e.g. occupied or unoccupied).
9.1.9 nviOutdoorRH
This network variable can be used to transfer the relative humidity of the fresh air
by the LON.
9.1.10 nviOutdoorTemp
This network variable can be used to transfer the external temperature by the
LON. The external temperature is valid for the entire MATRIX.Net network.
9.1.11 nviRequest
This NV is used to request the object status/mode. The RQ_REPORT_MASK and
RQ_UPDATE_STATUS functions are supported.
9.1.12 nviSetPoint
This network variable can be used to specify an absolute room temperature set
point by the LON in combination with “nviSetPtOffset”.
The set point for the unit/unit group in this case is obtained from the basic set point
(nviSetPoint) plus/minus the relative set point (nviSetPtOffset).
9.1.13 nviSetPtOffset
This variable can be used to specify a relative room temperature set point (see
“nviSetPoint”).
9.1.14 nviSpaceCO2
This network variable can be used to transfer the CO2 concentration by the LON.
Value range: 0 to 65534 ppm CO2 concentration. The value 65535 ppm is
invalid.
9.1.15 nviSpaceRH
This network variable can be used to transfer the relative humidity of the room air
by the LON.
9.1.16 nviSpaceTemp
This network variable can be used to transfer the actual value for the room
temperature by the LON.
9.1.17 nviSupAirPressCmd
This network variable can be used to specify the set point for the supply air duct
pressure by the LON.
9.1.18 nviSupAirSetPoint
This network variable can be used to specify the set point for the supply air
temperature.
9.1.19 nviSupAirFlowCmd
This is the set point for the supply air flow – with programmed air flow control, for
example.
9.1.20 nviTimeSet
This network variable can be used to specify the time by the LON. The modules
in the MATRIX.Net are synchronised automatically.
9.2.1 nvoCoolOutput
This network variable is used to transfer the calculated position of the cooling
valve to the LON side. The calculated valve position does not provide a precise
indication of the actual power output of the unit.
With unit groups, the individual values of the cooling valves are sent to the
MATRIX.LON, then transferred as an average value to the LON side.
This value is transferred directly where a central valve is used. Where units with
DX-evaporators are used, the control variable for the refrigeration circuit is
transferred instead of the position of the valve on the upstream side.
9.2.2 nvoDevInputStates
This network variable can be used to transfer the states of the digital inputs at the
unit.
9.2.3 nvoDischAirTemp
This network variable can be used to transfer the current supply air temperature
of the group to the LON side. The lowest value within the group is transferred in
this case.
9.2.4 nvoEffectSetPt
This network variable can be used to transfer the effective temperature set point
of the group to the LON side. The set point is compensated for by the summer/
winter factor (for example).
9.2.5 nvoFailure
This network variable can be used to show the error status of individual units
within a group. The error log is 32 ASCII characters long and contains information
on the unit and the type of error. The latest error that has occured (+) or the latest
error that has disappeared (–) is displayed.
The error log consists of:
Number of
Information Explanation
characters
Serial number Serial number of controller/unit. The assignment can be replaced with a free
16
(location string) format text using the service tool.
Group string
5 Specifies the group (1 to 16) where the error originates.
(error group)
Character string with two basic items of information: "XX.YY“
Shows the group where the error originates,
Code string XX =
5 “02” = sensor group, for example.
(character string)
Shows the individual error in the error group,
YY =
“00” = exterior sensor has short circuited, for example.
+ Error occured
Error status
- Error disappeared
C M0 4 1 2 3 . 0 4 4 . 0 3 1 SN= 0 2 0 F. 0 1 + 0
XX. YY
The “XX” error groups in the code string (character string) are listed below
showing the group where the error originates, “02” = sensor group, for example.
The individual basic items of information “YY” in the code string (character string)
showing the individual error in the sub-group are listed below, “00” = exterior
sensor has short circuited, for example.
Sensors Explanation
02.00 Exterior sensor has short circuited.
02.01 Exterior sensor has failed.
02.02 Room temperature sensor has short circuited.
02.03 Room temperature sensor has failed.
02.04 Inlet temperature sensor has short circuited.
02.05 Inlet temperature sensor has failed.
02.06 Supply air temperature sensor has short circuited.
02.07 Supply air temperature sensor has failed.
02.08 Return air or external room temperature sensor has short circuited.
02.09 Return air or external room temperature sensor has failed.
02.10 Humidity sensor has failed.
02.11 Pressure sensor has failed.
02.12 CO2 sensor has failed.
02.13 Coil temperature sensor (frost protection sensor) has failed.
DX-evaporator Explanation
06.00 Inadmissible pressure in refrigeration circuit.
06.01 Compressor has been switched off.
9.2.6 nvoFanSpeed
This network variable can be used to transfer the actual value of the fan speed to
the LON side.
During this process the controllers send the individual fan values to the
MATRIX.LON which are then transferred as an average value to the LON side.
The variable is defined by two values: “State” (status) and “Value”.
9.2.7 nvoHeatOutput
This network variable is used to transfer the calculated position of the heating
valve to the LON side. The calculated valve position does not provide a precise
indication of the actual power output of the unit.
The individual values of the heating valves in a unit group are sent to the
MATRIX.LON then transferred as an average value to the LON side.
This value is transferred directly if a central heating valve is used.
The output is signaled for units with electrical heating and the average of both
outputs is signaled in the case of units with auxiliary electrical heating.
9.2.8 nvoNetStates
This network variable can be used to transfer information in the form of an
accumulative error message from the group to the LON side. The following
messages are currently used:
Bit Explanation
0 The first MATRIX network digital input module (switch position A) is signaling an error.
1 The second MATRIX network digital input module (switch position B) is signaling an error.
2 The first MATRIX network digital output module (switch position A) is signaling an error.
3 The second MATRIX network digital output module (switch position B) is signaling an error.
4 The first MATRIX network digital input module (switch position A) is signaling an error.
5 The second MATRIX network digital output module (switch position B) is signaling an error.
6 The MATRIX network timer module is signaling an error.
7 The MATRIX network return air management is signaling an error.
8 One of the following modules is in service mode: digital input module 1+2, digital output module 1+2, analogue input
module 1+2, timer module or return air management.
9 The return air management is signaling a problem: the air flows of the return air and supply air fans can no longer
be equalised.
10 A conflict of addresses exists in two identical modules (MATRIX.DI digital input module, MATRIX.DO digital input
module or MATRIX.AI analogue input module) as the switch positions are the same. Make sure that
one module is set to switch position A and the other is set to switch position B.
11 One of the sensors of the first analogue input module has failed.
12 One of the sensors of the second analogue input module has failed.
One of the following modules has failed and bus communication with this module has been interrupted: digital input
13
module 1+2, digital input module 1+2, analogue input module 1+2, timer module or return air management.
14 Error in module itself
16 A controller in group 0 is signaling an error.
17 A global module or operator panel in group 0 is signaling an error.
19 A controller in group 1 is signaling an error.
20 A global module or operator panel in group 1 is signaling an error.
22 A controller in group 2 is signaling an error.
23 A global module or operator panel in group 2 is signaling an error.
25 A controller in group 3 is signaling an error.
26 A global module or operator panel in group 3 is signaling an error.
28 A controller in group 4 is signaling an error.
29 A global module or operator panel in group 4 is signaling an error.
31 A controller in group 5 is signaling an error.
32 A global module or operator panel in group 5 is signaling an error.
34 A controller in group 6 is signaling an error.
35 A global module or operator panel in group 6 is signaling an error.
37 A controller in group 7 is signaling an error.
38 A global module or operator panel in group 7 is signaling an error.
Bit Explanation
40 A controller in group 8 is signaling an error.
41 A global module or operator panel in group 8 is signaling an error.
43 A controller in group 9 is signaling an error.
44 A global module or operator panel in group 9 is signaling an error.
46 A controller in group 10 is signaling an error.
47 A global module or operator panel in group 10 is signaling an error.
49 A controller in group 11 is signaling an error.
50 A global module or operator panel in group 11 is signaling an error.
52 A controller in group 12 is signaling an error.
53 A global module or operator panel in group 12 is signaling an error.
55 A controller in group 13 is signaling an error.
56 A global module or operator panel in group 13 is signaling an error.
58 A controller in group 14 is signaling an error.
59 A global module or operator panel in group 14 is signaling an error.
61 A controller in group 15 is signaling an error.
62 A global module or operator panel in group 15 is signaling an error.
9.2.9 nvoOADamper
This network variable is used to transfer the position of the mixing air dampers.
Value range: 0 % (= recirculation air) to 100 % (= 100 % fresh air),
average of all units in the group.
9.2.10 nvoOutdoorTemp
This network variable can be used to transfer the ambient temperature to the LON
side. The ambient temperature is a variable that is common to all groups in a
MATRIX.Net.
9.2.11 nvoSpaceCO2
This network variable can be used to transfer the actual value of the CO2
concentration to the LON side.
Value range: According to SNVT definition. The value 65535 ppm is invalid.
9.2.12 nvoSpaceRH
This network variable can be used to transfer the actual value of the relative room
air humidity to the LON side.
9.2.13 nvoSpaceTemp
This network variable can be used to transfer the actual value of the room
temperature to the LON side.
9.2.14 nvoStatus
This network variable is used to output the object status/mode. The
RQ_REPORT_MASK and RQ_UPDATE_STATUS functions are supported.
9.2.15 nvoSubnetStates
This network variable can be used to transfer up to 64 error or status messages
from the group (sub-network) to the LON side. The following 18 messages are
currently used:
Bit Explanation
0 Controllers of all units are switched off when the frost protection function is active
1 At least 1 unit is switched off without frost protection.
2 Thermal contact/motor protection for at least one unit has been triggered.
3 The frost protection monitoring for at least one unit has been triggered.
4 The freely-configurable operating mode has been activated.
5 At least one controller in the group is in service mode.
6 The operator panel, valve module or DX-evaporator module is in service mode.
7 A controller in the group is signaling that the exterior sensor has failed.
8 A room temperature sensor for a controller in the group has failed.
9 An inlet temperature sensor of a controller in the group has failed.
10 A supply air temperature sensor of a controller in the group has failed.
11 The inlet temperature sensor of the valve module in the group has failed.
12 A room temperature sensor for the operator panel in the group has failed.
13 At least one module in the group has failed.
14 The safety chain for the DX-evaporator module in the group has been triggered.
15 The compressor has been switched off and disabled by the DX-evaporator module in the group.
16 At least one controller in the group is signaling that an error has developed in the electrical heating.
17 At least one controller in the group is signaling that an error has developed in the condensate pump.
18-63 Reserved, not assigned.
9.2.16 nvoUnitStatus
This variable is structured using several individual items of information from a
group and contains the following data:
Variable Explanation State
mode: Average value of heating/cooling requirements for all units in the NC=NH=HVAC_OFF
room. The following applies where NC is the number of units that NC>NH=HVAC_COOL
must fulfil a cooling requirement and NH is the number of units that NC<NH=HVAC_HEAT
must fulfil a heating requirement:
heat_output_primary: same as nvoHeatOutput
heat_output_secondary: always 07FFF (invalid)
cool_output_primary: same as nvoCoolOutput
cool_output_secondary: Setting of the energy recovery system
(average value of all units in the group)
fan_output: same as nvoFanSpeed
in_alarm: Common error for the individual sub-network (= room) and multi- no unit is signaling error:
room modules (= global MATRIX modules such as digital or in_alarm = 0
analogue input modules).
≥ 1 unit is signaling error:
in_alarm ≠ 0
Alarms deactivated:
in_alarm = 255.
The values for the nvoSetting and nvoScene object types must be assigned
<FOS_MnuItemStr>
according to what is expected by the corresponding actuators for this menu
<FOS_String_01> function by the LON. The content of the message container is sent directly to the
<FOS_String_02> MATRIX OP50 / OP51 via the gateway on the LON side when the menu function
<FOS_String_03>
is called up.
<FOS_String_04>
The following functions can be implemented, depending on the object type stored
in the message containers:
– Send a Type SNVT_Scene message
– Send a Type SNVT_Setting message
– Send a Type SNVT_Switch message
The SNVT_Scene and SNVT_Setting types are sent immediately when the SET
button is pressed. An additional dialogue opens with the SNVT_Switch type
where users can modify the value then send it by pressing the SET button again.
The “nvoSwitch”, “nvoSetting” and “nvoScene” variables can be freely defined.
This is described further in the plug-in help topics.
9.4.2 nvoSwitch
The switch dialogue provides users with additional options for settings. The
FOS Switch Dialogue
settings are mapped as follows on the SNVT_Switch variable:
Off
On Settings Value State
Value [75 %]
OFF 0 0
Automatic
ON 100 1
AUTO 0 0xFF
0 to 100 % 1
NOTE:
When defining the variables please remember that the unit to be controlled
must have the corresponding equipment.
The “nvoSwitch” network variable can be used to carry out simple lighting control
operations for example by assigning values to 2 bytes.
9.4.3 nvoSetting
The “nvoSetting” network variable can be used to carry out damper control
operations for example by assigning values to 4 bytes.
9.4.4 nvoScene
The “nvoScene” network variable is used to send information from the OP5x to
Lon actuators via the MATRIX.LON by assigning values to 2 bytes. This
information is converted into corresponding functions (e. g. lighting scenes).
10 Elimination of malfunctions
The table below shows typical LED profiles that indicate possible malfunctions in
the MATRIX.LON, its status and actions that can be taken to eliminate the
malfunction. (For further information, also see “States of status LEDs” on
page 27.)
The symbols shown in the table indicate the following:
1 – LED does not go on
2 – LED flashes
3 – LED goes on
1 2 3
11 Disposal