Siemens Display Unit Azl 52 00 b1 For LMV
Siemens Display Unit Azl 52 00 b1 For LMV
Siemens Display Unit Azl 52 00 b1 For LMV
Modbus
User Documentation
CC1A7550en
Building Technologies Division
10.12.2015
Supplementary documentation
Type of product Type of documentation No. of documentation
LMV5... User Documentation A7550.1
Basic diagram for LMV5... with 2 types of gases
LMV5... User Documentation A7550.3
Basic diagram for LMV5... with 2 types of liquefied fuels
LMV5... User Documentation A7550.4
Assembly of VKF41...C gas damper with ASK33.4 mounting
kit to the SQM45.295A9 actuator
LMV52... User Documentation A7550.5
COx supervision and control
LMV5... Setting Lists (parameter and error list) I7550
ACS450 Operating Instructions J7550
LMV5… Installation Basics J7550.1
LMV5... Data Sheet N7550
LMV5... Basic Documentation P7550
LMV5... Product Range Overview Q7550
This document contains a complete overview
AZL52 / LMV51 Operating Instructions U7550
AZL52 / LMV51 Operating Instructions U7550.1
AZL52 / LMV52 Operating Instructions U7550.2
AZL52 / LMV52 Operating Instructions U7550.3
AZL52 / LMV50 Operating Instructions U7550.4
AZL52 / LMV50 Operating Instructions U7550.5
SQM45 / SQM48 Data Sheet N7814
SQM9... Data Sheet N7818
QGO20... Data Sheet N7842
QGO20 Basic Documentation P7842
2/24
3/24
AZL... The burner management system is operated and programmed with the help of the
AZL5... display and operating unit or a PC tool.
The Modbus functionality of the AZL... display and operating unit serves for integrating
the LMV5... burner management system into a Modbus-based data network.
This makes possible the following applications:
Master-slave principle
4/24
Data structure Slave address Function code Data field Checksum CRC16
1 byte 1 byte x byte 2 bytes
Checksum (CRC16)
The checksum (CRC16) is used to detect transmission errors. If, during evaluation, an
error is detected, the relevant device will not respond.
Note!
The low-byte of the checksum is transmitted first.
0B 03 00 06 00 02 A0 24
CRC16
0B 03 04 00 00 42 C8 61 05
Word 1 Word 2 CRC16
5/24
Communication process
Start and end of a data block are characterized by transmission pauses. The maximum
permissible time between 2 successive characters is 3.5 times the time required for the
transmission of once character.
The character transmission time is dependent on the Baud rate and the data format
used.
Having a data format of 8 data bits, no parity bit and one stop, the character transmis-
sion time is calculated as follows:
Reply of slave
Transmission time = n characters * 1000 * x bits / Baud rate
Example Marking for data query or end of reply with data format 10 / 9 bits
6/24
Slave Reply
7550z08e/0703 t0 t1 t0 t2
where:
t0 Marking for end = 3.5 characters (time is dependent on the Baud rate)
t1 This time is dependent on internal handling; the maximum handling time is de-
pendent on the data type (internal and external data) and on the number of data;
for more detailed information, see below!
t2 t2 20 ms
This time is required by the device to switch from transmitting back to receiving;
this time must be observed by the master before a new data query is made; it
must always be observed, even if a new data query to some other device is made
Number of messages
The number of addresses per message are limited:
20 addresses of the size of one word when reading
6 addresses of the size of one word when writing
Note!
These periods of time are defined from the complete writing of the message from the
master to sending the first byte by the AZL...
1 address 25...75 ms
2...3 addresses 75...125 ms
4...5 addresses 125...175 ms
6 addresses 175...225 ms
7/24
8/24
9/24
Function Address Number Data designation Ac- Data type / Range Updating
of cess coding rate
words
03/04 37 1 Outputs R U16 - Medium
Function Address Number Data designation Access Data Data type / Range Updating
of format coding rate
words
R 03/04 38 1 Program stop R/W* U16 0=deactivated 0...7 Slow
W 06/16 1=24 PrePurgP
2=32 PrePFGR
3=36 IgnitPos
4=44 Interv 1
5=52 Interv 2
6=72 PostPPos
7=76 PostPFGR
R 03/04 39 1 Operating mode with load controller R/W* U16 0=ExtLC X5-03 0…5 Slow
W 06/16 1=IntLC
2=IntLC Bus
3=IntLC X62
4=ExtLC X62
5=ExtLC Bus
R 03/04 40 1 Selection of manual or automatic operation R U16 0=automatic 0…2 Fast
1= Manual
2=burner off
R 03/04 41 1 Modbus mode: Local / Remote R/W U16 0 = Local 0…1 Slow
W 06/16 1 = Remote
10/24
11/24
12/24
* These parameters need not be continually written since they are stored in EEPROM,
which only permits a limited number of write accesses over its lifecycle (< 100,000)
Data structures
Date U16 Year
Month
Day
13/24
Note:
In the AZL..., this data type is also used to
mark an invalid or non-available value by
using the value of «-1»
[] Data array
Data types
14/24
The routine used for identifying the path in the integrated load controller (termed “adap-
tion“ here) of the LMV5... system can be controlled and monitored via Modbus.
In principle, the general conditions are the same as those used when making adaptions
with the AZL52... (refer to subsection 6.4.2 Self-setting of control parameters (adap-
tion)) in the Basic Documentation of the LMV5... system (P7550).
The terms Start adaption, Adaption active / inactive and Adaption state indicate the
respective Modbus addresses (refer to ”Table of addresses”).
Start the adaption via Start adaption and change the value from 1 to = 1.
Starting the adaption has no impact on adaption processes already under way
(Adaption active / inactive = 1).
If Adaption active / inactive = 1, the process can be monitored via Adaption state (refer
to data type PT_ADAPTION).
When Adaption active / inactive = 0, the adaption process is completed.
On completion of the process, the result can be read out via Adaption state.
To complete the adaption process prematurely, the value at Start adaption must be
changed from 2 to = 2.
15/24
Medium These data are cyclically queried in the system by the AZL... The typical updating rate
here is 5 seconds, depending on system load.
Slow These data are cyclically queried in the system by the AZL... The typical updating rate
that can be expected here is 25 seconds, depending on system load.
Constant These data are updated in the system by the AZL5... upon each Power On or reset.
When making a query, the updated data will be available after 25 seconds.
Data that cannot be changed (e.g. the production date, etc.) – neither with the AZL5...
nor via the ACS450 – can be identified by the value of 0 in the first Byte of the strings.
Upon reset Same as constant data, but these data can be changed in the system.
16/24
Reason: Usually, the commercially available Modbus drivers do not respond to excep-
tion codes.
17/24
Having made the selection, the menu item can be quit via ESC. The setting is retained
until «Operation» «OptgModeSelect» «GatewayBASoff» is selected via the
AZL… menu.
When «GatewayBASon» is activated, plant operation and diagnostics via the AZL... are
still possible.
Slave address
Transmission parameters
When there is no Modbus communication, this timeout defines the period of time on
completion of which the AZL… changes automatically from Remote to Local.
This setting defines whether the AZL… shall work in Local or Remote mode.
Remote mode
18/24
General
The AZL... serves the Modbus via its COM2 port (8-pole Western jack RJ45). The port
is assigned to the functional low-voltage range.
Attention!
When preparing and fitting a connecting cable between the AZL... and a con-
verter, it is to be noted that PIN 5 and PIN 7 can deliver a current of 5 mA each.
Adequate insulation against other potentials must be ensured.
The maximum permissible data line length between COM2 and a converter is 3 m. In
exceptional cases, this data line length can be exceeded, depending on environmental
conditions (electrical interference) and the type of cable used – without Siemens as-
suming responsibility.
Attention!
To ensure protection against electric shock hazard, it must be made certain that
AC 230 V / AC 120 V lines are strictly separated from the functional low-voltage
area.
PIN PIN
2 CAN L COM 2 1 TXD
CAN
3 GND 3 RXD
8 7
4 VAC 2 9 6
8 1
4, 6 GND
5 1
7 CAN H 4 3 2
5 U1
8 VAC 1 7 U2
X70 X72
COM 1
COM1 X71
PIN 6
7 8
9 X71
7550z09/0703
1 5
2 RXD 2 3 4
3 TXD
5 GND
Note!
COM1 (PC port) and COM2 cannot be active at the same time!
19/24
Technical requirements
The technical specification provided by the suppliers of the converters must be ob-
served when doing planning work. Some of them do not meet the specifications of the
LMV5... system (e.g. operating temperatures). If required, technical measures must be
taken (e.g. suitable location).
The following types of converters have been tested by us with respect to function and
immunity (voltage surges):
20/24
Hedin Tex
AZL COM2 Cable interface converter
8-pole Western X1 RS-232
H4 M4
1 TxD 21 2
2 __ __ __
3 RxD 22 3
4 GND 16 7
5 U1 (only for eBus adapter)
6 GND __ __
21/24
7550d37e/0116
Predefined setpoint W3 (IntLC bus)
Preset load (ExtLC bus)
AZL... via AZL
LC_OptgMode (IntLC bus / ExtLC bus)
or via Modbus parameter 39
2 = IntLC bus
5 = ExtLC bus
Manual (1)
Timeout behavior
Timeout Modbus parameter 42
(save location: EEPROM AZL)
Modbus parameter 47
(save location: EEPROM LR) W1
Modbus parameter 39
5 = ExtLC bus
Remote
Manual (1)
Modbus parameter 45
Preset
(save location: RAM AZL...)
load W3
Modbus parameter 39
5 = Ext LR Bus
22/24
Modbus downtime
When there is no more communication between DDC and AZL..., the Modbus down-
time is used to switch over from Remote mode to the preselected setpoint in Local
mode. The timer will be activated when changing from Local to Remote. With every
permissible Modbus communication to this slave (AZL...), the timer will be reloaded.
Should the timer lapse, the DDC must again set the Remote mode, if required. The
timer value will be retained in EEPROM and will also be retained after power off.
Note!
23/24
Note!
An AZL… reset will be triggered when switching power on, or in the event of severe
system errors.
2015 Siemens AG Building Technologies Division, Berliner Ring 23, D-76437 Rastatt
24/24 Subject to change!