Ejector system design: choosing pins, sleeves and blades

If the ejector system is inadequate, the part sticks in the mold, warps, whitens (stress marking), or shows a mark/sink where the ejector pin pushes. Good design distributes force onto the part's strongest points, as evenly as possible.

Ejector types

• Ejector pin: The most common and cheapest solution. Used on flat surfaces and strong points like ribs/bosses. Avoided on cosmetic surfaces because it can leave a mark.
• Sleeve ejector: Pushes all the way around a boss (a circular feature like a screw boss); force is distributed more evenly, with lower mark risk than a pin. Costs more than a pin.
• Blade ejector: Used on thin ribs and narrow/long areas where a standard round pin won't fit.
• Stripper plate/ring: Preferred for thin-walled, symmetric parts (buckets, caps) to apply even force around the whole perimeter; eliminates pin marks entirely but increases mold cost.

Layout rules

1. Put force on strong points: Ribs, bosses, wall roots and other rigid areas are preferred; placing a pin on a flat, thin wall increases the risk of warping/marking.
2. Distribute symmetrically: An ejector layout concentrated on one side of the part will tilt it as it's pushed out; placement should be balanced around the center of gravity.
3. Increase count with draw depth: Deep-core parts (box, bucket types) need more than a single row of pins; a second row or a sleeve/stripper may be required.
4. Tune ejector speed/pressure: Even correct placement can leave marks if speed/pressure is wrong; the usual starting point is slow, then stepped up gradually.

Common mistake

Ejector pins should be planned not just by "where there's free space" but also by the pressure distribution of the melt during filling; if pin support is missing where pressure is highest (usually near the gate), the part can stick there.

Practical note

If a mold-flow (filling) analysis shows a pressure-distribution map, lining up ejector pins with the high-pressure points on that map reduces the number of trial-and-error iterations.