So I was presenting my robots on this year's PyCon.us, and this little guy didn't survive the flight over the Big Pond. It looks like the ESP8266 board is fried. When I get home, I will rebuild it properly, on a printed circuit board and with some nice distance sensors, and, most importantly, a voltage regulator.
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
Found out what was wrong. Turns out it's not power problems or magic blue smoke or anything like that. It's simply that I soldered the power switch directly to one of the traces on the module, and that got stripped at some point when some force was applied to the switch... Still seems like a dedicated PCB is a good idea, especially since I can then use those SMD time-of-flight distance sensors...
Are you sure? yes | no
Sad to hear! I really like your small robot! Will you use the ESP-12 boards this time? They come with the ADC broken out :)
Are you sure? yes | no
I will probably use ESP-12, but not for the ADC -- I discovered node.readvdd33() function (https://github.com/nodemcu/nodemcu-firmware/wiki/nodemcu_api_en#nodereadvdd33) which reads the power voltage, so that is perfect for monitoring the battery. I also want to use those time-of-flight distance sensors, so I will definitely need a PCB for it, which means that it will take several weeks anyways.
Are you sure? yes | no
so no regulator then?
Are you sure? yes | no
Well, if I'm making a PCB anyways, I may as well add a small linear regulator in there. I suppose the lack of a regulator is what killed the current robot.
Are you sure? yes | no
but the regulator will always give 3.3V so readvdd would give you a steady 3.3V too? Or am I missing something?
Are you sure? yes | no
That's true, oops :) So I will need the ADC after all. Thanks for pointing this out.
Are you sure? yes | no