Autronica AutroSafe BSD-340 User Manual

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 7
3. A detector has restarted, in which case it opens its loop switch and sends a Restart
message
Due to the electric properties and signalling type of the PowerLoop, the only way BSD-340 can
investigate and repair such problems is to power down the loop and raise it again. This is very
different from AL_Com loops, where AutroSafe can do all sorts of “troubleshooting” while the
loop is in normal operation. The AutroSafe will indicate ‘loop disabled’ during any loop raises
initiated by the system after a fault is detected.
2.2.3 Loop wiring
Due to the high current consumed by the loop units on a PowerLoop, it is vital that the wiring
length is checked with the PowerLoop Calculator in the Autrosafe Configuration Tool. This tool
ensures that the power loss in the cables does not exceed the operational parameters of the loop.
The system is designed to have BSD_340 PowerLoop Drivers distributed around the site, using
AutroFieldBus communication (maximum 1000+ meters cable length). BSD-340 PowerLoop
Drivers should be located as close to the connected loop as possible to reduce cable length.
Because of radio communication, whenever more than one BSD-340 is mounted together in a
cabinet, and loops are wired together, the system is more likely to have crosstalk issues (see
chapter 2.4).
2.3 Loop handling
2.3.1 Reporting topology to AutroSafe
During AutroSafe INIT the PowerLoop handling goes like this:
• Phase 1 of AutroSafe INIT: BSD-340 power-up/close-switch raise of its PowerLoop. This
takes approx. 50 seconds for a 15-unit loop.
Note! The BSD-340 knows how many detectors there are on the loop (see chapter 2.2.2
above). This means that after commissioning procedure has been run loop-by-loop, later
INITs will have much greater chance to succeed even with a lot of crosstalk.
• Phase 2 of AutroSafe INIT: BSD-340 reports the PowerLoop to the panel.
Note! If there are any missing detectors on the loop, the BSD-340 will first report the whole loop
topology to the panel. Next, the BSD-340 will report the missing detector. Timing between these
two reports is so short that the operator will immediately get the report of a missing detector on
the loop.
• Phase 3 AutroSafe INIT: When AutroSafe sends parameters to detectors, BSD-340 is
transparent to these messages.
2.3.2 Loop handling / RESET
As described in chapter 2.2.2, BSD-340 must use loop raise to evaluate and/or fix fault situations.
If BSD-340 detects a loop problem, it sends a RESTART message for itself to AutroSafe. AutroSafe
then executes general LoopDriver handling, which is:
1. Send a message to BSD-340 to power down the loop.
The loop is marked Disabled in the panel.
A disabled loop is not polled.
2. Send a message to BSD-340 to power up the loop.
At this point, BSD-340 does the power-up/close-switch sequence (see chapter 2.3.1).
When finished, it sends an “answer” to the power command back to AutroSafe.

Autronica AutroSafe BSD-340 Specifications

General

Brand	Autronica
Model	AutroSafe BSD-340
Category	Measuring Instruments
Language	English

Summary

1. Preface

1.1 PRODUCT WARNINGS

Important safety warnings for product installation and operation.

1.2 WARRANTY DISCLAIMERS

Legal disclaimers regarding product warranties and representations.

1.3 Target audience

1.4 Changes

1.4.1 Stored loop topology

Explains saving loop topology to EEPROM for control and identification.

1.4.2 New fault message: "Memory fault"

Details a new fault message related to topology saving or EEPROM corruption.

1.4.3 Other changes

Lists other software improvements in version 1.1.0, affecting loop handling.

1.5 Safety

1.6 Compatibility

1.6.1 AutroSafe IFG

Specifies software version compatibility between BSD-340 and AutroSafe IFG.

1.6.2 Loop units

Lists compatible loop unit software versions for BSD-340.

1.7 Tools

2. PowerLoop – how it works

2.1 Powerloops versus normal detector loops

Compares PowerLoop functionality with standard detector loops.

2.2 PowerLoop

Details the PowerLoop system, its electrical properties, and software handling.

2.2.1 Electric properties

Details the electrical specifications of the PowerLoop system.

2.2.2 Software handling

Explains the "raising" process for a PowerLoop and special cases.

2.2.3 Loop wiring

Discusses the importance of loop wiring and cable length for PowerLoops.

2.3 Loop handling

Describes loop handling procedures including topology reporting and reset.

2.3.1 Reporting topology to AutroSafe

Describes how the BSD-340 reports loop topology during AutroSafe INIT.

2.3.2 Loop handling / RESET

Explains the process of loop handling and reset for fault resolution.

2.3.3 Loop Polling

Details how AutroSafe polls detectors to ensure they are active.

2.4 Crosstalk

Defines crosstalk and its impact on PowerLoop communication.

2.4.1 Possible crosstalk issues

Lists potential problems arising from crosstalk events.

2.4.2 Crosstalk countermeasures

Outlines methods to mitigate crosstalk issues in PowerLoop systems.

2.5 Duplicate messages

Explains how duplicate messages are handled and their potential impact.

3. Upgrading BSD-340 PowerLoop Drivers

3.1 Before you start

Pre-upgrade steps, including downloading files and checking system numbers.

3.2 Label the BSD-340 board to identify the SW version

Instruction on labeling the board with the target SW version for upgrade.

3.3 Connect PC to loop driver

Guide for physically connecting a PC to the BSD-340 service port.

3.4 Start IFG Service tool and connect to loop driver

Steps to launch and establish a connection using the IFG Service Tool.

3.5 Disable loop

Instruction to disable the loop on the Autrosafe panel before upgrade.

3.6 Download software to BSD-340

Detailed steps for downloading EEProm and Application files to the BSD-340.

3.7 Raise loop and store topology in loop driver

Procedures for raising the loop and saving its topology to EEPROM.

4. Service operations

4.1 Delete and save topology

Procedures for deleting and saving loop topology.

4.1.1 Delete topology

Methods for deleting existing loop topology from the driver.

4.1.2 Save topology

Procedures for saving a new loop topology.

4.2 Replace PowerLoop driver (BSD-340)

Procedures for replacing the BSD-340 PowerLoop driver.

4.2.1 Without PC and IFG service tool

Steps to replace the BSD-340 driver without using PC software.

4.2.2 With PC and IFG service tool

Steps to replace the BSD-340 driver using the IFG Service Tool.

4.3 Replace loop unit

Procedures for replacing a loop unit.

4.3.1 Without PC and IFG service tool

Instructions for replacing a loop unit without PC software.

4.3.2 With PC and IFG service tool

Instructions for replacing a loop unit using the IFG Service Tool.

5. Commissioning operations

5.1 Useful commands

Lists and describes essential commands for commissioning.

5.2 Establish AutroFieldBus communication

Procedure to establish communication on the AutroFieldBus.

5.3 De-conflict systems

Procedures for de-conflicting systems and PowerLoops.

5.3.1 Changing system number

How to change system numbers to avoid conflicts between PowerLoops.

5.4 Crosstalk

Details on crosstalk detection, management, and analysis.

5.4.1 +40 setting

Explains the purpose of the +40 setting for crosstalk management.

5.4.2 Discover crosstalk

Method to detect and identify crosstalk issues.

5.4.3 Crosstalk map

Visual representation of crosstalk detected between loops.

5.4.4 List crosstalk statistics

Command to display statistics for crosstalk on a specific loop driver.

5.4.5 PowerLoop statistics (#PL_Stat)

Command to display internal statistics of the PowerLoop driver.

5.5 Serial numbers for verification (Recommended)

Using serial numbers and topology listing for verification.

6. External protocols

7. IFG service tool- user interface

8. Troubleshooting

8.1 Open loop and short circuit on the same loop may end up in infinite disable/enable

Troubleshooting steps for simultaneous open loop and short circuit issues.

8.2 Parameter fault on loop unit

How to resolve parameter faults on loop units.

8.3 Enable loop without saved topology

Warning against enabling loops without saved topology due to potential issues.

8.4 Memory fault after initialization

Causes and resolution for memory faults after initialization.

8.5 Open loop after initialization

Troubleshooting open loop issues that occur after initialization.