Creating an Embedded Side-View LED
The Bluetooth Sentinel design, included with Altium Designer 14’s installation, gives a good introduction to some of the new rigid-flex tools available. I was asked to modify this design to incorporate a different style of flexible region, but the repurposed board was left without room to place LEDs around its perimeter. Finding a way to add the LEDs back in posed an interesting challenge, and gave the perfect opportunity to try out some of the new tools.
One of the cool new features added for AD14 is the ability to embed components within the board. This can be done for a number of reasons, including cutting down on space in very dense designs, and shortening return lengths in high speed applications. For the modified Bluetooth Sentinel design, an alternative was needed for the LEDs, and embedding Side-View LEDs maintained the original functionality of the design tools, without having to modify it too much.
A thin package like the 48-213 SMD LED to the left was ideal for embedding, but really, the choice was only limited by the amount of vertical space available in the board. Creating this footprint was fairly straightforward, with only a couple minor additions to take advantage of the new features.
1. Footprint information and package dimensions were both available in the datasheet. When creating a footprint, one of the fastest ways to achieve a good end result is to set an appropriate Reference Point and Grid spacing. From there, it’s simply a matter of placing Pads, 3D Bodies, and any additional Mechanical information required.
2. Extruded bodies worked fine for most parts of the LED, the lens object being the lone exception. While the extruded bodies are surprisingly robust, and work well for polygonal shapes, the arced corners of the lens were more feasible to create externally and bring in as a STEP model.
3. Preparing a component to be embedded starts from the footprint itself. A Cavity - simply a Solid Region configured as shown - must be placed in the Library. Its height, as defined from the Properties, should be just large enough to allow for the component body. The LED package was 0.3mm, so the Cavity was created with a height of 0.35mm. This, of course, will ultimately depend on your specific Layer Stack and overall design intent.
4. [a][b][c]It’s important to note that Cavities can be placed within any footprint, whether or not it will ever be embedded. When the component is placed on an inner layer, the Cavity will carve out a section of the core material, but on an outer layer, it won’t affect the design in any way. Placing one of the newly-created LEDs on an inner layer showed how cool this looks in action.
5. Technically, a Cavity alters the Layer Stack in that particular area, and it’s crucial that this information is conveyed through fabrication notes. The Layer Stack Diagram that can be automatically generated and placed already takes this into account. In this design, there was no question where the Cavities were added, or what layers from the stackup were included in those areas.
6. Assembly must also be considered, since embedded components are placed before those on the outside of the board. It’s a good idea to create a separate pick and place report, as well as an extra assembly drawing printout, for any inner layers embedded with components.
I’ve included the footprint and completed design for reference, but this is certainly not the limit of how embedded components can be used. Just an interesting way to solve this problem!
[a]It's worth mentioning that the cavity can be a part of the component even when it's not embedded - it just automatically does it's job when you move the component to inner layers.
Then it's also worth *mentioning* what fabrication and assembly outputs would be needed - the layer stack table showing cavity regions, as well as separate Pick and Place report for the embedded parts, since they are mounted in an earlier process step.
[b]i was going to include a whole thing about how the cavities show in the layer stack diagram - it's too cool to pass up
About the AuthorMore Content by Max Clemons