phd-simscape-nano-hexapod/simscape-nano-hexapod.org

871 lines
39 KiB
Org Mode
Raw Normal View History

2024-03-19 15:13:18 +01:00
#+TITLE: Simscape Model - Nano Hexapod
:DRAWER:
#+LANGUAGE: en
#+EMAIL: dehaeze.thomas@gmail.com
#+AUTHOR: Dehaeze Thomas
#+HTML_LINK_HOME: ../index.html
#+HTML_LINK_UP: ../index.html
#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="https://research.tdehaeze.xyz/css/style.css"/>
#+HTML_HEAD: <script type="text/javascript" src="https://research.tdehaeze.xyz/js/script.js"></script>
#+BIND: org-latex-image-default-option "scale=1"
#+BIND: org-latex-image-default-width ""
#+LaTeX_CLASS: scrreprt
#+LaTeX_CLASS_OPTIONS: [a4paper, 10pt, DIV=12, parskip=full, bibliography=totoc]
2025-02-05 17:47:37 +01:00
#+LATEX_HEADER: \input{preamble.tex}
#+LATEX_HEADER_EXTRA: \input{preamble_extra.tex}
2024-03-19 15:13:18 +01:00
#+LATEX_HEADER_EXTRA: \bibliography{simscape-nano-hexapod.bib}
#+BIND: org-latex-bib-compiler "biber"
#+PROPERTY: header-args:matlab :session *MATLAB*
#+PROPERTY: header-args:matlab+ :comments org
#+PROPERTY: header-args:matlab+ :exports none
#+PROPERTY: header-args:matlab+ :results none
#+PROPERTY: header-args:matlab+ :eval no-export
#+PROPERTY: header-args:matlab+ :noweb yes
#+PROPERTY: header-args:matlab+ :mkdirp yes
#+PROPERTY: header-args:matlab+ :output-dir figs
#+PROPERTY: header-args:matlab+ :tangle no
#+PROPERTY: header-args:latex :headers '("\\usepackage{tikz}" "\\usepackage{import}" "\\import{$HOME/Cloud/tikz/org/}{config.tex}")
#+PROPERTY: header-args:latex+ :imagemagick t :fit yes
#+PROPERTY: header-args:latex+ :iminoptions -scale 100% -density 150
#+PROPERTY: header-args:latex+ :imoutoptions -quality 100
#+PROPERTY: header-args:latex+ :results file raw replace
#+PROPERTY: header-args:latex+ :buffer no
#+PROPERTY: header-args:latex+ :tangle no
#+PROPERTY: header-args:latex+ :eval no-export
#+PROPERTY: header-args:latex+ :exports results
#+PROPERTY: header-args:latex+ :mkdirp yes
#+PROPERTY: header-args:latex+ :output-dir figs
#+PROPERTY: header-args:latex+ :post pdf2svg(file=*this*, ext="png")
:END:
#+latex: \clearpage
* Build :noexport:
#+NAME: startblock
#+BEGIN_SRC emacs-lisp :results none :tangle no
(add-to-list 'org-latex-classes
'("scrreprt"
"\\documentclass{scrreprt}"
("\\chapter{%s}" . "\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
))
;; Remove automatic org heading labels
(defun my-latex-filter-removeOrgAutoLabels (text backend info)
"Org-mode automatically generates labels for headings despite explicit use of `#+LABEL`. This filter forcibly removes all automatically generated org-labels in headings."
(when (org-export-derived-backend-p backend 'latex)
(replace-regexp-in-string "\\\\label{sec:org[a-f0-9]+}\n" "" text)))
(add-to-list 'org-export-filter-headline-functions
'my-latex-filter-removeOrgAutoLabels)
;; Remove all org comments in the output LaTeX file
(defun delete-org-comments (backend)
(loop for comment in (reverse (org-element-map (org-element-parse-buffer)
'comment 'identity))
do
(setf (buffer-substring (org-element-property :begin comment)
(org-element-property :end comment))
"")))
(add-hook 'org-export-before-processing-hook 'delete-org-comments)
;; Use no package by default
(setq org-latex-packages-alist nil)
(setq org-latex-default-packages-alist nil)
;; Do not include the subtitle inside the title
(setq org-latex-subtitle-separate t)
(setq org-latex-subtitle-format "\\subtitle{%s}")
(setq org-export-before-parsing-hook '(org-ref-glossary-before-parsing
org-ref-acronyms-before-parsing))
#+END_SRC
* Notes :noexport:
2025-02-05 17:47:37 +01:00
** Notes
Prefix is =nhexa=
2024-03-19 15:13:18 +01:00
Based on:
2025-02-05 17:47:37 +01:00
- [ ] Stewart platform presentation: [[file:~/Cloud/meetings/group-meetings-me/2020-01-27-Stewart-Platform-Simscape/2020-01-27-Stewart-Platform-Simscape.org]]
2024-03-19 15:13:18 +01:00
- [ ] Add some sections from here: [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/index.org]]
For instance:
- [ ] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/stewart-architecture.org][stewart architecture]]
2025-02-05 17:47:37 +01:00
- [ ] [[file:~/Cloud/work-projects/ID31-NASS/matlab/nass-simscape/org/stewart_platform.org::+TITLE: Stewart Platform - Simscape Model]]
2024-03-19 15:13:18 +01:00
- [ ] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/kinematic-study.org][kinematic study]]
- [ ] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/identification.org][stewart platform - dynamics]]
- [ ] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/cubic-configuration.org][cubic configuration]]
- [ ] Look at the [[file:~/Cloud/work-projects/ID31-NASS/documents/state-of-thesis-2020/index.org][NASS 2020 report]]
2025-02-05 17:47:37 +01:00
Sections 5.1, 5.4
2024-03-19 15:13:18 +01:00
- [ ] [[file:~/Cloud/work-projects/ID31-NASS/matlab/nass-simscape/org/amplified_piezoelectric_stack.org][amplified_piezoelectric_stack]] (Just use 2DoF here)
2025-02-05 17:47:37 +01:00
- [ ] [[file:~/Cloud/work-projects/ID31-NASS/matlab/nass-simscape/org/nano_hexapod.org][nano_hexapod]] (it seems this report is already after the detailed design phase: yes but some parts could be interesting)
2024-03-19 15:13:18 +01:00
- [ ] Should the study of effect of flexible joints be included here?
2025-02-05 17:47:37 +01:00
- [X] file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/control-vibration-isolation.org
Questions:
- [ ] The APA model should maybe not be used here, same for the nice top and bottom plates. Here the detailed design is not yet performed
2025-02-06 16:02:34 +01:00
** DONE [#A] Copy relevant parts of reports
CLOSED: [2025-02-06 Thu 15:27]
2025-02-05 17:47:37 +01:00
2025-02-06 16:02:34 +01:00
- [X] Stewart platform presentation: [[file:~/Cloud/meetings/group-meetings-me/2020-01-27-Stewart-Platform-Simscape/2020-01-27-Stewart-Platform-Simscape.org]]
- [X] Add some sections from here: [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/index.org]]
2025-02-05 17:47:37 +01:00
For instance:
2025-02-06 16:02:34 +01:00
- [X] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/stewart-architecture.org][stewart architecture]]
- [X] [[file:~/Cloud/work-projects/ID31-NASS/matlab/nass-simscape/org/stewart_platform.org::+TITLE: Stewart Platform - Simscape Model]]
- [X] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/kinematic-study.org][kinematic study]]
- [X] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/identification.org]]
Effect of joints stiffnesses
- [X] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/cubic-configuration.org][cubic configuration]]
Not relevant here: in chapter 2
- [X] Look at the [[file:~/Cloud/work-projects/ID31-NASS/documents/state-of-thesis-2020/index.org][NASS 2020 report]]
2025-02-05 17:47:37 +01:00
Sections 5.1, 5.4
2025-02-06 16:02:34 +01:00
- [X] [[file:~/Cloud/work-projects/ID31-NASS/matlab/nass-simscape/org/amplified_piezoelectric_stack.org][amplified_piezoelectric_stack]] (Just use 2DoF here)
- [X] [[file:~/Cloud/work-projects/ID31-NASS/matlab/nass-simscape/org/nano_hexapod.org][nano_hexapod]] (it seems this report is already after the detailed design phase: yes but some parts could be interesting)
*Will also be used in Chapter 2*
- [X] Should the study of effect of flexible joints be included here?
*No, considered perfect and then optimized in chapter 2*
2025-02-05 17:47:37 +01:00
- [X] file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/control-vibration-isolation.org
** DONE [#A] Make a nice outline
CLOSED: [2025-02-05 Wed 17:45]
*Introduction*
- Choice of architecture to do 5DoF control
- Stewart platform
- Need to model the active vibration platform
- Control
*1 - Active Vibration Platforms*:
Introduction:
Maybe no sections, just a review discussing several aspect of the platforms.
1. Review of active vibration platforms (focused on Synchrotron applications)
2. Serial and Parallel Architecture: advantages and disadvantages of both
3. Which architecture => Parallel manipulator? Why *Stewart platform*?
*2 - The Stewart Platform*:
Introduction: some history about Stewart platform and why it is so used
1. Architecture (plates, struts, joints)
2. Kinematics and Jacobian
4. Static Analysis
5. Dynamic Analysis: very complex => multi-body model
For instance, compute the plant for massless struts and perfect joints (will be compared with Simscape model).
But say that if we want to model more complex cases, it becomes impractical (cite papers).
*3 - Multi-Body model of the Stewart platform*:
Introduction: Complex dynamics => analytical formulas can be complex => Choose to study the dynamics using a multi-body model
1. Model definition: (Matlab Toolbox), frames, inertias of parts, stiffnesses, struts, etc...
2. Joints: perfect 2dof/3dof (+ mass-less)
3. Actuators: APA + Encoder (mass-less)
4. Nano-Hexapod: definition of each part + Plant with defined inputs/outputs (force sensor, relative displacement sensor, etc...)
Compare with analytical formulas (see number of states)
*4 - Control of the Stewart Platform*:
Introduction: MIMO control => much more complex than SISO control because of interaction. Possible to ignore interaction when good decoupling (important to have tools to study interaction)
1. Centralized and Decentralized Control
2. Decoupling Control / Choice of control space file:~/Cloud/research/matlab/decoupling-strategies/svd-control.org
Estimate coupling: RGA
- Jacobian matrices, CoK, CoM, control in the frame of the struts, ...
- Discussion of cubic architecture (quick, as it is going to be in detailed in chapter 2)
- SVD, Modal, ...
3. Active Damping: decentralized IFF
Guaranteed stability?
For decentralized control: "MIMO root locus"
How to optimize the added damping to all modes?
4. HAC-LAC
Stability of closed-loop: Nyquist (main advantage: possible to do with experimental FRF)
*Conclusion*:
- Configurable Stewart platform model
- Will be included in the multi-body model of the micro-station => nass multi body model
** DONE [#A] Location of this report in the complete thesis
CLOSED: [2025-02-05 Wed 16:04]
*Before the report* (assumptions):
- Uniaxial model: no stiff actuator, HAC-LAC strategy
- Rotating model:
Soft actuators are problematic due to gyroscopic effects
Use moderately stiff (1um/N).
IFF can be applied with APA architecture
- Model of Micro-station is ready
*In this report*:
- Goal: build a flexible (i.e. configurable) multi-body model of a Stewart platform that will be used in the next section to perform dynamical analysis and simulate experiments with the complete NASS
- Here, I propose to work with "perfect" stewart platforms:
- almost mass-less struts
- joints with zero stiffness in free DoFs (i.e. 2-DoF and 3-DoF joints)
- Presentation of Stewart platforms (Literature review about stewart platforms will be done in chapter 2)
- Presentation of the Simscape model
*After the report* (NASS-Simscape):
- nano-hexapod on top of micro-station
- control is performed
- simulations => validation of the concept
2025-02-06 16:02:34 +01:00
** TODO [#A] Make sure the Simulink file for the Stewart platform is working well
SCHEDULED: <2025-02-06 Thu>
It should be the exact model reference that will be included in the NASS model.
** DONE [#C] First time in the report that we speak about MIMO control ? Or maybe next section!
CLOSED: [2025-02-06 Thu 16:01]
2025-02-05 17:47:37 +01:00
Maybe should introduce:
- "MIMO" Root locus
- "MIMO" Nyquist plot / characteristic loci
Or should this be in annexes?
Maybe say that in this phd-thesis, the focus is not on the control.
I tried multiple architectures (complementary filters, etc.), but the focus is not on that.
2025-02-06 16:02:34 +01:00
** ANSW [#C] Cubic architecture should be the topic here or in the detailed design?
CLOSED: [2025-02-06 Thu 16:01]
2025-02-05 17:47:37 +01:00
I suppose that it should be in the detailed design phase.
(Review about Stewart platform design should be made in Chapter two.)
Here, just use simple control architecture for general validation (and not optimization).
2025-02-06 16:02:34 +01:00
** ANSW [#C] Should I make a review of control strategies?
CLOSED: [2025-02-06 Thu 16:01]
2025-02-05 17:47:37 +01:00
Yes it seems to good location for review related to control.
Jacobian matrix.
Control is the frame of the struts, in the cartesian frame (CoM, CoK), modal control, etc...
[[file:~/Cloud/research/matlab/decoupling-strategies/svd-control.org][file:~/Cloud/research/matlab/decoupling-strategies/svd-control.org]]
2025-02-06 16:02:34 +01:00
** DONE [#C] Compare simscape =linearize= and analytical formula
CLOSED: [2025-02-06 Thu 16:01]
2025-02-05 17:47:37 +01:00
- [X] OK for $\omega=0$ (using just the Stiffness matrix)
- [ ] Should add the mass matrix and compare for all frequencies
The analytical dynamic model is taken from cite:taghirad13_paral
2025-02-06 16:02:34 +01:00
** DONE [#C] Output the cubic configuration with clear display of the cube and center of the cube
CLOSED: [2025-02-06 Thu 16:02]
2025-02-05 17:47:37 +01:00
[[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/cubic-configuration.org][cubic configuration]]
2025-02-06 16:02:34 +01:00
*No, this will be in Chapter 2*
2025-02-05 17:47:37 +01:00
2025-02-06 16:02:34 +01:00
** CANC [#C] Maybe make an appendix to present the developed toolbox?
CLOSED: [2025-02-06 Thu 16:02]
2024-03-19 15:13:18 +01:00
2025-02-06 16:02:34 +01:00
- State "CANC" from "TODO" [2025-02-06 Thu 16:02]
2024-03-19 15:13:18 +01:00
* Introduction :ignore:
2025-02-06 16:02:34 +01:00
Now that the multi-body model of the micro-station has been developed and validated using dynamical measurements, a model of the active vibration platform can be integrated.
First, the mechanical architecture of the active platform needs to be carefully chosen.
In Section ref:sec:nhexa_platform_review, a quick review of active vibration platforms is performed.
The chosen architecture is the Stewart platform, which is presented in Section ref:sec:nhexa_stewart_platform.
It is a parallel manipulator that require the use of specific tools to study its kinematics.
However, to study the dynamics of the Stewart platform, the use of analytical equations is very complex.
Instead, a multi-body model of the Stewart platform is developed (Section ref:sec:nhexa_model), that can then be easily integrated on top of the micro-station's model.
From a control point of view, the Stewart platform is a MIMO system with complex dynamics.
To control such system, it requires several tools to study interaction (Section ref:sec:nhexa_control).
2025-02-05 17:47:37 +01:00
* Active Vibration Platforms
<<sec:nhexa_platform_review>>
** Introduction :ignore:
*Goals*:
2025-02-06 16:02:34 +01:00
- Quick review of active vibration platforms (5 or 6DoF) similar to NASS
2025-02-05 17:47:37 +01:00
- Explain why Stewart platform architecture is chosen
2025-02-06 16:02:34 +01:00
- Wanted controlled DOF: Y, Z, Ry
- But because of continuous rotation (key specificity): X,Y,Z,Rx,Ry in the frame of the active platform
2025-02-05 17:47:37 +01:00
- Literature review? (*maybe more suited for chapter 2*)
- file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/bibliography.org
- Talk about flexible joint? Maybe not so much as it should be topic of second chapter.
Just say that we must of flexible joints that can be defined as 3 to 6DoF joints, and it will be optimize in chapter 2.
- [[cite:&taghirad13_paral]]
2025-02-06 16:02:34 +01:00
2025-02-05 17:47:37 +01:00
- For some systems, just XYZ control (stack stages), example: holler
- For other systems, Stewart platform (ID16a), piezo based
- Examples of Stewart platforms for general vibration control, some with Piezo, other with Voice coil. IFF, ...
Show different geometry configuration
- DCM: tripod?
** Active vibration control of sample stages
[[file:~/Cloud/work-projects/ID31-NASS/phd-thesis-chapters/A0-nass-introduction/nass-introduction.org::*Review of stages with online metrology for Synchrotrons][Review of stages with online metrology for Synchrotrons]]
- [ ] Talk about external metrology?
2025-02-06 16:02:34 +01:00
Maybe not the topic here.
2025-02-05 17:47:37 +01:00
- [ ] Talk about control architecture?
- [ ] Comparison with the micro-station / NASS
** Serial and Parallel Manipulators
*Goal*:
- Explain why a parallel manipulator is here preferred
- Compact, 6DoF, higher control bandwidth, linear, simpler
- Show some example of serial and parallel manipulators
- A review of Stewart platform will be given in Chapter related to the detailed design of the Nano-Hexapod
2025-02-06 16:02:34 +01:00
#+name: tab:nhexa_serial_vs_parallel
#+caption: Advantages and Disadvantages of both serial and parallel robots
#+attr_latex: :environment tabularx :width \linewidth :align lXX
#+attr_latex: :center t :booktabs t :float t
| | *Serial Robots* | *Parallel Robots* |
|--------------------+-----------------+-------------------|
| Advantages | Large Workspace | High Stiffness |
| Disadvantages | Low Stiffness | Small Workspace |
| Kinematic Struture | Open | Closed-loop |
2025-02-05 17:47:37 +01:00
* The Stewart platform
:PROPERTIES:
:HEADER-ARGS:matlab+: :tangle matlab/nhexa_1_stewart_platform.m
:END:
<<sec:nhexa_stewart_platform>>
** Introduction :ignore:
# Most of this section is based on [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/kinematic-study.org][kinematic-study.org]]
- Some history about Stewart platforms
- What is so special and why it is so used in different fields: give examples
Explain advantages compared to serial architecture
- Little review (very quick: two extreme sizes, piezo + voice coil)
Complete review of Stewart platforms will be made in Chapter 2
- Presentation of tools used to analyze the properties of the Stewart platform => useful for design and control
2025-02-06 16:02:34 +01:00
The Stewart Platform is very adapted for the NASS application for the following reasons:
- it is a fully parallel manipulator, thus all the motions errors can be compensated
- it is very compact compared to a serial manipulator
- it has high stiffness and good dynamic performances
The main disadvantage of Stewart platforms is the small workspace when compare the serial manipulators which is not a problem here.
2025-02-05 17:47:37 +01:00
** Matlab Init :noexport:ignore:
#+begin_src matlab :tangle no :exports none :results silent :noweb yes :var current_dir=(file-name-directory buffer-file-name)
<<matlab-dir>>
#+end_src
#+begin_src matlab :exports none :results silent :noweb yes
<<matlab-init>>
#+end_src
#+begin_src matlab :tangle no :noweb yes
<<m-init-path>>
#+end_src
#+begin_src matlab :eval no :noweb yes
<<m-init-path-tangle>>
#+end_src
#+begin_src matlab :noweb yes
<<m-init-other>>
#+end_src
** Mechanical Architecture
<<ssec:nhexa_stewart_platform_architecture>>
2025-02-06 16:02:34 +01:00
- [ ] Use this file as a reference: file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/stewart-architecture.org
2024-03-19 15:13:18 +01:00
2025-02-05 17:47:37 +01:00
Presentation of the typical architecture
- Explain the different frames, etc...
- explain key elements:
- two plates
- joints
- actuators
2024-03-19 15:13:18 +01:00
2025-02-06 16:02:34 +01:00
[[file:figs/nhexa_stewart_platform_conf.png]]
The Stewart Platform:
- Has 6 degrees-of-freedom
- Is a *Fully* parallel manipulator as the number of actuators is equal to the number of dof
- Is a *Symmetrical* parallel manipulator as all the struts are the same
#+name: tab:stewart_platforms_configurations
#+attr_latex: :environment tabularx :width \linewidth :align cXXX
#+attr_latex: :center t :booktabs t :float t
| | *Base Joint* | *Actuator Joint* | *Top Joint* |
|---------+--------------+------------------+-------------|
| *6-SPS* | Spherical | Prismatic | Spherical |
| *6-UPS* | Universal | Prismatic | Spherical |
2025-02-05 17:47:37 +01:00
Make well defined notations.
- {F}, {M}
- si, li, ai, bi, etc.
- [ ] Make figure with defined frames, joints, etc...
2025-02-06 16:02:34 +01:00
These frames are used to describe the relative motion of the two platforms through the position vector ${}^A\bm{P}_B$ of $\{B\}$ expressed in $\{A\}$ and the rotation matrix ${}^A\bm{R}_B$ expressing the orientation of $\{B\}$ with respect to $\{A\}$.
For the nano-hexapod, these frames are chosen to be located at the theoretical focus point of the X-ray light (xxx mm above the top platform).
#+begin_quote
Stewart platforms are generated in multiple steps.
We define 4 important *frames*:
- $\{F\}$: Frame fixed to the *Fixed* base and located at the center of its bottom surface.
This is used to fix the Stewart platform to some support.
- $\{M\}$: Frame fixed to the *Moving* platform and located at the center of its top surface.
This is used to place things on top of the Stewart platform.
- $\{A\}$: Frame fixed to the fixed base.
It defined the center of rotation of the moving platform.
- $\{B\}$: Frame fixed to the moving platform.
The motion of the moving platforms and forces applied to it are defined with respect to this frame $\{B\}$.
Then, we define the *location of the spherical joints*:
- $\bm{a}_{i}$ are the position of the spherical joints fixed to the fixed base
- $\bm{b}_{i}$ are the position of the spherical joints fixed to the moving platform
We define the *rest position* of the Stewart platform:
- For simplicity, we suppose that the fixed base and the moving platform are parallel and aligned with the vertical axis at their rest position.
- Thus, to define the rest position of the Stewart platform, we just have to defined its total height $H$.
$H$ corresponds to the distance from the bottom of the fixed base to the top of the moving platform.
From $\bm{a}_{i}$ and $\bm{b}_{i}$, we can determine the *length and orientation of each strut*:
- $l_{i}$ is the length of the strut
- ${}^{A}\hat{\bm{s}}_{i}$ is the unit vector align with the strut
#+end_quote
2025-02-05 17:47:37 +01:00
** Kinematic Analysis
<<ssec:nhexa_stewart_platform_kinematics>>
2025-02-06 16:02:34 +01:00
**** Introduction :ignore:
Kinematic analysis refers to the study of the geometry of motion of a robot, without considering the forces that cause the motion.
The relation between the geometry of the manipulator with the final motion of the moving platform is derived and analyzed.
*Definition of the geometry of the Stewart Platform*:
- $\bm{a}_i$: position of the attachment points on the fixed base
- $\bm{b}_i$: position of moving attachment points
- $l_i$: length of each limb
- $\hat{\bm{s}}_i$: unit vector representing the direction of each limb
#+name: fig:nhexa_stewart_schematic
#+caption: Geometry of a Stewart Platform
#+attr_latex: :scale 1
[[file:figs/nhexa_stewart_schematic.png]]
**** Loop Closure
At the displacement level, the *closure of each kinematic loop* can be express in the vector form as
\[ \vec{AB} = \vec{AA_i} + \vec{A_iB_i} - \vec{BB_i} \quad \text{for } i = 1,2,\dots,n \]
in which $\vec{AA_i}$ and $\vec{BB_i}$ can be easily obtained from the geometry of the attachment points in the base and in the moving platform.
The *loop closure* can be written as the unknown pose variables ${}^A\bm{P}$ and ${}^A\bm{R}_B$, the position vectors describing the known geometry of the base and of the moving platform, $\bm{a}_i$ and $\bm{b}_i$, and the limb vector $l_i {}^A\hat{\bm{s}}_i$:
\begin{equation*}
{}^A\bm{P} = {}^A\bm{a}_i + l_i{}^A\hat{\bm{s}}_i - {}^A\bm{R}_B {}^B\bm{b}_i \quad \text{for } i=1,2,\dots,n
\end{equation*}
2025-02-05 17:49:45 +01:00
**** Inverse Kinematics
2025-02-05 17:47:37 +01:00
2025-02-06 16:02:34 +01:00
For /inverse kinematic analysis/, it is assumed that the position ${}^A\bm{P}$ and orientation of the moving platform ${}^A\bm{R}_B$ are given and the problem is to obtain the joint variables $\bm{\mathcal{L}} = \left[ l_1, l_2, l_3, l_4, l_5, l_6 \right]^T$.
This problem can be easily solved using the loop closures.
The obtain joint variables are:
\begin{equation*}
\begin{aligned}
l_i = &\Big[ {}^A\bm{P}^T {}^A\bm{P} + {}^B\bm{b}_i^T {}^B\bm{b}_i + {}^A\bm{a}_i^T {}^A\bm{a}_i - 2 {}^A\bm{P}^T {}^A\bm{a}_i + \dots\\
&2 {}^A\bm{P}^T \left[{}^A\bm{R}_B {}^B\bm{b}_i\right] - 2 \left[{}^A\bm{R}_B {}^B\bm{b}_i\right]^T {}^A\bm{a}_i \Big]^{1/2}
\end{aligned}
\end{equation*}
If the position and orientation of the platform lie in the feasible workspace, the solution is unique.
Otherwise, the solution gives complex numbers.
2025-02-05 17:49:45 +01:00
**** Forward Kinematics
2025-02-05 17:47:37 +01:00
2025-02-06 16:02:34 +01:00
In /forward kinematic analysis/, it is assumed that the vector of limb lengths $\bm{L}$ is given and the problem is to find the position ${}^A\bm{P}$ and the orientation ${}^A\bm{R}_B$.
This is a difficult problem that requires to solve nonlinear equations.
In a next section, an approximate solution of the forward kinematics problem is proposed for small displacements.
** The Jacobian Matrix
**** Introduction :ignore:
In vector calculus, the Jacobian matrix of a vector-valued function in several variables is the matrix of all its first-order partial derivatives.
Suppose $\bm{f}: \mathbb{R}^n \rightarrow \mathbb{R}^m$ is a function such that each of its first-order partial derivatives exist on $\mathbb{R}^n$.
This function takes a point $\bm{x} \in \mathbb{R}^n$ as input and produces the vector $\bm{f}(\bm{x}) \in \mathbb{R}^m$ as output.
Then the Jacobian matrix $\bm{J}$ of $\bm{f}$ is defined to be an $n \times m$ matrix, whose its (i,j)'th entry is $J_{ij} = \frac{\partial f_i}{\partial x_j}$.
The Jacobian matrix is the *linear transformation* that best approximates $\bm{f}$ for points close to $\bm{x}$.
*Summary*: Linear approximation of a function with several inputs and outputs around a working point.
**** Jacobian Computation - Velocity Loop Closure
Let's note:
- $\bm{\mathcal{L}} = \left[ l_1, l_2, \ldots, l_6 \right]^T$: vector of actuated joint coordinates
- $\bm{\mathcal{X}} = \left[ {}^A\bm{P}, \bm{}^A\hat{\bm{s}} \right]^T$: vector of platform motion variables
$\bm{\mathcal{L}}$ and $\bm{\mathcal{X}}$ are related through a system of /nonlinear algebraic equations/ representing the /kinematic constraints imposed by the struts/, which can be generally written as $f(\bm{\mathcal{L}}, \bm{\mathcal{X}}) = 0$.
We can differentiate this equation with respect to time and obtain:
\begin{equation*}
\bm{J}_x \dot{\bm{\mathcal{X}}} = \bm{J}_l \dot{\bm{\mathcal{L}}} \quad \text{where} \quad
\bm{J}_x = \frac{\partial f}{\partial \bm{\mathcal{X}}} \quad \text{and} \quad \bm{J}_l = -\frac{\partial f}{\partial \bm{\mathcal{L}}}
\end{equation*}
With:
- $\dot{\bm{\mathcal{L}}} = [ \dot{l}_1, \dot{l}_2, \dot{l}_3, \dot{l}_4, \dot{l}_5, \dot{l}_6 ]^T$
- $\dot{\bm{X}} = [^A\bm{v}_p, {}^A\bm{\omega}]^T$:
2025-02-05 17:47:37 +01:00
2025-02-06 16:02:34 +01:00
The *general Jacobian matrix* is defined as:
\begin{equation*}
\dot{\bm{\mathcal{L}}} = \bm{J} \dot{\bm{\mathcal{X}}} \quad \text{with} \quad \bm{J} = {\bm{J}_l}^{-1} \bm{J}_x
\end{equation*}
The *velocity loop closures* are used for *obtaining the Jacobian matrices* in a straightforward manner:
\begin{align*}
{}^A\bm{P} + {}^A\bm{R}_B {}^B\bm{b}_i = l_i {}^A\hat{\bm{s}}_i + {}^A\bm{a}_i
& \underset{\frac{\partial}{\partial t}}{\rightarrow}
{}^A\bm{v}_p + {}^A \dot{\bm{R}}_B {}^B\bm{b}_i = \dot{l}_i {}^A\hat{\bm{s}}_i + l_i {}^A\dot{\hat{\bm{s}}}_i \\
& \Leftrightarrow\hat{\bm{s}}_i {}^A\bm{v}_p + ({}^A\bm{b}_i \times \hat{\bm{s}}_i) {}^A\bm{\omega} = \dot{l}_i
\end{align*}
We can rearrange the equations in a matrix form:
\[ \dot{\bm{\mathcal{L}}} = \bm{J} \dot{\bm{\mathcal{X}}} \quad \text{with} \ \dot{\bm{\mathcal{L}}} = [ \dot{l}_1 \ \dots \ \dot{l}_6 ]^T \ \text{and} \ \dot{\bm{\mathcal{X}}} = [{}^A\bm{v}_p ,\ {}^A\bm{\omega}]^T \]
\begin{equation}
\bm{J} = \begin{bmatrix}
{\hat{\bm{s}}_1}^T & (\bm{b}_1 \times \hat{\bm{s}}_1)^T \\
{\hat{\bm{s}}_2}^T & (\bm{b}_2 \times \hat{\bm{s}}_2)^T \\
{\hat{\bm{s}}_3}^T & (\bm{b}_3 \times \hat{\bm{s}}_3)^T \\
{\hat{\bm{s}}_4}^T & (\bm{b}_4 \times \hat{\bm{s}}_4)^T \\
{\hat{\bm{s}}_5}^T & (\bm{b}_5 \times \hat{\bm{s}}_5)^T \\
{\hat{\bm{s}}_6}^T & (\bm{b}_6 \times \hat{\bm{s}}_6)^T
\end{bmatrix}
\end{equation}
$\bm{J}$ then depends only on:
- $\hat{\bm{s}}_i$ the orientation of the limbs expressed in $\{A\}$
- $\bm{b}_i$ the position of the joints with respect to $O_B$ and express in $\{A\}$
**** Approximate solution of the Forward and Inverse Kinematic problems
For small displacements mobile platform displacement $\delta \bm{\mathcal{X}} = [\delta x, \delta y, \delta z, \delta \theta_x, \delta \theta_y, \delta \theta_z ]^T$ around $\bm{\mathcal{X}}_0$, the associated joint displacement can be computed using the Jacobian (approximate solution of the inverse kinematic problem):
\begin{equation*}
\delta\bm{\mathcal{L}} = \bm{J} \delta\bm{\mathcal{X}}
\end{equation*}
Similarly, for small joint displacements $\delta\bm{\mathcal{L}} = [ \delta l_1,\ \dots,\ \delta l_6 ]^T$ around $\bm{\mathcal{L}}_0$, it is possible to find the induced small displacement of the mobile platform (approximate solution of the forward kinematic problem):
\begin{equation*}
\delta\bm{\mathcal{X}} = \bm{J}^{-1} \delta\bm{\mathcal{L}}
\end{equation*}
These two relations solve the forward and inverse kinematic problems for small displacement in a /approximate/ way.
As the inverse kinematic can be easily solved exactly this is not much useful, however, as the forward kinematic problem is difficult to solve, this approximation can be very useful for small displacements.
**** Range validity of the approximate inverse kinematics
- [ ] [[file:~/Cloud/work-projects/ID31-NASS/matlab/stewart-simscape/org/kinematic-study.org::*Estimation of the range validity of the approximate inverse kinematics][Estimation of the range validity of the approximate inverse kinematics]]
**** Static Forces
The *principle of virtual work* states that the total virtual work, $\delta W$, done by all actuators and external forces is equal to zero:
\begin{align*}
\delta W &= \bm{\tau}^T \delta \bm{\mathcal{L}} - \bm{\mathcal{F}}^T \delta \bm{\mathcal{X}}\\
& = 0
\end{align*}
If we note:
- $\bm{\tau} = [\tau_1, \tau_2, \cdots, \tau_6]^T$: vector of actuator forces applied in each strut
- $\bm{\mathcal{F}} = [\bm{f}, \bm{n}]^T$: external force/torque action on the mobile platform at $\bm{O}_B$
From the definition of the Jacobian ($\delta \bm{\mathcal{L}} = \bm{J} \cdot \delta \bm{\mathcal{X}}$), we have $\left( \bm{\tau}^T \bm{J} - \bm{\mathcal{F}}^T \right) \delta \bm{\mathcal{X}} = 0$ that holds for any $\delta \bm{\mathcal{X}}$, hence:
\[ \bm{\tau}^T \bm{J} - \bm{\mathcal{F}}^T = 0 \quad \Rightarrow \quad \tcmbox{\bm{\mathcal{F}} = \bm{J}^T \bm{\tau}} \quad \text{and} \quad \tcmbox{\bm{\tau} = \bm{J}^{-T} \bm{\mathcal{F}}} \]
2025-02-05 17:47:37 +01:00
2025-02-05 17:49:45 +01:00
**** Singularities
2025-02-05 17:47:37 +01:00
- Briefly mention singularities, and say that for small stroke, it is not an issue, the Jacobian matrix may be considered constant
** Static Analysis
<<ssec:nhexa_stewart_platform_static>>
How stiffness varies with orientation of struts.
Same with stroke?
Or maybe in the detailed chapter?
2025-02-06 16:02:34 +01:00
The stiffness of the actuator $k_i$ links the applied actuator force $\delta \tau_i$ and the corresponding small deflection $\delta l_i$:
\begin{equation*}
\tau_i = k_i \delta l_i, \quad i = 1,\ \dots,\ 6
\end{equation*}
If we combine these 6 relations:
\begin{equation*}
\bm{\tau} = \mathcal{K} \delta \bm{\mathcal{L}} \quad \mathcal{K} = \text{diag}\left[ k_1,\ \dots,\ k_6 \right]
\end{equation*}
Substituting $\bm{\tau} = \bm{J}^{-T} \bm{\mathcal{F}}$ and $\delta \bm{\mathcal{L}} = \bm{J} \cdot \delta \bm{\mathcal{X}}$ gives
\begin{equation*}
\bm{\mathcal{F}} = \bm{J}^T \mathcal{K} \bm{J} \cdot \delta \bm{\mathcal{X}}
\end{equation*}
And then we identify the stiffness matrix $\bm{K}$:
\begin{equation*}
\bm{K} = \bm{J}^T \mathcal{K} \bm{J}
\end{equation*}
If the stiffness matrix $\bm{K}$ is inversible, the *compliance matrix* of the manipulator is defined as
\begin{equation*}
\bm{C} = \bm{K}^{-1} = (\bm{J}^T \mathcal{K} \bm{J})^{-1}
\end{equation*}
The compliance matrix of a manipulator shows the mapping of the moving platform wrench applied at $\bm{O}_B$ to its small deflection by
\begin{equation*}
\delta \bm{\mathcal{X}} = \bm{C} \cdot \bm{\mathcal{F}}
\end{equation*}
2025-02-05 17:47:37 +01:00
** Dynamic Analysis
<<ssec:nhexa_stewart_platform_dynamics>>
Very complex => multi-body model
For instance, compute the plant for massless struts and perfect joints (will be compared with Simscape model).
But say that if we want to model more complex cases, it becomes impractical (cite papers).
** Conclusion
:PROPERTIES:
:UNNUMBERED: t
:END:
2025-02-06 16:02:34 +01:00
Dynamic analysis of parallel manipulators presents an *inherent complexity due to their closed-loop structure and kinematic constraints*.
2025-02-05 17:47:37 +01:00
All depends on the geometry.
Reasonable choice of geometry is made in chapter 1.
Optimization of the geometry will be made in chapter 2.
* Multi-Body Model
2024-03-19 15:13:18 +01:00
:PROPERTIES:
2025-02-05 17:47:37 +01:00
:HEADER-ARGS:matlab+: :tangle matlab/nhexa_2_model.m
2024-03-19 15:13:18 +01:00
:END:
2025-02-05 17:47:37 +01:00
<<sec:nhexa_model>>
2024-03-19 15:13:18 +01:00
** Introduction :ignore:
2025-02-05 17:47:37 +01:00
*Goal*:
- Study the dynamics of Stewart platform
- Instead of working with complex analytical models: a multi-body model is used.
Complex because has to model the inertia of the struts.
Cite papers that tries to model the stewart platform analytically
Advantage: it will be easily included in the model of the NASS
- Mention the Toolbox (maybe make a DOI for that)
- [ ] Have a table somewhere that summarizes the main characteristics of the nano-hexapod model
- location of joints
- size / mass of platforms, etc...
2024-03-19 15:13:18 +01:00
** Matlab Init :noexport:ignore:
#+begin_src matlab :tangle no :exports none :results silent :noweb yes :var current_dir=(file-name-directory buffer-file-name)
<<matlab-dir>>
#+end_src
#+begin_src matlab :exports none :results silent :noweb yes
<<matlab-init>>
#+end_src
#+begin_src matlab :tangle no :noweb yes
<<m-init-path>>
#+end_src
#+begin_src matlab :eval no :noweb yes
<<m-init-path-tangle>>
#+end_src
#+begin_src matlab :noweb yes
<<m-init-other>>
#+end_src
2025-02-05 17:47:37 +01:00
** Model Definition
<<ssec:nhexa_model_def>>
- [ ] Make a schematic of the definition process (for instance knowing the ai, bi points + {A} and {B} allows to compute Jacobian, etc...)
- What is important for the model:
- Inertia of plates and struts
- Positions of joints / Orientation of struts
- Definition of frames (for Jacobian, stiffness analysis, etc...)
Then, several things can be computed:
- Kinematics, stiffness, platform mobility, dynamics, etc...
- Joints: can be 2dof to 6dof
- Actuators: can be modelled as wanted
** Nano Hexapod
<<ssec:nhexa_model_nano_hexapod>>
Start simple:
- Perfect joints, massless actuators
Joints: perfect 2dof/3dof (+ mass-less)
Actuators: APA + Encoder (mass-less)
- k = 1N/um
- Force sensor
Definition of each part + Plant with defined inputs/outputs (force sensor, relative displacement sensor, etc...)
** Model Dynamics
<<ssec:nhexa_model_dynamics>>
- If all is perfect (mass-less struts, perfect joints, etc...), maybe compare analytical model with simscape model?
- Say something about the model order
Model order is 12, and that we can compute modes from matrices M and K, compare with the Simscape model
- Compare with analytical formulas (see number of states)
** Conclusion
:PROPERTIES:
:UNNUMBERED: t
:END:
- Validation of multi-body model in a simple case
- Possible to increase the model complexity when required
- If considered 6dof joint stiffness, model order increases
- Can have an effect on IFF performances: [[cite:&preumont07_six_axis_singl_stage_activ]]
- Conclusion: during the conceptual design, we consider a perfect, but will be taken into account later
- Optimization of the Flexible joint will be performed in Chapter 2.2
- MIMO system: how to control? => next section
* Control of Stewart Platforms
:PROPERTIES:
:HEADER-ARGS:matlab+: :tangle matlab/nhexa_3_control.m
:END:
<<sec:nhexa_control>>
** Introduction :ignore:
MIMO control: much more complex than SISO control because of interaction.
Possible to ignore interaction when good decoupling is achieved.
Important to have tools to study interaction
Different ways to try to decouple a MIMO plant.
Reference book: [[cite:&skogestad07_multiv_feedb_contr]]
** Matlab Init :noexport:ignore:
#+begin_src matlab :tangle no :exports none :results silent :noweb yes :var current_dir=(file-name-directory buffer-file-name)
<<matlab-dir>>
#+end_src
#+begin_src matlab :exports none :results silent :noweb yes
<<matlab-init>>
#+end_src
#+begin_src matlab :tangle no :noweb yes
<<m-init-path>>
#+end_src
#+begin_src matlab :eval no :noweb yes
<<m-init-path-tangle>>
#+end_src
#+begin_src matlab :noweb yes
<<m-init-other>>
#+end_src
** Centralized and Decentralized Control
<<ssec:nhexa_control_centralized_decentralized>>
- Explain what is centralized and decentralized:
- linked to the sensor position relative to the actuators
- linked to the fact that sensors and actuators pairs are "independent" or each other (related to the control architecture, not because there is no coupling)
- When can decentralized control be used and when centralized control is necessary?
Study of interaction: RGA
** Choice of the control space
<<ssec:nhexa_control_space>>
- [ ] file:~/Cloud/research/matlab/decoupling-strategies/svd-control.org
- Jacobian matrices, CoK, CoM, control in the frame of the struts, SVD, Modal, ...
- Combined CoM and CoK => Discussion of cubic architecture ? (quick, as it is going to be in detailed in chapter 2)
- Explain also the link with the setpoint: it is interesting to have the controller in the frame of the performance variables
Also speak about disturbances? (and how disturbances can be mixed to different outputs due to control and interaction)
- Table that summarizes the trade-off for each strategy
- Say that in this study, we will do the control in the frame of the struts for simplicity (even though control in the cartesian frame was also tested)
** Active Damping with Decentralized IFF
<<ssec:nhexa_control_iff>>
Guaranteed stability: [[cite:&preumont08_trans_zeros_struc_contr_with]]
- [ ] I think there is another paper about that
For decentralized control: "MIMO root locus" can be used to estimate the damping / optimal gain
Poles and converging towards /transmission zeros/
How to optimize the added damping to all modes?
- [ ] Add some papers citations
Compute:
- [ ] Plant dynamics
- [ ] Root Locus
** MIMO High-Authority Control - Low-Authority Control
<<ssec:nhexa_control_hac_lac>>
Compute:
- [ ] compare open-loop and damped plant (outputs are the encoders)
- [ ] Implement decentralized control?
- [ ] Check stability:
- Characteristic Loci: Eigenvalues of $G(j\omega)$ plotted in the complex plane
- Generalized Nyquist Criterion: If $G(s)$ has $p_0$ unstable poles, then the closed-loop system with return ratio $kG(s)$ is stable if and only if the characteristic loci of $kG(s)$, taken together, encircle the point $-1$, $p_0$ times anti-clockwise, assuming there are no hidden modes
- [ ] Show some performance metric? For instance compliance?
** Conclusion
:PROPERTIES:
:UNNUMBERED: t
:END:
2024-03-19 15:13:18 +01:00
* Conclusion
2025-02-05 17:47:37 +01:00
:PROPERTIES:
:UNNUMBERED: t
:END:
<<sec:nhexa_conclusion>>
- Configurable Stewart platform model
- Will be included in the multi-body model of the micro-station => nass multi body model
- Control: complex problem, try to use simplest architecture
2024-03-19 15:13:18 +01:00
* Bibliography :ignore:
#+latex: \printbibliography[heading=bibintoc,title={Bibliography}]
* Helping Functions :noexport:
** Initialize Path
#+NAME: m-init-path
#+BEGIN_SRC matlab
%% Path for functions, data and scripts
addpath('./matlab/mat/'); % Path for data
addpath('./matlab/'); % Path for scripts
#+END_SRC
#+NAME: m-init-path-tangle
#+BEGIN_SRC matlab
%% Path for functions, data and scripts
addpath('./mat/'); % Path for data
#+END_SRC
** Initialize other elements
#+NAME: m-init-other
#+BEGIN_SRC matlab
%% Colors for the figures
colors = colororder;
#+END_SRC