BTM-Series Battery Temperature & Thermal Runaway Monitor

Battery Monitoring Systems

Overview

Features

Specifications

Resources & Support

FAQs

Request Quote

Eagle Eye Power Solutions Battery temperature monitor

The BTM-Series is a dependable low-cost scalable solution for protecting your batteries against over-temperature and thermal runaway conditions. Meet IFC and NFPA code compliance (see Product Features). Individual sensors are quickly and securely attached to each battery and connected in series from the main unit. Each thermal runaway sensor is sealed to IP68 (water, gas and dustproof), and the provided special gel-filled connectors are also sealed against acid ingress, dust, and gases.

Request a Quote

Key Features

Monitor individual unit battery temperatures for thermal runaway conditions
Simple fail-safe change-over relay alarm interfaces
Bright LEDs pinpoint individual overtemperature cells
No special tools required for installation
Sensor circuit break detection
Alarm on power supply failure (fail-safe)

Specifications

Alarm Range	Activation at 29 °C (85 °F), ± 3 °C (5 °F)
Reinstatement Temp	2 °C (3.5 °F) below activation temperature
Input Voltage	DC 12V 2-pin connectors or 12V AC/DC wall adapter
Output Relays	(2) SPDT volt-free contact relays Output relay contact ratings: 7A at 240 VAC, 10A at 120 VAC
Dimensions (L x W x D)	Monitor: 84 x 40 x 77 mm (3.3 x 1.6 x 3 in.) Sensor: 38 x 20 x 10 mm (1.5 x 0.8 x 0.4 in.) Cables: 300 mm (11.8 in.)
Compliance	IFC 2015 – 608.3, NFPA 1 – Article 53.3.2

Resources & Support

Product Literature

B TM-Series Data Sheet

Support Documents

Video Resources

btm-series-data-sheet-111519 Download

BTM-Series-Installation-Manual-041417 Download

BTM-Series-Quick-Start-Guide-103114 Download

FAQs

What is the maximum number of sensors that can be connected to a single monitor?

The maximum number of sensors for each monitor is approximately 200. If there are more than 14 sensors in over-temperature then the LED’s on the sensors become so dim that they are not visible, however the 1+ and 4+ indicators and relays on the monitor are still active.

Why is the temperature threshold for alarming set to 95ºF (35ºC)?

The nominal operating temperature for batteries is generally considered to be 77ºF (25ºC). If the battery is operating at 18ºF (10ºC) above that, it is a candidate for thermal runaway. The BTM is a fixed temperature device, so the temperature selected is above the normal swings in operating temperature but low enough to ensure that a battery that is overheating can be identified before thermal runaway occurs.

What are the maximum cable lengths for the BTM system?

At this time there is not a concrete limit on the total cable loop length or the length of cable between sensors. From an electronic point of view there is no reason why the length cannot be greater than 30 m (100 ft.). If the lengths become to excessive then there may be a possibility that the 4+ warning may activate with 3+ over-temperature faults. The system has been tested with a total loop length of 122 m (400 ft.) and the system operated normally.

What are the communication options for the BTM?

The BTM has (2) SPDT volt-free contact relays. Ratings are 7A at 240VAC and 10A at 120VAC.

What is the power consumption of the BTM?

The power consumption is 1.2W regardless of how many sensors are connected.

What kind of adhesive is used on the BTM sensor?

The sensors use 3M type 93020LE adhesive. If a sensor needs to be re-installed it is recommended to use this type of adhesive.

Name	Domain	Expiration	Description
bcookie	linkedin.com	365 days	The bcookie from LinkedIn is a browser ID cookie used for tracking the usage of embedded services of LinkedIn on websites. It serves to authenticate the user, ensuring a secure and optimized user experience when interacting with LinkedIn functionalities outside the main LinkedIn platform, such as 'Share' buttons or LinkedIn plugins on third-party sites.
lidc	linkedin.com	1 day	The lidc cookie from LinkedIn is used to facilitate data center selection and ensure secure and optimized routing of client requests. This ensures that a user's browsing experience on LinkedIn is smooth by efficiently directing the user's browser to the same data center, minimizing latency and enhancing website performance. This cookie is typically short-lived, being used for routing decisions in the near-term rather than for longer-term tracking or analytics purposes.
li_sugr	linkedin.com	90 days	The li_sugr cookie from LinkedIn is used for security purposes, specifically to track users for risk assessment and fraud detection. By monitoring and analyzing user behaviors, this cookie helps LinkedIn identify suspicious activities and ensure the safety and integrity of user accounts.
tk_lr	wpengine.com	365 days	The tk_lr cookie, associated with WordPress.com and Jetpack, is used to collect data for analytics purposes. It tracks a user's activity on the website over the long term, often for a period of a year, helping website owners understand the source of their traffic and providing insights into user behavior over extended periods. Remember that while WP Engine might host websites that use this cookie, the cookie itself is more directly related to WordPress.com and Jetpack's functionality.
tk_or	wpengine.com	3 days	The tk_or cookie, commonly used on WordPress sites with Jetpack or WordPress.com integrations, captures the original referrer a user came from, usually storing this data for a long duration (e.g., several years). This persistent tracking helps website owners understand the source of their traffic over extended periods and provides insights into user behavior and trends. While WP Engine may host websites that utilize this cookie, its origin and functionality are more directly tied to the Jetpack plugin and WordPress.com's features.
tk_r3d	wpengine.com	400 days	The tk_r3d cookie, commonly found on WordPress sites with Jetpack or WordPress.com integrations, is used to store referrer data for a limited period, typically a few days. This data helps website owners understand where their traffic is coming from, assisting in analytics and optimization efforts. It's essential to remember that while WP Engine may host websites that employ this cookie, the cookie itself is more directly tied to WordPress.com and Jetpack's features.
^_ga	google.com	2 years	Google Analytics cookies collect data about website visitors' interactions, enabling website owners to understand user behavior, measure site performance, and improve user experience. These cookies track details like how often users visit the site, which pages they view, and from where they've come. The aggregated data helps in optimizing website content and marketing strategies, ensuring visitors receive more tailored content on subsequent visits. Note that while these cookies gather information, individual users remain anonymous.
_gid	google.com	1 day	Google ID cookies are associated with a user's Google account and are used to recognize users across different Google services and devices. These cookies help deliver a consistent experience, remember user preferences, and personalize content based on the user's previous interactions. For instance, if a user is signed into their Google account, they might see personalized search results or ads based on their past search and browsing behaviors. The cookies also facilitate secure sign-ins and protect user data from unauthorized access. While Google ID cookies provide customization and security, users retain control over their data and can manage or opt-out of personalized experiences through their Google account settings.

Name	Domain	Expiration	Description
1P_JAR	google.com	30 days	The 1P_JAR cookie from google.com is used to gather website statistics and track conversion rates. It also allows Google to personalize the ads they serve to users based on recent searches and interactions. By collecting data on user preferences and behaviors, Google can ensure that users are presented with ads that are more relevant to their interests, thereby improving the effectiveness of ad campaigns and enhancing the overall user experience.
A3	yahoo.com	365 days	The A3 cookie from yahoo.com is used within Yahoo's advertising network to deliver targeted advertisements to users across their web properties and partner sites. By tracking users' online behavior, preferences, and engagement with content, the A3 cookie allows Yahoo to provide more relevant ads tailored to individual users. This helps improve the efficacy of ad campaigns and enhances user experience by showing ads that align with their interests.
AnalyticsSyncHistory	linkedin.com	30 days	The AnalyticsSyncHistory cookie is used by LinkedIn for tracking users across different websites to provide targeted advertisements and to analyze the efficiency of such ads. It allows LinkedIn to understand a user's interactions with ads over a specific period, facilitating better ad performance measurement and optimized ad targeting.
ar_debug	doubleclick.net	1 day	DoubleClick, which was acquired by Google, is known for its digital advertising products. The platform uses various cookies to serve and measure the performance of ads across the web. If you encounter a "debug" cookie from DoubleClick (or any other platform), it's typically related to debugging or development activities.
fpestid	wpengine.com	1 day	The fpestid cookie is associated with ShareThis, a social media sharing service. This cookie assigns a unique identifier to each user, enabling ShareThis to track user interactions across websites that integrate their sharing features. The primary purpose of the fpestid cookie is to facilitate the functionality of social sharing buttons and to gather analytics on user engagement with shared content.
IDE	doubleclick.net	400 days	The IDE cookie from doubleclick.net is used by Google to register and report a user's actions after viewing or clicking on an advertiser's ads. This helps measure the effectiveness and performance of the ad and present targeted ads to the user. With the data gathered from this cookie, advertisers can ensure that users see ads that are more relevant to their interests, leading to a more personalized browsing experience.
IDSYNC	analytics.yahoo.com	365 days	The IDSYNC cookie from analytics.yahoo.com is used to support the synchronization of user identification and exchange of user data between various ad platforms, websites, and networks. Its primary function is to help advertisers deliver more relevant ads across the web by understanding user interactions and preferences. Through ID synchronization, Yahoo can bridge the user's identity across different platforms and devices, ensuring a cohesive and personalized advertising experience.
NID	google.com	183 days	The NID cookie from google.com stores a unique identifier, which Google uses to remember your preferences and other information, such as your preferred language (e.g., English), the number of search results you wish to have shown per page, and whether or not you wish to have Google's SafeSearch filter turned on. Additionally, the NID cookie also helps personalize ads on Google properties, like Search, based on recent searches and interactions. By understanding user preferences and activities, Google aims to enhance the user experience across its various services.
receive-cookie-deprecation	doubleclick.net	180 days	The receive-cookie-deprecation from doubleclick.net is used to signal or test whether a browser or system environment supports or enforces newer cookie handling policies, such as restrictions on third-party cookies (e.g., SameSite policies or browser deprecation of third-party cookies).
test_cookie	doubleclick.net	1 day	The test_cookie from doubleclick.net is used to determine if a user's browser supports cookies. By setting and then checking this cookie, the platform can verify the user's ability to receive and store cookies, ensuring that subsequent advertising and tracking cookies can be successfully placed and read by the browser.
TDCPM	adsrvr.org	1 day	The TDCPM cookie is used to store a unique ID that identifies the device of a returning user, primarily for targeted advertising purposes. This cookie is typically set by The Trade Desk and is utilized to synchronize data across various ad platforms for effective ad targeting.
TDID	adsrvr.org	1 day	The TDID cookie is used by The Trade Desk to store a unique identifier for a user. This cookie helps in tracking users across different websites and devices, enabling targeted advertising and ad performance measurement. The TDID cookie is essential for delivering personalized ads and optimizing ad campaigns by recognizing returning users.
UserMatchHistory	linkedin.com	30 days	The UserMatchHistory cookie from linkedin.com is used to track users across multiple websites to deliver targeted advertising. It enables LinkedIn to understand a user's interactions with different websites over time, aiding in the synchronization and mapping of IDs between LinkedIn and its advertising partners. This process helps provide a more cohesive and tailored ad experience to users as they navigate various online platforms.
__cf_bm	hsforms.net	1 day	The __cf_bm cookie is used by Cloudflare, a content delivery network (CDN) and security service, to manage incoming traffic and protect websites from malicious bots. This cookie is specifically part of the bot management service provided by Cloudflare, which helps distinguish between legitimate users and automated bots. The __cf_bm cookie typically has a short lifespan and does not store any personal data; instead, it holds information necessary to identify and mitigate potentially harmful traffic.
_cfuvid	vimeo.com	Session	The _cfuvid cookie is used by Cloudflare as part of its security services. This cookie is set when a Cloudflare service, like Web Application Firewall (WAF), is protecting a website. It helps Cloudflare identify trusted web traffic and apply security settings for individual users, thereby preventing malicious attacks and enhancing site security. The _cfuvid cookie is generally used to maintain a secure session while users navigate the website, ensuring that legitimate users can access the site without interruptions while keeping potential threats at bay. It usually has a short lifespan and does not store any personally identifiable information.
_fbp	wpengine.com	90 days	The _fbp cookie is used by Facebook to deliver a range of advertising products, such as real-time bidding from third-party advertisers. It allows Facebook to track users across websites that utilize Facebook's advertising and analytics services, enabling the delivery of more relevant ads to users based on their online behaviors. WP Engine is a WordPress hosting service, and websites hosted on WP Engine might use Facebook's advertising services, leading to the presence of the _fbp cookie.
_ga	wpengine.com	35 days	The _ga cookie is used by Google Analytics to distinguish unique users by assigning a randomly generated identifier (a client ID) to each visitor. This cookie is included in every page request on a site using Google Analytics and is used to calculate visitor, session, and campaign data for the analytics reports of the website. The _ga cookie helps website owners analyze how visitors interact with their site, track user behavior over time, and make data-driven decisions to improve the user experience.
_ga_XXXXXXXXXX	wpengine.com	35 days	The _ga_XXXXXXXXXX cookie is part of Google Analytics and is used in conjunction with the main _ga cookie to track user behavior on a website. This specific cookie is part of Google Analytics "Google Analytics 4" (GA4) setup or might be associated with a specific property ID for Google Analytics in Universal Analytics. The structure _ga_XXXXXXXXXX typically represents a Google Analytics Measurement ID, which helps in tracking data specific to a particular property or environment. The cookie helps in distinguishing unique users and tracking their sessions across different pages, contributing to comprehensive analytics reporting.
_gcl_au	wpengine.com	90 days	The _gcl_au cookie, used by websites hosted on WP Engine and set by Google Analytics, is utilized to understand user interactions with ads. It helps in tracking conversions that can be attributed to ads on the Google Display Network and Google Ads. By capturing these interactions, website owners can measure the effectiveness of their ad campaigns and optimize them for better performance.
_GRECAPTCHA	google.com	180 days	The _GRECAPTCHA cookie is used by the reCAPTCHA service from Google to protect websites from spam and abuse. It helps distinguish between human users and bots by analyzing various signals during user interaction with a website. This cookie is set when reCAPTCHA is loaded on a website and is essential for maintaining security and preventing automated attacks or fraudulent activities.
__stid	.sharethis.com	1 day	The __stid cookie is used by ShareThis, a social sharing service that allows users to share content across various social media platforms. This cookie collects information about user navigation and preferences, primarily for the purpose of tracking and analytics. It helps ShareThis track the pages a user visits and the content they share, enabling the service to offer personalized content and targeted advertising based on user behavior across different websites.
__stidv	.sharethis.com	1 day	The __stidv cookie is also used by ShareThis, similar to the __stid cookie. It collects additional information related to user interactions and preferences on websites where the ShareThis widget is integrated. This cookie aids in tracking user navigation, content sharing, and preferences, allowing for enhanced analytics and personalized content recommendations. It contributes to the creation of user profiles for targeted advertising based on browsing behavior across different sites.

BTM-Series Battery Temperature & Thermal Runaway Monitor

Battery Monitoring Systems

Key Features

Specifications

Resources & Support

Product Literature

Support Documents

Video Resources

FAQs

Request Quote

Complete Your DC Power Solution

PRC-005-6 Battery Operation & Maintenance Compliance

BC-2500 Charger

Load Banks

get
Powerful

Sign Up

Tune In

Follow Us