Publishing sensor data in Raspberry Pi - Step-by-Step Execution

Concept Flow - Publishing sensor data

Initialize sensor

↓

Read sensor data

↓

Format data for sending

↓

Connect to network/broker

↓

Publish data

↓

Wait or repeat

The program starts by setting up the sensor, then reads data, formats it, connects to the network, publishes the data, and repeats.

Execution Sample

Raspberry Pi

import time
import random

def read_sensor():
    return random.uniform(20.0, 30.0)

while True:
    data = read_sensor()
    print(f"Publishing temperature: {data:.2f} C")
    time.sleep(2)

This code simulates reading temperature data from a sensor and publishes it by printing every 2 seconds.

Execution Table

Step	Action	Sensor Data	Formatted Data	Output	Wait
1	Initialize sensor	N/A	N/A	N/A	N/A
2	Read sensor data	24.57	24.57 C	Publishing temperature: 24.57 C	Sleep 2s
3	Read sensor data	29.12	29.12 C	Publishing temperature: 29.12 C	Sleep 2s
4	Read sensor data	21.03	21.03 C	Publishing temperature: 21.03 C	Sleep 2s
5	Read sensor data	27.89	27.89 C	Publishing temperature: 27.89 C	Sleep 2s
6	Read sensor data	22.45	22.45 C	Publishing temperature: 22.45 C	Sleep 2s
...	Repeat reading and publishing	...	...	...	...

💡 Loop runs indefinitely, reading and publishing sensor data every 2 seconds.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	...final
data	N/A	24.57	29.12	21.03	27.89	22.45	...

Key Moments - 3 Insights

Why do we format the sensor data before publishing?

Formatting the data (like adding units) makes it clear and readable in the output, as shown in execution_table rows 2-5 where 'Formatted Data' includes 'C' for Celsius.

Why is there a sleep or wait after publishing?

The sleep pauses the program so it doesn't flood the network with data too fast. Execution_table shows 'Sleep 2s' after each publish to control timing.

What happens if the sensor reading fails or returns unexpected data?

In this simple example, sensor data is simulated and always valid. In real cases, you would add error checks before publishing to avoid sending wrong data.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the sensor data value?

A 24.57

B 29.12

C 21.03

D 27.89

💡 Hint

Check the 'Sensor Data' column in execution_table row with Step 3.

At which step does the program wait for 2 seconds before reading again?

A After every publish step

B Step 1

C Step 5

D Step 2

💡 Hint

Look at the 'Wait' column in execution_table; it shows 'Sleep 2s' after each publish.

If the sensor data was not formatted before publishing, what would change in the output?

A Program would crash

B Output would include extra text

C Output would show raw numbers without units

D Sleep time would increase

💡 Hint

Refer to 'Formatted Data' and 'Output' columns in execution_table to see the effect of formatting.

Concept Snapshot

Publishing sensor data:
1. Initialize sensor
2. Read data
3. Format data (add units)
4. Connect and publish
5. Wait before next read
Repeat continuously

Full Transcript

This example shows how a Raspberry Pi program reads sensor data, formats it with units, publishes it by printing, and waits 2 seconds before repeating. The flow starts with sensor initialization, then reading data, formatting it, publishing, and waiting. Variables like 'data' change each read. Formatting helps make output clear. The sleep controls timing to avoid flooding. The loop runs forever, simulating continuous sensor publishing.