Tutorial: Improving the transient immunity of your microcontroller-based embedded design - Part 2
Nov 17 2006 (9:15 AM), Embedded.com
The hardware design techniques employed for an application will establish the baseline immunity performance. The purpose of hardware techniques is to reduce the level or frequency content of immunity signals below that needed to cause performance degradation or long-term microcontroller (MCU) reliability problems.
Hardware techniques should be maximized to ensure desired electromagnetic compatibility (EMC) performance before attempting any software techniques. This is important because software techniques do not reduce the level of immunity signals to which the MCU is exposed " they only reduce the impact of these signals on system operation. Even though the application performance may not be degraded, exposure to immunity signals can adversely affect long-term reliability.
In order to produce an application that meets both the mandated EMC requirements and minimizes cost, the design process must be both methodical and iterative. Rigorous system and PCB design methodologies are required to ensure quality and consistency in the design process. Without such methodologies, achieving EMC compliance will be accidental and unrepeatable. The design process must also be iterative to ensure the best possible system design and PCB layout at the lowest cost.
A design that minimizes cost cannot be completed properly in one pass " regardless of the quality of personnel or tools. An EMC-compliant, low-cost application is the result of close and consistent collaboration between the EMC engineer and all other engineering disciplines (i.e. " electrical engineers, mechanical engineers, PCB layout engineers, etc).
E-mail This Article | Printer-Friendly Page |
Related Articles
- Internal JTAG - A cutting-edge solution for embedded instrument testing in SoC: Part 2
- Optimizing embedded software for power efficiency: Part 2 - Minimizing hardware power
- Improving ASIP code generation and back-end compilation: Part 2
- Guide to VHDL for embedded software developers: Part 2 - More essential commands
- Using cryptography to secure embedded device authentication profiles: Part 2