Real-time sensor dashboard in Raspberry Pi - Step-by-Step Execution

Concept Flow - Real-time sensor dashboard

Start Program

↓

Initialize Sensors

↓

Read Sensor Data

↓

Update Dashboard Display

↓

Wait Short Time

↓

Repeat Reading & Updating

↩Back to Read Sensor Data

The program starts, sets up sensors, reads data repeatedly, updates the dashboard, waits briefly, and repeats until stopped.

Execution Sample

Raspberry Pi

import time
from gpiozero import CPUTemperature
cpu = CPUTemperature()
while True:
    temp = cpu.temperature
    print(f"CPU Temp: {temp:.1f} C")
    time.sleep(1)

This code reads the CPU temperature every second and prints it to the screen.

Execution Table

Step	Action	Sensor Reading	Dashboard Output	Wait Time (s)
1	Initialize CPU temperature sensor	N/A	Dashboard ready	0
2	Read CPU temperature	45.3	CPU Temp: 45.3 C	1
3	Read CPU temperature	45.5	CPU Temp: 45.5 C	1
4	Read CPU temperature	45.4	CPU Temp: 45.4 C	1
5	Read CPU temperature	45.6	CPU Temp: 45.6 C	1
6	Read CPU temperature	45.7	CPU Temp: 45.7 C	1
...	Repeat reading and updating	...	...	1
Exit	Program stopped by user	N/A	Dashboard stopped	0

💡 User stops the program manually, ending the loop.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
temp	N/A	45.3	45.5	45.4	45.6	45.7	N/A (program stopped)

Key Moments - 3 Insights

Why does the dashboard update every second instead of continuously?

The program uses time.sleep(1) to pause for 1 second after each reading, which controls update speed and avoids overloading the CPU (see execution_table rows 2-6).

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

In this simple example, no error handling is shown, so the program might crash or print incorrect data. Real dashboards should check sensor data before updating (not shown here).

Why is the variable 'temp' updated each loop iteration?

Each loop reads a new sensor value and stores it in 'temp', replacing the old value (see variable_tracker). This keeps the dashboard showing the latest data.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the CPU temperature reading?

A 45.5

B 45.3

C 45.4

D 45.6

💡 Hint

Check the 'Sensor Reading' column in execution_table row 3.

At which step does the program wait before reading the sensor again?

A Step 1

B Step 2

C Step 6

D Every step after reading

💡 Hint

Look at the 'Wait Time (s)' column; it shows 1 second wait after each reading.

If the time.sleep(1) line is removed, how would the variable_tracker change?

A temp would update faster, possibly many times per second

B temp would never update

C temp would stay the same as start value

D temp would update only once

💡 Hint

Without waiting, the loop runs continuously, updating 'temp' rapidly (see variable_tracker changes).

Concept Snapshot

Real-time sensor dashboard:
- Initialize sensors
- Loop: read sensor data
- Update display with new data
- Pause briefly (e.g., 1 second)
- Repeat until stopped
Use time.sleep() to control update speed.

Full Transcript

This example shows a real-time sensor dashboard on a Raspberry Pi. The program starts by initializing the CPU temperature sensor. Then it enters a loop where it reads the temperature, prints it to the dashboard, waits one second, and repeats. The variable 'temp' holds the latest temperature reading and updates each loop. The dashboard updates every second to show fresh data. The program stops when the user interrupts it. This simple flow helps beginners see how sensor data can be read and displayed continuously with pauses to avoid overloading the system.