Siemens LMV5 Quick Start Manual page 205
Hide thumbs
Also See for LMV5:
- Technical instructions (374 pages) ,
- Basic documentation (278 pages) ,
- Manual (39 pages)
Advertisement
Starting adaption via Modbus
Updating rate of AZL5
Fast
Medium
Slow
Constant
Upon reset
Error handling
Error codes
LMV5 QSG Rev 4
The routine used for identifying the path in the integrated load controller (termed "adaption"
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 (adaption)) in
the Basic Documentation of the LMV5... system (P7550).
The terms Start adaption, Adaption active / inactive and Adaption state indicate the respec-
tive 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.
System data that have already been updated automatically by the system process are
available on request, at a typical repetition rate of 200 ms.
These data are cyclically queried in the system by the AZL... The typical updating rate here
is 5 seconds, depending on system load.
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.
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.
Same as constant data, but these data can be changed in the system.
When there are faulty telegrams (CRC errors, etc.), the AZL... does not send any exception
code. It does not respond to this kind of message.
Reason: Usually, the commercially available Modbus drivers do not respond to exception
codes.
Sec 8 Pg 11
www.scccombustion.com
Advertisement
