Book Image

MicroPython Projects

By : Jacob Beningo
Book Image

MicroPython Projects

By: Jacob Beningo

Overview of this book

With the increasing complexity of embedded systems seen over the past few years, developers are looking for ways to manage them easily by solving problems without spending a lot of time on finding supported peripherals. MicroPython is an efficient and lean implementation of the Python 3 programming language, which is optimized to run on microcontrollers. MicroPython Projects will guide you in building and managing your embedded systems with ease. This book is a comprehensive project-based guide that will help you build a wide range of projects and give you the confidence to design complex projects spanning new areas of technology such as electronic applications, automation devices, and IoT applications. While building seven engaging projects, you'll learn how to enable devices to communicate with each other, access and control devices over a TCP/IP socket, and store and retrieve data. The complexity will increase progressively as you work on different projects, covering areas such as driver design, sensor interfacing, and MicroPython kernel customization. By the end of this MicroPython book, you'll be able to develop industry-standard embedded systems and keep up with the evolution of the Internet of Things.
Table of Contents (14 chapters)
11
Downloading and Running MicroPython Code

Chapter 3

  1. What is a high-level system diagram called?
    • A block diagram
  2. What is a detailed hardware diagram called?
    • A schematic or wiring diagram
  3. What three diagrams did we use in this chapter to define our software architecture?
    • An application flowchart
    • A state diagram
    • A class diagram
  4. What is it called when two classes are connected together without the use of the inheritance mechanism?
    • Composition
  5. What information should be included in a test case?
    • The test case number.
    • The test case objective (why are we doing the test?)
    • Conditions that need to occur before the test is performed.
    • Input that needs to be applied to the system during testing (push a button).
    • Expected results (what should we see happen?)
    • Who did the testing? (yes, who can we blame if we discover a problem in the future?)
    • When was the test performed?
    • The software version number that the test is to be...