6 — BLE Basics
Bluetooth 4.0+
Coin Cell (years)
Ultra Low Power
What Is Bluetooth Low Energy?
Hello students welcome to this bluetooth low energy development course, this is part of our free embedded systems course, so let us start this BLE development course , so what is Bluetooth Low Energy — shortened to BLE or LE — is a big shift in what Bluetooth technology is meant to do. All the classic Bluetooth versions that came before were focused on either adding more features or pushing data faster. BLE went in a completely different direction: how do you make a wireless technology that barely uses any power at all?
The reason this matters is that many of the most useful wireless devices in everyday life run on tiny batteries — the kind you find inside a watch or a key fob. These devices cannot be recharged every week. They need to run for months or even years on a single battery. Classic Bluetooth was simply not designed for that. BLE was built from scratch with that exact goal in mind.
BLE is not a small patch on top of classic Bluetooth. It is a thorough redesign of the radio, the packet format, the connection process, and the protocol stack — all aimed at one thing: using as little energy as possible while still being reliable and secure.
Why Power Consumption Is the Central Problem
BLE addresses power from two angles that are both important:
This is what determines how long your battery lasts. A lower average current means the battery drains more slowly, giving you months or years of use instead of days. BLE achieves this by keeping the radio off almost all the time and only switching it on in brief bursts to send data.
As a battery ages and starts to run down, it can deliver less maximum current. If a device needs a large burst of current to operate, it may stop working even while the battery still has charge left. By keeping peak current low, BLE devices continue working right up until the battery is genuinely empty.
Think of it this way: a device with high peak current demand is like a car that sometimes needs to floor the accelerator. An old or weak battery cannot keep up. A BLE device is designed to never floor the accelerator — it moves slowly and steadily, getting much further on the same tank.
The Two Bluetooth Systems — BR/EDR and LE
Classic Bluetooth is officially called BR/EDR, which stands for Basic Rate / Enhanced Data Rate. This tells you something about its two operating modes:
- BR (Basic Rate): The original mode, supporting up to 721 kbps of data throughput. Used for things like audio streams and serial port connections.
- EDR (Enhanced Data Rate): An improvement that raises the ceiling to 2.1 Mbps, used for faster file transfers and higher-quality audio.
Any device running on a version of Bluetooth older than 4.0 is a BR/EDR device. This includes almost every Bluetooth headset, keyboard, mouse, and file-sharing device sold before 2012.
BLE is defined in Bluetooth specification version 4.0 and later. It is a completely separate radio system from BR/EDR — different channels, different packets, different connection mechanism, different protocol stack. BLE deliberately trades throughput for power efficiency:
- Bluetooth 4.0: Maximum data rate of approximately 305 kbps
- Bluetooth 4.2: Improved to approximately 800 kbps
These numbers sound slow compared to BR/EDR, but that is the point. BLE use cases — a heart rate monitor, a temperature sensor, a door lock — do not need to send megabytes of data. They need to send a few bytes, reliably, as infrequently as possible.
Three Types of Bluetooth Devices
Every Bluetooth device on the market falls into one of three categories based on which radio(s) it includes. Understanding this is important because it determines what other devices it can communicate with.
BR/EDR
These have only the classic Bluetooth radio and cannot communicate with BLE devices at all. Most Bluetooth gear made before 2012 falls here — older headsets, older laptops, older game controllers. They are still functional for their original purpose but cannot participate in the BLE ecosystem.
LE Only
These have only the BLE radio — no classic Bluetooth at all. They are purpose-built for ultra-low power scenarios. Examples include: wrist watches, key fobs, heart rate monitors, thermometers, glucose monitors, step counters, and industrial sensors. A coin cell battery can power these devices for several years because the radio spends almost all its time completely off.
Dual Mode
These have both radios and can talk to both classic Bluetooth and BLE devices — sometimes simultaneously. Modern smartphones, tablets, laptops, and smart TVs are dual-mode. They do not have strict power constraints because they use large batteries or are plugged into mains power. Their role in the BLE ecosystem is to act as hubs that collect data from sensors and send it to the internet.
Device Compatibility Table
This is one of the most important things to understand when designing a Bluetooth system. Not all device types can communicate with each other.
| BR/EDR Device |
Single Mode LE Device |
Dual Mode Device |
|
|---|---|---|---|
| BR/EDR Device | ✅ YES | ❌ NO | ✅ YES |
| Single Mode LE | ❌ NO | ✅ YES | ✅ YES |
| Dual Mode | ✅ YES | ✅ YES | ✅ YES |
Key insight: Classic-only and LE-only devices cannot communicate with each other at all. The only device type that can bridge them is the Dual Mode device. This is why a smartphone (dual mode) can connect to both your Bluetooth headset (classic) and your fitness tracker (LE only) at the same time.
Real-World Dual Mode Use Cases
Dual mode devices unlock combinations that neither classic-only nor BLE-only devices could achieve alone. Here are four practical examples:
Communication Examples by Device Type
Notice that the most powerful pattern is LE sensor → Dual Mode hub → Internet. The sensor is cheap, runs forever on a battery, and just sends small data packets. The smartphone is always connected to Wi-Fi and the internet, and acts as the bridge. This architecture powers billions of IoT deployments today.
Checking BLE Support in Linux with BlueZ
Once you understand device types, the first practical question is: does your Linux Bluetooth adapter support BLE? Here is how to check using BlueZ tools:
# Check your adapter's Bluetooth version and capabilities
hciconfig -a
# Look for "HCI Version: 4.0" or higher in the output.
# HCI Version 4.0+ means the adapter supports BLE.
# Example output:
# hci0: Type: BR/EDR Bus: USB
# HCI Version: 4.0 (0x6) Revision: 0x1d86
# LMP Version: 4.0 (0x6) Subversion: 0x1d86
# Manufacturer: Cambridge Silicon Radio (10)# Scan specifically for BLE (LE) devices — different from classic scan
# hcitool scan → scans for classic BR/EDR devices
# hcitool lescan → scans for BLE advertising packets
sudo hcitool lescan
# Output looks like:
# LE Scan ...
# 00:1A:7D:DA:71:13 (unknown)
# 18:B4:30:B9:6A:E6 Nest-Protect
# 7C:2F:80:BE:04:D9 Polar H7# Check if the adapter is in the right mode for BLE scanning
# Using bluetoothctl (the modern BlueZ interface)
bluetoothctl
# Inside bluetoothctl:
power on
scan on
# This starts scanning for both classic and BLE devicesIf hcitool lescan returns “LE not supported” your adapter is older than Bluetooth 4.0 and cannot do BLE. You need a 4.0+ USB dongle. These are inexpensive and widely available.
Chapter 6 — Part 1 Complete
You understand what BLE is, the three device types, and which ones can communicate. Next: Bluetooth Smart trademarks and the core LE technical fundamentals.