Nr2 Lon Handbook

LON Handbook
ook
For commercial and industrial heating systems
Vitotronic 050, Model HK1M

Vitotronic 050, Model HK1W
Vitotronic 050, Model HK1S
Vitotronic 100, Model GC1
Vitotronic 200, Model GW1
Vitotronic 333, Model MW1
Vitotronic 333, Model MW1S
For wall-mounted and gas-fired

fired boilers
Vitotronic 200, Model HO1

1
General Information
Safety Information
¨
Please ensure that these instructions are read and understood before commencing
installation. Failure to comply with the instructions listed below can cause product/
property damage, severe personal injury and/or loss of life.
Licensed professional Power supply Service

heating contractor Install power supply in Service on safety-related
The installation, adjustment, accordance with the regula- parts is not permissible.
service, and maintenance of tions of the authorities
this equipment must be having jurisdiction or, in Initial Start-up
performed by a licensed absence of such require- Initial start-up must be
professional heating con- ments, in accordance with performed by a licensed
tractor. National Codes. Viessmann professional heating con-
recommends the installation tractor; all test results must
Working on the equipment of a disconnect switch to the be recorded appropriately.
The installation, adjustment, 120 V power supply outside
service, and maintenance of of the boiler room. The Informing the System
this product must be done installer must provide max- Operator
by a licensed professional imum 15 A overcurrent The licensed professional
heating contractor who is protection for the 120 V heating contractor must
qualified and experienced in power supply (fuse or circuit ensure the system operator
the installation, service, and breaker). has been supplied with the
maintenance of hot water applicable Operating In-
boilers. There are no user Ensure main power supply structions and must intro-
serviceable parts on the to equipment, the heating duce the system operator to
boiler, burner, or control. system and all external the operation of this equip-
controls has been deacti- ment.
vated. Close main oil or
gas supply valve. Take Safety Information
precautions in all instances Please refer to
to avoid accidental activa- subsection
tion of power during service “Physical Net-
work. work Structuring” for safety
information regarding exter-
Field-supplied electrical nal equipment connected to
equipment must be type- the control.
tested.
When opening the control

unit is required, no static
discharge must take place
via internal electrical parts.
As outlined in trademark legislation, the use of trademarks, product names and other such names
mentioned in this handbook must not lead – even if not specifically marked – to the assumption that
these names are available for free usage.
Revision: 04/02/2009
2
Product Information/ Applicability Information
The information stated in this handbook applies to the following controls:



Vitotronic 333, Model MW1S
Vitotronic 200, Model H01
The part numbers are available from the current Viessmann price lists.
The above listed controls must be equipped with one of the following communication modules:
Communication module For use with:

LON module for heating circuits Vitotronic 050, Model HK1M (accessory)
and boiler controller Vitotronic 050, Model HK1W (accessory)
Vitotronic 050, Model HK1S (standard equipment)
Vitotronic 050, Model HK3W (accessory)
Vitotronic 100, Model GC1 (accessory)
Vitotronic 200, Model GW1 (accessory)
Vitotronic 200, Model H01 (accessory)
LON module for cascade control Vitotronic 333, Model MW1 (standard equipment)
Vitotronic 333, Model MW1S (standard equipment)
Vitotronic 333, Model MW2 (accessory)
3
Contents
General Information ................................................................................................. 2

Safety Information .......................................................................................... 2
Product Information/ Applicability Information ............................................... 3
Contents .................................................................................................................... 4
LON Technology....................................................................................................... 6
Fundamentals of the LON Network................................................................ 6
Operation of the LON Network....................................................................... 8
Graphical Layout of Information Structure ................................................... 11
Physical Network Structuring ............................................................................... 13

Topologies .................................................................................................... 13
Large-scale Networks .................................................................................. 16
Start-up of LON Network with Viessmann Controls ............................................ 17

Start-up Procedure ....................................................................................... 17
Overview: Functional Objects of Devices ............................................................ 23

General Information ..................................................................................... 23
Vitotronic 100, Model GC1 ........................................................................... 24
Vitotronic 200, Model GW1 .......................................................................... 25
Vitotronic 300, Model GW2 .......................................................................... 26
Vitotronic 333, Models MW1, MW1S and MW2........................................... 28
Vitotronic 050, Model HK1M ........................................................................ 30
Vitotronic 050, Models HK1W and HK1S .................................................... 31
Vitotronic 050, Models HK3W and HK3S .................................................... 32
Vitotronic 200, Model HO1 ........................................................................... 34
Description of Functional Objects ........................................................................ 36

General Information ..................................................................................... 36
Node Object ................................................................................................. 37
Heating Circuit Controller Object ................................................................. 44
Domestic Hot Water Controller Object ......................................................... 46
Local Flow Demand Manager Object........................................................... 47
Central Flow Demand Manager Object........................................................ 49
Production Manager Object (Cascade control) ............................................ 52
Boiler Controller Object ................................................................................ 55
Information for Logical Binding ............................................................................ 59

Information for Self-installation (Selfbinding) ............................................... 59
Device Binding with Start-up Software (Toolbinding) .................................. 59
Additional Information on Toolbinding.......................................................... 66
Additional Information ........................................................................................... 67

Index ............................................................................................................ 67
Applicable Literature/ Websites ................................................................... 68
4
Introduction
This document has been created with various purposes and for use by various target groups:
The chapter “LON Technology” is directed toward heating contractors of central heating systems and
other target groups which are confronted with this kind of technology for the first time. This chapter
then, provides these target groups with a general overview of LON Technology without detailed
information regarding Viessmann control units and their communication.
The chapter “Physical Network Structure” outlines network wiring information and is directed toward
network planning specialists and heating contractors of central heating systems. This chapter pro-
vides recommendations for network development with Viessmann controls.
The chapter “Start-up of LON Networks with Viessmann Controls” describes the settings to be
performed on each control for communication between devices. This chapter targets heating contrac-
tors of central heating systems and system integration specialists who initialize network communica-
tions.
The chapter “Overview: Functional Objects of Devices” offers an overview of functional objects and
network variables contained in devices. It targets network planning and system integration specialists
wanting to exchange data between Viessmann controls and other devices.
The chapter “Description of Functional Objects” is directed toward network planning and system
integration specialists and describes how network variables operate, i.e. what needs to be done for
the creation of interoperable functions by means of network variables.
The chapter “Information for Logical Connection” is designed for system integration specialists. It
outlines the connection of Viessmann controls and allows the system integration specialist to recreate
connections produced in the selfbinding and in the toolbinding mode.
The chapter “Additional Information” features a listing of applicable publications and webpage
addresses for further information on this topic.
5
LON Technology
Fundamentals of the LON Network
What does “LON” mean?

“LON” means “Local Operating Network Technology”. It constitutes a network technology for the
creation of automated networks. “Local Operating” refers to the fact that network participants are
governed by their own ’intelligence‘, allowing for independent, local decisions, without relying on
assistance from the central network node. These network participants – which within the LONW ORKS
Technology structure are called nodes – can be control units, sensors, computers and communica-
tion devices, etc. Transmitted data consists of measured values, metered values, messages as well
as activation and deactivation signals.
Who is who?
The LONW ORKS Technology originated at the U.S. based Echelon Corporation, established in 1986.
The U.S. based “LONMARK Interoperability Association” is an independent union of manufactur-
ers, end users and system integration specialists with more than 100 companies worldwide. It sets
guidelines, supports and fosters the LONMARK interoperability standard worldwide and awards the
LONMARK prize for interoperable products. Viessmann is a member of this organisation.
LONWORKS Components
The LONW ORKS Technology encompasses all components required for the development, start-up, and
operation of automated networks: hardware, software and know-how.
The neuron chip, an electric circuit developed by Toshiba and Cypress specifically for the LON-
W ORKS Technology, constitutes the principal hardware component within the LON Technology. The
chip is physically located on the network node – in Viessmann networks on the communication mod-
ule – and allows data exchange between individual control units.
Network Node
Process
Neuron Electronic function
Network Chip Application (control)
Transceivers are used to interface with the transfer medium. The transfer medium can be anything
from a simple twisted pair of wires to a radio transceiver. A transceiver is a component that can act
both as a transmitter as well as a receiver. The transceiver is responsible for the physical connection
to the network and ensures that network nodes of different manufacturers on the respective transfer
medium comply with the physical requirements for communication.
The network node extracts “intelligence” from the software contained in the neuron chip. This soft-
ware is both the application program, which ensures functioning of the node as part of an applica-
tion process, as well as the operating system, which supplies all communication functions. When
communicating, the LonTalk Protocol is used. The LonTalk Protocol is a communication protocol
stored in the neuron chip. This protocol ensures that the structure of the message exchange between
6
network nodes adheres to strict rules. Similar to the worldwide telephone system, strict requirements
were put in place within the LON Technology to ensure that data exchange between devices of differ-
ent manufacturers can take place.
Another significant component when creating interoperable network nodes is the know-how.
Options contained in the LONW ORKS concept such as the implementation of standard network vari-
able types (SNVTs) support the development of network nodes that can communicate with foreign
network nodes without prior correspondence.
7
Operation of the LON Network
Network Variable Concept

A network node communicates with other nodes of the same network with the help of so-called net-
work variables (NVs). The function of network variables shall be illustrated in the following analogy:
in case of an electrical installation, terminal A of a switch is connected with terminal B of a lamp to
turn the lamp on and off.
Elektroinstallation
Electrical Installation
Switch
Schalter Lamp
Lampe
Cable
Leitung
L A B
Network Variables Communication

Netzvariablen-Kommunikation
Switch Lamp
Schalter Lampe
Transfer
Übertragungs-
medium
medium
Schalte!
Switch on! Licht ein?
Light on?
When communicating with network variables, the application program in the node “switch” interprets
the signal of the electrical contact and writes it, in case of change, to the output network variable
“switch on!” The neuron in turn ensures that the network variable is released to the transfer medium
(network). Upon arrival of the information at node “lamp”, the information is interpreted by the applica-
tion program and the lamp is switched on.
Now the neuron of the switch requires information which node is designated to receive the sent data.
The receiving node “lamp” also requires information regarding which data and from which sender it is
to receive with the input network variable “light on”. This information is generated at the so-called
binding process. Binding also determines which output network variable (see terminals in electrical
installation, which switch controls which lamp) of a sender is to be connected with which input network
variable of which receiver. (See wiring of a cable in electrical installation.)
8
Logical Connections
In the LON Network physical connection between devices takes place via the respective transfer
media. For example, all devices are connected with a twisted pair of wires and are equipped with a
matching transceiver. This physical connection alone, however, is not sufficient for data exchange
and cooperation of the connected devices.
Because physically all devices are connected to ‘the same wire‘, and all devices have access to all
information through input network variables (see terminal in electrical installation example), each
device must be informed as to which information is addressed to it.
Such settings – which data must be sent to which receiver or which data must be received by which
sender – are referred to as logical connections. Such logical connections are generated when
binding. This can take place with the help of a computer (e.g. Notebook PC), that is connected to the
network and a software package – LONW ORKS start-up software (binding tool).
Should a system contain only Viessmann control units, which are set up for communication as rec-
ommended by Viessmann, the connection (binding) takes place in a different manner: Viessmann
controls are equipped with a built-in start-up program, which generates the logical connections re-
quired by Viessmann controls for joint operation. This requires only a few configuration adjustments.
This procedure is called self-binding.
Addressing and Logical Network Structuring

Aside from its physical structure any large network also requires a logical structure. The purpose of a
network consists of data exchange between various network participants. In order for a LON node to
address another node or even a completely different group of nodes, each node within the network
requires an individual address.
A comparison to the telephone network shall clarify this. Within the telephone network each partici-
pant has his/her own worldwide applicable “address”, consisting of the country code (e.g. 001 for
Canada), area code (e.g. 519) as well as a participant’s phone number (e.g. 123 4567).
Similarly, each LON node is designated with its individual logical address within the LON Network.
Designation of an address takes place when binding each node to the network, either with the binding
tool or, as is the case for Viessmann control units, with manual configuration of a system and partici-
pant address at time of start-up.
The logical address of a LON node is structured into three hierarchical parts: domain number, subnet
number and node number, or in network terms: Domain ID, Subnet ID and Node ID.
LON Network Comparison:

Telephone network
Structure Number range controls via selfbinding de-
rived from:
Domain ID 1 … 248 Always fixed Country code
Subnet ID 1 … 255 System number Area code
Node ID 1 … 127 Participant number Participant number
If a node wants to send a message to another node (because the value of a connected network
variable has changed, for example), it will use the logical address as receiver address (e.g.: Domain:
001, Subnet: 15, Node: 27).
In addition to the logical address each neuron chip has a physical address of an individual 48-bit
serial number, called Neuron ID. Usually this one is not used when exchanging data between nodes;
instead the logical address is used. The neuron ID is used for the initial introduction of a node into a
network as well as for network management and diagnostic purposes.
9
Logical Address Structure offers the following advantages:
• Defective nodes can be replaced more easily.
• Data messaging is shorter than when the neuron ID is used.
• In large-scale networks the BUS load can be reduced by using routers. With routers, networks
can be divided into various subnets. Routers ensure that only messages that are intended for
participants of a specific subnet make it into the subnet. This way the BUS load of respective
subnets can be reduced.
Group Address Structure

Aside from structuring the LON Network into domains and subnets, nodes may be divided into logical
groups. This becomes especially practical when more than one participant is to receive the same
message. This way for instance a main disconnect button can send the shut-off message in one
single message to all participants of group “lamps”. Without this group definition, a message would
have to be sent to each lamp individually.
The following limits apply to the group address structure: up to 256 groups may be defined within a
domain. Each node can participate in up to 15 groups.
Viessmann control units also use the group address structure. Accordingly, all devices containing a
heating circuit controller may belong to a group called “load”. These now behave in accordance with
certain messages regarding heat production.
Transmitter Media
The neuron chip is designed for the connection to various transfer media. Transmission via a twisted
pair of wires at different transmission speeds with and without superimposed direct current for power
supply of smaller network nodes is most often used. Alternately, information exchange can take place
using existing power lines. Light wave conductors and radio transmission are other transfer media
that are available. Within one system various forms of transmission may be used. In order to copy
data from one medium to the other, routers are used. Viessmann controls can be equipped with
communication modules for the twisted pair of wires.
Communication Characteristics
When using the existing “Viessmann 2-wire-BUS” (so far used for the communication of Viessmann
controls) one device adopts the function of the BUS master. This means that this device is responsi-
ble for the communication procedure. No other device (all other devices are called “slaves”) is allowed
to send data to the BUS without having permission from the BUS master.
In a LONW ORKS Network the situation is different. All devices are equal; there is no BUS master
permitting transmission. The design of the neuron chips ensures that message collision is prevented.
Nevertheless collisions can never be completely avoided, especially in networks with a high commu-
nication rate.
Various mechanisms ensure that, depending on the importance of the message, these arrive at their
final destination. In a standard procedure, data is transmitted without a return receipt (unacknow-
ledged). In case of important data repeated message sending, a message receipt (acknowledged) or
a request-response procedure can verify a safe transmission. These connection characteristics can
be selected during start-up for each individual connection, using the binding tool.
10
Graphical Layout of Information Structure
In order to illustrate the complex functional structure of a LONW ORKS node in a structured and clear
manner, an illustration of each function segment is required:
Illustration of a Node
The node – i.e. the device and its functions as a whole – is first divided into its functional components.
One functional component can be a heating circuit control, for example. A functional component
comprises all input and output configuration variables for the applicable circuit control.
In place of “functional component” the term “functional object” or “object” is used. One node can
have more than one functional object.
In addition to the application functions of a device, a node may contain a node object, in which all
network variables are stored that must be attributed to the node as a whole and not to a single appli-
cation function.
11
The following illustration is used for the exact correlation of an object (functional object) within a node:
General Illustration of an Object
The object itself is illustrated by a rounded rectangle; a description may be inserted into the upper
segment. Input variables are represented by arrows on the left whose names start with letters “nvi”.
Output variables are shown as arrows on the right, their names start with letters “nvo”.
12
Physical Network Structuring
For each transfer medium - more precisely, for each transceiver type – specific requirements apply,
which must be followed to ensure “clean” communication between all participating BUS devices.
These requirements are as follows:
• wiring structure (topology) of LON devices
• maximum wire lengths
• maximum permissible number of devices
• layout of BUS end
Viessmann communication modules contain a transceiver type FTT 10-A. The following will list the
requirements applicable to this transceiver type. For further information regarding specific require-
ments for wiring, etc. visit www.echelon.com.
Maximum Number of Nodes
For transceiver type FTT 10-A a maximum of 64 nodes are feasible for one network segment. For
large-scale networks, a division into network segments is required (see chapter entitled “Large Scale
Networks”).
Safety Instructions
When connecting devices or installing wires, take note that in all instances the requirements of low
and extra voltage circuits, i.e. 0.3 inches/ 8 mm air distance and access clearance to live components,
are observed. In case of field supplied and installed components, an “electrically safe separation”
must be ensured.
Topologies
BUS or Line Topologies
Networks with a FTT 10-A receiver can be composed of different topologies.

Viessmann, however, recommends, where possible, the use of line or BUS structures for the following
reasons:
• As opposed to free topology, this unique form of network topology allows for an increase of
the maximum admissible wire length. Within this structure, the maximum cable length for FTT
10-A networks is reached.
• Viessmann communication modules, with two RJ45 plug-in connectors each and ready-made
connecting cables, allow for easy installation.
• When using line structuring, not like ring topology, wiring is not polarity sensitive. This means
that the BUS wires can be reversed.
13
BUS or Line Topology
K = Network node
A = Terminator resistor
Networks with BUS or line structuring using Viessmann components can be set up as follows:
a) Mit
WithSystemleitung
system wiring
Heizkreis-
Heating Heizkreis-
Heating
Regelung
Control
Circuit Conrol
regelung Circuit Conrol
regelung
1 1 1 Abschlußwiderstand
Terminator resistor
7mft.
7m/ 23 7m/ 7m
23 ft. 7143497
497 (2 pcs)
7143 Stück)
2 2
2 LON-Verbindungsleitung
LON connecting cable
7142495
7142 495
b) Mit
WithSystemleitung undand
system wiring Kupplung zurfor
coupling Verlängerung
extension 3 LON-Kupplung
LON coupling
7143 496
7143 496
Control Heizkreis-
Heating Heizkreis-
Heating
Regelung
Circuit Conrol
regelung Circuit Conrol
regelung 4 Anschlußdose (bauseits)
Field connections, connect
shield and
Adern wires
1 und 1 and Schirm
2 sowie 2
1 7m/ 23 ft. x times 7m/7m
23 ft. 7m/ 1
7m/
7m23 ft. 7m/ 23
7mft. 7m x mal 7m23 ft. anschließen
2 2 2 2
3 3 3 5 Datenleitung
supplied(bauseits)
Field-supplied
data wiring
c) Mit
Withbauseitiger Anschlußdose
field-supplied
supplied undbox
connection Verlängerung
and extension
Heizkreis-
Heating Heizkreis-
Heating
Control
Regelung
regelung
Circuit Conrol regelung
Circuit Conrol
1 4 4 4 4 1
7m/
7m23 ft. 7m/ 23
7mft 7m/
7m23 ft. 7m/
7m23 ft.
2 1 2 1 2 2 2 1 2 1 2 2
5 5
For networks with BUS or line topologies

topologies, a terminator resistor (Viessmann Part No. 7243 497, pac pack-
age of two) must be installed on both ends of the network segments, in order to buffer reflections of
data signals at the cable ends. This terminator resistor is not a standard resistor, but rather a specific
RC circuit. It is equipped with an RJ45 plug-in
plug connector and can be plugged in at the communication
module.
For networks with FTT 10-A, the

he following maximum values are possible for BUS and line topologies:
Recommended cable Total maximum

type cable length
TIA 568 Category 5
2950 ft/ 900m
(Cat. 5) cable
JY(ST)Y 2x2x0.8 mm
2460 ft/ 750m
(telephone cable)
14
For transition to field-supplied wiring, the LON Connection Terminal (Viessmann part number: 7171
784) can be used.
For communication, wires 1 and 2, as well as shielding are required.
Free Topology
Free topology allows the installation of any network, regardless of structure, in buildings. As the name
FTT (free topology transceiver) indicates, the BUS line can be installed in any given branching combi-
nation when this transceiver type FTT 10-A is used. Star-shaped, ring-shaped and line structures are
possible, as well as any kind of combination.
Free Topology Ring Topology
Star Topology
Combination
Topology
K = Network node
A = Terminator resistor
For networks with free topology, a network segment with a special terminator resistor (not supplied by
Viessmann – e.g. available from Echelon) must be connected in order to dampen reflections of data
signals at cable ends.
For networks with FTT 10-A and free topology, the following maximum values are possible:
Recommended cable Max. distance Max. cable

type between nodes length
TIA 568 Category 5 823 ft/ 250 m 1476 ft/ 450 m
(Cat. 5) cable
JY(ST)Y 2x2x0.8 mm 1049 ft/ 320 m 1640 ft/ 500 m
(telephone cable)
The maximum distances between nodes as stated in table on the previous page refer to distances
between any two nodes – not solely to the maximum distance between neighbouring nodes! Listed
maximum distances also apply to distances between each node and the BUS termination; in other
words, depending on the type of cable no node may be installed more than 820 or 1050 ft/ 250 or 320
m cable length away from the terminator resistor.
15
Large-scale Networks
Large-scale networks require the division into several network segments to function properly. With
each additional network segment, another 64 nodes can be installed. Maximum cable lengths are
applicable to one segment only.
For the connection of network segments, routers and repeaters are used:
Repeaters are devices with two BUS connections, reinforcing the signal strength. Since repeaters
only amplify messages (as opposed to reproducing), a maximum of three repeaters may be con-
nected in a logical series. After that, a router for message reproduction is required.
Like repeaters, routers are devices with two BUS connectors. Their application range, however,
exceeds that of the repeater. Routers have a message filter function and can thereby decide which
message to send on (to the other BUS side) and which not to, in case no device is supposed to
receive the message on the other side. This function allows the reduction of the communication load
(= number of messages per time unit) within individual network segments.
The decision of whether or not to forward the message is made by the router by evaluating the logical
destination address in the message header. This way, the router must be seen as a device which
performs logical network structuring, rather than one of physical network structuring.
Another difference between repeaters and routers is the fact that routers can be equipped with two
different transceivers. This allows different transfer media to be connected to each other. This way, for
example, an extension to a building may be built using a twisted pair of wires, while in the existing
building Power Line Technology (information transfer via 120/ 240V line voltage) was used.
16
Start-up of LON Network with Viessmann Controls
Start-up Procedure
In this chapter we will discuss the required steps for the start-up of the LON Network with Viessmann
controls.
1. Installation and Connection

All controls must be installed and connected according to the accompanying Installation Instructions.
The communication module must be connected as outlined in the applicable Installation Instructions.
2. Network Installation
The communication modules of the control units must either be connected via BUS cables or must be
field connected (for longer cable lengths). All terminator resistors must be connected as described in
the chapter entitled “Physical Network Structure”.
3. Network Configuration
When activating the control units, they connect themselves into one system automatically, using the
integrated self-installation mechanism. For complete start-up of all communication functions, the
following steps are required (depending on system type):
3a. System without Data Exchange with Devices from Other Manufacturers
For systems with Viessmann control units without data exchange with devices of other manufacturers,
the following configuration parameter (coding address) adjustments are required:
Vitotronic 100 GC1:
CA Description: Function Value Adjustment necessary?

(hex)
01 Single/ Multiple boiler system: Only for a multiple boiler system:
determines whether it is dealing 1 Single boiler system
with a single or multiple boiler 2 Multiple boiler system with Vitotronic 333 MW1
system
07 Boiler number: determines the Only for a multiple boiler system
boiler number of a boiler in a 1 … 4 Boiler number 1 … 4
multiple boiler system
77 Participant number: determines Only if participant number “1” is already taken by
node address via selfbinding an other participant:
1… Participant number 1 ... 99
99
98 System number: determines Only if several independent heating systems are
subnet number via selfbinding in one network:
1 ... 5 System number 1 ... 5
79 System fault manager: deter- Only if device is to check other devices for fault/
mines whether device is to record failure (please note: only one control unit per
all fault messages of the heating heating system must be fault manager):
system, checks participants for 0 Device is not fault manager
failure and generate a compiled 1 Device is the fault manager
fault message
CA = Coding Address
17
Vitotronic 200 GW1, Vitotronic 300 GW2 and Vitotronic 200 HO1:

(hex)
node address via selfbinding an other participant:
1… Participant number 1...99
99
subnet address via selfbinding present in one:
79 System fault manager: deter- Only if this device is NOT to check other devices
mines whether device is to record for fault/ failure (please note: only one control
all fault messages of the heating unit per heating system must be fault manager):
system, check participants for Device is not the system fault manager
failure and generate a compiled 0 Device is fault manager
fault message 1
7B Sending time information: Only if the device is NOT to send its time to the
allows the device to send the time network (please note: only one device per net-
to all other nodes in the domain work must provide time information):
0 Device does not send time
1 Device provides time information
81 Receiving time information from Only if device is to use the time provided by
LON: allows the setting of a node network to set its real time clock:
clock according to time informa- 0 Internal clock (without daylight saving time)
tion provided by the network 1 Internal clock (with daylight saving time)
2 Radio clock
3 Device takes time from network
97 Sending/ Receiving of outdoor Only if the device is to send the measured out-
temperature: allows the sending door temperature to other devices or is to adopt
and receiving of the outdoor the network outdoor temperature:
temperature within a subnet 0 Use local outdoor temperature
(please note: only one participant 1 Adopt outdoor temperature from LON
within a system must send the 2 Use outdoor temperature from outdoor sensor
outdoor temperature) and send to LON
CA = Coding Address
18
Vitotronic 333 MW1, Vitotronic 333 MW1S and Vitotronic 333 MW2:

(hex)
35 Number of boilers: determines Only if it is not a four-boiler system:
number of boilers in a system 1 ... 4 Number of boilers 1 ... 4
the node address via selfbinding another participant:
1 ... 99 Participant number 1 ... 99
5 Participant number (default factory setting)
subnet address via selfbinding present in one network:
79 System fault manager: deter- Only if device is NOT to check other devices for
mines whether device is to record fault/ failure (please note: only one control unit
all fault messages of the heating per heating system must be fault manager):
system, check participants for Device is not the fault manager
failure and generate a compiled 0 Device is the fault manager
fault message 1
7B Sending Time Information: Only if the device is NOT to send its time to the
allows the device to send the time network (please note: only one device per net-
to all other nodes in the domain work must provide time information):
0 Device does not send time information
81 Receiving Time Information Only if device is to use the time provided by the
from LON: allows the setting of a network to set its real time clock:
node clock according to time 0 Internal clock (without daylight saving time)
information provided by the net- 1 Internal clock (with daylight saving time)
work 2 Radio clock
3 Device takes time from network
97 Sending/ Receiving of Outdoor Only if the device is to send the measured out-
Temperature: allows the sending door temperature to other devices or is to adopt
temperature within a subnet 0 Use local outdoor
CA = Coding Address
19
Vitotronic 050 HK1W, Vitotronic 050 HK1S, Vitotronic 050 HK1M,
Vitotronic 050 HK3W and Vitotronic 050 HK3S:

(hex)
77 Participant number: determines Only if participant number “10” is already taken
the node address via selfbinding by another participant:
1 ... 99 Participant number 1 ... 99
10 Participant number 10 (default factory setting)
subnet address via selfbinding in one network:
79 System fault manager (not Only if devices is to check other devices for fault/
available with Vitotronic failure (please note: only one control unit per
050HK1M): determines whether heating system must be fault manager):
device is to record all fault mes- 0 Device is not the fault manager
sages of the heating system, 1 Device is the fault manager
check participants for failure and
generate a compiled fault mes-
sage
7B Sending Time Information: Only if the device is to send its time to the net-
allows the device to send the time work (please note: only one device per network
to all other nodes in the domain must provide time information):
0 Device does not send time information
81 Receiving Time Information Only if device is to use the time provided by the
from LON: allows the setting of a network to set its real time clock:
node clock according to time 0 Internal clock (without daylight saving time)
information provided by the net- 1 Internal clock (with daylight saving time)
work 2 Radio clock
3 Devices take time from network
97 Sending/ Receiving of Outdoor Only if the device is to send the measured out-
Temperature: allows the sending door temperature to other devices or is to adopt
temperature within a subnet 0 Use local outdoor temperature
CA = Coding Address
20
3b. System with Data Exchange with Devices from Other Manufacturers
For systems with data exchange with other devices from other manufacturers, or for systems with
Viessmann controls located on opposite sides of a router that must correspond with each other, start-
up software (binding tool) is required for the logical connection of these devices. The toolbinding
process is to be performed by the system integrator. It is his/her task to logically combine the various
devices in a system to one main function. In chapter “Connecting Devices via Start-up Software
(Toolbinding)” all logical connections required for the harmonization of Viessmann devices are de-
scribed.
During toolbinding, all necessary information for connecting the devices is produced with the help of a
computer and the LONW ORKS Binding Tool software (connected to the network) and is written to the
nodes. The process is as follows:
• All devices in the network are identified and introduced to the tool.
• Objects used by these devices are identified and named.
• On the monitor, the user connects all output variables to the input variables of the objects.
Depending on which tool is used, this takes place in a graphics or text format. Everything else
is usually done by the application program.
• The tool sends a series of network management messages via BUS to the nodes, reconfigur-
ing them.
• The toolbinding option also requires the adjustment of the configuration parameter (coding
addresses) as described in 3a. This is the only way to assure the desired function.
From this point on, the node will automatically send changes to its output variables to all predeter-
mined recipients, while its input variables will receive all data from the BUS addressed to it.
4. Participant Check
After the binding and setting of the parameter, a participant check should be performed. This partici-
pant check shows if all Viessmann control units are communicating with each other. Before doing this,
update the participant list of the fault manager (press the D button during the participant check to
erase the list, and wait for ca. 2 minutes until the list reappears).
21
Communication of control units connected to the fault manager is checked with
the Participant Check.
Prerequisite:
Control must be programmed as fault manager (coding "79:1“)
The LON Participant Number has to e programmed in all controls
Participant list in fault manager has to be current
1. Press and OK simultaneously Participant Check is activated.

for 2 seconds.
Participant Check
Participant Check
Participant Number
Serial List Number
2. Select desired Participant with +

or .
3. Activate Check with OK . "Check“ is flashing in display until

Display will indicate "Check OK“ Participant Check is finished.
if communication between both Display and all LEDs are flashing
control units is established. If no for 60 seconds on dialed-up
communication is the case, participant.
"Check not OK“ is displayed. Check for LON connections and
fault messages on respective
4. To check other participants refer control unit.
to points 2 and 3.
5. Press and OK Participant Check is finished.

simultaneously for 2 seconds.
5. Configuration for the Heating System
Following the participant check, a configuration for the heating system (adjustment of hydraulic layout,
burner, etc.) of the system may be performed. For more detailed information, please refer to the
Installation and Service Instructions of Viessmann controls as well as those of other system compo-
nents.
22
Overview: Functional Objects of Devices
General Information
Viessmann control units require two different types of communication modules:
Communication module For use with:

LON module for heating cir- Vitotronic 050, Model HK1M (accessory)
cuits and boiler controller Vitotronic 050, Model HK1W (accessory)
Vitotronic 050, Model HK3W (accessory)
Vitotronic 100, Model GC1 (accessory)
Vitotronic 200, Model HO1 (accessory)
LON module for cascade Vitotronic 333, Model MW1 (standard equipment)
control Vitotronic 333, Model MW1S (standard equipment)
Vitotronic 333, Model MW2 (accessory)
Should the wrong version of the communication module be connected, fault code “bF” – wrong com-
munication module – will appear.
Communication module Part No. 7143 426 provides the required functional objects and network
variables required by all devices. Depending on device and its configuration, network variables
or entire objects may not be functional.
23
Please note: Depending on the system configuration, some functional objects or network variables
may not be functional.
24
25
(continued on following page)
26
Continued: Vitotronic 300, Model GW2
27
Vitotronic 333, Models MW1, MW1S and MW2
28
Continued: Vitotronic 333, Models MW1, MW1S and MW2
29
30
Vitotronic 050, Models HK1W and HK1S
31
Vitotronic 050, Models HK3W and HK3S
32
Continued: Vitotronic 050, Models HK3W and HK3S
33
Vitotronic 200, Model HO1
34
Continued: Vitotronic 200, Model HO1
35
Description of Functional Objects
General Information
The description of functional objects of Viessmann control units explains in detail the meaning and
function of each individual network variable. First, it must be determined whether a network variable is
event-oriented or transmitted cyclically.
In the tables for the input network variables (nvi …), the column “RcvHrtBeat” indicates whether a
cyclical reception of these network variables is expected. If “Yes” appears in this column, it is ex-
pected that the network variable is received cyclically. If no message was received during the “Re-
ceiveHeartBeat-Time” for this network variable, the default value is used internally until another mes-
sage is received. The “ReceiveHeartBeat-Time” is adjustable (in minutes) with coding address “9C”
on the control unit. The factory default setting is set to 20 minutes. The “ReceiveHeartBeat-Time”
should always constitute a multiple of the “SendHeartBeat-Time”. If “No” appears in the column
“RcvHrtBeat”, the network variable is received sporadically.
In the tables for the output network variables (nvo …), the column “SendHrtBeat” indicates whether
the network variable is sent cyclically. If “Yes” appears in this column, the network variable is sent
cyclically. Cyclical sending takes place with the “SendHeartBeat-Time”. The “SendHeartBeat-Time” is
adjustable via a binding tool as a configuration parameter “nciSndHrtBt” (in seconds). The factory
default setting is set to 60 seconds. If the “SendHeartBeat-Time” is drastically increased, the “Re-
ceiveHeartBeat-Time” is to be adjusted accordingly (see above). If “No” appears in the column
“SndHrtBeat”, this network variable is only transmitted sporadically, e.g. when changing the value by
a certain amount.
The column “SNVT Type” determines which data type or which data format is used. Data types start-
ing with “SNVT...” are Standard Network Variable Types, i.e. data types defined as standard data
formats by LONMARK. Data types starting with “UNVT...” are User Defined Network Variable Types,
i.e. Viessmann-defined data formats.
36
Node Object
LONMARK requires a node object for each node. It contains variables, which are applicable to the
device in general and not only to one single functional object. At the very least, network variables
listed as “Mandatory Network Variable” must be available. Viessmann controls (for exceptions see
chapter “Overview: Functional Objects of Devices”) generally provide the above illustrated network
variables.
Configuration Parameter (configuration properties) of the node object:
Name SNVT Type Description RcvHrt

Beat
nciNetConfig SNVT_config_src Tool /Selfbinding: see “LONMARK Application Layer Interop- No
erability Guidelines”, version 3.2, chapter 3 (determines if
selfbinding or toolbinding occurs),
0 = CFG_LOCAL (Factory default setting, self-installed)
1 = CFG_EXTERNAL (tool-installed)
nciSndHrtBt SNVT_time_sec SendHeartBeat, send repeat rate: time for cyclical transmis- No
sion of network variables in segments of 100 milliseconds,
factory default setting = 60.0 sec.
Both of these configuration parameters can be changed with a binding tool. “nciNetConfig” determines
if a node is bound by tool or by selfbinding. The factory default setting is “CFG_LOCAL” (selfbinding).
With “nciSndHrtBt” the “SendHeartBeat-Time” is set. It determines how often a cyclical transmission
of the network variables takes place. This time interval should only be changed if absolutely neces-
sary, for example when the communication load must be reduced. It should then be verified, if the
Receive-Heart-Beat-Time (configuration parameter 9C) requires adjustment.
37
Input network variables of the node object:

Beat
nviNode SNVT_obj_request Object request, see “LONMARK Application Layer Interop- No
Request erability Guidelines”, version 3.2, chapter 3
nviNode SNVT_time_ stamp Time of day input: with this network variable the internal No
TimeSet actual clock time of the device can be set. For Vitotronic
100, Model GC1, it is always activated, for all other control
devices only if coding address “81:3” is selected. It is rec-
ommended to designate one device in the network as the
time of day sender and the other devices as the time recipi-
ents. This ensures that the clocks of all devices in the
network are synchronized.
nviNode SNVT_alarm Fault message input: this input variable receives fault No
Alarm messages from all other Viessmann devices in the system.
This function is used by the central fault manager to receive
cyclical fault messages of the participants. Fault messages
are transmitted cyclically, using SendHeartBeat.
This variable is only functional if coding address “79:1” is
selected.
(This variable is not available for Vitotronic 050, Model
HK1M.)
nviNode SNVT_temp_p Outdoor ambient temperature, outdoor temperature input: Yes
OATemp instead of using the temperature measured by the outdoor
temperature sensor installed directly on the device, the
outdoor temperature measured by another device may be
used. This outdoor temperature, received via nvi-
NodeOATemp is only functional if coding address “97:1”
has been selected. If no temperature value is received
during the Receive-Heart-Beat-Time, a default value of
32°F/ 0°C is used.
38
Output network variables of the node object:
Name SNVT Type Description SndHrt

Beat
nvoNode SNVT_obj_status Object status: see “LONMARK Application Layer Interop- No
Status erability Guidelines”, version 3.2, chapter 3
nvoNode SNVT_alarm Output for fault messages: the last error message is Yes
Alarm transmitted cyclically. If there is no fault, the fault code “00”
is transmitted. (For content of data structure and meaning
of fault code see below.)
nvoNode SNVT_time_stamp Time of day output: output variable for the time synchroni- Yes
TimeSet zation of other devices (only applicable for devices with
own system clock). This network variable is only activated
if coding address “7B:1” is selected.
nvoNode SNVT_temp_p Outdoor temperature output: sends the actual outdoor Yes
OATemp temperature to be used in other devices (only for devices
that are equipped with a sensor input for outdoor tempera-
ture). This variable is only activated if coding address
“97:2” is selected.
nvoNode SNVT_state Relay status output: logical status of control signals of Yes
RlyState device: structure in which logical signals of the control unit
are being exported. If corresponding signals are available
for each control unit (see below), the following applies:
1=on, 0=off or not available.
39
Logical signals of control units in nvoNodeRlyState:
Vitotronic
100 200 300 333 050 050 050 333 200
Bit Logical Signal GC1 GW1 GW2 MW1 HK1M HK1W HK3W MW2 HO1
0 DHW loading pump k k k k - k k k k
1 Recirculation pump - k k k - k k k k
2 Heating circuit pump 1 - x k k x x k k x
3 Heating circuit pump 2 - - k k - - k k k
4 Heating circuit pump 3 - - k k - - k k -
5 Setback contact HCP 1 - x k k x x k k x
6 Setback contact HCP 2 - - k k - - k k k
7 Setback contact HCP 3 - - k k - - k k -
8 Supply pump - - - - k k k - -
9 Primary pump heat
exchanger set for DHW k k k k - k k k -
tank loading
Pump for loading system - - - - - - - - k
10 Boiler circuit or common
k k k k - - - k k
supply pump
Internal pump - - - - - - - - x
11 Shunt pump k k k k - - - k -
Diverting valve in space
- - - - - - - - k
heating position
12 Flue gas heat exchanger
x x x - - - - - -
pump
13 ThermControl switching
k k k - - - - - -
contact
Diverting valve in DHW
- - - - - - - - k
position
14 Burner stage 1 x x x - - - - - -
15 Burner fault x x x - - - - - -
Compiled fault message - - - - - - - - x
x = always available for this device

k = dependent on configuration of device
- = not available for this device
The signals are “high active” i.e. a “1” means “contact closed” specifically “function activated”.
40
Content of data structure SNVT_alarm for Viessmann control units:
Byte Name Content for Viessmann control units

0 ... 5 location Sending location (6 digits ASCII), factory default setting:
“VI ” (VI + 4 blanks)
6 ... 7 objekt_id Object identification of node object
8 alarm_type Alarm type: 0 = AL_NO_CONDITION (in case of no fault),
1 = AL_ALM_CONDITION (in case of fault )
9 priority_level Priority level: 0 = lowest priority (in case of no fault ),
9 = HVAC alarms (in case of fault)
10 … 11 index_to_SNVT Always contains the nvoNodeAlarm index
12 … 13 value[0 … 1] Recognition of Viessmann devices: always 0x1917
14 value[2] Bit 27 unused
Bit 26
5
Bit 2 0 = Participant is not the fault manager
1 = Participant is the fault manager
Bit 24 Warning that content changed (content of fault buffer has
changed since last receipt by Vitocom 300)
Bit 23 System number
Bit 22
1
Bit 2
0
Bit 2
15 value[3] Participant number
16 … 17 year Fault send time
18 month
19 day
20 hour
21 minute
22 second
23 … 24 millisecond Always 0
25 … 26 alarm_limit[0 … 1] Always 0
27 alarm_limit[2] Fault code (high byte), in case of participant failure the fault manager
inputs the participant number of the participant with failure, otherwise 0.
28 alarm_limit[3] Fault code (low byte), see fault codes
Fault codes for Viessmann control units:
Fault Codes (hex) Description

00 System without fault
0F Service required
10 Outdoor temperature sensor short circuit
18 Outdoor temperature sensor interruption
20 Supply temperature sensor HC1/ system short circuit
28 Supply temperature sensor HC1/ system interruption
30 Boiler water temperature sensor short circuit
38 Boiler water temperature sensor interruption
40 Supply temperature sensor heating circuit 2 short circuit
41 Return temperature sensor heating circuit 2 short circuit
44 Supply temperature sensor heating circuit 3 short circuit
45 Return temperature sensor heating circuit 3 short circuit
48 Supply temperature sensor heating circuit 2 interruption
49 Return temperature sensor heating circuit 2 interruption
4C Supply temperature sensor heating circuit 3 interruption
4d Return temperature sensor heating circuit 3 interruption
41
50 DHW tank temperature sensor short circuit
51 DHW tank temperature sensor 2 short circuit
58 DHW tank temperature sensor interruption
59 DHW tank temperature sensor 2 interruption
60 Return temperature sensor 17 short circuit
68 Return temperature sensor 17 interruption
70 Return/ supply temperature sensor 17B short circuit
78 Return/ supply temperature sensor 17B interruption
92 Solar: collector temperature sensor short circuit
93 Solar: collector return temperature sensor short circuit
94 Solar: DHW tank temperature sensor short circuit
9A Solar: collector temperature sensor interruption
9B Solar: collector return temperature sensor interruption
9C Solar: DHW tank temperature sensor interruption
9F Solar: general fault message
A7 Fault control unit (wireless clock module)
AE Internal fault mixing value
AF Internal fault mixing valve
b0 Flue gas temperature sensor short circuit
b1 Programming unit communication fault (internal)
b4 Internal fault
b5 Internal fault
b6 Internal fault invalid hardware recognition
b7 Internal fault boiler protection coding card
b8 Flue gas temperature sensor interruption
bA Fault mixing valve module (KM-BUS)
bC Fault Vitotrol heating circuit 1 (KM-BUS)
bd Fault Vitotrol heating circuit 2 (KM-BUS)
bE Fault Vitotrol heating circuit 3 (KM-BUS)
bF Wrong LON module
C1 External fault message boiler
C2 Communication fault solar control (KM-BUS)
C5 Fault speed-controlled pump heating circuit 1 (KM-BUS)
C8 Fault water level control
C9 Fault maximum pressure
CA Fault minimum pressure/ fault maximum pressure 2
Cb Fault maximum pressure 2
CC Reserved external periphery
Cd Communication fault Vitocom 300 (KM-BUS)
CE Communication fault, fault indicator module (KM-BUS)
CE Communication fault expansion module (KM-BUS)
CF Communication fault: LON module to control card
Warning: this fault code also appears in toolbinding when the
neuron status is “unconfigured”
d1 Burner fault boiler
d4 Fixed high limit fault boiler
d5 Cascade: boiler is not responding
d6 External error 1 plug adaptor
dA Room temperature sensor heating circuit 1 short circuit
db Room temperature sensor heating circuit 2 short circuit
dC Room temperature sensor heating circuit 3 short circuit
dd Room temperature sensor heating circuit 1 interruption
42
dE Room temperature sensor heating circuit 2 interruption
dF Room temperature sensor heating circuit 3 interruption
E0 Fault external participant number/ device connected to LON
E4 Fault power supply voltage
E5 Internal fault combustion control unit
E6 Flue gas/ air supply system clogged
E6 Fault return message oil pre-heater (with Vitoplus)
F0 Communication fault combustion control unit
F1 Flue gas temperature limiter has tripped
F2 Temperature limiter has tripped
F3 Flame signal is present at burner start
F4 Flame signal is not present
F5 Air pressure switch not open for burner start or not closed when
ignition load is achieved
F6 Gas pressure switch not open for burner start or after flame
stabilization not closed
F7 Air pressure sensor short circuit or offset value outside of toler-
ance
F8 Fuel valve closure delayed
F9 Blower speed too low at burner start
FA Blower speed too high at burner start
FC Control of modulation valve defect
FD Fault combustion control unit
FE Coding plug defect or wrong EMV-error
FF Internal fault
43
Heating Circuit Controller Object
(x= 1, 2 or 3)
The heating circuit controller object constitutes the interface between the heating circuit control and
room temperature control. The communication module provides a functional object of this type for
each heating circuit control loop of a control. Within the control unit, however, certain heating circuits
may be deactivated with coding address “00”. This means that the corresponding functional object is
also not functional.
The table below shows the maximum number of accessories for each control unit:
Control unit Heating circuit 1 Heating circuit 2 Heating circuit 3

Vitotronic 050 HK1M Mixing valve - -
circuit M1
Vitotronic 050 HK1W, Mixing valve - -
Vitotronic 050 HK1S circuit M1
Vitotronic 050 HK3W, Mixing valve Mixing valve Mixing valve
Vitotronic 050 HK3S circuit M1 circuit M2 circuit M3
Vitotronic 100 GC1 - - -
Vitotronic 200 GW1 System circuit A1 - -
Vitotronic 300 GW2 System circuit A1 Mixing valve Mixing valve
circuit M2 circuit M3
Vitotronic 333 MW1, System circuit A1 Mixing valve Mixing valve
Vitotronic 333 MW1S, circuit M22 circuit M3
Vitotronic 333 MW2
Vitotronic 200 HO1 System circuit A1 Mixing valve -
circuit M2
Input network variables of the heating circuit controller object (HCC):

Beat
nviHCCx SNVT_ hvac_mode Heating circuit operating mode: determines how the heating Yes
ApplicMd circuit is to be influenced, see description below. If no mes-
sage is received during the Receive-Heart-Beat-Time, the
default 0xFF (=HVAC_AUTO) is used.
nviHCCx SNVT_ temp_p Room setpoint temperature: only functions if nviHCCxAp- Yes
SpaceSet plicMd is set to HVAC_HEAT. If no message is received
during the Receive-Heart-Beat-Time, a default value of 68°F/
20°C is used.
44
Beat
nviHCCx SNVT_ temp_p Supply setpoint temperature: functions only if nviHCCxAp- Yes
FlowTSet plicMd is set to HVAC_FLOW_TEMP. If no message is
received during the Receive-Heart-Beat-Time, although
nviHCCxApplicMd is still received with
HVAC_FLOW_TEMP, a default value of 68°F/ 20°C is used.
The network variable nviHCCxApplicMode of the heating circuit controller object has the following
effect:
Value Name Description

0 HVAC_AUTO The heating circuit control operates according to the internal settings on the
0xFF (default value)
control unit. Network variables nviHCCxSpaceSet and nviHCCxFlowTSet are not
functional. This is the factory default setting, which is also adopted if no message
for viHCCxApplicMd is received during the “ReceiveHeartBeat-Time”.
1 HVAC_HEAT The heating circuit control operates according to the heating curve and uses
nviHCCxSpaceSet as room temperature setpoint, i.e. operating mode switch,
timer and room setpoint temperature setting of the heating circuit are disabled.
Frost protection and economy mode (e.g. automatic warm weather shut-down)
can be activated. The network variable nviHCCxFlowTSet is not functional.
2 HVAC_MRNG_ The heating circuit control operates according to the heating curve and uses the
WRM_UP reduced room setpoint temperature of the control unit as room setpoint value, i.e.
operating mode switch and timer of the heating circuit are disabled. Frost protec-
tion and economy mode (e.g. automatic warm weather shut-down) can be acti-
vated. Network variables nviHCCxSpaceSet and nviHCCxFlowTSet are not
functional.
(3) HVAC_OFF The heating circuit control is turned off and only activates for frost protection
(4) (freeze-up temperature limit can be set with coding address) with a reduced room
(5) setpoint temperature. Network variables nviHCCxSpaceSet and
6 nviHCCxFlowTSet are not functional.
7 HVAC_TEST The heating circuit control operates according to the heating curve and uses
normal room setpoint temperature of the control unit as room setpoint value, i.e.
operating mode switch and timer of the heating circuit are disabled. Frost protec-
tion and economy mode (e.g. automatic warm weather shut-down) can be acti-
vated. Net variables nviHCCxSpaceSet and nviHCCxFlowTSet are not functional.
8 HVAC_EMERG_ The heating circuit control operates with a set supply setpoint temperature of
HEAT 68°F/ 20°C, i.e. heating curve, operating mode switch, timer, frost protection and
economy mode are disabled. Net variables nviHCCxSpaceSet and
nviHCCxFlowTSet are not functional.
100 HVAC_FLOW_ The heating circuit control operates with a supply setpoint temperature according
TEMP to nviHCCxFlowTSet, i.e. heating curve, operating mode switch, timer, frost
protection and economy mode are disabled. The coding address for the supply
temperature maximum remains active. Network variable nviHCCxSpaceSet is not
functional.
Output network variables of heating circuit controller object (HCC):

Beat
nvoHCCxUnit UNVT_hvac_ Actual operating status of heating circuit control: outputs Yes
State mode the currently active value of nviHCCxApplicMd (see
description above)
nvoHCCxEffRm SNVT_temp_p Effective room setpoint temperature: outputs the currently Yes
Setp effective room setpoint temperature
45
Domestic Hot Water Controller Object
The domestic hot water controller object allows for the possibility to influence domestic hot water
production. With coding address “00” the domestic hot water control of the unit can be deactivated. At
the same time, this functional object becomes non-functional.
Input network variables of the domestic hot water controller object (DHWC):

Beat
nviDHWC SNVT_ temp_p DHW setpoint temperature is used if nviDHWCApplicMd = No
Setpt HVAC_HEAT
nviDHWC SNVT_ hvac_ Operating mode DHW: (See description below). If no mes- Yes
ApplicMd mode sage is received during the Receive-Heart-Beat-Time, default
value 0xFF (=HVAC_AUTO) is used.
The network variable nviDHWCApplicMd has the following function:
Value Name Description

0 HVAC_AUTO Both the DHW controller and the recirculation pump operate according to the
0xFF internal setting on the control unit. The network variable nviDHWCSetpt is not
functional. This is the factory default setting, which is used in case no message is
received for nviDHWCApplicMd during “ReceiveHeartBeat-Time”.
1 HVAC_HEAT The DHW controller is operational and uses nviDHWCSetpt as DHW setpoint
temperature, i.e. operating mode switch, timer and DHW setpoint temperature of
the control are disabled. The recirculation pump is activated with configuration
parameter setting 64:1 and 64:2 and deactivated with 64:0.
(3) HVAC_OFF The DHW controller is turned off and only activates for frost protection (freeze-up
(4) temperature limit = DHW tank temperature 50°F/ 10°C). The network variable
(5) nviDHWCSetpt is not functional. The recirculation pump is turned off.
6
Output network variables of the domestic hot water controller:

Beat
nvoDHWCAct SNVT_temp_p Actual DHW temperature in °C Yes
Temp
nvoDHWCEffSetpt SNVT_temp_p Actual resulting DHW setpoint temperature in °C Yes
46
Local Flow Demand Manager Object
The local flow demand manager object facilitates data exchange among Viessmann control units and
is not required for the integration of external components.
The local flow demand manager object collects all internal temperature requirements in a Viessmann
control unit without its own heat production management (heating circuit controls Vitotronic 050). It
then passes these on to a device which controls heat production. Upon return, the local flow demand
manager object forwards status messages, received from the heat production management, to the
internal heating loads (heating circuits and DHW heating).
The network variables of all LFDM objects in a system are connected to corresponding network
variables of the CFDM objects in a system.
47
Input Network Variables of Local Flow Demand Managers (LFDM):
Beat
nviLFDMProd UNVT_ProdState System status: data structure (4 byte) for transmitting heat Yes
State production status to the heat consumers:
Byte [0]: output reduction in 0.5% increments (e.g. for
TSA function) as requested by the consumers,
0 = default value
Byte [1]: Reduction/ request for heat consumption:
bit 0: output reduction is critical
bit 1: active DHW tank load
bit 2: DHW request to central DHW storage tank
bit 3: unused
bit 4: heat consumption requested due to critical excess
heat (overheating)
bit 5: likewise for non-critical excess heat (boiler water
temperature is significantly higher than setpoint value)
bit 6: residual heat in boiler (after end of heat demand)
bit 7: unused
0x00 = default value
Byte [2]: production status: at least one …
bit 0: boiler is logged off (disabled or off)
bit 1: boiler received log-off request (soft disabled)
bit 2: boiler fault
bit 3: boiler is set to override operation
bit 4-7: unused
default value: bit 0 = 1 (off), bit 1 … 3 = 0
Byte [3]: central functions:
bit 0: central control activated
bit 1: central holiday program
bit 2: central operating mode “continuous standby mode”
bit 3: central operating mode “DHW production only”
bit 4: central operating mode “space heating and DHW
production”
bit 5-7: unused
0x00 = default value
Output Network Variables of Local Flow Demand Managers:

Meaning of SNVT Type Description SndHrt
Name Beat
nvoLFDMCon UNVT_Demand Supply temperature demand by heating circuit controls: Yes
sDmd Transfer of consumer demand for heat to heat production:
Byte[0], Byte[1]: supply setpoint temperature (Temp_p)
Byte[2], Byte[3]: attributes to heat demand (State):
bit 0: temperature request is maximum value
bit 1-7: unused
bit 8: DHW request to storage tank in central device of
heating system (independent of temperature request)
bit 9-15: unused
Byte[4] ... Byte[9]: neuron ID of sender (6 Bytes)
The network variable nvoLFDMConsDmd is the result of the maximum value calculation of the
requested supply temperatures of all the consumers (e.g. heating circuits). The forwarded value
contains (among other information) the neuron ID of the node.
48
Central Flow Demand Manager Object
The central flow demand manager object collects the demands of the heat consumers in the network
and calculates the maximum value of all the incoming temperature requests at input
nciCFDmConsDmd (requests from Viessmann heating control units). The network variables
nciCFDmConsDmd and nvoCFDMProdState are bound to the corresponding system network va-
riables of all LFDM objects.
Superior systems (building management systems, air conditioning systems, ventilation systems, etc.)
can influence the heat production via other input network variables. They can set additional tempera-
ture or load requests or also completely shut off heat production.
The functional object calculates from the maximum value of the requests of the external heat con-
sumer (nciCFDmConsDmd), the other input network variables, and the internal requests of the control
unit itself (heating circuit controller and other requests contained within the device, i.e. digital inputs)
the resulting request to the heat production.
Furthermore, the CFDM passes on the signals for output reduction or forced heat absorption to the
consumer, specifically the inferior LFDMs in its segment. The data from the internal heating circuits
regarding the central heating circuit control and the data of the internal DHW tank control regarding
the DHW loading status are likewise passed on to the external consumer.
49
Input Network variables of CFDM:
Beat
nviCFDMProd SNVT_switch Systems or boiler setpoint output: Yes
Cmd Byte [0] Value: 0 … 200 in 0.5% intervals
(200 = 100%)
Minimum output in % of boiler/ system
rated output, 0 = default value
Byte [1] Status: 0 = boiler/ system off,
1 = boiler/ system on,
0xFF = auto = default value
This input variable has priority over all other com-
mands/ requests, e.g. when for example status = 0,
then the boiler or system will be shut off, regardless of
other remaining requests.
nviCFDMAp- SNVT_hvac_mode System operating mode (see table below) Yes
plicMd
nviCFDMSet- SNVT_temp_p Supply setpoint temperature (the system can be selec- Yes
point tively controlled by temperature or output, the output
command has priority, see above), default value =
32°F/ 0°C
nviCFDMCons UNVT_Demand Supply temperature request by heating circuit controls: Yes
Dmd Byte[0], Byte[1]: Supply setpoint temperature
(Temp_p)
Byte[2], Byte[3]: Attribute to heat demand (State):
bit 0: temperature request is maximum value
bit 1 – 7: unused
bit 8: DHW demand to central DHW tank (independent
of the temperature request)
bit 9 – 15: unused
Byte[4] ... Byte[9]: Neuron ID of sender (6 bytes)
Default values: Byte[0] … Byte[9] = 0
(request = 32°F/ 0°C)
The network variable nviCFDMProdCmd has highest priority. With it, an output preset for the system
can be set. This preset overrides all other requests. For example, at status = 0, heat production is
available for some control units. With status = 1, the boiler/ system output can be preset with the
value; for values below the minimum boiler output, the minimum output is produced, etc. If no preset
is made via input nviCFDMProdCmd or status = 0xFF, all other demands become effective,
nviCFDMApplicMd is evaluated. The network variable nviCFDMApplicMd of the central flow demand
manager object has the following effect:
Value Title Description

0 HVAVC_AUTO The internal demands of the control device (heating circuit controls and
1 HVAC_HEAT digital inputs), the demands of the external heating circuit controls via
0xFF (default value) nviCFDMConsDmd and the demands via nviCFDMSetpoint are evaluated.
If all demands go to 32°F/ 0°C, then under certain circumstances, mini-
mum boiler water temperature is maintained.
2 HVAC_MRNG_ The internal demands of the control unit (heating circuit controls and
WRM_UP digital inputs), the demands by external heating circuit controls via
nviCFDMConsDmd and the demands via nviCFDMSetpoint are ignored.
However, the minimum boiler water temperature is maintained.
(3) HVAC_OFF Heat production is shut off. The internal demands of the control device
(4) (heating circuit controls and digital inputs), the demands of the external
(5) heating circuit controls via nviCFDMConsDmd and the demands via
6 nviCFDMSetpoint are ignored. Minimum boiler water temperature is not
(9) maintained.
50
7 HVAC_TEST Heat production takes place at base boiler output, or for example, base output
of the system lead boiler. The internal demands of the control unit (heating
111 HVAC_LOW_ circuit controls and digital inputs), demands of the external heating circuit
FIRE controls via nviCFDMConsDmd and demands through nviCFDMSetpoint are
ignored. However, minimum and maximum boiler water temperatures are
maintained.
8 HVAC_EMERG Heat production works with rated output or total output of the system lead
_HEAT boiler. Internal demands of the control unit (heating circuit controls and digital
112 inputs), demands of the external heating circuit controls via
HVAC_HIGH_ nviCFDMConsDmd and the demands via nviCFDMSetpoint are ignored.
FIRE However, minimum and maximum boiler water temperatures are maintained,
i.e. when the electronic maximum boiler water temperature limit is reached,
under certain circumstances, boiler output is reduced.
Output Network Variables for CFDM:

Beat
nvoCFDMPwr SNVT_switch Actual system output in % of rated system output: Yes
State Byte [0] Value: 0 … 200 in 0.5% steps (200 = 100%)
Minimum output in % of boiler/ system rated
output, 0 = default value
Byte [1] Status: 0 = boiler/ system off,
1 = boiler/ system on
nvoCFDMEff SNVT_temp_p Active system/ boiler setpoint temperature value Yes
Setpt
nvoCFDMSup SNVT_temp_p System supply temperature/ actual boiler water temperature Yes
plyT
nvoCFDMProd UNVT_Prod- System production status: information to the heat consumer Yes
State State (Viessmann heating circuit controls):
Byte [0]: output reduction in 0.5% increments (i.e. for TSA
function) as requested by the consumers
Bye [1]: reduction/ request of heat consumption:
bit 1: DHW tank load is active
bit 2: DHW demand to central DHW tank
bit 3: unused
bit 4: heat consumption requested due to critical excess
heat (overheating)
bit 5: likewise with non-critical excess heat (boiler water
temperature significantly higher than setpoint)
bit 6: residual heat in boiler (after request ended)
bit 7: unused
Byte [2]: Production status: at least one …
bit 0: boiler is logged off (disabled or off)
bit 1: boiler received log off request (soft disabled)
bit 2: boiler fault
bit 4-7: unused
Byte [3]: central functions:
bit 0: central control active
bit 1: central holiday program active
bit 2: central operating mode “continuous standby mode”
bit 3: central operating mode “DHW production only”
bit 4: central operating mode “space heating and DHW
production”
bit 5-7: unused
51
Production Manager Object (Cascade control)
(x = 1, 2, 3 or 4)
The production manager object contains the technical control functions of the cascade control in a
multiple boiler system. The purpose is to control the heat production with respect to the heat de-
mand and heat consumption. Depending on heat demand, boiler status and internal settings, boilers
are switched on or off. The production manager object contains interfaces PM1 … PM4 for data
exchange between up to four boilers. Interfaces PM1 … PM4 are bound to the boiler controller ob-
jects of these boilers. Thus, always bind interfaces starting with PM1. In a two-boiler system, for
example, boilers must be bound to interfaces PM1 and PM2.
52
Input Network Variables of the Production Manager (PM) per Boiler:
Beat
nviPMxBlrState SNVT_switch Current actual boiler output in % of rated output: Yes
Burner Status Byte[0]: Value Byte[1]:
Type Status
Single OFF 0 = 0% 0 = OFF
stage ON 200 = 100% 1 = ON
Two stage OFF1 0 = 0% 0 = OFF
STAGE1 100 = 50% 1 = ON
STATGE2 200 = 100% 1 = ON
Modulating OFF 0 = 0% 0 = OFF
MOD 1….200 = 1 = ON
0.5…100%
nviPMxSupplyT SNVT_temp_p Current actual boiler water temperature Yes
nviPMxBoCState UNVT_BoC Boiler status: Boiler status to cascade control: Yes
State Byte [0]: output reduction in 0.5% increment (i.e. for TSA
function) requested by consumers, default = 0%
Byte [1]: reduction/ request of heat consumption:
bit 21 to bit23: reserved
4
bit 2 : heat consumption requested due to critical excess
heat (overheating)
bit 25: likewise for non-critical excess heat (boiler water
6
bit 2 : residual heat in boiler (after request ended)
7
bit 2 : unused
default = 0x00
Byte [2]: Boiler/ isolation valve status:
0
bit 2 : boiler is logged off (disabled or off)
1
bit 2 : boiler received log off request (soft disabled)
bit 22: boiler fault
4 7
bit 2 to bit 2 : isolation valve (IV) status: (enumeration)
0 – IV_CLOSED, 1 – IV_PREHEAT,
2 – IV_CONTROL_CLOSED, 3 – IV_CONTROL,
4 – IV_CONTROL_OPEN, 5 – IV_OPEN,
6 – IV_TIME_DELAY_CLOSED
0 1 3 4
Default values: bit 2 = 1 (off), bit 2 ...bit 2 = 0, bit 2 ...bit
7
2 = IV_CLOSED
Byte [3], Byte [4]: operating hours burner stage 1 (in
hours), default = 0
Byte [5]: burner status:
bit 20 to bit 21: burner type (enumeration, like configuration
parameter settings on boiler, with consideration to input
“changeover staging/ modulating”)
2 7
bit 2 to bit 2 : unused
default = two stage
Byte [6], Byte [7]: rated output in kW (configuration
parameter), default = 0
Byte [8]: relative output of low-fire stage in 0.5% incre-
ments of rated burner output (configuration parameter is
evaluated in full percentage)
Default = 60%
Byte [9]: return temperature control from boiler coding
card (in full degree Celsius), default = 127°F/ 53°C
53
Output Network Variables of the Production Manager (PM) per Boiler:
Beat
nvoPMxBoiler SNVT_switch Boiler setpoint output Yes
Cmd Burner Byte[0]: Byte[1]: Burner
Type Value in 0.5% Status Status
Steps
Single stage 0 = 0% 0 =OFF OFF
1...200 = 1 = ON ON
100%
Two stage arbitrary 0 =OFF OFF
1...100 = 50% 1 = ON STAGE1
101...200 1 = ON STAGE2
= 100%
Modulating 0 = 0% 0 =OFF OFF
1 … 200 = 1 = ON MOD
0.5 … 100%
All burners Arbitrary 0xFF After nvoPM-
= default xApplicMd
This network variable has priority over all other com-
mands/ requests, i.e. when status = 0, the boiler will be
shut off, regardless of the value of other input network
variables.
nvoPM- SNVT_hvac_ Boiler operating mode, see table in chapter “Boiler Con- Yes
xApplicMd mode troller Object”
nvoPMxSetpoint SNVT_temp_p Boiler setpoint temperature: (the boiler can either be Yes
temperature controlled and/ or output controlled, the
output command has priority, see above)
For description of the network variable function and operation of the boiler control, see following
chapter.
54
Boiler Controller Object
The boiler controller object depicts the interface of the boiler control in a multiple boiler system. This
object is not active in a single-boiler system – in a single-boiler system, external demands are bound
to the CFDM object, the central demand manager of the system, and are processed together with the
device demands of internal and external heating circuit control.
In a multiple boiler system the operation of the boiler control takes place via three input network
variables. In this case, the boiler control is entirely mandated by the cascade control – the internal
demands of the device (boiler setpoint temperature and DHW production of a Vitotronic 100, Model
GC1) are not functional.
Depending on the chosen control strategy, a cascade control can request from the boiler an output in
% of boiler rated output or the boiler setpoint temperature, or both.
55
Input Network Variables of a Boiler Controller (BoC):
Name SNVT Type Description RcvHr
tBeat
nviBoC SNVT_switch Boiler setpoint output Yes
BoilerCmd Burner Bye[0]: Value in Byte[1]: Burner
Type 0.5% intervals Status Status
Single 0 = 0% 0 = OFF OFF
stage 1...200 = 100% 1 = ON ON
Two stage Arbitrary 0 = OFF OFF
1…100 =50% 1 = ON STAGE1
101...200 = 100% 1 = ON STAGE2
Modulating 0 = 0% 0 = OFF OFF
1…200 = 1 = ON MOD
0.5…100%
All burners Arbitrary 0xFF = After nviBoC-
default ApplicMd
This network variable has priority over all other commands/
requests, i.e. when status = 0, then the boiler will be shut
off, regardless of the value of the other input variables.
nviBoCAp- SNVT_hvac_mod Boiler operating mode: see description below Yes
plicMd e
nviBoC SNVT_temp_p Boiler setpoint temperature: (the boiler can either be tem- Yes
Setpoint perature controlled or output controlled, the output com-
mand nviBoCBoilerCmd has priority, see above) default =
261°F/ 127°C
The network variable nviBoCBoilerCmd has highest priority. With it, an output preset for the boiler
can be set. This preset overrides all other requests. For example, at status = 0, the boiler will be shut
off. At status = 1, the boiler setpoint output can be preset with the value; for values below the mini-
mum boiler output, the minimum output is produced, etc. If no preset is made via input nviBoCBoi-
lerCmd or status = 0xFF, all other demands become effective, nviBoCApplicMd is first evaluated.
56
The network variable nviBoCApplicMd of the boiler controller object has the following function, as
described in the table below:

0 HVAC_AUTO The request through nviBoCSetpoint is evaluated. If nviBoCSetpoint goes
1 HVAC_HEAT to 32°F/ 0°C, then depending on the boiler model, under certain circums-
0xFF (default value) tances, the minimum boiler water temperature is maintained.
2 HVAC_MRNG_ If there is no request to the boiler, then depending on boiler type, under
WRM_UP certain circumstances, the minimum boiler water temperature is main-
tained.
(3) HVAC_OFF The boiler is shut off. The isolation value is closed. Requests via nviBoC-
(4) Setpoint are ignored. Minimum boiler water temperature is not main-
(5) tained.
6
(9)
7 HVAC_TEST The boiler is running on low-fire. The request through nviBoCSetpoint is
111 HVAC_LOW_ ignored. Minimum and maximum boiler water temperatures are, however,
FIRE maintained.
8 HVAC_EMERG_ The boiler operates at rated output. The request through nviBoCSetpoint
HEAT is ignored. Minimum and maximum boiler water temperatures are, how-
112 HVAC_HIGH_ ever, maintained.
FIRE
110 HVAC_SLAVE_ The boiler takes temperature and output requests into consideration, i.e.
ACTIVE at the very least, the boiler operates at the setpoint output transmitted by
nviBoCBoilerCmd value and the setpoint temperature transmitted by
nviBoCSetpoint, whereas the minimum and maximum boiler water tem-
peratures are maintained.
The local input “disabled” is always evaluated and has priority, even with control via nviBoCBoi-
lerCmd.
57
Output Network Variable of the Boiler Controller Object:
Beat
nvoBoCBlr SNVT_switch Current actual boiler output in % of rated output: Yes
State Burner Type Status Byte[0]: Value Byte[1]:
Status
Single stage OFF 0 = 0% 0 = OFF
ON 200 = 100% 1 = ON
Two stage OFF1 0 = 0% 0 = OFF
STAGE1 1 = ON
STATGE2 200 = 100% 1 = ON
Modulating OFF 0 = 0% 0 = OFF
MOD 1…200 = 1 = ON
0.5…100%
nvoBoCEff SNVT_temp_p Current effective boiler setpoint temperature Yes
Setpt
nvoBoC Sup- SNVT_temp_p Current actual boiler water temperature Yes
plyT
nvoBoC UNVT_BoC Boiler status: Boiler status to cascade control: Yes
BocState State Byte [0]: output reduction in 0.5% increments (i.e. for TSA
function) demanded by the consumers
Byte [1]: reduction/ request of heat consumption:
0
bit 2 : output reduction is critical
bit 21 to bit23: reserved
bit 24: heat consumption requested due to critical excess heat
(overheating)
5
bit 2 : likewise with non-critical excess heat (boiler water
bit 26: residual heat in boiler (after request ended)
bit 27: unused
Byte [2]: Boiler/ isolation valve status:
0
bit 2 : boiler is logged off (disabled or off)
bit 21: boiler received log off request (soft disabled)
2
bit 2 : boiler fault
3
bit 2 : boiler is set to override operation
bit 24 to bit 27: isolation valve status: (enumeration)
0 – IV_CLOSED, 1 – IV_PREHEAT,
2 – IV_CONTROL_CLOSED, 3 – IV_CONTROL,
4 – IV_CONTROL_OPEN, 5 – IV_OPEN,
6 – IV_TIME_DELAY_CLOSED
Byte [3], Byte [4]: operating hours burner stage 1 (in hours)
Byte [5]: burner status:
0 1
bit 2 to bit 2 : burner type (enumeration, like configuration
parameter set on boiler, with consideration to the input
“changeover staging/ modulating”)
2 7
bit 2 to bit 2 : unused
Byte [6], Byte [7]: rated output in kW (configuration parame-
ter)
Byte [8]: relative output of low-fire in 0.5% increments of
rated burner output (configuration parameter is processed in
full percentage points)
Byte [9]: setpoint value for return temperature control from
boiler coding card (in full degree Celsius)
58
Information for Logical Binding
Information for Self-installation (Selfbinding)

Viessmann self- installation takes place as follows:
After activating power to the control, the processor of the electronic circuit board sends information
regarding device type and several configuration parameters to the communication module. If the
configuration parameter nciNetConfig is set to “CONFIG_LOCAL” (factory default setting), the self-
installation process is started. The communication module completes the address table as well as
network variable table with information based on configuration data received from the circuit board
processor.
Certain parameters are established:
• All Viessmann devices belong to domain 07 when self-installed.

• The system number (coding address 98) becomes the subnet address.
• The participant number (coding address 77) becomes the node address.
• Depending on the configuration, group affiliations “alarm”, “producer”, “load” and “production
manager” are entered into address table.
• In addition, depending on the device, address table entries for the domain broadcast and
subnet broadcast are created.
• Depending on type of device and the setting of the configuration parameter, the required net-
work variables are assigned to the corresponding address table information.
When self-installation is active, the configuration parameters 01, 07, 35, 77, 79, 7B, 81, 97 and 98
influence the logical connections between the devices and the control functions. If the devices are
bound via start-up software (toolbinding), the logical connections of the devices have no effect. For
proper function, setting of these configuration parameters is necessary.
Device Binding with Start-up Software (Toolbinding)

In the factory default setting, Viessmann control units are bound via self-installation process (selfbind-
ing). This self-installation process establishes all necessary connections for data exchange between
Viessmann control units. This, however, does not cover the entire range of requirements.
Especially the following requirements cannot be covered by the selfbinding process:
• If data must be exchanged between Viessmann control units and devices from other manu-
facturers.
• If, in addition to the relay outputs of the control, logical signals of the controls processor
should be used via an in-/ output module.
• If, for example, via an external 0-10V analog signal, a heat demand is connected for heat
production.
• If Viessmann control units in a system are located on both sides of a router due to long ca-
bling.
• If data exchange between Viessmann control units must take place in a different manner than
prescribed by the selfbinding process, e.g. if the outdoor temperatures of three sensors must
be distributed to two devices.
• If more than five Viessmann heating plants are installed in a network.
• Other possible requirements
If one of the above requirements applies, the system must be configured via start-up software (tool-
binding). When configuring with start-up software, all other bindings that would have been established
by the self- installation process, must be performed as well.
59
For the support of the toolbinding configuration the control units provide the following functions:
• By pressing buttons + and – simultaneously (approx. 2 secs.), a service pin message is re-
leased.
• The service LED (VL2) on the communication module shows the node status according to
generally applicable regulations. A second LED (VL1) shows by flashing (0.5 sec. on/1 sec.
off) the proper operation of the second communication module processor.
• When a node receives the Wink Message, the entire display of the device and all LEDs of
the operating unit flash for one minute or until any button is pressed.
• XIF files are available for the communication modules of Viessmann controls, or can be gen-
erated with the binding-tool from the self-documentation of the node.
• In the diagnostic level of the control units, selfbound or toolbound status of individual devices
is shown. To update this display, after toolbinding is completed, the device must first be
turned off and then turned on again.
Overview
A general overview of the connections established by the Viessmann selfbinding process is illustrated
below:
Connections Description
Between all LFDMs and the The network variables of the LFDMs of all heating circuit controls (devices
CFDM of the system without own heat production) are bound to the corresponding network
variables of the CFDMs of the system. Only one CFDM per system may
be active.
Between the BoCs and the PM In a multiple boiler installation the network variables of the BoCs are
of the system bound to the network variables of PM1…PM4 (starting with PM1).
Between the fault manager Network variables nviNodeAlarm of the designated fault manager and
and all other devices of the potential Vitocom 300 receive data from all other device network variables
system nvoAlarm on the system.
Between the time of day infor- Network variable nvoNodeTimeSet of the unit designated as time of day
mation sender and the time of sender is bound to network variable nviNodeTimeSet of all other units in
day information receiver the domain.
Between the outdoor tempera- The network variable nvoNodeOATemp of the device which is to send the
ture sender and the outdoor outdoor temperature is bound to network variable nviNodeOATemp of all
temperature receiver other units of the system.
60
Binding between the Central Flow Demand Manager (CFDM) of the system and all Local Flow
Demand Managers (LFDM) of the system:
These bindings are required if one or more heating circuit controls (Vitotronic 050 HK1M, HK1W or
HK3W) must send a demand for heat to a single boiler system (to Vitotronic 100 GC1, 200 GW1, 300
GW2, 200 HO1) or to a multiple boiler system (to Vitotronic 333 MW1 or MW2).
Device Network Comm. Network Device
Object
Object
Variable variable
all Vitotronic 050 nviLFDMProd nvoCFDMProd In a single boiler system:

HK1M, State State Vitotronic 100 GC1, 200
050 HK1W(S) and GW1, 300 GW2 or 200
CFDM
LFDM
050 HK3W(S) nvoLFDM nviCFDM HO1

of a system ConsDmd ConsDmd In a multi-boiler system:
Vitotronic 333 MW1(S)
or 333 MW2
61
Binding between the Production Manager (PM) and the Boiler Controllers (BoC) in a multiple
boiler system:
These bindings establish the connections between the cascade control of the multiple boiler system
and the boiler controls of each individual boiler. These bindings are required for each multiple boiler
system with Vitotronic 333 MW1 as cascade control and up to four Vitotronic 100 GC1s as individual
boiler controls.
The number of boilers can be set using coding address 35 from 1 to 4 on the Vitotronic 333 MW1.
Boiler 1 of the system:
Device Network variable Comm. Network variable Device: Setting of

Object
Object
coding addresses
nviPM1BlrState nvoBoCBlrState
(Boiler number, factory setting)

Coding address 01:2 (multiple
Vitotronic 100 GC1 of the first
boiler in a multiple boiler sys-
nviPM1SupplyT nvoBoCSupplyT
nviPM1BoCState nvoBoCBoCState
Coding address 07:1

PM1
BoC
(Cascade control)
nvoPM1BoilerCmd nviBoCBoilerCmd
boiler system)
nvoPM1ApplicMd nviBoCApplicMd
nvoPM1Setpoint nviBoCSetpoint
tem:
Boiler 2 (if applicable) of the system:

Object
Object
coding addresses
boiler (if applicable) in a multi-
Vitotronic 100 GC1 of second
(Multiple boiler system)
Coding address 01:2
Coding address 07:2

Vitotronic 333 MW1
PM2
BoC
(Cascade control)
ple boiler system:
(Boiler number)
62
Boiler 3 (if applicable) of the system:
Object
Object
coding addresses
boiler (if applicable) in a multiple

Coding address 01:2 (Multiple

Vitotronic 100 GC1 of third
Coding address 07:3

PM3
BoC
(Cascade control)
(Boiler number)

boiler system)
boiler system:
Boiler 4 (if applicable) of the system

Object
Object
coding addresses
boiler (if applicable) in a multiple

Coding address 01:2 (Multiple

Vitotronic 100 GC1 of fourth
Coding address 07:4

PM4
BoC
(Cascade control)
(Boiler number)

boiler system)
boiler system:
63
Bindings between the Fault Manager of the system and all other devices:
In a Viessmann heating system, any given control unit (except for Vitotronic 050 HK1M) can be des-
ignated as fault manager. This control unit monitors all other control units in the system for failure. If a
participant drops out and its cyclical message nvoNodeAlarm is not received by the fault manager
during the Receive-Heart-Beat-Time, a fault message is generated. In addition, the compiled fault
function is activated and the “missing participant” is shown on the display. In the factory default set-
ting, the Vitotronic 200 GW1, 300 GW2, 333 MW1(S), 333 MW2 and 200 HO1 are designated as fault
managers, i.e. for these controls, coding address 79 is set to “1” as the factory default setting. The
factory default setting for all other devices is “0”, i.e. their input network variable nviNodeAlarm is not
active.
In addition to the control unit which is designated as the fault manager of the system, the Vitocom 300
(if applicable) is also automatically the fault manager. This means that all network variables
nvoNodeAlarm of all control units must also be bound to it.
Device: Setting of Network Comm. Network Device: Setting of

Object
Object
coding addresses Variable variable coding addresses
All control units of nvoNodeAlarm nviNodeAlarm Fault manager of

the system except system (can be any
Node
Node
for fault manager: control unit except
coding address 79:0 Vitotronic 050 HK1M):
coding address 79:1
All control units of nvoNodeAlarm nviNode Alarm1 Vitocom 300 (if appli-
the system except or nviNode cable)
Node
Node
Vitocom 300 Alarm2 …
depending on
system number
Participant monitoring and fault messaging takes place with the registration of the participant number.
This is why an individual participant number must be assigned at the time of toolbinding to each
device of the heating system. Contrary to the node address, this number can be determined arbitrarily
and is set in coding address 77. If there are several Viessmann heating systems in one network,
system attribution of each individual device to systems 1….5 takes places in coding address 98 via
toolbinding.
64
Binding between the Time of Day Sender and all other devices in a network:
Control units Vitotronic 200 GW1, 300 GW2, 333 MW1(S), 333 MW2 and 200 HO1 send their time
and date via nvoNodeTimeSet in the factory-default setting and via selfbinding to the entire Viess-
mann domain.
It is recommended that the time on all devices be synchronized. This means that one device must be
designated as the time of day sender – e.g. equipped with DCF77 radio receiver (Viessmann acces-
sories) – and all other devices as time of day receivers. The Vitocom 300 (if applicable) must also be
provided with the current time information.

Object
Object
coding addresses variable variable coding addresses
Time of day sender nvoNodeTime nviNodeTime All other control units in

Node
Node
(one control within Set Set the network:
the network): coding address 81:3
Coding address 7B:1
Time of day sender nvoNodeTime nviNodeTime Vitocom 300 (if applica-
Node
Node
(one control within Set Set ble)
the network):
Coding address 7B:1
Bindings between the outdoor temperature sender and the outdoor temperature receiver:
Control units Vitotronic 200 GW1, 300 GW2, 333 MW1(S) and 333 MW2 send the measured outdoor
temperature via nvoNodeOATemp subnet-wide (factory setting and selfbinding) to the heating sys-
tem. With coding address 97, this operation can be turned off, or can be activated on other control
units equipped with outdoor temperature sensor.
During toolbinding, the distribution of the outdoor temperature can be set as desired within in the
network. The distribution of the outdoor temperature within the network can be set as desired during
toolbinding. This way, groups of devices with the same outdoor temperature may be formed. Please
note that coding address 97 must be set to “2” for the outdoor temperature sender and to “1” for the
outdoor temperature receiver.

Object
Object
coding address variable variable coding address
Outdoor temperature nvoNode nviNode Outdoor temperature

Node
Node
sender: OATemp OATemp receiver:

Coding address 97:2 Coding address 97:1
65
Additional Information on Toolbinding
Exchange of communication modules
In the Viessmann selfbinding process, the binding of devices is renewed each time the power is
turned on and changes to relevant configuration parameter (coding addresses) have been made. The
processor on the electronic circuit board relays all necessary parameters, which influence the self-
binding process, to the neuron chip on the communication module.
If communication modules of the same type are exchanged in a selfbinding system, the binding is not
influenced, as all required information is retrieved from the processor of the electric circuit board when
the power is turned on.
For toolbinding, the situation is different. The binding tool writes the binding information to the neuron,
i.e. the EEPROM. The configuration parameters of the control processor no longer influence the
binding. Only the internal functions (i.e. sending/ receiving time of day information, sending/ receiving
outdoor temperature, single/ multiple boiler system, etc.) are influenced by the configuration parame-
ters.
If a communication module is exchanged in a tool-bound system, the binding within such a system
must be renewed “by tool”. If the communication module of boiler 1 in a tool-bound system is ex-
changed with that of boiler 2, boiler 1 now operates as boiler 2 and vice versa – although the display
and the configuration parameter continues to show boiler 1. Because the participant check of the
control units runs via the participant address, a reversal cannot be detected with this test. The binding
can be checked only with the binding tool.
Fault management
Selfbinding takes place during initial start-up of the heating system. Vitotronic 200 GW1, Vitotronic
300 GW2, Vitotronic 333 MW1(S), Vitotronic 333 MW2 and Vitotronic 200 HO1 control units are set
as fault managers by the factory default setting. These controls compile a participant list of all con-
nected Viessmann devices. Recognition of a Viessmann device takes place, among other things, via
the network address of the device.
If the system is subject to toolbinding at a later point - entailing a change of address - the participant
list of the fault manager must be deleted (see page 21), so as to allow the fault manager to build a
new, consistent list.
66
Additional Information
Index
Air distance and access clearance ...............13 nvoNodeRlyState ........................................ 40
Applicability Information .................................. 3 Object ........................................................... 11
Application program ........................................ 6 Operating system ............................................ 6
Binding ............................................................ 8 Participant Check........................................ 21
BoC ...............................................................60 Participant number ..................................... 17
Boiler Controller Object .................................55 PM ................................................................. 53
Boiler number ..............................................17 Product Information ......................................... 3
BUS end ........................................................13 Production Manager Object .......................... 52
Central Flow Demand Manager Object .........49 ReceiveHeartBeat-Time................................ 36
CFDM ............................................................49 Receiving time information from LON ...... 18
CFG_EXTERNAL ..........................................37 Recommended cable type ......................... 14
CFG_LOCAL .................................................37 Repeater ....................................................... 16
Coding Address .............................................18 Router .......................................................... 16
Communication module ................................23 Safety Information ........................................... 2
Configuration parameter ...............................17 Safety Instructions...................................... 13
Configuration Properties ...............................37 Selfbinding .................................................... 59
Connecting cables .........................................13 SendHeartBeat-Time .................................... 36
DHWC ...........................................................46 Sending time information .......................... 18
Domain ID ....................................................... 9 Service LED ................................................. 60
Domestic Hot Water Controller Object ..........46 Service pin message .................................. 60
Echelon .......................................................... 6 Single/ Multiple boiler system ................... 17
Free Topology ...............................................15 SNVT_alarm ................................................. 41
FTT 10-A .......................................................15 Standard network variable types ................ 7
Functional object ........................................11 Start-up ......................................................... 17
Group Address Structure ...........................10 Subnet ID ........................................................ 9
HCC...............................................................44 System fault manager................................. 17
Heating Circuit Controller Object ..................44 System number ........................................... 17
Large-scale networks ....................................16 Terminator resistor ........................................ 15
LFDM.............................................................47 Toolbinding ............................................. 21, 59
Local Flow Demand Manager Object ............47 Transceiver .................................................... 6
Logical connections ..................................... 9 Transfer medium ............................................. 6
Logical signals of the control unit ..................39 Vitotronic 050, Model HK1M ......................... 30
LON ................................................................. 6 Vitotronic 050, Model HK1S .......................... 31
LONMARK ...................................................... 6 Vitotronic 050, Model HK1W ......................... 31
LonTalk Protocol ........................................... 6 Vitotronic 050, Model HK3S .......................... 32
LONW ORKS ...................................................... 6 Vitotronic 050, Model HK3W ......................... 32
Maximum cable length ..................................13 Vitotronic 100, Model GC1 ............................ 24
Maximum Number of Nodes.......................13 Vitotronic 200, Model GW1 ........................... 25
Network variables ......................................... 8 Vitotronic 200, Model HO1 ............................ 34
Neuron chip ................................................... 6 Vitotronic 300, Model GW2 ........................... 26
Neuron ID ....................................................... 9 Vitotronic 333, Model MW1 ........................... 28
Node ID ........................................................... 9 Vitotronic 333, Model MW2 ........................... 28
Node object ...................................................11 Vitotronic 333,Model MW1S ......................... 28
Node Object ..................................................37 Wink Message ............................................. 60
Nodes ............................................................. 6 XIF files ........................................................ 60
67
Applicable Literature/ Websites
Literature
[1] LON Nutzerorganisation e.V.: LONW ORKS Installation Handbook VDE Verlag, Berlin, Offen-
bach
[2] Tiersch, F.: LONW ORKS Technology – A Challenge and a Chance, DESOTRON
Verlagsgesellschaft Dr. Günter Hartmann & Partner GbR, Erfurt, 1998
Websites
LONMARK Interoperability Association:www.lonmark.org
Echelon Corporation:www.echelon.com
68

Nr2 Lon Handbook

Uploaded by

Copyright:

Available Formats

Nr2 Lon Handbook

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nr2 Lon Handbook

Uploaded by

Copyright:

Available Formats

LON Handbook

Vitotronic 050, Model HK1M

For wall-mounted and gas-fired

Vitotronic 200, Model HO1

Licensed professional Power supply Service

When opening the control

Vitotronic 050, Model HK1M

Vitotronic 100, Model GC1

Vitotronic 333, Model MW1

Vitotronic 200, Model H01

Communication module For use with:

General Information ................................................................................................. 2

Physical Network Structuring ............................................................................... 13

Start-up of LON Network with Viessmann Controls ............................................ 17

Overview: Functional Objects of Devices ............................................................ 23

Description of Functional Objects ........................................................................ 36

Information for Logical Binding ............................................................................ 59

Additional Information ........................................................................................... 67

Fundamentals of the LON Network

What does “LON” mean?

Network Variable Concept

Network Variables Communication

Addressing and Logical Network Structuring

LON Network Comparison:

• Defective nodes can be replaced more easily.

• Data messaging is shorter than when the neuron ID is used.

Group Address Structure

General Illustration of an Object

Maximum Number of Nodes

BUS or Line Topologies

Networks with a FTT 10-A receiver can be composed of different topologies.

For networks with BUS or line topologies

For networks with FTT 10-A, the

Recommended cable Total maximum

For communication, wires 1 and 2, as well as shielding are required.

Free Topology Ring Topology

Recommended cable Max. distance Max. cable

1. Installation and Connection

Vitotronic 100 GC1:

CA Description: Function Value Adjustment necessary?

CA Description: Function Value Adjustment necessary?

CA Description: Function Value Adjustment necessary?

CA Description: Function Value Adjustment necessary?

Participant list in fault manager has to be current

1. Press and OK simultaneously Participant Check is activated.

Serial List Number

2. Select desired Participant with +

3. Activate Check with OK . "Check“ is flashing in display until

5. Press and OK Participant Check is finished.

5. Configuration for the Heating System

Viessmann control units require two different types of communication modules:

Communication module For use with:

(continued on following page)

(continued on following page)

(continued on following page)

(continued on following page)

Configuration Parameter (configuration properties) of the node object:

Name SNVT Type Description RcvHrt

Name SNVT Type Description RcvHrt

Name SNVT Type Description SndHrt