i75
A wrapper around Pimoroni's interstate75 library which allows for running locally and easier testing.
This library provides a module, i75, which contains additional useful functionality over what is provided by MicroPython
and the Pimoroni libraries. For full details, please read the documentation.
This library also provides a script, i75, which is used when running programs on a normal PC for testing purposes.
This is done by a set of modules which replicate the functionality of the native Interstate75(W) hardware, in particular
using PyGame to represent a Hub75 LED matrix.
This emulation is far from perfect but hopefully allows a quicker development cycle than deploying to the physical hardware. In particular, problems may include:
- Full Python3.x is used, so syntactic and semantic differences with MicroPython won't be picked up.
- Your PC is many times more powerful than the RP2040 chip, so CPU limits won't be picked up.
- Our emulation of built-in functionality may be incomplete or incorrect.
- Sensors or additional hardware are not emulated.
Any help improving these limitations is most welcome. Please see CONTRIBUTING.md for more details.
Installation
To install this library either check it out from GitHub or install it from PyPI.
git checkout https://github.com/andrewjw/i75.git
cd i75
sudo python3 setup.py install
or
pip3 install i75
Running On A PC
To run your script simply follow i75 with the path to your script. There are examples provided in the examples
directory, which can be run as follows.
i75 examples/clock/clock.py
Running On Interstate75
To install the library on your Interstate75 run install.sh. This will create an i75 directory on the Raspberry Pi
Zero, and copy across the required files.
Install your script in the normal way, e.g.
ampy examples/clock/clock.py main.py
For ampy to work you need to tell it the correct device to use to communicate with Raspberry Pi Pico. To do that either
run install.sh -p /dev/tty.usbmodemN or set the AMPY_PORT environment details. For more details about ampy,
check out their documentation.
1 maintainer
Metadata
1 maintainer
Release files for i75 1.17.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| i75-1.17.0.tar.gz | 32.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| i75-1.17.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 86.7 kB
Release files / i75-1.17.0.tar.gz
| Download URL | i75-1.17.0.tar.gz |
|---|---|
| Size | 32.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7501c99e0476b503a3cb2661efa541506652a82b98ba1646a913986810bff3e5
|
|
BLAKE2b-256 checksum How to use checksums |
96979fd31306380f19a4cc193199e108e43fdfc5e5feabe51601f692e37dc084
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.10
|
Release files / i75-1.17.0-py3-none-any.whl
| Download URL | i75-1.17.0-py3-none-any.whl |
|---|---|
| Size | 54.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc33884f959071a6e2a8025821cfb239576b5b25568f0bf77b1f3d08ea29ff32
|
|
BLAKE2b-256 checksum How to use checksums |
4d880f9269b39ec5e54e8958a9116dc60cbef19863c2d4b25712868cb813a4fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.10
|
Security for i75 1.17.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
