Great video. I am using a Xiao ESP32C3 where it sends temp data from a DS18B20 Temperature Sensor to AWS. It's powered by a 1500 mAh LiPo battery and so far I have only been able to get the device to be on from a single charge for 1 days, 20 hours, 16 minutes. Now I am learning new power consumption techniques I can implement since I have been operating in Active Mode the whole time. This video was a great introduction to my next R&D step!
Great work. Looking forward to Part 2. Please use flux remover and then Super Wash or alcohol on your header pins. Flux is a conductor which may cause leakage, false triggers, etc.
It is a modular power supply platform from Keysight Technologies and the mainframe is the N6705B DC power analyzer (I believe they are on the 'C' version now). The mainframe takes up to 4 power supply modules. The module I was using is the N6762A, which is one of their mid range performance modules. It is not cheap, but comes in handy!
The main reason you use a esp 32 or 8266 is for connectivity ...and to my knowledge unfortunately you cant have the radio on and go to sleep , and you cant wakeup from receiving a bluetooth signal or wifi packet .... The esp is nice but its useless if you need to activate the radio and your on battery .... If you have any idea how to sleep and wakeup on receiving a bluetooth or wifi packet plz address it in the second video
You are correct and thanks for the comment. It is not really just an ESP32, but a problem with wireless connections in general. To maintain a wireless connection you need to transmit data wirelessly, which is a power hungry operation. Also you need to pre and post process data so you need some type of CPU involved. I am not a bluetooth standard expert, but you can sleep a bluetooth device and wake every couple of seconds to check for a device that is trying to pair. And if there is no device you can go back to sleep and if there is you stay awake until the bluetooth communication is complete. My application that I am planning is for WiFi to send and read data from the cloud, which doesn't require a constant connection. My device will sleep for some amount of time, wake up, and connect to the WiFi. From there it will send sensor data and then read any settings or state change information from the cloud. Take the appropriate actions and go back to sleep. The amount of time the device sleeps is just based on how real time you want the data or actions it performs to happen. But of course there are applications that do require a constant connection. I will show a WiFi example in part two but it is the wake up connect and go back to sleep approach.
Great video. I am using a Xiao ESP32C3 where it sends temp data from a DS18B20 Temperature Sensor to AWS. It's powered by a 1500 mAh LiPo battery and so far I have only been able to get the device to be on from a single charge for 1 days, 20 hours, 16 minutes. Now I am learning new power consumption techniques I can implement since I have been operating in Active Mode the whole time. This video was a great introduction to my next R&D step!
Awesome, glad you found the video useful
Great work. Looking forward to Part 2. Please use flux remover and then Super Wash or alcohol on your header pins. Flux is a conductor which may cause leakage, false triggers, etc.
Just so you know part 2 is already out. And I appreciate the tip on cleaning up the flux
Great video. What power supply or instrument did you use to do the digitized current capture that you showed at the end of the video?
It is a modular power supply platform from Keysight Technologies and the mainframe is the N6705B DC power analyzer (I believe they are on the 'C' version now). The mainframe takes up to 4 power supply modules. The module I was using is the N6762A, which is one of their mid range performance modules. It is not cheap, but comes in handy!
The main reason you use a esp 32 or 8266 is for connectivity ...and to my knowledge unfortunately you cant have the radio on and go to sleep , and you cant wakeup from receiving a bluetooth signal or wifi packet .... The esp is nice but its useless if you need to activate the radio and your on battery .... If you have any idea how to sleep and wakeup on receiving a bluetooth or wifi packet plz address it in the second video
You are correct and thanks for the comment. It is not really just an ESP32, but a problem with wireless connections in general. To maintain a wireless connection you need to transmit data wirelessly, which is a power hungry operation. Also you need to pre and post process data so you need some type of CPU involved. I am not a bluetooth standard expert, but you can sleep a bluetooth device and wake every couple of seconds to check for a device that is trying to pair. And if there is no device you can go back to sleep and if there is you stay awake until the bluetooth communication is complete. My application that I am planning is for WiFi to send and read data from the cloud, which doesn't require a constant connection. My device will sleep for some amount of time, wake up, and connect to the WiFi. From there it will send sensor data and then read any settings or state change information from the cloud. Take the appropriate actions and go back to sleep. The amount of time the device sleeps is just based on how real time you want the data or actions it performs to happen. But of course there are applications that do require a constant connection. I will show a WiFi example in part two but it is the wake up connect and go back to sleep approach.