Late night breadboard prototyping.
Got the moisture sensor and ds18b20 working.
- Plan on adding a more capable sensor - ens160.
- Refine sensing algorithm
- Build our first probe prototype
What are we building? An agric probe for grain testing
#buildNigeria2026 #BNAgric
I've haven't had a laptop for a while now and I've had to program using my phone and it's ASS 😡.
I'll have to manage sha.
2
6
195
Does my room have a predictable lighting pattern?
I'm using a BH1750 light sensor to investigate illumination changes throughout the day.
I can identify recurring lighting patterns using nothing but a low-cost sensor and some data analysis.
Check back on November 10, 2026.
3
9
131
I accidentally connected 3.3v to one of my I2C lines of the ens160+aht21 sensor.
Is that supposed to damage it cuz it doesn't work anymore 🙃.
2
12
426
Thinking of rebooting this old project. It's a networked biometric attendance system (BIOSYNC).
The goal? Identify someone across multiple nodes without having to register their fingerprint on every single device.
3
6
217
My printed frame is breaking in multiple places and the motors keep sliding out from it's clamp
It was printed in PLA which is not ideal but techniques can be made to improve rigidity
Any suggestions on improving its strength without adding too much weight? Help a builder out!
Fixed the Wi-Fi, fixed the power bugs, then ran system on it's battery.
4hrs later: reboot loop. Turns out, the cells were over-discharged - 2.9v.
I used the LX-LCBST module and it uses the TP4056. Wasn't it supposed to protect the batteries?
Third time's a charm I guess 🫠
18hrs into a mandatory 24hr sensor burn-in test and I accidentally pulled the power cable 🙃
Back to hour zero
For context, the ENS160 needs 24 hours of continuous operation during its initial startup before its startup status is saved to non-volatile memory
Check comments 👇🏾
Meanwhile, round two of the ENS160 burn-in is underway.
I just have to stay away from the POWER CABLE. 😭
Embedded systems will humble you over the smallest things.
#ESP32 #EmbeddedSystems #IoT #HardwareDebugging
3
31
And surprisingly, the Access Point has been behaving ever since.
No more disappearing act. (So far. 👀)
I still want to verify the suspected power issue by monitoring the 3.3V rail under load, but this was a pretty interesting find.
2
21
The repository also pointed me towards reducing the Wi-Fi transmit power.
So I tried:
"WiFi.setTxPower(WIFI_POWER_15dBm);"
This lowers the radio's transmit power from its higher setting, reducing its RF output and potentially easing the power demands.
2
23
Here's where it gets interesting.
Wi-Fi transmission isn't exactly free. The ESP32-C3 can draw substantial current during RF transmission, with the datasheet specifying peaks around 335 mA under certain high-power transmission conditions.
The onboard regulator can't keep up.
2
31
Apparently, board quality varies quite a bit between vendors, and some of these tiny boards have questionable power-supply implementations.
2
36
That observation gave me a pretty good lead: the power supply.
After some digging, I stumbled across a GitHub repository discussing power-related issues with some ESP32-C3 Super Mini clones.
2
43
My ESP32-C3 Super Mini's Wi-Fi Access Point kept refusing to show up.
Interestingly, when powered normally, the AP wouldn't come up. But when I accidentally powered the board through VIN using a power bank, it worked!
(Please don't randomly experiment with power inputs like me)
2
48




























