Troubleshooting Guide

Issue Possible Causes Recommended Course of Action
Attempting to move KT on RobotMoose, but KT is not moving. Drive tab is not selected. KT will not move unless the drive tab is the active tab. Click on the drive tab, and the top bar of the tab should turn blue, indicating that it is the active tab.
KT is not turned on. Ensure that you've plugged in KT's USB cable into the Backend computer, then start up the backend. KT should start up automatically, indicated by a big red light. If no light comes on, KT most likely needs to be recharged.
Wires have become unplugged. Unplug the Arduino from the Backend computer, then find the long black cable that has four smaller wires inside it make sure that the black wire is plugged into the spot marked GND, the yellow wire is plugged into the spot marked 2, the red wire is plugged into the spot marked TX3, and the blue wire is plugged into the spot marked RX3 (Image). Double check your wiring then plug the USB back in.
Backend is not running. Go to the robot computer and ensure that the Backend Chrome app is open and connected to your robot.
Pilot is not connected or is connected to the wrong robot. Ensure that the robot year, school, and name that you selected on the Frontend match what was specified on the Backend.
The Frontend or Backend has lost its connection to the Superstar server. Ensure that the Superstar selected from the dropdown menu on the Backend is robotmoose.com (or your local Superstar if you are running one). Also ensure that in your web browser you are connected to robotmoose.com (or the IP address of your local Superstar). Refresh your page to make sure robotmoose.com (or your local superstar) is still up and running.
Web browser is causing unpredictable behavior. Make sure you are using Google Chrome to ensure that all elements of the interface work properly.
When trying to start the Backend, the big green light on KT turns on, then the Backend disconnects. KT is incorrectly configured. On the KT's Arduino, there are slots labeled TX3, TX2, and TX1. These are serial ports for communicating with KT, and one should have a wire plugged into it. On the robot control page, select the configure tab, and make sure a create2 device is configured with the serial port that KT is plugged in to.
Programmed KT to move, now it won't stop. KT is stuck in a programming loop. When you run your code, RobotMoose will keep running the code in the current state unless it is told to go to a different state. For example, if you are in a state that does "forward(10)" and nothing else, KT will continually go forward 10 cm. If you don't want it to do this, then go to a stop state after driving forward 10, or use variables and control flow statements (more info on code API here).
KT Arduino has become unplugged If the KT Arduino somehow becomes unplugged, KT will be stuck doing the last command that was sent to it. Plug the Arduino back in and restart the backend.
There is considerable lag between sending commands to KT and those commands happening. Backend is being throttled. On the Backend computer, the Backend window must be visible at all times, otherwise the app may be throttled. Ensure that the window is visible (not minimized, covered up by other windows, etc.).
Network connection is too slow. You may have to start your own Superstar server (more info on our GitHub, for advanced users only).