Jean-Pierre MartineauandClaude Opus 5.5
9538bfedce
A LoRa chip on the host's own SPI bus (the uConsole AIO) is now a transport like serial, BLE, and TCP: --spi, an SPI profile, or the picker's row for /dev/spidev1.0. MeshTerm starts a software node as a child process under whichever Python has openhop-core, talks to it over a loopback port, and ends it on disconnect; the node also exits with its parent, so the pins are free whenever MeshTerm is not running. The node keeps identity, prefs, channels, and contacts under ~/.meshterm/radio/<spidev>/, and on first use copies the bridge's identity, contacts, and radio settings so it stays the same node. Board wiring lives in a profile's spi table; radio settings are the node's own, edited on Device config. Closes #21. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
51 lines
2.9 KiB
Markdown
51 lines
2.9 KiB
Markdown
# MeshTerm documentation
|
|
|
|
Everything that didn't belong on the front page. The [README](../README.md) is the front
|
|
door — what MeshTerm is, how to install it, and enough to get a first session running.
|
|
This folder is the rest.
|
|
|
|
## Using MeshTerm
|
|
|
|
| Read | For |
|
|
| --- | --- |
|
|
| **[What MeshTerm does](features.md)** | Every screen the menu offers, grouped the way the menu groups them, with the command that does the same job without it. |
|
|
| **[The command line](cli.md)** | The manual. Every subcommand and option, what each prints on the plain and JSON faces, the exit statuses, and recipes built on `jq`. |
|
|
| [The CLI cookbook](cookbook.md) | Common one-liners by task, for when you want the shape of a command rather than its specification. |
|
|
| [Configuring MeshTerm](configuration.md) | Preferences versus config, device profiles, and everything kept under `~/.meshterm`. |
|
|
| [Terminals, icons, and the Windows console](terminals.md) | Why the icons and charts draw on some terminals and not others, and what MeshTerm does about it on Windows. |
|
|
|
|
## Putting it on hardware
|
|
|
|
Only if you want MeshTerm running on a handheld's own screen. A MeshCore companion on
|
|
USB, Bluetooth or Wi-Fi needs none of this.
|
|
|
|
| Read | For |
|
|
| --- | --- |
|
|
| **[MeshTerm on hardware](hardware.md)** | Start here — which of the two manuals below is yours, and what the device-side scripts do. |
|
|
| [MeshTerm on the PicoCalc](picocalc.md) | A stock ClockworkPi PicoCalc to a Linux handheld with a LoRa radio soldered inside: the shopping list, the Lyra swap, Calculinux, and the radio. |
|
|
| [MeshTerm on the uConsole](uconsole.md) | A uConsole with the hackergadgets AIO LoRa board, whose SX1262 sits on the host's own SPI bus — MeshTerm drives it directly with `--spi`, or a small bridge fronts it as a companion for an always-on node. |
|
|
|
|
## Reading the code
|
|
|
|
| Read | For |
|
|
| --- | --- |
|
|
| [How the code is laid out](architecture.md) | The layering, and where a new feature goes. |
|
|
| [CLAUDE.md](../CLAUDE.md) | The actual style guide — terminology, UX standards, and the reusable building blocks. Written for AI assistants, and the house rules for everyone. |
|
|
| [CONTRIBUTING.md](../CONTRIBUTING.md) | The dev install, the three gates a change has to pass, and what happens to your contribution's licensing. |
|
|
|
|
## Historical record
|
|
|
|
A survey of the code, kept because a project that writes down its own problems is easier
|
|
to trust than one that doesn't — but it is a **snapshot of a date, not a to-do list**.
|
|
Some of what it describes has been fixed since, and it does not mark which.
|
|
|
|
| Read | For |
|
|
| --- | --- |
|
|
| [UI consistency survey](survey-ui-consistency.md) | Everything else in the CLAUDE.md UX standard — six sweeps found nothing, which is the useful part. |
|
|
|
|
## Also here
|
|
|
|
`screenshots/` holds the captures the README shows and the ones
|
|
[meshterm.net](https://meshterm.net) builds its landing page from, so a file in there is
|
|
referenced from more than one place.
|