The display does not start
Check power and the installed board target. With power disconnected, inspect the display cable and connector lock. TARS needs its landscape ST7789V2 configuration; a round-screen build is not a replacement.
Network discovery fails
Confirm that the robot is in provisioning mode, Bluetooth permission is granted and the Wi-Fi network is 2.4 GHz. Verify that the app matches the firmware region. See Wi-Fi and activation.
Voice commands do not respond
Check the region-specific wake word, online state, microphone and current operating mode. Exit BLE remote-control mode if voice services have been suspended. A network connection alone does not confirm cloud activation.
Motion is irregular
Stop testing. Check battery charge, cable connections, component orientation and calibration. If calibration reports an error, the firmware stays in calibration mode. Correct the connection or zero-position issue before confirming again.
What should I include in a support request?
Record the model, hardware revision, firmware version and region. Describe the steps that reproduce the issue, screen message and whether it happens before or after network connection. Include a photo of the assembled mechanism or a short startup log where useful.
Open shared troubleshooting · Contact Luwu
Building the public TARS firmware
- No TARS board option: the current public source includes RIG-Tars. Check that you opened a current checkout and selected esp32s3. Preserve your edits; an older download may need updating or replacing with a fresh checkout in another folder.
- Missing QR animation after flashing: confirm TARS, Overseas, Emote animation style and Flash Emote Assets. Build and flash the application and matching assets together.
- SERVO … NOT DETECTED: calibration feedback did not pass validation. Power off before inspecting servo IDs, connections and alignment. The firmware remains in calibration; a tool acknowledgement does not prove saving succeeded.
- Package script cannot find Test_Firmware: full release packaging needs that separate project. Use idf.py build and idf.py -p YOUR_PORT flash monitor for the robot firmware.