Manufacturing, Testing & Quality
Robots routing cables through clips: why SILO keeps simulation in the real-robot loop
Summary: Even after a robot has grasped a cable and knows the fixture position, it may still press the cable against the edge of a clip. For engineers evaluating routing automation, this contact motion deserves separate study: reliable grasping and transport do not mean a flexible cable will enter a clip along the planned path.
SILO offers a division of tasks: conventional motion planning handles grasping and transport, while reinforcement learning handles local deformation near the clip. When deployed on a real arm, the simulator remains in the execution loop. It first calculates the joint positions that an action produces on the simulated arm, then has the physical robot follow them. This review explains what that intermediate computation addresses and how to decide whether it merits a trial at your workstation.
Actions pass through simulation before reaching the physical robot
SILO comes from a July 2026 preprint by Stone Tao and colleagues. During training, a chain of articulated rigid bodies approximates the cable to enable faster parallel training. The learning task focuses on states in which the cable has already been grasped and brought near the clip. During deployment, vision estimates the shape of the real cable, while the arm and clips remain in the digital model. The deployment loop does not continue simulating a complete physical cable. Section 4 and Algorithm 1 explain this distinction. Full paper
One execution cycle can be understood as follows:
- Read the physical robot’s current joint positions and synchronize the simulated arm with them.
- Estimate points on the cable from the real camera to form the observation the policy needs.
- Let the policy execute one action step in simulation.
- Use the resulting simulated joint positions as the physical robot’s next targets.
- Once the physical robot reaches those targets, synchronize again and continue to the next step.
This keeps the simulated controller used during training responsible for interpreting policy actions. It reduces response differences that arise when the same action is passed to a different physical robot controller. It also adds waiting and synchronization overhead. For an engineering evaluation, the useful questions are therefore whether the physical robot can reliably track the simulated targets and how long each observation and wait takes, rather than just how quickly the policy network runs inference.
The authors’ demonstration page describes gripper orientation changes based on the cable’s bending direction and lateral swaying motions to explain how the policy uses shape information. The demonstration videos are labeled as accelerated playback, so their playback speed cannot be used to estimate workstation cycle time. Authors’ demonstration
What comparisons the results support
Table 1 in the paper compares tasks involving one to three clips. Each cell retains both successes and trial counts, avoiding a single success rate that combines different task lengths.
| Method | 1 clip | 2 clips | 3 clips | Reported time for 3 clips |
|---|---|---|---|---|
| Hierarchical imitation learning, h-IL | 19/24 | 14/24 | 12/24 | Approximately 200 seconds, estimated from a video of prior work |
| SILO | 24/24 | 22/24 | 18/24 | 87.48 seconds |
These are the authors’ research results. The h-IL row comes from prior work; it is not a contemporaneous control rerun on the SILO setup. The authors also note differences in the two methods’ assumptions and capability emphasis. These times can help formulate trial questions, but they cannot directly predict savings from replacing a production-line approach. Table 1 and comparison discussion
Two further boundaries affect trial selection. In Table 2, the three-clip task achieved 14/24 with the HDMI cable, while each of the other three tested objects achieved 18/24. Trials with four material types cannot be interpreted as an ability to handle any wire harness. The 15/20 and 10/20 in Table 4 belong to an ablation of deployment methods using a single clip and fixed starting states. They cannot be combined with Table 1’s 18/24 into one overall success rate. Tables 2 and 4
Which part may be worth transferring
Readers can separate their difficulties into three levels before deciding whether this learning approach is needed.
| Current workstation problem | Conditions to check first | Suggested first step |
|---|---|---|
| The grasp point is inconsistent, and the cable often slips between the fingers | Gripper contact, cable diameter, controlled slip and grasp repeatability | Improve grasping or guidance first, and measure that step separately |
| The fixture is located, but cable bending varies substantially near the clip | Whether the camera can continuously observe the cable segment near the clip; whether entry angles cover actual variation | Compare a fixed motion with a locally reactive policy |
| Adjacent clips differ greatly in orientation, and failures require regrasping or rerouting | Task-level planning, slack allocation and recovery actions | Define the recovery procedure first, then decide where the local policy fits |
More training is not the only way to address the first row. CaRoBio presents another research direction on the mechanical side: biomimetic fingernail structures added to the gripper, combined with a single grasp and guiding motions, achieve three-dimensional routing. Its paper also reports failures involving soft-cable stacking and excessive changes in direction between adjacent grooves. These studies use different fixtures, cables, robots and tasks. They are useful for comparing mechanisms and assumptions, but their respective success rates cannot establish a general ranking. CaRoBio full paper, Sections III–IV
This table presents engineering judgments drawn from the papers, not selection rules validated by their authors. It helps avoid attributing every failure to the policy before grasping is stable. It also helps avoid repeatedly adjusting a fixed trajectory when local responses to deformation are actually needed.
Start with one clip and keep records for the complete task
If the workstation already has locatable clips and a clear view, start with a single-clip comparison. Keep the cable batch, fixture, distribution of starting poses and ending conditions the same. Save the existing script’s results before changing the local control method. Record cable diameter, jacket material and bending state; “the same type of cable” does not adequately describe the experimental conditions.
The following is a proposed comparison, with no measured results entered:
| Condition | Keep unchanged | Change only this | Difference to observe |
|---|---|---|---|
| A: Existing baseline | The same fixture, cable and starting states | Nothing | Whether failures occur mainly during grasping, clip entry or completion detection |
| B: Local policy | The same as A | The control method near the clip | Whether edge catching decreases and observation waits increase |
| C: Changed conditions | The same control method as B | A predefined range of clip-entry angles | Whether the successful range narrows and which states still fail |
Define complete success first: for example, all clips required by the task are completed, the cable remains in the specified position, and there is no visible damage. The conditions should follow the actual assembly requirements. “The robot reached the target point” or “the cable passed the first clip” does not replace full completion. Record first-pass completion, completion after human intervention and non-completion separately. Use the same start and end points when comparing time, and retain time spent on human recovery and failures.
The attached record sheet places the plan, state range, failure stage, total elapsed time and evidence location in one row. The example rows demonstrate only how to fill in a plan; measurement fields remain blank. They are neither original paper data nor an automatic scoring tool.
Synchronization and vision determine applicability
SILO assumes that clip geometry and poses are known in advance. The paper limits the current execution method to approximately static tasks: stepwise synchronization between simulation and hardware produces stop-and-go motion, and large entry angles can still cause cable jams. Camera occlusion, different clip geometries and highly dynamic tasks require separate evaluation. Section 6 and Appendices C and H
Collision avoidance in the digital model also depends on the accuracy of the model, calibration and target tracking. Engineers still need to validate safety and protection conditions on the physical equipment. Non-intersecting targets in simulation do not establish that every part of the actual motion is safe. This additional validation is needed when bringing the method into a workstation.
As of the source-check date, the accessible materials are the preprint and the authors’ demonstration. Public delivery of a complete implementation package and reproducibility assets has not been confirmed, nor has peer-reviewed acceptance. What can currently be taken from this work is an architectural option and a comparison method; it cannot yet be scheduled for deployment as ready-made production software.
If an implementation is later released, additional geometries are reported or independent reproductions become available, the most useful checks will be whether new fixtures still require remodeling, whether on-site vision can provide the same observations, and whether benefits remain when recovery is counted in the complete task.
Related reading: Two approaches to robotic wire-harness insertion. That article addresses connector insertion; this one addresses cable entry into clips. Their success definitions and trial objects differ.
English summary
SILO retains simulation during real-robot execution: the learned policy acts on a simulated robot, and the physical robot tracks the resulting joint targets. This review explains where that architecture may help cable routing, how its published comparisons differ, and how to plan a local trial with common starting conditions, full-task outcomes and recovery records. The reported results come from the authors; MTTJ has not reproduced the hardware experiments.
Sources checked: September 30, 2026. SILO is cited as arXiv:2607.04616v1 and CaRoBio as arXiv:2508.09558v1; both papers are available under CC BY 4.0. This review was researched and edited with AI assistance. MTTJ prepared the explanations, comparison tables and trial suggestions and has not performed a physical reproduction.
Related resources and manufacturing scope
Trial tools and field guides
Instructions for the cable clip-entry trial record sheet
Instructions for the cable clip-entry trial record sheet
The template silo-trial-template.csv contains only headers. Use one row for each complete attempt. A, B and C in silo-trial-planned-example.csv are proposed plans that have not been carried out; they are not original data from the SILO paper. Copy the example to your own file first, then fill in the plan for your workstation.
Fill in one record
First enter the control method, cable diameter and jacket, fixture, starting-state range, sole changed variable and definition of complete success. A retains the existing method. B changes only the local control method. C retains B’s method and changes the predefined range of clip-entry angles. When comparing B and C, do not also change the cable material.
Use time_start_and_end to specify identical timing boundaries. Determine stop_condition from the workstation’s equipment protection and trial requirements. The arm reaching its target does not substitute for the cable completing entry into all clips.
Fill these fields only after the trial
attempted_at_utc: The actual attempt time, including a time zone.outcome: Suggested values arefirst_pass_complete,completed_after_interventionornot_complete; use consistent definitions within the same trial batch.failure_stage: The actual failure location, such as grasping, approach, clip entry, retention or completion detection. Leave it blank if not observed.human_interventions: The actual count. Blank means unknown; 0 means that no intervention was observed and this was confirmed.elapsed_seconds: Total seconds from the predefined start to the end or stop. Retain failure and recovery time as well.damage_observed: Actual observations and inspection scope. Do not write “no damage” if no inspection was performed.evidence_ref: The file location of waveforms, video, photographs or trial logs.next_decision: The next step supported by this round’s results, not an automatic judgment by the sheet.
All the above results are blank in the example. After entering actual records, change record_type to measured_trial. Do not mix the denominators from the paper’s one-clip, three-clip or different-cable trials into these records.
The CSV uses UTF-8 encoding and comma separators and can be imported into spreadsheet software. It has no macros, formulas or automatic scoring tool. The article already explains the three comparisons; the download simply reduces recording and handoff work.
