Skip to content

Comments

docs: go2 preflight checklist#1349

Open
leshy wants to merge 1 commit intodevfrom
ivan/fix/go2checklist
Open

docs: go2 preflight checklist#1349
leshy wants to merge 1 commit intodevfrom
ivan/fix/go2checklist

Conversation

@leshy
Copy link
Contributor

@leshy leshy commented Feb 22, 2026

go2 nav preflight checklist was missing - people will have issues, added

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 22, 2026

Greptile Summary

Added a pre-flight checklist section before the Go2 robot setup instructions. The checklist includes three essential checks: network connectivity verification (ping test), reminder to enable built-in obstacle avoidance, and clock synchronization instructions using NTP for video/lidar sync issues.

  • Improved user experience by providing clear pre-requisites before running the robot
  • Reorganized content by moving the obstacle avoidance tip from below into the checklist
  • Added practical troubleshooting guidance for common clock sync issues
  • Minor spelling error: "reacheable" should be "reachable"

Confidence Score: 4/5

  • This PR is safe to merge with minimal risk - it's a documentation improvement
  • Documentation-only change that improves user experience by adding a helpful pre-flight checklist. Only issue is a minor spelling error ("reacheable" → "reachable") that should be fixed before merge
  • No files require special attention beyond fixing the spelling error

Important Files Changed

Filename Overview
docs/platforms/quadruped/go2/index.md Added pre-flight checklist for Go2 setup - includes network check, obstacle avoidance reminder, and NTP sync; minor spelling error found

Last reviewed commit: ac8f3bc

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 file reviewed, 1 comment

Edit Code Review Agent Settings | Greptile


### Pre-flight checks

1. Robot is reacheable and low latency <10ms, 0% packet loss
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"reacheable" is misspelled

Suggested change
1. Robot is reacheable and low latency <10ms, 0% packet loss
1. Robot is reachable and low latency <10ms, 0% packet loss

@leshy leshy changed the title go2 preflight checklist docs: go2 preflight checklist Feb 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant