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.

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 9
2. Traffic like alarms or analogue values received by another loop
➢Wrong detector reported.
➢Traffic in one loop could ruin traffic in another loop, this would cause excessive
retransmissions which in turn could disturb other loops.
2.4.2 Crosstalk countermeasures
The BSD-340 software has some countermeasures to handle crosstalk.
Note! The wiring of the loops (see chapter 2.4) are very important to follow to minimize the
occurrence of crosstalk.
1. Loop ID
Each PowerLoop includes a “loop ID” in every restart message. The BSD-340 can then
ignore restarts from other loops. The “loop ID” is normally the BSD-340’s address on the
AutroFieldBus.
Note! There must be a way to accept wrong IDs so that new detectors and moved
detectors can be accepted.
2. Checksum seeded with LoopID
All PowerLoop messages have a 16-bit CRC (checksum) so that the receiver can ignore
messages ruined by noise. Each loop calculates CRC differently by seeding the CRC
algorithm with the LoopID. This means that all units on a PowerLoop can ignore messages
from other loops, even if they are influenced by crosstalk. The BSD-340 can also
determine what loop a crosstalk message comes from.
3. Timeslots
A PowerLoop unit always listens to the loop and avoids transmitting if someone else is
transmitting, but if two starts simultaneously there will be a collission, and both stop
sending. This problem, due to collisions, is solved by a “timeslot” system, and starting
transmission in a random timeslot. This strategy increases the chance to get a message
through.
Note! Crosstalk messages will reduce capacity from neighbour loops.
4. Slow retransmissions
The BSD-340 SW version 1.1.0, or later, no longer has a time delay in retransmissions of
messages, which was used for avoiding mutual jamming. The high number of timeslots
available for retransmissions makes a better use of bandwidth and assures that messages
get through.
5. Fault message “crosstalk”
When crosstalk is detected the BSD-340 will report a fault message to the AutroSafe
panel. This can be used during commissioning to reduce crosstalk.
6. Crosstalk “mode” of BSD-340
There is a “crosstalk mode” in the BSD-340. This is done by setting the address switches to
+40 (see chapter 5.4.1).
•No crosstalk fault messages (as they would become very annoying in systems with
continuous crosstalk)
•Ignore RESTART messages from other loops

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!

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 11
3.2 Label the BSD-340 board to identify the SW version
Apply a label to the BSD-340 board which states the SW version that is to be downloaded (refer to
chapter 3.6).
3.3 Connect PC to loop driver
Connect your PC to the BSD-340 PowerLoop Driver service port using a RS232 serial cable.
Check IFG Service tool user interface for help (see chapter 7).
3.4 Start IFG Service tool and connect to loop driver
a. Open IFG Service Tool on your computer (see chapter 7)
b. Click the drop-down menu for Select ComPort, select the port in use for connection with
the BSD340 and press Connect
c. Select Start Log to File to save progress and topology to PC file for documentation
Note! When the IFG service tool is running and connected to a loop driver, wait a minute to
check for any crosstalk
1
messages in the "Output window". Any loops listed here for crosstalk
should be disabled before you proceed. This to ensure the best possible outcome of the
upgrade.
1
See chapter2.4

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 12
3.5 Disable loop
From the Autrosafe panel, disable the loop which you are about to upgrade.
3.6 Download software to BSD-340
a. Press Open to the right of "EEProm". Go to the folder where you have stored the new
software files. Select *.EEP file from folder
b. Press Open to the right of "Application". Go to the folder where you have stored the new
software files. Select *.hex file from folder
c. Press Boot to set loop driver in boot loader mode
d. Verify Bootloader loaded (Bootloader BSD340 June 9 2004 10:54:54) in the "output
window" in IFG service tool.
e. Upgrade EEProm by clicking Program on the right-hand side - wait for completed
confirmation in the Command Input window
f. Upgrade hex by clicking Program on the right-hand side - wait for completed confirmation
in the Command Input window
g. Press Run –loop driver will start
h. Type #? followed by Enter in the Command input window to verify correct version Notice
that AFB Switch addr will change according to the set address on the loop driver.
i. If system number noted in step 3.1 (Before you start) is different from 0: Type #SetSysNoX
(X = earlier system number) and enter in the Command input window

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 13
3.7 Raise loop and store topology in loop driver
a. Type #si and enter in the Command input window to raise loop and save topology to
EEPROM
b. The loop raise should end with a message like this
If loop is successfully saved to EEPROM, proceed to step d.
c. Resolving failed save of topology
i. If there are devices on the loop which fail to start, or that there are loop breaks on the
loop, a fail message is reported: “Loop Not saved in EEPROM this time” will be printed
in terminal (see figure below)
ii. Since the powerloop requires to have a saved topology to work, use the print
topology #prntop command to get a printout of the topology and fault messages to
help resolve any faults.
iii. Note the symbol | in the Sw column. Different symbols may be used:
| = closed switch, X = open switch, ? = unit missing, S = Short circuit
In the example above there is a short between detector 1 and 2. In the SW column
the first detector states an X, which means that it has not been able to close the loop
switch. On detector 2 it is stated an S for short (towards detector 1)
iv. Investigate the loop and connections and resolve any faulty wiring or connections.
v. Type #si and enter in the Command Input Window to try a loop raise again after you
have investigated faults indicated on the topology after the last run of "si.
d. After loop has been successfully saved you can verify the saved loop, Type #prntop and
enter in the Command input window to list saved topology (output as in figure below)

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 14
-The same loop as the example above, but now without the short between
detector one and two in it.
e. Press Reset on the Autrosafe panel to clear AutroFieldBus faults caused by the upgrade of
the loop driver.
f. Enable loop on the Autrosafe panel
g. Enable any other loops which were disabled to remove crosstalk before the upgrade was
started.
h. Continue with the next loop driver (if any)
4. Service operations
4.1 Delete and save topology
Saving a new topology requires no existing topology in loop driver.
4.1.1 Delete topology
Topology may be deleted by two different procedures:
•By PC and IFG service tool using command #eraseEE
•Set address switches on loop driver to 97 (High:9, low7), press the reset button on loop
driver –then wait 5 seconds to complete. Set address switches back to correct values and
press the reset button on loop driver.
4.1.2 Save topology
Saving topology may be done by two different procedures:
Note! If there is any known crosstalk involved in current loop, any conflict loop should be disabled
before proceeding
•By PC and IFG service tool using command #SI
oType #prntop to list saved topology
•By manually disable/enable loop (loop driver without existing topology)
Note! A loop with faults (short, break and such) will not be stored. Only a loop which is complete
throughout will be stored in the system

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 15
4.2 Replace PowerLoop driver (BSD-340)
4.2.1 Without PC and IFG service tool
Note! If there is any known crosstalk involved in current loop, any conflict loop should be disabled
before proceeding
1. Disable loop
2. Remove old loop driver and replace with a new one
3. Disable other loops which you know have crosstalk with the loop you are working on.
4. Set switches to 97 (High:9, low7) and press reset button on loop driver to erase any
topology
5. Set address on loop driver back to correct address and press reset button on loop driver
6. Press reset on panel/top system to re-establish Autrofieldbus
7. Loop will automatically be enabled
8. Memory fault will be issued
9. Disable/Enable loop to save topology
10. Enable loop(s) disabled in step 3.
4.2.2 With PC and IFG service tool
Note! If there is any known crosstalk involved in current loop, any conflict loop should be disabled
before proceeding
1. Disable loop
2. Set correct address on loop driver
3. Remove old loop driver and replace with a new one
4. Connect laptop to new driver
5. Verify address by typing #? and enter
6. Disable other loops which you know have crosstalk with the loop you are working on.
7. From IFG service tool
a. Erase topology from EEPROM with using command #eraseEE and enter
8. From IFG service tool
a. Type #si and enter to raise loop and save topology to EEPROM
b. Type #prntop and enter to list saved topology
9. Set Systemnumber if different from 0: Type #SetSysNoX (X = earlier system number) and
enter in the Command input window
10. Press reset on panel/top system to re-establish Autrofieldbus
11. Loop will automatically be enabled
12. Disable/Enable loop.
13. Enable loop(s) disabled in step 6.
4.3 Replace loop unit
4.3.1 Without PC and IFG service tool
Note! If there is any known crosstalk involved in current loop, any conflict loop should be
disabled before proceeding
1. Disable loop
2. Remove old loop unit and replace with a new one
3. Disable other loops which you know have crosstalk with the loop you are working on.

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 16
4. Set address switches on loop driver to 97 (High:9, low7) and press reset button on loop
driver to erase any topology (wait 5-10 seconds after you have pressed reset button on
driver)
5. Set correct address and driver press reset button on loop driver
6. Press reset on panel/top system to re-establish Autrofieldbus
7. Loop will automatically be enabled
8. Memory fault will be displayed
9. Disable/Enable loop to save topology
10. Enable loop(s) disabled in step 3
4.3.2 With PC and IFG service tool
Note! If there is any known crosstalk involved in current loop, any conflict loop should be
disabled before proceeding
1. Disable loop
2. Remove old loop unit and replace with a new one
3. Verify address by typing #? and enter
4. Disable other loops which you know have crosstalk with the loop you are working on.
5. From IFG service tool
a. Type #si and enter to raise loop and save topology to EEPROM
b. Type #prntop and enter to list saved topology
6. Press reset on panel/top system to re-establish Autrofieldbus
7. Loop will automatically be enabled
8. Enable loop(s) disabled in step 4
5. Commissioning operations
The content of this chapter must be considered as useful tips. None of these actions are
mandatory
5.1 Useful commands
Command
Parms
Description
Example
#?
0
List Device Status
#rt
Reset
#Login
1
Login to device P1 (PowerLoop
LoopID)
#Login1
#Logout
1
Logout from device P1
#Logout1
#SetSysNo
1
Set PL Systemnumber
#SetSysNo5
#ping_ctrl
1
Stop/Start ping P1=0/1
#ping_ctrl0
#PL_Stat
0
Print PL stat
#PL_Clear
0
Clear PL stat
#PrnTop
0
Print Topology (PT_DB)
#si
0
Start Init
#EraseEE
Erase saved PTs (erase saved
topology)
#TraceAL
1
Trace AL_Com 0=Off, 1=On.
No print of standard protocols
#TraceAL1
#PrintCross
0
Prints crosstalk statistics
#ZeroCross
0
Reset crosstalk statistics

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 17
5.2 Establish AutroFieldBus communication
AutroFieldBus communication is up running on a panel already in commissioning mode. On a
running AutroFieldBus it is possible to remotely access PowerLoop drivers from another
PowerLoop driver with a PC connected. Use command #LoginX, where X = address on AFB
(exclude +40 settings and system number). This is useful to fetch crosstalk statistics and PL_stats
(see chapter 5.4.2 Discover crosstalk). In addition, you may fetch the topology. Avoid using other
commands as this will cause too high load on the PowerLoop driver you are connected to with a
PC.
Recommended procedure:
1. Start log to file (easy to read when finished)
2. #LoginX
3. #? (to have reference to loop driver in log file)
4. #Printcross
5. #PL_stat
6. #prntop (list existing topology as well as saved)
7. #LogoutX (important)

BSD-340-user-guide-eng, Doc. 1004474-2, 2020-09-18,
Autronica Fire and Security AS
Page 18
5.3 De-conflict systems
If more than one panel has an Autrofieldbus with PowerLoop in the same installation,
PowerLoops need unique system numbers as well. This number is an offset of address switch
setting on BSD-340. This is to de-conflict PowerLoops with same loop IDs so that the crosstalk
algorithm is not compromised.
System number is selected in configuration file at the AutroFieldBus interface. The lowest number
to use is equal to the number of PowerLoops on the other Autrofieldbus. For convenience it is
recommended to use a higher number so that adding more PowerLoops to an AutroFieldBus does
not imply changing the System Number on the other AutroFieldBus.
Note!Due to limited memory available, crosstalk statistics only presents loopID 1 -50. Any loops
with ID exceeding this will not be listed.
The loop ID is the sum of the AFB-switch address and an offset. The following figure explains this: