Skip to main content
On T3 Gemstone O1, Wi-Fi connections are managed by NetworkManager (nmcli). Once you connect to a network, its password is saved and the robot connects to that network automatically on subsequent boots. In a new environment such as a competition venue, school or home, the robot’s network must be added once.

1. Connecting to the Board Without a Network

Since the robot is not yet connected to the new network, it cannot be reached over Wi-Fi. Connect to the board using one of the following methods.

2. Adding a Network

Scan for and list nearby networks.
Connect to the network. If the network name contains spaces, write it in quotes.
If the command reports successfully activated, the connection has been saved.
For networks that require a user name and password:
peap/mschapv2 is the most common setting; if the network administrator specifies a different method, use that instead.
A phone hotspot is added like any other network. If there is no network at the track, this is the easiest method. The robot and the computer that will open the interface must be connected to the same hotspot.
Typing the password into the nmcli command saves it in the shell history. On a shared board, run history -c afterwards, or instead of typing the password on the command line, use the --ask option and enter it when prompted: sudo nmcli --ask dev wifi connect "NETWORK_NAME"

3. Finding the Robot’s IP Address

The network assigns an address to the robot via DHCP, and the address is different on every network.
The output looks like wlan0 UP 10.0.10.91/23. The web interface is reached at http://<this-address>:8000. The computer that will open the interface must be on the same network as the robot.
Some enterprise and guest networks prevent devices from seeing each other (client isolation). If the interface does not open, try a phone hotspot.

4. Managing Saved Networks

If more than one saved network is visible at the same time, the robot connects to the one with the higher priority.

Troubleshooting

The password is wrong, or the network is an enterprise network. For enterprise networks, use the enterprise network command above.
The network may be broadcasting on the 5 GHz band and the board does not see it, or the board is out of range. Check the nmcli dev wifi list output.
  • Is the robot software running? If the service is installed, check with systemctl status ugv.
  • Is the computer on the same network as the robot?
  • Does the network isolate devices from each other (client isolation)?