ALULA BAT-FIRE-ATT UNIVERSAL Communicator User Guide
- June 4, 2024
- alula
Table of Contents
ALULA BAT-FIRE-ATT UNIVERSAL Communicator
Scan QR for most up to date manual, features, and compatibility
BAT-
Fire is a device that connects to an intrusion or fire alarm control panel
(FACP) and provides central station alarm reporting.
Features
- Supports 12V and 24V regulated FACPs/burg panels
- Alarm capture via phone line interface or standard FACP/burg panel points
- Supports Contact ID (CID) reporting format
- Dual Path: Ethernet (primary) with Cellular (backup)
- Sole Path: Ethernet or Cellular
- Platform visibility through AlulaConnect™
- Trouble event detection and reporting
- Four programmable input/output ports
- At-a-glance system status via front-panel LEDs
- UL 864 10th edition commercial fire certification
- ULC-S559 commercial fire certification
- UL 1610 commercial burg certification
- ULC-S304 commercial burg certification (Security Level II installations)
Operation
Phone line capture
BAT-Fire provides two PSTN interfaces for the FACP/burg panel’s DACT phone line connections. BAT-Fire’s DACT phone interface connection provides phone line voltage, dial tone, ringback tone and all required CID protocol signaling. The BAT-Fire receives CID events from the FACP/burg panel’s DACT and then relays the CID events to the central station receiver.
Point capture
The BAT-Fire provides inputs that can be used to monitor an FACP’s alarm, AC
fail, and trouble points (dry contact outputs). In this topology BAT-Fire
inputs will be connected to the FACP points (dry contact outputs). BAT-Fire
will continually monitor the state of the FACP points (dry contact outputs). A
state change on a BAT-Fire monitored FACP point (dry contact output) will be
report-ed to the central station. (Refer to the Programming section describing
how to set-up a BAT-Fire input for FACP point capture.)
Note: for UL 864 10th edition, this configuration may only be used for panels
with one input zone. 9th edition and earlier permitted this method for
multiple protection zones.
Central station communication
The BAT-Fire can be configured to provide dual path connectivity using Ethernet/broadband and cell or single path connectivity using either Ethernet/broadband or cell to Bosch Conettix D6100IPv6 receivers at the central station.
Central station communication
The BAT-Fire can be configured to provide dual path connectivity using Ethernet/broadband and cell or single path connectivity using either Ethernet/broadband or cell to Bosch Conettix D6100IPv6 receivers at the central station.
Installation and Wiring
- Set up an account in the AlulaConnect portal.
- Mount the BAT-Fire using the guidelines listed below to meet UL 864, UL 1610, ULC-S559, and/or ULC-S304. Use the mounting holes on the back plate.
- Install the cellular antenna.
- Power down the FACP/burg panel.
- Wire the BAT-Fire to the FACP/burg panel. (See wiring diagrams on the following pages.) All wiring must be performed in accordance with NFPA 70/72 or CSA C22.1 (Safety Standard for Electrical Installations, Canadian Electrical Code, Part I, Section 32).
Note: 1/2” conduit should be used. Only one conduit knockout is to be
used for wiring. Multi-conductor wire connections should follow best practices
using pigtail or crimp connectors.
To meet UL 864, UL 1610, ULC-S559, and/or ULC-S304, ensure the following:
-
BAT-Fire must be installed in accordance with applicable standards: UL 827, UL 681, NFPA 70/72, ULC-S524, ULC-S561, and/or ULC-S301/302.
-
BAT-Fire must be mounted in the same room as the FACP/burg panel.
-
All wiring between BAT-Fire and FACP/burg panel
is max 20 ft for UL 864 and max 18 m for ULC-S559. These wire length guidelines must be used for both burg and fire installations. -
Run all wiring between BAT-Fire and FACP/burg panel through non-rigid metallic conduit (Canada) and non-rigid conduit (US).
-
All equipment used for the IP connection (such as the router, hub, modem, etc.) shall be UL/c-UL listed, and be provided with 24 hour standby power.
-
For dual or sole path Ethernet, plug in the Ethernet cable.
-
Power up the system. After 1-2 minutes, verify the Ethernet and Cellular LEDs. For Ethernet installs, the ETHERNET LED should be on. For cellular installs, the CELLULAR LED should be on, or displaying a short
blink sequence (dual path mode). Verify a minimum of two signal bar LEDs are displayed. (See Operation and Indicator Overview section for signal strength.) -
Physical installation is complete.
-
Press the Config button on the BAT-Fire for 2 seconds to enable programming. Program the BAT-Fire via AlulaConnect (see Programming section).
-
Close the cover. Confirm POWER, TROUBLE, and COMM LEDS are green.
-
After installing BAT-Fire, or modifying any FACP/
burg panel programming, verify proper operation and reporting of all event codes using your FACP/burg panel installation manual. Burglary installs must have cover tamper enabled and must be tested yearly.
Figure 1. Phone Line Capture Wiring
- Both Phone line 1 and 2 must be connected to the FACP/burg panel. The FACP/burg panel must be configured to supervise the phone lines.
- Most FACPs/burg panels can be supported for event reporting as long as it provides Tip & Ring connection and transmits events in Contact ID format.
- Warning: do not connect telephone company lines to the BAT-Fire. Attention: ne connectez pas les lignes de votre compagnie téléphonique au BAT-Fire.
- It is recommended to use separate cables for Tip & Ring 1 and Tip & Ring 2.
- Failures and Troubles are communicated to FACP/burg panel via the BAT-Fire dropping voltage to Phone 2. Refer to Programming section on how to configure Phone 2 trouble triggers.
- Stranded wire gauge range: 24-14AWG.
- If FACP/burg panel has one phone line, PGM4 should be wired as the trouble indicator (see Figure 2). This configuration is common in commercial burg applications.
Figure 2. Point Capture Wiring
- Refer to Programming section on how to configure BAT-Fire’s PGM1, PGM2, and PGM3 for FACP panel point capture and PGM4 as a trouble trigger. PGM4 is an open-collector output.
- This figure shows one possible configuration between BAT-Fire and the FACP/burg panel. A relay may not be required. Refer to your FACP/burg panel installation manual. If a relay is required, use a UL 864 or ULC-S527 listed relay (i.e. Fire-Lite® PAM-2 by Honeywell® relay).
- The panel must support the relay contacts as indicated above (NC for alarm and AC-FAIL and NO for Trouble) and battery calculation shall consider the additional current draw into the PGM’s during the Normal Standby state.
- Use 4.7k ohm 1/4 Watt minimum resistors (not included).
- PGM ports are not supervised.
- Only panels without supervisory signaling can use this setup.
- For UL 864 10th edition, this configuration may only be used for panels with one input zone. 9th edition and earlier permitted this method for multiple protection zones.
- PGM1, PGM2, and PGM3 are not to be used as alarm and trouble inputs in commercial burg applications.
Figure 3. Single Phone Line Burglary Wiring
- For UL 1610 installations, refer to Programming section on how to configure BAT-Fire’s PGM3 as a ringback trigger. A UL-approved siren such as Honeywell Model 747 must be used for ringback. The ringback feature on the control panel must be disabled.
- For UL 1610 partitioned installations, all partitions must be in the same building and under the same management. Install the ringback siren where it can be heard by all partitions.
Trouble Conditions
The following trouble conditions can be communicated by BAT-Fire to the
FACP/burg panel:
Trouble | Indication |
---|---|
Cover Tamper | Cover is opened |
Power Fail | Input voltage has fallen below 9V |
Cell Fail | Cellular communication has a performance failure (i.e. |
intermittent communication, not operational)
Ethernet Fail| Ethernet communication has a performance failure (i.e.
intermittent communication, not operational)
CS Trouble| Backup communication path to the central station is not
operational
CS Fail| Signal transmission to the central station is not
operational
Programming
Programming via AlulaConnect
Table 1: PARAMETERS FOR UL 864 & UL 1610 COMPLIANCE (USA)
NOTICE TO INSTALLERS, AUTHORITIES HAVING
JURISDICTION, AND OTHER INVOLVED PARTIES:
This product incorporates field-programmable software. All features/options
described below are permitted in UL 864/UL 1610. In order to comply with the
requirements in the Standard for Control Units and Accessories for Fire Alarm
Systems, UL 864, and/or Standard for Central- Station Burglar-Alarm Units, UL
1610, certain programming features or options must be limited to permitted
settings or not used at all as indicated below.
Program Feature or Option| Situation| Possible
Settings| Default Settings| UL 864
Required Settings| UL 1610
Required Settings| Notes
Supervision Preferenc (Comm Trouble Supervision)| ****
IP with Cell Backup
| ****
60 seconds –
6 hours
| ****
6 hours
| ****
6 hours or shorter
| ****
Primary: 200 seconds
or shorter Backup: 6 hours
| For UL 1610, if the primary path fails, system supervises secondary path
at the primary interval.
Sole Path IP| 60 seconds –
6 hours
| 1 hour| 1 hour or shorter| 200 seconds or shorter| Turn off cellular
supervision Turn off virtual interface supervision for both primary and backup
cellular
Sole Path Cell| 60 seconds –
6 hours
| 1 hour| 1 hour or shorter| 200 seconds or shorter| Turn off Ethernet supervision
Turn off virtual interface supervision for both primary and backup Ethernet
Remote Programming*| On-site or Remote| Enabled or Disabled| Disabled|
Disabled| Enabled or Disabled| If Disabled, Installer must press Config button
onsite
Phone 2 Trouble Trigger| If using Phone Line capture (Figure 1)| Power Fail
Cover Tamper Cell Fail Ethernet Fail CS Fail CS Trouble| CS Fail| CS Fail|
Cover Tamper CS Fail| Figure 1 : Any Enabled Trouble: BAT-Fire drops
Phone 2 line voltage
PGM4 Port Trouble Trigger| If using Point Capture (Figure 2)| Power Fail Cover
Tamper Cell Fail Ethernet Fail CS Fail CS Trouble| CS Fail| CS Fail| Cover
Tamper CS Fail| Figure 2 : BAT-Fire PGM4 Output (Any Enabled Trouble)
connected to FACP/burg panel Trouble Input
- If Remote Programming is disabled, updates to site-specific parameters and BAT-Fire firmware are only permitted when the Config button on the BAT-Fire is pressed for 2 seconds.
- These trouble triggers are required to meet the UL864 and UL1610 standards. However, all other trouble triggers listed in the Possible
- If Commercial Burg is selected, the more restrictive of the Fire and Burg timings will be used.
- Earlier editions of NFPA require supervision settings of 5 minutes.
- UL 864 10th edition permits the point capture configuration for FACPs/burg panels protecting only a single zone; the 9th edition permits point capture for multi-zone FACPs/burg panels.
- UL1610 requires 128 bit encryption or better. For active communications, the encryption shall be enabled at all times.
Table 2: PARAMETERS FOR ULC-S559 & ULC-S304 COMPLIANCE (CANADA)
NOTICE TO INSTALLERS, AUTHORITIES HAVING
JURISDICTION, AND OTHER INVOLVED PARTIES:
This product incorporates field-programmable software. All features/options
described below are permitted in ULC-S559/ULC-S304. In order to comply with
the requirements in the Standard for Equipment for Fire Signal Receiving
Centres and Systems, ULC-S559-13-R2018 and/or the Standard for Control Units,
Accessories and Receiving Equipment for Intrusion Alarm Systems,
ULC-S304:2016-REV1, certain programming features or options must be limited to
permitted settings or not used at all as indicated below.
Program Feature or Option| Situation| Possible
Settings| Default Settings|
ULC- S559
Required Settings
| ULC- S304
Required Settings| Notes
Supervision Preference (Comm Trouble Supervision)| IP with Cell Backup| 60
seconds –
6 hours
| 6 hours| Primary: 180 seconds
or shorter Backup: 6 hours
| Primary: 180 seconds or shorter
Backup: 6 hours
| For ULC-S559, if primary path fails, system supervises secondary path at the
primary interval.
Sole Path IP| 60 seconds – 6 hours| 1 hour| 180 seconds or shorter| 180
seconds or shorter| Turn off cellular supervision Turn off virtual interface
supervision for
both primary and backup cellular
Sole Path Cell| 60 seconds –
6 hours
| 1 hour| 180 seconds or shorter| 180 seconds or shorter| Turn off Ethernet supervision
Turn off virtual interface supervision for both primary and backup Ethernet
Remote Programming*| On-site or Remote| Enabled or Disabled| Disabled| Enabled
or Disabled| Enabled or Disabled| If Disabled, Installer must press Config
button onsite
Phone 2 Trouble Trigger| If using Phone Line capture (Figure 1)| Power Fail
Cover Tamper Cell Fail Ethernet Fail CS Fail
CS Trouble
| CS Fail| CS Fail| Cover Tamper CS Fail| Figure 1 : Any Enabled
Trouble: BAT-Fire drops Phone 2 line voltage
PGM4 Port Trouble Trigger| If using Point Capture (Figure 2)| Power Fail Cover Tamper Cell Fail Ethernet Fail CS Fail
CS Trouble
| CS Fail| CS Fail| Cover Tamper CS Fail| Figure 2 : BAT-Fire PGM4
Output (Any Enabled
Trouble) connected to FACP/burg panel Trouble Input
- If Remote Programming is disabled, updates to site-specific parameters and BAT-Fire firmware are only permitted when the Config button on the BAT-Fire is pressed for 2 seconds.
- These trouble triggers are required to meet the UL864 and UL1610 standards. However, all other trouble triggers listed in the Possible
- If Commercial Burg is selected, the more restrictive of the Fire and Burg timings will be used.
- ULC-S304 and ULC-S559 require 128 bit encryption or better. For active communications, the encryption shall be enabled at all times.
Programming via AlulaConnect (cont.)
- Programming BAT-Fire Phone 2 trouble triggers
- Select “Edit” to the right of Phone 2
- Check all desired Phone 2 triggers
- Power Fail
- Cover Tamper
- Cell Fail
- Ethernet Fail
- Central Station Fail
- Central Station Trouble
- Select “Save”
- Programming BAT-Fire PGMx port for FACP/burg panel point capture
- Select “Edit” on the desired input port
- Select “Configure as Input”
- Enter required configuration input data
- Sensor Type
- Report Code
- Zone Number
- Input Name
- Select “Save”
- Programming BAT-Fire PGM4 port as trouble trigger
- Select “Edit” on the desired output port
- Select “Configure as Output”
- Name output as desired
- Check all desired trouble triggers
- Power Fail
- Cover Tamper
- Cell Fail
- Ethernet Fail
- Central Station Fail
- Central Station Trouble
- Select “Save”
- Programming BAT-Fire central station receiver(s)
- Select primary and backup (optional) receivers
- Adjust Supervision Interval based on wiring mode
- 6 hours (default) complies with UL 864 10th edition requirement for dual path communications
- For specific AHJ guidance, sole path mode, ULC-S559 or ULC-S304 compliance, refer to Table 1 for Supervision Interval settings
- Select “Save”
- Programming BAT-Fire PGM3 port as ringback trigger
- Select “Edit” on the desired output port
- Select “Configure as Output”
- Name output as desired
- Check the UL Ringback trigger
- Select “Save”
Operation and Indicator Overview
Events are reported to the central station receivers and the Alula platform
event system. All
events use Contact ID reporting codes.
To enter programming press the Config button on the BAT-Fire for 2 seconds.
- With the BAT-Fire cover open, it will remain in programming mode for 2 hours.
- Close the cover. Programming mode will exit in 3 minutes.
Enroll/Reset button
- Hold for 5 seconds to reset the BAT-Fire
- Hold for 30 seconds to factory default the BAT-Fire
- All LEDs flash on then off at 5 seconds and again at 30 seconds when the Enroll/Reset button is held down. This indicates that the button has been pressed for a sufficient amount of time.
LED indicators
LED | Indication |
---|---|
Power | Pulses when power is present |
Trouble | Green – system ok |
Yellow – input voltage < 8V, or
- cell connection has failed, or
- Ethernet connection has failed, or
- cover is open
Comm| Green – central station receiver(s) all ok Yellow –
central station receiver(s) trouble Off – all central station
receiver(s) have failed
Ethernet| Off – interface not used
Flashing – attempting connection using this interface
On – connected using this interface
Wi- Fi| Unused
__
Cellular
| Off – cell is not registered
Flashing – last connection test failed
On – connected using this interface
Short blink – connected via Ethernet, last cell connection test
successful
Update| Off – firmware update available
Flashing – firmware update is in progress
On – firmware is up to date
Device| Unused
Cellular signal bar LEDs indicate the quality of the cellular connection. A minimum of two signal bar LEDs is recommended.
Number of Signal Bar LEDs Lit| Cellular Signal
Strength
---|---
0| Bad
1| Marginal
2| Acceptable
3| Good
4| Best
BAT-Fire will relay any signal sent from the panel it is connected to. Additionally, the following signals can be generated from the BAT-Fire directly.
Signal | Report Code | Device – Zone/User |
---|---|---|
Peripheral Tamper (Cover Tamper) | 341 | 0 |
Comm Test Trouble | 350 | 800 – 803 |
Manual Comm Test | 601 | 800 – 803 |
Auto Comm Test | 602 | 800 – 803 |
Optionally generated point capture event | Programmable | Programmable |
Zone Number
Pro Tips
-
The BAT-Fire is a commercial life safety communicator and requires a reliable and consistent cellular connection. Always follow best installation practices regarding mounting location and location of antenna to achieve and maintain the highest possible signal level. The signal bar indicators are engineered to ensure a durable, trouble-free installation.
-
Cellular antennas need to be in free air to communicate. Cellular antennas should not be mounted inside a metal enclosure.
-
Cellular antenna options for enhanced performance:
Indoor:- Taoglas™ TG.30.8113
Troubleshooting
Symptom | Troubleshooting Steps |
---|
__
Ethernet LED Off
|
- Confirm cable connected.
- Ensure router is powered.
- Ensure UDP ports 1234 and 1235 are open in router/modem settings.
- Ensure account is properly configured.
__
Cellular LED Off
|
- Verify sufficient signal strength for cellular (see cellular signal bar table in Operation and Indicator Overview section).
- Ensure account is properly configured.
Comms LED Yellow|
- Verify the reporting path and ensure the receiver is properly configured.
- Contact Alula for further technical support.
__
__
No Alarm CS Reports
|
- Ensure FACP/burg panel wiring is correct.
- Ensure the FACP/burg panel is configured properly.
- If telco reporting, ensure FACP/burg panel is set-up for CID reporting.
- If point capture reporting, ensure FACP/burg panel is set-up to trip appropriate relays.
- Ensure account is properly configured for event relay.
- Contact Alula for further technical support.
__
__
Poor Cellular Signal Strength
|
- Ensure antenna is securely threaded onto the BAT-Fire antenna connector.
- Reposition the unit (move or rotate).
- Move the unit/antenna higher in the building.
- Move the unit/antenna away from metal objects (appliances, ducts, stucco walls, mirrors).
- Move the unit/antenna closer to a window.
- Install one of the higher performance antenna options (see Pro Tips section).
Glossary
Capture| Sensing a status or condition
DACT| Digital Alarm Communicator Transmitter that reports on phone
lines
FACP| Fire Alarm Control Panel
I/O Port| A programmable input or output on BAT-Fire, named PGM1-PGM4
Line| A phone line, used for reporting alarm data
Phone Line Capture| The operation of the BAT-Fire
connecting to the FACP/burg panel phone ports and emulating the central
station
LPS| Limited Power Source
NFPA| National Fire Protection Association
Open Collector| An output that, when engaged, shunts current to
ground
Point| A single FACP/burg panel output that is either on or off
Point Capture| The operation mode of BAT-Fire connected to the
FACP/burg panel output(s) and sensing a trouble or alarm condition.
Additionally, the operation of the FACP/burg panel connected to a BAT-Fire
output and sensing a trouble or communication condition
PSTN| Public Switched Telephone Network, aka POTS – Plain Old
Telephone Service
Relay| An electrically operated switch that isolates the control
signal (i.e. FACP/burg panel output) from the switched circuit (i.e. BAT-Fire
input)
Trigger| An event that causes a BAT-Fire output to change state
Specifications
Physical
Housing Dimensions Weight Mounting Fasteners Pilot Hole for Screw into Wood
Pilot Hole for Wall Anchor Cover Securing Screw Antenna Wire Gauge Range| 8.6
x 5.8 x 2.2 inches [21.8 x 14.6 x 5.5 cm] 13.2 ounces [375 g] #6 screws and
wall anchors [included] Ø 1/8in [3mm] Ø 3/16in [4.7mm] #6 screw [included]
External [included] 24-14AWG
Device Specification
Reported Indications Current Draw Compatible Input Voltage Range Programmable
Output Current Maximum| Cover Tamper
154mA [Standby] 207mA [Max] @ 12VDC 109mA [Standby] 161mA [Max] @ 24VDC 10-28VDC Limited Power Will shunt up to 75 mA into ground
Environmental
Operating Temperature Maximum Humidity| 32°F to 120°F [0°C to 48.9°C] 93% non-
condensing relative humidity
Models
BAT-FIRE-ATT BAT-FIRE-VZ| BAT-Fire, AT&T BAT-Fire, Verizon Note: the only
difference between the models is the cellular carrier.
Certification
Safety Standards Radio Cellular California State Fire Marshal NY Fire Marshal|
UL 864 10th edition, ULC-S559, UL 1610, ULC-S304 FCC, IC AT&T, Verizon
Specifications subject to change without notice
FCC NOTICE
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions:
- This device may not cause harmful interference.
- This device must accept any interference that may be received, including interference that may cause undesired operation.
Changes or modifications not expressly approved by Alula could void the user’s authority to operate this equipment.
RF Exposure:
To satisfy FCC RF Exposure requirements for mobile and base station
transmission devices, a separation distance of 20 cm or more should
be maintained between the antenna of this device and persons during operation.
To ensure compliance, operation at closer than this distance is not
recommended.
47-00009 • Rev A • 2021-11-19
Tech Support Line • (888) 88-ALULA •
888-882-5852
alula.com
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>