Why "full servo" is not a complete specification

A drive label describes an architecture direction, not every control responsibility. The buyer still needs to know which stations have independent motion, which groups share a reference and which adjustments remain mechanical.

Actually, the important number is not the motor count. It is the number of product relationships that can be measured, corrected and restored without losing the approved sample.

The real question is which architecture matches the factory's products, operators, maintenance skills and changeover schedule.

Read the axis map as a responsibility document

An axis map should connect each controlled motion to the physical station, master reference, feedback device, recipe item and fault response. A motor list without these columns is an inventory, not an operating model.

Ask for the axis map before comparing servo brands. Brand matters for service and spares, but it cannot repair a missing control relationship.

Start at the unwinds: control begins before forming

Welldone's published baby-care architecture describes all unwinds as servo-driven in both full-servo and semi-servo directions, while the semi-servo line retains mechanical main-shaft transmission for other functions. This is why one label cannot describe the entire line.

For each unwind, request the material name, braking or drive method, web-guiding point, tension feedback and splice logic. A lighter roll, a new material batch or a splice introduces a disturbance before the product reaches the forming station.

I believe an axis map that starts at the cutter is already too late. The first drifting material can create the defect that becomes visible several stations downstream.

Waistband lamination exposes relative-speed errors

The waistband combines nonwoven webs, elastic and bonding at one point. A small feed-ratio difference may stay hidden while the composite is flat and appear only after contraction.

Ask whether elastic feed, inner web, outer web and pull roll are independent axes or grouped functions. Then ask which relationships enter the recipe and which still require physical adjustment.

A servo motor does not prove tension control. The feedback signal and correction logic do.

Pad cutting and rotary transfer need one position story

The cutter and transfer cannot be evaluated as isolated high-speed components. The cut body must arrive at the pickup point, rotate and leave at the receiving position without losing its relationship to the waistband path.

More importantly, ask how phase error is detected. If the operator only notices a bad product after final cutting, the axis map must show how the team traces the error back to cut timing, transfer phase or upstream web movement.

Final cutting reveals drift accumulated upstream

The final cutter is blamed because the defect is visible there. Yet the cutter may follow its reference correctly while the product feature reaches it early or late.

Request registration marks, dimensional checks and alarm history that distinguish cutter phase from upstream drift. Changing the final-axis offset without finding the first wrong relationship can move the defect rather than remove it.

Automatic rejection needs product identity, not only motion

A detector can identify a defect several product pitches before the reject gate. The control system must retain that product's position until ejection.

Ask what happens to the tracking queue during deceleration, an emergency stop and restart. If product identity is cleared, the procedure must define how the unverified section is removed before good output resumes.

Separate recipe-controlled settings from change parts

A recipe can store electronic values such as ratios, phases and selected positions. It cannot replace a mold, knife, guide or mechanical spacer that changes with product geometry.

A quotation that says "quick changeover" should therefore carry two lists: stored parameters and physical tasks. Without both, the automation claim is incomplete.

Choose the architecture your maintenance team can recover

Full servo shifts more troubleshooting toward drives, encoders, networks, recipes and electronic position relationships. Semi servo retains more dependence on main-shaft transmission, belts, gears, differential joints and physical phase condition.

Neither model removes maintenance. They demand different skills, spares and diagnostic evidence. Request the alarm list, backup method, drive replacement procedure, mechanical inspection points and remote-support boundary.

A factory with limited electrical capability may need training and critical drive spares. A factory with strong mechanical technicians still needs a disciplined inspection plan for shared transmission components.

Take this axis-map checklist to Booth 19.1I29

1. Mark every unwind, feed, cutter, sealer, rotary transfer and reject function.
2. Assign each function to an independent axis, grouped drive or mechanical train.
3. Write the master reference and feedback signal beside every critical relationship.
4. Separate recipe-controlled parameters from manual settings and physical change parts.
5. Record what happens after splice, stop, emergency stop, restart and drive replacement.
6. Connect every alarm to the affected product feature and inspection evidence.
7. Carry the final map into FAT, training, spare-parts planning and handover.

The output of the booth meeting should be a marked control map and an open-item list, not a handwritten motor count.

Technical data conflict: architecture must stay tied to the exact model

These may be different machines, versions or option packages. This article does not merge them into one specification. Buyers should require a dated axis map, model reference and signed configuration for the exact quoted line.

Related project guidance

A servo label cannot replace a control map

Full servo, semi servo and mechanical architectures can only be compared when the controlled relationships are visible. The axis map shows where the line measures, corrects, stores and recovers product position.

If one critical relationship failed during the night shift, could your team identify the responsible axis, feedback signal and recovery procedure from the documents supplied?

FAQ