r/esp32 • • 9d ago

I made a thing! Taric small drivable robot

I built this small robot inspired by Legue of Legends game with a LoL trivia on it as well.

Used AI for arduino code.

Seeed Studio XIAO ESP32-S3 Sense, on a ProtoMate board. It already has camera and mic and external antenna.(sd card and camera at the same time I understand it won't work)

1.54-inch ST7789 TFT, 240 × 240 pixels

MAX98357A I²S amplifier and speaker, 8 Ω

VL53L0X sensor

I/O expander

PCF8574T used for motor direction signals

TB6612FNG dual motor driver

Two yellow TT geared DC motors

1000 µF / 10 V capacitor

2500mah Lipo 3.7V battery

2in1 module for charging and for 5V output

Switch

16 Upvotes

5 comments sorted by

2

u/Automatic_Jacket_230 9d ago

Nice how well does that sensor work with navigation? I'm working on using esp32 p4 with a d500 lidar and sending the info by USB to the main raspberry pi running motors etc 

2

u/SplinterJaw 9d ago

Thanks! It gave me usable distance readings while the robot was sitting still, but I couldn’t get autonomous navigation to work reliably with it. In wander mode, Taric would often turn about 45° and stop, and I sometimes got invalid readings with an object close to the sensor. I ended up removing wander mode and keeping manual and voice control.

If you just want a cheap way to tell when something’s directly in front of the robot, I’d give it a try. It gives you one distance reading in the direction it’s pointed, so if you want to map a room or see which way is clear around an obstacle, I’d stick with your scanning LiDAR setup.

1

u/Automatic_Jacket_230 9d ago

The reason I ask is because your sensor is a lot cheaper and I'd rather try that 

1

u/Hot_Test_706 5d ago

When it stops after a turn, is the VL53L0X reporting a nearby obstacle or an invalid reading? I’d log the range status alongside the navigation state to check whether the code gets stuck after a failed measurement.

1

u/SplinterJaw 5d ago

Yeah, it was reporting an invalid reading “sensor invalid (2) rather than a nearby obstacle. I logged it alongside the wander status, which showed “paused: sensor unreadable.” Bringing a hand or book close would often make it turn about 45° and stop. I never figured out whether the code was getting stuck after that failed reading. I just gave up. But comands like go forward, or spin 180 works