BLE vs Classic Bluetooth: Which Radio Fits the Job

• BLE is built for short connection events and long sleep periods, so average current tracks how often it transmits.
• Classic Bluetooth (BR/EDR) holds a continuous link, which is why it carries live voice and streaming audio.
• BLE uses 40 channels of 2 MHz; Classic Bluetooth uses 79 channels of 1 MHz with fast frequency hopping.
• A serial-to-BLE module bridges a plain UART to GATT, not to the Classic serial port profile.
• Choose BLE for battery life and serial data, Classic Bluetooth for continuous audio and live voice.

1. What Is Bluetooth Low Energy (BLE)?

BLE is a 2.4 GHz wireless protocol for short, infrequent data exchanges at low average power, built around advertising and short connection events.

BLE arrived with the Bluetooth Core Specification, but it is not a slower version of the older radio. It is a separate link layer that shares the band, the brand and parts of the upper stack, and for a battery-powered sensor or serial bridge that distinction is the whole design conversation.

Core characteristics

• Duty cycle sets the current budget: the device sleeps most of the time and wakes for brief radio events, so average current follows how often it transmits.
• Attribute-based data model: data lives in attributes, read and written through the Attribute Protocol (ATT) and organised by the Generic Attribute Profile (GATT). A serial bridge hides that model behind a pipe.
• Forty channels of 2 MHz: 37 data channels and 3 advertising channels, with GFSK modulation at 1 Mbps on the LE 1M PHY, per the Bluetooth Core Specification.
• Connection events instead of a continuous link: connected devices meet at a negotiated connection interval and sleep in between.
• Small payloads per packet: throughput depends on the connection interval, packets per event and MTU.

2. How Does BLE Work?

BLE moves through a fixed sequence, from an invisible device to a link that carries application data.

1. Advertising on three channels. A peripheral sends advertising packets on the 3 advertising channels at 2402, 2426 and 2480 MHz, placed between the busiest Wi-Fi channels. A 20 ms to 100 ms advertising interval gives quick discovery; longer intervals protect the battery.
2. Scanning and the connection request. A central scans those channels, receives an advertising packet and may reply with a connection request carrying the access address and initial parameters. The link then hops across the 37 data channels.
3. Connection events and the connection interval. Both ends wake at each event and exchange at least one packet. The interval, commonly 7.5 ms to 4 s, sets the trade-off: short intervals lower latency and raise average current.
4. Attribute access through ATT and GATT. The central reads or writes attributes using ATT procedures, while GATT defines the services and characteristics they belong to. Notifications let the peripheral push data without polling.
5. Sleeping between events. Between events the radio is off, so latency tolerance maps straight into battery life.
6. PHY and payload options. The LE 2M PHY and data length extension raise usable payload per event on newer silicon.

3. What Is Classic Bluetooth (BR/EDR)?

Classic Bluetooth (BR/EDR) is the original Bluetooth radio, designed for continuous, higher-throughput links such as voice calls and audio streaming.

BR/EDR stands for Basic Rate and Enhanced Data Rate. It is what most people still mean by Bluetooth, and it uses the same 2.4 GHz band as BLE.

Core characteristics

• Two data rates, two modulations: Basic Rate carries 1 Mbps with GFSK, while Enhanced Data Rate raises the payload rate with a different modulation, per the Bluetooth Core Specification.
• Seventy-nine channels of 1 MHz: the band is divided more finely than in BLE and the link hops rapidly across it, sharing the band with other traffic.
• Piconet topology with a master: one master coordinates up to seven active slaves, with held or parked devices in reserve.
• Synchronous links for voice: SCO and eSCO reserve slots at fixed intervals, which is how a headset keeps a steady audio cadence.
• Profiles carry the application: the Serial Port Profile (SPP), A2DP and the hands-free profiles define use cases, and all belong to BR/EDR.
• A link that stays up: the connection is continuous, so average current runs far higher than BLE for the same sensor data.

4. BLE vs Classic Bluetooth: What Is the Difference?

BLE and Classic Bluetooth solve different problems in the same band, and the choice follows from whether the product needs audio-grade bandwidth or battery life.

The decision rule: choose BLE when the product runs on a battery and moves small amounts of data or bridges a serial port; choose Classic Bluetooth to carry live voice or continuous audio.

5. BLE Configuration and Key Parameters

A BLE link is the product of a handful of parameters, and each one fails in a recognisable way when it is set for the wrong job.

• Connection interval versus latency and current: 7.5 ms to 4 s, with 15 ms to 45 ms common. Short intervals cut latency and raise average current; long intervals do the reverse.
• Slave latency: a peripheral may skip connection events when it has nothing to send. That saves current and delays the first packet after idle, so slow-feeling links often carry high slave latency.
• Advertising interval: 20 ms to 100 ms gives fast discovery, while 1 s or more saves power. Advertising without connecting is the beacon pattern.
• Transmit power versus range in dBm: 0 dBm is a common default, with 4 dBm on many modules. Path loss grows by roughly 6 dB per doubling of distance, and extra power raises peak current.
• Receiver sensitivity: figures near -93 dBm to -97 dBm at LE 1M decide how much margin survives cable and enclosure loss. Good sensitivity tolerates a poorer antenna.
• UART baud rate on a serial-to-BLE bridge: 9600 bps to 115200 bps is the usual range and both ends must match. If the UART feeds bytes faster than the link carries them, the bridge drops data.
• MTU and payload size: a default ATT MTU of 23 bytes leaves 20 bytes of notification payload. A host that writes long frames without checking the negotiated MTU will truncate them.
• Antenna choice and enclosure loss: a PCB antenna is convenient and ground-plane sensitive, while a ceramic or IPEX antenna needs matching and a keep-out area. Metal, water and the body absorb 2.4 GHz energy.
• Coexistence with Wi-Fi in the same box: BLE and Wi-Fi share 2.4 GHz, so a crowded band raises retries. The symptom is throughput that collapses while the Wi-Fi radio is active.

6. When to Use BLE and When Not To

Good fit for BLE

• Battery-powered sensors and tags running for months on a coin cell.
• Serial bridges replacing a cable between a microcontroller and a gateway.
• Products configured by a phone app over a short, secure connection.
• Dense deployments, because short connection events leave airtime for other links.
• Meters, door contacts and tags that report occasionally.

Good fit for Classic Bluetooth

• Voice designs needing a synchronous channel through SCO or eSCO.
• Consumer audio streaming where A2DP is part of the product.
• Legacy equipment that already implements a BR/EDR profile.
• Products pairing into an ecosystem that supports Classic profiles.

Poor fit for BLE

• Continuous high-rate streaming such as uncompressed audio to a headset.
• Low-millisecond real-time response, because the connection interval sets a latency floor.
• Long-range outdoor links; BLE is short-range, and 120 m assumes clear line of sight.
• Hosts with no spare UART, SPI or USB port.
• Designs expecting SPP or A2DP, which BLE does not carry.

Poor fit for Classic Bluetooth

• Coin-cell products, where a continuous link exhausts the budget.
• Sensor nodes reporting every few minutes.
• Dense deployments of hundreds of small endpoints.
• Products with no audio and modest throughput needs.

7. Real-World Applications

In wearables, industrial sensing and asset tracking, BLE is usually the secondary radio: a node measures, stores and then wakes to advertise or notify. Serial bridging follows the same idea, giving a legacy controller with a UART a wireless link without firmware changes.

Ebyte's Bluetooth range is BLE. None of the modules listed here implement Classic Bluetooth, SPP, A2DP or audio, so they suit sensor data, configuration and serial bridging rather than headsets.

For a compact sensor node, the E104-BT53A3 is a small SMD Bluetooth 5.2 module based on the Silicon Labs EFR32BG22C224F512GM32, covering 2402 to 2480 MHz with GFSK, a 120 m reference distance and a 13 x 19 mm footprint, with a 38.4 MHz industrial low-temperature-drift crystal oscillator. The E104-BT53A1 uses the same Silicon Labs EFR32BG22 family, with a 120 m figure and a low-power design.

For serial bridging, the E104-BT5032A is a serial-to-BLE module based on the Nordic nRF52832, BLE 5.0, 2.402 to 2.480 GHz, working as master and slave, with a 60 m figure and a high-gain ceramic antenna. Where the device acts as a peripheral, the E104-BT51A is a serial-port-to-BLE slave node module based on the TI CC2640R2L, Bluetooth 5.0, with a 50 m reference distance in a clear open environment and a 16 x 11.5 mm PCB antenna.

The E104-BT5011A covers designs needing either role over a longer link: a serial-to-BLE master and slave module based on the Nordic nRF52811, BLE 5.1, 2.402 to 2.480 GHz, 70 m, 11.5 x 16 mm, with an absolute maximum supply voltage of 3.6 V. Teams writing their own application logic can start from the E73-2G4M04S1A, a Nordic nRF52810 module, BLE 4.2 and 5.0, supplied without firmware, with a 1.8 to 3.6 V supply range.

The reference distances above assume clear line of sight, and 120 m will not survive a metal enclosure or a body in the path. Antenna choice and keep-out area affect installed range more than module choice.

8. FAQ: BLE in Practice

Q1: What is the difference between BLE and Classic Bluetooth?

BLE is built around short, periodic connection events for low average power, while Classic Bluetooth maintains a continuous link for higher sustained throughput. BLE suits sensors, tags and serial bridges; Classic Bluetooth suits voice headsets and live audio. Both share the 2.4 GHz band but are separate radio designs.

Q2: How fast is BLE compared with Classic Bluetooth?

BLE typically delivers tens to a few hundred kbps of application throughput, set by connection interval, packets per event and MTU. Classic Bluetooth sustains much higher rates, which is why it carries audio. A BLE 5 module with a 2M PHY improves the figure without reaching streaming rates.

Q3: Why is my BLE link dropping or running slow?

Start with the connection parameters, then the RF path.

• Bursty data that stalls → the connection interval is too long.
• Throughput collapsing when Wi-Fi runs → coexistence; review the channel map and antenna placement.
• Drops at range but not on the bench → enclosure loss or a blocked antenna.
• Bytes lost on a serial bridge → baud rate mismatch or MTU overflow.

Q4: Can BLE carry audio or replace SPP?

No. Classic Bluetooth carries voice over SCO and eSCO links and audio through profiles such as A2DP. BLE has no equivalent classic voice channel, and the Serial Port Profile belongs to BR/EDR. A serial-to-BLE bridge emulates a serial cable through GATT, which is a different mechanism.

Q5: How far does BLE reach, and what limits the range?

BLE is a short-range radio, and a 120 m reference distance applies to clear line of sight, so ordinary indoor links are much shorter. Transmit power, receiver sensitivity, antenna gain and enclosure loss set the budget, and walls or a body between the two ends reduce it further.

Q6: What is the easiest way to add BLE to a device that has a UART?

Use a serial-to-BLE module and treat it as a transparent pipe. A peripheral module such as the E104-BT51A takes UART data and exposes it over a GATT characteristic, so the host firmware needs no Bluetooth stack. Match the baud rate and confirm the MTU before sending long frames.

9. Practical Checklist Before You Choose the Radio

1. Start from the power budget, not the data rate. If the product survives on a coin cell, the continuous link of Classic Bluetooth rules it out before throughput is discussed.
2. Decide early whether live voice or audio is in scope. If it is, plan for Classic Bluetooth or LE Audio; if not, BLE covers sensing, configuration and serial data.
3. Set the connection interval from the application, then re-measure current. Latency and average current move together, so validate both on hardware.
4. Budget the RF path, not just the module. Antenna type, keep-out area and enclosure material decide installed range more often than the module datasheet does.
5. On a serial bridge, match baud rate, frame format and MTU before shipping. Most bridge faults turn out to be configuration mismatches.