News for hackers. Stuff that matters.
Re:Coding Up an IoT PCB Design by Namidairo on Tuesday May 03, 2022 @11:32PM (#31256438)
I've always been a little amused when I see an entire ESP32/ESP8266 or similar module just sitting on top of boards instead of being a part of it.

I presume it's cost/complexity, but it's a weird thing that ends up as a common solution.

Re:Coding Up an IoT PCB Design by picture on Tuesday May 03, 2022 @11:34PM (#31256454)
There are some reasonable reasons, like how it may speed up passing regulations. I believe RPi used some integrated WiFi modules that had certification done separately. And yeah, there's a lot of passives in those modules that I would not want to manually assemble
Re:Coding Up an IoT PCB Design by svnt on Wednesday May 04, 2022 @02:22AM (#31257328)
The search term you want is modular certification.

The volumes necessary to justify the cost, time, risk, and specialized skill set necessary to achieve both regulatory and standards certification of a WiFi device are significant.

Re:Coding Up an IoT PCB Design by underpickled on Wednesday May 04, 2022 @09:26PM (#31268243)
If you're referring to the module on those boards, I can tell you it's because the actual IC was impossible to source. Only modules were readily available.
Re:Coding Up an IoT PCB Design by ranger_danger on Wednesday May 04, 2022 @02:44AM (#31257460)
Cost. You can easily get the premade ESP8266 boards for a quarter at scale. Laying out your own design for an ESP32 costs a lot more in time that's unnecessary usually.