<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.3" xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Robot. AI</journal-id>
<journal-title>Frontiers in Robotics and AI</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Robot. AI</abbrev-journal-title>
<issn pub-type="epub">2296-9144</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">873446</article-id>
<article-id pub-id-type="doi">10.3389/frobt.2022.873446</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Robotics and AI</subject>
<subj-group>
<subject>Original Research</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>FAS&#x2014;A Fully Actuated Segment for Tendon-Driven Continuum Robots</article-title>
<alt-title alt-title-type="left-running-head">Grassmann et al.</alt-title>
<alt-title alt-title-type="right-running-head">FAS for TDCRs</alt-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Grassmann</surname>
<given-names>Reinhard M.</given-names>
</name>
<xref ref-type="corresp" rid="c001">&#x2a;</xref>
<uri xlink:href="https://loop.frontiersin.org/people/1673966/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Rao</surname>
<given-names>Priyanka</given-names>
</name>
<uri xlink:href="https://loop.frontiersin.org/people/1144288/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Peyron</surname>
<given-names>Quentin</given-names>
</name>
<uri xlink:href="https://loop.frontiersin.org/people/1167552/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Burgner-Kahrs</surname>
<given-names>Jessica</given-names>
</name>
<uri xlink:href="https://loop.frontiersin.org/people/1099096/overview"/>
</contrib>
</contrib-group>
<aff id="aff1">
<institution>Continuum Robotics Laboratory</institution>, <institution>Department of Mathematical and Computational Sciences</institution>, <institution>University of Toronto Mississauga</institution>, <addr-line>Mississauga</addr-line>, <addr-line>ON</addr-line>, <country>Canada</country>
</aff>
<author-notes>
<fn fn-type="edited-by">
<p>
<bold>Edited by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/1093108/overview">Ivan Virgala</ext-link>, Technical University of Ko&#x161;ice, Slovakia</p>
</fn>
<fn fn-type="edited-by">
<p>
<bold>Reviewed by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/1130173/overview">Farrokh Janabi-Sharifi</ext-link>, Ryerson University, Canada</p>
<p>
<ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/366143/overview">Anand Kumar Mishra</ext-link>, Cornell University, United States</p>
</fn>
<corresp id="c001">&#x2a;Correspondence: Reinhard M. Grassmann, <email>reinhard.grassmann@utoronto.ca</email>
</corresp>
<fn fn-type="other">
<p>This article was submitted to Soft Robotics, a section of the journal Frontiers in Robotics and AI</p>
</fn>
</author-notes>
<pub-date pub-type="epub">
<day>26</day>
<month>04</month>
<year>2022</year>
</pub-date>
<pub-date pub-type="collection">
<year>2022</year>
</pub-date>
<volume>9</volume>
<elocation-id>873446</elocation-id>
<history>
<date date-type="received">
<day>10</day>
<month>02</month>
<year>2022</year>
</date>
<date date-type="accepted">
<day>21</day>
<month>03</month>
<year>2022</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#xa9; 2022 Grassmann, Rao, Peyron and Burgner-Kahrs.</copyright-statement>
<copyright-year>2022</copyright-year>
<copyright-holder>Grassmann, Rao, Peyron and Burgner-Kahrs</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/">
<p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p>
</license>
</permissions>
<abstract>
<p>We propose a segment design that combines two distinct characteristics of tendon-driven continuum robots, i.e. variable length and non-straight tendon routing, into a single segment by enabling rotation of its backbone. As a result, this segment can vary its helical tendon routing and has four degrees-of-freedom, while maintaining a small-scale design with an overall outer diameter of 7&#xa0;mm thanks to an extrinsic actuation principle. In simulation and on prototypes, we observe improved motion capabilities, as evidenced by position redundancy and follow-the-leader deployment along spatially tortuous paths. To demonstrate the latter on a physical prototype, a simple, yet effective area-based error measure for follow-the-leader deployment is proposed to evaluate the performance. Furthermore, we derive a static model which is used to underpin the observed motion capabilities. In summary, our segment design extends previous designs with minimal hardware overhead, while either archiving similar accuracy in position errors and planar follow-the-leader deployment, or exhibiting superior motion capabilities due to position redundancy and spatial follow-the-leader deployment.</p>
</abstract>
<kwd-group>
<kwd>continuum robot manipulator</kwd>
<kwd>soft manipulator</kwd>
<kwd>design</kwd>
<kwd>degrees of freedom</kwd>
<kwd>helical tendon routing</kwd>
<kwd>tendon actuation</kwd>
<kwd>follow-the-leader deployment</kwd>
<kwd>position redundancy</kwd>
</kwd-group>
<contract-num rid="cn001">RGPIN-2019-04846</contract-num>
<contract-sponsor id="cn001">Natural Sciences and Engineering Research Council of Canada<named-content content-type="fundref-id">10.13039/501100000038</named-content>
</contract-sponsor>
</article-meta>
</front>
<body>
<sec id="s1">
<title>1 Introduction</title>
<p>In medical and <italic>in situ</italic> inspection applications, robots are required to operate in a constrained environment and follow tortuous path. To achieve these high motion capabilities at the end effector but also of the whole robot body is desirable, in order to enable obstacle avoidance, follow-the-leader (FTL) deployment, where the robot structure moves along a predefined path, and to be able to perform a task, i.e. positioning and orienting tools at the robot tip. A promising category of robots, which are scalable to a small size, dexterous, and flexible enough to provide these capabilities comes to the fore; continuum robots. In <xref ref-type="bibr" rid="B8">Burgner-Kahrs et al. (2015)</xref>, a continuum robot is defined as an actuatable structure, which forms curves with continuous tangent vector. Amongst the existing classes of continuum robots, tendon-driven continuum robots (TDCR), depicted in <xref ref-type="fig" rid="F1">Figure 1</xref>, are one of the most frequently considered.</p>
<fig id="F1" position="float">
<label>FIGURE 1</label>
<caption>
<p>Envisioned tendon-driven continuum robot (on the right) as combination of extensible segment TDCR [top left, from (<xref ref-type="bibr" rid="B3">Amanov et al., 2019</xref>)] and TDCR with helical routing [bottom left, from (<xref ref-type="bibr" rid="B37">Starke et al., 2017</xref>)].</p>
</caption>
<graphic xlink:href="frobt-09-873446-g001.tif"/>
</fig>
<p>The capability to form a curve with continuous tangent vector is beneficial for FTL deployment. However, the motion capability of current designs of TDCR is limited, especially w.r.t. FTL behaviour. They are highly dependent on the TDCR design regardless of the modelling, sensing, and control of the FTL deployment. Therefore, a closer look at TDCR designs that improve motion capabilities is worthwhile.</p>
<sec id="s1-1">
<title>1.1 Related Work</title>
<p>A TDCR is usually composed of a flexible backbone along which tendons are guided using spacer disks, these last ones being fixed to the backbone. It is actuated by changing the tendons&#x2019; length and applying tendon tensions, which cause a reversible deformation of the backbone. This actuation strategy is referred to as extrinsic, since the actuators used to deform the backbone are not embedded within the manipulator&#x2019;s body. Extrinsic actuation allows for small diameter to length ratios of the robot and reduces the reflective inertia of the manipulator. TDCR are usually designed with several actuatable segments, by routing additional tendons along the backbone. These tendons are attached at specific intermediate disks fixed on the backbone, delimiting the so-called segments, and routed to the robot base where the actuators are located. The design of most of them uses two or three segments. As a result, they are good candidates for a small-scale robot with high motion capabilities, maneuverability, and interesting FTL deployment properties due to their high number of actuated dof. However, a high number of segments comes at the expense of complex tendon routing, high friction between the tendons, and a bulky actuation unit. Improving the robot motion capabilities can be performed by enhancing the capability of FTL deployment and the workspace.</p>
<p>Regarding FTL deployment, TDCRs have been considered to follow paths composed of sections with planar constant curvature (<xref ref-type="bibr" rid="B33">Palmer et al., 2014</xref>; <xref ref-type="bibr" rid="B23">Kang et al., 2016</xref>; <xref ref-type="bibr" rid="B30">Neumann and Burgner-Kahrs, 2016</xref>; <xref ref-type="bibr" rid="B3">Amanov et al., 2019</xref>; <xref ref-type="bibr" rid="B13">Gao et al., 2019</xref>). A path can be followed by deploying the TDCR along the desired path and modifying the tendon tensions, which subsequently change the curvature of the segments. To improve accuracy during deployment, a TDCR with extensible segments, which is depicted in top left image in <xref ref-type="fig" rid="F1">Figure 1</xref>, is proposed by <xref ref-type="bibr" rid="B31">Nguyen and Burgner-Kahrs (2015)</xref> and further developed by <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref>.</p>
<p>However, due to the fact that existing TDCRs rely on straight tendon routing, only paths composed of sections with planar and constant curvature can be followed. Therefore, to facilitate general path-following, a TDCR design would require more dofs in task space (<xref ref-type="bibr" rid="B3">Amanov et al., 2019</xref>). As a consequence, following spatial tortuous paths requires at least two segments and for a more complex spatial path significantly more segments are required. Aside from the challenges caused by using high number of segments, e.g. complex tendon routing and increased friction, FTL deployment accuracy of standard TDCR decreases at the transition between two sections of the path as shown by <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref>.</p>
<p>As an interesting side-effect, the use of extensible segments enhances the workspace and position reduncancy of a TDCR. Existing works in the literature mainly focused on investigating the workspace improvement, i.e. which end-effector positions can be reached by the robot end-effector using the actuated dofs (<xref ref-type="bibr" rid="B6">Blessing and Walker, 2004</xref>; <xref ref-type="bibr" rid="B39">Walker et al., 2006</xref>; <xref ref-type="bibr" rid="B3">Amanov et al., 2019</xref>). A workspace volume increase of 22.5% compared to a TDCR with constant segment length was obtained by <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref>. The positive impact of the segments extensibility on the workspace is also clearly demonstrated by <xref ref-type="bibr" rid="B26">Li et al. (2017)</xref>. Position redundancy, i.e. the capability of changing the robot configuration while staying at a desired end-effector position, was less considered but is also an important performance metric. It indicates the range of achievable robot tip orientations for the considered tip position, which is critical for manipulation (<xref ref-type="bibr" rid="B36">Simaan et al., 2009</xref>) and inspection (<xref ref-type="bibr" rid="B20">Goldman et al., 2013</xref>) tasks. The redundancy can also be leveraged for respecting anatomical constraints with the robot body (<xref ref-type="bibr" rid="B13">Gao et al., 2019</xref>)), or for minimizing the potential energy stored in the backbone (<xref ref-type="bibr" rid="B29">Moll and Kavraki, 2004</xref>). It was demonstrated by <xref ref-type="bibr" rid="B40">Wu et al. (2017)</xref> that the position redundancy is strongly impacted by the number of actuated dofs. Considering extensible segments improves also the position redundancy distribution at the workspace center <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref>.</p>
<p>The workspace and steerability of TDCR can also be enhanced by using non-straight tendon routing. In particular, helical tendon routing, which is depicted in the bottom left image in <xref ref-type="fig" rid="F1">Figure 1</xref>, has been used to obtain TDCR configurations, which are not possible with straight tendon routing. As a result, a larger variety of tip orientations can be achieved in the workspace (<xref ref-type="bibr" rid="B16">Gerboni et al., 2015</xref>) or different position can be reached, while keeping the same orientation (<xref ref-type="bibr" rid="B35">Rucker and Webster, 2011</xref>). Further, using an additional helical tendon to existing straight tendon routing can lead to a fourfold increase of workspace volume and modification of workspace shape as demonstrated by <xref ref-type="bibr" rid="B37">Starke et al. (2017)</xref>. However, the prototypes presented in <xref ref-type="bibr" rid="B16">Gerboni et al. (2015)</xref> and <xref ref-type="bibr" rid="B37">Starke et al. (2017)</xref> combine fixed helical and straight tendon routing and may lead to complex tendon routing, especially if several segments are stacked. A similar approach is the configurable tendon routing in (<xref ref-type="bibr" rid="B4">Barreiros et al., 2019</xref>), where non-straight tendon routing can be realized. However, the chosen fixed tendon routing is a design parameter and cannot be controlled during the operation of the TDCR.</p>
<p>To conclude, the current design paradigm, i.e. stacking segments with fixed tendon routing, has reached its limit for improving motion capabilities while achieving small scale manipulators. Although different non-straight tendon routings are considered to achieve larger workspaces and, therefore, higher motion capabilities, current tendon routings are fixed and only used as design parameters. We propose to exploit the tendon routing as an additional dof in order to induce torsion in the backbone, thus exploiting all significant deformation modes of a TDCR segment. It is our hypothesis that taking advantage of the fourth dof has a significant impact on the motion capabilities and, therefore, on the FTL deployment as well as position and orientation capabilities of a TDCR.</p>
</sec>
<sec id="s1-2">
<title>1.2 Contribution</title>
<p>In this paper, we propose a design of TDCR segment which leverages advantages of both extensibility and variable helical routing, cf. <xref ref-type="fig" rid="F1">Figure 1</xref>. We present our progress in the development of a TDCR with four&#x2009;dof per segment. We introduce the design and evaluate its merits by several assessments in simulation and with real prototypes. In particular, the contributions of this paper include:<list list-type="simple">
<list-item>
<p>&#x2022; A mechanism able to continuously change the tendon routing from straight to helical routing and capable of FTL deployment along a spatial tortuous path using a simple deployment strategy.</p>
</list-item>
<list-item>
<p>&#x2022; An analysis of position redundancy and FTL behaviour using a static model considering four&#x2009;dof.</p>
</list-item>
<list-item>
<p>&#x2022; As minor contributions, an area-based error measure for FTL deployment and a different view on spacer disks to exploit the provided passive dof.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s1-3">
<title>1.3 Organization</title>
<p>The paper is structured as follows. We first introduce the conceptual design of TDCR in <xref ref-type="sec" rid="s2">Section 2</xref>. We then propose a static model of the robot in <xref ref-type="sec" rid="s3">Section 3</xref>. The FTL deployment capabilities are studied in <xref ref-type="sec" rid="s4">Section 4</xref>, where the deployment strategy and the area-based error are described. The position and orientation capabilities are studied in <xref ref-type="sec" rid="s5">Section 5</xref>. The results are discussed in <xref ref-type="sec" rid="s6">Section 6</xref> before concluding.</p>
</sec>
</sec>
<sec id="s2">
<title>2 Conceptual Design</title>
<p>In this section, we discuss the concept of the proposed mechanical design. First, we consider spacer disks with passive dof. Second, we propose a segment design for TDCR which is capable of generating non-straight tendon routing. Afterwards, both physical prototypes are introduced.</p>
<sec id="s2-1">
<title>2.1 FSD&#x2014;Floating Spacer Disk</title>
<p>We introduce a categorization of spacer disks into four types. The categories are based on the most general spacer disk, referred to as FSD (floating spacer disk), which can translate along and rotate about the TDCR&#x2019;s backbone.<list list-type="simple">
<list-item>
<p>Type-0: A spacer disk which can neither rotate nor translate along the backbone.</p>
</list-item>
<list-item>
<p>Type-I: A translational FSD which can only translate along the backbone but not rotate.</p>
</list-item>
<list-item>
<p>Type-II: A rotational FSD which can rotate while translation is prohibited.</p>
</list-item>
<list-item>
<p>Type-III: The last type of spacer disk can translate and rotate freely.</p>
</list-item>
</list>
</p>
<p>The first type of spacer disk, i.e., type-0, is fixed to the backbone and is a widely used spacer disk for TDCRs (<xref ref-type="bibr" rid="B35">Rucker and Webster, 2011</xref>; <xref ref-type="bibr" rid="B28">Mishra et al., 2017</xref>; <xref ref-type="bibr" rid="B37">Starke et al., 2017</xref>; <xref ref-type="bibr" rid="B25">Li et al., 2020</xref>). End disks and disks attached to the base fall into the category of type-0 FSD. Type I FSD can be found in the literature (<xref ref-type="bibr" rid="B6">Blessing and Walker, 2004</xref>; <xref ref-type="bibr" rid="B23">Kang et al., 2016</xref>; <xref ref-type="bibr" rid="B1">Amanov et al., 2017</xref>; <xref ref-type="bibr" rid="B24">Lastinger et al., 2019</xref>; <xref ref-type="bibr" rid="B38">Visentin et al., 2019</xref>), where the rotational passive dof is constrained due to its design. The position of each disk can be depended on the repulsion forces between them in order to distribute the disks along the backbone. Adding an additional rotational passive dof leads to an FSD with two&#x2009;dof, i.e., type-III FSD. An example is given by <xref ref-type="bibr" rid="B31">Nguyen and Burgner-Kahrs (2015)</xref>. However, the design by <xref ref-type="bibr" rid="B31">Nguyen and Burgner-Kahrs (2015)</xref> does not utilize the rotational passive dof. Another FSD with rotational passive dof is given by type-II FSD. Since type-II FSD and type-III FSD are coupled with tendons, the resulting orientation of each of them is influenced by the adjacent FSD of any type. To conclude, type-II FSD have not been realized thus far and type-III FSD have not been fully exploited.</p>
</sec>
<sec id="s2-2">
<title>2.2 FAS&#x2014;Fully Actuated Segment</title>
<p>Here, we present the general idea of our proposition of TDCR segment with four actuated dof, i.e. bending in two directions, extension and twist, obtained using extrinsic actuation. A schematic design is depicted in <xref ref-type="fig" rid="F2">Figure 2I</xref>. The proposed segment design is partially based on the extensible segment TDCR design described in our previous works by <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref>. It uses flexible, slender and non compressible tubes as the backbone, which shear deformations are typically negligible. Our segment design, called FAS (Fully Actuated Segment), allows then to actuate all significant deformation modes of the backbone. Furthermore, connections to concentric tube continuum robots (CTCR) are made. We kindly refer to <xref ref-type="bibr" rid="B17">Gilbert et al. (2016)</xref> and <xref ref-type="bibr" rid="B27">Mahoney et al. (2016)</xref> as well as to <xref ref-type="bibr" rid="B22">Grassmann et al. (2020)</xref> for more details on CTCR. For visual aid, <xref ref-type="fig" rid="F2">Figure 2A</xref> to <xref ref-type="fig" rid="F2">Figure 2H</xref> illustrate the effect of each dof and their combinations on a continuous slender structure.</p>
<fig id="F2" position="float">
<label>FIGURE 2</label>
<caption>
<p>Degree of freedom of a single segment of a continuum robot represented as a blue continuum structure. <bold>(A)</bold> <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>
</sub> is a one&#x2009;dof bending in a plane. <bold>(B)</bold> <italic>&#x3ba;</italic>
<sub>
<italic>y</italic>
</sub> is a one&#x2009;dof bending in another plane being perpendicular to the first bending plane. <bold>(C)</bold> Using <italic>&#x3b2;</italic>, the change of length as extension or contraction of a segment is one&#x2009;dof. <bold>(D)</bold> one&#x2009;dof twist along the centerline of the segment induces by <italic>&#x3b1;</italic>. <bold>(E)</bold> Bending in both bending planes results in two&#x2009;dof. Note that bending in one plane, e.g. <inline-formula id="inf1">
<mml:math id="m1">
<mml:mi>&#x3ba;</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:msqrt>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:msqrt>
</mml:math>
</inline-formula> with an additional rotation of the banding plane, e.g. <italic>&#x3d5;</italic> &#x3d; arctan2 (<italic>&#x3ba;</italic>
<sub>
<italic>y</italic>
</sub>, <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>
</sub>), yields the same two&#x2009;dof result, where <italic>&#x3ba;</italic> and <italic>&#x3d5;</italic> are directly actuated. <bold>(F)</bold> Variable segment length with the ability to independently twist results in two&#x2009;dof. <bold>(G)</bold> Variable segment length additional to both bending are in total three&#x2009;dof. <bold>(H)</bold> The four dof envisioned design can actuate all degree of freedom which include both bending, variable segment length, and twisting. <bold>(I)</bold> Schematics of a TDCR prototype composed of one FAS. The green and red colors indicate the alternating poles of the magnets used for the type-III FSD. This TDCR prototype is capable of all illustrated motions.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g002.tif"/>
</fig>
<sec id="s2-2-1">
<title>2.2.1 Bending&#x2014;two&#x2009;dof</title>
<p>At least three tendons are equally distributed around the elastic backbone and attached to the end disk. All tendons are routed through each FSD. As the segment backbone cannot be compressed, applying tendon tension, denoted <italic>&#x3c4;</italic>
<sub>
<italic>i</italic>
</sub> for <italic>i</italic>th tendon, results in bending of the segment only. This bending provides two&#x2009;dof, i.e. <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>
</sub> and <italic>&#x3ba;</italic>
<sub>
<italic>y</italic>
</sub>, which is the bending around the <italic>x</italic>-axis and <italic>y</italic>-axis, respectively. The bending and their combination are illustrated in <xref ref-type="fig" rid="F2">Figure 2A</xref>, <xref ref-type="fig" rid="F2">Figure 2B</xref>, and <xref ref-type="fig" rid="F2">Figure 2E</xref>.</p>
<p>Note that an in-compressible segment can also be actuated by specifying tendon displacements. However, tendon displacements are coupled. For instance, a planar one&#x2009;dof bending requires two tendons and, in this case, therefore, two actuators. In turn, these two&#x2009;dof in actuation space lead to one&#x2009;dof in arc space and one&#x2009;dof manifold in the task space, i.e. the planar curve with <italic>y</italic> and <italic>z</italic> coordinates can be parameterized with one parameter, e.g. <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>
</sub>. Further, spanning a perpendicular bending plane in the <italic>zx</italic>-plane, leads to another one&#x2009;dof manifold in the task space, which can be parametrized with <italic>&#x3ba;</italic>
<sub>
<italic>y</italic>
</sub>. Combining both bending planes, where four actuators are used (four&#x2009;dof in actuation space), leads to a two&#x2009;dof manifold in the task space creating a curved plane in the spatial space. Note that each point on the two&#x2009;dof manifold has a fixed orientation and, therefore, the orientation is uniquely determined by the arc parameters <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>
</sub> and <italic>&#x3ba;</italic>
<sub>
<italic>y</italic>
</sub>. For the sake of completeness, an alternative derivation can be given by considering one bending and one rotation of this bending plane, see caption of <xref ref-type="fig" rid="F2">Figure 2E</xref>.</p>
</sec>
<sec id="s2-2-2">
<title>2.2.2 Extension&#x2014;one&#x2009;dof</title>
<p>The backbone can be attached to a carriage at the proximal end of the backbone. The carriage can be translated in the actuation unit similar to a CTCR, cf. <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref> and <xref ref-type="bibr" rid="B21">Grassmann and Burgner-Kahrs (2019)</xref>. Therefore, the translation <italic>&#x3b2;</italic> can be extrinsically actuated. In order to enable rearrangement of the FSD, a repulsion force between them is desired. For instance, permanent magnets (<xref ref-type="bibr" rid="B31">Nguyen and Burgner-Kahrs, 2015</xref>) or springs (<xref ref-type="bibr" rid="B6">Blessing and Walker, 2004</xref>) can be used. Note that springs might prohibit rotation around the backbone due to high torsional stiffness. Here, we consider FSD equipped with permanent magnets with alternating pole orientation. They automatically distribute along the segment due to magnetic repulsion forces as <xref ref-type="bibr" rid="B31">Nguyen and Burgner-Kahrs (2015)</xref> previously demonstrated. The range of extension and contraction of each segment depends on the tube length and the thickness of the FSD (<xref ref-type="bibr" rid="B30">Neumann and Burgner-Kahrs, 2016</xref>). <xref ref-type="fig" rid="F2">Figure 2C</xref> illustrates this one dof.</p>
</sec>
<sec id="s2-2-3">
<title>2.2.3 Twisting by Rotation&#x2014;one dof</title>
<p>Rotating the backbone results in rotating the end disk, which is a function of <italic>&#x3b1;</italic> and the other states of the TDCR, since the end disk is rigidly attached to the backbone. In <xref ref-type="fig" rid="F2">Figures 2A,D</xref> continuously deformed structure illustrates the one&#x2009;dof twisting by rotation. As the end disk is rotated and each intermediate type-III FSD has a passive rotational dof, each intermediate type-III FSD will be rotated due to their interaction with the tendons. Consequently, the tendons are not routed straight any more. Applying tendon tension <italic>&#x3c4;</italic>
<sub>
<italic>i</italic>
</sub> along the non-straight tendon routing then leads to twisting as shown by <xref ref-type="bibr" rid="B35">Rucker and Webster (2011)</xref>. To conclude, the design has the ability to generate variable non-straight tendon paths by varying <italic>&#x3b1;</italic>.</p>
<p>To the best of our knowledge, the rotation <italic>&#x3b1;</italic> leading to variation of relative rotation of the intermediate spacer disks has never been proposed before. The designs by <xref ref-type="bibr" rid="B28">Mishra et al. (2017)</xref>; <xref ref-type="bibr" rid="B38">Visentin et al. (2019)</xref>; <xref ref-type="bibr" rid="B25">Li et al. (2020)</xref> also introduce a rotation. However, the additional rotation can be seen as a rotation of the base or as rotation of the bending plane, see caption of <xref ref-type="fig" rid="F2">Figure 2E</xref>. More importantly, these designs cannot generate non-straight tendon routing.</p>
</sec>
</sec>
<sec id="s2-3">
<title>2.3 Prototypes</title>
<p>To highlight the capabilities of the proposed design, we study its merit through two different prototypes throughout this paper. The first prototype combines type-III FSDs with 4dof to obtain a FAS prototype. The second prototype with fixed segment length has several type-II FSDs. Both prototypes are depicted in <xref ref-type="fig" rid="F3">Figure 3</xref>.</p>
<fig id="F3" position="float">
<label>FIGURE 3</label>
<caption>
<p>TDCR prototypes. Both prototypes are loaded with different weights on one tendon for different rotation <italic>&#x3b1;</italic>. <bold>(A)</bold> First prototype is composed of type-III FSD with fixed overall length of 60&#xa0;mm. <bold>(B)</bold> Second prototype is composed of type-II FSD.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g003.tif"/>
</fig>
<sec id="s2-3-1">
<title>2.3.1 FAS Prototype With Type-III FSD</title>
<p>As illustrated in <xref ref-type="fig" rid="F2">Figure 2</xref> and shown in <xref ref-type="fig" rid="F3">Figure 3</xref>, this prototype is composed of three tendons, one backbone, and twelve FSDs. The tendons are microfilament braided threads made of Spectra Fiber<sup>&#xae;</sup> (diameter of 0.28&#xa0;mm) and fixed to the end disk. A superelastic Nitinol rod (metal alloy of nickel and titanium, diameter 0.635&#xa0;mm,Young&#x2019;s modulus 58&#xa0;MPa) is used as the backbone. The translation and rotation of the backbone are manually actuated. We use a collet to maintain the rod at a desired deployed length, emulating an actuation carriage. The minimum segment length is 23&#xa0;mm. The magnets composing type-III FSD are ring neodymium magnets (grade N45, outer diameter 5&#xa0;mm, thickness 1&#xa0;mm, inner diameter 1.5&#xa0;mm) as designed in <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref>. All FSD have a thickness of 1.5&#xa0;mm, a diameter of 7&#xa0;mm, and contain three holes for the tendons to pass through, spaced with an angle of 120&#xb0; at a distance 2.5&#xa0;mm from the center. Both base and end disk are equipped with a magnet of the same type used for the intermediate type-III FSD. The end disk is rigidly attached to the end of the Nitinol rod. Each disk is machined and made out of aluminium.</p>
<p>To achieve the minimum segment length, the magnetic repulsion forces must be overcome because the distances between the type-III FSD are decreased. Note that the backbone is not compressible. However, its length can be controlled by a translational motor or a set screw. By treating the translational dof as a passive dof, we can find the minimal tendon forces to achieve the minimum segment length. The applied tendon force for each tendon is achieved by adding 120&#xa0;g of weights. Actuating the segment length with a translational motor and assuming that actuation of the segment length is independent from the tendon displacement, the applied translational force of the translational motor would be 3.6&#xa0;N.</p>
</sec>
<sec id="s2-3-2">
<title>2.3.2 Prototype With Type II FSDs</title>
<p>The second prototype is composed of four tendons, one backbone, and six type-II FSDs. All tendons are fixed to the end disk which is rigidly attached to the end of the backbone. Braided threads made of Spectra Fiber<sup>&#xae;</sup> (diameter of 0.28&#xa0;mm) are used for the tendons. The backbone is a Nitinol rod (diameter 0.635&#xa0;mm) which can be rotated by rotating the collet. All six type-II FSDs including the end disk have a thickness of 2&#xa0;mm, a diameter of 20&#xa0;mm, and have four holes for the tendons to pass through, spaced with an angle of 90&#xb0; at a distance 7&#xa0;mm from the center. The distance between two adjacent disks measured from midpoint to midpoint is 13&#xa0;mm, giving a total segment length of 93&#xa0;mm. Each disk weighs 0.69&#xa0;g and is 3D printed with a stereolithography printer (Formlabs<sup>&#xae;</sup>, Clear resin). To prevent the passive translational one&#x2009;dof of an FSD, each type-II FSD is sandwiched between two stoppers. All stoppers are made from the same material as the spacer disk and are rigidly attached to the backbone. <xref ref-type="fig" rid="F3">Figure 3</xref> depicts the physical prototype with exemplary configuration.</p>
<p>For experimental assessment, a pretension of 0.01&#xa0;N is applied to all tendons. Each tendon can be loaded manually with precision weights to bend the flexible backbone.</p>
</sec>
</sec>
</sec>
<sec id="s3">
<title>3 FAS Modeling</title>
<p>To investigate the proposed FAS design we derive a static model. The continuous backbone is represented by using a lumped parameterization approach, where it is approximated by a finite number of parameters. We adopt the nomenclature defined in <xref ref-type="bibr" rid="B34">Rao et al. (2021)</xref>, where a segment with <italic>n</italic> disks is divided into a series of subsegments <italic>i</italic> of length <italic>l</italic>
<sub>
<italic>i</italic>
</sub> &#x3d; (<italic>L</italic> &#x2b; <italic>&#x3b2;</italic>)/<italic>n</italic>, where <italic>i</italic> &#x3d; 1, 2, <italic>&#x2026;</italic> , <italic>n</italic>. Each subsegment consists of disk <italic>i</italic> and the portion of the backbone between disks <italic>i</italic> and <italic>i</italic> &#x2212; 1. The piecewise constant-curvature (PCC) approximation is applied to each subsegment, modeling the segment as a series of mutually tangent arcs. We assume that the shear, elongation, and compression of the backbone are negligible and that the disks are equally distributed in the inserted backbone length, as done in <xref ref-type="bibr" rid="B10">Chikhaoui et al. (2019)</xref>. We consider frictional forces acting between the tendons and disks, modeled according to the Coulumb friction law. Additionally, we consider gravity acting on the robot due to the weight of the disks. We model the tendon paths as partially constrained, i.e. the portion of the tendon between two disks is represented by a straight line segment. We adapt the model proposed in <xref ref-type="bibr" rid="B41">Yuan et al. (2019)</xref> to account for variable tendon routing.</p>
<sec id="s3-1">
<title>3.1 Kinematics</title>
<p>The center of each disk <italic>i</italic> is denoted by <italic>O</italic>
<sub>
<italic>i</italic>
</sub>. A reference frame is attached to the base of each subsegment <italic>i</italic> at <italic>O</italic>
<sub>
<italic>i</italic>&#x2212;1</sub> consisting of the local <bold>
<italic>x</italic>
</bold>
<sub>
<italic>i</italic>&#x2212;1</sub>, <bold>
<italic>y</italic>
</bold>
<sub>
<italic>i</italic>&#x2212;1</sub>, <bold>
<italic>z</italic>
</bold>
<sub>
<italic>i</italic>&#x2212;1</sub> axes, shown in <xref ref-type="fig" rid="F4">Figure 4A</xref>. The bending curvature components along the <italic>x</italic>-axis and <italic>y</italic>-axis are represented by <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>,<italic>i</italic>
</sub> and <italic>&#x3ba;</italic>
<sub>
<italic>y</italic>,<italic>i</italic>
</sub>, while <italic>&#x3b8;</italic>
<sub>
<italic>i</italic>
</sub> represents the geometric twist angle about the local <italic>z</italic>-axis, independent of the backbone torsion. The backbone is rotated by <italic>&#x3b1;</italic> in the actuation unit. This rotation results in each intermediate disks rotating about their local <italic>z</italic>-axis due to the tendon interactions. The rotation of each disk <italic>&#x3b8;</italic>
<sub>
<italic>i</italic>
</sub> around the backbone is a passive dof and relative to the backbone rotation due to torsion. We assume that this rotation can be expressed as a function of the index of the disk and written as<disp-formula id="e1">
<mml:math id="m2">
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mi>&#x3b1;</mml:mi>
<mml:mi>f</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>.</mml:mo>
</mml:math>
<label>(1)</label>
</disp-formula>
</p>
<fig id="F4" position="float">
<label>FIGURE 4</label>
<caption>
<p>
<bold>(A)</bold> Diagrammatic representation of two disks <italic>i</italic> and <italic>i</italic> &#x2212; 1 and the portion of the backbone between them. The corresponding frames attached at <italic>O</italic>
<sub>
<italic>i</italic>&#x2212;1</sub> and <italic>O</italic>
<sub>
<italic>i</italic>
</sub> have been indicated. Only one tendon has been marked red for clarity. <bold>(B)</bold> The <italic>m</italic> tendons are arranged concentrically around the backbone at a distance of <italic>r</italic>
<sub>
<italic>d</italic>
</sub>.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g004.tif"/>
</fig>
<p>Since the base is fixed, <italic>f</italic> (0) &#x3d; 0 and <italic>f</italic>(<italic>n</italic>) &#x3d; 1 are assumed. Then the relative angle of rotation between the disks is given by <inline-formula id="inf2">
<mml:math id="m3">
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula>. Therefore, each subsegment experiences bending and twisting, represented by the configuration parameters <inline-formula id="inf3">
<mml:math id="m4">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">X</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3bc;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">[</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mspace width="0.17em"/>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>y</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mspace width="0.17em"/>
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mspace width="0.17em"/>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula>, where <inline-formula id="inf4">
<mml:math id="m5">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3f5;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula>. The angle of twist <italic>&#x3f5;</italic>
<sub>
<italic>i</italic>
</sub> is due to tendon tension imposed by the bending, i.e. <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>,<italic>i</italic>
</sub> and <italic>&#x3ba;</italic>
<sub>
<italic>y</italic>,<italic>i</italic>
</sub>, whereas both geometric twist angle, i.e. <italic>&#x3b8;</italic>
<sub>
<italic>i</italic>
</sub> and <italic>&#x3b8;</italic>
<sub>
<italic>i</italic>&#x2212;1</sub>, are due to <italic>&#x3b1;</italic>. Therefore, <inline-formula id="inf5">
<mml:math id="m6">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mo>&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> considers both contribution from the kinematics and statics.</p>
<p>Using <italic>&#x3d5;</italic>
<sub>
<italic>i</italic>
</sub> &#x3d; arctan2 (<italic>&#x3ba;</italic>
<sub>
<italic>y</italic>,<italic>i</italic>
</sub>, <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>,<italic>i</italic>
</sub>) and <inline-formula id="inf6">
<mml:math id="m7">
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:msqrt>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>y</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:msqrt>
</mml:math>
</inline-formula> for the sake of simplicity, the position of the end of a subsegment <italic>i</italic> written w.r.t. to the reference frame attached to disk <italic>i</italic> &#x2212; 1 is given by<disp-formula id="e2">
<mml:math id="m8">
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold-italic">p</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mmultiscripts>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mfrac>
<mml:mrow>
<mml:mi>cos</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3d5;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfrac>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>cos</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mfrac>
<mml:mrow>
<mml:mi>sin</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3d5;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfrac>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>cos</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfrac>
<mml:mi>sin</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>.</mml:mo>
</mml:math>
<label>(2)</label>
</disp-formula>
</p>
<p>The corresponding transformation matrix from the frame at disk <italic>i</italic> to disk <italic>i</italic> &#x2212; 1 is given by<disp-formula id="e3">
<mml:math id="m9">
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold-italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mmultiscripts>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3d5;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3d5;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">&#x302;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold-italic">P</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mmultiscripts>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msup>
<mml:mrow>
<mml:mn mathvariant="bold">0</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x22a4;</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:math>
<label>(3)</label>
</disp-formula>where <bold>
<italic>R</italic>
</bold>
<sub>
<italic>y</italic>
</sub> and <bold>
<italic>R</italic>
</bold>
<sub>
<italic>z</italic>
</sub> are two of the basic rotation matrices with index indicating the axis of rotation.</p>
<p>The transformation between any two reference frames is given by the product of transformation matrices between pairs of consecutive disks. The tendons are numbered in an anti-clockwise manner and are arranged uniformly at a distance of <italic>r</italic>
<sub>
<italic>d</italic>
</sub> with an angle of 2<italic>&#x3c0;</italic>/<italic>m</italic> between them, as shown in <xref ref-type="fig" rid="F4">Figure 4B</xref>. The location of tendon <italic>k</italic> at disk <italic>i</italic> for a robot with <italic>m</italic> tendons is denoted by <italic>P</italic>
<sub>
<italic>i</italic>,<italic>k</italic>
</sub> and its coordinates w.r.t. the frame of reference at disk <italic>i</italic> &#x2212; 1 is denoted by the <inline-formula id="inf7">
<mml:math id="m10">
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="normal">v</mml:mi>
<mml:mi mathvariant="normal">e</mml:mi>
<mml:mi mathvariant="normal">c</mml:mi>
<mml:mi mathvariant="normal">t</mml:mi>
<mml:mi mathvariant="normal">o</mml:mi>
<mml:mi mathvariant="normal">r</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mspace width="0.3333em"/>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>O</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>P</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>&#x20d7;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:math>
</inline-formula>. This vector is given by<disp-formula id="e4">
<mml:math id="m11">
<mml:mmultiscripts>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>O</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>P</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>&#x20d7;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:none/>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mmultiscripts>
<mml:mo>&#x3d;</mml:mo>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold-italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mmultiscripts>
<mml:msup>
<mml:mrow>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi>r</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2061;</mml:mo>
<mml:mi>cos</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi>&#x3c0;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi>r</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2061;</mml:mo>
<mml:mi>sin</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi>&#x3c0;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x22a4;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mo>.</mml:mo>
</mml:math>
<label>(4)</label>
</disp-formula>
</p>
</sec>
<sec id="s3-2">
<title>3.2 Static Modeling</title>
<p>While the backbone representation maps the curvatures to the resulting pose in the task space, static modeling is required to obtain the curvatures for the corresponding input tensions. We do so by calculating the net moment<sup>
<italic>i</italic>&#x2212;1</sup>
<bold>
<italic>M</italic>
</bold>
<sub>
<italic>i</italic>
</sub> acting on each subsegment <italic>i</italic> caused by the forces acting on a subsegment. These forces include gravity acting in the negative <italic>z</italic>-axis due to the weight of the disks, frictional forces written using the Coulumb friction model and the forces applied on the tendons, as described in <xref ref-type="bibr" rid="B41">Yuan et al. (2019)</xref>. We then use the Hooke&#x2019;s law to relate the net moment to the resulting curvature and torsion of each subsegment using the following equation (<xref ref-type="bibr" rid="B34">Rao et al., 2021</xref>),<disp-formula id="e5">
<mml:math id="m12">
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">M</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mmultiscripts>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3d5;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mi>E</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>I</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mi>x</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mi>E</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>I</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>y</mml:mi>
<mml:mi>y</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mi>G</mml:mi>
<mml:mi>J</mml:mi>
<mml:mo>/</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi>&#x3ba;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi>&#x3f5;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:math>
<label>(5)</label>
</disp-formula>where <italic>E</italic> and <italic>G</italic> are the Young&#x2019;s and shear modulus, <italic>I</italic>
<sub>
<italic>xx</italic>
</sub> and <italic>I</italic>
<sub>
<italic>yy</italic>
</sub> are the second area moments and <italic>J</italic> is the polar second moment of cross sectional area.</p>
</sec>
<sec id="s3-3">
<title>3.3 Numerical Solution</title>
<p>The equilibrium <xref ref-type="disp-formula" rid="e5">Eq. 5</xref> constitute an implicit static model of FAS as a system of 3<italic>n</italic> non-linear equations of the form<disp-formula id="e6">
<mml:math id="m13">
<mml:mi mathvariant="bold-italic">G</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">X</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3bc;</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mrow>
<mml:mi mathvariant="bold-italic">p</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>E</mml:mi>
</mml:mrow>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="bold-italic">u</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn mathvariant="bold">0</mml:mn>
<mml:mo>,</mml:mo>
</mml:math>
<label>(6)</label>
</disp-formula>where <bold>
<italic>X</italic>
</bold>
<sub>
<italic>&#x3bc;</italic>
</sub> is the state space vector, such that <inline-formula id="inf8">
<mml:math id="m14">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">X</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3bc;</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">X</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3bc;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x22ef;</mml:mo>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">X</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3bc;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula>, <bold>
<italic>p</italic>
</bold>
<sub>
<italic>E</italic>
</sub> is the end-disk position and <bold>
<italic>u</italic>
</bold> is the vector of actuation inputs. This vector contains normally all the tendon tensions <italic>&#x3c4;</italic>
<sub>
<italic>i</italic>
</sub> applied at the robot base. However, we can reduce in our case the dimension of the actuation space spanned by these tensions by looking at the FAS properties. Since the backbone is assumed to be inextensible and the torsion deformations due to tendon actuation can be reasonably neglected, as demonstrated later on, the <italic>m</italic> tendons can only control two bending degrees of freedom independently. As a result, the tendon actuation space can be represented by two variables. We chose here to express the tendon tensions with polar coordinates. We consider that pulling on the <italic>m</italic> tendons is equivalent to pulling on one single tendon, located at a distance <italic>r</italic>
<sub>
<italic>d</italic>
</sub> from the backbone, an angle <italic>&#x3b3;</italic> around the backbone tangent from tendon 1, with a force <italic>T</italic>:<disp-formula id="e7">
<mml:math id="m15">
<mml:msub>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mi>T</mml:mi>
<mml:mo>&#x2061;</mml:mo>
<mml:mi>cos</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi>&#x3c0;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>&#x3b3;</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2b;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:mfrac>
</mml:math>
<label>(7)</label>
</disp-formula>
</p>
<p>The pretension term <italic>T</italic>
<sub>
<italic>t</italic>
</sub> is a predefined value added to prevent slack in the tendons and to ensure that constraint <inline-formula id="inf9">
<mml:math id="m16">
<mml:msubsup>
<mml:mrow>
<mml:mo movablelimits="false" form="prefix">&#x2211;</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> holds. As a result, the tendon actuation can be parametrized using <italic>&#x3b3;</italic> and <italic>T</italic> only. Considering now the actuated backbone rotation and translation, the actuation space of the FAS is four dimensional and spanned by <inline-formula id="inf10">
<mml:math id="m17">
<mml:mi mathvariant="bold-italic">u</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mi>T</mml:mi>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mi>&#x3b3;</mml:mi>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mi>&#x3b1;</mml:mi>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mi>&#x3b2;</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x22a4;</mml:mo>
</mml:mrow>
</mml:msup>
</mml:math>
</inline-formula>.</p>
<p>The implicit static model (6) is used to solve numerically the forward and inverse static of the FAS. The forward statics are obtained by fixing <bold>
<italic>u</italic>
</bold> and solving the equations for <bold>
<italic>X</italic>
</bold>
<sub>
<italic>&#x3bc;</italic>
</sub>, which allows in turn to obtain <bold>
<italic>p</italic>
</bold>
<sub>
<italic>E</italic>
</sub>. The inverse statics are obtained by fixing <bold>
<italic>p</italic>
</bold>
<sub>
<italic>E</italic>
</sub>, as well as three actuation inputs, and solve <xref ref-type="disp-formula" rid="e6">(6)</xref> for <bold>
<italic>X</italic>
</bold>
<sub>
<italic>&#x3bc;</italic>
</sub> and the remaining actuation input. Both forward and inverse static models are solved using a Newton-Raphson algorithm on <sc>Matlab</sc>.</p>
</sec>
<sec id="s3-4">
<title>3.4 Model Verification</title>
<p>In this section, we verify our model. First, the influence of the backbone rotation on the disk rotation is determined. Afterwards, robot shapes are measured for different configurations. Some of them are used to calibrate the model. Finally, the model is evaluated.</p>
<sec id="s3-4-1">
<title>3.4.1 Identifying Tendon Routing</title>
<p>To quantify the non-straight tendon routing obtained after rotation of the backbone, we identify experimentally the function <italic>f</italic>(<italic>i</italic>) in <xref ref-type="disp-formula" rid="e1">(1)</xref> by using the first physical prototype, see <xref ref-type="sec" rid="s2-3-1">Section 2.3.1</xref>. Since the tendons are only pre-tensioned, the segment is straight. To measure the angle between the base and the different FSDs, we add a protractor scale at the base and attach an outward-pointing marker on each FSD. We read off the current angle of an FSD for a given <italic>&#x3b1;</italic>. The length of the segment is set to 65&#xa0;mm, while the angle <italic>&#x3b1;</italic> is varied, i.e. <italic>&#x3b1;</italic> &#x2208; { &#x2212; <italic>&#x3c0;</italic>/2 rad, &#x2212; 4<italic>&#x3c0;</italic>/3 rad, 3<italic>&#x3c0;</italic>/2 rad}.</p>
<p>
<xref ref-type="fig" rid="F5">Figure 5</xref> shows the orientation of each FSD and the end disk w.r.t. the base. The angles of the FSD, normalized w.r.t. <italic>&#x3b1;</italic> and indexed from robot base to tip are 0 &#xb1; 0, 0.12 &#xb1; 03, 0.15 &#xb1; 08, 0.23 &#xb1; 11, 0.36 &#xb1; 05, 0.45 &#xb1; 07, 0.54 &#xb1; 07, 0.61 &#xb1; 08, 0.64 &#xb1; 09, 0.74 &#xb1; 07, 0.82 &#xb1; 06, 0.87 &#xb1; 06, 0.98 &#xb1; 02, and 1 &#xb1; 0, respectively. We deduce from the above that <italic>f</italic>(<italic>i</italic>) is a linear function, equal to <italic>i</italic>/<italic>n</italic>, when the robot is in a straight configuration. In the rest of the paper, we will assume that this function stays linear when the FAS is bent. While this is an approximation of the real distribution of the disks rotation, it leads to a static model with reasonable accuracy as demonstrated later. Hence, the type of non-straight tendon routing is a helical tendon routing for the straight configurations with pre-tension. Note that helical curves in space are characterized by a smooth curve, e.g. tendon routing, with tangent lines at a constant angle to a fixed axis, e.g. backbone. Therefore, the prototype is capable of generating variable helical tendon routing. We identify two main causes of the error indicated by the error bars in <xref ref-type="fig" rid="F5">Figure 5</xref>; tilting of the type-III FSD and parallax error.</p>
<fig id="F5" position="float">
<label>FIGURE 5</label>
<caption>
<p>Course of disk orientation for tendon routing assessment. Orientations in rad of each disks indicate a helical tendon routing. <bold>(A)</bold> Three different rotations of the end disk <italic>EE</italic> (type-0 FSD) causing change of the orientation of each disk <italic>D</italic>
<sub>
<italic>i</italic>
</sub>, where <italic>D</italic>
<sub>1</sub> is the proximal type-III FSD, <italic>D</italic>
<sub>1</sub> is the distal type-III FSD, and all other type-III FSD are in between with increasing <italic>i</italic>. The blue, red, and green curve corresponds to disk rotation induces by <italic>&#x3b1;</italic> &#x3d; &#x2212;<italic>&#x3c0;</italic>/2 rad, <italic>&#x3b1;</italic> &#x3d; &#x2212;4<italic>&#x3c0;</italic>/3 rad, and <italic>&#x3b1;</italic> &#x3d; 3<italic>&#x3c0;</italic>/2 rad, respectively. <bold>(B)</bold> Normalized angles of the three different rotations indicate a linear trend.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g005.tif"/>
</fig>
</sec>
<sec id="s3-4-2">
<title>3.4.2 Data Acquisition</title>
<p>For the model verification, we use the second physical prototype, see <xref ref-type="sec" rid="s2-3-2">Section 2.3.2</xref>. This prototype cannot change its segment length. However, it should be more suitable for the verification due to the absence of repulsive forces between adjacent disks and the larger radius of each FSD compared to the first prototype. Note that the required tendon tension for a specific bending is proportional to the square of the distance between the tendon holes and the backbone as mentioned by <xref ref-type="bibr" rid="B32">Oliver-Butler et al. (2019)</xref>. Therefore, the second prototype is more sensible to tendon tension variation, which can be seen in <xref ref-type="fig" rid="F3">Figure 3</xref> by visually comparing both prototypes under different tendon tensions.</p>
<p>The points are measured with a tactile measurement device (MicroScribe<sup>&#xae;</sup> MX, Revware Systems Inc., NC, United States) for different <italic>&#x3b1;</italic> values and weights. <xref ref-type="table" rid="T1">Table 1</xref> lists all 20 configurations. For each configuration, 20 points on the perimeter of each disk are recorded. To obtain the midpoint of the respective disk, we then use eigenvectors and apply Apollonius&#x2019; problem for given <italic>M</italic> &#x2265; 3 different points.</p>
<table-wrap id="T1" position="float">
<label>TABLE 1</label>
<caption>
<p>Configurations for model verification assessment. The tendon tensions of <italic>&#x3c4;</italic>
<sub>1</sub> are indicated by the mass of the precision weights. The weights are sampled from an uniform random between 0 and 250&#xa0;g. Adapted from the machine learning literature (<xref ref-type="bibr" rid="B5">Bergstra and Bengio (2012)</xref>), we prefer sampling from a random distribution over a grid search approach</p>
</caption>
<table>
<thead valign="top">
<tr>
<th colspan="4" align="center">
<italic>&#x3b1;</italic>
</th>
</tr>
<tr>
<th align="center">0 rad</th>
<th align="center">&#x2212;<italic>&#x3c0;</italic>/2 rad</th>
<th align="center">
<italic>&#x3c0;</italic> rad</th>
<th align="center">&#x2212;3<italic>&#x3c0;</italic>/2 rad</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">89&#xa0;g</td>
<td align="center">213&#xa0;g</td>
<td align="center">106&#xa0;g</td>
<td align="center">187&#xa0;g</td>
</tr>
<tr>
<td align="left">242&#xa0;g</td>
<td align="center">20&#xa0;g</td>
<td align="center">181&#xa0;g</td>
<td align="center">132&#xa0;g</td>
</tr>
<tr>
<td align="left">214&#xa0;g</td>
<td align="center">92&#xa0;g</td>
<td align="center">145&#xa0;g</td>
<td align="center">15&#xa0;g</td>
</tr>
<tr>
<td align="left">127&#xa0;g</td>
<td align="center">113&#xa0;g</td>
<td align="center">131&#xa0;g</td>
<td align="center">230&#xa0;g</td>
</tr>
<tr>
<td align="left">178&#xa0;g</td>
<td align="center">42&#xa0;g</td>
<td align="center">203&#xa0;g</td>
<td align="center">178&#xa0;g</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The Apollonius&#x2019; problem is concerned with the construction of circles that are tangent to any combination of three given objects, where an object represents a point, line, or circle (<xref ref-type="bibr" rid="B11">Coxeter, 1968</xref>). We take advantage of the PPP-method, i.e. three points are given. The PPP-method requires three distinguishable points and provides the sought-after midpoint. Here, we present the extended method for <italic>M</italic> &#x2265; 3 different points. Note that computing the midpoint by using the mean value of <italic>M</italic> different points will lead to a high error with high variance. The equation of a circle for a given 2-dimensional point with index <italic>i</italic> is <inline-formula id="inf11">
<mml:math id="m18">
<mml:msup>
<mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x3d;</mml:mo>
<mml:mi>r</mml:mi>
</mml:math>
</inline-formula>, where the midpoint has the index <italic>m</italic> and the unknown radius of the circle is <italic>r</italic>. By expanding out the equation, reordering the values, and using the substitution <inline-formula id="inf12">
<mml:math id="m19">
<mml:mi>h</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>r</mml:mi>
</mml:math>
</inline-formula>, the equation <inline-formula id="inf13">
<mml:math id="m20">
<mml:mi>h</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>&#x3d;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:math>
</inline-formula> can be obtained. For each measured point, a linear equation is obtained leading to a system of linear equations given by<disp-formula id="e8">
<mml:math id="m21">
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mn>1</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mn>1</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mo>&#x22ee;</mml:mo>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x22ee;</mml:mo>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x22ee;</mml:mo>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mn>1</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mn>1</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mi>h</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mo>&#x22ee;</mml:mo>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msubsup>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>&#x2b;</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:math>
<label>(8)</label>
</disp-formula>which can be solved via pseudo-inverse. Note that <italic>h</italic> is an auxiliary variable and <italic>r</italic> can be used for a sanity check, i.e. <italic>r</italic> should match the radius of the measured disk plus the radius of the probe of the tactile measurement device.</p>
<p>To extend the above method to 3-dimensional points, we project the measured points onto a suitable plane and utilized the above method exploiting Apollonius&#x2019; problem. The transformation to the plane can be found by finding a frame, where two axes span the plane and the third axis is orthogonal to the plane. The frame can be found by computing the eigenvectors or principle components of the set of measured points. Methods like Singular Value Decomposition (SVD) or Principal Component Analysis (PCA) can be used to determine the axes of the frame. For the projection, the <italic>z</italic> component of each transformed points is set to zero. The found frame is used to transform the measured points before the projection and transform the midpoint back to the original coordinate system. Note that the frame of the original coordinate system can be any orthonormal frame.</p>
</sec>
<sec id="s3-4-3">
<title>3.4.3 Calibration</title>
<p>Due to errors in assembling and manufacturing, the measured base coordinate frame does not match the robot&#x2019;s base coordinate frame. We model these errors by adding rotations of <italic>&#x3b3;</italic>
<sub>
<italic>y</italic>
</sub> and <italic>&#x3b3;</italic>
<sub>
<italic>z</italic>
</sub> about the <italic>y</italic>-axis and <italic>z</italic>-axis. To estimate the two angles in addition to the coefficient of friction, a nonlinear unconstrained optimization problem was implemented to minimize the average of the tip errors over twelve readings. The Nelder-Mead simplex algorithm implemented in <sc>Matlab</sc>&#x2019;s fminsearch function was used to perform the optimization. The values of <italic>&#x3b3;</italic>
<sub>
<italic>y</italic>
</sub> and <italic>&#x3b3;</italic>
<sub>
<italic>z</italic>
</sub> were obtained to be &#x2212;0.0873&#x2009;rad, &#x2212;0.0524&#xa0;rad. The friction coefficient was obtained to be <italic>&#x3bc;</italic> &#x3d; 0.30. The Youngs modulus was estimated as 58&#xa0;GPa.</p>
</sec>
<sec id="s3-4-4">
<title>3.4.4 Evaluation of Model Performance</title>
<p>We use two metrics to evaluate the performance of the model. The tip error measures the Euclidean distance of the measured position of the last disk from the position predicted by the model. The backbone shape error is the average of the Euclidean distance between the measured and predicted position of each disk. We generate a set of robot configurations by considering four different values of <italic>&#x3b1;</italic> and by actuating one tendon with different weights, see <xref ref-type="table" rid="T1">Table 1</xref>.</p>
<p>The obtained errors for four different values of <italic>&#x3b1;</italic>, averaged over multiple readings with individual tendon tensions are summarized in <xref ref-type="table" rid="T2">Table 2</xref>. The corresponding shapes of the robot, obtained experimentally and through the model have been depicted in <xref ref-type="fig" rid="F6">Figure 6</xref>. The average tip and backbone error over the 20 observations are 4 and 2.17&#xa0;mm (respectively 4.39&#x2009;% and 2.39% of the robot length), which are reasonable values for a first model and proof of concept of FAS.</p>
<table-wrap id="T2" position="float">
<label>TABLE 2</label>
<caption>
<p>Average tip errors and backbone shape errors for different values of <italic>&#x3b1;</italic>. Mean and standard deviation of the errors are listed. We report the absolute errors in millimetre and relative errors in % w.r.t. segment length <italic>L</italic> &#x3d; 93&#xa0;mm.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th rowspan="2" align="left">
<italic>&#x3b1;</italic> in rad</th>
<th colspan="2" align="center">Tip error</th>
<th colspan="2" align="center">Shape error</th>
</tr>
<tr>
<th align="center">mm</th>
<th align="center">% w.r.t. Length</th>
<th align="center">mm</th>
<th align="center">% w.r.t. Length</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">0</td>
<td align="char" char="plusmn">2.44 &#xb1; 1.71</td>
<td align="char" char="plusmn">2.68 &#xb1; 1.88</td>
<td align="char" char="plusmn">1.96 &#xb1; 0.56</td>
<td align="char" char="plusmn">2.15 &#xb1; 0.62</td>
</tr>
<tr>
<td align="left">&#x2212; <italic>&#x3c0;</italic>/2</td>
<td align="char" char="plusmn">3.89 &#xb1; 1.74</td>
<td align="char" char="plusmn">4.28 &#xb1; 1.91</td>
<td align="char" char="plusmn">2.14 &#xb1; 0.15</td>
<td align="char" char="plusmn">2.36 &#xb1; 0.17</td>
</tr>
<tr>
<td align="left">
<italic>&#x3c0;</italic>
</td>
<td align="char" char="plusmn">3.58 &#xb1; 1.74</td>
<td align="char" char="plusmn">3.93 &#xb1; 1.91</td>
<td align="char" char="plusmn">1.91 &#xb1; 0.42</td>
<td align="char" char="plusmn">2.10 &#xb1; 0.47</td>
</tr>
<tr>
<td align="left">&#x2212;3<italic>&#x3c0;</italic>/2</td>
<td align="char" char="plusmn">6.09 &#xb1; 2.25</td>
<td align="char" char="plusmn">6.70 &#xb1; 2.47</td>
<td align="char" char="plusmn">2.68 &#xb1; 0.76</td>
<td align="char" char="plusmn">2.95 &#xb1; 0.84</td>
</tr>
<tr>
<td align="left">
<inline-formula id="inf14">
<mml:math id="m22">
<mml:mfenced open="{" close="}">
<mml:mrow>
<mml:mn>0</mml:mn>
<mml:mo>,</mml:mo>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>&#x3c0;</mml:mi>
<mml:mo>/</mml:mo>
<mml:mn>2</mml:mn>
<mml:mo>,</mml:mo>
<mml:mi>&#x3c0;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>3</mml:mn>
<mml:mi>&#x3c0;</mml:mi>
<mml:mo>/</mml:mo>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula>
</td>
<td align="char" char="plusmn">4.00 &#xb1; 2.19</td>
<td align="char" char="plusmn">4.39 &#xb1; 2.41</td>
<td align="char" char="plusmn">2.17 &#xb1; 0.58</td>
<td align="char" char="plusmn">2.39 &#xb1; 0.63</td>
</tr>
</tbody>
</table>
</table-wrap>
<fig id="F6" position="float">
<label>FIGURE 6</label>
<caption>
<p>For different tension values, experimental measurements (in black dots) plotted against the backbone curve predicted by the proposed model for <bold>(A)</bold> <italic>&#x3b1;</italic> &#x3d; 0, <bold>(B)</bold> <italic>&#x3b1;</italic> &#x3d; &#x2212; <italic>&#x3c0;</italic>/2 rad, <bold>(C)</bold> <italic>&#x3b1;</italic> &#x3d; <italic>&#x3c0;</italic> rad, and <bold>(D)</bold> <italic>&#x3b1;</italic> &#x3d; &#x2212;3<italic>&#x3c0;</italic>/2 rad. The figures show the 3D plot (top row), projection on the <italic>xz</italic>-plane (middle) and the projection on the <italic>yz</italic>-plane (bottom).</p>
</caption>
<graphic xlink:href="frobt-09-873446-g006.tif"/>
</fig>
<p>The errors are the lowest for <italic>&#x3b1;</italic> &#x3d; 0 rad as it only experiences in-plane bending. The largest errors occur for <italic>&#x3b1;</italic> &#x3d; &#x2212;3<italic>&#x3c0;</italic>/2 rad, where the out-of-plane deformations are larger. The errors could be attributed to the simplified assumptions made by the model. The model considers the tendon location at each disk to be a fixed point. However, due to manufacturing constraints the holes made for the tendons have a certain tolerance and this results in the tendon locations at each disk to vary in different configurations. Other possible sources of error could arise from inaccuracies in measurement, assembling, and manufacturing of the prototype. Along with the error between measured and predicted robot shapes, we observe that the robot backbone is not significantly twisted by the tendon tension. The maximum value of <italic>&#x3f5;</italic>
<sub>
<italic>i</italic>
</sub>, in the robot configuration involving the largest tendon forces and backbone rotation, equals 3.7<italic>%</italic> of <italic>&#x3b1;</italic>. This is due to the fact that the Nitinol rod composing the robot backbone is torsionally stiff.</p>
</sec>
</sec>
</sec>
<sec id="s4">
<title>4 Follow-the-Leader Deployment</title>
<p>In the following, we highlight the FTL deployment capabilities of the proposed design. First, we motivate a simple deployment strategy. Afterwards, this strategy is evaluated on a physical FAS prototype. Second, we further investigate this strategy in simulation with our proposed model. It has the advantage of neglecting hard-to-model phenomena, e.g. magnetic repulsion forces and slip-stick effect between FSD and backbone. Note that the repulsion forces are needed to distribute the FSD along the backbone. Therefore, we neglect the accurate modeling of the repulsion forces and assume a static equidistant distribution of FSD along the backbone to mitigate the influence of model inaccuracy of those hard-to-model phenomena.</p>
<sec id="s4-1">
<title>4.1 Deployment Strategy</title>
<p>Achieving FTL behaviour requires the continuum robot to keep a constant curvature at any arc-length along the path during the deployment (<xref ref-type="bibr" rid="B14">Garriga-Casanovas and Rodriguez y Baena, 2018a</xref>). This has been achieved so far for multi-segment TDCR by using specific optimization routines. The displacement to be applied on each tendon is calculated at each step of the deployment in order to minimize the error between the position of the robot backbone and the path to be followed (<xref ref-type="bibr" rid="B33">Palmer et al., 2014</xref>). As a result, approximate FTL behaviour is obtained, which accuracy depends on the accuracy of the model used to predict the robot shape and the range of extensibility achievable by each segment (<xref ref-type="bibr" rid="B3">Amanov et al., 2019</xref>). Although this optimization based approach can be generally applied to any continuum robot, it is complex and can be computationally heavy. We propose here a simpler deployment strategy for TDCR and, in particular, for the FAS, that takes advantage specifically of tendon actuation.</p>
<p>When a single segment TDCR composed of straight-routed and fully constrained tendons is considered, and the effects of gravity and friction are assumed to be negligible, it has been shown that the tension applied by the tendon can be represented by a constant moment applied (<xref ref-type="bibr" rid="B9">Camarillo et al., 2008</xref>). The constant moment results in constant curvature of the backbone. As a result, by applying a constant tendon force and by progressively increasing the length of this segment, the deployed robot bends in a plane with a constant curvature. It has the same curvature at any arc-length along the path. Consequently, a one segment TDCR for which the tendon force is controlled can be used to perform perfect FTL deployments along planar paths. Similarly for the FAS, we suspect that applying constant tendon tensions during the deployment will lead to a segment with constant bending and torsional curvature. Deploying the backbone, i.e. changing <italic>&#x3b2;</italic>, while keeping the backbone rotation, i.e. <italic>&#x3b1;</italic> constant, should thus lead to FTL deployments along spatial helical paths.</p>
</sec>
<sec id="s4-2">
<title>4.2 Area-Based FTL Error</title>
<p>To assess the FTL deployment, we propose a measure which takes the covered projected area of the volume of the robot&#x2019;s shape along a path during a deployment sequence into account. First, we define the overall covered area <inline-formula id="inf15">
<mml:math id="m23">
<mml:mi mathvariant="script">A</mml:mi>
</mml:math>
</inline-formula> given by<disp-formula id="e9">
<mml:math id="m24">
<mml:mi mathvariant="script">A</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:munderover accentunder="false" accent="false">
<mml:mrow>
<mml:mo>&#x22c3;</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:munderover>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
<mml:mo>,</mml:mo>
</mml:math>
<label>(9)</label>
</disp-formula>where <inline-formula id="inf16">
<mml:math id="m25">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> and <italic>n</italic> are the area covered by the projected robot&#x2019;s shape at the <italic>i</italic>th step and the number of steps to reach the end of the path, respectively. Hence, <inline-formula id="inf17">
<mml:math id="m26">
<mml:mi mathvariant="script">A</mml:mi>
</mml:math>
</inline-formula> is the projected area of the volume covered during the FTL deployment. Note that <inline-formula id="inf18">
<mml:math id="m27">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> and <inline-formula id="inf19">
<mml:math id="m28">
<mml:mi mathvariant="script">A</mml:mi>
</mml:math>
</inline-formula> are defined as sets of points which constitute the respective area.</p>
<p>Second, we can define the area-based FTL error in terms of sets as<disp-formula id="e10">
<mml:math id="m29">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x5c;</mml:mo>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x22c3;</mml:mo>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
<mml:mo>&#x5c;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfrac>
<mml:mo>,</mml:mo>
</mml:math>
<label>(10)</label>
</disp-formula>where <inline-formula id="inf20">
<mml:math id="m30">
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:mo>&#x22c5;</mml:mo>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula> is an operator acting on the set, which gives the area a numerical value depending on the sensors used to sense the shape. The numerator is the symmetric difference, also known as the disjunctive union, which represent the difference between the ideal area <inline-formula id="inf21">
<mml:math id="m31">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> and actual covered area <inline-formula id="inf22">
<mml:math id="m32">
<mml:mi mathvariant="script">A</mml:mi>
</mml:math>
</inline-formula>. The denominator normalizes the difference w.r.t. <inline-formula id="inf23">
<mml:math id="m33">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula>. Note that <xref ref-type="disp-formula" rid="e10">(10)</xref> represents a simplification of a volumetric error measure, which considers spatial points and a continuous time during deployment. Further note that it is assumed that the robot is extending. To consider the contraction of the robot, <inline-formula id="inf24">
<mml:math id="m34">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> is replaced by <inline-formula id="inf25">
<mml:math id="m35">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula>, whereas <inline-formula id="inf26">
<mml:math id="m36">
<mml:mi mathvariant="script">A</mml:mi>
</mml:math>
</inline-formula> reminds the same as changing the order of the operands in <xref ref-type="disp-formula" rid="e9">(9)</xref> does not change the result.</p>
<p>Finally, we define the area-based FTL error <inline-formula id="inf27">
<mml:math id="m37">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> quantified by<disp-formula id="e11">
<mml:math id="m38">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
<mml:mo>,</mml:mo>
</mml:math>
<label>(11)</label>
</disp-formula>which is equivalent to (10) since the nominator of <xref ref-type="disp-formula" rid="e10">(10)</xref> in combination with the overall area (9) leads to <inline-formula id="inf28">
<mml:math id="m39">
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x5c;</mml:mo>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x22c3;</mml:mo>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
<mml:mo>&#x5c;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2212;</mml:mo>
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">A</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula>. However, (11) gives a more practical implementation.</p>
<p>In this paper, we use a camera to sense the shape and images as sensor outputs. To give a numerical value to the area, we construct a binary image, where all pixels occupied by the robot are white and the rest are black. The operator <inline-formula id="inf29">
<mml:math id="m40">
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:mo>&#x22c5;</mml:mo>
</mml:mrow>
</mml:mfenced>
</mml:math>
</inline-formula> adds up then the white pixels in the binary image.</p>
</sec>
<sec id="s4-3">
<title>4.3 Preliminary Study on FTL Deployment</title>
<p>Using the FAS prototype described in <xref ref-type="sec" rid="s2-3-1">Section 2.3.1</xref>, we load one tendon with an additional 5&#xa0;N to the pretension. We indicate the termination point of the tendon as well as the end disk orientation using a red flag. <xref ref-type="fig" rid="F7">Figures 7A,B</xref> shows a sequence of an in-plane deployment and an out-of-plane deployment, where <italic>&#x3b1;</italic> &#x3d; 0 rad and <italic>&#x3b1;</italic> &#x3d; &#x2212;<italic>&#x3c0;</italic> rad, respectively. As can be seen from <xref ref-type="fig" rid="F7">Figure 7</xref>, the orientation around the tangent vector of the backbone is constant during deployment, whereas the orientation changes continuously along the spatial path. The change in orientation indicates torsion along the backbone during the deployment.</p>
<fig id="F7" position="float">
<label>FIGURE 7</label>
<caption>
<p>FTL deployment with physical prototype. <bold>(A)</bold> Sequence of an in-plane FTL deployment with straight routed tendons. <bold>(B)</bold> Sequence of an out-of-plane FTL deployment non-straight routed tendons. The red flag on top of the end disk is used to indicate the orientation. <bold>(C)</bold> Segmented binary image of the representative sequence. The reference step is contrasted with the overlapped segmented image of all images within the sequence to obtain the binary image, which will be used for <inline-formula id="inf30">
<mml:math id="m41">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula>. <bold>(D)</bold> The Evaluation process as described in <xref ref-type="sec" rid="s4-2">Section 4.2</xref> is exemplary shown for the in-plane FTL deployment. The accompanying video provides additional visual aid.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g007.tif"/>
</fig>
<p>For the evaluation of the FTL deployment, we utilize (11) and consider nine steps of each sequence, see <xref ref-type="fig" rid="F7">Figure 7D</xref>. In order to consider all continuous intermediate steps between two discrete steps, we manually segment the prototype with a conceived sleeve including all disks, tendons, and the backbone. An example of a conceived sleeve is represented with a blue hull in <xref ref-type="fig" rid="F7">Figure 7D</xref>. The sleeves of each sequence are overlaid and binary images are generated. The binary image indicate the occupied area representing the occupied volume during the deployment. <xref ref-type="fig" rid="F7">Figure 7C</xref> illustrates the area indicated by white pixel in the binary image. We achieve an error of <inline-formula id="inf31">
<mml:math id="m42">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.1537</mml:mn>
</mml:math>
</inline-formula> and <inline-formula id="inf32">
<mml:math id="m43">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.1399</mml:mn>
</mml:math>
</inline-formula> for the in-plane and out-of-plane deployment, respectively.</p>
<p>Using the photographs taken from a motion sequence in (<xref ref-type="bibr" rid="B2">Amanov et al., 2016</xref>), the extensible segment TDCR achieves <inline-formula id="inf33">
<mml:math id="m44">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.2280</mml:mn>
</mml:math>
</inline-formula>, whereas a CTCR used in <xref ref-type="bibr" rid="B19">Girerd et al. (2020)</xref> achieves <inline-formula id="inf34">
<mml:math id="m45">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.3285</mml:mn>
</mml:math>
</inline-formula> in simulation and <inline-formula id="inf35">
<mml:math id="m46">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>3.2728</mml:mn>
</mml:math>
</inline-formula> with real hardware. Note that in (<xref ref-type="bibr" rid="B2">Amanov et al., 2016</xref>) the extensible segment TDCR has three segments and that a CTCR is typically incapable of pure FTL deployment as stated in (<xref ref-type="bibr" rid="B18">Gilbert and Webster, 2013</xref>). However, results give an intuition about which value of the error measure <inline-formula id="inf36">
<mml:math id="m47">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> corresponds to an acceptable FTL deployment since it has been shown in (<xref ref-type="bibr" rid="B30">Neumann and Burgner-Kahrs, 2016</xref>) that an extensible segment TDCR (<xref ref-type="bibr" rid="B31">Nguyen and Burgner-Kahrs, 2015</xref>) is capable of FTL deployment. The achieved results <inline-formula id="inf37">
<mml:math id="m48">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.1537</mml:mn>
</mml:math>
</inline-formula> for the in-plane FTL deployment show a smaller error as the physical prototype has one segment. For the case <italic>&#x3b1;</italic> &#x3d; 0&#xb0;, the built prototype is essentially an extensible segment TDCR with one segment. Using three segments instead of one would probably lead to similar errors as the one reported by <xref ref-type="bibr" rid="B2">Amanov et al. (2016)</xref>. Consequently, the value of <inline-formula id="inf38">
<mml:math id="m49">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> seems reasonable. More important, the error for the out-of-plane FTL deployment being <inline-formula id="inf39">
<mml:math id="m50">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.1399</mml:mn>
</mml:math>
</inline-formula> is in the same range. This demonstrates that one FAS is capable of FTL deployment along spatial paths, which cannot be achieved with previously proposed TDCR segment designs.</p>
</sec>
<sec id="s4-4">
<title>4.4 Analysis of FTL Paths in Simulation</title>
<p>The errors of FTL behaviour observed during the FAS deployment may be due to two reasons. First, as the torsion of the path to follow is constant, the geometric twist angle <italic>&#x3b8;</italic> must vary linearly with the arc-length along the path. As for now, the geometric twist angle <italic>&#x3b8;</italic> is determined by the backbone rotation <italic>&#x3b1;</italic>, which is kept constant during the deployment. Second, the curvature of the segment may be constant for one deployment step but might change slightly with the segment length as the tendons are not fully constrained. They are here locally constrained by the FSD. The goals of the analysis in simulation are two folds: to study the effect of these two sources of errors and to demonstrate the range of reference path that can be followed with the FAS.</p>
<p>In order to do so, we first update the FTL deployment strategy. In addition to varying the inserted length of the backbone and keeping the applied tensions constant, we use variations in <italic>&#x3b1;</italic> to follow the natural change in twist of the reference path. We consider the reference path as the shape of a segment with length <italic>l</italic>
<sup>&#x2217;</sup> actuated by pulling on the first tendon, with the central backbone rotated by <italic>&#x3b1;</italic>&#x2217;. The FTL deployment is then simulated by solving the forward static model while varying the insertion length <italic>l</italic>, where <italic>l</italic> &#x3c; <italic>l</italic>
<sup>&#x2217;</sup>. The applied rotation <italic>&#x3b1;</italic> for any intermediate configuration is scaled linearly w.r.t. the inserted length and is calculated as:<disp-formula id="e12">
<mml:math id="m51">
<mml:mi>&#x3b1;</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mi>&#x3b1;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2217;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mfrac>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2217;</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:mfrac>
</mml:math>
<label>(12)</label>
</disp-formula>
</p>
<p>We then simulate FTL deployments with different number of disks along the backbone, to observe the effect of the tendon constraint, and for different reference paths. The obtained intermediate configurations in the FTL deployment have been shown in <xref ref-type="fig" rid="F8">Figures 8A&#x2013;D</xref>. We observe that for small numbers of disks, the obtained configurations do not perfectly align with the reference path. This deviation is due to the assumption of partially constrained tendon. As the tendons are not always normal to the end disk, the moments resulting from their forces, and as a consequence the backbone curvature and torsion, change with the deployed length. When the number of disks is increased such that the tendon path resembles a fully constrained design [as defined in (<xref ref-type="bibr" rid="B34">Rao et al., 2021</xref>)], exact spatial FTL is achieved.</p>
<fig id="F8" position="float">
<label>FIGURE 8</label>
<caption>
<p>FTL deployment results for varying segment lengths and configurations. A Sequence-wise FTL deployment is shown in <bold>(A&#x2013;D)</bold>. For <italic>&#x3b1;</italic>&#x2a; &#x3d; <italic>&#x3c0;</italic> rad and <italic>l</italic>&#x2a; &#x3d; 0.3 m, the desired path is shown in black. The corresponding backbone shape obtained for intermediate lengths with <italic>n</italic> &#x3d; 10 is shown in alternate colors for <bold>(A)</bold> <italic>l</italic> &#x3d; 0.1 m <bold>(B)</bold> <italic>l</italic> &#x3d; 0.15 m <bold>(C)</bold> <italic>l</italic> &#x3d; 0.2 m, and <bold>(D)</bold> <italic>l</italic> &#x3d; 0.25&#xa0;m. <bold>(E)</bold> FTL deployment results for 20 random values of <italic>&#x3b1;</italic>&#x2a; and tensions. The corresponding spatial paths for <italic>n</italic> &#x3d; 50 and the intermediate FTL deployment stages have been shown for different values of inserted length, i.e. <italic>l</italic> &#x2208; {0.1, 0.15, 0.2, 0.25&#xa0;m}.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g008.tif"/>
</fig>
<p>The intermediate configurations have been super-imposed and indicated for different values of inserted lengths. Applying (11) to different projections of the covered area for nine equal-distance steps for a diameter of 5&#xa0;mm, we get <inline-formula id="inf40">
<mml:math id="m52">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mi>y</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.257</mml:mn>
</mml:math>
</inline-formula>, <inline-formula id="inf41">
<mml:math id="m53">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.012</mml:mn>
</mml:math>
</inline-formula>, and <inline-formula id="inf42">
<mml:math id="m54">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>y</mml:mi>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.091</mml:mn>
</mml:math>
</inline-formula> for the projection onto the <italic>xy</italic>-plane, <italic>xz</italic>-plane, and <italic>yz</italic>-plane, respectively. Those values correspond to a model with <italic>n</italic> &#x3d; 10 disks, where as <inline-formula id="inf43">
<mml:math id="m55">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mi>y</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.0581</mml:mn>
</mml:math>
</inline-formula>, <inline-formula id="inf44">
<mml:math id="m56">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.0259</mml:mn>
</mml:math>
</inline-formula>, and <inline-formula id="inf45">
<mml:math id="m57">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>y</mml:mi>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.0303</mml:mn>
</mml:math>
</inline-formula> correspond to <italic>n</italic> &#x3d; 50 case. For comparison, for <italic>n</italic> &#x3d; 50 and with the previous FTL strategy, where <italic>&#x3b1;</italic> &#x3d; const. w.r.t. <italic>l</italic> during the deployment, we obtain <inline-formula id="inf46">
<mml:math id="m58">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mi>y</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.474</mml:mn>
</mml:math>
</inline-formula>, <inline-formula id="inf47">
<mml:math id="m59">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>x</mml:mi>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.8128</mml:mn>
</mml:math>
</inline-formula>, and <inline-formula id="inf48">
<mml:math id="m60">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>y</mml:mi>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1.538</mml:mn>
</mml:math>
</inline-formula>. It is apparent that previous FTL strategy leads to higher FTL error and, therefore, varying the value of <italic>&#x3b1;</italic> linearly with length leads to better FTL performance. Further, the FTL error decreases with larger values of <italic>n</italic>. This reinforces the previous observation and lets us conclude that the higher the number of FSD, the better the accuracy for the FTL deployment. Finally, we can make an evident observation that the values of <inline-formula id="inf49">
<mml:math id="m61">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="script">L</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>FTL</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:math>
</inline-formula> are view dependent due to the projection of the 3D volume of the robot&#x2019;s shape onto a plane.</p>
<p>In <xref ref-type="fig" rid="F8">Figure 8E</xref>, we show 20 spatial paths with <italic>&#x3b1;</italic>&#x2a; &#x2208; [ &#x2212; <italic>&#x3c0;</italic> rad, <italic>&#x3c0;</italic> rad] and randomized values of tensions applied to the first tendon for <italic>n</italic> &#x3d; 50. We see that the robot observes FTL deployment for intermediate lengths along the various 3D spatial paths.</p>
</sec>
</sec>
<sec id="s5">
<title>5 Position Redundancy</title>
<p>Investigating the position redundancy of the FAS involves to find the different robot configurations leading to a desired tip position, and to analyse the resulting robot shapes and tip orientations. Therefore, we first state a computational method to investigate this position redundancy. Second, the phenomena is qualitatively verified on a physical FAS prototype. Afterwards, further investigating on the redundancy are provided in simulation.</p>
<sec id="s5-1">
<title>5.1 Numerical Analysis Method</title>
<p>In order to obtain the robot configurations, standard approaches rely on a heavy discretization of the actuation space (<xref ref-type="bibr" rid="B40">Wu et al., 2017</xref>), spanned by <bold>
<italic>u</italic>
</bold> in our case, or of the task space (<xref ref-type="bibr" rid="B26">Li et al., 2017</xref>). In the first case, the static model is solved for each set of actuation inputs, leading to a dense set of tip positions. The robot configurations leading to tip positions in the vicinity of a desired position are gathered, leading to a set of tip orientations. In the second case, the tip orientation is parametrized by rotations around specific axes and discretized for each possible tip position in the workspace. The inverse static model is then solved for each tip pose, and converges eventually toward a robot configuration in case the pose is achievable. These two methods are both computationally expensive, and their result depends on the discretization strategy and density. The task space discretization approach requires to know the rotation axis of the robot tip, which cannot be completely controled with the four&#x2009;dof of the FAS. Moreover, the convergence of the inverse static model depends on the initial guess provided to the numerical solver.</p>
<p>To alleviate these problems, we compute the robot configurations by varying one actuation input and solving the inverse static model for a desired position <bold>
<italic>p</italic>
</bold>
<sub>
<italic>E</italic>
</sub> using a continuation method. The idea is to dedicate three actuation variables to maintaining the segment tip position at <bold>
<italic>p</italic>
</bold>
<sub>
<italic>E</italic>
</sub>, and to vary the fourth input to change the robot configuration and obtain different tip orientations. In particular, we vary the backbone rotation <italic>&#x3b1;</italic> as it has a major impact on the robot shape. The continuation method allows to vary <italic>&#x3b1;</italic> and to compute the corresponding set of robot configurations without relying on an a priori discretization and being sensitive to bad initial guesses. The set of robot configurations is considered as the smooth function <inline-formula id="inf50">
<mml:math id="m62">
<mml:mi mathvariant="script">B</mml:mi>
</mml:math>
</inline-formula>, called branch of solution of the inverse static model and defined as:<disp-formula id="e13">
<mml:math id="m63">
<mml:mtable class="align" columnalign="left">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:mi mathvariant="script">B</mml:mi>
<mml:mo>:</mml:mo>
<mml:mi mathvariant="double-struck">R</mml:mi>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x2192;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="double-struck">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>4</mml:mn>
<mml:mi>n</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>3</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right">
<mml:mi>&#x3b1;</mml:mi>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x21a6;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="bold-italic">X</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3bc;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x22a4;</mml:mo>
</mml:mrow>
</mml:msubsup>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mi>T</mml:mi>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mi>&#x03B3;</mml:mi>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mi>&#x3b2;</mml:mi>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x22a4;</mml:mo>
</mml:mrow>
</mml:msup>
<mml:mspace width="2em"/>
<mml:mtext>such&#x2009;that</mml:mtext>
<mml:mspace width="2em"/>
<mml:mi mathvariant="bold">G</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">X</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3bc;</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">p</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>E</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="bold-italic">u</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mn mathvariant="bold">0</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(13)</label>
</disp-formula>
</p>
<p>It is computed using a prediction and correction process. Starting from a point of the branch, the next point is predicted by incrementing the actuation input by a given step size and by taking the corresponding point along the branch local tangent <inline-formula id="inf51">
<mml:math id="m64">
<mml:mi>&#x2202;</mml:mi>
<mml:mi mathvariant="script">B</mml:mi>
<mml:mo>/</mml:mo>
<mml:mi>&#x2202;</mml:mi>
<mml:mi>&#x3b1;</mml:mi>
</mml:math>
</inline-formula>. The inverse static model is then solved, starting from the predicted configuration, using a Newton-Raphson algorithm. The step size is automatically reduced in case the numerical solver has more difficulties to converge, i.e. the number of iterations required to converge increases. The process is repeated until a specified number of points along the branch have been computed. Once the robot configurations have been found, the resulting tip orientations are computed as rotation matrices <bold>
<italic>R</italic>
</bold>
<sub>
<italic>E</italic>
</sub> using <xref ref-type="disp-formula" rid="e3">Eq. 3</xref>. The prediction-correction method is implemented in the <sc>Matlab</sc> toolbox called MatCont (<xref ref-type="bibr" rid="B12">Dhooge et al. (2008)</xref>).</p>
<p>Finally, analysing the tip orientations requires to have an intuitive representation of them. Service spheres provide such representation as demonstrated in <xref ref-type="bibr" rid="B26">Li et al. (2017)</xref>. A service sphere of a given radius <italic>r</italic>
<sub>
<italic>S</italic>
</sub> is defined, where its center is located at the robot tip position <bold>
<italic>p</italic>
</bold>
<sub>
<italic>E</italic>
</sub>. The intersection of the robot tip tangent with the service sphere creates then a point <bold>
<italic>p</italic>
</bold>
<sub>
<italic>S</italic>
</sub>, which represents the tip orientation. With forward and inverse kinematics based sampling method, the service sphere is usually discretized in a finite number of patches. The patches that contain a tip orientation point are then colored, which allows an easy visualization of the possible tip orientations and the evaluation of orientability metrics. We use the service sphere representation in this work to visualize and analyse the tip orientation of the FAS. The set of tip orientations obtained after varying <italic>&#x3b1;</italic> results in a set of consecutive points <bold>
<italic>p</italic>
</bold>
<sub>
<italic>S</italic>
</sub> on the service sphere, forming a one dimensional curve defined by:<disp-formula id="e14">
<mml:math id="m65">
<mml:mtable class="align" columnalign="left">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">p</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>S</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>:</mml:mo>
<mml:mi mathvariant="double-struck">R</mml:mi>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x2192;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="double-struck">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>3</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right">
<mml:mi>&#x3b1;</mml:mi>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x21a6;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">p</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>E</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>r</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>S</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>E</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="bold-italic">e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>z</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(14)</label>
</disp-formula>where <italic>r</italic>
<sub>
<italic>S</italic>
</sub> is the radius of the service sphere.</p>
<p>To illustrate the position redundancy of a segment with variable helical tendon routing, we conduct a reachability assessment. As before, we conduct a preliminary study with the physical FAS prototype described in <xref ref-type="sec" rid="s2-3-1">Section 2.3.1</xref>. A more in-depth study in simulation follows afterwards.</p>
</sec>
<sec id="s5-2">
<title>5.2 Preliminary Study on Position Redundancy</title>
<p>We choose two target points in the robot workspace. Their position is indicated by a blue bead (diameter 2&#xa0;mm). They lie about 58 and 51&#xa0;mm in front of the prototype, and about 51 and 37&#xa0;mm above the base of the prototype, respectively. Positions of the backbone origin, the hole for the first tendon in the base, and the projection of the point (blue bead) on the same <italic>xy</italic>-plane lies on a line, i.e. <italic>x</italic>-axis. The tendon force, the backbone rotation, and the backbone translation are then actuated manually in order to reach the target with different configurations. <xref ref-type="table" rid="T3">Table 3</xref> summarizes all the configurations, configurations 1, two and three corresponding to the first target points, and the others to the second. Their realization using the prototype with one FAS is represented in <xref ref-type="fig" rid="F9">Figure 9</xref>. Note that the tip position is the end disk position plus an offset, i.e. flagpoles with length 7&#xa0;mm.</p>
<table-wrap id="T3" position="float">
<label>TABLE 3</label>
<caption>
<p>Configurations for position redundancy assessment. The tendon tensions are indicated by the mass of the precision weights.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="left">config</th>
<th align="center">
<italic>&#x3c4;</italic>
<sub>1</sub> in g</th>
<th align="center">
<italic>&#x3c4;</italic>
<sub>2</sub> in g</th>
<th align="center">
<italic>&#x3c4;</italic>
<sub>3</sub> in g</th>
<th align="center">
<italic>&#x3b1;</italic> in rad</th>
<th align="center">
<italic>L</italic> &#x2b; <italic>&#x3b2;</italic> in mm</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">1st</td>
<td align="char" char=".">351</td>
<td align="char" char=".">1</td>
<td align="char" char=".">151</td>
<td align="center">&#x2212;2<italic>&#x3c0;</italic>/3</td>
<td align="char" char=".">76</td>
</tr>
<tr>
<td align="left">2nd</td>
<td align="char" char=".">321</td>
<td align="char" char=".">1</td>
<td align="char" char=".">1</td>
<td align="center">0</td>
<td align="char" char=".">76</td>
</tr>
<tr>
<td align="left">3rd</td>
<td align="char" char=".">351</td>
<td align="char" char=".">151</td>
<td align="char" char=".">1</td>
<td align="center">2<italic>&#x3c0;</italic>/3</td>
<td align="char" char=".">76</td>
</tr>
<tr>
<td align="left">4th</td>
<td align="char" char=".">601</td>
<td align="char" char=".">601</td>
<td align="char" char=".">1</td>
<td align="center">&#x2212;2<italic>&#x3c0;</italic>
</td>
<td align="char" char=".">60</td>
</tr>
<tr>
<td align="left">5th</td>
<td align="char" char=".">501</td>
<td align="char" char=".">401</td>
<td align="char" char=".">1</td>
<td align="center">&#x2212;<italic>&#x3c0;</italic>
</td>
<td align="char" char=".">55</td>
</tr>
<tr>
<td align="left">6th</td>
<td align="char" char=".">501</td>
<td align="char" char=".">1</td>
<td align="char" char=".">1</td>
<td align="center">0</td>
<td align="char" char=".">55</td>
</tr>
<tr>
<td align="left">7th</td>
<td align="char" char=".">501</td>
<td align="char" char=".">1</td>
<td align="char" char=".">401</td>
<td align="center">
<italic>&#x3c0;</italic>
</td>
<td align="char" char=".">55</td>
</tr>
<tr>
<td align="left">8th</td>
<td align="char" char=".">601</td>
<td align="char" char=".">1</td>
<td align="char" char=".">601</td>
<td align="center">2<italic>&#x3c0;</italic>
</td>
<td align="char" char=".">60</td>
</tr>
</tbody>
</table>
</table-wrap>
<fig id="F9" position="float">
<label>FIGURE 9</label>
<caption>
<p>Motion capabilities indicated by position redundancy. The red flag with flagpoles of 7&#xa0;mm indicates, on the one hand, the orientation of the end disk around the tangent vector of the backbone and, on the other hand, the rotation <italic>&#x3b1;</italic> of the backbone. <bold>(A)</bold> (Left column) Configurations with significant backbone rotation and negligible translation, see <xref ref-type="table" rid="T3">Table 3</xref>. (Right) Overlay of all configurations. The accompanying video provides additional visual aid. <bold>(B)</bold> More extreme configurations, requiring backbone translation.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g009.tif"/>
</fig>
<p>For the first target point, we start from configuration two and vary the backbone rotation and the tendon tension without changing the robot length. Configuration two is a pure in-plane bending in the <italic>xz</italic>-plane, where the first tendon is loaded with 3.21&#xa0;N and <italic>&#x3b1;</italic> &#x3d; 0 rad. We obtain the robot configurations 1 and 3, which lead to the same target tip position. While the robot shapes are close to each other and the tip orientation is rotated about the vertical axis of approximately &#x2212; <italic>&#x3c0;</italic>/6 rad, the tip orientation varies significantly from &#x2212; 2<italic>&#x3c0;</italic>/3 rad to 2<italic>&#x3c0;</italic>/3 rad. For the second target point, we start from configuration six which is again a pure in-plane bending in the <italic>xz</italic>-plane. The backbone is rotated with larger values, ranging from <italic>&#x3b1;</italic> &#x3d; &#xb1;2<italic>&#x3c0;</italic> rad. As a result, the backbone must be translated to reach the target point, leading to configurations four to 8. Position redundancy is achieved while obtaining robot configurations with significant variations of tip orientation.</p>
<p>From the preliminary study with FAS prototype, we can conclude that the additional dof of the design greatly contribute to the position redundancy of the design. The dof for the extension of the segment has a negligible contribution for small values of <italic>&#x3b1;</italic>. However, leveraging <italic>&#x3b2;</italic> leads to a higher variation of <italic>&#x3b1;</italic>, and therefore to higher variations of robot shapes and tip orientations. Further, note that neither a non-extensible segment, which can only bend, nor an extensible segment, which can bend and elongate, exhibit position redundancy. In addition, note that the workspace of a non-extensible segment is a curved plane in the task space. Hence, a point on this curved plane can be reached with the FAS with different tendon tensions <italic>&#x3c4;</italic>
<sub>
<italic>i</italic>
</sub> and a high variety of <italic>&#x3b1;</italic>, while <italic>&#x3b2;</italic> has a minor contribution.</p>
</sec>
<sec id="s5-3">
<title>5.3 Analysis of Position Redundancy in Simulation</title>
<p>We investigate numerically the FAS redundancy at three positions in its workspace. Making use of the symmetry in the robot workspace, we select three different planar configurations obtained by pulling on the first tendon, shown in <xref ref-type="fig" rid="F10">Figure 10A</xref>. We consider that the frictional and gravitational forces are negligible, an assumption that we relax later on. The one-dimensional curve <bold>
<italic>p</italic>
</bold>
<sub>
<italic>S</italic>
</sub>(<italic>&#x3b1;</italic>) on the service sphere is computed with the continuation process for <italic>&#x3b1;</italic> &#x2208; [ &#x2212; <italic>&#x3c0;</italic>, <italic>&#x3c0;</italic>]. For each configuration, the corresponding service spheres have been depicted in <xref ref-type="fig" rid="F10">Figures 10B&#x2013;D</xref>.</p>
<fig id="F10" position="float">
<label>FIGURE 10</label>
<caption>
<p>Position redundancy evaluated for three positions for a FAS segment. <bold>(A)</bold> Three configurations considered for evaluation. The service sphere is plotted for configuration one in red <bold>(B)</bold>, two in blue <bold>(C)</bold>, and three in black <bold>(D)</bold>. Friction coefficient is assumed to be zero.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g010.tif"/>
</fig>
<p>We obtain sets of helical robot configurations, as expected, that draw a circular curve on the service sphere. The center of this circle and its radius give indications about the main rotation axis of the segment at the target tip position and the angular displacement achieved around this axis respectively. We observe that the higher the initial curvature of the segment, the larger the disk radius and the angular displacement. We also observe that these large range of orientations are obtained with significant backbone rotations and small backbone translation. The evolution of the segment length with <italic>&#x3b1;</italic> during the continuation process is plotted in <xref ref-type="fig" rid="F11">Figure 11</xref> for the corresponding three configurations displayed in <xref ref-type="fig" rid="F10">Figure 10B</xref>. We see that the variation in length is in the millimeter range, which aligns with the observations made in the preliminary study. It is interesting to note that these circular curves are not closed-curves. The same point on the service sphere, or a same tip orientation, can be approached using different set of actuation inputs and different robot configurations. Consequently, a specific property of the FAS is to be able to achieve the same tip position and tip tangent with different and discrete values of tip axial rotations, which coincides with the preliminary study.</p>
<fig id="F11" position="float">
<label>FIGURE 11</label>
<caption>
<p>Variation in redundant robot configurations <bold>(A)</bold> Sparse redundant configurations with <italic>&#x3bc;</italic> &#x3d; 0.3, for the same tensions considered in <xref ref-type="fig" rid="F10">Figure 10</xref> <bold>(B)</bold> Plot of variation in length of the backbone with <italic>&#x3b1;</italic>. The dashed lines represent the plots for <italic>&#x3bc;</italic> &#x3d; 0.3 and solid lines for <italic>&#x3bc;</italic> &#x3d; 0.</p>
</caption>
<graphic xlink:href="frobt-09-873446-g011.tif"/>
</fig>
<p>Finally, we briefly investigate the influence of friction as they have been observed to have a significant effect on the segment shape. The changes of segment length during the backbone rotation and when considering friction are plotted with dashed lines in <xref ref-type="fig" rid="F11">Figure 11</xref>. We observe that the changes in length is larger for configurations one and two when friction is considered to be non-zero compared to the frictionless case, while the opposite trend is observed for configuration 3. The different trends are observed due to the difference in backbone configurations, occurring due to presence of friction.</p>
</sec>
</sec>
<sec id="s6">
<title>6 Discussion and Perspectives</title>
<p>The FAS design has been shown effective to obtain a TDCR segment with four&#x2009;dof including bending, extension, and twisting. Our initial results show that utilizing twisting as a dof has a beneficial impact on the motion capabilities of a TDCR. To back up our hypothesis, we highlight the capability of the proposed design by qualitatively and quantitatively study its merit through different assessments. The assessments are performed with one of the two physical prototypes and accompanying validations in simulation with the proposed model provide additional insights. In the following, we briefly discuss on the FAS design and then its inherent FTL deployment capability as well as its quantification. Further, we discuss the position redundancy and the static model. Each discussion point is accompanied with promising future directions.</p>
<sec id="s6-1">
<title>6.1 Design of the FAS</title>
<p>All dof can be actuated independently in an extrinsic manner. In addition, our proposed design is simpler than the prototypes presented in <xref ref-type="bibr" rid="B37">Starke et al. (2017)</xref> and <xref ref-type="bibr" rid="B16">Gerboni et al. (2015)</xref>, which involve to combine helical and straight tendons and then may lead to complex tendon routing, especially if several segments are stacked. Special care needs to be taken for the friction between FSD and tendons. On top of that, the use of magnets in type-III FSD introduces new challenges regarding modelling the orientation and position of each FSD. Further, the repulsion forces decrease rapidly as the robot extends, limiting the robot&#x2019;s maximum length. While the magnetic repulsion force can be improved by increasing the magnet&#x2019;s thickness, it would in turn limit the robot miniaturization and increase its weight. Among other improvements, finding an alternative to magnets is a future direction to revise the current design.</p>
</sec>
<sec id="s6-2">
<title>6.2 FTL Deployment Capabilities</title>
<p>We start with a fairly simple deployment strategy, i.e. constant tendon tension and backbone rotation while deploying the backbone. For the preliminary study, the resulting errors are in the range of inaccuracies of the used physical FAS prototype and comparable with the extensible segment TDCR (<xref ref-type="bibr" rid="B3">Amanov et al., 2019</xref>, <xref ref-type="bibr" rid="B2">2016</xref>) provided that the deployment length and backbone rotation are small. Note that even in the case of not perfectly distributed FSD along the backbone as can be seen in <xref ref-type="fig" rid="F7">Figure 7A</xref> the resulting errors are sufficiently small. Also note that these are valid postures as this assessment is for FTL use and independent of the model evaluation. In simulation, we show that the deployment strategy needs to be adapted to achieve perfect FTL deployment. The deployment is slightly modified, resulting in a constant tendon tensions with linear change in the backbone rotation and deployment. Indeed, as the backbone must have a constant torsional curvature during the deployment, the angle of the backbone base rotation <italic>&#x3b1;</italic> must be varied linearly w.r.t. the arc-length <italic>s</italic>. While on the one hand this can be seen as a limitation, on the other hand it can be used for FTL deployment strategies in future work.</p>
<p>Another key element to ensure perfect FTL deployment with a TDCR is to include more FSDs. The more FSDs, the closer the TDCR&#x2019;s tendons to be fully constrained, see <xref ref-type="bibr" rid="B34">Rao et al. (2021)</xref> for a discussion on partially and fully constrained tendon paths. In simulation, we have found that perfect FTL deployment can be achieved with 70 FSDs. Also, slight discrepancies between the robot shape and the reference path are observed when 10 FSDs are used.</p>
</sec>
<sec id="s6-3">
<title>6.3 Area-Based FTL Error</title>
<p>In the literature, FTL deployments are quantified by repeatedly measuring the robot shape during the deployment. In <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref> and <xref ref-type="bibr" rid="B14">Garriga-Casanovas and Rodriguez y Baena (2018a)</xref>, a 3D laser scanner is used to obtain a spatial point cloud of the robot. Afterwards, the centerline of the robot&#x2019;s backbone is extracted relying on a thinning algorithm or on a model of a backbone. Downsides of this labor-intensive approach lie in the use of dedicated hardware and point cloud post-processing.</p>
<p>In contrast, the proposed area-based FTL error (11) is easy to evaluate, interpret, and visualize. The evaluation can be realized with binary images after segmentation and using a simple threshold after combining several binary images as well as summing up all occupied pixels in the respective images. The value can be interpreted as percentage of the normalized surplus of the occupied area during the FTL deployment. Lastly (11) can be visualized as shown in <xref ref-type="fig" rid="F7">Figure 7</xref>. Nevertheless, sources for uncertainty are the manual image segmentation, the low discrete steps, and the dependency of the view. These issues could be alleviated by substituting the manual approach with a learning-based approach enabling an online multi-view evaluation of an FTL deployment. This will be the subject of future work.</p>
<p>Note that an area-based accuracy assessment is used in <xref ref-type="bibr" rid="B10">Chikhaoui et al. (2019)</xref> to compare two modeling approaches for a TDCR by projecting a measured point cloud onto several planes. In <xref ref-type="bibr" rid="B19">Girerd et al. (2020)</xref>, superposition of all intermediate shapes of a CTCR is used to highlight the approximate FTL deployment. A similar approach is utilized in <xref ref-type="bibr" rid="B3">Amanov et al. (2019</xref>, <xref ref-type="bibr" rid="B2">2016)</xref>, where the overall occupied space over the course of deployment is used to visually show the feasibility. However, none of these qualitative approaches are used to quantify an FTL deployment.</p>
</sec>
<sec id="s6-4">
<title>6.4 Position Redundancy</title>
<p>Thanks to the four&#x2009;dof, one segment alone already shows interesting properties such as position redundancy as indicated in <xref ref-type="fig" rid="F9">Figure 9</xref> and <xref ref-type="fig" rid="F10">Figure 10</xref>. Interestingly, the overlaid images shown in <xref ref-type="fig" rid="F9">Figure 9</xref> and <xref ref-type="fig" rid="F11">Figure 11</xref> expose that the change in orientation of the end disk is high in comparison to the shape deviation. Note that the segment length has a minor influence on the position redundancy, while <italic>&#x3b1;</italic> and <italic>&#x3b8;</italic>, respectively, has a major impact as indicated in <xref ref-type="fig" rid="F9">Figure 9</xref> and <xref ref-type="fig" rid="F11">Figure 11</xref>. The workspace of a TDCR with only two&#x2009;dof, i.e. <italic>&#x3ba;</italic>
<sub>
<italic>x</italic>
</sub> and <italic>&#x3ba;</italic>
<sub>
<italic>y</italic>
</sub>, is a two dimensional manifold. Therefore, a position on this manifold can be reached with different tip orientations, where <italic>&#x3b1;</italic> has a significant contribution. The position redundancy also known as orientability is higher for higher tendon tension as shown in <xref ref-type="fig" rid="F10">Figure 10</xref>. Further, the combined applied tendon tensions are higher for the out-of-plane bending compared to the in-plane bending, see <xref ref-type="table" rid="T3">Table 3</xref>. Leveraging orientability capability for dynamic obstacle avoidance and for motion planning are promising future research directions.</p>
</sec>
<sec id="s6-5">
<title>6.5 Static Model of a FAS</title>
<p>During the preliminary study with the physical prototypes, we observed hysteresis behaviours, with velocity-dependent and bending-dependent configurations. We tried to mitigate those phenomena by using multiple measurements via a tactile device to induce noise and reduce measurement biases. The derived static model is calibrated to account for unmodeled effects. It achieves a reasonable accuracy, i.e. average tip error of 4.00&#xa0;mm corresponding to a relative tip error of 4.39%, compared to 4.10&#xa0;mm (1.7%) reported for a Cosserat rod-based approach in (<xref ref-type="bibr" rid="B35">Rucker and Webster, 2011</xref>). The assumptions of equidistant disk spacing and linear rotation distribution along the backbone are shown to be reasonable approximations. However, they are sources of error for the static model. Specifically modeling the inter-magnetic forces in magnetic spacer disks, and the influence of tendon actuation on the rotation distribution, should be investigated in future work. Additionally, more specific mechanics-based modelling approaches, e.g. (<xref ref-type="bibr" rid="B35">Rucker and Webster, 2011</xref>; <xref ref-type="bibr" rid="B10">Chikhaoui et al., 2019</xref>), can be adapted for the FAS design and then used to estimate the workspace including position redundancy measures based on (<xref ref-type="bibr" rid="B7">Burgner-Kahrs et al., 2014</xref>; <xref ref-type="bibr" rid="B40">Wu et al., 2017</xref>) or to extend the FTL deployment strategy proposed by <xref ref-type="bibr" rid="B30">Neumann and Burgner-Kahrs (2016)</xref>; <xref ref-type="bibr" rid="B3">Amanov et al. (2019)</xref> to tendon tension.</p>
<p>In addition to extending the current static model and exploring a dynamic model, developing a kinematic model, which allows to investigate the redundancy, is desirable. This is motivated by an interesting fact stated by <xref ref-type="bibr" rid="B15">Garriga-Casanovas and Rodriguez y Baena (2018b)</xref>: An extensible TDCR with six&#x2009;dof in the arc space is only capable of five&#x2009;dof at the end effector in the task space due to a loss in rank of the Jacobian matrix for the velocity mapping. Due to the high impact of a geometric twist angle on the orientability, using a FAS might provide a viable solution. Using two concatenated segments provides eight&#x2009;dof in the arc space and could be used to mitigate the above problem.</p>
</sec>
</sec>
<sec id="s7">
<title>7 Conclusion</title>
<p>We propose a fully actuated segment (FAS) design for tendon-driven continuum robots, which features extensibility and variable tendon routing produced by twist. The actuated twist is implemented by reconsidering spacer disks and leveraging a design of a concentric tube continuum robot. Variable segment lengths are achieved by translating the robot backbone and by using floating spacer disks. Variable tendon routing is achieved by a simple yet effective mechanism to rotate the backbone. As a consequence, the design exploits four dof for one segment; bending in two planes, translation, and rotation. Thanks to the extrinsic actuation, it is a light-weight and slender segment.</p>
<p>The design is qualitatively verified with physical prototypes and further quantitatively validated in simulation with a proposed static model. We demonstrate that a prototype composed of one segment generates helical tendon routing and exhibits position redundancy, which is not possible with previous designs. We also show with a physical prototype and in simulation that it can achieve accurate FTL deployments along planar and complex helical-like paths, the last ones being enabled by the actuated twist. For both paths, we show that the strategy for FTL deployment is fairly simple. Further, we show in simulation the higher the number of spacer disks, the higher the accuracy of an FTL deployment. In addition, we proposed an error measure for FTL deployments and assessed deployment capabilities.</p>
<p>Overall, we prove our hypothesis that utilizing all degrees of freedom has a significant impact on the motion capabilities and, therefore, on the FTL deployment, as well as on position and orientation capabilities. Although our results are preliminary, we believe that the FAS design provides a rich source for future work and has potential in medical and <italic>in situ</italic> inspection applications.</p>
</sec>
</body>
<back>
<sec id="s8">
<title>Data Availability Statement</title>
<p>The raw data supporting the conclusion of this article will be made available by the authors at <ext-link ext-link-type="uri" xlink:href="https://github.com/ContinuumRoboticsLab">https://github.com/ContinuumRoboticsLab</ext-link>.</p>
</sec>
<sec id="s9">
<title>Author Contributions</title>
<p>RMG worked on a major part of paper writing as well as conceptualizing and designing the mechanism and physical prototypes. He was responsible for designing and evaluating the case studies with the prototypes. PR worked on developing and calibrating the model and using it to analyze the proposed mechanism. She also generated the numerical results presented in the FTL deployment and position redundancy studies. QP was responsible for developing the continuation-based numerical tools used for the simulations. RMG, PR and QP designed the FTL deployment and position redundancy study in simulation. JB-K is the senior author of this paper. She conceptualized, advised, and regularly discussed research questions and results with all authors. She edited the paper. All authors were concerned with conceptualizing and revising the paper through regular discussions on the theory and implementation details.</p>
</sec>
<sec sec-type="COI-statement" id="s10">
<title>Conflict of Interest</title>
<p>The authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec sec-type="disclaimer" id="s11">
<title>Publisher&#x2019;s Note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<ack>
<p>We would like to thank Ernar Amanov, Sven Lilge, and Thien-Dang Nguyen for general discussion about this topic that have greatly inspired the course of this research. We acknowledge the support of the Natural Sciences and Engineering Research Council of Canada (NSERC), (RGPIN-2019-04846).</p>
</ack>
<sec id="s12">
<title>Supplementary Material</title>
<p>The Supplementary Material for this article can be found online at: <ext-link ext-link-type="uri" xlink:href="https://www.frontiersin.org/articles/10.3389/frobt.2022.873446/full#supplementary-material">https://www.frontiersin.org/articles/10.3389/frobt.2022.873446/full&#x23;supplementary-material</ext-link>
</p>
<supplementary-material xlink:href="Video1.MP4" id="SM1" mimetype="application/MP4" xmlns:xlink="http://www.w3.org/1999/xlink"/>
</sec>
<ref-list>
<title>References</title>
<ref id="B1">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Amanov</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Granna</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2017</year>). &#x201c;<article-title>Toward Improving Path Following Motion: Hybrid Continuum Robot Design</article-title>,&#x201d; in <conf-name>IEEE International Conference on Robotics and Automation</conf-name>, <fpage>4666</fpage>&#x2013;<lpage>4672</lpage>. <pub-id pub-id-type="doi">10.1109/icra.2017.7989542</pub-id> </citation>
</ref>
<ref id="B2">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Amanov</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Nguyen</surname>
<given-names>T.-D.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2016</year>). &#x201c;<article-title>Metabot-magnetic Extensible Tendon Actuated Continuum Robot</article-title>,&#x201d; in <conf-name>DGR Days (German Society of Robotics)</conf-name>. </citation>
</ref>
<ref id="B3">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Amanov</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Nguyen</surname>
<given-names>T.-D.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Tendon-driven Continuum Robots with Extensible Sections &#x2013; a Model-Based Evaluation of Path-Following Motions</article-title>. <source>Int. J. Robotics Res.</source> </citation>
</ref>
<ref id="B4">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Barreiros</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>O&#x2019;Brien</surname>
<given-names>K. W.</given-names>
</name>
<name>
<surname>Hong</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Xiao</surname>
<given-names>M. F.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>H.-J.</given-names>
</name>
<name>
<surname>Shepherd</surname>
<given-names>R. F.</given-names>
</name>
</person-group> (<year>2019</year>). &#x201c;<article-title>Configurable Tendon Routing in a 3d-Printed Soft Actuator for Improved Locomotion in a Multi-Legged Robot</article-title>,&#x201d; in <conf-name>IEEE International Conference on Soft Robotics</conf-name>, <fpage>94</fpage>&#x2013;<lpage>101</lpage>. <pub-id pub-id-type="doi">10.1109/robosoft.2019.8722801</pub-id> </citation>
</ref>
<ref id="B5">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Bergstra</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Bengio</surname>
<given-names>Y.</given-names>
</name>
</person-group> (<year>2012</year>). <article-title>Random Search for Hyper-Parameter Optimization</article-title>. <source>J. machine Learn. Res.</source> <volume>13</volume>, <fpage>281</fpage>&#x2013;<lpage>305</lpage>. </citation>
</ref>
<ref id="B6">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Blessing</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Walker</surname>
<given-names>I. D.</given-names>
</name>
</person-group> (<year>2004</year>). <article-title>Novel Continuum Robots with Variable-Length Sections</article-title>. <source>IFAC Proc. Volumes</source> <volume>37</volume>, <fpage>55</fpage>&#x2013;<lpage>60</lpage>. <pub-id pub-id-type="doi">10.1016/s1474-6670(17)31080-7</pub-id> </citation>
</ref>
<ref id="B7">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Gilbert</surname>
<given-names>H. B.</given-names>
</name>
<name>
<surname>Granna</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Swaney</surname>
<given-names>P. J.</given-names>
</name>
<name>
<surname>Webster</surname>
<given-names>R. J.</given-names>
</name>
</person-group> (<year>2014</year>). &#x201c;<article-title>Workspace Characterization for Concentric Tube Continuum Robots</article-title>,&#x201d; in <conf-name>IEEE/RSJ International Conference on Intelligent Robots and Systems</conf-name>, <fpage>12691275</fpage>. <pub-id pub-id-type="doi">10.1109/iros.2014.6942720</pub-id> </citation>
</ref>
<ref id="B8">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Rucker</surname>
<given-names>D. C.</given-names>
</name>
<name>
<surname>Choset</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2015</year>). <article-title>Continuum Robots for Medical Applications: A Survey</article-title>. <source>IEEE Trans. Robot.</source> <volume>31</volume>, <fpage>1261</fpage>&#x2013;<lpage>1280</lpage>. <pub-id pub-id-type="doi">10.1109/tro.2015.2489500</pub-id> </citation>
</ref>
<ref id="B9">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Camarillo</surname>
<given-names>D. B.</given-names>
</name>
<name>
<surname>Milne</surname>
<given-names>C. F.</given-names>
</name>
<name>
<surname>Carlson</surname>
<given-names>C. R.</given-names>
</name>
<name>
<surname>Zinn</surname>
<given-names>M. R.</given-names>
</name>
<name>
<surname>Salisbury</surname>
<given-names>J. K.</given-names>
</name>
</person-group> (<year>2008</year>). <article-title>Mechanics Modeling of Tendon-Driven Continuum Manipulators</article-title>. <source>IEEE Trans. Robot.</source> <volume>24</volume>, <fpage>1262</fpage>&#x2013;<lpage>1273</lpage>. <pub-id pub-id-type="doi">10.1109/tro.2008.2002311</pub-id> </citation>
</ref>
<ref id="B10">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chikhaoui</surname>
<given-names>M. T.</given-names>
</name>
<name>
<surname>Lilge</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Kleinschmidt</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Comparison of Modeling Approaches for a Tendon Actuated Continuum Robot with Three Extensible Segments</article-title>. <source>IEEE Robot. Autom. Lett.</source> <volume>4</volume>, <fpage>989</fpage>&#x2013;<lpage>996</lpage>. <pub-id pub-id-type="doi">10.1109/lra.2019.2893610</pub-id> </citation>
</ref>
<ref id="B11">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Coxeter</surname>
<given-names>H. S. M.</given-names>
</name>
</person-group> (<year>1968</year>). <article-title>The Problem of Apollonius</article-title>. <source>The Am. Math. Monthly</source> <volume>75</volume>, <fpage>5</fpage>&#x2013;<lpage>15</lpage>. <pub-id pub-id-type="doi">10.1080/00029890.1968.11970941</pub-id> </citation>
</ref>
<ref id="B12">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Dhooge</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Govaerts</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Kuznetsov</surname>
<given-names>Y. A.</given-names>
</name>
<name>
<surname>Meijer</surname>
<given-names>H. G. E.</given-names>
</name>
<name>
<surname>Sautois</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2008</year>). <article-title>New Features of the Software MatContfor Bifurcation Analysis of Dynamical Systems</article-title>. <source>Math. Comput. Model. Dynamical Syst.</source> <volume>14</volume>, <fpage>147</fpage>&#x2013;<lpage>175</lpage>. <pub-id pub-id-type="doi">10.1080/13873950701742754</pub-id> </citation>
</ref>
<ref id="B13">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Gao</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Takagi</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Kato</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Shono</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Hata</surname>
<given-names>N.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Continuum Robot with Follow-The-Leader Motion for Endoscopic Third Ventriculostomy and Tumor Biopsy</article-title>. <source>IEEE Trans. Biomed. Eng.</source> <volume>67</volume>, <fpage>379</fpage>&#x2013;<lpage>390</lpage>. <pub-id pub-id-type="doi">10.1109/TBME.2019.2913752</pub-id> </citation>
</ref>
<ref id="B14">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Garriga-Casanovas</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Rodriguez y Baena</surname>
<given-names>F.</given-names>
</name>
</person-group> (<year>2018a</year>). <article-title>Complete Follow-The-Leader Kinematics Using Concentric Tube Robots</article-title>. <source>Int. J. Robotics Res.</source> <volume>37</volume>, <fpage>197</fpage>&#x2013;<lpage>222</lpage>. <pub-id pub-id-type="doi">10.1177/0278364917746222</pub-id> </citation>
</ref>
<ref id="B15">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Garriga-Casanovas</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Rodriguez y Baena</surname>
<given-names>F.</given-names>
</name>
</person-group> (<year>2018b</year>). <article-title>Kinematics of Continuum Robots with Constant Curvature Bending and Extension Capabilities</article-title>. <source>J. Mech. Robotics</source> <volume>11</volume>, <fpage>739</fpage>. <pub-id pub-id-type="doi">10.1115/1.4041739</pub-id> </citation>
</ref>
<ref id="B16">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Gerboni</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Henselmans</surname>
<given-names>P. W. J.</given-names>
</name>
<name>
<surname>Arkenbout</surname>
<given-names>E. A.</given-names>
</name>
<name>
<surname>Furth</surname>
<given-names>W. R. v.</given-names>
</name>
<name>
<surname>Breedveld</surname>
<given-names>P.</given-names>
</name>
</person-group> (<year>2015</year>). <article-title>HelixFlex : Bioinspired Maneuverable Instrument for Skull Base Surgery</article-title>. <source>Bioinspir. Biomim.</source> <volume>10</volume>, <fpage>066013</fpage>. <pub-id pub-id-type="doi">10.1088/1748-3190/10/6/066013</pub-id> </citation>
</ref>
<ref id="B17">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Gilbert</surname>
<given-names>H. B.</given-names>
</name>
<name>
<surname>Rucker</surname>
<given-names>D. C.</given-names>
</name>
<name>
<surname>Webster</surname>
<given-names>R. J.</given-names>
<suffix>III</suffix>
</name>
</person-group> (<year>2016</year>). &#x201c;<article-title>Concentric Tube Robots: The State of the Art and Future Directions</article-title>,&#x201d; in <source>Robotics Research</source> (<publisher-loc>Berlin, Germany</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>253</fpage>&#x2013;<lpage>269</lpage>. <pub-id pub-id-type="doi">10.1007/978-3-319-28872-7_15</pub-id> </citation>
</ref>
<ref id="B18">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Gilbert</surname>
<given-names>H. B.</given-names>
</name>
<name>
<surname>Webster</surname>
<given-names>R. J.</given-names>
</name>
</person-group> (<year>2013</year>). &#x201c;<article-title>Can Concentric Tube Robots Follow the Leader?</article-title>,&#x201d; in <conf-name>IEEE International Conference on Robotics and Automation</conf-name>, <fpage>4881</fpage>&#x2013;<lpage>4887</lpage>. </citation>
</ref>
<ref id="B19">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Girerd</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Kudryavtsev</surname>
<given-names>A. V.</given-names>
</name>
<name>
<surname>Rougeot</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Renaud</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Rabenorosoa</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Tamadazte</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2020</year>). <article-title>Slam-based Follow-The-Leader Deployment of Concentric Tube Robots</article-title>. <source>IEEE Robot. Autom. Lett.</source> <volume>5</volume>, <fpage>548</fpage>&#x2013;<lpage>555</lpage>. <pub-id pub-id-type="doi">10.1109/lra.2019.2963821</pub-id> </citation>
</ref>
<ref id="B20">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Goldman</surname>
<given-names>R. E.</given-names>
</name>
<name>
<surname>Bajo</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>MacLachlan</surname>
<given-names>L. S.</given-names>
</name>
<name>
<surname>Pickens</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Herrell</surname>
<given-names>S. D.</given-names>
</name>
<name>
<surname>Simaan</surname>
<given-names>N.</given-names>
</name>
</person-group> (<year>2013</year>). <article-title>Design and Performance Evaluation of a Minimally Invasive Telerobotic Platform for Transurethral Surveillance and Intervention</article-title>. <source>IEEE Trans. Biomed. Eng.</source> <volume>60</volume>, <fpage>918</fpage>&#x2013;<lpage>925</lpage>. <pub-id pub-id-type="doi">10.1109/TBME.2012.2226031</pub-id> </citation>
</ref>
<ref id="B21">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Grassmann</surname>
<given-names>R. M.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2019</year>). &#x201c;<article-title>On the Merits of Joint Space and Orientation Representations in Learning the Forward Kinematics in SE(3)</article-title>,&#x201d; in <conf-name>Proceedings of Robotics: Science and Systems</conf-name>. <pub-id pub-id-type="doi">10.15607/rss.2019.xv.017</pub-id> </citation>
</ref>
<ref id="B22">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Grassmann</surname>
<given-names>R. M.</given-names>
</name>
<name>
<surname>Lilge</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Le</surname>
<given-names>P. H.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2020</year>). &#x201c;<article-title>CTCR Prototype Development: An Obstacle in the Research Community?</article-title>,&#x201d; in <conf-name>Robotics: Science and Systems, Workshop on Robotics Retrospectives</conf-name>. </citation>
</ref>
<ref id="B23">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kang</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Kojcev</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Sinibaldi</surname>
<given-names>E.</given-names>
</name>
</person-group> (<year>2016</year>). <article-title>The First Interlaced Continuum Robot, Devised to Intrinsically Follow the Leader</article-title>. <source>PLOS ONE</source> <volume>11</volume>, <fpage>e0150278</fpage>&#x2013;<lpage>16</lpage>. <pub-id pub-id-type="doi">10.1371/journal.pone.0150278</pub-id> </citation>
</ref>
<ref id="B24">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Lastinger</surname>
<given-names>M. C.</given-names>
</name>
<name>
<surname>Verma</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Kapadia</surname>
<given-names>A. D.</given-names>
</name>
<name>
<surname>Walker</surname>
<given-names>I. D.</given-names>
</name>
</person-group> (<year>2019</year>). &#x201c;<article-title>Tree: a Variable Topology, Branching Continuum Robot</article-title>,&#x201d; in <conf-name>International Conference on Robotics and Automation</conf-name> (<publisher-loc>Montreal, QC, Canada</publisher-loc>: <publisher-name>IEEE</publisher-name>), <fpage>5365</fpage>&#x2013;<lpage>5371</lpage>. <pub-id pub-id-type="doi">10.1109/icra.2019.8794463</pub-id> </citation>
</ref>
<ref id="B25">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Li</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Tsai</surname>
<given-names>Y.-Y.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>G.-Z.</given-names>
</name>
<name>
<surname>Lo</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2020</year>). &#x201c;<article-title>A Novel Endoscope Design Using Spiral Technique for Robotic-Assisted Endoscopy Insertion</article-title>,&#x201d; in <conf-name>IEEE/RSJ International Conference on Intelligent Robots and Systems</conf-name>, <fpage>3119</fpage>&#x2013;<lpage>3124</lpage>. <pub-id pub-id-type="doi">10.1109/iros45743.2020.9340975</pub-id> </citation>
</ref>
<ref id="B26">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Li</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Wu</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Ren</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Yu</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Kinematic Comparison of Surgical Tendon-Driven Manipulators and Concentric Tube Manipulators</article-title>. <source>Mechanism Machine Theor.</source> <volume>107</volume>, <fpage>148</fpage>&#x2013;<lpage>165</lpage>. <pub-id pub-id-type="doi">10.1016/j.mechmachtheory.2016.09.018</pub-id> </citation>
</ref>
<ref id="B27">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Mahoney</surname>
<given-names>A. W.</given-names>
</name>
<name>
<surname>Gilbert</surname>
<given-names>H. B.</given-names>
</name>
<name>
<surname>Webster</surname>
<given-names>R. J.</given-names>
<suffix>III</suffix>
</name>
</person-group> (<year>2016</year>). &#x201c;<article-title>A Review of Concentric Tube Robots: Modeling, Control, Design, Planning, and Sensing</article-title>,&#x201d; in <conf-name>Encyclopedia of Medical Robotics, Minimally Invasive Surgical Robotics</conf-name>. </citation>
</ref>
<ref id="B28">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Mishra</surname>
<given-names>A. K.</given-names>
</name>
<name>
<surname>Del Dottore</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Sadeghi</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Mondini</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Mazzolai</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Simba: Tendon-Driven Modular Continuum Arm with Soft Reconfigurable Gripper</article-title>. <source>Front. Robot. AI</source> <volume>4</volume>, <fpage>4</fpage>. <pub-id pub-id-type="doi">10.3389/frobt.2017.00004</pub-id> </citation>
</ref>
<ref id="B29">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Moll</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Kavraki</surname>
<given-names>L.</given-names>
</name>
</person-group> (<year>2004</year>). &#x201c;<article-title>Path Planning for Minimal Energy Curves of Constant Length</article-title>,&#x201d; in <conf-name>IEEE International Conference on Robotics and Automation. vol. 3</conf-name>, <fpage>2826</fpage>&#x2013;<lpage>2831</lpage>. <pub-id pub-id-type="doi">10.1109/robot.2004.1307489</pub-id> </citation>
</ref>
<ref id="B30">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Neumann</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2016</year>). &#x201c;<article-title>Considerations for Follow-The-Leader Motion of Extensible Tendon-Driven Continuum Robots</article-title>,&#x201d; in <conf-name>IEEE International Conference on Robotics and Automation</conf-name>, <fpage>917</fpage>&#x2013;<lpage>923</lpage>. <pub-id pub-id-type="doi">10.1109/icra.2016.7487223</pub-id> </citation>
</ref>
<ref id="B31">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Nguyen</surname>
<given-names>T.-D.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2015</year>). &#x201c;<article-title>A Tendon-Driven Continuum Robot with Extensible Sections</article-title>,&#x201d; in <conf-name>IEEE/RSJ International Conference on Intelligent Robots and Systems</conf-name>, <fpage>2130</fpage>&#x2013;<lpage>2135</lpage>. <pub-id pub-id-type="doi">10.1109/iros.2015.7353661</pub-id> </citation>
</ref>
<ref id="B32">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Oliver-Butler</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Till</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Rucker</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Continuum Robot Stiffness under External Loads and Prescribed Tendon Displacements</article-title>. <source>IEEE Trans. Robot.</source> <volume>35</volume>, <fpage>403</fpage>&#x2013;<lpage>419</lpage>. <pub-id pub-id-type="doi">10.1109/tro.2018.2885923</pub-id> </citation>
</ref>
<ref id="B33">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Palmer</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Cobos-Guzman</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Axinte</surname>
<given-names>D.</given-names>
</name>
</person-group> (<year>2014</year>). <article-title>Real-time Method for Tip Following Navigation of Continuum Snake Arm Robots</article-title>. <source>Robotics Autonomous Syst.</source> <volume>62</volume>, <fpage>1478</fpage>&#x2013;<lpage>1485</lpage>. <pub-id pub-id-type="doi">10.1016/j.robot.2014.05.013</pub-id> </citation>
</ref>
<ref id="B34">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Rao</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Peyron</surname>
<given-names>Q.</given-names>
</name>
<name>
<surname>Lilge</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>How to Model Tendon-Driven Continuum Robots and Benchmark Modelling Performance</article-title>. <source>Front. Robotics AI</source> <volume>7</volume>, <fpage>223</fpage>. <pub-id pub-id-type="doi">10.3389/frobt.2020.630245</pub-id> </citation>
</ref>
<ref id="B35">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Rucker</surname>
<given-names>D. C.</given-names>
</name>
<name>
<surname>Webster</surname>
<given-names>R. J.</given-names>
<suffix>III</suffix>
</name>
</person-group> (<year>2011</year>). <article-title>Statics and Dynamics of Continuum Robots with General Tendon Routing and External Loading</article-title>. <source>IEEE Trans. Robot.</source> <volume>27</volume>, <fpage>1033</fpage>&#x2013;<lpage>1044</lpage>. <pub-id pub-id-type="doi">10.1109/tro.2011.2160469</pub-id> </citation>
</ref>
<ref id="B36">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Simaan</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Kai Xu</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Wei Wei</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Kapoor</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Kazanzides</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Taylor</surname>
<given-names>R.</given-names>
</name>
<etal/>
</person-group> (<year>2009</year>). <article-title>Design and Integration of a Telerobotic System for Minimally Invasive Surgery of the Throat</article-title>. <source>Int. J. Robotics Res.</source> <volume>28</volume>, <fpage>1134</fpage>&#x2013;<lpage>1153</lpage>. <pub-id pub-id-type="doi">10.1177/0278364908104278</pub-id> </citation>
</ref>
<ref id="B37">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Starke</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Amanov</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Chikhaoui</surname>
<given-names>M. T.</given-names>
</name>
<name>
<surname>Burgner-Kahrs</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2017</year>). &#x201c;<article-title>On the Merits of Helical Tendon Routing in Continuum Robots</article-title>,&#x201d; in <conf-name>IEEE/RSJ International Conference on Intelligent Robots and Systems</conf-name>, <fpage>6470</fpage>&#x2013;<lpage>6476</lpage>. <pub-id pub-id-type="doi">10.1109/iros.2017.8206554</pub-id> </citation>
</ref>
<ref id="B38">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Visentin</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Mishra</surname>
<given-names>A. K.</given-names>
</name>
<name>
<surname>Naselli</surname>
<given-names>G. A.</given-names>
</name>
<name>
<surname>Mazzolai</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2019</year>). &#x201c;<article-title>Simplified Sensing and Control of a Plant-Inspired cable Driven Manipulator</article-title>,&#x201d; in <conf-name>IEEE International Conference on Soft Robotics</conf-name>, <fpage>422</fpage>&#x2013;<lpage>427</lpage>. <pub-id pub-id-type="doi">10.1109/robosoft.2019.8722729</pub-id> </citation>
</ref>
<ref id="B39">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Walker</surname>
<given-names>I. D.</given-names>
</name>
<name>
<surname>Carreras</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>McDonnell</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Grimes</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2006</year>). <article-title>Extension versus Bending for Continuum Robots</article-title>. <source>Int. J. Adv. Robotic Syst.</source> <volume>3</volume>, <fpage>26</fpage>. <pub-id pub-id-type="doi">10.5772/5740</pub-id> </citation>
</ref>
<ref id="B40">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wu</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Crawford</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Roberts</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Dexterity Analysis of Three 6-dof Continuum Robots Combining Concentric Tube Mechanisms and cable-driven Mechanisms</article-title>. <source>IEEE Robot. Autom. Lett.</source> <volume>2</volume>, <fpage>514</fpage>&#x2013;<lpage>521</lpage>. <pub-id pub-id-type="doi">10.1109/lra.2016.2645519</pub-id> </citation>
</ref>
<ref id="B41">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yuan</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Zhou</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Xu</surname>
<given-names>W.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>A Comprehensive Static Model of cable-driven Multi-Section Continuum Robots Considering Friction Effect</article-title>. <source>Mechanism Machine Theor.</source> <volume>135</volume>, <fpage>130</fpage>&#x2013;<lpage>149</lpage>. <pub-id pub-id-type="doi">10.1016/j.mechmachtheory.2019.02.005</pub-id> </citation>
</ref>
</ref-list>
</back>
</article>