Book Image

Practical Python Programming for IoT

By : Gary Smart
Book Image

Practical Python Programming for IoT

By: Gary Smart

Overview of this book

The age of connected devices is here, be it fitness bands or smart homes. It's now more important than ever to understand how hardware components interact with the internet to collect and analyze user data. The Internet of Things (IoT), combined with the popular open source language Python, can be used to build powerful and intelligent IoT systems with intuitive interfaces. This book consists of three parts, with the first focusing on the "Internet" component of IoT. You'll get to grips with end-to-end IoT app development to control an LED over the internet, before learning how to build RESTful APIs, WebSocket APIs, and MQTT services in Python. The second part delves into the fundamentals behind electronics and GPIO interfacing. As you progress to the last part, you'll focus on the "Things" aspect of IoT, where you will learn how to connect and control a range of electronic sensors and actuators using Python. You'll also explore a variety of topics, such as motor control, ultrasonic sensors, and temperature measurement. Finally, you'll get up to speed with advanced IoT programming techniques in Python, integrate with IoT visualization and automation platforms, and build a comprehensive IoT project. By the end of this book, you'll be well-versed with IoT development and have the knowledge you need to build sophisticated IoT systems using Python.
Table of Contents (20 chapters)
1
Section 1: Programming with Python and the Raspberry Pi
6
Section 2: Practical Electronics for Interacting with the Physical World
9
Section 3: IoT Playground - Practical Examples to Interact with the Physical World

Discussion of APA102 and the SPI interface

If you cast your mind back to Chapter 5, Connecting Your Raspberry Pi to the Physical World, where we discussed Serial Peripheral Interface (SPI), you may remember that we mentioned it uses four wires for data transfer. However, if you consider our circuit in Figure 8.6, we're only using two wires (DI and CI), not four. What's going on?

Here is the SPI mapping for the APA102:

  • Master-Out-Slave-In (MOSI) on your Raspberry Pi connects to Data In (DI) on the APA102. Here, your Raspberry Pi is the master sending data to the slave APA102 LEDs on the strip.
  • Master-In-Slave-Out (MISO) is not connected because the APA102 does not need to send data back to the Raspberry Pi.
  • SCLK on your Raspberry Pi connect to the Clock In (CI) on the APA102.
  •  Client Enable/Slave Select (CE/SS) is not connected.

The last line CE/SS of importance and worthy of further discussion. A CE/SS channel is used by a master device to tell a specific...