BLE connection and data exchange in IOT Protocols - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start scanning for BLE devices.

IOT Protocols

ble_scanner.start_scan([1])

Drag options to blanks, or click blank then click option'

Aduration=5

Bscan_time=15

Ctimeout=10

Dinterval=20

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names like timeout or interval.

The start_scan method uses duration to specify how long to scan in seconds.

2fill in blank

medium

Complete the code to connect to a BLE device using its address.

IOT Protocols

device = ble.connect([1])

Drag options to blanks, or click blank then click option'

Adevice_uuid

Bdevice_name

Cdevice_address

Ddevice_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using device name instead of address.

BLE devices are connected using their unique device_address.

3fill in blank

hard

Fix the error in the code to read data from a BLE characteristic.

IOT Protocols

data = device.read_characteristic([1])

Drag options to blanks, or click blank then click option'

Aservice_uuid

Bcharacteristic_uuid

Cdevice_address

Ddevice_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using service UUID instead of characteristic UUID.

To read data, you must specify the characteristic_uuid, not the service or device identifiers.

4fill in blank

hard

Fill both blanks to write data to a BLE characteristic.

IOT Protocols

device.write_characteristic([1], [2])

Drag options to blanks, or click blank then click option'

Acharacteristic_uuid

Bdata_bytes

Cservice_uuid

Ddevice_address

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping characteristic UUID with service UUID or device address.

The first argument is the characteristic_uuid to write to, and the second is the data_bytes to send.

5fill in blank

hard

Fill all three blanks to subscribe to notifications from a BLE characteristic.

IOT Protocols

device.subscribe([1], callback=[2], enable=[3])

Drag options to blanks, or click blank then click option'

Acharacteristic_uuid

Bnotification_handler

CTrue

Dservice_uuid

Attempts:

3 left

💡 Hint

Common Mistakes

Using service UUID instead of characteristic UUID.

Forgetting to enable notifications.

To subscribe, provide the characteristic_uuid, a callback function to handle notifications, and set enable to True.

Practice

1. What is the main purpose of Bluetooth Low Energy (BLE) in device communication?

easy

A. To connect devices using low power for short-range communication

B. To provide high-speed internet access

C. To replace Wi-Fi for long-distance communication

D. To increase battery consumption for faster data transfer

Solution

1. Step 1: Understand BLE's design goal

   BLE is designed to use very little power to connect devices nearby.

2. Step 2: Compare options

   Only To connect devices using low power for short-range communication correctly states BLE's purpose as low power and short range.

3. Final Answer:

   To connect devices using low power for short-range communication -> Option A

4. Quick Check:

   BLE = low power short range [OK]

Hint: Remember BLE saves battery by using low power [OK]

Common Mistakes:

• Confusing BLE with Wi-Fi
• Thinking BLE is for long-distance
• Assuming BLE uses high power

2. Which of the following is the correct sequence to establish a BLE connection and exchange data?

easy

A. Connect, scan, exchange data, disconnect

B. Scan, connect, exchange data, disconnect

C. Exchange data, connect, scan, disconnect

D. Disconnect, scan, connect, exchange data

Solution

1. Step 1: Recall BLE connection steps

   The device must first scan to find others, then connect, exchange data, and finally disconnect.

2. Step 2: Match the correct order

   Only Scan, connect, exchange data, disconnect follows the correct order: scan, connect, exchange data, disconnect.

3. Final Answer:

   Scan, connect, exchange data, disconnect -> Option B

4. Quick Check:

   Scan before connect [OK]

Hint: Scan first to find devices, then connect [OK]

Common Mistakes:

• Trying to connect before scanning
• Exchanging data before connecting
• Disconnecting before data exchange

3. Given this Python-like pseudocode for BLE data exchange, what will be printed?

device = BLEDevice()
device.scan()
device.connect()
data = device.read_characteristic('temp')
print(data)

medium

A. Nothing, because read_characteristic() returns None

B. An error because scan() is called after connect()

C. The temperature value read from the device

D. A connection timeout error

Solution

1. Step 1: Analyze the code sequence

   The code scans, connects, then reads a characteristic named 'temp'. This is the correct order.

2. Step 2: Understand read_characteristic output

   Assuming the device has a 'temp' characteristic, it returns the temperature value, which is printed.

3. Final Answer:

   The temperature value read from the device -> Option C

4. Quick Check:

   Correct order means data is read successfully [OK]

Hint: Scan then connect before reading data [OK]

Common Mistakes:

• Assuming scan after connect is wrong here
• Thinking read_characteristic returns None by default
• Expecting errors without connection issues

4. You wrote this BLE connection code but get an error: device.connect() fails. What is the likely mistake?

device = BLEDevice()
device.connect()
device.scan()
data = device.read_characteristic('humidity')

medium

A. Using wrong characteristic name

B. Reading characteristic before connecting

C. Not disconnecting after data exchange

D. Calling connect() before scan() to find devices

Solution

1. Step 1: Check method order

   The code calls connect() before scan(), so the device doesn't know which device to connect to.

2. Step 2: Understand BLE connection flow

   Scanning is needed first to discover devices, then connect can succeed.

3. Final Answer:

   Calling connect() before scan() to find devices -> Option D

4. Quick Check:

   Scan first, then connect [OK]

Hint: Always scan before connect to avoid errors [OK]

Common Mistakes:

• Connecting without scanning first
• Reading data before connection
• Ignoring disconnect step

5. You want to optimize BLE data exchange to minimize power use. Which approach is best?

hard

A. Scan and connect only when needed, exchange data quickly, then disconnect

B. Keep the connection open continuously and send data frequently

C. Send large data packets slowly over a long connection

D. Avoid disconnecting to reduce reconnection overhead

Solution

1. Step 1: Understand BLE power use

   Keeping connections open uses more power; scanning and connecting only when needed saves battery.

2. Step 2: Evaluate options for power efficiency

   Scan and connect only when needed, exchange data quickly, then disconnect minimizes connection time and power by scanning, connecting, exchanging data quickly, then disconnecting.

3. Final Answer:

   Scan and connect only when needed, exchange data quickly, then disconnect -> Option A

4. Quick Check:

   Minimize connection time to save power [OK]

Hint: Connect only when needed, then disconnect fast [OK]

Common Mistakes:

• Keeping connection open wastes power
• Sending data slowly prolongs connection
• Avoiding disconnect increases battery drain