The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I have used the standard ESP32 board for a complicated project using I2C, SPI, Wifi and ULP code. Worked like a charm, never noticed anything weird or unstable about it. Probably a case of wanting to shift the blame to someone else.
No worries, I will follow your advice and never buy an Adafruit version.
As to the original ESP32's version: SPI really did work well on that. I used it quite a lot to shift a lot of data to and from the built in Serial flash, thousands and thousands of recorded analogue data samples which were neatly sent to a remote server using the WiFi component. Really nice performance for a 7...8 Euro unit.
I don't think I would condemn them that hard. I have never purchased any microcontrollers from them but have bought some devices. Their programming libraries are good for starting out. I am using a couple of temperature modules and a Temp/Humidity/Pressure module for an exercise to use Blazor, running on a Pi, as a dashboard. Started at Adafruit. No worries. Now, the temp module is $4.95 from them and $0.77 from Alibaba (+ $1.75, 30-50 days shipping). I would guess that all of that stuff is sourced from China. I have never tried to get support from Ada, but I guess you could view your experience 2 ways. One way is they were honest with you, and maybe ask for your money back. The IoT world is full of hype, cheating, and lying as well as good stuff. I like the good stuff (always look at the datasheets).
Like they say: Good, Cheap, Fast: pick any 2.
Pi's rock and start at about $8.
The I2C bus was never really intended for the way we use it, FWICS.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
You did not see, in person, the joy in the streets I witnessed.
It's an event - an experience - that cannot be; should not be - forgotten.
What is telling, however, is you're making yourself some sort of victim-to-be, some sort of martyr in the making. I will skip enumerating from the pathetic-yet-laughable script, of the same nature, read aloud by what I see as "the other side".
There's a bunch of people, not all of them in Washington, DC, that just plain have to get over themselves. Or, at the least, reminisces about their past posts and realize that "what goes around comes around".
I've been wrestling with a problem all morning for what I thought would be a simple clock that also fetched weather information and exposed a tiny website on the home network at http://clock.local that will get the time and weather information. Simple, right?
The trouble I've been having is trying to get this thing to do WPS connect in the background. Everything has to be interrupt driven because I have no threads/scheduler and that's fine, but then I basically need a coroutine (like yield in C#) around all of the call backs because i have to ...
and I just figured out the solution.
woo. I'm leaving this here because i love when that happens.
Anyway, I love not having to deal with threads. I love that callbacks are safe to set global variables from.
Everything is so bloody simple. Yay.
But also, everything is so bloody simple. Boo!
Expect more articles. These things should keep me in material for at least the next month.
One problem with that is garbage collection. By nature garbage collectors tend to want to reserve a lot of memory. It's possible in theory to do .NET on a limited host, but maybe not something so limited as an ESP32. I could be wrong.
C++ isn't so bad, especially when coding these little things. There's no room for templates (what C# calls generics) so the code isn't actually that confusing. Most of it is C ish. There's very few reasons to do pointer ops so you won't typically be using things like * or -> except maybe * occasionally when dealing with strings.
Another option for some of these things is micropython which is python with a stripped down runtime.
There's no room for templates (what C# calls generics) so the code isn't actually that confusing. Most of it is C ish. There's very few reasons to do pointer ops so you won't typically be using things like * or -> except maybe * occasionally when dealing with strings
It is C++: templates can be used and have their usage (possibly you mean STL containers and the like...).
"In testa che avete, Signor di Ceprano?"
They have their usage but you have to understand you have very little SRAM for program storage - it's precious, and templates tend to bloat code where every literally byte counts. It's why they're barely used by Arduino library writers. This isn't the same as coding for a PC for example.