This is a great post that should bring awareness to the board designers. I'd like to supplement the article content by proposing that simulations of the PDN (Power Distribution Network) be done prior to board fab (and during layout) to ensure that there's enough copper in the plane (or thick traces) that need to accomodate high current switching activities. In today's board design (specifically in the pwr/gnd plane structures) the designer needs to be aware that the pwr/gnd planes can be fragmented due to pin breakouts, via structures, narrow areas, etc... As such, the full current-carrying effects of the planes cannot be realized. There could be narrow areas (or neck-down) sections of the plane that must carry the required currents from the regulator to the destination devices. These types of areas are the bottlenecks in the plane structures and can cause significant (and dynamic) voltage drops when there are high current switching activities from the device power pins connecting to the rail (or GND return paths). The current will take the path of least resistance (ie. shortest path) to/from the voltage regulator so if these areas are not analyzed correctly there can be areas of high concentration of current density (mA/mil square) that potentially can heat up the traces causing breakdowns over time. The idea is to have sufficient copper pours to minimize the DC drop (or loss) voltage. The best way to fix the problem is to avoid it in the first place before the board is fabbed and components are stuffed. The bench used to be my favorite place to spend time but nowadays I spend more time in simulations than sitting on the bench measuring things. Simulations can identify issues before the board is fabbed... Now where would you rather spend time (and money)?
@zeeglen: Once - and only once - I proposed similar. The software people were like to have me strung up, drawn, and quartered for even THINKING such a heretical notion.
I recall a computer in the UK -- you could purchase one with a certain amount of computing power for a certain price -- when your company needed more computing power, you could pay for an upgrade.
The technician would come round and pull out your mother board and plug in a new "super duper" motherboard with "twice the computing power" -- once back in his van, he would take your old board and swap the jumper from 1X clock to 2X clock, then that was the "new" board he would take into the next company...
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.