Amiga Pass Planner v0.9.30 — MorganicSystems

MorganicSystems

+

Pass Planner v0.9.30

Organize passes · plan tools · track runs

🔑 Set key

Saved ✓

Site: › Machine: · · Passes:0

Pass Library

Named cultivation passes organized by bed, tool, and purpose.

Pass Detail

No pass selected

Select a pass from the Library tab to view and edit its details, or click + New Pass to create one.

Map View

Visualization of passes with GPS anchors. Click a pass in the Library to highlight it.

Center Lat

Center Lon

Setting anchor for: —

Run Log

Execution history for the selected pass.

Data & Import

Import context from the Inspector or track files. Export the pass library.

Import the JSON export from Amiga Inspector to get site context, machine identity, and bed geometry.

Import Track File

Import a farm-ng track JSON file to create a new pass with pre-loaded waypoints.

Export

Export workspace backup or individual pass data.

Reset

Use Import menu → Clear All Data or Reset to Demo Data to manage app state.

Pass Planner Guide

What is Pass Planner?

Pass Planner is a planning and operational-record tool for Amiga autonomous passes. It helps you organize passes, configure tool intentions, review readiness, and track run history.

Pass Planner does not control the machine or send configurations to the robot. Tool configurations, readiness checks, and run logs stay in Pass Planner as your structured planning record — you carry this information to the robot and configure it manually.

Today, routes primarily come from recorded tracks (teach-and-repeat) or imported track files. Pass Planner organizes and reviews these routes but is not a full route editor.

What Pass Planner is NOT

Not a full route editor — today, routes come from recorded tracks or imported files, not from drawing on the map. The map is a review and anchoring surface.
Not a machine controller — tool configurations are plans and intentions, not commands sent to the robot.
Not a live monitoring surface — machine state comes from Inspector snapshots, not real-time feeds.
Not a two-way sync tool — data flows one way: Inspector → Pass Planner. Each tool owns its own domain.

How it connects to Inspector

Pass Planner and Amiga Inspector share a site-first architecture. Both tools organize around the same sites and machines, but serve different purposes:

Inspector — assesses machine condition, collects snapshots, tracks readiness
Pass Planner — plans autonomous passes, records tool intentions, tracks run history

You can import Inspector data into Pass Planner to get site profile, machine context, and readiness status. This enriches your pass planning with real machine data.

Importing Inspector data enriches Pass Planner context but does not make it a live mirror of Inspector. Pass Planner keeps its own stored planning state independently. Data flows one direction: Inspector → Pass Planner.

Key concepts

Site

The farm or location anchor. Passes are filtered by the currently selected site in the context bar. You can switch sites using the site dropdown.

Pass

A planned autonomous operation consisting of a route (waypoints), tool sequence (H-bridge/PTO configurations), and machine context. Each pass tracks its own run history.

Completeness

Each pass shows a completeness status: Ready, Review, or Incomplete, based on 6 planning checks: track, GPS anchor, tool sequence, machine context, machine readiness, and compatibility. This is planning completeness, not operational authority.

Track Stats

Path length, estimated duration, headings, and waypoint count. Geometry warnings flag potential issues like very short tracks, large waypoint jumps, or missing GPS anchors. These are initial planning heuristics, not guarantees.

Tool Sequence

H-bridge and PTO tool configurations with engage/disengage timing and e-stop behavior. The sequence timeline shows the planned active zone visually.

Typical workflow

Site and machine context is shared automatically from Inspector via the workspace
Create passes and configure routes, tools, and targets
Review completeness panel and resolve any warnings
Export a Pass Report (.md) for field reference
After running the pass in the field, log the run with outcome and notes

Reports and exports

Operator-facing Markdown reports

Pass Report (.md) — summary of one selected pass, including completeness, track stats, tools, and run history. Found on the Pass Detail tab.
Site Pass Report (.md) — summary of all passes at the current site. Found on the Library tab.

Backup

Export Library JSON — full backup of all passes across all sites. Found in the Export dropdown. Use this for data preservation.

Debug / diagnostic exports

Pass Diagnostic JSON — raw diagnostic artifact for one pass, including completeness checks, track stats, and machine context provenance. Found on the Pass Detail tab.
App Diagnostic JSON — whole-app state snapshot for troubleshooting. Found in the Export dropdown. Not operator-facing — intended for development and debugging.

Tips

Passes are filtered by the selected site. If you don't see expected passes, check the site dropdown in the context bar.
Unassigned passes (no site set) appear in a separate section at the bottom of the Library.
V3.0 provisional data is marked throughout — verify against the machine dashboard before field use.
The suite cross-link (← Amiga Inspector) navigates between tools. Each tool keeps its own independent state — clicking the link does not transfer data.
Export Library JSON saves ALL passes across all sites. Site Pass Report only covers the current site.