Gather Lobo logoGather SDK
AI CodingRobot

Field Playbooks

These playbooks are written for non-developer field users and focus on safe hardware operation.

Playbook 1: Daily Bring-Up

  1. Inspect E-stop accessibility and wheel area clearance.
  2. Power on and wait for expected idle light state.
  3. Confirm network access from operator device.
  4. Open control page when required by the active stack.
  5. Run a short low-risk motion check in a clear zone.

Playbook 2: Person Following Session

  1. Start from stop/idle state.
  2. Use documented button sequence for person-follow mode.
  3. Wait for target-selection indication.
  4. Confirm active-follow indication before walking route.
  5. If tracking degrades, stop and reselect target.

Use detailed guide:

Playbook 3: Remote Control Session

  1. Confirm robot is in idle stop state.
  2. Enter web driving mode using documented button combo.
  3. Confirm web controls are enabled and lights indicate remote mode.
  4. Drive slowly first; verify response before full route.
  5. Exit remote mode and return to stop state before handoff.

Use detailed guide:

Playbook 4: Project Prototype Review

  1. Confirm all changed files are under ~/gather-sdk/projects.
  2. Review imports, cleanup, optional sensor values, and physical units.
  3. Run python3.10 -m py_compile or mocked tests before using hardware.
  4. Compare the result with the project guide's first prototype.
  5. Obtain instructor approval before any physical motion test.

Start with:

Playbook 5: Motion Fault Recovery

If behavior is unexpected:

  1. Use physical E-stop immediately when unsafe.
  2. Return to known stop/idle state.
  3. Re-check button mode and light state.
  4. Re-run startup checks from a clear area.

If persistent, escalate to your support process.

Playbook 6: Integration Smoke Test

For teams integrating external systems via supported interfaces:

  1. Verify E-stop status is healthy.
  2. Confirm motor enable/disable path works.
  3. Send low-speed command and confirm controlled stop.
  4. Confirm button and safety telemetry updates.

Use only: