Autronica AutroSafe BSD-340 User manual

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18
Power Loop Driver BSD-340, SW version 1.1.0 or later
User Guide
Power Loop Driver BSD-340
SW version 1.1.0 or later
AutroSafe Interactive Fire Detection System

COPYRIGHT ©
This publication, or parts thereof, may
not be reproduced in any form, by any
method, for any purpose.
Autronica Fire and Security AS and its
subsidiaries assume no responsibility
for any errors that may appear in the
publication, or for damages arising from
the information in it. No information in
this publication should be regarded as a
warranty made by Autronica Fire and
Security AS. The information in this
publication may be updated without
notice.
Product names mentioned in this
publication may be trademarks. They
are used only for identification.
E-1676
This product contains static-sensitive devices. Avoid any electrostatic discharge.
The WEEE Directive
When the marking below is shown on the
product and/or its literature, it means that
the product should not be disposed with
other household wastes at the end of its
life cycle. During waste treatment, disposal
and collection, please separate the
product from other types of wastes and
recycle it responsibly to promote the
sustainable reuse of material resources.
This product should not be mixed with
other commercial wastes for disposal.

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 1
Table of Contents
1. Preface........................................................................................................................................... 3
1.1 PRODUCT WARNINGS......................................................................................................... 3
1.2 WARRANTY DISCLAIMERS................................................................................................... 3
1.3 Target audience .................................................................................................................. 4
1.4 Changes............................................................................................................................... 4
1.4.1 Stored loop topology................................................................................................ 4
1.4.2 New fault message: “Memory fault”........................................................................ 4
1.4.3 Other changes........................................................................................................... 4
1.5 Safety .................................................................................................................................. 5
1.6 Compatibility....................................................................................................................... 5
1.6.1 AutroSafe IFG............................................................................................................ 5
1.6.2 Loop units ................................................................................................................. 5
1.7 Tools.................................................................................................................................... 5
2. PowerLoop –how it works............................................................................................................ 6
2.1 Powerloops versus normal detector loops......................................................................... 6
2.2 PowerLoop.......................................................................................................................... 6
2.2.1 Electric properties..................................................................................................... 6
2.2.2 Software handling..................................................................................................... 6
2.2.3 Loop wiring ............................................................................................................... 7
2.3 Loop handling...................................................................................................................... 7
2.3.1 Reporting topology to AutroSafe.............................................................................. 7
2.3.2 Loop handling / RESET .............................................................................................. 7
2.3.3 Loop Polling .............................................................................................................. 8
2.4 Crosstalk.............................................................................................................................. 8
2.4.1 Possible crosstalk issues ........................................................................................... 8
2.4.2 Crosstalk countermeasures ...................................................................................... 9
2.5 Duplicate messages........................................................................................................... 10
3. Upgrading BSD-340 PowerLoop Drivers...................................................................................... 10
3.1 Before you start ................................................................................................................ 10
3.2 Label the BSD-340 board to identify the SW version ....................................................... 11
3.3 Connect PC to loop driver................................................................................................. 11
3.4 Start IFG Service tool and connect to loop driver............................................................. 11
3.5 Disable loop ...................................................................................................................... 12
3.6 Download software to BSD-340........................................................................................ 12
3.7 Raise loop and store topology in loop driver.................................................................... 13
4. Service operations....................................................................................................................... 14
4.1 Delete and save topology ................................................................................................. 14
4.1.1 Delete topology ...................................................................................................... 14

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 2
4.1.2 Save topology ......................................................................................................... 14
4.2 Replace PowerLoop driver (BSD-340)............................................................................... 15
4.2.1 Without PC and IFG service tool............................................................................. 15
4.2.2 With PC and IFG service tool................................................................................... 15
4.3 Replace loop unit .............................................................................................................. 15
4.3.1 Without PC and IFG service tool............................................................................. 15
4.3.2 With PC and IFG service tool .................................................................................. 16
5. Commissioning operations.......................................................................................................... 16
5.1 Useful commands ............................................................................................................. 16
5.2 Establish AutroFieldBus communication .......................................................................... 17
5.3 De-conflict systems........................................................................................................... 18
5.3.1 Changing system number ....................................................................................... 19
5.4 Crosstalk............................................................................................................................ 19
5.4.1 +40 setting .............................................................................................................. 19
5.4.2 Discover crosstalk................................................................................................... 19
5.4.3 Crosstalk map ......................................................................................................... 20
5.4.4 List crosstalk statistics............................................................................................. 20
5.4.5 PowerLoop statistics (#PL_Stat) ............................................................................. 20
5.5 Serial numbers for verification (Recommended).............................................................. 21
6. External protocols ....................................................................................................................... 22
7. IFG service tool- user interface ................................................................................................... 23
8. Troubleshooting .......................................................................................................................... 24
8.1 Open loop and short circuit on the same loop may end up in infinite disable/enable.... 24
8.2 Parameter fault on loop unit ............................................................................................ 24
8.3 Enable loop without saved topology ................................................................................ 24
8.4 Memory fault after initialization....................................................................................... 24
8.5 Open loop after initialization............................................................................................ 24

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 3
1. Preface
1.1 PRODUCT WARNINGS
THESE PRODUCTS ARE INTENDED FOR SALE TO, AND INSTALLATION BY,
AN EXPERIENCED PROFESSIONAL. AUTRONICA FIRE AND SECURITY
CANNOT PROVIDE ANY ASSURANCE THAT ANY PERSONOR ENTITY BUYING
ITS PRODUCTS, INCLUDING ANY “AUTHORIZED DEALER”, IS PROPERLY
TRAINED OR EXPERIENCED TO CORRECTLY INSTALL FIRE RELATED
PRODUCTS.
A PROPERLY INSTALLED AND MAINTAINED PRODUCT/SYSTEM MAY ONLY
REDUCE THE RISK OF EVENTS SUCH AS FIRE, SMOKE, FLOOD; IT IS NOT
INSURANCE OR A GUARANTEE THAT SUCH EVENTS WILL NOT OCCUR,
THAT ADEQUATE WARNING OR PROTECTION WILL BE PROVIDED, OR THAT
THERE WILL BE NO DEATH, PERSONAL INJURY, AND/OR PROPERTY
DAMAGE AS A RESULT.
AUTRONICA FIRE AND SECURITY
BATTERY OPERATED SENSORS, DETECTORS, KEYFOBS, PANIC DEVICES
AND OTHER PANEL ACCESSORIES HAVE A LIMITED BATTERY LIFE. WHILE
THESE PRODUCTS ARE DESIGNED TO PROVIDE SOME WARNING OF
IMMINENT BATTERY DEPLETION THE ABILITY TO DELIVER SUCH WARNINGS
IS LIMITED AND SUCH WARNINGS MAY NOT BE PROVIDED IN ALL
CIRCUMSTANCES. PERIODIC TESTING OF THE SYSTEM IN ACCORANCE
WITH THE INSTRUCTIONS PROVIDED IN THE USER MANUAL IS THE ONLY
WAY TO ENSURE ALL SENSORS, DETECTORS, KEYFOBS, PANIC DEVICES
AND OTHER PANEL ACCESSORIES ARE FUNCTIONING PROPERLY.
1.2 WARRANTY DISCLAIMERS
TO THE MAXIMUM EXTENT PERMITTED BY LAW, AUTRONICA FIRE AND
SECURITY HEREBY DISCLAIMS ALL WARRANTIES AND REPRESENTATIONS,
WHETHER EXPRESS, IMPLIED, STATUTORY OR OTHERWISE INCLUDING
(BUT NOT LIMITED TO) ANY WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE WITH RESPECT TO ITS PRODUCTS
AND RELATED SOFTWARE. AUTRONICA FIRE AND SECURITY FURTHER
DISCLAIMS ANY OTHER IMPLIED WARRANTY OF MERCHANTABILITY OR
FITNESS.
AUTRONICA FIRE AND SECURITY MAKES NO REPRESENTATION,
WARRANTY, COVENANT OR PROMISE THAT ITS PRODUCTS AND/OR
RELATED SOFTWARE (I) WILL NOT BE HACKED, COMPROMISED AND/OR
CIRCUMVENTED; (II) WILL PREVENT, OR PROVIDE ADEQUATE WARNING OR

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 4
PROTECTION FROM, FIRE , SMOKE, FLOOD; OR (III) WILL WORK PROPERLY
IN ALL ENVIRONMENTS AND APPLICATIONS.
1.3 Target audience
This user guide is intended for use by experienced professionals with extensive knowledge about
the AutroSafe IFG solution and PowerLoop Drivers.
1.4 Changes
Software version 1.1.0 for BSD-340 improves safety and fault handling by introducing several new
features.
1.4.1 Stored loop topology
Loop topology must be saved to the EEPROM during commissioning of the loop. Saving the loop
topology to the EEPROM improves control of the loop content, i.e. unit type w/serial number and
LSI (Loop Sequence Index).
1.4.2 New fault message: “Memory fault”
A fault message will be reported in the AutroSafe IFG system in the
•Loop topology is not saved
•Loop is changed
•Content in EEPROM is corrupted
The fault message will have two different data types depending on the fault reason:
•Data field 32: Topology missing (missing device, new device, loop break etc)
or
•Data field 16: corrupted content
1.4.3 Other changes
In an operational system the BSD-340 will raise the loop automatically in the following situations:
•First loop break
•Short-circuit
•Restart message from a loop unit
During loop raise the loop will be indicated as disabled on the AutroSafe Panel.
Loops will no longer be raised on reset. Any break or short will be present until next manual
disable/enable, or any restart on loop is detected.
Automatic disable/enable not followed by any fault message is an indication of intermittent cable
problems on the loop. Wirings should be checked.
In an open loop situation, a second loop break (multiple loop breaks) will not be reported as a
loop break, but by loop units not responding.

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 5
1.5 Safety
“Memory fault”is a warning meaning that the loop is not running normally. The actual loop must
be checked and verified for correct cabling and content.
1.6 Compatibility
1.6.1 AutroSafe IFG
BSD-340 PowerLoop Driver software version 1.1.0 is only compatible with AutroSafe software
version 4.3.1 or later.
If your installation uses subscription of analog values from BN-342 or HC-300, using AutroSafe
4.8.1 or newer will give the best PowerLoop crosstalk performance. Using older AutroSafe
versions will work correctly, but the PowerLoop data traffic is higher.
1.6.2 Loop units
BSD-340 PowerLoop Driver software version 1.1.0 is only compatible with loop unit software as
listed below:
•BSD-340 Version 1.0.7.0 or later
•BN-342 Version 1.4 or later
•X33 Version 1.5 or later
•HC300 Version 1.2 or later
All loop units delivered since 2009 have the latest software version. The above software versions
are available in:
•PowerloopUpgradeTool_3_8
•IFG_UpgradeTool_3_8
1.7 Tools
•PC with serial port (or USB to serial converter)
•Serial cable male and female 9 pin D-Sub
•IFG Service Tool (PC application - see chapter 7)
•BSD-340 upgrade files (available to download from the Autronica Product Web).

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 6
2. PowerLoop –how it works.
NOTE: This chapter is intended for experienced professionals with knowledge about AutroSafe,
AL_Com, loops and LoopDrivers. Please refer to the following documentation for more
information:
•System Design and Engineering- 116-P-SYSDEENGIN-IFG/XGB
•System Description - 116-P-ASAFE-SYSTEMD/EGB)
2.1 Powerloops versus normal detector loops
PowerLoop was designed as part of the «Integrated Fire and Gas» functionality for AutroSafe. The
BSD-340 PowerLoop Driver communicates with Powerloop units through AL_Com, the same way
regular loop drivers (BSD_310) communicate with regular loop units. However, unlike the BSD-
310 Loop Driver, the BSD-340 PowerLoop driver handles the loop locally, and reports to the
system operator without involving AutroSafe’s loop handling module.
2.2 PowerLoop
2.2.1 Electric properties
The PowerLoop, is a two-wire loop that can distribute power to gas detectors, up to 30V DC,
100W (3A). The maximum capacity of detectors or other loops units is 15. Each detector has an
internal loop switch, just like regular loop units.
Data signalling uses a “power line modem”, which is a radio signal transmitted over the loop
wires. This gives 1200 baud transmission, just like AL_Com loops. Similar to wireless radio signals,
PowerLoops may experience reflections and cancellations depending on the cable length and
layout –which means that transmitters must be powerful and receivers must be sensitive.
2.2.2 Software handling
A PowerLoop is “raised” the same way an AL_Com loop is raised:
1. BSD-340 powers the first detector from the A side
2. The detector sends a Restart message (serial number, detector type)
3. BSD-340 orders the detector to close its loop switch, powering the next detector
4. The procedure in point 2. and 3. repeats until the loop is closed
Some special cases:
1. If the BSD-340’s B terminal is reached, there is a “closed loop”
2. If no Restart message is received, there is a “loop break”
3. If two Restart messages are received, there is a “branch” (which is illegal on PowerLoop)
4. If loop power disappears immediately after a loop switch is closed, there is a “short-
circuit”.
This is noticed by the detector, which opens the switch again and sends a short-circuit
message to the BSD-340
5. After a loop break or a short circuit BSD-340 starts raising from the B side.
This will in most cases bring all detectors to live
When the PowerLoop is up and running, some issues may occur:
1. Periodic loop measurement detects a loop wire break
2. Periodic loop measurement detects a loop short-circuit

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.

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 8
3. AutroSafe now continues as described in chapter 2.3.1 above.
4. When the loop raise is complete, AutroSafe sets state Enabled on the loop, and loop
polling starts again.
Note! RESET does not cause a loop raise. The operator must disable, then enable a loop to
raise it manually.
2.3.3 Loop Polling
According to EN-54, AutroSafe must report missing detectors within 100 seconds. AutroSafe sends
a POLL message to all detectors and requires an Acknowledge in return as proof of life.
1. BSD-340 divides polls over time based on the number of detectors so that one complete
loop scan takes 60 seconds.
BSD-340 updates an internal table indicating if a detector is alive or not. This scanning is
independent from AutroSafe’s polling.
2. AutroSafe polls BSD-340 every 20 seconds (to keep total time under 100).
BSD-340 then reports “Point Not Responding” for all detectors that does not answer with
acknowledge message.
2.4 Crosstalk
Crosstalk, or cross loop communication, occurs when radio signals transmitted in one loop is
received by the BSD-340 controlling another loop. This happens because the loop cables work like
antennas and may occur when cables for multiple PowerLoops are run in parallel or when BSD-
340 LoopDrivers are installed close to each other. In general, PowerLoops should not be pulled in
parallel, and
BSD-340 PowerLoop Drivers should be distributed around the site using AutroFieldBus, and be
located as close to the PowerLoop as possible.
Crosstalk is electric noise, and can be divided into two degrees of severity:
•Crosstalk/Full Crosstalk:
A complete message is transmitted between PowerLoops without errors, lost or ruined
bits.
Note! The PowerLoop can, to some extend work fairly good when there is error free
crosstalk, however this is not an acceptable situation and needs to be fixed.
•Noise/Partial Crosstalk
Weak reception causes a message to be partially transmitted between PowerLoops or has
bit errors when received by another loop.
Note! Noise causes retransmissions, which in turn may ruin messages on other loops, so
this is the worst situation.
2.4.1 Possible crosstalk issues
When crosstalk occurs, the system may experience several issues:
1. Restart messages from one loop received by another loop.
➢During loop raise: Faults could be new branches or wrong detector type
compared to configuration. INIT could often end with loops disabled
automatically and fault messages.
➢During operation: Loop would be powered down and raised, making Restart
messages that would disturb other loops.