Lufft 8511.EAK, Руководство по эксплуатации

Страница: 22 / 158

o
Avg:
the average value over all values in the “reporting interval” is
calculated
o
Sum: the sum
value over all values in the “reporting interval” is
calculated
o
Min:
the minimum value over all values in the “reporting interval” is
calculated
o
Max:
the maximum value over all values in the “reporting interval” is
calculated
o
Mod: the modal value (i.e. the value most often appearing in the
interval, for coded values like road condition or precipitation type) over
all values in the “reporting interval” is calculated
o
Vect:
the vectorial average value over all values in the “reporting
interval” is calculated
o
Last value:
the last value in the “reporting interval”
Note: The TLS channel configuration MUST be unique, e.g. the same channel
must not be assigned more than once. This is independent of the active/inactive
status of a sensor channel!
Each channel with a valid TLS configuration (FG, type and channel != 0) is treated as
“configured for TLS”, even if the channel is disabled (a channel can also be
enabled/disabled via TLS protocol).
The TLS types supported by LCom for sensor data are listed in Appendix:
Supported TLS DE Data Types . TLS FG, type and channel must be set to 0 if a
sensor value should be read by the UMB device but not reported via TLS.
So if you want to assign a different UMB sensor channel to a certain TLS
channel/type, it is not sufficient to configure the “old” UMB sensor channel as
inactive; rather the “old” UMB sensor channel must then be configured with TLS
FG=0, Type=0 und Channel=0 (and hence no longer as “valid TLS sensor”) before
you can assign the same TLS channel to a different UMB sensor channel.
Note for TLS FG6:
From LCom Version 1.3.9 on, LCom supports
– besides the door contact (type
48) and the “extended power supply” status (type 151) the following DE Types
as well: