Skip to content

v1.5.2

Release date: 2026-04-06

v1.5.2 is the SBC release.

This release turns the Raspberry Pi / edge-device story into a first-class part of the SDK. The goal was not just to make the runtime possible on a single-board computer, but to make it feel like a coherent product: lighter installation, persistent patient runtime, kiosk presentation, service export, bridge scaffolding, and documentation that explains the system clearly.

Highlights

1. New edge install profile

You can now install a leaner runtime profile for SBC hardware:

python -m pip install -U "iints-sdk-python35[edge,mdmp]"

This profile is aimed at:

  • Raspberry Pi 5 edge demos
  • UNO Q hybrid Linux + MCU experiments
  • always-on classroom or expo rigs
  • persistent digital patient runtimes without the full workstation reporting stack

The full workstation path is still available with:

python -m pip install -U "iints-sdk-python35[full,mdmp]"

2. New iints edge namespace

The SDK now has a dedicated edge workflow:

iints edge setup --output-dir iints_edge_demo --board raspberry_pi
iints edge status --workspace iints_edge_demo/patient_runtime
iints edge bundle --workspace iints_edge_demo/patient_runtime --output results/edge_runtime_bundle.zip
iints edge update --output-path update_edge_runtime.sh
iints edge hardware-bridge --board uno_q --output-dir uno_q_bridge

This gives the SDK a much cleaner public story for SBC use:

  • scaffold an edge project
  • run the live patient
  • inspect the runtime state
  • export a bundle back to a laptop
  • prepare physical bridge artifacts for UNO Q

3. Kiosk-ready Digital Patient dashboard

The live patient flow is now much stronger for presentation:

  • iints patient kiosk
  • richer dashboard status cards
  • scenario shortcuts for live demos
  • certification and realism review status shown directly in the UI
  • Raspberry Pi Connect-friendly presentation flow

The dashboard is designed to be self-contained and offline-friendly, so it works better on real hardware during a booth demo.

4. Exported systemd service support

The persistent digital patient runtime can now be packaged for auto-start more cleanly:

iints patient export-service --workspace patient_runtime

or generated automatically through:

iints edge setup --output-dir iints_edge_demo --board raspberry_pi

The scaffold includes:

  • a ready-made service unit file
  • install notes
  • update script
  • edge setup guide

That makes the expo/device story more robust after reboots, crashes, or power interruptions.

5. UNO Q bridge scaffolding

v1.5.2 also strengthens the hybrid-board story:

iints patient export-uno-bridge --output-dir uno_q_bridge

and via the new edge alias:

iints edge hardware-bridge --board uno_q --output-dir uno_q_bridge

This exports:

  • an Arduino sketch scaffold
  • protocol notes
  • bridge README

The goal is to let the Linux-side runtime hand off supervisor events to the MCU side for LEDs, buzzers, and other physical indicators.

6. SBC support matrix and architecture docs

The docs site now includes a dedicated SBC page with:

  • a support matrix
  • official vs experimental support categories
  • Raspberry Pi / UNO Q recommendations
  • a Mermaid architecture diagram for the edge runtime

This makes the docs much clearer for public users evaluating whether their board is a good fit.

New commands in practice

Recommended Raspberry Pi flow:

python3 -m venv .venv
source .venv/bin/activate
python -m pip install -U pip
python -m pip install -U "iints-sdk-python35[edge,mdmp]"
iints edge setup --output-dir iints_edge_demo --board raspberry_pi
cd iints_edge_demo
./run_edge_patient.sh

Then inspect or present it with:

iints edge status --workspace patient_runtime
iints patient kiosk --workspace patient_runtime

And export the runtime back to a workstation with:

iints edge bundle --workspace patient_runtime --output results/edge_runtime_bundle.zip

What changed under the hood

Added

  • new edge operations helpers for setup, status, update scripts, and ZIP bundle export
  • generated edge scaffold files (run_edge_patient.sh, launch_kiosk.sh, update_edge_runtime.sh, EDGE_SETUP.md)
  • richer workspace summaries including certification, realism review, kiosk URL, and artifact paths
  • UNO Q bridge export support in both patient and edge workflows
  • support-matrix docs styling and Mermaid diagram initialization on the docs site

Improved

  • import iints and import iints.analysis are safer without the full reporting stack installed
  • the live patient API now exposes a kiosk view and scenario reset endpoint
  • the dashboard now shows more runtime metadata and edge-focused controls
  • technical docs, installation docs, getting-started flow, public release checklist, and manual all explain the SBC workflow more clearly

Why this release matters

Before v1.5.2, the SDK could already simulate runs, certify data, and explain results. But the edge-device story still felt like an advanced internal path.

With v1.5.2, the SDK now has a real SBC deployment narrative:

  • install a lighter edge profile
  • scaffold a board-ready project
  • auto-start it as a service
  • present it in kiosk mode
  • export the runtime back to a workstation
  • document supported boards clearly

That makes Raspberry Pi and similar edge devices feel like first-class targets rather than afterthoughts.

Upgrade

Workstation:

python -m pip install -U "iints-sdk-python35[full,mdmp]==1.5.2"

SBC / edge device:

python -m pip install -U "iints-sdk-python35[edge,mdmp]==1.5.2"