Tube Bending Datum Handoff Test
Tube bending datum handoff test begins before the forming motion. The workstation must prove the incoming tube pose, transfer datum custody from the infeed to the clamp and forming mechanism, associate the sample with the actual recipe and tool set, and preserve a conservative disposition whenever that chain becomes uncertain.
EVST calls this control model the Datum-Custody Handoff. It is for tube-forming engineers linking infeed, clamping, bending, unload, and sample measurement. It does not supply a universal bend recipe, springback correction, dimensional capability, or cycle for tubing and tooling that have not been tested as one application.
Tube bending datum handoff test begins at the infeed contract
Define what must be true before the robot enters: the bending machine is stopped at the specified position, hazardous movement is inhibited through the approved design, the forming-area access is sufficient, the safeguard state is correct, and the tube or part route is ready. Define the authority that proves each condition. An ordinary PLC output should not impersonate a safety-rated state.
Then define what must be true before the forming motion is allowed. The loader and its tool are outside the protected forming volume, the tube is seated against the declared datum, the correct recipe and tool set are active, the unload route is available, and the required safeguarding has returned to its operating state. The permission is the last link in a physical chain, not a convenience bit.
The contract should cover each bending machine mode used by the project. Setup, inch, manual, automatic, bending tool change, and maintenance may have different permitted actions and controls. Do not copy the automatic-cycle assumptions into a mode where an operator or maintenance technician has access.
Prove tube identity, rotational pose, and single-part state
The incoming definition includes tube geometry, thickness, surface, pickup location, presentation tolerance, orientation, and any family identifier. Challenge unknown rotational pose, a shifted tube datum, a missing tube, a double feed, and an infeed position at its declared limit. If single-tube or orientation detection is required, validate it with the actual diameter, wall, length, and surface range rather than a nominal sensor setting.
Gripper design should include the tube, cups or magnetic elements where applicable, adapters, sensors, valves, hoses, cable routing, center of gravity, inertia, and acceleration. Long or thin-wall tube can flex, sag, or rotate during motion. A static part-present signal may remain true even when one edge has shifted outside the placement envelope.
At the clamp and bending tool, define the seating features and evidence. Loader position alone may not show that the tube retained its rotational datum, reached the locating stop, or settled consistently in the clamping surfaces. Use the check specified by the real bending tool and quality plan. If seating cannot be proved, withdraw only through a validated recovery path and withhold the bend cycle.
| Permission link | Physical meaning | Fault response |
|---|---|---|
| Bending machine safe for entry | Required bending machine and safeguard state is established | Robot remains outside the forming area |
| Robot allowed inside | Access path and tool state are valid | Entry command is inhibited |
| Tube or part confirmed | Material is in the expected state and location | Route to hold or controlled recovery |
| Robot clear | Arm, tool, cables, and carried material left the protected volume | Forming remains inhibited |
| Forming permission | All links and mode conditions agree | Record conflict; do not substitute a delay |
Keep loader-clear independent from elapsed time
A clear output should be derived from validated robot position or the approved safety/control architecture, including the real tool envelope. The arm flange may be outside while a long gripper, hose, or held tube remains inside. Model and test the complete moving assembly at the least favorable path and changeover.
Challenge a stuck loader-clear signal, a late update, conflicting position information, communication loss, and power interruption. The bending machine should not infer clearance because the expected travel time passed. Recovery after a controller restart requires fresh evidence from both systems before the chain can close.
Where safety-related signals cross controllers, document their architecture, performance requirement, diagnostics, and validation responsibility. This article does not prescribe a safety category or performance level; that selection belongs to the application risk assessment and applicable requirements.
Tie every formed sample to the actual datum and recipe
A formed-tube handoff can fail even when the loader completes its programmed move. The tube may retain spring force, remain captured by a clamp or mandrel, rotate during release, or shift before measurement. Define what proves tool release, safe unload, sample identity, and a valid route to the measurement step before the next tube is introduced.
If the mandrel, clamp, pressure die, support, or transfer tool can retain the tube, include that condition in the detection and recovery plan. Position sensing, clamp-state confirmation, a tool sensor, or controlled observation may be appropriate. Test the selected evidence against credible partial-release and trapped-tube states.
Preserve sample identity through forming, unload, and dimensional measurement. A failed placement, occupied destination, or lost quality result should send the part to a named hold state. Do not allow the next tube to overwrite the record of an uncertain previous cycle.
Exercise jams and shifted material deliberately
The minimum forced-fault set includes an unproven safe state, unknown tube rotation, a shifted datum, a tube not released from the tool set, and missing loader-clear evidence. Add lost grip, failed bending tool sensor, unavailable downstream location, bending machine alarm, mode mismatch, safeguard fault, and communication loss as the actual design requires.
For every fault, record whether the tube is on the infeed, loader, clamp, forming tool, measurement fixture, or exception route; whether the bending machine can move; where the robot is; which hazardous energy remains; and what intervention is allowed. Automatic retry must have a limit and must not repeat an action that can crush material, damage tooling, or create an unexpected bend cycle condition.
Recovery instructions should not tell an operator only to “clear the alarm.” They identify the physical inspection, safe access mode, reset location, material disposition, and fresh-state handshake required before automatic operation returns. After a jam, the next cycle starts from proven bending tool and material state.
Integrate tube-forming hazards and access from the start
Primary hazards include crushing at the clamps and forming tools, long-stock sweep, stored force, sharp tube ends, dropped material, pinch points, and entry during jams or tool changes. The risk assessment covers production, loading, setup, teaching, tooling service, tube replenishment, inspection, unload, cleaning, recovery, and maintenance.
OSHA machine-guarding guidance addresses point-of-operation, rotating-part, chip, spark, and safeguarding considerations relevant to the connected equipment. ISO 10218-2:2025 and OSHA’s robot guidance cover the robot application boundary. The final design still needs the bending machine builder’s requirements, the actual safeguarding system, local law, and site validation.
Test stopping, reset, visibility, trapped-person prevention where applicable, unexpected restart protection, and hazardous-energy isolation. The robot should never be used as the only measure preventing a bend cycle while people have access to the hazard.
Balance the workstation from permission-state timing
Break the cycle into tube presentation, safe-state confirmation, robot entry, placement, release, withdrawal, loader-clear proof, forming motion, formed-sample unload, inspection, and downstream handoff. Record bending machine motion and robot work separately. Include waits created by feeder, bending tool, safeguard, inspection, and downstream availability.
A faster arm cannot compensate for slow or uncertain permission transitions. Conversely, shortening a verified clear-state dwell without understanding why it exists may reduce diagnostic or safety margin. Optimize only after the transition timestamps and limiting segment are visible.
Use representative material, bending machine modes, changeovers, replenishment, and recoveries. Report a bounded result with the measurement method. The video is a process reference, not evidence of a universal bend cycle rate or production output.
Accept the Datum-Custody Handoff with evidence
The campaign should cover representative tubes, rotational-pose extremes, datum-detection faults, clamp seating, formed-sample unload, loader-clear disagreement, safeguard functions, communication interruption, mode changes, jams, recovery, and restart. Save the loader and forming-state sequence, clamp and tool-set revision, tube sample, inspection result, and disposition.
Send EVST:
- tube drawing, bend schedule, material, and presentation information
- bending machine, clamp, tool set, recipe, and mode details
- safety and control-interface documentation
- gripper, detection, and downstream concept
- bend cycle timing, target cycle, and changeover plan
- jam, sample-measurement, inspection, and recovery requirements
An application review can connect those facts to robot reach, tooling, handshake logic, safeguards, and test cases. Missing bending machine or safety information remains a blocker; it is not filled with a guessed signal or copied diagram.
Frequently asked questions
Can bending machine permission be based on a fixed delay after robot exit?
No. Time alone does not prove that the arm, tool, cable package, or carried material cleared the protected volume. Use the approved position and control evidence, then test stale, missing, and contradictory signals. A delay may support stabilization only after the physical condition is known.
Is part-present sensing enough for tube seating?
Not necessarily. The sensor must detect the failures that matter, including missing, doubled, shifted, or bridged material as applicable. Validate it on the real tube range and bending tool. If the quality or tooling consequence requires more evidence, add the appropriate check.
What happens when a part remains in the bending tool?
The bending machine stays inhibited. The cell enters a defined recovery state that controls hazardous energy, operator access, part disposition, and a fresh proof of bending tool clearance. Repeating the bend cycle or blindly retrying the robot is not an acceptable default.
Does automation remove the need for a bending machine safety review?
No. It changes exposure and control architecture, but the bending machine, bending tool, safeguards, modes, maintenance, and abnormal operations still require application-specific assessment and validation. Robot integration and bending machine safety must be designed together.
Conclusion
Tube bending datum handoff is production-ready only when each entry and forming permission can be traced to a real state. Give EVST the tube, bending machine, bending tool, interface, safeguarding, tube flow, and recovery data. The Datum-Custody Handoff should make a missing state stop the workstation predictably—before speed optimization begins.
Related EVST reading
- machine-tending cell boundaries
- machine-tending process fundamentals
- robot grinding contact-window planning
References
- OSHA Machine Guarding — General Requirements — used for point-of-operation, rotating-part, chip, spark, and safeguarding considerations.
- NIST Performance Assessment Framework for Robotic Systems — used for performance requirements, metrics, test methods, and repeatable verification.
- OSHA Technical Manual: Industrial Robot Systems and System Safety — used for robot application components, hazards, risk assessment, risk reduction, and safety-system evaluation.
- NIST Assembly Performance Metrics and Test Methods — used for assembly performance metrics and test-method development.