ReChain force hydrant - Revision history

Apm: /* Operating the tension hydrant / Usage */

2025-05-13T13:30:42Z

Operating the tension hydrant / Usage

← Older revision		Revision as of 15:30, 13 May 2025
Line 16:		Line 16:
	== Operating the tension hydrant / Usage ==		== Operating the tension hydrant / Usage ==

	{{wikitodo\|Add sketches of possible designs here.}} <br>		{{wikitodo\|Add existing sketches of possible designs here.}} <br>

	★ (1) Press the tensioning mechanism against the tension hydrants positively locked nut THPLN thereby <br>		★ (1) Press the tensioning mechanism against the tension hydrants positively locked nut THPLN thereby <br>

Apm: added {{ReChain}} template

2024-11-19T11:22:22Z

added {{ReChain}} template

← Older revision		Revision as of 13:22, 19 November 2024
Line 1:		Line 1:
			{{ReChain}}
	{{site specific term}}		{{site specific term}}
	Up: [[ReChain tensioner]] <br>		Up: [[ReChain tensioner]] <br>

Apm: Added a detailed step-by-step operation guide

2024-11-11T18:53:17Z

Added a detailed step-by-step operation guide

← Older revision		Revision as of 20:53, 11 November 2024
Line 15:		Line 15:
	== Operating the tension hydrant / Usage ==		== Operating the tension hydrant / Usage ==

	{{wikitodo\|Add ~~details~~ here.}}		{{wikitodo\|Add sketches of possible designs here.}} <br>

			★ (1) Press the tensioning mechanism against the tension hydrants positively locked nut THPLN thereby <br>
			– (1a) first (by slight push) engaging the end effectors DOF to the still locked nut, and only then <br>
			– (1b) second (by further push) unlockinng the THPLN from its [[ReChain hull segment]] (to which it was locked to). <br>
			The purpose here is to never let anything go uncontrolledly free-spinning out of [[machine phase]]. <br>
			This finishes the transfer of the control of the THPLN from its lock-state to the enforcedly controlled effectors DOF <br>
			The THPLN may still be hard to turn as it is under heavy load. Thus the next step is NOT attempting to turn it. But … <br>
			★ (2) Screw the tensioning mechanisms nut TMN (other than the THPLN) onto the over-standing thread <br>
			★ (3) Use the tensioning mechanism to pull on the TMN thereby removing the load on the THPLN making it easily turnable. <br>
			– Yes this (intentionally) briefly increases the inner tension even if we desire is to reduce or remove inner tension. <br>
			★ (4) Turn the (now load-less) THPLN to either incerase, decrease, or fully remove the tension (that will later result). <br>
			★ (5) Do the steps in reverse (3)(2)(1b)(1a). Reload THPLN, TMN uncrew, lock THPLN, decouple THPLN. <br>
			In case of removal of all tension (and adding some slack) structural disassembly state can proceed in the now fully detensioned state.<br>
			For additional slack to not destroy [[machine phase]]: <br>
			How the additional slack distributes may be managed by weak springs (macroscale) or vdW forces (nanoscale). <br>
			[[Machine phase]] being preserved means that an open loop control robot <br>
			still can know where everything is without any senses at all. <br>
			Non need tor camera (macroscale) or touch probing (nanoscale). <br>
			And no need for the associated compute intelligence. <br>

	== Details for reliability and or nanoscale physics ==		== Details for reliability and or nanoscale physics ==
Line 24:		Line 42:
	Each tension hydrants shall feature a [[ReChain positive locking mechanism]] that <br>		Each tension hydrants shall feature a [[ReChain positive locking mechanism]] that <br>
	blocks back-slip by significant energy barrier rather than friction. <br>		blocks back-slip by significant energy barrier rather than friction. <br>

			== Factoring apart of sub-functionalities ==

	For more modularity the tensioning function shall be factored apart <br>		For more modularity the tensioning function shall be factored apart <br>
	form the length adjustment function for the [[ReChain core chain]]. <br>		form the length adjustment function for the [[ReChain core chain]]. <br>
	Generally [[ReChain]] systems shall factor the [[ReCahin tensioning device]]s out of the frame systems all together. <br>		Generally [[ReChain]] systems shall factor the [[ReCahin tensioning device]]s out of the frame systems all together. <br>
			There is no point in leaving huge mass and volume of a tensioning mechanism in the frame system that fulfills no further purpose.

	== Terminology: Why "Hydrant" ==		== Terminology: Why "Hydrant" ==

Apm: basic page transfer

2024-11-11T18:14:09Z

basic page transfer

New page

{{site specific term}}
Up: [[ReChain tensioner]] 
Alternative name: [[ReChain tension hydrant]]

A '''ForceHydrant''' is a spot in a [[ReChain]] system that provides 
access to the inner tension of one of the [[ReChain force circuit]]s of that system. 

A force hydrants can be used to:
* tension a force circuit after loose assembly
* detension a force circuit to perform recomposition and adjustments of the elements of that force circuit

'''Optional:'''
A force hydrant could be used as a spot to extend a force circuit there (temporarily or permanently), possibly introducing a branching point in the force circuit. For a force hydrant to allow for proper extension of the ReChain frame system, it needs to be designed such that further [[ReChain hull segment]]s can be added in a [[ReChain self centering]] way.

== Operating the tension hydrant / Usage ==

{{wikitodo|Add details here.}}

== Details for reliability and or nanoscale physics ==

To ensure no accidental loosening and slipping can happen. 
Even in the case of very large numbers of tension hydrants (mol). 
Each tension hydrants shall feature a [[ReChain positive locking mechanism]] that 
blocks back-slip by significant energy barrier rather than friction. 

For more modularity the tensioning function shall be factored apart 
form the length adjustment function for the [[ReChain core chain]]. 
Generally [[ReChain]] systems shall factor the [[ReCahin tensioning device]]s out of the frame systems all together. 

== Terminology: Why "Hydrant" ==

While there is no water flowing in [[force circuits]] there are some analogies to hydrants here.

'''Both systems feature pressure and tension:'''
* water is under (omni-directional) pressure
* a tensioned [[ReChain hull segment stack]] is under (unidirectional) pressure
* pipes are under circumferential tension
* [[ReChain core chains]] are under axial tension

'''Both systems provide public access to a bigger hidden network sprinkled all over the place''' 
There can be many access points sprinkled over a single (potentially branching) [[ReChain force circuit]]. 
Access points that all allow access to multiple of one single hidden part of the system which may be rather big. 
Not all force circuits are connected to just one single big [[ForceCircuit]] 
just like not all water systems of the world are connected. 

== Why not just one single big force circuit? ==

'''To prevent boundless detensioning.''' 
One reason not to connect everything together into just one single giant force circuit is 
that then the whole system would lose tension when the force circuit ruptures … 
– either controlledly via a [[Re Chain predetermined reversible breaking point]] 
– or uncontrolledly with permanent damage 
Similar to a minimal unit of [[ReChain tensegrity]] 
where just the absolute minimum of [[RepRec DOFs]] is constrained and 
if something ruptures at just one single spot then the whole system collapses. 

It's more practical to split up the force circuits into multiple smaller ones. 
This stops accidental detensioning from spreading boundlessly. A boundless [[ReChain RUDs]] would be bad. 

Some parts of frame systems could be tensioned redundantly by different force circuits. 
Albeit at the cost of about doubled mass. 
Redundant tension can remove gaps lacking pretension at the spots where forces circuits separate. 
{{wikitodo|Add a sketch.}}

'''Design challenges:''' 
Extending force circuits through nodes is challenging. 
Nodes that shall support that need to me vastly bigger and more complex than 
nodes where force circuits end and have their tension turnaround points 
Multi way connections would server as mechanical differentials equilibrium the tension to all sides. 
It may be desirable to have the capability in more advanced systems, but it's not needed for starting out. 
Modularity does not suffer from lack of this as simple nodes without tension feed-through can be small and compact. 

== Why going for bigger force circuits? ==

* Detensioned but monolithic sections may not be as stiff as tensioned sections. (?? To check.) 
* Quick undeploy maybe? Like quickly being able to folding stuff up would be very useful 
… Related: [[ReChain foldability]] as a further possible design goal. 
* {{todo|Are there more arguments that larger circuits are desirable?}} 

== Misc / analogies ==

Analogy: Splitting the force circuit is a bit like 
leaving out some dominoes in a standing domino row stopping the chain reaction short. 

Analogy: Working on mains. 
— German mnemonic in electric engineering: "allseitig und allpolig abtrennen (und erden)" 
— Translates to: "Disconnect and earth all sides and all poles" 
Locking the force circuit at all sides around a force hydrant 
before opening that force hydrant (close the "valves" on all sides) 

== Related ==

* [[ReChain positive locking mechanism]]
* [[ReChain tensioner]]
* [[ReChain temporary force circuit isolation spots]]

Page originally created 2020-06-13 (zim wiki)