Common symptoms
Scope
First-line symptom→action guidance for common GO2 field issues. The majority of issues resolve through basic resets — exhaust the simple fixes before escalating. [SOURCE: SOP V3 §III Rule 5 "Start with the Simplest Fix"; §XIX "Troubleshooting"]
Purpose
Reduce time-to-resolution and dependence on engineering. Catch the common cases on-site so escalations are reserved for genuinely novel issues.
Required inputs / tools
- Powered (or trying-to-power-on) GO2 robot.
- Skild tablet or browser at https://control.skild.ai/robots.
- Microfiber cloth.
- Deployment Slack channel.
Procedure — Symptom → Action table
| Symptom | First check | Resolution |
|---|---|---|
| No response to any input | E-Stop engaged? | Twist the red button (rear panel) to release. [SOURCE: SOP V3 §XIX] |
| Tablet cannot connect | Correct WiFi network? | Verify network name matches the robot (e.g. GO2W-32). [SOURCE: SOP V3 §XIX] |
| Connection failure persists | Is the Verizon dongle blinking green? | Blinking green = connected. Any other state = not connected. Remove top case → unplug/replug dongle until it returns to blinking green. [SOURCE: SOP V3 §XIX] |
| App requests credentials on launch (“Authentication failed”) | — | Do not enter a password. Refresh app and wait. Robot has not finished booting; auth screen clears automatically. [SOURCE: SOP V3 §IX] |
| Erratic behavior during mapping or navigation | LiDAR clean? | Wipe lens with microfiber cloth. Verify flush with casing. [SOURCE: SOP V3 §XIX] |
| Recurring localization failures | Environment changed since last map? | Re-map. Do not iterate on an outdated map. See /robots/go2/operation/mapping/ “When to Re-map”. [SOURCE: SOP V3 §XIX + §XI] |
| Robot does not follow route | Autonomous mode active? | Sit. Restart from map selection and pose. Full reboot if persistent. [SOURCE: SOP V3 §XIX] |
| General app or interface glitches | — | Refresh the application or restart the device. [SOURCE: SOP V3 §XIX] |
| Browser status dot is not green | Correct robot selected? | Refresh page. Log out + back in. Confirm correct deployment selected in Robots list. [SOURCE: SOP V3 §XIX] |
| Browser shows stale data or frozen UI | — | Refresh page. If state is lost, re-select the robot from the Robots list. [SOURCE: SOP V3 §XIX] |
| Map tracer lags behind camera | Landmarks still match? | Visual lag is normal. Do not intervene unless landmarks diverge. Use judgment. [SOURCE: SOP V3 §XIX] |
| Robot enters auto-sit mid-run | Motor temperature or battery threshold hit | Auto-sit at 75°C motor temp or 20% battery (autonomous mode only). Wait for cooldown or perform battery swap. See /robots/go2/maintenance/battery-and-charging/. [SOURCE: SOP V3 §XVI] |
| Robot is sitting / circling / hesitating in a safe area | Tracer may be re-planning | Wait. The robot may reconnect pathing on its own. Use judgment. [SOURCE: SOP V3 §"When to Stop the Robot"] |
| Need manual control without killing the active goal | — | Enter Teleop (controller LT + X, or browser Teleop button) — does not kill the goal. For keyboard arrow-key control on browser, use Manual Teleop. [SOURCE: SOP V3 §XV + §"When to Stop"] |
| Dramatic hazard (robot fell, upside-down, legs kicking) | — | Physical E-Stop. Approach with caution — moving legs can injure you. [SOURCE: SOP V3 §"When to Stop the Robot"] |
”Newbie blockers” — first-day-operator gaps to be aware of
These are common confusion points for first-time operators, captured from the browser-nav SOP newbie review: [SOURCE: SKild.Sops/browser_nav_sop/newbie_review.md]
- Clicking a deployment from the Robots list opens the home screen. The home screen is the default monitoring view (Video Feed top-left, Map View top-right, LowState Metrics bottom-left, Sensirion Metrics bottom-right).
- “Camera button” location for on-demand image capture: in the Video Feed panel on the home screen — exact icon placement varies; ask a shift lead if unsure.
- Physical E-Stop is on the REAR panel of the robot (red button, opposite end from the green status LEDs).
- Two buttons during navigation start: “Start Navigation” loads the map and prepares the robot (no motion yet). “Autonomous” begins executing the saved route.
- “Teleop” vs “Manual Teleop”: plain Teleop uses on-screen controls / tablet controller. Manual Teleop is keyboard arrow-key control on the browser.
- Localization tolerance: position must match reality within roughly one map grid cell at a known landmark. Larger drift = treat as lost.
[SOURCE: SOP V3 §XII] - Map mode (tablet): green toggle = Scroll Mode (taps pan); red toggle = Place Mode (taps commit to map). Check before every interaction.
- Map mode (browser): hold spacebar + trackpad scroll = pan. Release spacebar before placing waypoints / poses.
Default to caution
Localization confidence is the safety floor. When uncertain, sit and reset — it takes seconds. Allowing a poorly-localized robot to continue autonomous navigation creates genuine safety risk.
[SOURCE: SOP V3 §XII]
Whenever possible, stop the robot from a distance using Kill Task, Terminate Tasks, or Sit. Approaching a thrashing robot to hit the physical E-Stop is a last resort, not a first response.
[SOURCE: SOP V3 §"Default to Software Stops"]
Conflict resolution log
[RESOLVED 2026-05-18 — C2: Controller scheme = LT+X / LT+Y / LT+RT confirmed.]April 2026 ABM SOP §XXI Controller Quick Reference. Operators expected to know “from muscle memory” (line 739). PS-style L1/L2/X/Y from older GOI + Robot Delivery SOP is deprecated for GO2.[RESOLVED 2026-05-18 — C7: Cooldown = "sit and let cool" (no prescribed duration).]April 2026 ABM SOP lines 552, 598. Older “10–15 min” and “~50°C minimum” specifications are not in current procedure.
Escalation
- Software / app issue unresolved after refresh + restart → post in deployment Slack with: robot state, screenshot, time, what you tried.
- Hardware issue (damage, missing parts, persistent boot failure) → STOP. Do not operate. Notify site coordinator and deployment Slack. Submit Incident Report.
- Repeated occurrences of the same issue across shifts → file Incident Report flagging it as patterned, not a one-off.
[SOURCE: SOP V3 §XVIII "Shutdown" item 5]
Source notes
[SOURCE: GO2_Standard_Operating_Procedure_V3.docx]§III Rule 5, §IX, §XII, §XVI, §XIX (full troubleshooting table), and §“When to Stop the Robot — Decision Guide”.[SOURCE: GO2_Standard_Operating_Procedure_ABM.docx](April 2026, Tyler Kugima) — §XIX Troubleshooting (8-item symptom table), §XXI Controller Quick Reference. Authoritative for ABM-LGA.[SOURCE: GO2_General_Operating_Instructions_V3.docx]— older companion (controller mapping conflict source — now resolved).[SOURCE: ~/Desktop/SKild.Sops/browser_nav_sop/newbie_review.md]— newbie blockers section.
Related
- /robots/go2/operation/localization-and-pose/ — pose-reset details.
- /robots/go2/operation/mapping/ — re-mapping when localization is recurring.
- /robots/go2/maintenance/battery-and-charging/ — thermal and battery thresholds.
- /robots/go2/troubleshooting/controller-reference/ — Xbox-style mapping.
- /general/incident-response/ — when troubleshooting fails, file a report.