A previous release had provenance metadata, but this release does not. View details.
raspiarduninoAI
Hopper gate valve + telescope control integration with holographic GUI.
Auto-detects and connects to Arduino/MKS Gen 1.4 boards by default!
Installation
Core install
pip install raspiarduninoai
GUI install
pip install "raspiarduninoai[gui]"
Local development install
pip install -e ".[dev,gui]"
Quick Start
Default Mode (Auto-detect Hardware)
Simply run the GUI - it will automatically detect and connect to Arduino boards:
raspiarduninoai-gui
The system will:
- 🔍 Auto-detect connected Arduino/MKS Gen 1.4 boards
- ⚡ Connect to detected boards automatically
- 📊 Start monitoring sensors in real-time
- 🔄 Fall back to simulation mode if no hardware found
List Available Ports
raspiarduninoai-gui --list-ports
Simulation Mode (No Hardware)
Force simulation mode for testing without hardware:
raspiarduninoai-gui --mock
Manual Port Specification
Override auto-detection and specify ports manually:
# Specify gate port only
raspiarduninoai-gui --gate-port /dev/ttyUSB0
# Specify both ports
raspiarduninoai-gui --gate-port /dev/ttyUSB0 --tele-port /dev/ttyUSB1
For detailed hardware setup instructions, see HARDWARE_SETUP.md
Usage
This library provides a policy-based control system for managing a hopper gate valve based on sensor inputs (ultrasonic distance, dust detection, PIR motion).
Holographic GUI
Launch the holographic GUI interface for real-time monitoring and control:
raspiarduninoai-gui
Features:
- 🌟 Futuristic holographic design with neon cyan/purple theme
- 📊 Real-time sensor monitoring with animated circular gauges
- 🎮 Manual control interface for gate operations
- 🚨 Live alert notifications and system status
- 📝 Real-time system log with color-coded messages
- ⚡ Smooth animations and visual effects
The GUI provides:
- Sensor Telemetry Panel: Live gauges showing material level and gate status
- System Status Panel: Detailed sensor readings and active alerts
- Manual Controls Panel: Buttons to open/close gate and simulate sensor events
- System Log: Real-time logging of all system events
Basic Example
from core import build_default_core
from policies import PolicyConfig, PolicyEngine
# Implement the hardware interface
class MyHardware:
def send_gate(self, command: str) -> None:
# Send command to gate controller
print(f"Gate: {command}")
def send_tele(self, command: str) -> None:
# Send command to telescope controller
print(f"Telescope: {command}")
# Create the control system
hardware = MyHardware()
core = build_default_core(hardware=hardware, logger=print)
# Process sensor data
sensor_payload = {
"board_id": "GATE_001",
"timestamp": 12345,
"sensors": {
"ultrasonic_mm": 450, # Material level
"dust": False,
"pir_motion": False,
"gate_open": True
}
}
decision = core.on_sensor_payload(sensor_payload)
Custom Policy Configuration
from policies import PolicyConfig
# Configure custom thresholds and behaviors
config = PolicyConfig(
stale_after_s=5.0, # Consider data stale after 5 seconds
low_material_distance_mm=500, # Close gate when material < 500mm
close_on_dust=True, # Close gate on dust detection
close_on_motion=True # Close gate on PIR motion
)
policy_engine = PolicyEngine(config)
core = HopperCore(hardware=hardware, policy_engine=policy_engine)
For more examples, see example.py.
Running Tests
# Run all tests
pytest test_state.py test_policies.py test_core.py test_gui.py -v
# Run tests without GUI tests (if display not available)
pytest test_state.py test_policies.py test_core.py -v
# Run with coverage
pytest -v --cov=. --cov-report=term-missing
Release Readiness
This repository runs automated checks for each push/PR:
- install/build verification (
pip install .andpython -m build) - dependency vulnerability audit (
pip-audit) - automated test suite
Release publishing is automated via GitHub Actions:
- pre-release (
prereleased) → TestPyPI - full release (
published) → PyPI
One-time PyPI setup
- Create projects on both indexes:
- In each project, configure Trusted Publishers for this repository and workflow:
- Repository:
jmwilson2019/raspiarduninoAI - Workflow file:
.github/workflows/release-testpypi.yml(TestPyPI).github/workflows/release.yml(PyPI)
- Repository:
- Create a GitHub pre-release to validate publishing to TestPyPI.
- After validation, publish a full GitHub release to publish to PyPI.
Architecture
state.py: Manages sensor state and data validationpolicies.py: Policy engine that evaluates sensor state and makes decisionscore.py: Core controller that coordinates state, policy, and hardware interfacesgui.py: Holographic GUI for real-time monitoring and control
Wiring
Gate Board (MKS Gen V1.4) Final Pin Assignments
| Component | Pin / Header | Notes |
|---|---|---|
| Gate Motor 1 | X (54 STEP, 55 DIR) | Standard |
| Gate Motor 2 | Y (60 STEP, 61 DIR) | Firmware-commanded to same target as motor 1 |
| Enable (both) | 38 | Active LOW |
| Pump Relay | Heatbed (8) | High-current relay output |
| Valve (PWM) | Hotend (9) | PWM range 0-255 (0 closed, 255 full-open, intermediate = partial) |
| HC-SR04 Trig | 17 | Digital output |
| HC-SR04 Echo | 16 | Digital input |
| Dust Sensor OUT | 18 | Digital input |
| PIR (HC-SR501) OUT | 19 | Digital input |
| Sensor Power | 5V / GND headers | Shared 5V/GND rail |
Telescope Board
Telescope board wiring is unchanged from the existing 4-motor telescope setup.
Wiring Notes
- Tie all sensor grounds to the same board ground reference.
- Confirm the gate enable logic is active LOW before first motion test (
LOW= drivers enabled,HIGH= disabled) to avoid unexpected movement. - Keep high-current pump relay wiring isolated from low-voltage sensor leads.
- Verify HC-SR04 orientation and stable 5V supply before trusting distance data.
Cockpit GUI
A holographic HUD-style control surface for the rig lives in
run_seraphina_gui.py. It reuses the existing
state.py / policies.py / core.py modules to parse the gate board's JSON
sensor stream and exposes:
- Always-on cockpit gauge cluster (hopper level, valve % open, annunciator lamps for gate, pump, dust and flow, and the current policy decision).
- Manual controls for the gate presets (sent as
OPEN <steps>per the firmware contract), the pump relay (PUMP ON/PUMP OFF), and the telescope. - A Seraphina AGI chat panel that prefers the
seraphinaPython API and falls back to the installedseraphinaCLI when no Python entry point is exposed.
Run
pip install -r requirements.txt
python run_seraphina_gui.py
The script assumes the gate board is on /dev/ttyACM0 and the telescope
board on /dev/ttyACM1 at 115200 baud (the values defined at the top of the
file - adjust there if your wiring differs). Hardware and Seraphina
integrations all degrade gracefully when their backends are missing so the
HUD can be launched on a bare workstation for layout work.
First Power-On Verification
- Flash the gate-board firmware.
- Open serial monitor at
115200. - Confirm startup banner:
GATE_BOARD_READY. - Confirm periodic JSON sensor lines are emitted.
- Test
STATUS,GET_PRESETS,OPEN <steps>, andCLOSEcommands incrementally.
Metadata
Release files for raspiarduninoai 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| raspiarduninoai-0.1.4.tar.gz | 48.1 kB | Without provenance | Details for raspiarduninoai-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| raspiarduninoai-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for raspiarduninoai-0.1.4-py3-none-any.whl |
Total release size: 96.7 kB
Release files / raspiarduninoai-0.1.4.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | raspiarduninoai-0.1.4.tar.gz |
|---|---|
| Size | 48.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd69c2206744ad5725abee75bd08411180bdece29eb3fd630c2b08368ad58cda
|
|
BLAKE2b-256 checksum How to use checksums |
08f9360ea1a56b6497710b90f67ace11e5d0149449bb110c3142877e2be2983c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / raspiarduninoai-0.1.4-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | raspiarduninoai-0.1.4-py3-none-any.whl |
|---|---|
| Size | 48.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa249adc10a096a57e62a2adeb90187bbbf1a3b3914ec840139e59993a113fb4
|
|
BLAKE2b-256 checksum How to use checksums |
9f663016a0ea45a87598f3d0faa9449c399d4897836a4194f304f8a8ad126ad5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for raspiarduninoai 0.1.4
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.1.3 2 files With provenance
- Added 0.1.4 2 files Without provenance
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.