News & Updates

Designing high-speed channels on complex boards requires simulations, measurements on test boards, or both to ensure the design operates as you intend. Gibbs ringing is one of these effects that can occur when calculating a channel’s response using band-limited network parameters. Just as is the case in measurements, Gibbs ringing can occur in channel simulations due to the fact that network parameters are typically band-limited.

In electronics, there is the possibility that your PCB can get pretty hot due to power dissipation in certain components. There are many things to consider when dealing with heat in your board, and it starts with determining power dissipation in your design during schematic capture. If you happen to be operating within safe limits in a high power device, you might need an SMD heat sink on certain components. Ultimately, this could save your components, your product, and even the operator.

One thing is certain: power supply designs can get much more complex than simply routing DC power lines to your components. RF power supply designs require special care to ensure they will function without transferring excessive noise between portions of the system, something that is made more difficult due to the high power levels involved. In addition to careful layout, circuitry needs to be designed such that the system provides highly efficient power conversion and delivery to each subsection of the system.

Overvoltage, overcurrent, and heat are the three most likely events that can destroy our expensive silicon-based components or reduce our product’s life expectancy. The effects are often quite instant, but our product might survive several months of chronic overstress before giving up the ghost in some cases. Without adequate protection, our circuit can be vulnerable to damage, so what should we do? Or do we need to do anything?

Today’s PCB designers and layout engineers often need to put on their simulation hat to learn more about the products they build. When you need to perform simulations, you need models for components, and simulation models often need to be shared with other team members at the project level or component level. What’s the best way for Altium Designer users to share this data? Read this article to learn more about sharing your models with other design participants. 

When some designers start talking materials, they probably default to FR4 laminates. The reality is there are many FR4 materials, each with relatively similar structure and a range of material property values. Designs on FR4 are quite different from those encountered at the low GHz range and mmWave frequencies. So what exactly changes at high frequencies, and what makes these materials different? To see just what makes a specific laminate useful as an RF PCB material, take a look at our guide below. 

In today’s fast-paced world where iterations of electronics are spun at lightning speeds, we often forget one of the most critical aspects of development: testing. Even if we have that fancy test team, are we really able to utilize them for every modification, every small and insignificant change that we make to our prototypes? In this article, we will review a very low cost, yet highly effective and quite exhaustive test system that will get you that bang for your buck that you’ve been looking for.

If you’ve ever looked at the BOM for a reference design or an open-source project, you may have seen a comment in some of the entries in your BOM. This comment is either “DNP” or “DNI”. If you think about it, every component placed in the PCB requires some level of placement and routing effort, which takes time and money if you’re working for a client. This begs the question, why would anyone design a board with components they don’t plan to include in the final assembly?

When it’s time to share your design data with your manufacturer, it’s like taking a leap of faith. Sending off a complete documentation package might seem as easy as placing your fab files in a zip folder, but there are better ways to ensure your manufacturer understands your project and has access to all your design data. For Altium Designer users, there are multiple options for creating and packaging release data into a complete package for your manufacturers.

If you’re designing a circuit board to be powered by anything except a bench-top regulated power supply, you’ll need to select a power regulator to place on your board. Just like any other component, your regulator has stated operating specs you’ll see in a product summary, and it has more detailed specs you’ll find in a datasheet. The fine details in your datasheets are easy to overlook, but they are the major factors that determine how your component will interact with the rest of your system.

It would be nice if the power that came from the wall was truly noise-free. Unfortunately, this is not the case, and although a power system can appear to output a clean sine wave, zooming into an oscilloscope trace or using an FFT will tell you a different story. When you take "dirty" power, put it through rectification, and then pass it through a switching regulator, you introduce additional noise into the system that further degrades power quality. If you’re a power supply or power systems designer, then you know the value of supplying your devices with clean, noise-free power.

If you’re an electronics designer or you’re just beginning your career as an engineer, the PCB stackup is probably one of the last things you’ll think about. Simple items like PCB copper thickness and board thickness can get pushed to the back burner, but you’ll need to think about these two points for many applications as not every board will be fabricated on a standard 1.57 mm two-layer PCB

I often get questions from designers asking about things like signal integrity and power integrity, and this most recent question forced me to think about some basic routing practices near planes and copper pour. "Is it okay to route signal traces on the same layer as power planes? I’ve seen some stackup guidelines that suggest this is fine, but no one provides solid advice." Once again, we have a great example of a long-standing design guideline without enough context.