ReChain fall in assembly: Difference between revisions
basic page |
m removed stub marker |
||
| Line 1: | Line 1: | ||
{{site specific term}} | {{site specific term}} | ||
The design principle idea here: <br> | The design principle idea here: <br> | ||
Latest revision as of 16:25, 17 May 2026
The design principle idea here:
Refrain from tight tolerances and press fits altogether.
All parts need to feature plenty of tolerance such that
nothing accidentally holds together due to friction (macroscale)
or commensurate interdigitation energy barriers (nanoscale).
This is meant to be applied in conjunction with: Post-tenstioning after pre-assembly
More econvretely here in ReChain context: Rebar chain tensioning
When assemblies are getting tensioned up in a later step
then some parts assume exact positions through self centering structures.
This especially holds for ReChain hull segments
For ReChain core Chains self centering may not be needed as
things only attach to the hull segments outside for positional reference.
At macroscale this can lead to problems like: ReChain fall out disassembly
ReChain assembly helper cliplocks can help.
Naming
A more general name here could be: PlentyClearanceAssembly
Macroscale
The term "falling" only matches macro-scale physics well,
where falling in is the thing happening when there is plenty of clearance and the end-effector lets go.
Nanoscale
At the nanoscale things get less trivial due to vdW forces.
One needs to design wit the with the resulting minimum energy state(s) in mind.
Which of them are error sates and which of these error states are not self correcting and problematic.
One likely gets intergigitating and sticking at commensurate surface corrugation notches.
One might want to design for superlubric non-commensurate interfaces
and for vdW suck-in to just have just one single stable
that is the desired assembly state (possible changed by tensioning tings up).