It’s definitely not a reliability issue, with the platform - ESP32 in general is very popular so it’s surely an issue with my usage. I’m fairly certain it’s just a cheap manufacturer issue I ran into. I bought essentially a no-name ESP32 at first and that’s the one that refused to last. Proper manufacturer solved that issue for me and now ESP32 works just fine.
The raspberry pi actually never worked, largely because I tried to shoehorn way too much complexity in and manage too many things. It’s just a BT scan and a HTTP call.
I don’t think it’s a power issue as it’s getting 5V1A from a power outlet directly to USB-C into the device. Though that’s definitely something I need to look into, as the Xiao ESP32-S3 I have also had intermittent issues, and IIRC the XTensa cores are more power-hungry than its RISC-V based sibling, the ESP32-C3.
> I don’t think it’s a power issue as it’s getting 5V1A from a power outlet directly to USB-C into the device.
It's not the total voltage/wattage the PSU can provide, but the voltage at the processor.
The ESP's varying current draw notoriously causes too much noise and a lot of boards don't have large enough decoupling capacitors so the voltage drops too much and it glitches out. Also a warning that USB PSU's can very MASSIVELY in quality (I'd suggest an apple one for testing if you have one handy).
I think you're right that the RISC-V processor is either better behaved and draws power more consistently, or the board has shorter traces to it's bypass capacitor or a larger bypass capacitor.
This is correct, I thought it wasn't and was going crazy trying to debug my Pi 3 resetting my 3D printer every time, with any of ten power supplies I tried, including a configurable bench PSU.
I switched to the official Pi PSU after someone said "trust me on this" online, and yep, zero issues in all the years since.
It's voltage for Pi 3. They forgot to account for voltage drop due to protection or something. Official as well as third-party Pi 3 specific adapters are rated at 5.1V to mitigate that problem.
Early alexa devices also have power supplies that are rated at 5.2V, those could be an alternative. I also had a good experience with a 30W oneplus warp charger after some power issues with cheap 5V2A ones.
I chased a reliability problem with an RPi3 for a while before figuring out it was a poor quality USB cable that I was using for power.
Not saying that’s your issue obviously, but I spent a couple more hours than I really should have swapping USB power bricks but not the cable (because it was threaded through the printer enclosure and laziness prevailed).
I didn’t consider that as highly as the outlet adapter since that’s what pushes the amperage and wattage, but thanks, I’ll definitely be investigating that next!
I've found cable quality to be quite important for Raspberry Pi, particularly if you're not using an official adapter, the head room can be low and the resistance of the cable can tip it over.
I haven't had major issues with ESP devices but I try to keep them on <30cm cables of decent quality and ensure they're shielded. Though I haven't tested experimentally, I'd expect low quality, poorly shielded cables to have some effect on the signal quality.
Just put a huge low-ESR cap on the 3V3 rail. Newer WiSoCs like ESP32 draws too much for too short that regulators can't catch up. I've once had brownouts with an Uno R3 style ESP32 board, and it didn't stop until I added a 0.22F EDLC from my junk bin, which is absurd and not a recommended usage of EDLC, but I think even 330uF electrolytic from same bin didn't cut it.
Are you sure that the system isn't still running, but it has just disconnected from wifi and is failing to reconnect? I have a few status LED's flashing to show the main CPU is still running, and it often is, even when the device has fallen off the network.
I find that happens fairly frequently unfortunately, and haven't managed to track down the cause.
Hm, that’s a good call. I have a callback on the connection dropped to reconnect but it’s possible it needs a full reboot? I’m going to have to sit in on the serial monitor and wait until something happens and see. Thanks for the tip!
I live in a very wifi-busy area (hundreds of networks), and I suspect that the wifi logic somehow hangs itself waiting for some packet/message/state which gets lost and never comes.
The raspberry pi actually never worked, largely because I tried to shoehorn way too much complexity in and manage too many things. It’s just a BT scan and a HTTP call.
I don’t think it’s a power issue as it’s getting 5V1A from a power outlet directly to USB-C into the device. Though that’s definitely something I need to look into, as the Xiao ESP32-S3 I have also had intermittent issues, and IIRC the XTensa cores are more power-hungry than its RISC-V based sibling, the ESP32-C3.