Technical Guide — SMT Industry

SIPLACE Pro Programming and Component Shapes

The quality of a SIPLACE program starts with the component shapes and with how the libraries are organised. Accurate shapes, production data imported properly and optimised paths mean fewer rejects, fewer stoppages and faster cycles. Here is how a properly built program is set up.

SIPLACE Pro is the software environment used to program, optimise and manage the jobs of ASMPT pick & place machines. Beneath the surface of a production program there is work that makes the difference between a line that runs clean and one that piles up rejects: the correct definition of the component shapes, the organisation of the libraries, the accurate import of production data and path optimisation. In this technical guide we look at how to tackle each of these aspects from the point of view of someone who programs and maintains ASMPT SMT lines (our credentials). For hands-on support, ElectrONIK Lab provides SMT programming and optimisation services remotely and on-site throughout Italy.

In brief. In SIPLACE Pro the quality of a job depends above all on the correct definition of the component shapes: the model through which the machine knows the dimensions, pad/lead geometry, polarity, height and pick-up and vision parameters of every component. A shape built on the real measurements (of the component and of the tape), not on the nominal datasheet figure, drastically reduces recognition errors and false rejects; tidy libraries, accurate data import and path optimisation matter too. ElectrONIK Lab programs and optimises ASMPT SMT lines remotely and on-site throughout Italy.

1. What a component shape is and why it is decisive

The component shape is the "model" through which the machine knows a component: body dimensions, pad/lead geometry, polarity, height, pick-up parameters and vision parameters. When the machine picks a component, it compares it with its shape in order to centre it and verify it. An accurate shape guarantees reliable recognition, correct centring and a low reject rate; an inaccurate shape is the leading cause of false rejects and placement errors, as we see in the troubleshooting of SIPLACE errors.

Key principle. The shape describes the physical reality of the component, not the nominal datasheet figure. Real tolerances matter: a shape built on the actual measurements of the component (and of the tape) drastically reduces recognition errors.

2. Creating and optimising shapes

Creating a shape starts from the dimensional data of the component, but it does not end there. The steps that make the difference:

Shape optimisation is iterative work: you start from a working shape and refine it against real production data. A shape well optimised on a critical component can appreciably reduce rejects and micro-stoppages, with a direct impact on OEE.

3. Component libraries: order and reuse

A well-structured component library is an asset. Standardising shapes, avoiding duplicates, applying consistent naming and reusing validated shapes across different jobs reduces errors and speeds up the creation of new programs. The opposite chaos — duplicate shapes, inconsistent names, different parameters for the same component — is a constant source of problems: the same component that works in one job and rejects in another because it uses a different shape. Investing in a tidy library means reaping the benefits on every future program.

4. Production data import

Programs often start from the import of design data: BOM, centroid file (pick & place data, X/Y positions and rotation of the components) and PCB data. A clean import saves hours of manual work, but it requires care: the alignment between the reference designators in the BOM and the positions in the centroid file must be consistent, the rotations must follow the correct convention, and the packages must be mapped to the right shapes in the library. The most frequent errors arise here: wrong rotations, mismatch between BOM and centroids, unmapped packages. An import verified up front prevents a long session of corrections at the machine.

5. Path optimisation and balancing

SIPLACE Pro optimises the assignment of components to the heads and the feeders and the placement sequence in order to minimise cycle time. Path optimisation and line balancing determine the real production speed: distributing the components well across the machines on the line, making the most of the multiple heads, cutting unnecessary travel. A well-optimised job can produce the same board appreciably faster than one set up without care. On high-volume batches, every second of cycle time saved translates into additional production capacity. It is one of the areas where experience makes the biggest difference: the software proposes, but knowledge of the process is what allows you to choose the best setup.

6. Traceability and integration with line systems

Traceability — knowing which component, from which batch, ended up on which board — is by now a requirement in many sectors (automotive, medical, industrial). SIPLACE Pro and the ASM ecosystem support traceability at component and material level, integrating with the line management systems. Integration with platforms such as ASM OIB (Operations Information Broker) makes it possible to connect SIPLACE machines with MES, material logistics systems and document management, enabling real-time data flows: setup verification, material control, process data collection. Setting these flows up correctly is part of the value of programming done well, and it also enables the predictive maintenance we discuss in the guide on SMT line maintenance.

7. Programming and reducing downtime

Careful programming affects not only quality but also the availability of the line. Robust shapes reduce stoppages caused by recognition errors and pickup errors; well-prepared setups and correct data reduce start-up and changeover times; path optimisation raises performance. All of this feeds into the wider subject of how to reduce machine downtime on an SMT line. A program done well is, in practice, preventive maintenance carried out once that protects every subsequent production run.

Frequently Asked Questions

Why does a component reject in one job and not in another? +
Almost always because the two jobs use different shapes for the same component. It is the classic effect of a disorganised library with duplicate shapes. The solution is to standardise and reuse validated shapes from a single, tidy library.
Is it better to build shapes from the datasheet or from real samples? +
From real samples. The datasheet gives the nominal value, but the actual tolerances of the component and of the tape matter: a shape built on real measurements greatly reduces recognition errors and false rejects.
What are the most common errors when importing production data? +
Wrong rotations, a mismatch between the reference designators in the BOM and the centroid file, and packages not mapped to the correct shapes. Verifying the import up front prevents long corrections at the machine.
Can you optimise an existing SIPLACE program remotely? +
Yes. Shape review, library clean-up, path optimisation and traceability setup can largely be done remotely. We come on-site to validate in production when needed. We operate throughout Italy.

SIPLACE programming to set up or optimise?

Request programming support, remotely or on-site throughout Italy. ASMPT-certified Service Engineer.