Bluetooth Low Energy, from the radio up · check

Know Over the air already?

One question for each of the 5 puzzles in this module. A right answer marks that puzzle as passed, so you can jump ahead. A wrong one tells you which puzzle to start with. Nothing is sent anywhere: it's saved in this browser.

Puzzle 0: A year on a coin battery

A strap's battery is nearly empty after two days instead of months. What's the most likely cause?

Not quite. Any coin battery would drain like that; what decides it is how long the radio is awake. Learn it in puzzle 0 →

Not quite. BLE is built for coin-sized batteries: the size isn't the problem, how long the radio is on is. Learn it in puzzle 0 →

Right. Battery life is decided by how much of the time the radio is on.

Puzzle 1: Shouting into the room

You shorten a strap's advertising interval from 1 s to 100 ms. What changes?

Right. Advertise often to be found fast; rarely to last long.

Not quite. More advertisements give the phone more chances to hear one, so finding gets faster. Learn it in puzzle 1 →

Not quite. Every advertisement wakes the radio. Ten times as many means ten times the radio time. Learn it in puzzle 1 →

Puzzle 2: A timetable for two

A heart strap's connection interval is 1 s. Your app shows the heart rate. What does the user notice?

Not quite. Packets only travel at connection events; between them both radios sleep. Learn it in puzzle 2 →

Right. Data can only move when the two sides meet.

Not quite. Anything up to 4 s is allowed. It's slow, not broken. Learn it in puzzle 2 →

Puzzle 3: The filing cabinet

Your app works with one brand of heart strap. A different brand also offers the standard Heart Rate service. What does your app need to change to read it?

Right. Standard services share UUIDs across brands.

Not quite. Timing has nothing to do with where the value lives; the UUIDs do. Learn it in puzzle 3 →

Not quite. The standard service and characteristic have the same UUIDs on every device that offers them. Learn it in puzzle 3 →

Puzzle 4: Don't ask, get told

Your app calls setCharacteristicNotification(characteristic, true) and nothing else. The heart rate changes. What arrives?

Not quite. No notifications are sent at all until the CCCD is written. Learn it in puzzle 4 →

Not quite. That call only prepares your own phone. The strap starts sending only when its CCCD is written. Learn it in puzzle 4 →

Right. Two steps: your phone, and the switch on the strap.

Back to the overview →