[martin_a]

ESP32s are _sick_!

I've only been building things with Arduino Uno/Nano/Mega (clones) so far and they are kind of limited. Those ESP32 I've now got seem to have _everything_ onboard: lots of IO pins, hardware PWM (although I do not understand that fully yet), WiFi, Bluetooth, hall and temperature sensor onboard.

All of that for 8 Euro/piece. It's sick for IoT projects, really looking forward to doing more of that.

I've got these: https://www.amazon.de/dp/B074RGW2VQ

edit: I'd love if Arduino et. al. would start using USB-C plugs though. I've got everything from USB-A to micro USB around here and I'm constantly looking for the right cable to use a board. Does anybody know why they haven't switched to USB-C yet?

[Gigachad]

I suspect USB-C connectors just cost 5 cents more so they aren't used on most dirt cheap dev boards. I've seen adafruit update their stuff to USB-C but they also charge a good premium over the generic ebay clones.

[skybrian]

Shop around, there are boards that have USB-C connectors. I've seen some on Adafruit.

[martin_a]

Thanks, I'll have a look around!

[girvo]

Amusingly, the PWM output we do on our firmware is actually done using the RMT infrared remote control peripheral instead, as the LED strips we need to control are too fast for the internal PWM controller lol

[martin_a]

I just had a quick glance at the PWM documentation but I don't fully grasp it anyway: I select one of the 16 internal PWM controllers, set it's clock/frequency and then bind an output pin to that.

I thought that fading a LED would then stick to the frequency of the PWM controllers, but it seems I still have to take care of the speed?

I thought setting the PWM frequency to 100 Hz and cycling my LED brightness from 1 to 100 would take 1 second. It doesn't work that way it seems?!?