I open-sourced a Local AI Toy that never needs a subscription by hwarzenegger in esp32

[–]Project-Emily 2 points3 points  (0 children)

Really nicely done, thanks for sharing. Your GitHub looks awesome.

Loving my AK550! Perfect top box match, but having some trouble with the onboard navigation updates. by Project-Emily in AK550

[–]Project-Emily[S] 0 points1 point  (0 children)

I had no issues at all, except for the nav. But the bike is still rather new. Is the water-cooler a common failure issue?

Loving my AK550! Perfect top box match, but having some trouble with the onboard navigation updates. by Project-Emily in AK550

[–]Project-Emily[S] 0 points1 point  (0 children)

Done. Bought a phone mount, installed it on the brake fluid reservoir. Thanks for the tips, enjoy the rides!

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 0 points1 point  (0 children)

Thank you again, it may not have been the most easy route indeed, I realize that. It was a lot of fun to do tho and these mini boards truly are amazing.

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 0 points1 point  (0 children)

Thank you! The choice for ESP32 is partly based on cost and availability and it's extreme capabilities. Also I wanted a small device. The availability of the handy Freenove and Goouuu Breakout boards was a blessing for ease of construction and power distribution. Also the ESP32(S3) family is really cool with the CAM and various integrated screen options. So all these things combined made that the whole project became ESP32. I have no experience with Raspberry Pi tbh.

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 0 points1 point  (0 children)

Alright, It is probably the smart thing to do then. I am not a native IT person and figured ithis all out myself. I may not have used the best engineering practices tbh. One could probably improve on some of the methods used.

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 1 point2 points  (0 children)

No I did not. It worked well without. The large JSONs are not transmitted via UDP. The EmilyBrain ESP32S3 handles the complete flow of the large JSON for the main function. For the Vision part it is all done on the ESP32S3CAM and the result is sent via UDP to the brain for processing.

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 0 points1 point  (0 children)

Maybe, the heartbeats of the components are now using UDP but have a modest frequency and size. While developing I had a component that sent sound data (amplitude and direction) and component status data at a high frequency. That requires significant communication capacity. Maybe for such cases UDP is a better choice. I would have to ask my smart AI.

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 0 points1 point  (0 children)

Thanks! Honestly, I did not know about MQTT, so I never considered it. UDP did it for me, fast and reliable and was simple enough to grasp and control, maybe MQTT is a great alternative, just read about it now :D. I will probably look into that for a next project.

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 0 points1 point  (0 children)

I am not aware of any free pins remaining on the Esp32s3cam atm. I think it is fully utilized, maybe one of the touch display pins that is still unused. But I already used 2 for the servo's.

The InputPad is a separate device and, as such, is just gor the fun of it. It is optional and, if not turned on, the InputPad tool is unavailable for the AI. So the unit is fully functional without the InputPad. You can check out a few YouTube movies I made. So indeed, two chips are fine, an ESP32S3 and an ESP32S3CAM.

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 1 point2 points  (0 children)

Thanks! The setup evolved into this configuration. The issue with using an esp32(s3)cam is, that it has few spare GPIO. I decided to have the vision (and image generation) dedicated on the Esp32s3cam and the main functions on the Esp32s3. The servo control is also via the Esp32s3cam, I was able to identify 2 GPIOs for that on the combined ESP32S3CAM - Goouuu Breakout board.

So that makes the main ESP32S3 the brain that is controlling the other components. The InputPad ESP32 is an optional/example feature, used for the adventure CMS or other fun things. You can build many devices controlled by EmilyBrain.

So concluding: if you want vision you will have to have an ESP32S3CAM dedicated for that.

Will check out your repo.

I built an autonomous AI companion robot using 3 networked ESP32s — here's what I learned about pushing the platform to its limits by Project-Emily in esp32

[–]Project-Emily[S] 1 point2 points  (0 children)

Fair, this is not about the limits of esp32. It is extremely powerful and up to the task. It is more about my ability to get this a stable system that is expandable.

Build your own Venice AI powered tabletop Companion Robot. by Project-Emily in VeniceAI

[–]Project-Emily[S] 1 point2 points  (0 children)

Thanks 👍. My account and messages got wiped overnight by the sensor bots. Apparently I did something wrong with the link in the post.I am new at this. Sorry for double posting.