Search

Wednesday, 9 November 2016

Top 15 EMC Design Considerations for your electronics product

As a personal note, I was listing out the considerations I do before floor planning of the PCB. Almost all these points should be kept in mind before planning to place the components as well as when you are doing the PCB layout. Here, at Leaf Design Lab, I take utmost care while designing the high-speed layouts of DRAMs, SRAMs, eMMCs, Ethernet and HDMIs with multi-core processors and avoid most of the EMC issues right the first time. Most of the issues can be taken care at the layout stage, but there are plenty during the components selection/ schematics preparation stage to take care, which I will list down in upcoming posts. Here we go:

1. Related to Ground Plane

  1. Avoid high Impedance Ground paths to components; thus increase the size of the ground plane (GND) as much as you can. An ideal way is to dedicate a whole layer for GND just beneath the decoupling in a multi-layer PCBs.
  2. Avoid Long Ground Loops, which in fact acts as an antenna and radiates the energy.
  3. Use more than 2 layer PCB for better EMC performance or Use ground grids for 2 Layer PCB (As per personal experience, this is difficult as you have very less freedom to route on 2 layer board already.)
4. Do not make the ground line common and terminate to ground. Use dedicated lines for the parallel components to connect to ground. Use separate vias for each ground termination, if there is a separate ground plane beneath as shown in the image here. [This is the 3D model of the same PCB in the cover image. See the Decoupling flower beneath "C" character in the image.]
5. High-Speed traces nearest reference plane to be solid ground to avoid impedance mismatches and thus avoiding ringing, reflections, undershoots or overshoots due to them. Check the PCB stack-up; if a high-speed signal layer is near to power plane, avoid the plane crossing.
2. Use Faraday cage surrounding whole board. Use via stitching to create a cage for internal emissions to be inside and external emission to be outside. No signal traces should be routed out of the Faraday cage. As shown in the images below, the faraday caging and via shielding is done. It should be done as per your manufacturer's capability keeping in mind that the tolerances and clearance constraints are met.
3. Layers and Power Plane: 20H Rule (Check my detailed post here for Faraday Caging and 20H rule)
4. Make Rooms and Place components as per segments. Use filters at the segment boundaries (Difficult to keep the filters for high-bit parallel lines due to tight real estate on the board and to reduce the overall system cost. Must if you are making a product of Med-Mil standard)
5. Use planned Board Stackup to avoid cross talks and to keep proper reference planes for high-speed traces. (It's a big topic in itself, so avoiding the explanation here)
6. Keep high-speed signals and clock traces as short as possible and keep them nearer to the ground plane (although, there is a trade-off between impedance matching and crosstalk for high-speed lines because of strict rules of transmission lines) and away from the board edge. Vias in such signal near the connector and PCB edge must be avoided. Keep away such signals from Power plane as well to reduce the inducing noise on power planes.
7. Differential lines must run in parallel to cancel the magnetic fields of these out-of-phase lines. Adjust/tune the length of shorter running differential line near the source by adding a small serpentine.
8. A return path of the signal should run closely in parallel with the associated signal trace to provide least reactance path creating the shortest current loop.
9. Keep Crystal oscillator traces very short and place such crystals near to the chip. Keep ground test point near to such crystals or oscillators, if in case there is a need to ground the body of a crystal during the testing period to check the changes in emissions.
10. Terminate the floating clocks with suitable matching termination network. Series termination, parallel, thavenin or AC termination, etc are the type of clock terminations. Series termination should be placed at the driver side. It consumes low power but increases rise and fall times of the signal. In most designs, 20ohms to 33ohms are enough for the series termination.
11. Avoid the impedance mismatches on clock lines (especially in high-speed/DDR clock lines) to avoid the reflections in the signal in form of radiations. Introduce the impedance matching on the traces by considering them as transmission lines over 30MHz. To match the impedance of these lines : Trace thickness, Ground Clearances, PCB stack, dielectric constants of the PCB materials and reference plane plays a crucial role. Highlighted differential lines in the image above are 100 Ohm impedance matched 4*16bit DDR3 DQS clock with air-gap of 5.3mils and trace thickness of 3.7mils.
12. Analog signals are highly affected by high-speed and switching signals. Guard the signal with the ground trace and stitch the ground trace with the vias to create a shielding for the analog signal. Do not share the ground planes of Analog and Digital subsystems, isolate them with inductor or ferrite bead. Following is the example of TWL6040 Audio Codec IC with analog and digital ground isolated by inductor/ferrite bead. **Please note that the signal is on layer 6 with a solid analog ground plane on layer 7 hence not crossing any planes. The analog and digital grounds are isolated on layer 2.
13. Noise coupled on the power supply rail is high frequency due to AC-DC and DC-DC switchers into the power management system. The decoupling capacitor provides a low-impedance path for high-frequency current and thus decouples such noise from power plane to the ground. Such capacitors should be placed inside 50mil area near the power pin of the processor. Use capacitor with low ESL and low ESR values. Moreover, choose the rated voltage of capacitor by 5-10 times of operating voltage to keep in mind the derating at certain voltages.
14. Add metallic shielding over potential emitting components or on the components to sustain the ambient radiation. Multiple shields can be added to a single board to attenuate the radiation from one region of the board on the other. This attenuates both E-field and H-field component of the radiated electromagnetic waves.
15. Use shielded cables for high-speed data lines or twisted pair cables. Use multiple return paths in a flat ribbon cable.
Not everytime you can address all the points to rectify the issues. Sometimes, there is a tight budget BoM or sometimes there can be real estate shortage on the board. Hope, you liked this article; it's been a long time since I have written an article here. Let me know if there are any of the top techniques that I have missed. I will keep updating the feed with different articles. You can discuss your EMC issues right here in the comment section or you can directly message me!

Cheers,
Rushi.

Sunday, 25 October 2015

Shopping List for Raspberry Pi Sensors

Hi All,

The response on the book is overwhelming. Thanks to all the readers around. My email is kept buzzed all around by your automated emails from Raspberry Pi. Love you all!

As included in the appendix section, just adding the shopping list for anyone who has purchased the Raspberry Pi sensors book! Here's what you require to purchase.

Basic Requirements

Raspberry Pi [Raspberry Pi 1 Model B or Raspberry Pi 1 Model B+ or Raspberry Pi 1 Model A+ or Raspberry Pi 2 Model B]
Micro-SD Card with SD adapter with storage capacity of 8GB or more
Personal Computer with Windows or Mac OS X or Linux environment
Ethernet Cable (RJ45)
5V 1A or 5V 2A Power adapter with micro-USB connector
HDMI or RCA Cable
Breadboard
Multimeter
Wire Stripper

Sensors

HC-SR04 Ultrasonic Sensor [Quantity: 1]
DHT11 Temperature-Humidity Sensor [Quantity: 1]
LDR or CdS Photocell or Photoresistor [Quantity: 1]
TMP35 or LM35 or TMP36 Temperature Sensor [Quantity: 1]

Integrated Chips

Analog to digital Convertor [Quantity: 1]: MCP3008 Dual-in-Line package or MCP3004 Dual-in-Line package

Components

¼ Watts through hole Resistors [Quantity: 5 each]: 1KΩ, 2KΩ, 270Ω, 330Ω, 470Ω, 4.7KΩ, 10KΩ
Electrolytic Capacitor [Quantity: 5 each]: 1µF-16V
LEDs [Quantity: 5 each]: 2mm or 3mm or 5mm Red/Green/White/Yellow LED

Others

Single stranded wire [Quantity: 1 meter]
Female to Male Jumper wires [Quantity: 15], Female to Female jumper wires [Quantity: 15]
Bergstik connectors [Quantity: 2 each]: (Dual-row male, 2.54mm Pitch), (Single-row male, 2.54mm Pitch)
Female to Female GPIO ribbon cable for RasPi 1 model B (26 pin) or B+(40 Pin), RasPi 2 Model B(40 pin) [Quantity: 1]
General Purpose Circuit Board dual sided solderable
Soldering Iron Pencil type (30-50 Watts)
Soldering Wire with Flux [Quantity: 50gms]
Camera [Quantity: 1]: Logitech C270 USB Web-cam or Raspberry Pi camera



Raspberry Pi Sensors
and
Integrate sensors into your Raspberry Pi projects and let your powerful microcomputer interact with the physical world!

Sunday, 27 September 2015

Obsessed with Internet of Things? Ok. The things are connected. So now what...?

"Total Number of internet connected devices reached 8.7 billion in 2012" - X source

"The growing network of connected objects referred to as the “Internet of Things” is estimated to be in the billions by 2020." - Y Source

"The Internet of Things (IoT) is one of the fastest growing areas of tech – covering everything from consumer wearable devices to high-tech industrial systems." - Z Source

"IoT is completely a disruptive technology according to analysis."  - Z' Source


There are multiple opinions on from different sources which make the world so obsessed with the IoT. But really, Internet of things is far bigger than anyone realizes. Some people tell that it's the term given to the connected things and it's just about providing IPv6 to any "thing" that is available in the vicinity. 
Be it the massive infrastructures, be it your pillow, be it your home, or be it your clothes, it's not about connecting the sensor to the multiple Arduinos and RaspberryPis and connecting it to the internet, It's about building the ecosystem. It's not about connecting relay to the Internet to control the appliances, but It's about the intelligent architecture that very well suits the need of the users, may it be using artificial neural networks or may it be using the multiple algorithms for enhancing the user experience. Honchos are building the Skytran and that is the kind of solutions the world really wants. "Air" is built with the same vision and philosophy. We are here to deliver the extra mile!
When developers are talking about delivering an extra mile to enhance the human living experience, they’re still not thinking big enough to justify the needs of the world. It’s not a lack of creativity; it’s a lack of scrutiny. Future is always within our vision, and you don’t need to visualize or build what’s already there.
"A solitary fantasy can transform a million realities" - Maya Angelou

3 essential rules for IoT Businesses

Here is my take! There may be many rules for the successful IoT business, but I would like to encompass these three as the essentials to build the successful IoT product. It's about M2M and IoT (It took me long to understand difference between M2M and IoT, and if you don't know, Here is a good article) therefore it's all on us, to understand where it's leading to.

 Rule 1: Data


It's just not about delivering the product, It's about leveraging the data which is created from millions of end nodes. Obviously, we would require powerful data storage capability and tremendous remote processing power to understand the sheer amount of collected data and to build the intelligence in the system for better predictions and controls.

Rule 2: Security and Robustness

Who likes it when connectivity becomes unstable? Nobody enjoys the interrupted signals and improper codecs. Thus the connection protocol aspect of IoT is incredibly critical to give users that seamless, “always on and interacting” feel -- what’s the point of always having technology with you if it isn’t going to be always connected? Consumer devices in particular – from fitness trackers to home appliances – are generating more granular information. And when that information is about people or their health, it’s more sensitive.

Rule 3: User Interface/Experience

Similar to the previous point, nobody enjoys the broken user experience. Be it developers or the product end users, they need a flawless system to hack and play around with minimal hassles.
"IoT is not the 'Thing' that gains the Internet, It's that the Internet gains from the Thing." - Patrick Isacson

Accessories

There is an idea of many developers who are working for IoT, to build an ecosystem(SDKs) for the developers to build on their own platform. It may take many skills with many skill resources to design and deliver a successful IoT platform that is both scalable and extensible to be versatile. According to the Reuters "The IoT Platform Companies Database 2015", there are 250+ platforms available to start development on IoT so there are 180+ startups, 45+ SMEs, and 25+ MNCs which offers such platforms. This is really alarming! Who will connect these all platform to make the "ONE internet of things"? This is really needed to leverage the data mining and to provide better analytics. "ONE Internet of things" not only can make businesses more efficient but makes the businesses ready for future!
Why do I call it an accessory? Because, this is currently "announced" as an add-on to almost every internet of things product sold! It is treated as an accessory! As the Internet of things is said so abstract and developers and designers are busy creating their own hardware and software platforms with different open/proprietary protocols, and shouting that their platform having cool X-Y-Z features is too much obsession for the people. This will ignite developers to start talking about the Web of Things! Similarly to what the Web (Application Layer) is to the Internet (Network Layer), the Web of Things provides an Application Layer that simplifies the creation of Internet of Things applications. Web of Things reuses existing and popular Web standards. But I am still concerned at the common/cross-platforms solutions on which multiple devices can communicate. It is an open discussion, though!


Security

Are we ready enough? 
As everyone started turning to Internet of things and as everybody is talking about the IoT, the term "Security in Internet of Things" has become too popular to discuss on every IoT tech geek's breakfast table. Some devices fall short of enough stack in the tiny microcontrollers used as an actuator end-point, or some devices are just about being low power without any security engines running. As users become more reliant on smart devices and wearables, an increasing amount of sensitive data is being accessed through these devices and transferred among them. The developers must strengthen the defenses by taking clues from the smartphone developers and industry.  But it is not easy as to just talking about the security. There's much more work needed for low power and low memory embedded devices.
Product development—at least for products that anyone expects to be successful—has always been iterative, incremental, and collaborative.
Now, it's upon us being the builders, the innovators, the creators or the end user to bring the IoT to a stage where all work on a unified platform. It's a big task to create "ONE internet of things" but filled with too many opportunities for everyone around us to change the world we see today!
Thanks in advance for your Likes and Shares. It would be great to have your added thoughts on this.