Web Remote Controller

This project uses the robot's preinstalled browser controller to drive under direct supervision. It is an operator interface, not a method for accessing Ubuntu, editing project files, or configuring the robot network.

Project Goal

Open the controller, enter web-driving mode, complete a short low-speed route, stop cleanly, and document how the interface communicates motor and safety state.

Learning Goals

• Distinguish local development access from the browser operator interface.
• Identify stopped, web-driving, and debug states from the robot lights.
• Enable, command, and stop the robot through the existing controller.
• Evaluate which safety conditions are visible in the interface and which require physical confirmation.

What The Operator Uses

• Left wheel-hub button (Service Button 0)
• Right wheel-hub button (Service Button 1)
• Robot status lights
• Physical E-stop
• Web control page with a joystick and control buttons

When facing the robot, the left wheel-hub button is Service Button 0 and the right wheel-hub button is Service Button 1.

Light Meanings

• Red: Robot stopped
• Yellow: Web driving active
• White: Debug mode active

Before Moving The Robot

1. Power on the robot and wait for red lights.
2. Confirm the area is clear of people, obstacles, and drop-offs.
3. Keep the physical E-stop released, visible, and reachable.
4. Agree on the route, maximum speed, and stop signal with the instructor.

Open The Web Controller

1. Connect the approved operator device to the robot's operator network.
2. Open http://10.10.0.1:8080.
3. If the assigned robot uses another configured port, try :8081, :8082, :8083, then :8084.

Do not use this connection for SSH, Ubuntu access, SDK development, or network configuration.

The page includes:

• Joystick
• Engage Motors
• Emergency Stop
• Enter Debug Mode

Enter Web-Driving Mode

1. Start from red lights.
2. Press the left and right wheel-hub buttons together.
3. Confirm yellow lights and enabled controls on the page.
4. Select Engage Motors only after the instructor confirms the route is clear.

Complete The Route

1. Begin with the smallest joystick movement.
2. Verify the robot responds in the expected direction.
3. Drive the agreed route at low speed.
4. Release the joystick and confirm the robot stops.
5. Press the left and right wheel-hub buttons together again.
6. Confirm the lights return to red.

Safety Behavior

• The robot may block forward movement when a person is too close in front.
• Turning and backing may still be possible.
• Interface state does not replace physical area checks.
• Use the physical E-stop for an immediate hard stop.

Project Observations

Record:

• Which interface elements communicate motor state.
• How quickly the robot stops when the joystick is released.
• Which obstacles inhibit forward motion.
• Which safety facts cannot be confirmed from the browser alone.

Possible follow-on projects include a field-of-view overlay, clearer speed feedback, or a read-only safety-status panel. Any controller or deployment change requires instructor approval and is outside the beginner gather-sdk package.

Troubleshooting

Controls are disabled

Return to red lights, then press the left and right wheel-hub buttons together and confirm yellow web-driving lights.

The robot does not move

Confirm yellow lights, motor engagement, a healthy E-stop circuit, and a clear path. Do not change network or controller settings.

The page disconnects in debug mode

This can occur when the preinstalled application changes network state. Debug mode is an instructor or technician workflow; return to the documented stopped state.

Quick Reference

• Enter web driving: left + right wheel-hub buttons together → Yellow
• Exit web driving: left + right wheel-hub buttons together → Red
• Immediate hard stop: physical E-stop