pyDE1 0.0.1

Controller for Decent Espresso DE1

pyDE1

License

Copyright © 2021 Jeff Kletsky. All Rights Reserved.

License for this software, part of the pyDE1 package, is granted under

GNU General Public License v3.0 only

SPDX-License-Identifier: GPL-3.0-only

This code is work in progress. Although many features are working, as described in Section 15 and elsewhere of the GPLv3.0 LICENSE:

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

Overview

This represents work-in-progress to an API-first implementation of core software for a controller for the DE1.

The API is not stable at this time and is subject to change without notice.

This repo may have non-fast-forward commits.

Consumers should expect that there will be stable "inbound" (commands to the controller) and "outbound" (notification) APIs. At this time, the outbound payloads are expected to be JSON with a form similar to that being produced by the .as_json() method of the various subclasses of EventPayload. These are versioned, and the "wrapper" of default implementation(s) is planned on being versioned as well.

Ideally, the consumers of these APIs will only need to understand high-level actions, such as "Here is a profile blob, please load it." The operations and chioce of connectivity to the devices are planned on being "hidden" behind the APIs.

Revision History

2021-06-08 – Initial release

Requirements

Python 3.8 or later.

Available through pip:

• bleak
• aiologger

The Raspberry Pi version of Debian Buster ships with Python 3.7, which does not support named asyncio.Task() The "walrus operator" is also used.

Python 3.9 is expected to be part of Debian "next". Until that time https://github.com/pyenv/pyenv can be used to install a version of your choice. On a RPi 3B, a complete build too under 15 minutes.

Development work is being done on Buster with Python 3.9.5 on a RPI 3B at this time.

The bleak library is supported on macOS, Linux, and Windows. Some development has also been done under macOS.

What Seems To Be Working – High Level Functionality

• Connect by address to DE1
• Read and decode BLE characteristics
• Read and decode MMR registers
• Encode and write MMR registers
• Upload firmware
• Parse JSON profile (v2) and upload
• Connect by address to SkaleII
• Scale processing for weight and flow, including period estimation
• Stop-at-time
• Stop-at-volume
• Stop-at-weight
• Enable/disable "shot" logging

The main process runs under Python's native asyncio framework. There are many tutorials out there that make asynchronous programming look easy. "Hello world!" is always easy. For a better understanding, I found Lynn Root's asyncio: We Did It Wrong to be very insightful.

Work In Progress

• Confirm sufficiency of outgoing API with an MQTT-based approach in a separate process
• Implement notifcations for selected asyncio.Event() objects, such as the FlowSequencer "gates"
• Bring in find-first-matching functionality when available from release bleak
• Clean up the imports with likely a combination of pulling events and exceptions out, along with interface definitions.
• Documentation, including more doc strings, and typing
• Package for pip

Known Gaps

• Monitor and report BLE connectivity
• Manage unexpected disconnects and reconnects
• Abort actions, such as uploading a profile
• Timeouts on the locks and certain await actions
• Adding, removing, or replacing the DE1 or scale with the FlowSequencer
• Move to aiologger to reduce logging delays
• Develop an example "inbound" API implementation, probably REST-like with nginx over a pipe.

Notes

The code is littered with TODOs and personal notes. Ray may find his name mentioned with some loose thoughts about changes. These are loose thoughts worthy of some future discussion, not blockers and not direct requests!