BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 10
Note! Regarding timeslots and retransmissions: There are some situations where
responses must occur within fixed time limits, where crosstalk may slow things down to a
point where faults occur. (1) Loop Raise, where BSD-340 waits for a few seconds for
RESTART messages. Failure to meet a time requirement here may cause Loop-Break fault,
and if that happens from both A and B side, one or more detectors may be “lost” from the
loop. (2) Parameter setting from AutroSafe, which is used during INIT/Enable phase 3;
AutroSafe has a hard timeout of 6 seconds waiting for an answer.
Failure to meet a time requirement causes a Parameter fault. (3) Command from
AutroSafe, typically setting up subscription to analogue values. Slow response causes a
Point-Not-Responding fault. In these situations, the software is not able to adjust for
crosstalk, and loop wiring must be reconsidered (see chapter 2.4).
2.5 Duplicate messages
All messages on the PowerLoop are sent with ACK (acknowledgement), which means that the
receiver must send an ACK message back to the sender. If the sender does not recieve the ACK
within a time limit, it will re-send the message. If for some reason the ACK is lost, this could be a
problem for some messages from detectors to BSD-340/AutroSafe.
- A RESTART duplicate during loop raise is handled as a branch
- A Parameter ANSWER duplicate confuses AutroSafe’s parameter sending, it expects one
answer and gets another, so it terminates parameter handling for that detector.
The BSD-340 sw version 1.1.0, or later, has an elaborate duplicate handling, with more RESTART
situations and all parameter handling during INIT.
3. Upgrading BSD-340 PowerLoop Drivers
3.1 Before you start
Download etvc files from the Product Web.
Note! Check offset before upgrade (Refer to chapter 0). Check the configuration for system
number (offset) or, on a running system type #SetSysNo0. in the IFG Service tool when
connected to the BSD-340 loop driver. Terminal will either return old system number or
nothing (nothing = system number 0). Note this for later use if it is different from 0 as you will
have to set it manually later. All loop drivers on the same AutroFieldBus will have the same
System ID.
Note! Ensure that all loop devices have been upgraded to the 2009 version of the software.
This can be checked by means of an older version of IFG Service tool. Without the latest
software (2009 revision) in the loop devices (detectors) the end result will not be optimal!
To Next Page
Loading...
Need help?
General
