BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 20
5.4.3 Crosstalk map
This map is developed based on “Crosstalk detected” faults, crosstalk statistics and #PL_Stat from
all PowerLoop drivers.
5.4.4 List crosstalk statistics
#printcross command will show statistics for crosstalk seen from one PoweLoop driver. Each
PoweLoop driver has to be checked.
This is measured over 900 minutes. Although crosstalk between “My LoopID=15” and
“LoopID=16” is high it is not a severe problem since it is between two loops. If there were high
crosstalk numbers with three or more loops involved, cabling had to be checked.
5.4.5 PowerLoop statistics (#PL_Stat)
#PL_Stat will show a printout like this:
5.4.5-1 Frame err: 405 = 1029 (measured over approx. 15 hours)
Notice: Numbers are presented in hexadecimal values and can easily be translated to decimal
values using Windows` built in calculator in programmer’s mode (Due to limitations in in BSD-340
internal memory no conversion to decimal numbers is available).
Frame errors may be a reference to crosstalk (source not defined) seen as noise. Some noise is
normal, even within own loop – especially in loop raise. The example above is measured over
about 900 minutes, which in average is just above one frame error per minute - frame error rate is
To Next Page
Loading...
Need help?
General
