Automated Screwdriving State Control: Datum to Rework
This guide is for manufacturing engineers, assembly-process owners, controls engineers, integrators, quality teams, and maintenance planners defining a fastening cell. EVST frames the problem as state ownership: each transition should either produce evidence for the next step or route the assembly to a known exception state.
What the reviewed sequence shows—and what it cannot prove
The usable sequence supports a bounded observation of an automated tool approaching and working over a located metal assembly in an industrial fixture area. Repeated tool-to-workpiece action is visible. That is enough to discuss the questions a screwdriving project should answer, but not enough to infer the answers for this installation.
The sequence does not establish fastener identity, feeder condition, hole position, thread engagement, bit condition, torque or angle history, seating depth, head position, joint quality, cycle time, continuous-run stability, fault recovery, or traceability. It also does not establish safety validation, compliance, or certification. Those conclusions require project records beyond the visible action.
Key decisions before equipment selection
- Define the fastener family, presentation state, and proof that the correct fastener reached the driver.
- Define the workpiece and hole datum through loading, clamping, fastening, and removal.
- Specify bit engagement, alignment, compliance, and tool-service states.
- Separate motion completion, fastening-result evidence, and product acceptance.
- Give every screw position, retry, diversion, rework, and release decision a traceable state.
Choose an architecture by state ownership, not headline speed
The driver arrangement changes where identity, alignment, result, and recovery states live. Compare the options against the actual product mix and exception policy before estimating output.
| Architecture | Useful starting condition | State evidence to preserve | Recovery question |
|---|---|---|---|
| One spindle, one fastener family, sequential positions | A common fastener and tool setup serves several accessible points | Active position, fastener-present state, attempt number, result per hole, and completed-position map | Can an interrupted part resume at one known hole without repeating an accepted point? |
| One spindle, mixed fastener recipe | Different positions need controlled changes in fastener, bit, or driver parameters | Recipe revision, fastener source, bit or tool identity, verified change state, and result per position | How is a wrong or uncertain change prevented from reaching the next hole? |
| Multiple spindles, simultaneous pattern | A stable geometry and common operation support parallel engagement | Spindle identity, individual engagement and result evidence, fixture load, and complete pattern status | Can one failed spindle be isolated without marking the full pattern accepted? |
| Fixed driver, indexed workpiece | Part presentation can bring each hole to a controlled driver axis | Index position, clamp state, hole eligibility, driver result, and transfer ownership | After a stop, how is the physical index reconciled with the stored completed-position map? |
Start with fastener identity and feeding state
A feed cycle should not collapse into one “ready” bit. The useful state model distinguishes the expected fastener family, available stock, orientation, transfer, arrival at the escapement or pickup point, retention at the bit or nosepiece, and any purge or clearing action. The sensing method can vary, but the next motion should not assume a fastener merely because a feeder command completed.
For mixed products, define how the cell prevents carryover from the previous recipe. Residual fasteners in a tube, rail, escapement, bowl, or handheld replenishment route can create an identity problem even when the controller loaded the correct program. A controlled change may require emptying, segregation, verification, and a recorded return-to-ready condition.
EVST recommends specifying uncertainty explicitly. “No fastener detected,” “fastener detected but identity unconfirmed,” and “transfer interrupted” should not all enter the same retry loop, because each condition can leave different hardware in the feed path.
Carry the workpiece and hole datum into the tool axis
Robot repeatability alone does not define the relationship between the bit and the thread axis. The datum chain can include incoming part variation, fixture location, clamp seating, part compliance, hole position, robot base and tool frames, driver mounting, bit runout, and any vision or probing correction. Identify which elements are measured, mechanically constrained, assumed, or allowed to float.
A workpiece-present signal is not the same as a workpiece-correctly-seated signal. If chips, a bent feature, an incomplete clamp, or a variant mismatch shifts the hole, the tool may still reach its programmed point. The cell should determine whether the datum is valid before engagement and define a stop or diversion state when it is not.
When several screws constrain one assembly, the first accepted fastening can change the relationship seen by later positions. The validation plan should therefore examine the full order, clamping strategy, and part stack rather than qualify each coordinate only in isolation.
Design bit engagement, alignment, and floating as one interface
The bit, fastener recess, nosepiece, driver axis, and hole axis form a temporary mechanical interface. A compliant or floating element can accommodate a defined range of positional or angular mismatch, but it cannot prove that the correct fastener or hole is present. Too little accommodation can increase side loading; uncontrolled accommodation can hide a poor datum until engagement fails.
Define how the tool approaches, captures or retains the fastener, establishes axial contact, begins rotation, and reacts if engagement does not develop as expected. Bit wear, contamination, magnetic or vacuum retention state, nosepiece contact, and cable or hose forces can change this interface over time. Tool-service status should therefore be part of production state, not a maintenance note detached from the result record.
Separate commanded motion from fastening-result evidence
A robot reaching the programmed end point shows that motion execution progressed. It does not by itself establish that the threads engaged, the joint seated, or the product met its fastening requirement. Likewise, a driver reaching one numerical threshold may be necessary for a project but is not a universal proof of an acceptable joint.
Result evidence can include project-specific combinations of torque, angle, rundown behavior, time, depth, head position, axial displacement, presence checks, or downstream inspection. The required combination depends on the fastener, thread-forming or pre-threaded condition, material stack, joint design, tool, and acceptance plan. Avoid turning a convenient signal into a quality claim it was never validated to support.
The official ISO 5393:2017 standard page describes a laboratory performance test method for powered assembly tools used with threaded fasteners, including torque repeatability and built-in torque measurement precision. It provides tool-performance context; it does not define a project’s fastening value, acceptance window, or product-specific proof of joint quality.
Make multi-screw order part of the recipe
A multi-screw recipe should identify every fastening position and its permitted order, prerequisites, and completion evidence. If the order is flexible, record the rule that selects the next eligible position. If the order is fixed, prevent a bypass from appearing as a completed assembly.
The position map should survive pauses, tool changes, replenishment, controlled retries, and handoff to another station. A global “cycle complete” flag is insufficient when one screw is uncertain. Retaining status per position allows the controller and quality system to distinguish accepted, not attempted, attempted but uncertain, rejected, and rework-complete conditions.
For simultaneous multiple spindles, keep results separable by spindle and hole. A single group result can obscure one channel that did not engage or one driver whose evidence is missing. The project must decide whether the whole pattern is held, selectively reworked, or inspected by another method.
Route exceptions before designing retries
Automatic retry is not a neutral recovery. A second attempt can act on a fastener left partly engaged, a fastener dropped near the product, a damaged recess, a crossed thread, an empty bit, or the wrong hole. First classify the known and unknown state; then permit only the recovery action validated for that class.
| Exception class | Containment state | Evidence before re-entry |
|---|---|---|
| Feed or identity uncertain | Stop the fastening attempt and isolate the feed path or affected assembly | Known fastener identity, cleared residual hardware, restored presentation, and reconciled recipe |
| Datum or clamp invalid | Prevent tool engagement and hold the workpiece | Correct part identity, seating, clamp state, and verified hole relationship |
| Engagement or result uncertain | Mark the individual position as unresolved and block normal release | Disposition based on joint condition, preserved first-attempt record, and authorized next action |
| Sequence interrupted | Freeze the completed-position map and physical part location | Controller state reconciled with actual index, screw positions, tool, feeder, and fixture |
| Inspection or record missing | Divert the assembly from accepted output | Completed verification or approved disposition with traceable ownership |
A rework station also needs a state contract. It should receive the product identity, unresolved position, prior attempts, tool and recipe context, allowed action, and release authority. Rework is not complete merely because another driver cycle ran.
Build traceability around decisions
A useful fastening record explains why the cell moved from one state to the next. Depending on the application, fields may include product or carrier identity, fastener family, feeder and tool identity, recipe revision, hole position, attempt number, timestamps, result signals, disposition, operator or system action, and release decision. Retain only the fields justified by product, quality, regulatory, and operational requirements.
Traceability should remain readable after exceptions. If a failed attempt is overwritten by a successful retry, the record no longer explains the product history. EVST favors append-style event records or an equivalent method that preserves attempts and dispositions while still exposing one current state for operations.
Validate the state chain in stages
- Fix the product revision, fastener family, joint design, hole map, fixture concept, tool stack, and intended acceptance evidence.
- Verify fastener identity, orientation, transfer, retention, purge, and replenishment states.
- Measure the datum chain from incoming workpiece through clamp, hole, robot, driver, bit, and any compliance element.
- Exercise engagement with representative part, fastener, tool, and bit conditions, including planned service limits.
- Confirm result evidence per hole without treating robot motion completion as product acceptance.
- Run the complete multi-screw order and reconcile the stored position map with the physical assembly.
- Force feed, datum, engagement, result, interruption, inspection, and record-loss cases.
- Verify diversion, rework, return-to-ready evidence, and the authority that permits product release.
This is an engineering validation sequence, not a universal acceptance recipe. Numerical settings, tolerances, samples, run duration, maintenance limits, allowed retries, and sign-off rules remain project decisions.
Safety and standards context
The official ISO 10218-2:2025 standard page provides requirements context for industrial robot applications and robot cells. The official ISO 12100:2010 standard page describes machinery risk-assessment and risk-reduction principles.
These sources do not establish that the reviewed sequence or a proposed concept is safe, compliant, or certified. Applicable law, standards, equipment instructions, risk assessment, safeguarding, validation, and operating procedures must be determined for the installed cell and jurisdiction.
Four bounded statements that can be cited
Automated screwdriving is a state-control problem: fastener identity, workpiece datum, tool engagement, per-position result, and exception disposition must remain connected.
A robot reaching a programmed point establishes motion progress, not universal proof that a threaded joint is acceptable.
Floating or compliant tooling can accommodate a validated alignment range; it cannot correct an unknown fastener, wrong hole, or invalid workpiece datum.
The reviewed sequence supports observation of repeated tool-to-workpiece action, not a measured claim about fastening result, cycle time, continuous-run stability, safety validation, compliance, or certification.
Related engineering guides
- Blow-feed screw fastening, torque evidence, and traceability considerations
- Dual-stud locking, poka-yoke, and recheck planning
- Handling, assembly, and inspection interfaces in an automation line
Frequently asked questions
What should an automated screwdriving record contain?
Record the fields needed to explain the decision for each fastening point. Common candidates include product identity, fastener and tool identity, recipe revision, hole position, attempt number, result evidence, exception code, disposition, and release state. The final set is project-specific.
Does reaching target torque prove that a joint is accepted?
Not universally. Torque may be one relevant signal, but the required evidence depends on the joint, materials, fastener, tool, sensing method, and validated acceptance plan. Motion completion and numerical threshold attainment should not be treated as interchangeable with product acceptance.
When is floating compliance useful?
It can help accommodate a validated range of positional or angular mismatch between the driver and the hole. It cannot establish fastener identity, repair a wrong hole selection, or compensate for an invalid fixture datum without project evidence.
How should multiple screws be sequenced?
The recipe should define each position, its prerequisites, allowed order, and completion evidence. Preserve the result per position so an interruption, retry, or single-spindle fault cannot be hidden by one overall cycle-complete flag.
What should happen after an uncertain result?
Hold the individual position and assembly outside the accepted stream, preserve the first-attempt evidence, classify what is known, and route to a validated inspection, rework, or disposition step. Do not assume an automatic retry restores a known state.
Inputs for an automated screwdriving concept review
Prepare product models and revisions, joint stack details, fastener specifications, thread condition, hole map, allowed fastening order, fixture and clamp concept, feeder method, bit and driver information, required result evidence, inspection plan, traceability fields, changeover range, target cycle, maintenance constraints, and exception cases. An EVST concept review can then map state ownership, interfaces, sensing questions, and recovery logic without inventing untested performance.
How this article was prepared and maintained
The article combines bounded observation of available media with an engineering decomposition of fastener identity, datum control, bit engagement, result evidence, sequence, and recovery. Official standards pages support only the scope stated at the point of use. Corrections can be submitted through the company contact route, and the privacy policy explains site data handling.