From ce33167fb45612100688ca7b73f9efd6f25b0e6e Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Mon, 24 Jun 2024 20:29:36 +0000
Subject: [PATCH] Deployed 4c67efd to git-main with MkDocs 1.6.0 and mike 2.1.2

---
 git-main/404.html                             |  14 +-
 .../path_planner_assets/Big_hourglass.png     | Bin 0 -> 40943 bytes
 .../Big_hourglass_fillet.png                  | Bin 0 -> 33234 bytes
 .../contribution-guidelines/index.html        |  14 +-
 .../firmware/building-and-flashing/index.html |  14 +-
 .../firmware/code-architecture/index.html     |  14 +-
 .../firmware/debugging/index.html             |  14 +-
 .../firmware/unit-tests/index.html            |  14 +-
 .../controller/controller-base/index.html     |  14 +-
 .../controller-general-overview/index.html    |  14 +-
 .../controller/controller-outline/index.html  |  14 +-
 .../index.html                                |  14 +-
 .../controller-state-machine/index.html       |  14 +-
 .../controller-total-energy/index.html        |  14 +-
 .../navigation-overview}/index.html           |  56 ++-
 .../path-follower/index.html                  | 382 +++++++++++++++++-
 .../path-manager/index.html                   | 366 ++++++++++++++++-
 .../path-planner/index.html                   | 148 ++++++-
 .../rosplane/parameter-management/index.html  |  16 +-
 .../developer-guide/style-guide/index.html    |  14 +-
 git-main/index.html                           |  14 +-
 git-main/search/search_index.json             |   2 +-
 git-main/sitemap.xml                          |  70 ++--
 git-main/sitemap.xml.gz                       | Bin 540 -> 545 bytes
 .../user-guide/autonomous-flight/index.html   |  14 +-
 .../flight-controller-setup/index.html        |  14 +-
 .../user-guide/getting-started/index.html     |  14 +-
 git-main/user-guide/hardware-setup/index.html |  14 +-
 .../improving-firmware-performance/index.html |  14 +-
 git-main/user-guide/overview/index.html       |  14 +-
 .../parameter-configuration/index.html        |  14 +-
 .../user-guide/preflight-checks/index.html    |  14 +-
 .../user-guide/rc-configuration/index.html    |  14 +-
 git-main/user-guide/ros2-setup/index.html     |  14 +-
 .../user-guide/roscopter-setup/index.html     |  14 +-
 git-main/user-guide/rosplane-setup/index.html |  16 +-
 .../running-gazebo-simulation/index.html      |  14 +-
 versions.json                                 |   4 +-
 38 files changed, 1142 insertions(+), 282 deletions(-)
 create mode 100644 git-main/assets/path_planner_assets/Big_hourglass.png
 create mode 100644 git-main/assets/path_planner_assets/Big_hourglass_fillet.png
 rename git-main/developer-guide/rosplane/{path-planning/path-planning-overview => navigation/navigation-overview}/index.html (93%)
 rename git-main/developer-guide/rosplane/{path-planning => navigation}/path-follower/index.html (63%)
 rename git-main/developer-guide/rosplane/{path-planning => navigation}/path-manager/index.html (63%)
 rename git-main/developer-guide/rosplane/{path-planning => navigation}/path-planner/index.html (83%)

diff --git a/git-main/404.html b/git-main/404.html
index 4acf930..9351b4a 100644
--- a/git-main/404.html
+++ b/git-main/404.html
@@ -1066,7 +1066,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1076,7 +1076,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1087,11 +1087,11 @@
   
   
     <li class="md-nav__item">
-      <a href="/git-main/developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="/git-main/developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1108,7 +1108,7 @@
   
   
     <li class="md-nav__item">
-      <a href="/git-main/developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="/git-main/developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1129,7 +1129,7 @@
   
   
     <li class="md-nav__item">
-      <a href="/git-main/developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="/git-main/developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1150,7 +1150,7 @@
   
   
     <li class="md-nav__item">
-      <a href="/git-main/developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="/git-main/developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/assets/path_planner_assets/Big_hourglass.png b/git-main/assets/path_planner_assets/Big_hourglass.png
new file mode 100644
index 0000000000000000000000000000000000000000..a7b85c2823fe793cb8d422398de1c8c4ed2659ad
GIT binary patch
literal 40943
zcmd4(WmHw&8$Jpn2qG=r2#9n@hja-Dh;(<SbR*pY(jXz-U7PN1q`SMj&*b^N<3HXH
z=i?dUoDUAy*sQ(gTzAjwzONnpO-39U0UrSh3JO``i^z8<DCl}9s8_D=aNv`x$9pF5
zAD6wTioLwGk-d|yts#`OuDy+gwY`O@-g`$wTRT&0D;5S$hEH_wP3-M$?6?^jE&tCA
z4A!>BjN?TZpTR@k+I&&9gMvcUefjq)k3ZKG3Mx%QLPSu(`Om?ki;BYLeb4E2A|CFQ
zhx}|OG8U}pJB=U96N4Vhc71e(+Dgm)d-F!2s*o5}Gu5~pqoX>;pZCp-d38`U@cqMs
zw~wDBZ|R2+aB+{O9fo56a1BBNafgjlAtUEh1qB80q<&~Z@VdIJTMPpKT?ehb7gYZ5
zO69}bdZCxAb~1@ktpBdCC45T2?WBHXU(oIS|GN_Xolg7m2vWM=uQmVou&56^2>)G$
ze)xa)QK;!u2=X~!U9vo2U|{gL?M=$3&Y9$MWhgi~aWltEYVe7T4(F;lIXP_}?;Pyn
z$^59qU$)-w=W@RFmr8PVsJlC0Z?f?GpS*0;pFbL8Y@OZR%!d7#R*UtDWIb*QczAe?
z&rkP_H*29LtSyhKE!UNIJDCwrC%o65sczRt^b72U{W15R-Op}Pl9JFX?f!_@mbDcX
z?HwJy-Qfi1X9J9OyW`pXgr&lPC<?`Du};e#wYZ+pLhz^C_Wvp5=@-Ycdvt#+ZFF>W
z$1ftD1U7T*Lgmt}ow3ZB*;%aJ@`}pJv0cx57CZui0RrpBw$Z=BKYsjxSTBRuT*P6P
z8lTqok`@$v^>}xAKXK20vjWroi|D?WKTWmLXmw@fB=GS0{?Gm8zId)o3KM>KR(5u|
z@dz>B?FL4UY})Vw#BO)K_SoZ||8^t#^Yg=b<7qbmCpS0WTr`GIke48^hK#SfGv(yS
z_^ePm8@*9=4Grg~JtXG?j4hv;b{^%~+1Vo+OSMWF$Mv6ymfg>hBY3Z7(xwQovAf%R
z-z4(7u}6QDcFpS9pRJ@MCMNcRXoHR7aoVhS%rj^;era$##AP;sXEUGrz{*;6(oC7^
z?DH1mW0~`*UH~e|)0b*^(#{srVnm@J=3>P{C8!S{K0tl@_N`Ujx=A#aMsali@--aX
z84z=Ha<bd<_2FVe{MF(7`s%88aWQ=?t@4xb&7DWYQ4F=b^Qu1%RGtRJcD3gUhd~4C
zsZsp;;r9GuZxWG%gX7@fASf)%V6s5*`moY)02@<uH8;(3?XY&adwLp&fPg@))@o?B
z()ju8mh!^~o0}8exhm81+-nZgaX+PEwNDOv3P4fMXQxlaKYv1P4JC_fX%PbrH68OY
zGBWN>6$5!ad_Qo2Cw<);1Y{b<<8(v_b#!#}(=^8E>EZU`U^aR?)$NyNgX8H@!?EpJ
z=i4}XbvOY@Nd#cP9TOALebJQbYiq#3a8&B;cVQwXGR0A4()fl@`5#)VOeYY;KlAeP
zKHEQUY#88kSbbGe!j|QKWCbe>rtzos5W9s@NX4DptVb-@KD!+^1&U>^-fpK+^75wS
z%jYudv_d%^&RvdflMoOfCWtAM81%<bvsy3x0Y=0-o@ZrdwntL4YhTY_#qjxyf&!*u
zfdc8rk6WnM{(*s&?zd;+u7sq1H?{xyR?NkPz12dUpo|O(c*%_+j^)m&sW=ABdYhe5
z(yfuSk=`isL>6NdsP*pfj)8$t@B)!T$s7|EhEjU^`Vvx7`oKc`EzzK!ACJ9AoEPdH
z_P@7ydU)QfzNvRQmeJ8!5#Dz{Zo2*=BV%-bb;xQthxt=3Q%tVbO7o+1l1Q!9;?e%@
zP+#BbN}I2Wx;o6t-d=xaFb0?F1r;eNDeC88Ajww~ROh~|=2Kxn$k<nVb8~ZiRaf|I
zW)HhHZauD;;Jyc7Qw9bGD;paMb-YwmK?EFDk-vZY#K%vQ^QWQ-Jz$L2zxSh(2Ug&l
zn@j2G>3MNDkMriu8}LA}Y{^)aCResr5;6KTw<E5f?KR$R<k7UsB_H_tTU7Qmz~A1z
zd*@Gz)7sYNJ(ekMx7rT-i-g~E`KcoSnHCA6gOICZ=H;A_%we4|vHNtfR=%9fY=|Hs
zAu*WBd(UY83^W%U91J<W0>XXRynbA2a<y7+_E>gQR#t`rvOldQmW3yMdW$!PB@{!=
zVl<fUdbzh_&)wM6ln+F;+Pl*giZf=y3L?^F^YQ8FX<Jv9e<%(k^k{}CVyg4n+a>39
z<Q(Z_F?)N~#RjKbujeOGN4Z(>CDVU-V<a`xMXHr2Ps<Vi?(XlGYnPh@65`^NK3u*S
z40wNL;0)bic<1r=eEnS}sCL`KL_hflOVSHyboRWkg@V>TlGg)&rXVBpVYi$^BO;O>
zN@9Dqmn>~TkPFEuGw4HKTU&G9%g?Q|-9+dJM5X-vxsfS7mbF;vK6m~Yw&TqYC#T%>
z^c7U{T(7OmX>Ces>R`s^n>CWj8z(|uS4>96()&5=mD-gjYu_p~q0a~}SuXS)8rsh>
zla0YdmTOB{8JVrAV)fUrUoX`1GBf|KUG_|Fa=WguSrq~yxI05Ml=$Yx%NUdS{rjK5
zi63?EoA{=mi#O8{P*C7JlO5J{)v8PcfpCsno;}NlThVZEdLVY&CetO0Bu7$TzO;69
ztb5~}z9kirdr6*UxGCHY&@0ihd=TsV9uhAkf$iaxR}*<_&%a^<{QX}&=;Bu_SJu|P
zan6bz<968VJX&lB4h^MUh)YcDi`Vv)(9wBcZ8mu~(Bq6LCnpDWU2Jp3bnWWU0*sW5
z>*=}P`IHRgm#(?FdK>PV<@s7`ZQUUuc)5ivab<YjPeQ`Ncp%1Vd)`t2=KwE<eX!J&
ze0#n<(d6c&R%7wD6~w_rF1wEr{7;;~vsXa`1!8(bNtxST_FxQh*(>MGSmmAhT1F)$
zC3_H$n4q4QHu|D(R|83QKyG*mG*(ttFM-C-@3rUC?KYXZC_QkR$VfDHi<y%zp-fdK
zV?NmQYGn@lQ*Vwc4f=lbH`Nte&eu4*x#4&=c|ChJ-yiXWiIIa1>W!rGK0KU{P=&Mu
zy+|$AI~?CX#l&Euknj!OoUT82vtWYEBm**2dxrbvr1EQ6*iY6=pMl{8L`0x6HeH~X
zwmiA6@?ArpfOiE^qI-5WF(?Qgn?d7d)U+O--J%y{kFJB+O4SBOda=wXKR-Wy<oczh
zC6N5j)<PN2W{uOLqN9bu%D2G05XIv{`%hLoTn?+JdxwXg2J$;vSqt14FP;<2^?ROn
zuR!ox#<BMT@#!T-*>e-g$jB%ZDuo-Tx&(aE?|xWa<Nlc~6`wJ^zq{CQP5zk{gvx8o
z%hD2iP*uqlWas8$U}ARu%a_Odq~`}2aCvdocSJ-(AgT{)hM;BqiF_%*uvZ?hm$#Fx
zn^%DlM5nOjVx~$orGTusyq+5AFiHKWKK-AHjmE?J{(r?A74-l4@c*WaGaz1UVbbqL
z;saH~@87@Sk&!nmNBGFe$krHJMod_3FZUD)iHM%3D*pag9C`&76f87*B!^(p#`UWz
z4@wwmItP(>Jw$;_&*FAv0Rm_zWtw~YT30BS!`?q_nFzbvGsB062g$teFXdv46Np+j
zcXvq*Vc$i4j)Ymw{sjdf6P$r?29qPF#?R0H@oPdWFf5Y0rrq7$y1Kf^goL2zXnBd4
zmkKn<mWrGl2HXXzGylrUO2`1UVwS_|tFyDSnObWSp!x5s?BQa<$?TRvp`rI3PY?)X
zV`~fB)8qci66(*NKmV&*GiD?TH%KJNdtesoe!%#)*(}!|>8Q2vQB&`t-nZNzHE{Cq
z;4EcX3jS9aH-6Z`j*8cE4ZgUzXjj+M%YaCszX*eB`eo_QpFfY9RezwQT(0Hi;=&^#
zN#j2#o!%eYzobwESpwX5gUFn54>dJ4<p(n5kM-_$OJH%~1RUsCSccvG|JBu<nUU`n
z0~1(H(S-w${tEiSiHL}t^iifo0`D)=?HJTd`u{x%-JT>vHjPiC#WQ7E%Pl-B>qC2c
zy9y|wNEp6h{HLMph`~(tuguKMHja)Td3iN+a9%zaDUTXF)fvzH|7;l#_W1wE;X-}x
z;2C=f@uzmT@VK0vGWm<qcu6U)e*gTyI%EHfzoBgbE0%!U4(I(-&n<nV9U_XmalN7y
zO4RyaHJ;Jldvsu>8G}^4zUwUl4@h;cE47C>jzW{{TZM&$QR(Vx5V-bYkuNhw^$<nx
z-g2}#)C-iY5}6k}LH!+zaNq2`Xt#33Ho;y@e85Y(Ug2U+YitlyRu$rm{*l<HTh=$6
zB`ei;a-^fDTIbR0E2+xMH?w;#<xloSCLpfs$vKhxE6DWEFwwt+i+ct&bs^;B_1TG`
zBvo#RYK`!Lo<DC?b6N@R@j8e6k~B$e32#JyW+XJIz3loyPLZ?W-I{SbB)rA46wS<x
zx9E{`r)Wr7n~PGgmTr_spp(jk33|9&U;*jN3_?$QvQ=!mw0Er%$EaH3e~)NC+ca!j
z6-DDGu=-QqAm_a@jK)U%kZFKcfEk&t9%sV(t*L1@&V7)z-R*|5t^(DQ_|?8P8|>Q2
zU!85EBeR!yGZ6h_@}FD7F+r~ki)E#w-<_}YwoYyTR<Z1YxQ~_UrY1qX2a07*>r&}4
zd!x30xOMAPKH3y2emLyN-d2gii(B279IzlW5vjv<Lr<_z3z)FNwZr`kk5(PP03qK>
z)%f@o{S#`^SHDatY59Z?M4$YZo3w=|YjS4s3#xuce0$M&OUE}TO68<GYYeBy8s7B$
z-37Hwa+9j9LfHq3xAk#Cxg6nZ0ayN^<vBQ;eTq4$OO>Bi@GM;ArVe40YPL$0UbfLx
zVcq6!tvekb>DgB$tq<$qnlzk^B{Za#>THj0PamEkpo1|%&-TjEL)W!ji{CWq%%Fo{
zR0o%p5LO0jP_y_Yvb!#Pe$!yo;q4!pW;$oIZB>ukxcbHBg5BC<%{n^Wyl;U<xaT^3
zQz{4Nuw>R|pUmPJ-ccrSj`!>FSK3Jqr|cJxcF8L+)y=t4wQ;3SPpWa7WKSXAzksGC
zsEng};(A-Z=^f4@67DM|+nzs}gLB@MVzWUxF~r}0p@(ur)+7d=&>#3f$XWkd_~2{R
zbOe?ap8-xE<DHeoNQu8L2Bt-ju&8M1gr0eJ*RWb>aueGT%GB%nd5nW~k;4#~y14-j
zNOsig#WRsiHhN~c%0knj!<$)~3*$OW<9f(VvXVg|e=p{*7tJHuZEs=y<{0k0zYros
z7$1dJElBMO*cxQ9e^0utrLMiT?7E;sB3|#WxK>^kqF@_kt}BW7wjR5rRmb4Ci`6kj
zcGKWHTyC^=bW);tvmmT1T9$PO)FB-AW^vo;6otw&!d{${TsvHX*w4kngnQ~2&v}+q
zGa^3yp<cH9Oc9lsoS%`9^QIxAo~0$7h$n?-UHvaK(PyH(9lg-x6gCD&B^6V)ovIwX
zP}?))jV%I5in;*!`n2`7E&C=4Wi)f04NGXWL@gKO>Vy1rN|r+zhinaehHm;GKzV@1
z70ir?wU58(jHOB~)J0#nKB8>T{YdC>4o9({J~F6tL}oi<=s05h=Hw+I^Nq(MS^8&d
z4l{2eFh^!`%H`JjOyw^#keJ>WlHEKmt9oJY%p`ombCRD@kCeDX8+`*PcU}%f1WvZW
zT&aU+Fv>Hrk^KP}eHNTiU)O1l8W-|ElE!Yxf47TDH`hJdz&_dSW}ype5Rhqp2c^tI
zo1}F9;oo%P-qJ5;p4s$i({J7v2kzgQZ8^QjqxF?x@NAo56q&D?g&G2s=6q*Twcl({
zM;$4^G;Cp%A?#Zw^?!Y_c>m#?1zppHx14p6O97Mi6CZrxkW4s_C$aChFyP;sihX%U
zJkcR2+XC-(CwgOdbVt-Ym)iQ<Be*lQL1KEu>BQii=JP}jzO96MA24pgUs@8zgHHE#
zf8vk@QY44N!b^na)s}z`A}(+X3T!`Sze|?AT8k&YhnKwzPMx#lH2&igD;ov5Qba-)
zTlr^?#OaK^J@F1$FtLP{w|BL8bkHm$dDNW$lUM^DB?SR%WTqWi!;y}LdRS(XUAA6n
zc1SMF@l{^OO`M{$^^k-TadY=U@wSTB=ioGG+f%A5gwA7$(P}jQBS>fAKtz-=)7oLy
z_GL-+F7BG|8OJ;_rs&`LTJp&zqQ9b8=<*Frj8C}T9_PDqWg#K3`Do9iunjrUa>YDW
z#UFiSQ}kSwz|J~-Q(8O&NgOpd4w{iKXjJ;_hls1VCoXgnf5nztvcF0$Yo1Y=k9W3g
zE^%~UYT?t|`*^y?D9+`@8?8N2%6u@^og(rM<dtr`aGGaL2cJ@>k5HpIIUMqCQ(eVD
zIb5f9mHHaF0hm>&#^<Lvs*R?kL)HvAsatebxi}rWT?-c$eo}?Tqf<Lj_%5)BK!<z~
zShy)7sjb`_yE<)+A)7@tA-3(+qk{ylr?DAUH-vkdVyP~!eBmI}aGHkGhc#i`5omnQ
z1m{pDI~*mMFQfDw2uNZdAMJy%0!yGzH0JlhtW~kXb9NZ<CrsI@ir2;GxudyU4e8Q4
zi?a40*1PGm{`Z%fC;I%%7LTJGL=nwx??-tsU65bmPH89y%dO`$h29l$uJDl>-@mRE
z{S>&Lf`#Jw^ElG~R4f|Jk|5*!w$-&p!z*wHsfVwr%gz^&Ypg$a_)SfMqNgi5U0n<>
z%uKhpdYs06hBn4Zw`<w$HQM*S#K^xeUnISJxYQkW?Q|G;|Ka|r#2__d=1P8&5}bKY
zm=w-3H1tyJJix$Z_HRW~(*?EkPO`kgEz#^SJ4CT4I+MPhcgwV7MX<cFDRbhmt47To
zqhc*MfTPYS<qzQs56s*pW0!OPuoEX(P;j<Y+N1JghlV@6J?!byRCzwPbN}Q=jjly4
zwt<61J7dF0WaA@2y-{g8!nDpZUD$o|`%K$68fttnp6~t_0mN<3Wf=I6q&M#C5EURz
z$x(BYtkWdajoQU%0qAVRmc>Wuv^=!G7aOc{bkhm`_)mLriIqi=Up{CKX(Vp`PFIKX
zXgY^JUuVdmVk(wRP!&2lo>kr7nXdZS-F;lS+gV9BTbIy1?Uj{yMaA&8kW`m#x5U9F
z%oAU_cRjtD*}MtpLy|;Man@@Wd%0UvXCf-p-jMdZ$~@o9(riQ?3t7^}IEXM}jYKu)
zjVwM~-PrJ4@?}qS;z`FVC0UDr=<q)Tp}wydnLi#aNH1v_CSBZZ{$kt3R~s9|dKAl)
zGm&qAwlw1(8lx3<_UaIW9$`ptFnTj=Dy}n2RiV@p#;_+*L@xF-r3e=kWSg2wTCZqP
zv<w9oM8B6(Fsa~lU@nSjU{0Vn7A(EXenN{0l3T$yS<(v)%4ijD65i$X;EA88a50{I
zyX2Np0vV_P!1O>Q2yj{|w(yw<ynD)e29^C=47=V!G+Y?WS#KnEQxcjkp^_e#N5wS*
zm5&@|&a}^JJp=^5kXR)1!ltqfY66Hm2;Fhl2>V=*vCLVUOb|lp^1U`r=1x<E8g2rm
z#Cz0)PO|A$x)ZB;aaY?|cSwX=;MjdAC-$L4maH(psV)^9*aW<yqKnJyJBD1t^?kE}
z<VB&UD?-TD%DP2IXHQ12#d2h}8+u*cp?dxHgAhDU8FwQT3ggNzZB`Wej{>n%hIg4%
zFNI@n0Zjw?_ghzS=wum<?39W?YkPCkbpFSA8SkO@wsZ=|Q252SA@r}_#V$H$G&Axa
zw+!B!%T}1!$3UbiIKei8q$%Z99B%M|eHuURt)?@oKkpx0a>KC|2mC!H=p-Z<h)7l%
z-RRbvGrd}itb=Wy7s`>xI!NO6N1wwfIvmuj0Ma1)t*)~&Ej)b#_7PvInHk~8qFyw;
zUbp}yFsYX5cj4Fj=^N?4!O6HHiNk`*wNb3KkzCuGGy1)|`h<oLp?Xh=F`+Z_)-BQi
z)GM#7?C9#+l)Z-7@1m#hICT#XqW}<8%Xt+R0RiD?-gqF6{$Hs!Nt2c=z*`eJthG*Y
zo}uu#ZW}8OsG!J`lo%#REKS%Di1rj#ii2g>c+Eb^(|Gkv!xBM?=k(Hkpcqb8Zg`@7
zU8<iZT`zzPfX>A!qee^0040IU#75JQd$R$(M~N(@%rj=Giib4<#F2P(O*F>%SNnQp
zzh*CN-iDr3e0|QoW%G>V(%_^@Y6TnJ4LmqS?o1Zq0DNUIh36Xeng9uo+vz9_KnmsM
z<r)o+;oy*~Z)n)XbKD3cAS470Ud(7P;S-%kT_iZpG23o@p;5>a0Dz>_9rY)>bFSaa
zw($0~>xt}>QV%y>*{LnGmjRBXpQ^DcYe+iko_X#H3r|K`P=2K81l@-n>_sHb;nVmh
zH)sHxh}gNAL~5Q*Y-M~?Ix4{1?l#9(HBKVpYwDuaXeRuR6Mpxt68jc?4JPj5=ODv3
zC1qD8=+t;z&Rl&XS$QfNqaN$w98koZ&<&oCt^ijY250P(tE-Q6bYZniuAw;E?orh8
zIXae>LjVKG*MKmScwD@L0ua1G&o82{$?V0QzDHfjiSA7uRgK49+|%t-b7yz44+{r3
zEmp{VCM4azc`-O!^gn4<c#(d$gASY+Sh--fa`9Wod}K{Z(iAZN(NY7--z~f_8Uoo5
z=a<8;QU1uTeX^u$F`51*9}WLA1bUJOl;^Y@@#f5)xkj**d-n}x&*Su-T+Xp_L%xHW
zzq`unru<vbad5-|at8L!urSr^;RepNoQ?-7t9+JoRgmNRxms&k4GoRpDFh~mMd~vo
zu_VRwbO-5Dbbe0>+lq2M=gNY{+cg7QxFQ`%f7J&I6S35SuFY;fR;d7+dtbDQT6gH#
z+W&$9{EDLtAE@rqHv`q3H|N7eH1B?^JWjalTxL^msLcv@n#8=lPk$zZHzOszmR(3@
zus_eoWKq^r?Oz;K`Tl*}gA|AAfg1n_fA0Zi9GQ|5UR-=gLJax}@e2zJ?WHWt%uf!*
zlqH5`dnasAT6-#$Uk59`VY1@;@8D~ROz({N6D%e`EJ@e{x5uP3Bix4BX3n@F^GoEF
zO4<u*GEmnvTMVior>1oNqiddZ@lLz?xR&M=7hKQw*$5*P%PIGb-IZ_9*f%e<nYcxB
z(1|M4VO+Yo<ZQtB4oQiQ$fSEO_n}{8H084kGe9h#gs-`Nti5h)YokyYBWVJNhrcC;
z=;lPYG1QJmEp#;vH`cCxJeD`{)#r&!E>%tZO50_Z5({;Kp25x6(Lql;9Jmp~<g=9c
z*X$!YnxbNF!SRzbzo0)A(R6U}M{0Oa>Dc$#5#@R|kv-XmnrLluc{d>&WmC3$0_cUq
zQ-|tJTQ&AK7}jG&Nx2||!5gk|oItiy^>;@9qApTW?Tp>2y1Tp206f-X{&#dV;&H?E
zvfI38OGI?^MB1+{=*Ek2sjo?_`6v5fVMqX6BF@j@kB*D&sn^eWx0S1|c;6GDPkm72
zaPh0)7yd1F!w7#zZgSka-*u5nNiYgu=8%>xKhBom&*lAa7P*QKB>=mJ-^9XI_1M6-
zbNXQOB#GWsr9P`u{YxNxS0mrdo~pWDc!TpKHZ<@#|L&<oLuO#>WYhj_y=d0g*P61j
zvY&ZFx4fJ|Q^dOEk)4{F+Sw)1RZCw_&&Jj^1GI+x?~AmW?wXH7gM&$F_S!JG_Agy8
zTs@-x!I#|&(THKa7;QkrW-<J^EOm%bCJixb0dq*!h2Y?P4N)MB_E=vT-f<C2*{SL{
zM@!o!J`DWM39HgD-~SAvNL|&1ZowfK_6JT`eM;}QL+-ns+Lb(mWXG}}-f$h?@P9#X
zOBxkVqAQ%+LcL!V%SogyCp0A6c_NBu&?IAHi<OFJ&}G8qbUt|x1=?#}pdSJHKyrmj
z^l-@dFOZ~!q~sd^^DXLnPXr@Ufqr+`>iG!&_Vd&6GcKPyCqUZPK$}btgmH?i&%d-j
zUEZKr5~}F+(3!jcvBaILriV>Yt2{ixE3r-yo~X)JU|#CH?L<10ac`3wL2<5e!#*}c
z{?7wr@U}~qSNDnDJ~Z-2al=w3WT*@CJn~iHO7l1?a8y(Ni-q+J`5l-^9hhafl?Xu}
z(ETBJT|KR(4|-?*+S7%~s6PP=i$O#bu2g8a*&iE5#1og7M|E&`_yT=fH{TkqUMrMn
zB!ZVbJ*XUE_PDcm_wcygD=d|?H!B}pfYvxH+Q<wQPoFR|Q7nb~cOTigUwSrhXZ`jw
zOWHRX3|kKhI*q=!$xJ4!aVuNAa#_aU(DWprsHiuxXmIrFbxm5Mq_Om8{@tl>%4sL_
zGKy+~8_pA6Y@1eVIeOb>#>feCIHF@^bu3SfF6U3SSd~A2{^YOv_)xmDV}e4+`OPo(
z(L+<1R<Agk|ASXxS}uzxOe$Ha4k3?Ik@zfIXi$;mzd<f|^|Xz>D{2iyVxdDB{qi3+
zpPV3|weQGv3#UX_-#^WR{zax<$m{Uq(qw6mIt2D-LFFg<p(PU}=Sf!Ua_r&me*57O
zdZwiRiLbUu-rMaQPGmZAY{9EvE%&d4{hOepR{!(dFB<pM4$<*)W6t3rJ<ID?r?On%
z|MCc?P_7=);@rO_?N0+I)mw%qvgI!APPX&U9aZK#f0w<(e_PMBwY?z|`|F1a<K}dZ
ztv;Mr0HG}-M7Nhp<bm9BLaT)fDMSWB2Fl^R1=-*UIeafJYG)y??9I72Xz5yiSF4Xd
z4c>ZZGSHuxoYV1<zEsccXDO2PLkmRPx0@@58DVd3RT=`e?#NpXzmXzkbPI#hxsqKu
zadZ6e4>S~^#fMZZtXqjVW{#tcRrnjotlEZc%htxhfl#z(^e0>`o#Pye9mf$ex@RcT
zUG<f1dJPR#80qyNH*C9%UJL$c*j*+Hv#wj*cD0mc#|MU~qgKY%j`WK5IikS|qQ2-0
zU6?kH_<hNqED+E6s*{*p;jy7Lg(ZnmdPC+4X%aj|+uQS7*RGb_Ni);Y8dS67CBiup
z@wuFlphgT~fg|df&rwyD*1z$%k(Sxl+lGf0HW5fW`QuWIb#}c6+?&X~i}vGji_}N9
z@1*Ofa&`+9nlL0E+o;}Uwz0JiPKHS3t3oN*M?qFXLtZa_|G0kCgRS-JOiF73Q<Rjo
z@sl6N)&}JKkLEcSa_Mte?dr#pd;SmB&$(Gj``%9T#@{xekw``GekUdN_|zc|Ml=Zs
zT)q9cH#I8Jf|z1^O-4E0kH&>fQN+JvSaLPK_O;&<s$eNaR{6mVsPCPkqQuDXn=V%I
zA}X#nMIU(2J$;6p#{LW}?RU1Oq@+o&-G}LXSVF&Cng*Ef2U97k4a9H@1%0Re#1>jw
zlV;qvgeXGbcp7Vkyn4sda)>rFSmmmEd6gb@RX5&gqQGU#Mf7tHD`iL{d=p@eAsQ{w
zp>26S*b4{Q;{OPt8#UhI-a;#ncb`udWZ$Hu$`Tl&T1m|7t~wrZ!s$-CLnnPp{GbT{
zH^Qdh!#MN9m5(Q;uIB8OTD7T?bIDM7YUVNAO<yN`74yuuB)fbGTjB)8WL`N=sreX+
z{v#t7ti_ZV7-W2?RbqI}R47^E7)Hn$xe=B+7&hy@{ulE3uSNIim5a(H9oK$tx+xRp
ze%_}Qg|Qdq^^<}_mCMyfZ3~{B%}R0H9L<6IsrfSbuQ;svSE*FUV(F}euTZp%N|YXA
zFMEDNnS7swNm1hCqN4#ajY@X19n$o<Az6}P|LUB9%rVEIe-uZ)arF4Bxm)q|My|ku
zJ<@4fwEE+xgCyCXlB-(`%J6b1n7Cm@d`X=+>ceY)2z%fU@zwUdYFne6;6;83zjc8w
z%0ezFnsH`^{draGF{lx22=IlFg_!DMDSFg5yd(Ce0!j@`aYt@RT<SOz6y|tQNf<LJ
zYH+!6KYC~h1F<pQ*U|PecYp)Ii&>sFi)>l*NH}-H@r{>I%y7Sh!h+3qeG`Olyw?#c
z3p)_wN03O^kmRkDIr<$tl;*oFJA-Ig1*T-av2n4!jsjY@*mKX8ys(R@JkqKJ|5<_&
zB?|Su&gr*`Lz)ch&)Cv8I%N)@ocaJpcC>_qQ0PdUF7<@(`Om7eg9Zj_vL7XT>3xit
ztdAQOi!#kqzGwsEtDG8Gr$ph}FTm$SZ4twIOPyxZ$Ed1GcBS`|V7MHsX|1hiLwkac
zcXDTciccxdoY34RFAE|Q{B&6VVGE5e^k5mBuR6FG)w;?%kK0P4WU5y_g$KpNeVY+X
z==<F|vhgp&Isgdi=JfFsNeHR!@Nn4P)@KK4{8VC}EZG?(cvO%6Gv;UQl)5!_bi8Y>
zA|Z{gyR4jdzx7)lf?PB7QDAfHEGh$S?e7czH9W<#L9E`zbZC}iB8$D0d&edeOc?mF
zF0|^4YEbrlX=G|jL}?*Cz3*m5TgJ!I-`_j6N<|sOX&V|-ESzifH7nGox3)d>Z_MTq
zxR+EV2@YRbVCcOk4WOIWneaC!<=rHEM=AnLFqqdV+9erv-A$J|x@sT3j9K%Kfr331
zX+);TFVUz_EqY0SpsA{lKr<Cd7*^rq!Bd;P_%s16K*L+7)COAf1nxMJTH_`>oUP6s
z_q0?+7!TPG#%0<W*ZVZ@X_VfPkBNl67Pq#Gr}JaN@Rg(3az^L3UXa+hq;M}<^vP6Y
zhk|v*u}2Qf492CHz*WnmxMzq?ND7b7Ol?Mf9Mt>;M#$7d6zt0>78gW=$TES#5Uz3*
zZDfCGTlO@}qpaH;xWSoCeW$+uXpt78+rt`Goz_~==bYH98D#qbpr;j&@w3&26hudK
z`ZY$3YAL%u8}8F)Dr|TWB~~P=3Ee)M8w3fETS6%P%tD>g_%BL?8@XyB&OCEAYey~T
z;bKLDYT;Cpps+nvTF%K@uxf3eIn@Z)79#18#5a-2<gJJQ#Xy$(UEd;!7j}}Tcl?i#
zN*+KMJcD=!CQ}f1W1ndsS#eg526!3Eu%@JY^s)X)#^E!*!9J?*j8&h#;hY_<{o4Z4
zn#zk<Db<OT)a1Q}hj?6iW5(io2F3!6=chmBDl!eAAgw1C@0-Mz$H*jU&S(Vti<WP2
z!s$#H5dI^8a#e-<4liYMYV=X6hNyFI#r>`Vg>e(xBwaw?7k>_?Ft1$24K}&qtDMkT
zI89|uf|wm;O@2UeHIfx3&Wnv^P;t(w2%-RVnpSYyXI8~@7iU#A4UT-)F^6Epa#q@A
zE#hL@s&n&7ROO!RmS9O}UI#u&4CI#41qwvcr;nL(hVzO07BdxzkpuipT9q&aT~+_w
zYQk}*<YY6<ISCII1~u}jOnXYQ?AB!%JgsUjkgnOBxUi*ttf<%1rv*{67UBlR`(eVx
zNb3V|#@Om@nDe<vEO>rh^~xg2DamKA;CGI+;_@R3U&^Skxgb1{8@e)+N<x63;|`iS
zcZsBS|6C$IPZCpG$oAS4`s!ay%uIO_R*k1CX%T&Ggl(0lFVxG9WshC^AXppoqq@?^
zzRs0)ejz&u9s6LtbH0fjvQ$pI+!em%{=j(A{~WtDM{Xih>Ni2#cUchH+$aC-{>P|l
za)SYB=kXs<Q=sz5q;oyMz^HV<53!B<yhEN<<knr*gO>3O-xw-*&r%8n0%pW?^w`4M
z$Cm|bSeiOo;!=GJ3aHNBlrNmx|2wy6(6Loh(!cfg3|pv=Roa!>{k!-}x?fj?J*lz!
zxsAq_Rnm7==h*7#w?9?w8L}8Vp{&v7FW!HUGmH^4j<upb==ZYQ@T<aQzg*GXa3C{Z
z7D~Oyy^0)|lhhXg_{c27o|B%OV!ZOTpQylXpzF(KY<O&3^Sh@DQ_e_BV{RtXeL-l(
zhfcIb*TzbDopY~G7LQOARg6h_<tvI4K&x_A8j#qbhz7<V_S0g-BlrHhNsBx7Vo()C
zFlDCP#QSAWwu1R}vY@qL^;1j^cl68BL(FSnOM}Ppua;sXX#|zQd?kH>+jxenx(ucG
z*>26m2BB6znjw~h#7~&>)mHa281<yB_2O~0oR8=kxVYgo>LVJ)atmBVBSm@%j>yrh
z#)$XUc8^IJ)_0gSlXC;+-yZS-F#H4NVe#O^@%Q8>DIZYFSWMq0BZVL_IpJks<{usQ
z&NsC~#y<HSufehKdJ@TQJW9F^5f?F71Ry5&ITeQ}uKz%Lfv$!CbY-|yT=W_HxM}e0
zMxRw$yKBGRL7_?#wl%%nhr4M^EL`+hzGpBtWc;Xoh;HwdVCq>dBntrDT__s$hDYck
z)SIj6+le)7y}>2@A-)kT7V3mU<8fo+4S2a#m1Sn=V6-INk`swSkCjuI8Dy#$F7eW=
zbIS!$6p}e%F9){J>iP0Y=Aj^Yoqg{T5Z90ce0}2+X|W6i^~|vI6J64M1)Sd2Q;7Ol
znPw-rwt}Y2$?ph`PM8_so{OUqTFCCRKWZqRYY%akw&R(<HpI0y8qD0j?VcG)SK?rm
zll8W)gGga#C=Adum2G`NN7Tb8YpU>lH^<gk%B$ksGDiDadi``qC>1JY$=yGMnR3h7
zcD2Q_*uXpJHyJS6GuzP)dd^7a(5q_0UHDU*kc`oyB+8)zQ9E{uKa91gl!q&&NJeaO
zbL%!1)P(Aif?WYS_z}KI5#CB#PeKbXjt&501BnOIq%Dh8%|m=M6>T^HQEz;rZ)820
zZ!Kshe1p9{TrD7H3~GvSeK4;7Uhun+et}t<hF(zlfk?55&}BQA$*QKb@4DgcO!WZU
zb)z`F@FVu)ByX7kE-VVxm}t27op0OJB(PRp_U+Q;)k31T7V}PiOGWzrj^sy5wXc}e
zW;65od;dMHYjpulRt$m~-R+aKPYE8-V>S(B2HNJ^oqZSo#!<Sl(7sui)w|9RUn1Ok
zOaAch@hsmOUPbUIlWwsgB`*uhTSG}^ep-=xSxt^iLD6uzi?w;dF}09#9WO_-1Jjal
zDx}T6rIG~PWwM9-S{>&co0hKKKRI!szh9ho{~?AGc!vUovivBo`z<zHW{46wNo=r}
zSn0%gp*IO{het5)v|oH}O8f1CZGido_sSLYgG3m&EuEq%V(EXJc?&{(Nm$r@Itr>@
zbit)HDQ)ZhAH{a2MtkoJRv!zzFeNusV(?S4tHm+%?WS2?*_2lYXt3bO5BJhSV$SSG
z^{tC3SVmeCW9DDqb0#)?kn0AJL39BzYyMu_Y|OXj*-t?OZ>By)PF7733fLJD{ZSS7
z7N?gdu};y_p}-LesbJ(8dFk1?w>;v??V2a#Xoj|2IzTCeqhvdx1`&pS&u<2{8@IP6
zEkEi|Q4O+oI|xJH@kRgsDrGs{mgjQbjeD&rmsQ}(b>bLNpH+>zb-x&KE^0vsu)yqi
zN7^fnUmYR2R6#C8nw?+3xB+3)i;sHEhx0%{zp^)HM)RUqyH9qmm{ZLVMyKkB=!6ZY
zWQW{}Lfc?0f>eA=D$LI&EhBX*Q;<l@U7t!o_;U_zepjK8PUTv1H3iyH03h^H@yKE$
zuOa#?)6a-BR@}pJ4`<;)vVIjY_HXxXl>T3#Jm4~Gj4!=8uK8iRT>&KD*vZeCvw>o{
z&^q>|zdo7~Ce?ei&J6==I$JX`B8GCD0_!D#Ktwk<0?Rbi_+I2k#gyreRw?>oJ52@8
zU()AAKFlH03G`fKE@Uu<A<Ul+$0`_1_=b(!N9;)_bX-_bTDjV*>GFePu9t3tBRy$7
zV#}g-H9gQLtD>3&YCY8t7dUdAyDFs^I$%L6haowR{*}~D-xRS#wcckWydXdCo$z5H
zc2BOBMwTu<PN-IfWk$#;Yz<}gbr=jsA`Zx`L;uj&p)9hB#S%uE5C^d>c?A~D`OgEa
zV6>EKzh0YKj{04SgDQ4SwWHBL#FoBv#cDJbaX{)1c(1{ZwyHfDZ#fF`Tqt98S{CIG
z{n77b-|+2V^>4CI-q@<s^3B;rHWy{KIAWBT;^-V2{2Mw>|3~mTT+G)z9f)(Y7c9wc
zIsf&3e&F_d14fe~9~A5r-ws)t2mv1^C=Jx}&;)dw6^GQsARs+sR+f)r4>v|8B~l71
zC-|2Z5?MPUl4dI^Zdsw`O1sO>;aC`gp1Go3sn7$`Kh4T-X7)aLrz<2BB*>w9FHr~4
zF_n_kldB0)=`8%pWHpg)IhR;TI#o!ykicZ~IGc+1ph&tU3sy{`p5mqc*xu5SHZo%e
z0axLwjKhg5gYew8YBgJi4Ua(6-`a6%BRIwK?Ep`!4LB~Dpmy}d=BWFB3nE0VCV7)G
z_=_Q=8?x`DQnrbk)WOg6MO8TR<J&475#LXBwDsNV<!7Oh9I6=#73Jel-)w4?m178j
z3jctif?y}#60~gZ&=j_jn&RPJqu5)9X6}(glOU-r7vTNl!nH8T=7Bo1CP6M(_`iJM
zI@*>N7Ysw0%|O`koWqqGy**CMTJ)=ANBrqdD-Lo;hAAt4c<7)cxg^JZ19|-|9NrlH
ziz{$(xJ?A9Bmvj!2Q}U&_IiYlq}LTDPKtcXO0oI79y_Iro!<&^8;?G8Y(2MMq5ie9
zHetnXG*4`>kb}!B=#P`1o<*ztofkvmqFzamGR%q|w~iUq+~-`>e&@UN;(Mni8V6sC
zSwa7pMfv*^2&|hL$8d|u==P%2hWgotCei&D)|jp1kMW7+V7M<oWjAlOD|*U2U(*KV
zijis2M@?vhGj9%#72htNK{C<ZH%jphqpjY$5ch&=_k2>NjT3f5k)(8)`4cPq<XqqJ
zFDg5*-uBracT>&(oSp01jl5nJEVpY^JTc1Ao<`a30T3TWBP++8^YCsz+FX}$S0c-p
zMU!Fcfb-<GCVY`!-lLv6^iA9Ubrc8mB7Qfo)7Ed7W;Fapz^D3F)K_@<+HokgeVDRy
z!4Tmz!i77@NUnc4{@vp5mvXLhJV}h<EZbW%=ADunGKkzRjan2+M3C+<X_+vY67N#m
zl)v?tNM&<AheIr7dt5U&*nX(~pf`D7el#xnR%&Qazbk-#hA5$9eNX8iM&sN2fqo+C
z&My`jVt?&USe+7u9?Z3_eXLSn|8G5(yqs=_Vhstpe%xZQ)$-90`+RwCWXj)(m5-mF
zn^yX&9*8ggS?T|=L|Wof*4?H=yT|*tXOxsWSnCau!s$A&HT#&X^eobv=z^q(lEh9E
zxrZAjeDV4~$jw{EdJ5m4N)o^bKX)e(4dnXJ6)glgNJ+g9=WFdw*F-BSDo!pgvb369
zMMOn)_4Va70;@T@8|;ou4cV~d#7tQc4$baIOKMQxFl3)jUcGMSH5;gPnj8Oa_wxt)
zK0F7pzrK_-$8rFGhs+#diW_liKTu*sbJguh?P+Uv>I@lvYYh^T^jC7O@xZR_mo{`|
z(vA8|bV-HK%UVxS+B-sqh{IrTcd>i0*nnegZB3(86a>f_`T6;Oc$`oGwE_+aw>6Zp
z`HO&nfE>xv+Cp-Oh)+q`Yta5q{L~sN#Zh^~{sbL*z3W0o`zNVi6y(csX`Il>O;AFh
za^5DX;kO6=EG`66dX6k8IN)*hDg2Z+#_9p<5zCYAZP681wbztCdW7e`06I%KXkGo1
zg@1jbkqwd>exK!j@wIAly)3J#F#_#}m#O2M+uKDaFDoksK(e7zs|o@*IFsGhS1^*R
z7(=1*hX(=+#W~a48&^j7bmZ7L4#6I&E^I64n7*-!M;y^cSZR7_MjEx!$-9KpU}5M8
znAY9DN1GzS4}TS5w#A_NIRm%`(Y)Tbb)zv>Cjw+l7%Cg#ZDFk&6Pg;r;NoyF(~6nV
zc~d_pG0NskCM^qS4#Yr<UMr8TO{oAX&dAJkxj(FhfI)RR;w7?d<K!u;_)RZ=3J{#m
zMCur2{qAiK%(xMqH1&pGaTpo$ck9ooi0w_G{qcHx<!)H7Xl`w04j&R1Q74su!Nb*A
ztorl%)Y>GUn8Q-xeH$MpnDsd^JE^P63bO5+9>QiwZU_M~dY=1CxADa2<m9xlXjq-q
z@|#ppIR>Memiv5o-N89upJ@P9W3|DVgZl#qrKH`T)w$}bsUz|K>W?>C)nC19Wf;pU
z*qnBuzceOwmMgNrLmps=V)mgh(>IHhd1$J<e)TKjCqaZr2M3mih8HMeq`IDJxG5<7
z!PIwH_kC_pfqJdg50W`DgN+0=oIe&Hc0$fxy7Gc@-bi6cI$(aRIkdF%hTI`f#m1j>
z?($;HvW;PrvnT<IASWRX*NPLJ&|^^36_Qy%BOXEg!LTD&WI;{%4Fv(_7iB`o_iPeH
zZrKkriaFsJ(CHO{yc{pJtb&E06QEQe;W7JRP|Bn)rI1O<VJaw!%3&hGB}yI1Ez~!B
z^9utT5tGBjhpQiB8V#SW-#D9C0zfWLkZC^eZt-IKw?%IEN~_iy)NfAiKImtDrZKg8
z2@t7TXINM`N9#wd!xB~2!9`IbQCQd#71&5cFIGi$)Sg*2u~NUArk8`m);F+?o0C<A
zQmqs~FjzZ03@3ZE_eyTd`)$jEb7P6ZN7_&B^oAGU9$*0LeN8H4xc#QT>hrAkR6n2C
zj?zTrgpG65F7{|Arn9*{bof^l)flT~NXOHpw%lsxXZ*sqIpGL@?1MT<?@Zl0cqERi
z&`?*vFvC*AGXqmWMWo<c>KfRNku?4h&<g_Gk9XeQ-Y={PCt4K1q0;FLdIy>+c<Sov
z1q%7?`=u>1T1$@u+r)hC2}VOnAk_G#rIEZ4C_41%wHgyvR&*>ZEb`=YQ2@h@Aufqz
z>+VnkNeru4j9P>5ThQ58FiWD^5n39+YA_ILnLn4ozkYFirgEfC$HGdgJ=xxsa<VS)
zPj+8$;cIUnlhdr>(j;yC%-yElhUd3X>>lmh`XmANDZ&dEpMQUO-g<fxH6wFN^<u4&
zE*um?8fHva!z43qu;vLu0QbWVkdX>Ndrl+p#y6T$R*x0`7L5Mqsa3z2h~d9HIRhi3
zGr(_vj*N;D1S8fa6FJD0#v@yRyo5x;M~H)iBNjo7EMQ?l2iQvMi%!d6!k@wY`SIHR
zcq!%a{u%@QyX}6lw)6;G>%1J}`3}M<KRBwKx!>b|wU7@Frxd#Jboy|d#?>WYi3C$c
z@T1A$-Bgp`kMntxJ=B1pu@$A+1;co1N|f%X8dL7oU4p#44PWSKEGGtK0+AsG40yXU
zCZ}Mb7`%{-6%&0}7aN{jC>%Q+1sSTnCb&5=$MtUH03<vi5s}w`%cP>ZxU7FSqaT6Q
zqx-z#i^``nRiyfd-;4Mspm&}2)0RfY#Q0TLvq1qt7~P(2{`u^J{*%w+?qvWSFcT3;
zC;>;Ntc=NMB=zx2&rok~D_~RrmKPYQCvIAyAYa)*H+g0#JRmWCxW0djYO}dr9!~Q3
z$&V@*UA|JKY8$=ffJ?mcARKABBs*yf0g49UwG%)>QD21{UYx!{f`fU({uFe%#F&@t
zRAzIpT8O{FPAEJS2Q#Lknp`SC+F#~Cf}Htym`zy9{9DbJkEWvMu_rN;kgDe0VqG1l
z<IzH25}WyxjkbhVSX^rAujJ%;4+l2urADR=A5*oe>t(OBsw!3uO-;b5(I3x}xaO4s
zV;ZW>?zb=zfHo)vs4J_}czDlG>*MB5;`X%ly%!RIHN?-sqh&%e$YNPgx$5kZ(|IkF
zT$Tu8n}|7TTc4thEtc4Ey$OB<7}yn{{ENIYe5g*S%7wT*ac-Kf1(Pl?Y4Z;P%Ro>0
zy;@6(MVU%ub~}B#&2l2BgbJ@~Dw9XI{WTm4VQ;nhG$3VOFG|vEr1HAOjqu%v0R}~d
zjr#ZR=zx)Oedu(&pOuvrcw~3{#D5N$folf`8qW92imOk-w6#ZYn#K?`X)y5&a+-b$
z0v#b%m)A!b9pM|KdR%@zT|x5-MRV4^K;7AB+?>gPVtLZa2Q9=D`(32d${yW^vX64P
zOC7RJVsKXn`J9pJnOA7+rd;0Ww*FM;*GgPNy?q>Z6r1AZu#13+b_Uv}Pozvw7{Exx
z<YEGsj;e_k>^A$cxb1fYO0}AB+06d6l&qG%wCA&Ob8(i?F)*Gl^|k5~VH3pi!L;sI
z2W#=C`6d)ZZG0h_z=$2oXRPDx>&>LS0CpBw_LlI|b+wZL`AGM{h0Qo5#m$SQ@Pp@*
zPoKBM&=RZAC@DfkvdP@cntUeDDNQ(C;fR|loWlLlHobk9Fzt_fgRFw7Yo`2(d0op~
z&W%7cIx8jF|NomRpvpU0RxZ`bHXMj!wOU93WX!YXM=)jp=t0fa^G&55?(W3(BTe_u
zVOpi)rHpfl?-+8De5`&p0Lt?dJvcInu@(=Ob$eTI<MmalzgdZ``?Xp>>Gy*e#ofFf
zRul{f<jrBTcClmYU<W*W{?$F$WA#i}fb)mhQeh>J4@p1shhNoBaGFw%0Y*mMj9Q|W
z_Uvs%oPY#%O}cuMtAm#7E`{U4j3AhHd9wL5Hvt$`y%C$cyTQ4++vJCCK+1rpCE@JM
z`NFVGdghW76&3x@ansVYRph^ZMFPTaot&(;NdvP;XM-#wn4a3;Q!vaFp>f_~sG!KO
zh*)oRMd7GHN|z#*Ihqs4VQJ=4d8`M|Qft4xl~05;QSvv_h-2<tedPgL;ktk-yjwuU
ztBhg3w2h~>#Ljjz_a;sKOP(vnPmReC-;%=<6PBpRNHL=l5VqUYjQc;hz;?IH$YaLp
zB|H4J-Fzdvo(bsHbnv3PAb^O7i({any|B#2o~#VkmP{;MUAe)I(*fJ{g<1_rdoimW
zfh=IG=ROC=d@KX@rS5qduo}w{Z9E_5@iKQU_u|<Xat-BptEr5YBDT7rPBdytZ*CwF
zG`?Zc4`z`)Q*R#M?B*6_r#Z67gzSdrn5~DQ^ZjGxO|+X;8)m<K&@Cx?Oh}?GEbC%T
zyFvcLwL2Y;pF+8^dwyI>0Z4-NVVfiC_BJTm1&er(-47XV8i@|8-XWGEppgDsM||h4
zr>Dp1c134AlG-(W{e&^z^!fPUVDRp8ACKSj^XlrVv$ONboOvl$fX2@k<~JZ~ou@rN
z1OobAqS<6YIUvcRrwDV<PuPDi*f66dRSwcqnjG-HPR)~&oZoZDAP`Kx;j`~u?qxbu
zquKt@F}#~so|XxY0A}VV<|aqKNxmv_wd^Zb)OyK)k-dcm$+fT?X6kD3Z!PQaNpliB
zF=$&l9@p-v)=b}ZnEG#<USrM&S-D(Wi`%3AbB*e`4jeB^db9j1G6Kt=N}|^8Otp$9
zs<bvOQ^|<1quSgw<8jg7EEYc@4zFYqxk?GuGacPvaA<AguGHo;>zfuIsT|9KcD{M4
zs_-6+sVoe9u6zVtCD=kOky>MR76fAbox)|EQpTiHF}yL4GBTnu51_#W&L3noHD0{O
z`z4wUbwAeOfJPbm(doq0;!I_<UgFm8Z4>>jye&Z_Q^MXe-?qm3YOW~`877T}fTOt-
z742C>{)nFm)9>{#|B*mDT6sOTcD=vfG8`^R3V6OH$?vj+I?7`|aN75gy$@zZDlw0%
z_e1l_x?QBnb%7N-2))90Jf#d_-67`pB=qv~0wuiYbcv?vXu9C4r~xc2EFr(=A0i&d
z6Og=rfbt%jPUTxnU@ettVh-2Uh7c?1U=J9IaDw4a%{!JFJjEYe_#T)a&p4*t5G7cT
z`<bPrHGnz?;w*fhDCWXj5c|c_)Yvhq>PWv}Dd;as4s9LddY8oW)4yHj)GaM7itmAF
zYh$LKwPgCKf(&11--_bf<It(J{uK_q0jG}L<raSMTLUK5Y8S4&s;W7NJm6OedO)oK
ze$#-8oxK9B-8aiP*{7tmuqfoCAH)<4M+(u5HrJq*Z~G)dD1v5<8^#qedf*rF%{I0D
zn(U-&%?`hMbL1J0F|t^&+E`BO+18At+fM0f99!|F=Zl*4e!+Jj{6e6PM~0q3*E<xS
zu8tn^pjS0I`fY14u>*_<wgHEP0AA_r>@2WsG;HjEz(8?1l5sK+NGcvm(Xs<Gr~vFJ
z2+&7D$;PgOVo!U%sW7pS{Nlgij{He1`>TVlCq<?RjSg<UlPzvUg|oGFXy>pffz3HS
zZB;`0sRf3)(unrqJ?|!~sx|(RiQoaQ6Gi5Xk>;ogtDnFBJ8WzvjleRKT07~&oG+tT
z8TJU5cDhroHt1FcXP3VOQkQUioQ@O&%%;cGYq9S4DOaX*rHhe~1Cm``h)5cD2Gjal
zJmaLybL3VZMijcMKHNx8Mmg77-PCx5>?E~OiSnA!0a9hwj8Dl;yn?(}dZ2GLg!Y}#
zXAwhGx1~Me_N<yo)w+GM$~EYl8%IW0a}JiTwJ6I61Z9uH|57I8gj^GHC<}3~R^BKm
zGRs=8x(>2FSX*Qw<OKhaDQqUZCJ|8C9<#rSlI`|GTa$a~IDqo6-y|H((66wGO}4tA
zduL1Wg`IG`=3)Ay8OD<J9`~=h@ax=_lZc#TFMWA+VH@Mo1<je9_wfWj5UGPwf@QDp
zjx+=6h4V+kBi~h-EQcPUjC+AGcdtNz@D=^8q6agVD*LSV`RY*&4zw?{7DOjS-Hqn%
z*Bhxu30Cx)Y(G>qL;R)6aZ?`Ugi=@fhwKSu8M`{15r5Jtj=*`C7iDyh7pP)fa36M{
z(tvHtf-ZYk;~#?yv7m~gf_Ruxr{bYdA|F*JI={3l_Kl`WW4x?TT^}p1qzkDsJNy>y
zo>TGosGAyM;pxbNv*2G~0AH%hG4TkHXCZ)tNm65MWW?-#bF#)=BzhVdLG51#&#t5f
zI6-==C-B(zRXNSJTi*AMb}d2}Jq91vz;H~9GC2Q$5ibK{<7ZtrN5>jE%+sKS!%g6w
zblypB$>)W9A8%98d^jR9g0FC43j(x}qb_<=+S42REZF^^|1ZMcGOEfgY}-Z<L>d7>
zQY59j6cA8A8j)^Lx?55jL`u5Lpb_a-=`IDNyStnBTKjpvAKw`781Ik0$8e#nb>Hir
zb6#~Gr-7plcF#snnqo>O<s~JCL$6K)j4G}=bI}>RWZWMKgaJZG=~Pw!6VGSkq51p%
zEl^*eV?KU*j~_(ivF3uK>~`KqJeLIb37*p<t>sfpq}9%n3a9rSiLd1=SI21oTyI86
zs%DN4g7Jm`mnS&p?FMHWF!cU`-iVejn&#K9;huhJbmiBDbgS_pk8o?**w`39_+>Lf
zLU)CG!u;VkAU%}-1XoBGyMR!a(eZWM;=+XV)b8EC!+a_m+lK~sEl?xQkG`q3GpxPp
zylAwwAJ|xh#?dtPg`H3hLB^(lU+<jlTDKO{;?#SJo#>_m<L%cT<f9`5zv?Ol)06P#
z^||sb=A_m}essu&GVW*AL3s39^$X0wA*vnKH8n)jrq<T-&z>O>F{`nxH*3+FK4ErD
zco^XJ+(L}fw9+&9Z~DL2eZs8`jCE23UA;myAr><U#V$TmuKH6G(Fy5hJ!x$Cmp^up
z6I@ub7t+22nD@=OpGyf`(LAP%t}agwakjfN(9!uS<i~HbOWlDu{Hc4&i(*xvLPx+n
zW_Nbj)v<3d75EUBzxBgbcja)sKi6qlJHH?gX)#}|MX<c>>zWFW)gQv5<((S}r-2QU
zfodj;Kg^pA9PyF-C0T8Ow&o?9Z5xtLF9{X%!=ZOmTFpm^>>ix$Z2@yECLH;JzhwPv
zIvFe1S`|_S#Egs{$*1t48UUgIRPMoA6&4`U#)9-9Y-8YUGDe`f_LF~Io3`Sy^k_M2
z=P<9++#AqLTYQyB+F5{3hx>jbA2XQgkT$pZb~Xx1*kU5|)V}|Cg3XM(c)q2_GFeKt
zHC^IXXdrAO82bI_Emu`jbNIT~p0y}`QGri1IgIceV&!X{+D?hOp|D&x8p*z5uir(6
zv0M=(sR(jI$WNZ0OgdUk*C)M<q2B|*1L0^^clk`ygkvneE_Dx6)z6>5WUE3%GrAgO
z&B?11yC$4p<;L$)@N&D(dAl|Z%iyV7;^gRk!!Ni0?z3uqO_m<v9^_;tDON{s^~Bw`
zh1JpA#qq8ft)b68Glqh9uV()U6z<SgEaabwC=+DA<|L69Q!h|nB-pw4>VL|JaEET~
z!r13<g{AuRyA_J#of$=d$$Z%O{x)6gigk5dv(rLaJeF2fRWQjZh4ou8fyXwQ2ixaQ
zF}5v1I+UZ^v#MKK`4kPv@0C@@j0sSqjm-z@G5^Z${=S!{CQ&f(5Zx;UbCls=;hYLx
zpzOVLgwl~amM2y7i<D#%((o*YvTH`6n(wM1LqBt`?>oJKFEY~-9$6rqAd&G|8SKvf
zLW1WwIyzceCz$o%qwCC;IpIJDrdWuPDQJ2c65G~kM#t<PC3TxO_1<jBGZ8p#td&d!
z6gb>@KatPsq4Q*6YT2ALFd(^LQ`|Q_;x-P6yuvm5i1m!0$tX+miWT+4mD^Tn9pTot
z4mIb`@?DePr<KVm(gz3<MXYw2Arg<wiE?ul1bhToH!!%&FM54SgY-=?1K2Sq?2UDo
zwHKsOt{&oqWiY=TzggGw$t$78VWY~fVAOndKKl8Fwyaq}o8cD{xr+il@{=9KErkU$
z)n6B4xR!jdL5^2hU>9jQZXRl~wfB7X?z;E1CbT_o?M+5<D`jM#TZLE9ds0If4uhKA
z!<Ex}uw|aWw`B_Ib{5Sa0g&P==e?psf|MT^5fq4TZQ7Q~vg2=}IAO3C@o-|r5;>V7
zz2i<To)j4cg@yY747?u&*xs#m{^Jykd=WQ3S;*}tNr5&n-M9P;SLef@V!gQWzoN@(
zZDdxO7rb!_-V(gV$k?_l{#5byN;6THL5i=~Ywrl9l}q1Me)UljQQ>dB?{sx_rCH;!
zL{+H>3WI7KbNtUfQX$!(e$iIYH60mo+*FWeot*xh|Kv(SH`nFe<6^0mIdf^Whl+oH
zG}DvnE|l`vjFaj<NE@4K?TlWXCg3Ecw_|kSZL3ZSFloCNUw6l4bMCV5acT)yq7a4D
z!WJ9%91t+DpnIYd+M^!_JO@3!X|D;WS;))}yzOhir!T5U3pgExF7QMWS$)$oZF@;l
zG4}T%ro-Ho?p!<~UT?lQHP&Vvm5ty3g$~<@&>^1JQlm$8khCahz(hAwllT)`>TK7z
zBD#W>LX>+_X4y{EIV2(W8$nV9dpziQZ#nz5Lx$QO`fJh^kNMe{n9u{L<dNvrApyVb
z^kwrEntxU`j_%hfvcWilaJ-wotQPJ1reoUD6*(WDO&IMlTkJ>LktH$Gr{7)0;c-n^
z5iUBne`N6RNGS4iSyixLH=B!yFYn%i1JoMV>4lDQO}C81-~{TV2y@I%{U0IW%*mg0
zZ(eGZTQP)<pewgvq1BKSeJ0W#xN5q&5aqL-?g5Ys36B{bAYx`AQS;nuC9Xf2_Goq1
z=%y~YMSUHO$<K9WaP?S?q7f}|B!-G|O+tS{c=e=FJW$va^JFS3AV$rVws+#_bFJ4|
zvY+hEtV~)uyZ_z`wsv-EpA{@7Q_5`lYqhb8IIq25saWLC{f|-dlm}a3c+wF6&GV{7
z#AgA<hURyJTZ4mxSY&)3p>U{NVWEnQjI2>@M~#Ap#aJwXN!^vTQRR5%wD7=t%qtW*
z=R@|-Orgp{x*(Z5jqU&bCxD?(;ag3KV5qexRC`-~Q`uowe#*Cv5`Gc&&Jg$I#@9I?
zYl^w9m%rH?#pgE_HD)I%GU9X0A84t1>xo}t2C9U}46t&-bE=}Eau)*wS?;PjFYhbn
zvt&N&uCY?%FjzKvb0v-E-x~t(PA2<0P5Yox0$FF_Qx)0QJ~vM1r0TB@4uuLCk!C-v
zD->$uB2R?pINH56$2})F_QlTIUp&cupk71HjgnxDxw|0bZ`(iD$3FAJ>8+*1dStdr
zSeu*BdM_x`5Ray==5^H~q4oea2F4?5>RXV!`1$*vt$oV~2??16-dAgD>z8UA<^V<p
z2TUx_rj2_U)<Uu{#Y6fL%TBNl$(gs}70&%_SEZu1&Y!-|oyf)6sgg8jl^GR?_Ppk;
z-8Mxh$19@z(ztg!L=>qOm_B-_mD#%rFrc6fR6Dz_->L3OL8GRO?x|JU|G>J6178a4
z9FU4*(krIRK?-#Skwa&H|H?w7C|hwe1~p6SVD5f*7PDvhH4kX@N*PiNYpt<Hi<;RP
z?!HG>ZI+ZLe2_(BK2?cnxKs$=jK;tDAtzd%2V&Dn;h$|%BNX@f#+f|KQ>qh;^?iQx
zv{Rn)lRZz^eP;FMp93{zz8!}0J4X#8_$VS5n`MDFHc*OXP)vUV<#_~B4fs&^M-96h
z>zXd|nHn&~FVpk$tpvT&@+=kY=e5upyPWk#ioTT~$^zy!d)oQJ8&*QI16C~7k2Z1=
zTJb&vWgF-=V2k{n_!-VUIVnKV9ut;VR3p9BW3Horz<V&_`m=UWI^9eS*YrtJkywbR
ziUHs{KB+xASVe|XI36CJ(yL(RvRF_-GYYDQh+nXO;dI`5Ip04+t0UMeSHN37x+zwW
zsK>bSk!WmgFwDYQYVgUJqKFK;0_9)3oddx)4KLL$M@d}0LQQSBj6aHgBD>%&FiLS~
zI7Y86x0IzL)^=29exCOzOgye0B1k9^%?DF?Lkaf5dswQG5WEl`FHP6Ki-DD6e|fr>
zEmHoX`lQYl5iSU%d8XiwrWqaVF+2U)oG0Gk4Y24Vo^EQ^2p*2RGhA*=6?7_)Qaa?&
z(T829)-MqjN=UA&(6+o*JtZWLTlsU3wS}^%m-OZq&l=DBWW+o^63NG}H!>UIosS`w
zw3!leaCF3M@?J@ET?J5-;Q&y7W}#K^!b>B}-j=otNQ1G)@JJ-ycMR&iqcEUe7R`Ue
zdCF*x2<-}ocvf6irG+YN<W*|UXX?w<R>eK$?vG>g+VhVZi~PD8A|<tq7(CtYrtL}Z
zLq17=ZF@o+?sxUJTsPM8q;HF>K?CtAE}9y?3|XF^m~E%u{y0?kuqzAH2}z}AEPH#U
zSg+I$Dvw;OVm*;QsS>NLKUo-Z;z`R{?+8@<5;afkJG#3wr}k)+-z(y3a3@!eD{j~%
zs&ths{-4XwyjFp1n%{$+p7q(}pEQYO^g@qTKS<?BZ}>3=50&jF)h#?_sAM;OSl~9b
zZa3#8_0iYLaYMeS(*J?lu)3sp7c#NvQ;&MwG<`Z=ms@S8Np6euLo}w3Q7se7tR-k`
z<`nNu)nZn<3u1@vFHAp-2X2eQhfDU4*^EA?W-=oA?oKD(C)kq1X4RLQ0d$CV^YzHW
zo6Ylx>vaoy^AaQjB_g9gL8&<8(giM4Bs&{M)8eh7Ij%p8mITZ=gC?ZZV`|NXZdJJq
zci~~y84K3dVI<_^<|wZiRzG=yK!$usD`$(XH!{~HfeM3rL!K=g14A%8O9r;KxOVzC
z#iumAJAOsKa<hlK!o)PvVfWQ6=cG(QaeUAvsRNDGXY`eqg_ZLPW9XE&e-m-~9R4=G
z7%;OdoIq`_)$OS93~1q{n)7)}N1aNuc<3W7bi~O?<bgl=4%xfWd%0LG#E7N{6Pm;R
z+fmdK+ZXP$KYe}1Od*s*JUM$8w<ckamqTG<c_|}_!#q;hvNERA##s0Lm7MIc$-fK3
zVJGq+Ew44hg#dpL8kJgkZYWv*d5Tq4;%L!p>XxqY9yjk)=fZDOaOV3|jc~d(!#$mE
zSv9gm*&R^65IQTbY#}`Rw+Jw$$Lql?>fWN+DYhJ4sQkYl>Bu+q9uv(d@y=;WGJTud
zc9u3z$46u_y5SL-gY$2uxnA5I5^{f)bCQyK#_nj+?W(br^ul0TGx_Z$hUiV#uQ+U_
z>^9}9vjs-d8asInv>dq20uT5ezxBQ;u#HM0e*VDqY@8RT<TQ4mKy*;5<`%|c&VtEO
z`>xFs{Lv2(#wjNz8NHRLsHDm2MQ5W7q4qlX7Vu{CA&V=!)q}oP>k>!qHv-fYQpVQI
zUiH~lF(ZMWfbSBkeEm&IJ><vg{y!QWohwd5e)YkZov5foynSy1u-dA&R89rX6YHKU
zk27N2I+_r>a-r3K+8L-yrSjw*>aDit$T&^Eikhh$pMK~6Tl>_%A-JigfM}ko##Ji;
zl}084>I;&RPA`(a<m(7mN0f(WC>^*wZTx_Nq4OhOPOO>pb_Mx|vbgY?0>ZcNU7vAG
zFEr9#jd*OH9yu~)T*S+K#&a=bJIm-_NR-lMD)+cwwI039rW(>D^%aNJ9s)E@O$zzg
zyJv#5t=_@ZF7$B@{mS^yeEln<$Ep&aRY<1oG<CfSky_lGmmC%=iB929qS&}U?`DUS
z6=eLUvGjhUzO0`vg;lbArg#fMX54TR<C8^2qt56itS=hAK(J(N-TrLnH7s`+ygX;j
z!P=klWj)k&`&sL8Kb~4$V-hA|ytu8k{BUtIhYO{Q&L;i7OV2|l56rl-2-x{2$4;64
z8Pe=pa-&(LBF<-ATGJ!MEhmf_K~-kbeIhshbxk1k3{_FC`#?{5>fh4Y?Fu2qOx3q*
z8HBA8Im#gx<D|)z%LAb?w8a-6bIbL28Kr|7cA^?=Ngu1a&yUV&@=&TGG;rAn%+80G
zu)pwrL=$L;pU@U*<$O#zT9<P2puoPv6-mAh=Zh5TXs}2C-iycOCLCG3rgq!wgnT8*
z5^3EtD*n%r`@F;U4tA<H|00)E_8aL|1bQm4$b@^CI-{PYu{=iHX&?fcBzTY={d8U2
zObp#hlNCTd%a7-6lZ3cAge{HIxH>`ZjJD^S%nQZ*kM2paho)!tTSlG=o)VbH3n@QP
z@7v4;c{zg~<tJM`?&={zl0wi~LnjF{SoFfRzpaMYj3$pzgBlJ>nX3I+?PM!Vqf2@7
zDuM=@tO+CEjiuDdP-DCkoEZAnZ?L_1Y`V8>ZRX-5Ce>{6luNNW`R-)sJ8WZrd;wms
zd*t<SQy5DY%k}1A2GI!82t2x%2$T~<{B{m>q#w=RJGNnXN|_$cT|Ky`8-~#b?4H*l
zcO0NV@;8g<%sNN2Zsm5TcH?K2V+^MIpT#eO2{)7b(k!Oz&3W-X*Awe>l>076Y9GoV
z)KrDfw1}U-M3A4lIa~Ukr8w<Quh&~~|1pfNWd57%vam)kRz0qrQXxlujl*0NR2*HQ
zOy>2wGUlfJ)6vY(;j+=XW#7DmJ7=n%T&*ju0&9k3-ZcK3Btrz(YU-7oyVHx(uKK$d
zjcwJIILSS4%AZA8w7!zyRvUBrBEMlK60+N_$L>S_{NERtx3*Bre$m@W-uN^Kcch5+
z^mi2;-ED$`l=oX>%y%N?hxg1jaBnvpreYetT*OlQ0O;P<M@zR``o)D0X+BWj!Hz1d
z<v=iSbZdu7UXUDYsEd~jC)d5A{_t8?pLjijq~lA9@aY>Bas{d7LG6DqtVXAC^5`Ae
zP1rpVl7bEf5St;iO&{L3dZ`^i(|B%YCo()7n~3SP0hG=GUU}5$1uQ<fGLzo#rKP|6
z`y+uMdOc@<pIuMR&W;0sun+(QLm@5Uj|$^!1D^O(&cHw}(m6RS&kKQ`j{#Q)%2<Nr
zd}<~}(*lw;-V#M3w%-qHiVwqg6QY<|lAG!%`cEw6`-xZfbr*Q+b3QJnmLiX!R+WzP
zqAVP8I1uB!m)-mErhxI)iAinDO#UZhdzxBS?aIZa1pTk#ffzt|4P43aNr!goJ%E`$
zlaxdQVqp%Hd;p%ALL(Ky;dyEYvT+h&cOE2=_8)GHMgo-=^su$N(6m7?5fKFrX=&+D
zVdBo3dHwG00EsXq*IvmQdr~C-{O^5ZQ6-o{1_XZs23hlAochj(9$u!d2mBtE=@wKn
zF5P)7(@)a>Y5RP&9AW1fr4;iqp-a_#S!t>Z^a<>WT3?0pKdnuUwob}%{7Q6^%B+{)
z8jM;o5NK1FIs(9APcm<qy574$z`GR|$@`Q;(A~4Y)GhdKpBBmM{E(WPI|jhE_eB)m
zyrDHTG(;dlqa#wHqkYTDxPh7{ASfv8{!3Q!=OA5ul4!`XzdlWEkeolwweKPG_Y2uS
zUI$7JHn*a(#`klw=w=>F5UBCT!b~lC9&Ps*40}c2Umfc?FA*w`+>J1hGx+Lp7F{P8
zF9fRoi7_L?x$}e{v{+sFL_4^1rJGBsxZa;K8+|T$&N9vsE&1=&_){~o^73!zeg{II
zm4um@83|yXW)PklcA%QgGzudMUFPQI)wQ*t?r;D6GG^PO5O|Xai0mCo=Kr5y{tAe7
z*OlED553XWOP3h)Z=qHj9GawO2{Ts|t&ZmkVWz0HjsESMjKfe~Uo9u4#4PGC&O#aU
z$s<syq-;6(BaUWayxaBCx7Rkh$(bqXm$1FLApTR!#JV@iZD!jQY#PTT#(753VkfP{
z`ioF8VPIws>*(mXkTi+;^a)78`(76wfTx^ZSzniV_3G7J<;+e@Z0zArV_;R*Avnn|
zPFY|SN$L&b`<N#2NxABJGLGIs64TsP9SJF%2|gp~ZYC=$!uMrqaqldNvOnhT?8sb+
zvDUaVe>y8Q?Hs!xfbmwPV9aWAee`x>hrc<TeXI;d`UMRv+$@xx4fi<(8xm5v>^aAQ
zh^S1slvU+neFq6qEWCq5ZU9p!&@Dp4rPSHnNk_DghlYnSZGo?NbIwV(`XRWh5%tNp
z90lCKR*AWN8wXViS*+f**bAJJ>U!CfZHa$;HP{Q<YH?A_Euu<;t?|S{f9ERHryu6^
z3w>2fY!fn;_?R!=N>)0?zAZ6SmzAn{^|)<P&M|>mrpCiI_;n3=QA=zn{uBaP3@t1X
zr;N<Z%-=p9Zf>)4b7Dv9fAciU=mCn`(%w!$L=*@Rjn2-_6KDz|8toW27p51JbvOO1
zpoBlq)|HxiNM#)&>bStNnH=uE>k)e?M>rd_-r^d>$HHPJQNg5|_~$cMkzd1r*_+sx
zA=w6B{ti@D;#yncuC%4yVu_dvwAoQF@79e}oPOcy(j;@feIlrt#}GFz|C2v6ABLB|
z4A>T7E*IrIeM}%WIy_9EsMzmw*w9v|LOi*V5&q%Be4M%-HK2LF+w#-X2LZ(rkilBj
z{m{mJx13~(LB#;C=H}-5?6F*nzyTWgn&@7o_$7-#!+nl$tW=KkgNiH^%h<0@7?^Lw
zV!HkmJ|upGuAKUm{P56xl)S>4JAzJUdA^N3&tpmIQu^y)+`C1eD^_5H#Z2tJ%ucRo
z?W>hbwRmy2dbIYTSk<D&p8{J*vVqMJ3<%zNpcljBmm7di^Im<CF_hkdR-tYE9vY40
z$63UK3!reh43RYR;jcs@eZV<3hxR!F=<&bpa~QfzfN6&x&odN##q{nj>3QRjYknjZ
zC7@dpK$287%qgYRClhjLtEBW#zVm}_hzd72`|7#ae_9c|dy7)i1KNv=ja}RFVRlai
zf|F~4&6CR>RN5~8tXwBQqLS{7zd|qBd^~&_=Xi2`LPob1PZEYv>*C_VqFWmam5Q{U
z9ytUT1uBoH{XW+!V`{Vi*RFYA7Un>;y>a8swZ}E|&3A#mtWu=K8_%w<m+iRf2SK!D
zRgB?|&L3e%<sUYgNJ$91-2EQz^7ck?>>%DexzPcPAJzVNU*3mLCx=A%XDt}KQrMw)
zZf1D>Qd3HJiRb8^{=)vH;+gmis&#XgQ+RG@WLY>o8zz|#q3_t6?Pmjt^%x*m^|#f5
zBwcAcb3NdNXc@z3%ZL1OpXXY{U0IgF5ady6`Wf{|-C`@C>|r-+fAxizbzSYP)*B>4
zZ#FJ2T2K_J3L}@S&*V%i%scd~RFiAJFPTF#-d~QcS-2B#W%-M9#+xVd!)I$&+jnJJ
z5tAE(yg*5&Ys>a4{_+?iKoJsbI}2<`7|qzWZ_8a(d4&H>(jJIbVe4HZe$WzRr?0d1
z_ANbi7e?#gof*oTz~UR~m7kG|RySA)6Q(5Dx{-SpSY*Vb3y-adnSv^E6rUqiFv<8d
ze2Jl)`Y&wdmKmt95`181M~!M<Ht<FNIm%*zmf8a{&i;X0{j>BS!^$*Q#Z3|x3;EI0
zg_aURJ;p<hbyvG{{P=+jG2eh%T}I{RO3U>-&xUU(EA>x?XtFUP165l(CBLGSKOf4`
z-bX}hT-lacLu{FCKE8%G$WCXj1GmicQD(@rN@ZpON5X$6KA2N{fv9UR1u)8dKo%Pu
zLw(U4UPc0k?9>efZ%xacWcC_wM|@26%B+Qa7oL2T7!Z=0ldLjX%iRBLN2v=tBMA)Q
zCw^Sj!cz^DwO`!2B%fO2HRH%e=_6&{ugIcFxT+nhv&W7fh4B=1`Vo74@k=sF)j_9g
zJgo-g3u1$i8|3~8bvMbX*wS?jZ{eZD$9IIH7W7i4v9DH@o9^jFINZ|KJkj3pOP!HL
z1c-8yPOQ(wD9N=YM~?fy*VzYnP*iGTJD-US2V%^nk=%bE&1)-F7XKIovfAoqT=>?D
zZUUvqyx#ZEyX)5SrX&@&_~wT!IbC(7M6}d1;(v)8ny*TQt*5V+?*~=0e1a?sCdFU%
z*twQsDx<xf{%mlfgE8Oqll}zF<$q(v%Gx8^T61m@jG~YRJv~2h^k)VBQIw3-!n6B&
zAsM0WR)QeodTt)+_-nPdUS;duxf>>Vs?O^0K!!KI_iMZO``><i{w_6I|2CG{A)Y9k
z@k{DMkBb!z3hj@5iD5X>uXNA)#v;mRZ#^9>WV?D}!9m^9e9HGeT|cMX3-h?gw_ye^
zF{X#G7dgF5t0%iKzGvo7`h%1PGnL^mv1nhO;(0dWqWD`)y*bPh|LNTx(;Mb~<RG2f
zM6<CyBWy32sNrvP=pbpiSJ1v2vDqBe!Q>{?)%6x|oxf`Cl_w$h>c5u=d+2>Xg1?_b
zrYae~wxW=iXLe(Og2as_w2Kl4YT=3{cA}|UZ`y)}WTHm`?}4-=#D|GJ#t&sCrojs>
z!u6irZLIv?TE-GCwI`3bYPm~-UPpy>!{}K=g)j*5=bC3HCE-pjPtpsSyAHpsOUbby
zTK-(Qa-|yW`F)!(GEnV}!5gG3Z?@%PolD%_sn5*AVQ~ntM<N!epw<#PCpj^<d{M^;
z-^`-F$*pAJtDLt87jp`Wn5WPuc2s{H@STSg`?aMds6&9%YIiCnj?u?C<xXG16m}|9
zf-Smf**fo)khihX6P5d{w&T^@mmoQIwf`0j#wRD)xNeV^69U-Z0{)K8G{nyO4W`i5
zvI+2z%JtLp?%72h-==<kcQ^lTq!&h!ez2E*^LEK@bxg~R=2Z*#NVlemSyw7Eg`17N
z&`z;n=TB)LG#-qo`%K(1Ypwr1T5`qAjHp<si&WZuTfG_c@h<3)SsG(kjIB?HMXl<|
z6{_52PFj~jH^e#K{z^IBMlg5k5R&41RN;R(Xq6r5O|U0JQdTz3=_SF(&7YBDY4#$B
z_b%<{Ph~aC><K)sibQCjbNnw4EW$L2O_OZvD=|1BPu>4yj{?yL^Iv+}*A(IxYSwO@
z>IwkxekE>-?d&0urf2t<a^Cc3r|R?kJE7$w9dC=M${fb`53Wrv>u<OKdPXw+nakSp
zT~3^G+`XIz4<r7Lr)U4)`_L&icqe~OT&qsg^ovPG`RV*O^lfc~87bB`k23eC)LVDO
zLxyCOA3p4IlC49kTlsm7db&)%U-@^mzEHoX>WnohVIZFKZXV3rbI~$IiQsz+{Ohp7
zZrz$DwEN^Jizs`*vX>3X|Kw~z!_V*OHxs_~y1MQxU@(K#M)>Xr%HQ9Gu7}dW2S8f~
zCF^PePxt{2OMq_Kcg4D&BwHAgYigx>;ct$Mj_VtQQr5`&2fk%dfpBMj!@_jCE0B>3
z<Su7%8NEx^m;+l$;fj6lHj#4jzX#f}y{3>Gu8ia!Y44m=MNC2DxB`C-j}t?oB=A(z
zjNR%R&6Bm<nNCh?4(=ZloVHRD%dL8u#v!;l$*7%&Z(5(3=rX?hudc$8?KW8xE&V&W
ze^>MdrO^Tnad0}1SU;S9InHM($9#sah;C@kqlLb0Rjd2t_FmcC>OBiG1+L+9TK@8M
z&!pj?7s1-4`@6i4kf%r{1rSV$MS`M73@@wx6VcKx-%m^RM7dbt&zU-)I~w9wlHx?N
z(>yYWRA*<ZB<)@J6}QwIh?nh|i-!@}&s9`k>B_d56ecy|tXFyNyHc2Npd!Y-tY_7)
zLi}pa;m<JpZ`iA@PX#6t>-M?i6*%b>5p@Oj5FY?+|BR1$sS|OLG{8JFtRZL!2vwT#
zWZF@3$*W_3w@KymL0}8U=J1z$K1f#Z%aMI(Lw_D?j5Snjn#mVLA>(E8w$k*xja+2L
zGk$eF9i;1DROQ(<1Lmo!UGbB#^8eFxCDvnIH^TL3E9#pr_?A_tT}NLRX8A7*F)F=}
zC$O>pZow51b<Ubg<6{P%IW1ji>(~L`Z$*8_o;S@(g(+WWs@}pAdu8H|m490r_CGku
z6u-_InYJ2d5v@JgmIVsxy-7-CZ(s9LYD;s}$AD{>EiLr)uaRXW*bbcdD^+a2e`@GX
zHoBYdf*Fx)h4iCb;mse)0N0JZKla6Mrj6i6@~9A^TNu_({V!Pf_M-kQN&$P4QC%X{
zN9(gk%*m+sXCSnc=4HQAJ6g~J@4V+2qu4=7KV!$gx(+8ZA?#*jM-w&6Y*~N0x|j``
zLkUMH8`?%x9{=eRZ3AGa$jIi40&Xw9*sWJYDPI*0)vIt_M)upmFzEXJ3DdwDii&0P
zwXNYv!q_(ku1^^xHdP-RaEjcXRL}*#x;!(OdMu*h`e7GI9j1CdtE6H4pgqs%=;KG#
zZHNOQ6iAW@W&1ifUGIL8(esV&{q_n0)=W|OtQ3_YODs<=3QCpiCZ*~OtuNRzfCw!p
zkC!w>7>iixW_1qZ3F0VRW9*d;&~86^WK7YtIubqq_x(;RTTi`K9CWhBTsgz}y@eHq
z^C_K5)T1jaJnaT#Cy|C9V!!vVxO^(};qtR=DYN-Mxc1iqNwL4?8xk~KW-&lCSRMUK
zdJ8RR+^Qvw2kCVhtBjdGfTvrT$9jkWtBN|bo_W0Rbz;d2Pm~~ny`9;aJ!Y(XSkHHJ
zZ@c%93_G+bxqoDM^q>2=5TBaVD#<Hfy}8EcXf?#eIBJw{my@;bZCTTL#}S^rOfb63
z&!wzdp~H8!0>m-LL(&6db_DqjDW5sC-lQ&_%}VOqa*~TvAv%7J((houw3L7AL;${T
z<tKOV3q0gE>?a?)z^*;SeEvm|PG+a2NYYEg;&0N90#j;JbmtEgbq%<nI325Z+1_;S
zK^Jp7dW~9LKlU+TQVB`Ot~9P@91+Y6$@qRuMYfsjY#uJXJQSRQZsuIEtY;aw@8U-t
z!jI)6l*{kFh5zZ9KA9k&Ali`l<CY6Uq5F3v(5ZWV*L*T(n_j-T6HF|2$x>}knjqmw
zQrz=a!_KsihpOeWn@Gd{lvLg3?ZMjDGSAvImfrk#92{KlM}Fz8cKu?xZK|?Ocs(&9
z^VNhIQILG>>R~AzoTEN$uG!o@xkOk8%Wr10{%0YpX=lgdpYh~v<E@-pO*o^QvQgNK
zq`Ciy9<}@H2OQ2|P(L>}w7!EKByp8xXG74^|K2f0N#RoFh@ffTC6GhU#|mpBmeG4W
zqbH(_f6Tkh>A?Pnq1*5?v=?Ybmew`5c7fsMn4rW4BW_=qYRANd$Q8;rGYj&WHX`T_
z+Dh81<I^QjZT5c*o4Dtaeedh%K-FpB4){-+F>ebz2N)R+kwp1Bo@n!!L2fvPLhJS@
zj!}aVmM(?oDk<lu?yZact>`B#(;i8mKax*tdVONAqT>MJCJO19v9T{rIsovLhbLde
zO2AFXlVPj0!#~!M=5>ACN>4`<oRC2AwmJ08`eReKZnhvb&@0#19o(ry70W3FT>4?e
zGAlsJTV@ti32GIB)k=Of+QLy=9dkS7I&7yB_g$V1RXUkq@=`+DnbYtC;FBJVbS-$6
z9+5-F{{{G^VR!5E^Y6KCf4!~C4H<`ws!P=!IWc~Q83RuCV~@)8#y-rj<9pF%F-s$s
z=)<X~3sX;^G9z!SQq*AX1SVq7|GnM8>CFgkQ*7Q_!sACNrhuYe>9lCZv>5B!pfy(5
zu;szo@&ST9vB4a{d0{iVHTAQkhyA<VqKptc8aczV-MTLU?<@08Kx<*^GlL*a!s!8j
zXl2wfs;X*Ig$etECrw5*Ho`<jI}sX|MOg~AA>^1M)XS`|;LQhzH6^B|mA(<vZgZhd
z$1u-bnmDcS5BE2a3TumWe!BcBH{%j#xh8mNdZuh*E!ZBQruy#DByj<k``~y!%_!2Y
zb48%`a?zK1AS1~<MzDi=PwLo8w>5sexUDPEWe&rhDOvoZ2BvSdj^ry&o|_8{IpO<D
z{PT$bjPA8x_IsbtYw<4lE<SfJh=2BSYZSdp_vT|e#Gv~93WEEP{>82$D|&X}-~3P5
zcaImSdC*z3RbDPHlAW3>K0;D`N)Eg5_aA2?xv8s46L;P_w|~MIZD(_QP1I-od)HdA
zoSW=kTrK$%x&)qf(gCmgU1jYL-G2lC7L+kk2PN}rf@4j<DHWqQj(X*OZS~sW^kCAd
z1!mH8IRXT(KsWPsWmACu#xt?J=c%Lmbq8RuCAHK<h|;XPrY3)V@r974(4NTkDS6>b
zXemytZ7j2`>~!`Ac^w#<5JG)++>w(+H4wWEZPTU^Y4l~?L*RjR^^^aCOQ(FcgC3q9
z03ggAT)Z)?*C^u)vTK#D93J&ED@}hDa$0|83x}3pyD`fi>q@HrZSuC_X5t`8s#sz{
zLV1KT&{3X92L%7eUxzJL@2lN?PvydpT$3#2G~x7ub=ac0M6vmZ;LYPoPnCi6KDl<A
zj>zZb>-3JZ;4^nh6Mo<C$*+O9-9;C4G9)car_p0B4ttFDDg8yF1ZToGU-toJeR#!{
zUiP@ESN8~o6;J~;8%Y8aTATt*P|S{%g+*3#9WHm!X7e;jCttruM;Ki;Bfy;c`xZ(^
z?MvSrcJ8BQ^Vq8g8EaCU&aYib)%Q65<L`I*VK`@9$hj>umM3DlP_A;9a50&}6hiv4
z^~Sr;Is%gIYZGwjz5KBwFRv-{d9u%NJZKoHevFz#icGV081Y>@s6M4IQ|~5I4TK0V
zxi0nM0k)kds^=7bqm`l7^<X0IwX%-o4eDUcaANW_8UwNG{m9Vlh!O~^?*l}2M8I95
zJ7M;p@qjhGTd={~9>e!0!YN1noZ8%RDB3<*Q{}8yB5_9B7PmM^RrU1TV<!Yr|Ku&o
zWdwOIv*k@f<GSm8sC9nnwHp^RuKv=Rnrhy%^>QnL1J~@&s;@-0Ho9Ea!>gGH`a}0)
zYu@wTPzGM^$b3B<&nJ)k5G|D=O+qsNU(dX~8*91&YgJfSIAFnQDYEa-jtGA^bZ6`h
zpS1Ko7jB3j8ApMWWA@EgDt-3VpZl|v^^-*+AWAl2c7~e*DEp6bYIFX2&Vv@8b^CST
z&fEe8>2Ps8|3)Ok!E)CE3kjvKQ3U1apW9<csN|<O``eYuW3@?N(JTe-r83za$_V*4
zexzY#&Jc=A)#P}JtnRV#sYI3V383i!QVEj2WwsX~Qc!L7i;RqXckTTlJBRUWU?3B}
zRLwga7cXD;*(ZJn1WEZx&Anw|8khD@>b1kaX%C;9$q2l;E@z1D=Svdt^}5&-0=7on
z>R#&=d_?>br{Ye8dfs~(4GxB3>XvVBa0>J7>=|16{bCB<*Qr;#qov$;%^fBylpp>=
zULD&ORpJ^Gt@1240~0go#jF*B@XPphy^f>({oj3k3cvjsD_*P8L7_R8aJYROdMX@_
zFS0wT)qNFIl(ibM?ljV|yTIg5F-K5F=R|etmOX3U&=IPq<%@V}!EPKKll`G)q>o|6
z;yY+VKMcT^pgRP~)kBgWcmAN)^xaWH4iA=7>r@uWw`Hb|z#Lg>Z+cpaYikei$9S*(
z<*yevLrYp+XUCaGM-TS^$3R?3Fkft&2c`)J35G;*U0q#GH~u{PzwzYpZ&2^v-QWMj
zhbC*hfgH|YFlELPM8I4_$&H<H=wIG3jU;OQaIln8Z;L*wWa=MJnFKyJsj5hXVDCzb
zJWb8jqf56eukc5r5vLb$7pdXgd3&`-tH3Zb*P0Q@VQS|#7@0j)g9DB!!ur3`-VF1l
zu?8IZOB(+?h-9C{ZjX7l9(=X9NM`=(Z<?S#nSm*5lUDquo?>xYnw&RVSA<7X$=TT%
zxH8141@nD=B0@d&QUt&IOkXrpY+3EnhU$IBo#=`-;t7)lrFCrNlx*|I(lu$#m|?hO
zN86q!K$u>RQ{Y`vDSjnBB>lk1vS=wr<Y-mI82Hh&+>YIXZB>O@Jh<s#b>i;f#z_J-
zzj+P(N0MTvO5ZOI=!l71bZ3u<+Lcs6tQw<<(p*~li9q@twNJ+j%|}foOJT0PZEmRS
zZ@Z_Pb+j(-MiLda^KNhzdL;SD?_^?9VFAvuXkXO*vL2ZRbDoXEYvF;-3ZX&K@a{E%
zvs-<-Exstho-GIlj4f21jJk{~5R7pMsxiozS!t55%ZMLK(xis_RzHaPepIy;_Zw_r
z{;Z>oi`t5IFmvof<f2jC&9fm6J`K~GYGlksJsJ!^xOGw@42;K?=)}4DAV?PZ>4)Pj
z2_DPbcpubx)9kkXHjM^?@wSDBnR_&>Cb8*p{qw+x0Ul++njq4j;?<V+hUVNk<7Lh0
z7Ap8){^$JrD@GPTJrwTOW{yPQI@rq#_Ey#7m#2LtL=)LKWQ9$~znWz(8-s(4Cz;4$
zYkF*YbIXf6U~2)Bdydux+>LKlAF$%zHv|-Txz)c<2z{oGj?Cq$rluwqDNjgZA_>go
zTUQEQtAooLbh$kDI~i~%O`(tU^q_~Eiy)ZM*{Z1G=@e&df%47Uk>y`H({;(z$-E%W
z%o1+6r%<w3E5Y%&BG_2Hi9ek!VocMVGoOi{`=Hu^IfW)+_@5J3;Fu$S2Y(`4&oO|!
z#Op{QC1l<EN70f4VS%LlHr~gEiik*K1#Zi3!3f=61FfBbVEs%N=Ks$96$yn}^OWfa
zzk?IC2z4&0+~rhNHS15fY>S@uZA~I?7FNjZXh&97)Q9aR-BrFsbil^TA5#c982~Bw
zWNH*D-5`kyDl2<;Um!`;M+6+(82I?^<Kp5D4Gq~jJ1_n8MF9<r@a_ehPW7{;t|qVA
zh2>>Q(ElOYXV6}`7<FdVttDhGm=T$~i-onAWSTw)|2>`@`KCw(4swSjk#x`P^Hz<z
zwIhQ+4Shuu-CXZXoho(eIuE2A-*TH43|%R{p`p8`Fd;5q@{q86b#@>!4F)Y}FHm=%
zd+D2xGB3fx1v|c7rwt3JkL(W((O5n4N^=>m+<RS+53>8}roe~xRe3kZrx;2*Y|*P~
ztvnv$W}*X6E|>OTp)WTTD16_tDf7xL;T}E@z+XHYond}%&h5IbgE095-_aWPBPN9A
zpuT^6oRli#j^d0d2Z<6PYWVWtgwt!)Rs)XA;j5#JNyn8w<uVg_adB}ZmG@Uqz)<cP
zG<0h`&$tl2b0FYag#Or#`|GjZt^SKcpZ<}NN;?-6Y8h^JDKdH><c-%dwU;=rTo{|~
z3Y?+Hze<>Y!PKwKy8L*`A^t%!*UXr&Q@h3M0~cDZj&PR>&)jvomBt_9q)gq_lt;iI
z$)kV0SH1$2Alpm#)OaeJxw<sd4#8c59&>ERiQlDfzeWLR_wWKgecY0?^(rjN<I)1H
zpGD}|g<@st)}eD@1?hE(1a^Fc<s)kK*q5%`lXKtz_-1pg)M<M%32bPmTyMa-PKof#
z?!pQDaSl8_!Cx&`wctJ=A3#$cos!ZGbc_&C(!&e+ss&u|J1!`V!7~vo#d1bB{*@Zv
z0YAYUU?hN>-ootcGjNgo_uWupt~4hn=M3y>$11JKK4gQ@qOO39HuN)oTjMTlZ%05^
z4qRPln{h>H1qG8pi}~M_ze=5pHHgqa=<j(rC<Q$`5J}{z6_G+;AAbEXXy7j_>iFGZ
zRJ<4bAm1JTGgT)1^4)rEx_|uyCJ+&>tbo(_Dj81d38adXsS-vEeXk=Tgts8Hg%G}Y
z@TEUJ6vR+|4VEh|FH9xNt)ErhrJCEz7|s=5Hps;b3jd@iI%P7V)g-O+MNxC$@cu&b
zotGV~#&4dFBE#Wa>Tbl1Aij-qUYIA8`l)S<8s~gQHu$4qTsVxWyRbK_dyy6SC7)@f
z*!0KQ8w^C;Gq7~{`$Fi?v7tk|0kZIB*wI<Y4=GjE9|zbbf|W&a$F@hoH;2QDx9{9h
z$&tiH2(!8SpEk>arQAS!M_1Q8!g{Zur1AIE6a_dLK-X1HM~6Ja`}}cMRu-sO?7;N^
zv^o2Wot~$2!C*)@2Q6dJnIL90!9rHDWVFoS7jmu3Ru_y)?4F#Mf+w(C`qQKwsmLEr
zYp)86iUh$97U2m>Q!z3U**G-YF!;B={wXxZrFNzplEC~E(fQ}&iw6g}x$W&fFaiEo
z=gN*)05jeftRVWO2bedILT=U;V2~jebbNp(=*?Bmp>(?h%`>O{{BwlmFW8kf!<_d6
zJ}Z*O#zxqAf7mtgPrLcU$J+mOhiVs`4>`dL7MyucrE@yO2_F{`$xKa~Z5;Zw=zdj{
zP`t!gsY<ljR+U$=4m!GHDM%cT3a4;@$QC(@ZI99WeUuNt0v%N~ZDcj;7MHNx-gNw8
z;~>QA8KKnKiUSGCp&IG-B4HH7M-GxWPzw?C=JiiWdKVaJ`9;-CeImG&H6Q$4fT*5*
z*xkpkv{B(~B6z&VKXFs^E(M<PZrB%Z0jLE9<{Yf1YLBvLzCaw%lPVYk7mS2(!-YHY
z9E8uHB);{Kk#QAw=43g=cBs;N;&;i^<Rk_a%4|{9w9&sGZwoa_{l2BUWBiZz@3v(I
zbpDaN$@08jg9YV0{H5Q(LI>AKgsNj>r05;=UvK5=H3+pwQmr5e3h*g(YMt)FfB?Ah
z`sL)%+`4rOcXP|x(NUt{@BHfO=|Hl`<*q~!4n-G8Uy%^*e&Dl;csx!}r=Vp%RH846
zgizCnTpg;o>`co;hm`W{3`6-dA?hWKe3f>B+-TLNHWGjT@AVbKVePMZ{4|pOWpWH^
z$xyQBMx={ez3Fy*Xh^6(zu{Oc3a|-QE-ufJX{1S0^V0+i6Az6!Qg5+Sjc656Xa6AE
zvh)}(RX~0E!4Z{@T4n&gZ-h<-PG6K~--ZX_&{*zEyBPRSR|B?}m`x%;gx4yH2g}Z<
zhi<S-RPStnnJ))eV*@jz6{rP_jEoPTJV}8K>gs^uNE9rGKT75xW>YdVA9`QzNrBZY
z!ejt`S)J_++(d+-p#cYp*+eBP+$mThgIN-H03Dz-rm(A+CSdOeKDak?iNoI%n`|d`
zd@7HRk71I9h;5WP;9t$DMBR;e81dXJ?sv=kpVNcWhN+JohhL{gFZ?XYs$nMb5eI9y
z*bMAopUa!$ZDE#tiyNv_4_uDsStS3-mmy&tx~QDE8hV1+)OqbV(+U{p-0X=i&r}q$
zzJ9CE5`Oe`?3XM>T$gka-s|VAjc#IWeh-;K6YvU^o)OgaoL_MUr%l{?p@e24QnHft
z?HEMf4I(r-R3n8Im0Z8Bj^=ML1b^~M*ZkaE@|_jHxk5U0{L$9b&UJY?;k7tb9mZU>
zla+l=y?w15EV@o=Nc%T1tC5lgi_Y!eAEdtcAiFBQY}L<;NzzA7O4W~)tWRu;z(kdY
zhX?(B24~yDXlXE)9i3Oee3kc_qav#Uv$)ooz`FuL03sK3xXsDQxeCtOpI<$m_B@dP
z0|<bD-(?rjJ%?QaM@41WRO`KonOVr@rWL52$%ApJ+J?T!f*9Q)RoLS=(AM^N)duIi
z!}MqIEVrx^+Qp=oSiZMxQLb*N>;zQ>i{{o}&WeB9Kl;Qz%dcLeYKrMG5EJpOG;|wW
zc@g`>;?h!{Rk!2y<vTcv7GPq5gP*@03{w1IFkR8^3i|)y04<7*kN*wR>Xsvg$~TpQ
zf2(36mwU%?o+|Y<1!|zVHGR3<bymMxCsex5nR~<LPryn^!;ao=pLSi^kByCuP)C=7
zkI6?8PH{UMI5x*%-vbcIRDNZBeSM}9qa9dfd#{UIg7L;f9v(v2iBU4i=e)*?G2|T`
z$jG$$?~IR(+y_fmrX>J<z$#Z-Q-m|{v>o>7^+yjMBEjRRQEByH(LoTre}kH?wrqQk
zH_W{(YFA(y;P#1=tE;UlOMsKiBm7w|nKP#TI||mQ`%TE+oyf=XcRuR9QZQfT$Bs(Q
zt*g>1alGmNgM)w<0OuwuA%TIhq`0^(1fK>}0`H5os~(ApQo$1*ti!g_WORYh;DC|E
z-2%0u-!R32uw@6^g8QJjzKj>8$Y+rfbk~l$&A1--*5S!gfZL7_(m9W7eAKtI>x&(G
zFjWTk8Hu-xE->;B!)j*E*_O7pkuU~g2&gTPa$AlTBaD2}@7^`v6EZb5rKO{z77!pI
zZ>JU#I?tm?xPSkCl*||DmoLR4DTOmjN@l(ad(+U+3^w`r6zbI6BcPXi2680`U3Wou
zf~?diDtdFt4K%FV1Ox<Ncq);l^b=GlttYb(eI<g@pZ4C}o}Ql9>j2F{2j&czwn&1g
z6k+QN?|j!K`Qc~TvVG(>8#Ltj$9J;&uJ7btqYBhw36x6K1g_{WBboHAZ|98+b!@fb
zPzVLU14ctnFS#@cR>;cg>cMcdH8(e-0E(#vFcPJP&1j8%FrUK-wmXP7gl|@(#(@ri
z9*EUqFZNw>sj+H83V9-k@f#E4`mHBE4;L{Fyo>iAo5U{O8)CY9_bxg*x*6X~SQSr!
zk7frNW3{R(Fn+H;TTV#?P66maIf45%+2nH*I%+lc{T4kvJ)GQ9FyV-df-<+TaL{7u
z<m`-3MizE@>NYkumfKTi%}PZ@g|H-+mXiwrS8y;rhfq!p@mL}~Oz4gV%8p@k(68QJ
zY>3rbryD%x<_0enSeexdpP8FK24$Lojm@-G8n_A@!DAc}8tNMyd}n@P0bYpsW)m$b
zoj_BD6vT4t`rR#(I@Irn$m=&qKkmI3&^I`liL<mIQE^qQz-do3Y1kklB3d0Sp@Kn1
zTyAb|0RaK@uWWK@LPUT6{vB)b5%rM=00+1N1$A}FBqk>Q1cN3BKKvN2S+py$E>3pT
zA5h!8bav+b7#^;ys)|aJvz$>lROrS1-p}j3^iKbvb~NSe8UK=PAm5hHZ+z-4Rc-As
zKsv#ZdF%ZAe0>{-x=38K>T@#(TI}`b)OKx8^q<CgBl^q8H0r`t6BU9h1IVPj&c2*M
zaBRc;A{oRYy?tKH?Ciu(=?RcnSXs{;;dV2!v#)eh7O8-4Z@z&_#4`l8ul;s;ZDe8Y
zZ6E*55AM&#DON>McGGT=XjT;oLy0oLi6sJsTu-IZn_byPG5$b5b31+iGEXtXGFw(_
zgzhUFLJ;Y5t{__iX6Hu3U*&W2^2A=hejR*b4~ZF!t}g3WR#sYDc9=5FK1D{4Kz)Sa
zYe=Q^Nfz;|Rlh3y%;oJe$CkXAaI6|-JUV_E<^(fv9Uao%l$x?&lx)8_#tGOc@kjXE
z7wa1vVF;HcnB@BY<A?Z*7lE^$!}h~%E3ALt4YjQTnFXQciYzE7n26uxyF!zOx4`SA
zjzhsGe%}@(+SEYDu9G0`)Z5#ut+TnCJ2s|qc`<Xd9NFE~g-1dX0wZ1bKpTgI1iZRA
zh)$)vyo8%v7ousTX6NUTVTm>>XlW%IL~J8oSy>sKZ=kyuD&r@Qc$Y_+!*s9M!?Tok
zD$~-^W;N(lw#haY7Xv7TWA%w4EPX)beM$}9R=yD5=VWFgk@4I7XX~tA1wkwp<x`T4
z(Gn>oB|HH9M90Mif{VAa4#$5^#-DY|Z8j&z#z+tc4NL$JLXh)ZQql;*UBC9%U>0u-
ze$|L<1hy!DAOaZPTwksKlSuf_-?%)q&6<5gb3l#idCVZ6{AcFu4DIYZ#uc-qk?__3
zJeTpdo`tf(1&E^$O2@)WA@`YBSy9{VJ9>Mq)t`WQGXAC#kQpQ-IDw^u)5K2w*)r>S
z0$#RiS9kYb-;<r6gM;|@LT|%YjE;jN3HPVA?rSsxA0;{_MSCv`z+dQ?n9Z=&XggmW
z$aLJL9)ForNlX(E#qgMwwH0Dd>V)o6&^)=ldzaPNNC^Z(bX?qaxJ!ShUWCK>6EHt-
z#7Kw%ry?~A3)b7WZ>8nsRb5BXsYxRwo$gX=8E;S4K!jl0m--7lyax-^*#WKb@X;e=
zP*cxu=r(y%fWeNh9KC;ZG(M!ew-se|8a)NikGH}Q+aD}at|TnThF=&P(}4FkCJfhV
zXlTslM2g&-%vcbBSxe)?)j<vpj`t}kWL(_b_J9onejOqP^KWVrm64G-wS@n1nDmfn
zXlaSl$7K23Tno4#=4R?b80&et*PbZiC4_~IZD?xx?Z?hZ61VB>))uyxmlt?;KVo2z
zTDp47$oLbIiia_s2Il6W;3kIIbahPTbA5evktpQM^oHvJ<T7wvpQ|<OkhlNp>cW7u
z5y()4%l#RVknPNai5eU^zaW>wsL_D{Mdc%<uohmEzds7n&xr{#@^-_HC~Ch-uulSi
zGHm!cBFBa8LDlO~fY}`xxQkouBucLO!X;|kQ5u?>p@0ZP{1w<xnO2q@1d*O)DH*`Q
zm|Iu~vycpSiyim~&OsuFp<kx=%a?Z%XAArj1d0-I24G<P2HPNe2q8cSi$>+Sdkc~X
z)@mDY5JFrJh}$4a_|O@{U<~r<kPjckL3B=HoXBrWsec3ew;O0zqvPX)Qd7x4k_+Ag
zN3Ck_tJ=(|qm9vnyPHts;56+cCnP35u!hSd-QM07fHV(g8Y2QRi7|?sJWkkP6Gj6j
z=9{-~sp;rYVcUlDdTs-8q%kO@!V`DL?sV4>5xPNCP~?6?MHeTNrNlTeFz_C>X)tO>
zhJu;2tgOE@?QcjkARIzsByd84FO?Btk`5!}jcEXCi;azaC@f3?7`xwnX-`Vw88Y3*
zrGD->_y<*7`r_}+El;bQbdQ??EW85x;>bFOB@7Z{C_{M}H9%o*ab;xzXf)p|Do~L;
zug_L?cXxmOD>Fp|3P@c6Zh%tb;Nc0Vt9t^u&Ieclh~R+s-mlhHREYS*;GnrdcR+%L
zwGe|?D$V`<xS;e!$HKau>B(iRp+TbG1fJ%r!{2ay>K&G35Jdy9qsn|p?F~1V6Us%6
zQ;H&Iw;|)Rv$y{RQ~hv}QBhGy@L0m?nO*KpN#r)g@$rI$9CD7my>_aDw@^<D2E-_2
z!nc7hioi@X-CVH;;Zorsja66@-~8zusfGGcrOgzEzP>&QDX9?zQGN%Ae^yf?h=GYY
zx3<<PdOh{$4<QWX`_;l>1dj6l5fL~L7T^;S2Ec8Btn(o0{5krd4o|i$`XEM;7oUQ%
zGQO3y^%*TO(&W?>Y!=F|U$-Ruo0w=G7>E+BEH6jgrRR^LGdK5MsDr=R{ZyFeW@i`E
zw6<o=FDSUhC}j*(MRZ6>JC+<e-f$5T5#@bc6&be~e(n3!gP4dY%XMekFPIkg{JX{d
z-Q5y!b79HdSe$>!{QUVg9UWb6K>-2n7AP@;!@^__Y!_+r^Yaml)xZD=h=s7~jZU_w
zkYYo3VDNr+brl@~zOji3l=m{8y?eX6@8JS{-~y)BU)Th|W=m5W5OqAvtrSt1zcF0|
zgS%J}3+WSn+`_`bzc}0Nd*gY%P-iBc$=fS5Mx3U82V&a8a%*X6$plCi#FlOcz5Ecn
zo&33e>b=8I<GMo$D&|s?UeY+nk&%&V__7No+*7l%sDG4|QQr$iEcm?FT^X1-IBnhR
zO&@`UhXuQb5+fndYhQ<!2yTTZ;bosO4$=jbQ?*xEoWB=x-kGL=Le*IPJ8sxuO1Ko^
z>guApm+TxJo1rEGWf^Sm*Hz!Y<H3CktgG_~K6yezg90@h5`G(Uq_^T)T3Y9F)&P%~
zg9_U-_!dO-FIMNDAnoq${o<eTM1gH_bv^%jcy@8|He7V7h!-i;u#nzEDm)8$6v<P!
zU4k9<d!YkmriyX<Gd?#Ipv*o6P#%H=b_>b-e2qbjqErJ5$qe#=x8(tN`wYpo&(H@+
zfu|=4ySU!FB_dC_OV#i&e)#YKkBqF_Cyoja5AjsUC2^s`q8D&n#`+4d4cIuFM@Org
zFE%$fKf=0RTwZ>}&W;N(KJR7aZrGvx7X;vuBnS))1g4#&oZQDu1*jJ@F*9?T579!l
zcOM=PIFDYyiX$Z>qmJq10O|>1qXE-L2{Ex-aBQNg@TSLwhTfHvmoK%R-~%NMD&mLF
zp9f?{1O}o)lG!9s3{O<=2~B_*6=E~iYK9{fJ|#j#`iO=GmQ85W^-&4zNX<~xL}F~Z
z7O|T}l9Q9;FdKLXYH7p?tnYpHMeDpCLU=^zIWt2A+a_!W0g;jY+!gS-5IioJ#-{@O
zp&RftRlhPqbo~&%xA5?A5>BJrkoN5Y2vM9Z;h=L9#NUW}jmT^uk3&q!L(I{{*G_*g
zG%7JM1a`V#Fz|nKxgv@<xWy=Rb#+_X+8&9BP$CW{ZWFnb9Vzrd5pv5d4D5Y5ScHaF
zRv+{8nMfWy$g6u2@Kn8`qM{lK)#T*lw=q-E*Lqf0;?0=41hph#aUjB$=QPT&{1HJ3
z&po>T$4lni?ifUCGOH_bcv}*Rk~9HNx#8i6mJaywgDWv5MS|u2L1Z!A=Q6{OS;fUT
zP1onl&mZC6l=F&*EayNRv)==Mgb!l3F~S-f7l-(K<sW=~Z^08We#FBsE<Gv^;n8RL
z79&o032{cWwMja=21hXr4G#Ji7qfXCJPV0OL_|X-<n3aLin#9X?(5soVaLn%Yi#;2
zu%adny{C(ar17$&5i1RGiKL;+tBnsoaw0u*cCJYF`0uCkBe9k|OO%U>vG5~aUS1?5
zfWY#e{P*|AGrxXCYiny;-<JILn^WdSA3adq7cLR@S&{$K*p-Jvy|3{pMWK_*L7~O%
zP*RAavTr%3Q?{(xW*B78B%`u6Nk>MGC4*8PmAI9fI25uQD$5bV$WpSDts47s+|RH3
z+<VVI_j!&#J!brt_xrw|<@>(h7P=ZZ2x>_U)+fc)b#i5J$05&vMNy3!6SnvIE9oxb
zH`yv2GYbnoWNxn9ys~QM0^?Uh86cb64egSfH+y!INpY_SXLr-DIChzhiWV1~+rV!5
z*^jqt3`W<t%l*q8jJblBA{6<f4Kv4cvoERDnzAiMxlu0nI)0B;tIge)FA+<8DAHr+
zmjB-FUq1hzC-9eFjjh6b+h0pV7a08qu?htn(=kc)(evpolT%a9-rg|~$NuTCjG-1)
zZEfF!4#7v&KYjYNz*Nat&)NQU9i5$eWb!s-z_TL{3(c&pWwUQbvsuZ>E*MDU@9!UB
zDSs(3aTBgNs;Ed^Ps^AoP12qp{>SXXLREP=>GZRbPWARjWCDN-3ky@6oiAXN5>lF;
z*$_Y_GS>w|89l&kqRNZ+&WTfagAI=h3on<JYGcrLgv!ar?Bb(i^sgU|K<%#LaQK0_
z0K*wPrZRdqL~&h6-5|&11Fu-C1Bv_r(GSZ(ZyyWjbo0}o2`2%gW;KWw`uLc$hX+c#
z5TRQj^)b}3T!4u$=j7~0VdBJXi@S0~P%r&W2*3Ju^yp<E4=-L6!J(c07{B{xNfxL3
z2516OR|#6GLQ>UgdOs><(s@HoCvO|Yx{z#5Oui#KSy|P95_Tr-wy;H>>Vp20_{&`d
zZS9+n66515&YU^Z!TsI)gtPOG1<bZhxp{NztEMI!gPjixkz$fD!uFS=M^B&&kjLXu
z(UP=y&Ny}n`niItYSP`TtS1Qx8|i)JE8Lx(E0DqF)YG<TP?<2-l6*TJUpQ=Ns6?ew
zukoNn)wi@Hu3ok3F~DB(jT_K9>TPl8CwU0XhVK0Q{0cHMjPJ$7o}kfCSz1~;IU(Wo
zh4_3jT!2k6H9kN|qbQI*n67thA1e<}B{1lrBaS!iT$m_pN=QhMAWg$55Nw1rm9|+@
zG7lq!^9TokBY8?mKtN!+uY#|%5d#5F+|my1Amm#ZDs|_lM_)i&ZLNscEG{qCEuhwZ
zXKiLy4%pg>Va$!l0#JEpX4PTZxP$fJDaL}8u*(()6zh9?Z|U@=HR+x_^SMuN8Ya+V
zXt`|Qx9LaWOEG|3YzAW`CuNYc^b|3pgi`pXIOtRXC}63B{rd^#u4b#e4<B3y(Vqm9
zG9zIa)$U$>b#<gx$n0;5_9bVP18B5&aR&POwq|C(Wi+hd<A01<M9)8$>X;G@Y*Mvs
z#5X5}UQ<dRvm5N|E8pgAFseZx^-yazHZgIRiU0K)i^X%ZFYs|TGBR3R_|g+Rp$v<(
zA`sdX1!Z3`zp1Hf&!dvc%Brfle&jlLDzyso^j(gV7CBC?NbnK^=$IWi^5%;h0?%z@
zbR?h=OPOPfSm7&gys7o7{m_|Vk^X~Mm!OzRznK{#6f<Fx283(svCa1pN(=KNkLJ`d
zZB>}`s=nTp`TMxaA6BSakBO3Ew<*ZjcwGRU?oLeZx+t)IaFe5NbXi_zj*yq7x%mYU
zD9n^Djli|OoI@iNob5F(>=Z>IVPQiWO&M&ksvSC%h=Vv7J>p5cYi=m}$&-!6K@(9R
zY?G6dBoEV3l9`p&CEyxfEmw4*AH43}z`*LGM~{{&C@F~`nLhP@w~~DCeytN^GOYQv
z??s{wv3`e-(=_ixl*ue9aS$nFvz3W4`?cw*scS*JfO<<!AkU$ofbev`3-yab(IfTg
z^ulE^2n~I{J<P_&2B~W8`*7~bj6822A45d)cyHNy9UYyA(HfeXQhIuN^5Ht3M;Ft-
z|DnjMQo_K)V;6+ky|Y3~<^ux*jBV#hi?nm+<~EI}rcczPJD3SdQUOSf>{Sb9GaHb$
zH8^pPO)dpOOv;bmV&ts7>;w0-*!a)=fIHGH&GdP!i9evN#fL|kz839De7{do@iHJz
zUkS<?T4sCh_DG_*pnq4KPvAR3b0fL=xUg;A!sh$G=!~iSabjR-$UrtxPbQu+J=!@t
z-E|7Wc<vV(pDu0(xRdSGCVwq}D-wRvD0)1g!1cvOf2o=3b`TY|XNzoWYwLD-`Cqyn
z!~E<dgA<WxcgV>JK-`D|QU)p$d~<kP>&yc-Upe#`2Benv6XDAm?u|EcvThcV?Oo&y
zTP}f|LPJ4g=BM#rF5^%EJ#_ivna3Uq7^J|C+ohmj8C2->6e0_yg0Y%#Wl%@jx~0EL
zI0gpkwm?3SQB|Fc4*Z|K^iRzRZhO19Mb@zj>>{AJx!rvtpZBrj<;yF}rvd`g8iVe<
z;q+A3*9*J5yAwy6;|OXB>JsL#qgmUupQ^ZLPZbg%(bo;_X6+}>^P{FN#JBKty{QNG
z?`K%b`?@`9L%a*CtE;CEHa)(rT4QZ)zQWtvyR;-Tb0w6UfswbRq4xfc1_pd65ykbv
zDyMohiSg$L(WZQUa=3zJf8qpzV(^Z>XO3&l5A_ha<_EEuW?*HKZdurp|MchypSMpp
zU^V|S{In@u<1+YHRc-BMMMPUQ5bXwW@yo5Pma$jMS}bOEI{OBWaeqv{b*riDxP`@L
z5<2v>i81G#j$1JaX<{B&)|Qq@FEj7JND|^s^LQis@q6On_7xOlGp2IG)g_R{dW<eN
zzHu=AM^)AA8|@!Du50=#b8l;`hkBv{He_vY|4PDQpAm0zQq<vq=j%KBo=Ny(*U2Ic
za6S0rT~@w}vK<UYvbB{}+o((ag9i$wCSG1%EL&!l*)Cfk?mRZz8O`L!5B28n^2CUu
zkWK{Cb;qR1J59Pa$}qgte7UNzam7VNcAqECg@tMJrl#DMXKQtAvB!>6+uLcL*>wb6
z_Ev7~myihdW2H~Ou|Gv*<K&c-I@Em2g4EY-ZEmoB9%N_#in98k<&;X`r`FvC2-)Ps
z#44iT+1YL3!Dxo>u_$0?K`lGSlO2IkB#Bd-F#=My7(<hmy)tvyDp`w{WHI_B6wc%^
z*+e!`-S8E-B?)S{A6vzxdQCERAYeaO%Cl$Z^15R7;!q6e6l~}wL7ihYfLC450_656
zD7X^mUnjmAU|6*~nj<eR4+%yPHFV&^hsQ7@lsQRVF)s#A6UCMe$4CtdqkEw^Z+hAt
zlk(h&nP|wQ;~TqT8ZecSD1kV0T1dMqeDR9_`6L!^ePbgG8afjdEXU_z2N6#BSg&-5
zH*}2eCBBnbzZ{yBM#!uZ^;kf^-;3MD`;@XmzXZu94bwL^{7}SHPG+%cokFLqWaEGC
zfWKdD{mALz=`kB}XbqY@YXF^jpFdM{;M@vK75O&e-~+<JMW$)Qjph{=o+L^sX19s9
zwp4cnjdoO!R2R-C$#NPcsK{d8YSUTqAsmT4d-u8#0Ooj3Qfg`{8w#;CnXKp`r=^uX
zHP*$7u5lS09<GB(+04G6DTh<ET|g_3DTw6}egD`rfQ;i+i1hEi%)DoOog-m!^}Nwf
zKdB%Th|9(})e|%tJ0li^Gu=2%HTs3?es@>b>dMN>S#p$mUb1#q+@B$Ea3dPhHCU-B
zDN1~Nd}@Ag4^}7^eJfy{M8oj&#jmgMFI55p0@N@OLHmW<w<p#gom)`To9fRDY;M!}
zhNmMnSB!zQ{ymEGH~%VK7sY~eRk|z7TVUOmNO+O?BY#4}I}89^%-tUOTVoV~xX&5l
z&kkO#g8a040D_l5Ep5!NEI(fqF4lnqh26d@%26nwrC)&7S8zZ5V+%T?G$b*8u|MFW
zI5c~HLME=GBBK(z0|dFDX9f0<Bpjf5KvKsZE4`gwz2qSmwgfTO-p6M&;M3+Ek=fe_
zD)%)dB7y{s(HY)=>4O=J;w*;+1pyh}v~5|~^FHWJTGqJ^(ST!>b#-fq_y;{Bk-%Ib
z^AdWr1C)3^q|KDHG#Ql4si~>GJ<G%ZH&{BBSyKK|mth_e+8_WVL<<8rZn+N67&{E2
zGVnAAzv;-4=)NKxoFS!oR%HEF&9hv4!!<h`SAM%b3E)gZwnf|WCcmDNPM>tt{~bGb
zu7XWwh|EGLjqqO~L|T|B%F6O%4~ZTSH4c%X4c2cal_OKqz$M|&eF<!7X)!;3oB^?L
zl>5671P)8j33Fmm-m25i-HpSl8!p|yzX!7@m;iA*<mCkcttd=qq(+7}PEv0M+k~@O
z_%&SyFVEPfTbg)@9&ex0hPw(C2{Hpy`x+1PI?EBh8>FSzk%-a+sg2;}kx@}!rwBg^
zE9FnypMDY`QM|kap>OM5|3A`OUZ=KGF@0Tfa&m)-Js60=&p)prQNFyd`OM=PV9Ovp
zx)mfLF$G;)+mya7h<^!5$$roT)8ODWJMJ9K*nsHrtiZ7mNKN|)o$baRdHG5RuB+Vu
zB&xxEnman`Sab991@mEBw{8uQ5hf9$Rp<geW@?+}S;&t|?oCtU-Pf1Hu`EduEEX%{
zK|z5S02yNhN(n+R&Uz+QL|<Kn5K8W>zR15$pF-K5nVHFbYlJ-}c8)ftrl$V&G$~QR
z!!c70_4RfRN;4kz#>IzKZKlsIT)TD+Zu+UfTllcb?HnP*<0`;8Ba{^E5tG>!gm5u3
zipo%cGJ=^b8<{V)O%%lVA}Fne4-uH=PEJ?x7R#%v?{tq{OG?VXwIMFY{9<rPd<571
zO%BYo60FLyp!*7wX^4tJ1T$EGGfXS!omC(#w>obATlql&FvB{7`lB|}0Hq$-LVj(K
z{St1||IC@l#Ke{W&o~kN*4S_BmasjuLuw}a`!8Z<q9D)@G`wnJ>j6fcROsgq4#RuL
zjz?^XA!f*=C{wv_6%ox?kj~KXeEs^(gJ;HlY40Slh!0CqnK{Lqkc_xlB_&dL8+DD1
xghcpukPhk*0Z;WEz8dyj*j25aks?!b%MAy!UZ3nMxJ|;(k;5j2x%w2wzW|1mW;Fl+

literal 0
HcmV?d00001

diff --git a/git-main/assets/path_planner_assets/Big_hourglass_fillet.png b/git-main/assets/path_planner_assets/Big_hourglass_fillet.png
new file mode 100644
index 0000000000000000000000000000000000000000..3b93248af6de958d11a09f47af24185c507a2dc5
GIT binary patch
literal 33234
zcmd@6WmJ}H`#p@_w19ww(x6DGG)R|9s34$7cS%S$k_IIuAtj}hN_UsEl!%mccX#jO
zTI+fK@!NZk@qT~T7>=dH73X=xob#CH9jK%rOMpj(heDwU9zB$LhC-qHpipS@m$2b0
zGXWAu@IN6(X>~_sn-`8Q2KFYXCkBqTmNt%-=7!guP3#@aZLE1Y1Ub0buA4bJ+Byhx
za$5bbAK<XDH|6}DO)3f(!L@y;;ebLB86bbqzDi`8qfoCU9!cGM?wYVR=Hg1GGSa%W
zk#T^I`^e`V;b&hC%nwuqc$e@PQtqRklF{G0f~NO0YJvD({+)m~KF`t)Zg<^Ze5d<h
zk&%_@Gj>GhN$by_RF4^Ne9Euuaq7Ynad@#WKAhN@$h(lhP3dQFodN!HZfqDp3xNL~
zu0KO(g)bPIMxoxrzlSK9eE#_X8Qc`)`-xBgU-az=&RBV7Y$CdZ^up#Kau#Oh`Pvo-
zmPUUf7E#fJ;NZ)jnr&I+qS+ccI)Wt54;u$Q2Lyz$qLGDrTb&+m!LN2q&(F&Y7n->3
z^{YL4{P^cbih*36j>(3%Lf+>dxz&2A>1k<PmP1^}2OD8;8z<@vZBDagLTTd6lc^<o
zo_ylh7$Be%9a=U$?P22PCia0FYvs5&J2PLu?o;WsvOS<>W4F85E59+At-<>^hNJ7(
z=LZ{&ijq>>7%W;i*BOomPd4fl14)?5U+vwlJKLvDl?gHI{UW_OT0u%g6h`BjcSkLE
za(4G1FT3RB;P$xt1~Dn=+vMbAm0{15eGMkP3iHu&yR`K5-p>#GwX81|Q^Q=3=3<IY
zcPQ^#km>5`#tmE)b<+wvPHwf*v)sJ-)?uN$z-~rH{A^cQ{A884C6rd~WPdH^XWi~^
zx$3PJ>gt1WcUO0J(;Rz-?Rq5$q=VIhR=U&|UGb>u%^&z=Z0aAvB+g?i92Um;(JIxf
zt*tdUR+g9JQ#a0RJTA@-M7Nqq%Yw@+`oA|dH*>$*H9Ov2icFs=u^Nf?@$spO&eE+B
z?h!jk=&!sf8@dUP`@6!y^k)pG;>X)6Y$Jb*%^SVXcjz+|lNAPYb&AM>0z?HJ@ztg5
z<s+G&pdLPah`P?s9&+P>pVIf|x3qP1Zs}GF+SKe_`}Xad>WS6g;=sj4Gjw!xTNjs1
zsX&srh=@-oC_*~XSg*5VG^H<6xE*UfutgYU>lm(!ziuRX9h>8kvHJM?<2Wt<F_`+{
zt7@W}ryJ64YzR+sy5W71YS#OuyrQDF*jyPd<2rcE!pNBKdE)%#%NOg48r_;#eCEI3
zO*Q&E%>DdWMaNn7{_35U!>ySL=QS$0PuXA9uSz!{H)BOy);+@>NNv-Vpx!?W4Gasz
zNzre3<5Qtx`{NyMF)U84=SiX0*(*On+Mh{c?y+L-{HRRD<oRA%dL}Ne4`>+JlM4&2
zaHF`pF9)n97QSUB8D5;9$;a{dDvBR9{l0&Vg2J_9`_ZFEe{!^9I$}6?{=Uq6ny-J4
zSw6O&R8h1cn3C6ZyPYNHr}yEMzo4MtW(&2=hlGUA&8bGW{b5s$I<GU@l{)7&&H7O)
z7m>F(L>c$qVh2;*y)BpHW7?C{Rova)eyfjtawIS~IPLkjXKZ@4qJ5=QcP+R~yA#-G
zWu@rY9;2jZlbBdob{3Mo?e~^dye`gM#=S2*N5{s@d%s|flv)|V%OX+aak5s1s^0#2
zhwS$A0OFf6`4;`RsRXP$|CYQIa#^S8h-NPuRlq)k^>-gR2nh&Cd9}BUyy`%XmU6Z0
zmPpIdls|n$R8&)5-TC9Q<2|&+@fs0gV&dJUK7Z95O^rRuYDgzLJG=7oa@6F;hGL#>
z%}|8{3&dFE+R5rz6**Vg<MHlBA_@7KmJoJNw6U?V4GQ-P`#I~1^%i#%>Ga1RVaqsf
z-MV#nc&I)Q!=@1-ad8^im#L`yRp~Puy`t2%#2EUuaQAChuS)CdU;q61bFs|?9VaK}
zi=Lz>;SAF1#b(5k8LGLkt?263b>n93n)&)@gL!&&oOT?V#R2|wui7F`(Oli!wx)wP
z?GHB%oHxd;RBGj7IHG5XIv-KT+T5IIkK;A9wYRUFO9}Y|RVKEnNlGS+&U0`Gmb`s?
zt|KRUqweB7_hf8UMwFaGJ705SV}qzZ+57w`FO-GhC|MKP5Kky<QS4gRSXfxzym`Z_
zmYa~ywAL1W6JkKA($PH2^Ud40TRS^5@Ff(V<<JLytG}C2X13Z{l7D@DdQ-E^`bldj
zt%D_3YxqssuR2xE8GCabF=du@6(*c)Y@OdnL!_2QD;$JK6yIVKn2nZmL)>S|hS9mO
zfBJaux{LkRw6u?WswY7ss`KoQbW`nDEG4P+;Ri%wQqP~0g;3r7;&HTHmhfuMy4@Gj
zt|geVsikFmIV;b8x(T<^dF?U$2wR|>wS%K$_1rNvZr>VGf{Kfa<=L&uw%4mRB4T6P
z1SUKj6uHl-A<NQ~KHpa@^Pbvx$6tk;5il!(L}e|jYBmKWB_)lZZM}u(vu7j=J;|Bs
z1%|3CD}TN<UYs9Dz*{$^J&GJEc}cFEsZg`Fb@3!irNFRxsLVz$V^83?_l!5%{VE+D
z;i(wju>uvp<wGdc6#SM$p0va?)YNhw9-?95$7UH;xVX5On3$u^o52C1<<OtoJhu*K
z!Z0?MGLtoPF5s_dX5-aD`qsY3rX8C7-&N3fo{&56Dk>`au!-T$LXkFY^do>J&>YaI
zbPVJ+YEi0owY&ZNtL>nXv9z%<qfbAn*!rxDUOjwkw(aDi4|XLWFtDMyxtYhRyNlmu
z+%ix@YBlH>x%JcZ$5(}2);nXljRd{VMG2_+jp6F@v0Seqllsc-j8I5<7}WFbic}PT
z^zB)Cx$PACgx3kXxVU&U<F=~BpRZ{37iSX}y|te135kj3!-eTg+||QAXc)0PCU{|D
z`xJRK`&3wXWcrZVjEsz24)dKf?iLT*BbdHD|3(5i;}FfPW<8XD1G#rs{M|BkUZa*^
zEyCMwv*EIr@bC(&#|usHp)=ov?MaaEP70wG;BlCjmuDuGINij6oK`(a7Wa%_8!786
zGVSqx`heI?3F+S_^Hm$QsmARQ!SoVI!$qc~G&G&{uQA*X#$4D<tQq}a7nyF|!qwB$
zqkFY@gZW9kW9!m$=t|8WZakn6d&LKs;0CnAckkY5G5g%RcQ0F~D*F8FWT%;2&lYMI
zQnMwzYtxx{G9B0cesmdk^M^(}>hvBe2m1I!KbyI^7`@uLW0fpb4JIGu40(f}QMUwz
zgr;U@9>npOERIzPh`riv<NJ!GKaj0aURn7&SEq{Y&toY%KIR$gns{j`#*T={$XgnP
zj7Yv{m06b(E|h*($&!J%I-HGEw4{9>FyuobNgPfCQN~q!aqbQkBGITU#^HAalbqQ|
zDZ4)*?QhIq49<`L1N++Dz2gx)*yfpzsU#&O)zl3O1uIy<3poJ)UJaf{>+}Omq>v;U
zSXNd>m%+in5TQun*Wim!&Z=E*n?&<1nK}yfqOm=a1($%J#EAly!Ja6TRzwCMi50Ei
z6IQfNY#SS!`ctg!t*rt(J_d$u8+l!C%$_-$Uq898QPmMRy&4i`Y=@=4_0G>vGk0eH
zA+A3EX!+X8%uFgg6=Sm9-sX?SeoA^-QrF7YUST7&?(4N5H>^GA#XVxJ$10yflZJ+I
zOXWM+M(qg)0s?NAIW9e0{`2i^S((7=*RPAs`}|<dv_5Loyt><;rPkWt|M7Ra9Iw~u
z;b<1T{?Kzjy0_Pz*(R8L+z-~7V3TcXkNlu;Atj9q5Xtzf6?VC}ckeJYODv=TRs;kE
z87=)zKRsGV7Tx=!tZEW3V50ziAuuQ?)n#KGX;^GJm4B}FlMsh%XW$qFigmb@`Fy(j
zQl{ud7h4`gQahA+3cy=8Wr9)qJM&#>nVCBi7w3aKl?x#P<0%j%+I3#ErlzJ)zMlZt
zqY$!ZL_rl@D4Xz_fz-PpEG&F*hnaz);`RgFl%WET7}WS<dwU*8to-WSr>WS4goFsV
zYHDh-g?j3BIE4cM#Mapv`#L{=^w+PfSu;|yvVB!98#G~@Vq%FagLw;wcGC6{MMb=!
zp`oRO4;Tj*ujLOFc_gC%#eCqbJ^b<e7zY7F(d=3>RnBX!OX)EW6%|={cp{{Ou4(*a
zWM(EIBQti&PD#1`?Afz&`#HSz_4T;%J9qDX{PX8|$4XRGlt{}93hcnZKuFtjx|b{w
zRi~$?mk0?<S3-LYCH|mT_t|<FeK4>u>ks7{xUfO?(*0;`WY1Gf5WEKq=X$)9xinr=
zW#VaQ$S_vrk_pJvaq-t{d~%M>Zjp^&rB+(eoO)h8<Yj<t5#Vc5aT+q42j$(>)pha9
zZMSFx3hi2tIOxe3S4c<<X9A?8X1#v$;_6S-dcspx7{x)JXr6m-&prZdAwO2>M9KRi
zSfwJb_81S!f*%pRwZ_3rm;?zG)z9O-m2b+KgbfW1j7&@#YcWw#@4~`**tITD*n~6>
zp#ZVv*>v7?ytA~l6g`^<$jv1?=Ao|bjJx;ot~uV-+i4>W+x2}DvxYs}^5_&46c6?F
z^`n0#3EI7B387X_l_7xqJ&_NytME9o&u|jpcmdT86=#i$0Wd0|t*vdOHZLpdPHt|l
z#``UqWC=k2Y#+(n@vS}d05Rl3-pry!Z)Cg{vYW<)e#pSa77VCqvz6ZaLu~9rL&GoW
z@(^{y<#sm#5QyUt(&z((a$NfDYuNn$X^!Sy)T`aa23SVdoi2glDi=;Y@3Xso8Bb>R
z2K9P+U7beMwn;tpnv)hsIQEgW0r<E83@BT@;LR85AQD(y4QsRCX}FOriZ8kogq~-q
zh5#R!T3-GME6i3_@i>aL;fF82My-dC%J=66vu)uXP=@2tWu%%E7B^@MOpiFwf}uxo
z1#58#yqu^N(<-%`nr;qCfWi($LX+S+n%SSP#83p8AiMx^Rqfv+D}vNE;)%25uRH>%
z14)lfPf!1;WlIqjpmK%p{!D9FYflfS+B9*v2=6xnrB(G>ITVu%w9e_p#fPvQyjEFS
zWgM9bi9ZGh2eHE&-r<rS!V7CuIkUqTrvbA7{hOYiUN4^jT+JOPADs>xD|)<`YB^SU
zS9Uu7?#pWr{4N(%a{$Lk_B#Hi5@(v^=67~-u+VlA_;4S9%xWBoWJP*`QR{Z{#i_rZ
z*O4zQk*1Y{on6I@wjB~I4g4A=6xinG<{G!D>FE{WRiH2a7VFYD*y)jQSpIV>nnUL&
z5LY)~S@vmH3nX8o1N)jN2(GFU@x{CPbKgBMAi&t4M6!Jr7VLDlPqF%RyMxbWJYj35
zRm<vPfqjy??CwI>Ct3JuTPLTv#opAkjEvuP-rn~gJg{?eN{28ArWF}jrU)YE%#aD8
zf?l*eVpB&9Pm`sZ11<OmP-CcsTkt?y<5f>nWrAshBH&%HBHN{)8L>Y7f{6m4Qj}d4
z`34K0goZ{Q`Zy)GAtsQGY`r=<A3&+k3Jj(HWn<-YPhSgoob3%p-BQLD5D);&3B4*u
z#Ztf;O~B$$0K)o?SMszpX>86l#w`DQeHwLJ1&^GZ{O89ztwa*1`Xyt=JX>Qf6I;*(
zr>CawK{t&Ruo<Ua0m;Lj<uS@39Lf9W=#`E-&&eZ*i%UdAnc5Zhq6ec6!PEllxvk|M
zM?3&?W&j`<LH|HFhC-q+x5-a3alj+{tHX_e7vILj#PoYXb(#bgVBC`=1`QIat#sa}
zcB<Lx4FHhL2eK*IwMu7UNqvs^UmmQF0r#2x^G&%k{%#Q98I*U~DlEmF4yPJ!)<xhh
zmgCiN&TD@Wu;jct)Bq_&$!GR~32nUCoD{)HNOA(%HUf0SXZC9{x-}6(49e}?*}=pD
zTsJ}3X*qfhVGzJq7DviB0ng5+$LM|mR*<b(^7H$s`$ml{RO_KyPZ40@f<59VYzR5C
z7n5e>4S7ZG9&I|0R*a*To2fjNm|k&STQw2Z(#W(zzc*B1<hEY1fHH%3YHx4P)+m|}
zWq%2LWML(*F5~gX+o;uvx@7adi~^`o9lS9%No^;72NT}OvUF}u+m#TO(MG7tlsxYM
zYVq2Pi|Tsrsr<{F{pa}kPR}0JQnR~jIGvxm`CX=b6B9#DB({6S^LY0&T=Fs%-zA?y
zla50718ec)#hZqPhJvqlS(B2Iip_e_0ZwF@`<{P;TL=mZPp_?cw#Lc?Q{0o6znoXS
zjfaAZ7(nd~rr<_usn*ZtrY6u(a8TlhlNiW;0y>g}c2cOVM_iDxtGF7ciE91{{TQ0g
zTc%;4Pt%aL1*4TUv=C%~XV~&)rl)Nk9n%aN{ai-#ppdENaq3pLQQK7CgY*O{)CdV7
z=Dx44iE_9Pci!6G{xLC;Y&BB4)u$*yOh(oO1pTX8UXsc%&{Dg}dbHnteF&UINCuN!
z^eo^A)8A>2pg9R?6^yQn9jp!;m8{Pv=VWHGAi%n{G_bAaDMrc=ZwYFi!NpY8xi0x+
z=W?Zp=~*D5QEMm@C>&5uwFW5tUPD)aRGhPtJ+G{)(i&5!7@OHWZ}02tTi$~QZh*>&
zWMaBpOv~6<VyV@L{o3CWw!tZDuj3^aU=5NDZ?G=<qu9pB$1R5oeW9clSq}4zyDiXy
zWY!7mxpDG`qr1CXHSY;?Umcy<O~|pg@ZRC=#y=XHZw<y|?>jt_lQWub3Ph?xdAVRm
zq16aK9yv!R<aeR=AY^T1cz6TU%Jcr7MF<#B;QUyUJtE*62qcHfx=|h$6oju&=b3O7
zXfkB`ZROvpwH|ID4;;vE0W}@iR_6nD3W$b6+(U4r%w_>ZiEQnP?NYlj_KcAlQz&hP
z&&i1^Tr5yz?itr43)F#2FLWoSLdS^HJVrz#i0`G|RN3fI6`)H%dE_DSk4|@bfYac~
zhSE%dGEn?-aJ}^8<1J-BjiML5g(h;qF@UmGzLZn@eBT!oBU8vrGImWe0f932_|$xx
ziP}HkRf0fk+U(@*xk63d5u@kT4rGZS)>|B~_ZJXI4o^;s%z7DkczA$Vk6L+S*PU+T
z16M&XDac*&CIBpug#D_TL-q9O)6QgxWVpFTh{v_?lLv1lo07g^DX}3M-1Fyu*dsH6
zh31?0F_+p*B+bo0pL-8G3Mxt76*@WvC_fcY%V`gefJAN`9ApAmF18$w0Kx0KTAo*{
zXF@{4A-wU?{3ja#^ISPlFzkZ`5WNjry%FH&=ii?PB18suX=3{wg@l9z1U~|RSwYK5
zl?{6V6y|xh`c`zSJ8X@R#~~NUAPihwo6#nq0(6-sd$xdB^HsfoVZvjFV8Z+2OeeFD
zIDA$4oMpe$_;f_*eiH)|6Bb}AU^ZL85B@p>lLGjFv=9&q`QIzePV^qAuC@~u_;0E2
z-nOFg_LcRMtQoYVjhKxP(WzVW1<B$crUJx=xInQIhs{|YVK+le>E4Dt|H$1s&ydVP
z6mP>Ac?%3Ok&OS7>{O*`)&H*_gy;ItZ-eS4ri{*NPwh`c-(t)|Oimt?Gs6e%XuQUK
z;i3G63{;yOt+MXDgRAYFe3zt<#@^1z%^iMmx*!q7ra_{nrUv~K_%G8P)$DvHGom!;
zzW`6T;^Yw_rP%CgrQ_0%rM}FfVs8be@9=OE36``zv+Qug43G&AkB+uL%X?a3Z<4E5
z*A0ASX}E|5_(_RV01+b~oBg#BSs58@5Xn-Z+9!y*ML<&j73K@aiJ?L@heDiWBZ3(~
z7Np>P;<sYeDrLKRM>S0`Sv(t_{MkCRsbY(MJkX##JUq+>b7`SJN3S7D9?)LsjG_7Y
zT-DXpu5%yN0O^|^Zcbt1;DDTU<NToRLZhax-FW(wP3>psM*y&uAVCd{jD%b_uR|RE
z=<ACFHJgN<-ewp|SQ2P#PzT>ZnJ=;Ep9Z<FRM>iJy7_4GEfMs=J5X)j`TBCd=%mQv
zq2{+t0dxTx>eHeZPfD%F;+GbR92OMl+*i5bX#jsrL%m$+k+>+ftaDr<NfdTM0Lh0B
zR}hswJ-Mpgm_bl57V6>7kWttcsG0~+0lD>RG@HhK(Egxcrvh$+R`TQfIn(1P6mmOQ
zCXgnLomK%R139=4We{0!=yyHO<Qa&B=l+SNdFDo+mofI<+`(+VF8iw*$Q1zzZ0+uL
z7LWDx5cvRChKn^r&x5QbKwvSn9?_jnUe&ponHi00S8gDG2=fPo6+Pee$>H?S4(NVk
zzCoiaNSq+5*7SP;hWrd_1jymUkj9{;xdGRr5VXAxoA`t4GSW%qjsTo(LtYmdHsiq>
zJ%)y62C)V*T8Z#FD0A$AV|VhZe{^uxbwX=nYXwyr>+0?22-my}!l1yoYoo=*&O%RL
z+9OgB5n3{yd{Qqo#)Sxgs@MH2L$A&YTD~8E?Lw&kAaQpA?<?Hhsfz=g30wpQ2zE=q
znLw*=M1Hlv5DOTm=+SJXv9U2~zUk^D?D71+$fv_T0r)Jy#~!#*ESCW~0C7{8rCbQp
zh2w-jN|kI1UAks#UFk(B&YEztaWe48wmsq3Szp6j9PZ0+H#av$qP5`qBF?MVZ`^qO
z>z5LWSs~$J^ZTm^eSvU7?+lzSx0~7A-_N-3i^pd@8ViGt0w}UHG&E3TX#m+70UZ64
zt21JM%Ar%K9`PM?8&XQj_LO^X142WwQ`GWwp-?tIs|8pCN_F%0tF{j}I+Mgcx$Vqr
zFug~B6CjKCbLGh%+qi&%zW{oaPZEuT-G)*e^yw2d<kc*w_z2XFK7*1jhpZ_My@$Sr
zfc2;#6oTP8ZwU}hUaSrkoWi#8S^XvR!6jveI?!8nzG~wPpa7xzfDX6dJzz|vI?@_K
zEelF9aP*94>5nn7vC)-4o(J(Y=jZXs$qvX#2ybz973}&XU<%9OxG{dF*UY$m{n;^;
zF?JtA1LJ~pTL@1?SBa4D0oI9(1OSV$t-L4a3<W`F&Phq>3WP;H@K}p62^<k9rRr8V
zU$rX=`zy25@**N4&||eW#$9I!VB!*%oJ<b`qE*NXW&Fvm)*8Exy%zV4;UfQlfJ>vJ
zqiiM&H*e<bPn23w!y-Xab`*|2jE1;}>BRz|UDbBW*XUSC-^=m-An-^*p{1h(pNNPE
zI=?JD2lN&6PFw?Ml&m0f0q!B=)TOzud}f^vq!f^zrmp|HcgAkEz;8s$|DeZyN)YSJ
zu`6|*U}IIzxXc`Rs}=i|pooZ84S$?`nYPP}>U_?Am0i%h>WcO10Sqtl0jMH45tJJ{
znDziX(}qTyyLGx#vw?6Wq&EV@Gx>XsgyaVVUy(<)_xAq&3t+}jv7sousj8|n(Sm>8
z0^Ej(p0J_JpcX;Yn0%keF)r(7AmWL{E!;QFYkMn;t8dK{SLk?WKowxGq@yFBp6A|G
z0QH&~UOu2E0~HMeFy^p2#0_%U3v;Z|8g~IiWri58pgREMuK+CuMm3E33V#Uc#ZU7>
zpCT9tl$>1M8Vhr*YPVnbl6%YjaY7Evzz18~Z|!_jh8Y*Au24qA3=9lV2_i0`z&`t+
zx`@=)y?u)T9iqGVyfcn>b)+oJrtU1-pWchY2VSM?doVyQ6cA92?3@5l5esZ8vDj2=
zkC*QtSatEUe=OVv(Fq`)JkF06qP4yNJb9k09S2<=N<%5!0~^?g6lB{ssC~Ju+8Oec
z2wc$Cra^iXz|@P%k6G|PD7BR?8{O+;RT?n!00k`nHYl}<-AQ6{u=hid)BpuQKZ}A~
z{g9Lt3QYq*bt+Pkv@0SKMO;WoNsXL3PA0Yi(?B7IL6sjgtwQ^`$54)pR5C#EDF^I}
zozBR@GO=?KI7IpclO1X7>WF#@Qo?7unU>wPkr>#xt+tzC`A|cF=VHMGr8`lC+}qom
ziqA|Eh7AZd&rJ3zeAG$read})evXXF;AKf@X`jH#U-Tml2~=Nks7*){Ii0vT)63AR
zfw-7QkSz#nvh<!&5Z|D**?`!^_Glcw(1eVUAdCXvzyAVbMqsovNh|Y{ll4$9hpXLq
zVdyjsy2C<hn0Vpsnc3MUsHNS&Kp()k(Y*hAzgS%|034ji@cyKW2pB=*)z;R+t3sj~
zm8>oIXMwDa2z6Pnu^8OqYRe22=UWo5Tg}TA+nrveqeS1+EpmDoA-C>$R!VO1AHDa8
z2hC$TkmV9Seq&cx2=vk<?{hbWq+&XqDwti;c^w)+eqSOWFaZz{7s~5-><G%7or6QF
z{oGGB&0^NF@8CG#&j?IuPMYh$%!l=r|HK~xb(kBZ`RSP%b71r)?(nEE^I(NqWdwc5
zW4BipdeP8wuineS-1G<jgpMl%Apoj=S312!@FQ%7)l(*7;&zkA7fo<obA4U!GpCM=
zAQ+j#K*0<|7wFHe!^3fpBAM;h{@w+8;tydA#h8(UBNUlBlk0g9`vB<;hDhwq)03z_
z-3<U46)B!PAnbnnBL@|aQDC;?TK%U)G52V=(9<$&osP7!f`S5|-1R&XR7mau37-M|
zCz=O>UbXdoXecv3KmWlSa$@37y|ntESMj3(9hLxwiVT|o8uPfUYj>2w{H^0=lXdx)
zFgN#BsEM^@9ioMTJenO{)vHX-DA9YMvKly#Mg~0G8jXm8Yce`)sB#!7(LK6rgL(82
z_{f|MnXx-A{|UsxzcxCkPy<UfS937l@k|34Ds(wPw{1qyxnXwswXtAU!_UAL7UTSI
zh6uiwt=S_@_x$)H+dtwe><AM$9zsnXN3)q9c}q&7(9qC;QAI;3A_Z9!Fk3)yFeBin
zv^2&nPn&A!>ZPadSv&%z6F*^El9Tk~Lqvq38`)n8AwaPZWgwJ%G=Eq4P<IZb7j<>@
z(j;Am2tC#dQg|hj`uciFbPS9Q^9ky*oM+0)XmIh_i}Q^Owzv0DAl53t0Cn@=pe#xQ
z8hnlWK`D(XFlvxF#@_!&-3;w$ZuSKn`uq3q-2~P49U59%JA3<QawP!)v~3{Ws^;j`
zAtRt?bzYvQXJ^o9On;@^1J3v}qS|S7C>$0p40um3$Xm|qqwNSK0kUZ*qyU168BCc#
zT}p#4FAr~lcr%_{jU)w@2Lv}->baEEHuhQ0O;9+;7PdAwk+}@??I;NO-W)9fPzKbC
zUWBAObq@~4m~=#kfA}B?$QMyzHmY|*P4FlXKL?N7wlRz-A3#pSObr{RU7w+umwt~A
z2$;QX;$v91t%I)*RsaoH37rn0GMgZ;j2Co*aL@&R5|uv(20Rr10u<KtC>I8yQj9Ff
z+Wrp;L%i|7C=Am3|0O_o|D`bC19}7_f`14Q{QV!x&k$4OE425tKyVls_8%Q34{`rX
zkD@LD5!QqJ%Fcg(`@gOsoo6S>|D{omIO+)D0mda4k1g}xzd|wjpAUu&&yCEIn#6DY
zmw2s4V80Id?_Cf^d+Yz0IW=*7L;FW0MJ~-ehH>p*vbGwrE%BcVaR{;g?<+;Vg-)gS
z&kZ<)gl?meo%}P%T8$`5<#=sax4Q-j`hO8Td{_w26L=nuZ$$r#6k1!O@mW&%2e8j}
zU~UGoBwc4?y9`3){rmS_q0<SuZKs)>Kv{*-d-cYR8?LWjJu9(LfdOIEk|4|yz&1n!
zKYd#*w-dB)`ywi!au2!*z4g#}FQ@w$>TR2#Lr*gTOxFTP9BHG_-oU^yQ0NKL3zQ!i
zfyx7cSBT-zS^V>j6#p6<G(-@rAbMI5Q4z`<6vY=HUzC20fUqh2WP@gE43oMOL!RK%
z3)7xzw;iMwf};iC&qN`j?Bn9$8G_9Rg-{ReO2_uwx3Xbc0WjPIyhR$XCZeLqJUl%S
z2-e!la&naz=2Q;s>~D`Y#O_hI>Q(%8<+3KwD?{3Z<5_nmyN`f~`#u{0v@eiLWlzpg
z$RtuJ#b?gR(vl4+i6&oCQv*XnYHSML2Rs~~@=(UtuLN1Gdv*jf-}~YmSu?<{p>$$D
zp^DmQIfDXYIa(f$pz#4HNXX<!g@ctf0OnOAbS$9h!vkhPHf*y*wl{^4DM5&S5{*O=
zQgGFK@QfS4NFp!Y0~{zrl}>k{lQ#DDhC?B;%c>ei;5qPN#4rNV1h*D9A+0bOC=4Ai
zwTaJ}0q|%QCqGZ71o+qn2zNcf|Fe=<9EA`%MBIhx8^X?1Tk!}9nQz@{x6lE50O02`
z&x_X>IKML$>5*9%8PjV9hNGbn|JSfl?vejzDFoI~?-8``2ijWS7ioMy0_v6^&e~Y>
z<hHhlASB=07_VVpf#PWWQSv<U-!gbWmI@m$M(ACFvY?_U5O8Bg>-@gAGFSx0tmVPH
zu(~=42r7_G1E9EQM3lis!~7K=)JAFGjBIDe+S=M|826BW13sgKVIsmAK;f|j0~GiI
zhO(_;uv-O{j{?bO#iS*SSQR=tIz+dIz<rjhEd<dhBPE6Tav-~)xcdnh0)X7|IxZ?f
zmaugwD~g#2DL}J|6LsT(as6jNR^TCcE95Y*^z9jwmdX<;Df{7&*Y!(KBSdy2J2A}e
z#LGUEV)WM9o*3Yh(`qh=$H2AXt{<3s$kDqeLSKsb6lcj~3DAi}{!QtD5Oe+Cpyz;B
zF%~0wU4Hh}E5Dq^E5za6?Y;M)Sb08!uOBN+$cz!GZEtO#B|NS*T(O0E8AS63ofSsj
z`h=G@?We-<zj@S7qxSrBzO)j3Iy#$7F7x1lpqQmas@KO27<dOo*NlH~YUSK{uu43@
zl3>!FD;2%^IL$bPrKg`m<`b3lmXk}VQ!Grfi3E}`Bcfs2wi-lIPcu0^D;X5<qd0)I
z^E?gzw0!+iQE9^DFZvi)?*?l>&M~=_@6xWh3f#A^Zk0Hd!>^O$$l<3P+XZ>TE0O-r
z)i~GUZ~Jthr83?1Vybia)f;-luzb!XbY%fLqvaN(=lDA_N5ajn)%KUHyF>XeYf4Gc
zTr6XJ1<W=6l}KOVu#)g}n^;@eNMmkpxyixleL>nmqx=SOJE;oZ%&M8;O7G5YTxm$#
z=Q|XYu0*Zfx}^q_Q2o1jE=iU7G<Sc+;$qPjCb)BfUl;5X;H-3Fa_KuNb|Ln=N;RtF
zJ^AFW@3#DiYjFEYm_5(Y?TKumrdU0~UcTxpi7VGKy_QfN3C}?az7RU^zx?Iibwe8<
zXr!86gf~=ftlhSZyOhdc@Pjnp26yyNUfPE;>OB5ijhr_8FFJSbx|YkM{Lmyegt~T&
z1g`9DQ8BmB%^O<8uPs9%mE|J{9=aojFG!u8#I(3Z&^pjqnP<@B!FB%l6fcUe?2_sl
zDtA0Cl=z}mnmJdjGq|g@!jYX8WuwOO_Ydpih05kz#FKHKR7i*m?o`z-OEybfD=4;A
z{GxaIZ>Sadd_=wIu&R?>2>an@W6*(F9&f3;u#C|!((qucq0TkKNT>W&V%(=NUhe%%
z{^!-k8WZ`J*SVd7`tmJPOp1{%9$b?uOp;Xm0jq(t?@OzHDWR-=Ac-WC&#?U<r_!?Y
z5I@#Hm>(}r*NQx$(z@N(9Xzru{ENk%m~ey5l?I8p{C%#h{lxi}Oy%knoF3V03rq3R
zTXua3Zx|Sars@THp3VP3e}S_**{<e4EKJkR^cV$CEEioTNlAI7?uUoFpx4~Q%G;Zr
zf%@s0_3d~2tYy2k4GmX`GpvMLe6!}gUej@eimKFHO1v4Q%*?vOZUT6^@{qgd>GG_{
zi)$W%{1=qgE4GX=tZ2{CW7!XOv4m?{M;Xf3SRS6NR5T>{rl<;h9llzPXYzM$yM*tB
zjab9G693_3$KJwP-K95<p==6$+xMbdDFLPoFnOGaGAVQ##a{#!uk3~AG=^(`!BoQ4
zFEw7lcRXUVq_bJS<2se*mY9nF+>6TMz~@7Nd=-V?z17dW^6Kufb5)V$+-B_AJ~%on
zS79AKyH;AfpeGK`7TzA)Arlb~yXD3C`*RtIr2FT8t~%RB&Uz-inuNb1(-8Q?JCE}`
zUx=9PfI`sN%dl<BA?C<#>}iIz=+C2$L9|V0hc7b^3><T{5`K8CA6yFq{3s+`N@~zL
zzn$8HFFI(N_P-x@_K<vWNJd=(&$$b&QIzSjS2HYc$wEE*j=Oe6bay9vE9HUK8<XAq
z)VG1Hcl<Z+pOHMr-RtnuW?&%tIx{2ubazpk`ISqm@<f;wZRjislh0#R(Oj+P>j=gA
z7MrfJfV>3WJclhFme)izm$2ka{xaQc)bFqD3qE6iU9#mZ5s|BE=Uv&)*>Lmfn|?)@
z<<l#8O~n0>o!_i66{y@*MmOV(LM=bFb&Iqi4xqYBF#c{$BF={BqM}FC)%Z+ce&mOf
zF8>7c`AaHF930Xo9XP$k9#^Uqn0fchFz0PV+FKeIhFlM6K4Xn8Y35-n4qk4SJHwQg
z@~KP4{36>BSo0KLpMUnR-W5NCB=Hwxtb*mI8+-RYc9!|yks#={j&qiKT=A2rK=#n?
zj5y2d4ej|di@FqCps71CiQ>WM2St=K1HR-q9u`Pk!O$B5U}zS9cLB{oPJh(6+-tbH
z`)0kUuY8X6ByEB@xtv791gYR|>%<u*eHK|KK2c2C_ha1m0g1;u{v4Q1J%&+ompSY9
z;{Nyk4DI4O&e2%LnI*|EAH}*QzAbWlwj|8?V9FxSxxI}`z2<^%;>==9F<*w;TlcHp
z8`(SGlT!kQVt6H-KTkGjc+CBYOS19)Z`jk<pLUGVFYmn(7BkpD-&vb7TIuw}F1x@q
z2%jHmoMNx<J>?b=j5Q;nlZxED?wl-duxf+bIpX}LOSZe<s7>fS`EJTcBa^vS4eL5b
zTxJq6vD+{8W7Kzc@K0%?if;6rVc8i59qn&+$9*vHa-^yKJRjcJFY>xdFGEKmQ`-cR
z)l1#w-RzxtuQy(F-J)6|!3yEcxZCZcWw7=4!bK~nYfnr!zb(1Fsyj(XRv}^`cY;3!
zlZ$$Lm7H~s%#sTKQ%l2Ko%Nou`~CjVdDRA=-*L_rQSmLsPg*Gs+|gUR<LRF+teSl>
zkus<p;Jla4P+Osa0hrIu;ITmUL6<&e&sNK1o+ZR;gsA&jw=`iXq2xM7@)fgf{_0x%
zq(gK(m3J#Koeub38W_xCR&**J%Ih0T%Th6~nAFc?jASI#5;dF8Dw3?ZUasJ3dTdeC
zwq(yNj6E_o`;JNM<}+H3l@M+)BPnGccZ?EmOBm}a^U4w<!mW!v!Cluw$BB-Mskhzn
z3IDlP-;BW(Mrf^i>)nfw_lKNUMUA}W^ru3Vo9KieK$VEPyqP9<MpFDu7n6wG(-ZK+
z$(@TnQ6EDWM`#h-CZyYOu0vedrRSFhIpPN^P9B7CD6L@aF#fr)-9Ej_+(h?c`#4p*
z++tm8am9L_g+jSZ(Dx4{*!DL$WxaZb4M#sy(T-0W-d0HD&UUQ05Gtd`5*!`lJKh~m
zz|5s5SO|+B6cW7WtE#kcl~t3sk0a(;Uu?m!X!2w@@4V0@9U59Ql@czU<&P=%r#$v~
zuMk&diu>%}($lMR2slRly(6F(u!@`4+`t=|qVBoVHkHUbRh6-+6Loa4G{|1%S}ELH
zVQr_nZ`CBwGnn#%+dDVil*@C+j_%@A?QdA1$x^P=*kj^wkC~RdJ1mj&l2=c@C}{6@
zHxU0U<KoOLZK&+ccfh8ZxWvo<Mv-_YXNrn@@+pezfHXLlLf)}ipPyc+qkMv>$k>!&
zg)q@%>~qn(YqpsV#&$`$l<)JZimX;x80>K<y~i*eelZ>znr@rmPl6R3Xgvi?<G}g2
z3FAVC?b&v%Xfc@cz|;n&R3?A<|EC<ZC@!1S>ihgPi)@@MkpR`Dq}Lzp(N(K)=+%6V
zYNmE|vve%T?$oQ%X6>we3URA=dh1j)LCAR@??R{CUzk2ye=?hP^@)7J6Hh6r^=TOv
zRvehdCAP=l>VwBFj^Bz3u|&*w#x=FJ_QAYUehvm?3LqW2f>E8<N(<~daC{*JM!jIm
z`H1*dK~DnmA4jdyHd2juFBNTGDu0jlQtoAQHT|7~O((0vsat~iqZZ@upf&8;TvJ%}
z$++zKooDV%b%niH;w|dX->ZFkZu6hiudNA6YgW!{UJ0+Bk-<-)dwXkt{xt<A5BM7p
z+p~qm?e1>x3425eVo^*=11rPs`q(EJvuKry{maA<2}gaP|C_QuOb9@NT4bxq8*^m1
zds(pX+JGm4J2|?yrwLy4YhkgJ$2hiIr>z{=E2P~#-1}T|E=(H7Sbm3<Tk<(de+Thy
z4ymR3OE;A&D6ZazntRw%g3n2C`UgSK1)o+9X#c0Cl{ISvI)i+&cw$~{<=)rap&@k`
zpl1(A%gT~cQ@iWUbj8Rsv+5H4ReUp88lNn&x{P5;SpTDT)6Pwu|57)7l{q=7)8lKi
zE2b|uwJut!|CaM%iRlP_^!TXgEiPGOaA!%}jx_5aabWg0gCVcLUrEH!$2`I80}6C2
zj03?6WWT%kbiO<B<*@U7CncCVC?vd2t$0sBB?Hq>_5c<ZR(Ncz>&SuplP63}OwASr
zB3O?li-=NstX(Yy4`a9#Zx!u39A@LmuUwWL)DkmcY#K}y_|j3}tWPTbQtzYxW3uaF
zjrvFHjE1!n58sBVZuNhEn^0@p?{}4y*xhkv{hc*hP)$28?j)#(Fo$)~-d{g+N8SJb
z;*lEX5i4*$fL6pg4Mz4tR5LKd+uGYJVFNpY(5q9A=6-66I?RjV%d{Ey1F`kf8rOxm
z)}J1ha$6>2n-89kH@AnYsswSZr9X_W8~5SZdp|QX-?ZhRc4)RFzD%g|sHa`)(By(X
z{;`adeRDsbL!B|Fz?1hk_L+Ki(N4i&C<rnUZ3i+%hOx8!N*KL_f|(gBh@?zBJR~rM
z2Y;E_ur&oX%;8`z!UJPd#P<$aiuh;1fEsO&IAP%;2B5r`d0Zfxqp~u4p7OJ2py8IR
zh-0coILFZolzCF6UF<n*<N5jPa!Hss@m}xaP|M3K(m%PyoFnmLAa#L#<$=eTnQ{%Q
z)l0H;S0B@iGazz58f=o%cfVnE;w?5P=Mfe;2}a2M!Qmq6!uZ$7I4QRFX=~8z4|Tf+
z$ODL}Z4IoNCg86@Jkt!)ongX3!NJBL1FParg763?sp_>8u$fISFTYac{_C6a{@1b`
z0Gm&>{vi_$%~I+|dg?pGQpLOy?t)*xn2-yY%KjbTVtFN^$jEEe#|`rK?DK7vT5YEf
zoNBbQpQo|Rw2D}}?)XnG#hca^GHjzB)^QUT!{#Tp^RoMBl)$kWe(TYP$SnBa02xoi
zE{DV65O7>u$EAeOONjTePQvM_-}wd)#7{RLfW5aHw0UG&Jp|@+(DHshV>`y5=J=f(
zXM>w}LZx7R=I$Bj2X#fBPtbVX*LLrfu*AkA!{dyZQ~OCGIhXrH<g#>mG(Y<8zTZ{~
zM33dOi3u?7Th9}DHnn^I8g||N9l8hqKt-Lp9VL8yRX0~xu9pLB<DLgPppi&De0T{a
zgEMPo6X$9<4o)irCQyW{&-O>E_Xf1USK|jn+gRu*lFinhyX;uSiz+lnV1jO(mxyE_
zHU^#Pvoq1xzrCZGo1DNLfuG6)O$C1ZBb%KiwswiazeoE;%lu5|kVnEV^!4KJ&)yC6
z<0)5uIG}xVg}9<7Yp}~DsJb6VX;r@VC0eK4E_sufpf?%62fh|_tSr%6x5shIiIbn#
zC-qLFt0?^%GHx!!7Ay(kmnP5tE~&HGQoFSES*8Dn=+hFe8@1~dO1NOi&!#@&bK+n#
zQXUrnvwE2O542k;BdNFSC1<66#`&Z4R{lBlj>j7mGY;#4;2$@v_x*Q!BwX=h^3u0<
zlKMJ>L>iVoy+7;^1{g%*(%she8R&n%sh+NXD#}AdK|)+HY(rm?ex5#OnYW2eyoUV`
zbE@>ZgVuS?^R>OC40cl<(iQcN4vr@;IY=}-wyIy+FWc|YsciX@m>FBO$4E_>T$1hL
z%-5T5c|%j}j(p$d^-&#~4O4b7q-&l{Df3lUzNz_mLOecirR9IKLTb<k7~dC8B|?!J
za^QPb%3VEl*qdyaC6)KOa_3FSCK>{F)MD$_7#(I53K#xNL^`@x3X<q>$Ex<fSIT>S
zFM(#Kb2o;;&?v~ic)DP>pXM9)2Saw8A%yb%_rcdAJ4_9BTpjcp@L9T6XmmQ?KKh44
zRnZxG|HgtW(6=6a6q;ORs6jtDcYo*SjpFaB?<_uhQ9WWaY`xs5-(97+nbydekat1o
z_0-b}EHorKb-*TrY9$Xej-7VCPC2Dc9=6mCl4se}ifONN+m`R-=rnQ-+3(UIj}2v^
zTle^+ozVbG6oEN8-z^vm0>mm~<6C}TlxBp?<Y~X$rsE)ZHG&xW|NGSTy#*opUSzBB
zMqaZtK6=~^K?s#vTbH<4S)x33-c+2o7HcRRd!&8d`fwToudndE3`x*XkdY~8(Nv@}
zGPIfrzY)7!^J3)#W6a`l4knk@E>_{|S<-oyV9Rs5-2a<PEpfr?GJFb4nAvpc>1)|i
zb2YxiidIbh-^a0B{A)6F9tm(f`Q%*F{7qpO@ESS3@-;r5i?r}2hJABLh1mIBC3G`?
z&_4YY(TULjm0CEzrsB3W`zS;#ntyqplb_S~c06grPsO)IBeX<w8%sZmN`kg5*9@b>
zn;c4$^lhfGyv8G&dfX%UBGhNmqN40S>TBWLFuZ92=ONCp!dp+>>P183|HFn-Q{3?4
zG&y|^>P}SZIJeMuO2=L?+67(OiIjz3XS|@|Gi6Z`AX36lq5Zw51$1f=KT1|d2uI7y
zhrsCiKMaWX`KzC!x7Ex4)(IyVP*{o^(mkrS^@oKNWz~(%4{RkQRQ>0LRDt9lqtDqb
zndiH_u29)DTb)>Wuo6q!uz79raO2gzQ7cBftna?&Pt&=iPm!DFz2x$^TEh|i{NG=v
zmvs9eBz&)VV1BOYngc_*!!;T$Q(cb-T{r!+B#73}HH6cOQZYh0u70trxDT$|mhG`e
zkge_UXWscI&+)1h)43eCbS+|7B}b^F-9XDq$`$UC+Kz`<ppkIVP`g*4^`9joN>6z6
z#K@peu-v1ix_cPoyE9+UEefUiBtrM~-*>OA3pQ6<u?)K&vI%tGhUyxxf|p^n_vOzm
zjVm}fd*o#8_@N0EQjKA%JAoZ$Nsfoo>^{yigBzC2K5*db6b!{QLiX=K!z2aoJ(x&f
zFxAwx)_s$c9ut<wXfUrnlybheG1KL&rnWN`3j6a&HpQDeiY(oF2K&+f)XGLv4y^(5
zEr*3~%hE`TY{n2R(!wBa_tPUfZ2&EctK~$CuBH|a+a&hxozRii!*FqH*fhBS4137I
zI<VZq35f)lIvyUn!g$pcPE{@ea)iEEMQ^u&dyFoIx{N{M#SN9bjN)*`@zP}hmN&#b
zv6%@KnGZhEKM*k5!M$cF(e9gN9&JT*l~ZygUfMiYtBHXh0X`nZj`YgtEu?OCFsTtq
zT{#egqhQ}v8eyIWgVjE;GlDH8r!+Gog9Mz4(B2Ru0pjyllsIz?#ZFXP#NYK1BDJ9t
zs@{_=ckZq39;3H#<W{^nqcxjE<Ov<F!<mKKVaLu(Y!io4V2r^Fc5}_b?^#xPT}Bjf
zJ5!$g-_9?zfoylg;|c@uqfmb-b?P>5pusreR&Q^w#%*^1fnaQqhoRZ}t@3IGy%d~3
z{l*R?<>%Cb-c8lr4Y;?9-w5YP_Qnqjdl+u3yf}9X5}fLhi{5L-f3@k@rIeJb5p{o@
z$cr40SnK_<D*=w8p0UoM;~SzLh;>uPvw`a$pr0(F#e`eevR7M^(HyO9>`A`_r9{mP
zE42H-!xd_q<19^|0Iku~zOwf5%g2-~IHY0EFMVlzVDN{NHs$qA2BB3=P3)`V8uvB*
z8rCg}wuX3h{@G9wf0BBb{y4yK4lr|O56DVM86W&|i?5Y*p8ewtJ%zUK##vrqN)3MF
zgR!o#)E(9jIgNUcpBMp~l^?T>VwdgF8t@1D<(b1(g7<zlrQB%2{H%Y&wMwX<<|mu{
zNXBinV%|zGQ(m-D@C1PE0c_r4qk_R;wB@=CN<H8z7oq#-8Jr(zD_#GJ`gXQ#O#Y^y
zcT!kaO0TI<$yahMoiMa9#8V!iHyIcpjedPofsi>qnzM<w<i5Fj>6K86t7H|X6WM{L
zi_<ltnl}Qt$0r&}Z#_n>1?Nr-C!iMr-b5zDa99DxGiijY+mk!DF+;E=&j!09ALpIm
zk+{^)Z*<9hV+P$KJ^szxMzI=c*L<RllJ8AEtv`!wTW@7p3jUnGxu9NoCosJ#;u8C$
zLZ)!Dxf(B-UYL6w7Q11dbCNt-ibX7aLXj04Luo|LHAygcBX&0M=s56Xcs%gFcgYV;
zcHjqyz8m-1`r63YFq~dVek7cXI1{?qXVTUGn_-0Dmf1UlXtoZ{lkFDLi`r#^Qw_)G
zfyOG4#92bS3rx(;o&nfZ*x#^z5iT7Q91KWp#lTPlY{{hw@1+?pxZ_e>#mppdUp3#G
z&6@lltfymOBnp53g;Ee+HuX>xQSx_r*L(rBJX0={M(%je<2yZ`Wl8-f3aQ*W3@*`7
z<sW#5)aI!ViF2MZeCX1upYS}OMYaxxcVMQ)H8ousd8#P7B~|){v|a5q=)vwqXIa1u
z^CwxNWI3Ob<Oi#2O0~X6`?h9l?p{9ws)BB=(c{g;X@0hRDA@6CsF7_ruFVGLVz%t9
z_cQ*sAoAsyG?kJc<-$VqmS<9QsF(YnPS#a%_fk`0vO-dc3lc4ve89(WdVaFO21io*
z_}wWm8SLe9$CXZ)zV_1+vhhyPDX3#qEyTzC=m&|@cVKeXUeU&YC+@3G;q?-^YqLYc
z9l?6;vEQge3ni8qY`RCgH`7lR$uxo&mdR3m7HVqz+uoWT=$&0yT-_<NV`M1(n4?vH
zan$4O3TFodotDXfqNoN%NEEme5-R0VIws+8=J{ImyiL86Fp5`H*_ip!pi9<vsmHSB
zi5VIZcF9-CRjns(D_gerJ;n}q3~$qOPAJyEKxh0^CqdMk$^SM}MBSQb_+?3uu=qoz
zno0{lqLPFh{J><Ln39r`@LqPdf$TZ4rYEka^MlB;hC37-%s;+g{Aj(Zzn=A>_>Pv%
z)XaQm5W(ZEj!z*+*`6vejG6km=U97j#zo+lHyyGxBItT-NT~9V@uI?mJtUFEhS6vF
zf@Pmw3wIKxT+P7R?QdTT$4NFt@h#%ixYR38#M|IxX8stU*MF`PyZP>D>E=c3^Ro$C
zXU7zkeuhr(5^)Jf_kgwttVbPOu?0thVIGBkF<wJWxpf?G81{{k!c&uU&p=P$F{Ufv
zRN_xRRq5;D@B@$Sq@>r$8ZuZ;Fu&6FGSB>BO&hyVg`||o*Hb<kEgL$nLer#*JpCV3
ztV+K{3mifD6Zbu+hr=+oaguZ#q;0_8C`yErOsXQ;c5uZZ!*!pUd{tL3`_UwRYF|G(
z_T@>)mw0)dRo&8gG`6Q-n%0OcdF&Q{eRdaftW9xy$0(a9fk$2I%T7AEtjF${D?VTQ
zwnUFFjHf#T;}Q9xegD0AE0OjPUcJDSp|`=8-^O2@#1+Nla@WW*mb|~%J8T&i<0C>4
zi->;`mSx^9R>aBlU#1-_^D(pkBKvZ;UE6}n1JRI9q<By6T*Zm2JKK=TcbmI%EUFp(
z>~-Z`W}+n8)=2ZCIUCms;ex$HSzG7RESxA3$*Qy!7yc9E(DLLoZi%i>67}RT<$P-g
zC1t(~TCg`wt=o`jkG|%zSe^9J{c(@+&r}_HHj*8;eYxWhMN#y)o%3>RMWS*$92X~w
zrXQq5OHpV?_h#{Ca9-6*#-jH+yrGtByf&Q=Z1Eb0_F>*z65`IjwkS8uq-27;Y=0`9
z`u4HY)hQv)MwY7vd;YdtyZ^aW?`NtYUH90GDc^@ZT(Ol~6a*5QT^HBZ=SS0D3aQ^9
z9x0EGZumi)iE=Gf;HH+n86j}Gf@uqOeeghUfq6gQb;}TO?{t(F7xRHLpc|t52@F@=
z=HpB^_iM`tS6#N7NENSKyXFVhQ?Mk6UYzcL0sQy(U;_%|*b77tQ0d3;sRD-+7w4ub
zFTkw!JWrPvJn6_MihxnoK~y!I<|!+Urk6#MOvX~xq%tPQ8CsS<VA^5M#&7Q4Y(_^{
z=v!L;7|Mh_MEKQ9b4rhsm+0^&&1H2o40oUGyn1|IB0hDQT)7YCs_6!ClE8x^Sdce?
zvmd7*6v7GCM6fo(`7gv<2x1{H{AX~s5L{ZaaGq`mjujG6@wIKGP{Ri~z_BbiIZw}P
z+6~UnBvAD<KQ8rWkt6jJ9D@2V6Yu;a5QcmRLZKMAfWbPAoJNPkc*wzN&gxBcnE7{Y
zxk}py%c8lK6Yc)RwraiCtNFo;p!A8K4ORU?7fcP?%FEv6yx2lN-F-$|yYVb&Q{U!U
zZpK!fw7cu<jGlV+OjOccwxi#LI*(9%1f1{Q%3Qoh4bxyoz<CvL+Y8yxUQ)}|z5yT9
z0#$(I%9Rh1+~fWKm-zxYvI@Q+<dY+ikN21p2kpxgTzl~0EPaK!;50xEtb?o2c*(Or
z@cH(;nNJW=t4SD?=JQT4WC}~o+NUWW8(AFRz5Eu2jyt`Do~L#VqZ9cs4;r`DeSQ10
zmk?=Ho2T=<;q7qx+*yDoGlmww8BghnIDTEf@=r?OyhhF!fI|fgiPE5yg3Ivd-s}dr
zcID&w0%44=Ie!BlLmYVwaJfgZK79k`*PS2uoVMU-@9=_#Atf!XL3>A7IDTkoXrxvR
zWKB4otr`^2bu|aqs`Y-}no=E6`AOr^&HP>V9c7to2mZWU7svUbgv@{Y@l5upLtJyr
zDMu4%ks(t~?Q!Cu_xrw?IYvG8{4=t_-#lNhOh1^h_l0r8!=!K<|NDCz6ZG(T26)%l
z+TcV^oQO-V$q1Z16@>K$gk_2xC4wXS;8@TaV+K=f=kBGde-9a3i?o?Qy*fNT){Or3
z>(`00P`LY)7Uq|6-$9oL9X;2%XmWMl?WIlyQE^p>(P&~^6!uQ^^#_WFMVa)&Lw<in
zjDmsYy&2-HBiAFZTy5nG$@Z%GrbN^vKzc3{hhxTYoJUEIP&k(<eA<mGX9`_5bmfk~
zvRUA?q6$7xztq&5aQvWfSMg_C+jVfQ1d_6BZ#EM3!N*{LF}wr91cG`(tW^+dIap@c
zI{-`->ez(SEKH-_HJtqDG*8@QLWgyEsE&eJ94&RZA)0>jxZm4p=!%|;xV75Hqr8EI
z&m>q6pL8I#(M;I>E`C{-cgn07uD32S&=-uI47}|N!qLN|h#c95xioMXfjicrl?QgW
z_*4Qy)yD_*Gn!ovY;|xz-vp|Nl#C3Vuz3?1NeZU5k|<6%%7cPq1L@#thvOZQQBlTD
zr(phrBO!3Ysc!D1>R(+h>@Hcm33H?yVZ*a0lRX$9&jftJ%yem}R-0OI`TRod>o9@G
z{X&nSpVFR3OU=RvQt>8VpK3a~vzt)uE6jw?br|^m9nOfUH&wg44BOp{2E9B-l&{CA
zB~8e~@reH#WHzi^z2H=f{(35oQl73D*!}{-!ZN{>j~q9o_c3hlbdZ#mktqawf7Z-@
z&O*DtzsIPE&x+9{D;asgTXt?mfzjSN851^Hruca}Qfa}2^%+=;dE?|oRfXQk%;9Zy
zac%``()Lt7Fm*dE(sQd-;MVm{WAmcpI4DzKaIw98gcsxzzi_@X!8Y2`3%;A-O03b6
zmuei^<sZz?z(b83-E=1O)Iv_p!wCz-YzjWYd@vvjJ1$DX2{N{JEwB%R!6y?yG%|&N
z;NAHx$BDR&)itr)|NkDYh7WrQn#El|pAQesYra<%c;y-{<)A?;A85<LA$~dz*TvXh
z`a9UAxjffU-L-0)`S`Y-OaJ~VF;$p)SK6NJ!=7JO1_dE7u?RPiTqD8y`dq4~;@VLr
z;6PGl`SLlRK=@1wF1zWbRhr{cQBl!YI8F+-M`Z62?=9H)!Q*IDA+`c$<kO=a+)J0>
zhy*rrco<|_UZ>^f9d`e}k8Z<<2~5P4OK+3OvV8r8SIO~uJ?r{3rLC=>(Te^n)5Gf9
zr{|Q~LNV!$SN9GkVS>PQ<oh>@V0(IWZsl}hHBoeH&c;$GzQibCHY#hdFRpNk71guU
zPR~&0sJMg5NK4bFzy|v@@@Xu~16HqI3ByRmwB83TE~$GfrC0R+wq(VJOVq7DG74;u
zg545}aGtMSDscxtx9L62SJ;ujfMyFl)3ooFF_va&M4fm2xV4xrUTl9spi}K{GeE;o
z-|?{oBYtw)5$qdX7-lh!XSJ>3K3-m4(cu*WM8)L|0IHA=6c7<4ZkHZ!m=}LTbl^+d
z*A*$3JdQ<O$IEF#cb5f7P%KXDs9$6%2I7fvle*Lxvug4;V@7_&F@Z^hbctLiG_)jW
z>T4!<n`eZ_oUlX-9ol3K%k6QYBhmt+gD6z4W(i&+7jkeO`d}Jzgw~3KgM;jj>i?&_
z^N#1bfBQa4vJ%cSD-@-HtjdTq6h%}@A*+l^W|;{kD;h?kjHZTck!+Hcm8=l5v%bEH
z?ECe0c3!{VbzkRo-}mGG_d5USaaQ_%zVFX_9mnxHp0B_{?`_?N>x}Fjy}nmJh!F~=
z1h@zkTnXsRmmcTfw$@xK94)0Kf02*YFoDHJ-`nE6x767xO~;snCN-@FvuOj|qZzMM
zeo8K!dL7ynaA5GZ?SP&Fs$0mvB*ho8m!+os-1rtV7&i*@j1bFLjJiV~BAij4j90$D
z;oh=w&tP7u!*N+I9N%}48%^5$a^bM==}E2177_+sLAM)idp~W%cIEy26<5xT<~#Ze
z7{IFDHFwYxO98D+-_Qd{p=0rScX1uCABj|O4^Wh33cFU~vpc43rPAlw*PWt$Sgaj&
z<&sb0rXt>FboLuR);6`%$*uK!ZW%67Ubmh9`Iuil(Nyv9ii^p2<S{#5#E0IP&Z;}g
zsT|OHB%LE4`?7AdZ`PTT6{IT(WfaXld+1ORDGQ?6w~ozj+`IHd$D4S{$8{TZ1OqQM
z$#dpfGPQ5_=9gJBH!beOMzQaC@;pv*yhm;G^<Q`Fx82O>8+uyV|7J-3nT2IV&W<~m
zt~PrpO$?__)Z029YgZ21QP#i{4AC!|O=*a%lZXSo*micrCFY(+Z<{>FL%;6bD{dXm
zrN5-RTw;#tcnrNNms~QVxuchsa7W|qPHMCMh~blyw7ofcx1IEL@+<27<5jEcz6G=s
zh1R`9GpiMQf*xGSc2oADt^L#M#Sx7;^?f5E`iu{8pSmYu1i}}Ztk5J#|B%d;u-)t~
z`Q9qK1`|7f8q}O!<GifUJ0$6w(yzC4A4ln*Pnv(JEUUe`<>$eqY^^2tkF$s<6?Ht=
z=Ii_;#OUOk(KOc0LR0nM_@AH5mSGQJoK`$q)zInJ&D?yD2HPBZ2Cr~Sn=U8Kd5}wc
zP9<CJ3ow5)9uL~uf0R_uF2CiOCYt1;=w`s@?#wYE;gu)Q=DgQ0amSOG!~&<N^GDxT
zM|Jfj)bz~UB!@!XrW01$TxGJs5=MRT%{yq$8i@wl7ku4*OKqJ;sSe#Q(&2>e2lRIk
zRLZ^^;i`0~e1${G-=pR!6kIKrxu<>w<&(t9)aB(FOGB2tPrP2HRdnKwaZ$z{*V^+L
zFPL_VUCyCx6WnqYLLKiGt=dc7yzVt?*fYJf+`m?5Ry1zn>n@&&-~2^kb&#8|eqDak
z4pw2Vvd0&FD-X1X`QMp7F}YIK=*3qa0ay0fJ@Ge26@xx5RDLZ;?<%7?#`?3%YlEov
zqogXCsg^3vvb5>%PM>60+=p}?Oq<co&+UeE%>cpA1E^=S02lk~3bmYOzIg4lNAEdP
z0lpRV2Mg;>PtM4@>CneITzfLuk(j3{`sbKggXmA^QU4nVc-WnW6vgvqZ$1jxs;2U>
z$|!e#;~3w8YDwp`JvBM&5vqtGF2#xDj0Lvo*o&2DKtPAFzPON(&Z(S76Y7-j=KU1T
z(6dm=m`|SK=3;H%?lWAsW|$XuHHAj;s_HAeROg<&W&X3&#x+4Xyz5Sn?mU_1TgP>j
zQM9ALL;pmIgPhQmCRP{vPeSgBo{&EOc_X+DQ{ZShkLFC0Bqrwu&5tj+_jT{?>Y(Yl
zzq`+cLe+aQp(yvRuq<8@yN3P1Ho<~t%8U~ZU1aA^A3x-!^1<e5-&65*=kE9!=v}60
zL9DhSzhwB;;nI@I5A6Qk%9wTNg{mfj4+N~FCm;N_Uev#OvBHeeD=+`&6F<e$Yn%7P
zNmOR|KFDS@EU=Yg*O_ZXEZG`;=WR%APo<ZN;RQs-YNjQd9`8@64N)0d6lPkK>(E5U
zaqh4DMn96`>(_b^-wqe|qba5bXmIP1yWF5SV2RowsE9@>f>C}=Y}GVpYuH>zJ)h@#
z71pm&s-K<hto>=cM_rLkqA%XOCw%g}(yQy!c5CZr*9A?SX@D59I4jS$+mckPsJ9=;
zUmW0FPp9aTs{1y6FGpDhau#SD4F*q$23<5n&|qxM^J9Fx!qHafv~T38HQ&zl=i(6c
zVu~;5Ue1`8A38xXW8EweRrosLu1kg)eQOkdv+Xaj+gBz;jp7wbfBp!}%JuHn+Pi8<
zWd64LA5=#(*V}4tt&u44sO8>`Uz&vA=t4_6E6U!>DD@|dI(vIRpv^!Ng>U<HyV#Sp
zML4h5`#5qwY~22$u|m<|WAommr^>ftbe>jt+vwK5kz*}iW)FGz?XZz2JzROo!%Z&w
zsuJ=;Gwqz=DV^LRoNm(^$LX?9Eq-3ulW`gW<koTJ(FQIK;gJ3JB$u#Wc8)T$#w`(j
z7xZO$t5!=U%E%jsUXC<kPJh;@$5v%<pr~M}!QkD8)lbaEZ0%C4J_cKHo?#oWYBiww
zapBYr_gZ=9!4u;&U)CGstyT4qS%pIpZGk=AYxk+l_bw&?cn#LN)4%4U9}|@vHrTaf
zRZ{Zd^|1=+9dp;IZj<_S>P{P=HNJc9<o23|pb8~Dr+${v>UP$Alw?2cc=h_GFo%m|
zD|m%q<V1FNn^p{hEpmrQHw<HtU_$exDNg?&eS2F^>D&3^sU3HJ9)7|sm)Uj6bwhR3
z^qr{OE8N}kzM>YK1B%v5a$>D}ssmo8-_o0Z_67;NXM)>9!c1yjoj38xxS8K9RT6Eq
z=5*u8fQBBj;V)l$EJ)9xxGW~@NsAjVLC8%!;bhNzu&1+zsy)6{`iNJ-^W|G!TJ(qQ
zyy-BKC{^gPl_4Yk*+A*G*|f2ZuG41oNdpw!cY*C{)VqVn#D<D|we}eUg~K0Kx}+<b
zBj015u3q98d$Rm(y2A?&P+FyTJv=KO8912cFzfA|U?U}RWu>Ua?I%UDc^79}&Gc18
zoop#T_PsmQq;g(w+0Al#>7HVRw^?#u6vToUZn&xjlzJ7{@@#%1B~c<<@a_nAR^Q<V
zIiDSyE0RN$r3XSvmRrx#Rd0V07-GGtcatUC{DH)nZ)&;rQLi4k2fC*F1S<#4bVR$4
zM`*-q92z@+pDRf5`PoBfcdXK03@rz&=dUZw?)LEYPt%>-$n5KMy0I!g{npWWYQ?;=
zA5UJ8@|LGZh4Mp^qbxU1ab{|bAhRpU0zHYX!?x<8OF#%fS92BY4A0{W=uvqvE>3r3
z^jp(IL7tZ9b|ydjei;TnKmOfKI#$BCI_2H<oef-x6p`L3hV_l{O20O=ZLt1^xcW#B
zvs8+~aksW@wW+0Z_F9a_$l=BtDgzo5QI1}$fv-ZSGaH>!w0*(jWplIY>5$%svGp;B
zJ5P)CXuJEyxc5D_(aq+aXV?tQ<VgChhAqIRZK#+W?|J2A%3ZTAd!>=G{t~VYZTGn{
zV@5X7k|ga#g%#{Ut!Jb=wKv^oy8GC_<y}xwz|P)UOHs<fuWaM<d#6*J?A%`PeI8o2
zb8Y&qiK}<Rq6_kMcZBCo$<g3}$IME;ADmaQzlshUKZ7{E_*Ffd=S%yTW$z?UF+@9^
zI#?U$Q79p3GCQ#;_J-D;sC$pp9Q1vscgefVGcCwoW{8`ZyXwU_KWS<PebI3b`$hS#
z%1|`&&~q_?-Nrcwv$svkD{_Q=sy`>imdxg;AtUj~0f}R0X4}t+RYNCpMz=0Rq}*jb
zQD^I5-%)X^-sR~Yls!0-MW@9@gsAsEd1v#qiwD2t3!s)$eHk;;e79(-I~UsVYnC(=
zBs+BQF|j%Levis;Yj0TFC+cG&IWk!^Ytv~h&GO=8lkeJi(IZM4%Bn%Fr2VN|1pOBZ
z4J)2NTi}+Qvhj+?rm~tr{{ErtYg-aT$24{>t7yMkF9<>8;Vg!wp~((SE?;xsGyjNK
zRgw_0$#W_*ci~D3M}p@4-hJ;^eXi3{>0YI15XDV7DK~BuujL#e9r*TZ*mo}Fo+W)J
z<ogU(B^dcYjB;;VXGyxPEq(t>wFtb>&#bC0-zwUh9Hi;FR2h(>iSD!#4xROHx<j}W
zBM*<V8@c!EJoxi+Ft?;7!<j9g%|3doMN@aYf9SdGm!J_X!@UQPKB6T4UZ&%l$zY9@
z^?1-l7X6fatc<-D#j+duO8wH=|Df8X+L;OkOX$<YIDca-EG)FWcu{!Wy6d?9MH7D1
zU0v)V;L#Sev^+q^9l@IbqY_{K+A!xn8kf3|3q(PMN7>zN<oF&H>fP8LuV2rM&fswc
z1Z6GEqa^md@iK6E)8VvQw1uarn0da5nb{Rt&5pi;J8p#yCN1yl2M5S|_;Smz!smLb
zoI*Gmr>-;SH%)Pt3IF#UP9#+a^g}Hm14z}K#8Uz_x<O0nXXx>We@x-M*>_iEouI9g
zUAMQdddkpGpG(dg|G>zuinQ(P9Il<+@Jsbp1Ml_D6D$dlUhO-tYKayFCfHth62G_l
zPbimUTn{N8QcdV=G2)bDaek%8?mkj?M}Sqmv*Y0=Llr7hh)MT?rYQQOo<Ktb>eaWQ
zp^vy;B8RkubWh2JUu>Nk@2h)tTvR;*jDS?z&OHzgo|D%^9u0VBMMCcTG=q4wV{lL%
zxIHwfPd>923U-Rp%q(w=>xx);x#`nf;(2z7{VI`<FBRUl{nePq%=PjdlB|0~ZQYUt
z>_EUn-E=I^`?8$tgfxwJwgJ!dF|+$&)m?R2A4h0gV)KRfKKyE#ervzIe?t3I8a>4v
zz$P<XdC+{!WnnQcQ4df>2Lg0-7;7OE2ApXYIVX~{D+kMr<Ig|M9A1O*0vLzQj3K_(
z)2B~QiVL02W14y^g&d67$WO`Y&n(5oWmn&Fa{22GRfgPSNJ*Q&^hrp;^9gfg(^8qN
zg6Hg%LAAGT4Go<ZEq5&k+$IOt^17$pN8RFMZR$Nns$EZByy)1)b{`jI61)C4?XMi`
z4<-?M5b%k(GZJPjQqO1%t~@FNQp&?MgGQPFY2x{8kuBBFC9I6UWp<O#?S+C9uQSX@
zzP4JLm(v^`hAx(FW0LgB{xR;rD|n&gy#n)rggQ1w<^mGtT=_f9`JyoEF<cs<9%#r}
zT~u^}+McI3cWO0%fAiZvL}#{t%Ty?)*j-N2liw$>6>U_jC5>rBLI!SCe9iG#cszub
zTj)m3fcJ*5?$b-{4c4udNI5<QcjXckq-ZovF|XuBHx<EYHfMGz{pZ9UyNfLrYgfRE
zdO!ZAP}<wxU45M&lT%MPTNDc((>1ucWxlJ);IbUgZuUEl^xJRyCR!G~Z%FdsF*R*^
z$CLr?Tk@Di|8{p_QZVohn56a<TSB30(XV}1cR@#cdY^CCz^k(LDpW7Ui?PT^-wO{9
z-w}qU_NP4y=;H-O_Hg<IUBbqOTyU@<UKnu3e}flpTKGqJA-^)PrvS<TqG>ZV52PUS
z^j|Np-}ipYQrE0cPfRx9FfgmVrGjct!Swai*9zf<ue|ozT@+Be_t^iE-6@R@{}?HL
zJ$hfA-36Zz*u1(#b3#J@#1hXO|4pcL2mX0EM9#6n&FQ`AHHeWEwM9dbCn#=~s!m()
zr?#pmVyPr})#wzy{6)4aG4H-M+JpgQOEIIAumVM?V<s#t3{XJO@dz|-gWBPuCFSQg
z8xrHo%x~#io9xKV5WIyl_oe9dm&^CH%TDmzUHN|F>5U^bkzaG;T!y|#pQ>JceV<K!
z`PyF9N~Iq{zr1_Se{8IiIf?sU-q3;<E2BlTqhfPPWo7f#bX*1B7&0DQ)_Zg5ag~un
zxqS55{|Bug=y_(CxLA2o&J<&${_@fI?>rcvK}s8!Cx!|@*uo`$^YK?IDBTZ$bA#+#
z_nSt;GbjllV`i~w)lDIeAdd=3mWjxB`RJ>e`k5~nsgcX%x#7gwu3yXsQDH}0LznMb
zwjxqu)lJK}Xy>p58*A4J6C%<?=K=KGB?Wa{x;S<>ov0IQiCV3pcyz5Fw5Nxko6^oI
zp0Zb5_TbY-V^SB`sX^m3)U+FI&rRTSpx0Cg2M9vxv56KN?Wbz&>Y3nKO1u5CofvJu
z4ZL|!P!J2>_CN~7Ry_iV%yB4YQh{T;u}ZugIl&QEzG?GmI)61ser2bKyO*_yru?$z
zGuwIl%{TeK^?!SN-IsqMI`(|x-c4c7N@eq&8w&%LcJy@yK1da&S3I>*pyTR5Vt3M=
z4AGIQTc-{l>ihI&E0gm(N?-9YDA)>PxU>(b%Ql6C7bb9Sij?#4=Il$b6>obtYT|j1
z`A{MAk>n(aO5r`rDXyMbxsZ3MzjN;^S}G|~%cZ7bA8f+C?%C6n(>5GgTCsPc-v*Q_
z$JU8mVNHk~q>0=<8y-HfJf!Y{eOTmF4(CwU{-3Aaudkv!Jm<V}+l{HNvl1cOMgRH-
zAMNx+gIpEpPeX$rpzoS{6D#dA#<D?kby1p&BK@Ss)0%o^=OPz{oKw9k2Wvx<&(*#+
z5M>IV88yfaiynAebxY*NugtFD-oTJ2{x`g@;0|*S3iIpJS=vJRb)T+n6q?wLR&6x_
zbLohUdRtj;<SwaX$REi}8WD}uvVK<ZZ2eYa#?Z4g4u%CA$2T6}N<bT5VM`?s17~EG
zThz7aEv_sN{7w?@hF~MP%w6y64rhw5ZlM{>^-&sM+sUQ&i$27I@tWnN=lSYuA(`!l
z4=0zjdT6PPM2OgMu$S3rh%Ap|9TwS@XmvP|>+Muw=F*d&+Gj(9*4q>`FV$DwEaZYJ
zD|^uFM~OcKTm+|wuJ#J<Es(x*pKdVsT6J8(XNyjX&BHNwA$v~JJkCbPrS+no)z#Y5
z!eY<MSWnu^T=~CxDV0SlWqCdwwc>y2*G)?rwFTBe2_V809b=}s%+is5gOge-?L|W$
zt<8n69@(xP7%AZhVhAIj%W&LS{_Ggzk7m}z=;ze*k_NZsF*?^sebNfifXank7`#%i
zswXs`J=zqFpAO4yoL>3V$jd6E^T9I8Tvu=Hd!C5Cm45^=gv4G&KRMT}s>3gDy2$4;
zHr%|{cCn*$w6|D-MZlHum9mY%aWNq_F|--@H9dK}?a}bb{+uNOBg`Z7w(}dsW|R?v
z1$@0OGe$mkWbx}xe0(ms^$LSwJFB>|SHA6ANA~S*ON>5ymJN5-oIfNiO!Xx1MX2L<
zorf}eVIwCican#c#s&H(-wVV1ZRc*p3;!9k`XPal&6`W_eknp3+Uo2e^ZEOVs%TqR
z*^e`~U3eq@+`FbHl>EgD#9BcpW7T2a`?n>bMC<n`kY(8tbJa*S{CQABGr#7AWQS0&
zmkIK$G%9muciTd~rT(KfmE{4~1GhFwvF2K_oOxo>ctK4o)#0g7@IEy9s;H!VsD;W(
zT4F;+A?Y0vSrqf#*fY%a$aTZ`i_=IAqj^?HXu+`aJms@2Wm@wrMa21!>!Dpqv-}to
z=IMOF87uy0eyu))29W9WwV<YZ0X5CEX{KwN3w~B4ofC6A&g_1Hnc>7)UY;PuMf!kg
zOe){8%PU-GmqqpM%`BniTzzVV@=kiAdY?mG9bXWAZWbaO>Yzwd>D~UzYD}22)9KIW
zv26KD>DzgdqTqIv)?I+5Y{Lc2DT75?!KCWdU`mrO&Yt^Mmd_V=mdpPd=KPf=tuabh
zvi*y~K`;QwD33_U3ceVZp0!|3i(x4iTqex#Sa~h^2*pafNovWb#1@64>{;k6gu>m|
zOZd91Z#X^WQ{v&D^0t?*ay~FNm;JSs&Yhp}UiBA+qd^SO<O`QwS<7BCE$V!QYpW~s
zzb+z*i}}_jg@b=hW%gwL#62}H@?3TnG(1@=NB1eAuy>5&z#rbkiyUbn3%)RQ*Wz?Z
z@9Sndz9U~fZ`Zxz!@29jS9jEG4xdeP(JWwX-}8On;$K{x2QI#4ON+l3$|x6F+O3@0
z{B}A&!Yiqt6~)-F95gABCv-bRFc95`=8M<-m2aFWRgBj-Fa3IsZf6`_okBs-NhLFt
zZh^(2&aNaa4a*a)eO4&%F57QxifxE;MTWa>dHUSabHMGrRLfl)8Y%+=!^TDyg-Y*x
zXD~->?Y*?^Bxm;hO5=FVvw~|O2~*4Euc7g{wmF~ED1R{PQP~;_lTW~br0*V-1N*{T
zI60i~PJ$HG7oX24n*LD%U(IC(#h?6tB&-;Cne<bY+kovuhG$N|8sWBvpc~zrrW9z=
z67mdGy1xLtuhXsCbE62mh+rD_?&aC(<{Uc*_X|zXu+XVQutbECdbAr|?N5Fu)HvRW
z``*yHR>r<!fk}HuKG!zmwzFzE#)E46sMp=1XmWu;{A0^0xw>gI?+aY{afBFiAV!&j
z;|RB+vn0COlS2s#_@8=<K8vH9&aJ}qS`B&*#%e72J`d7c=h|+e4f`RhC7f!yCh`y&
zneAo(HpsiXqdGv0Cw^maiQbKH{YjF0VbWtk_4H{WlznJexFtQI>rX<_nI_t$mj{gi
z@6kjfR`TyChZ}4E9iUj&%mn^I)mul#^h4e#d{@tT#BYs=QFlAPW1Zk{aw2bRw*a~f
z&M_N<TL6r9AI34is7SbO0v$mB9~mE*rvc5O8EOn<JW@lUA4vHk@wXVj=0C&$e%*Fk
zq7TRMWv2*4M=?ITPq%Eyz*uuWf7XM2NAM`et|Cde3_L<*`SWYt@h~%#r2(Z#(R1o@
zIDPsXe?@DPyC^s|#Xv2m08nQBd^6tFgVn1aYW$(7%#35?zQMxRSp7nDp=r>`8Ryez
zh}7}l10#k?fcu?=^x$lV4@#|AEq8}x>+AtmJ9T?E*6uEHZ1`vHOS0Y8FIn7xZ1QFp
z=h*K3cgQzkMIk-{?fA_X9Z&|NuT1E|*kG5ftt1F|IxYW+djk}WW$fgic)_nVLR|pI
zN7%r^!m<vW%Y+^Rl%1bxU(hp*0f7-=7vZR$Z%km_1?vU!HcNnMumgA97!~+X(Gx2`
zmr{=ap{NE#sETC5zyUFDMZ-bDAsR(*lCh4rx3_N21eHqn5M^(I7xhHhjPT3}bq20N
z)sXK_4W(8S=)c$uq&)#ZNJ!gvtNm_MX-+#AQh!VeiB}=E$BK0fk{hO`rwPRmW&amI
z!$XGB6Xo=^6XTc``Vz!zLg@yr0iWg#;5qDBR^!TQT2xBFnj?8`JJ^g3AqT_%Pz4S0
z1Z!4d<HKIBL{5E>V*aOjNJU_?h>eXU3>c_zVHp$l6QsOYAUDt;*)cG10Bbp7>$#)<
zv>~1TL53_nD3Noqo&rXtg<c*kbnu&`f(VlBbEN8jlb%lA9Y9_Jij6Y}<<h{xL@Oge
zm{qN>ufeoHEkOo8Urh>rmy;nEBNb0z-ChE<iujf6lo{gf*)A8MGv}7IUQJW2IL?AQ
zf6757_?PU(6Y?mzUJ5&{cHlq(=tWpSD14+G7sPul<HuFHZdE=cAcWF}Bsk2DRKq5~
ziissv#>U_Jpu7Hy5Uh#x61CsmdSq6V*-#DW&T=o4l9B>w#tW2R^K*-kXn;z<J3Xz7
zkX7yQ;XB7Oq2R%mU~@SVN}q3ogO<A3$4BEi$oOmzg&G8<3S_WH-okt5o<#1iYoPo~
z+IHlN@jKz^L2L9T_&V&-=As{fT?vkiyr7F^61GTq@oTyk62Ii_BLH~;lxa=Y0H+s#
zrS*7p#I|}?ak{A@goF)EMAB>h|BdU?<K^WAs9K61nEooZwiK)O_WJs5bu+{$qg!^$
zdL<Dl#ZP~Y`fI&o<?IH>XA>Z3#?ef%ICe<b1cH~jLX}LlViAJY2>61S8Q?{NGXj+s
zU^@)q3GFT*Zp0y%_uBBXiwiArr&6cF1#7cj+F25%ovn+#`OGLLARxeOjT-s?{{pK5
zE;anrYlt@B?^Ypmh34WX0P6|L9NX&pb?e@z5O0bw>EGRAgp!A4jdP3zt+RUp>b=07
ziJvW<yEkf0+qeGwo>h2#9+&3acj@Dr4r_#oMS8B^|2(ressmm4{rluh2IC(T*0z+7
zz(In``2qF;b?IRCata9Cg7gygP;+p0CS{E=^@9}G7;W%`bBGAC0J*~xsG8S-;v@iK
zqecrX;t1TZzagHFtWUfXvY??1|5|;A4EBXBXp{xg)f|~8C^)~Rn|*bku|jq59I(`}
zRxwv5c+dby7>E#TMH4r(99M^2&_-u?((w}gDnZ?o+_cFbP{nc31v@%B?JA^^Z7{{g
z;D*|8MymikhmIW!t$+7dYVe|>A$jKP_hk*Vv-&<JD>*s$-WE`Lft3LOan&)*5gDu<
z3Nl8(_g$>$`t9%W=5I<<t`lwo$S#I8qOd)w!$?*?Upd+<LCA*&xy`Pb*haXG(ZgrT
zxFi2+hLR2xt^-ZU!bJ30%Z<^vk(iih231;RZC3!kL-(=}6K<b)FB<Ss|J4E;3_iXT
zob@zBLd>op-HDWt;>=JgEQx6UKRRLc-_ZE@_+YniYYE$rCoa<mjE{oW-oZg92>nvO
zgNdw@VW<_YcmUKt8S{@1@$oo=Lm_1Wi_&_N47h%T*aQXGrlU`nLzJ|L*n+JH636=G
z^#DXdMFo^=)U%U6=sEscQdPcJXo~)Qr6Y^Nv<nx4_;LW47;&X02d-{o+zAQZ?H5V`
z{5uEBCqSmm0OH2N?cLe93zOu1I#ok3zf}i-LJ_TK;?eX1uyQ=4F+4VO4m>8S*=u8a
z8(o$9=j&p)PA&9LTa}0}9@7(ld;ToO8Gkd~{`<vEZ422&4d&C{_;vQI0vV_l>r)xS
zE}Ko!=16W|G}x}KR%1i+o7Kk~&c`*b!KCRrcu1^}{6mb)fldy*v-qN9KxFqI9|?}}
z<qmWC6K&K)hD`TY`tv{5G_nc|O`AQp2CxwSBpC65US3xwd;kyI{+p4l?`x-uBs*K{
z0S~Y5VIE4QKegMa&lxhUDaMVXhJ)sb;vTY17GFehYMd_l*M7ye5mIN;Jd3om75~9o
z_@V#&p-QC=6|B5V$!T-iVll-1ry()kDGkCE4pVO!2|?!b80!|~)aq9nu(?13xsE!P
z%<J;iO0J=Z6uJOF1Q)&^Ib_&(Wa{447}3dq?~ui-#+znXhhg>^Uv@%6r+=*MG?<@w
zp(lG^-9RHW!hx`1Fo>Ta(GPs&N&vZ0!r6QDXmGt0^_zubQPg(=o1Pz!SvU+57xJ`>
z%*<WLBMQsQH-G1L8N29}<>5H>)6Hu~qquU6O$HTWiPO>%kVa>i8MrHtTK}?Wqt3`r
zYGq6hQO8~GJ?9R#LH>~sME0CyptXg!Y^idd9V@vB&|(+Fz+uubtJsR;-x>xJ<tbo`
z>Zd<{_KXLO&(dH91Oi9L8?Z`T8or5vIDEf6KDf#$PG3*&{_!YK*vts6(g$uCc6g~3
zb~Ig(fMslU0)SipI8vQOFz1L)MrGv;><9@GFEHb)YXz){wv$o|w~q-f4n=5F-v$<%
z36@9M3+?B(7NMN;E<a_mIyHZ`B%kpe`>d_SgF=oBOcu|=ccu^w;K170Lws>(x{IqT
zB}e9)dm6{_>#2-cx7@iptl2<(Gd@h^{Wwj<2FGVyEVwfg^xc*FtR1tew<yOrx%hMB
zyA2^STV@RQ^@o%M(13L|lq-wtrIp$uG{AjDd=Q{mGZ@ZrW9yrgY4zyQahQ1yoi8u!
zqTc8+a6?FvTU~1wlb4rAJV|(<Vvz-r_a+Vv{q*7H)DoINgjq$B)M^XIRKA~Ccfp9@
zLA3V)VS@M|wW80QyTRe|;i?S2ksp~oCF8@mBkqTzNg(bK`d4(=3SFGC-nAWcSL_=(
zmd7xho%$!1dx`bd0j`aQ^Uu%0k#0Feo1nn4ATUCEqkekvhYv>qk;hF?Y!GoB;u{m3
zDVdzkt6CGRWr+jH+qZI%g@>KfN0u6r&yGjF0t6n&?Q%Bu$&VkGVl|`6Au&RSq$viR
zsQTd_r5=IIFm5k?H*eD8yDW<sbP`1+3M13eZ92EEJbN~?V0dt1O{9&}Oe=M8ssV&w
z#3$Ac?zC+0|MeYo@)$a^Q?~)|6$1(NL$C`z$DOzhdYo<pveiMvjp(hd385omvXGDz
zoO8N0Qc|_wpVEjWazg5yNatjW5xIc)j~tCe-yRR6fyr}FQG#G6rk@^o!qCN=;L?GD
z@7dp<@dgS(fT}a0$pX!qV7?*lSjojj(6Nww>hySFsA5#ze|@w*k>@cDcsvi3Z@7a#
zuAk1H&Mb%;3~R5>c<pXIHSD$|T)|;8h{7g>Op;E}s)OSrnwS!^&Q)#k?o)Hw6{4Xu
zz1lcFOc71bBH6ApXtT2nN3#Z+`XO#wk9G&Vt{%tm$!<r7tWLm!30fSoTeB~Y<L|Kf
z5Y9SrL3yxn6hF2a5eF6|Oz~KVQ6FyD7kITb-x<tVYl`43BVK`o^G@j~(3$D0uVy6+
zz&+Qj=VHa}J}jJ)eson}UX)Z;R>mfGr+H{+;8D$<Ek3Huh06?jBl|E7ZUSY=izE7-
zWiv*O*E89)jH5`B<qX)W`>_jP&r`TmN)rglW9x0(g}bjmTS2AolbV`phm9^vzy^&4
z%ZyLKZf!%+$8<E?@si<#J0jB(Nkp#}Z<JsJ`3vVfYf<S;Omlqei*{CABleq`K80~=
zotVSc>bRH(CZ-83mDHB039XD*`tFMDXn?e$f#&{+87)glnJFrCyvhi_bCpK1(V|rb
zt7=sKUj1~NSYC`%`s1CRQ+_7g+0)<S$UDYe?dW3_|Ev*CE-r>$7<(F2I526v&|;up
z4kh_&LBSaPuhV7X3$fOqRQC`NC<*aPZUzJtwYMu*D~U=2_6?Q>Ob)NYCyn?zTtLVs
zNTB;aip%3-nxk4@2!`vgCFvv72(i%_hUuA7zxOR`AXCCVx2-DvdzfH#25CRUEJRIQ
zOda<+;-@OUP@UM<*7m)(zdt;&I`j4C(HJVWD4F!CUF!!8-KWfoaKxU>aeY%ynZ*0!
z^D*IOU=!F%>{8F*mau=%o@-LLn-GJ;{V*vJD|suWI1g>;Hhf4Rx&gQW2;MFz;F0mJ
z4Pg{*k*PEf-fY#SK*%|HKmd=&+*r{C#P0`)?yO+wzzvG6ruFfzuw^XVi~AwGbS1G8
zt&x|?$Km$@T}CWLl3J?lPz{63{iz9g2X-Ewb7(Noo51^PW_5aHWN)8xB+Jo?aH2op
z5*@#@h0mi5^YZVVndd`W-aVfn<?4)<slL+MS@*APL%r{MCNGZYSSJ|a?4p96HnrTg
zq6eplEItnm(enh%yb<_O7>b<-CHxDH+?e`VH4F*vuG@)GL=pU1u@Op6PYhdbQ}PsV
zjklJ?j#xv^6#&g;_|M?b-H#hSD-PQtxZ~g^bpz(Z{rX{*hp?4zBatO|%4F2`V|e4Y
zq@eXj%Fw0fPt1jOm=Z`vyHO8xp>0~Hq%>ghySC#Pu%2laS+|bcC&)=zw&?A}HtP74
zIk(e-A@BZq#dhny7)E1q96RC<X5^hjWg8_hQ(gSaB&juTZE!TPXO4bmKmz(7oES;E
znVo$Hu|)j8{Bbvm>rx0WrlTjUY97)eyHnLLgNw?2bgY;U!lBWL{3Fz-;o;m!V4%<K
zQT;UXjEJ_;ZG`&@OiIMqf~ylSF#ttTf%GBOArfd5yzf=+@abCZuddRqgUgm$bPt4t
z0Kdy&;@uLM#GP2)RnZg99FfRXc68jyF^a>{b_p9feoxU?h?BjHu!*~Mfs9433Gksc
zJHjB36hS`hJq&PgK+7PH6*ml?y#*{7kO(1#X+yWMeP}zN-Gx4VOgy--l%9|IFFqZ4
z!!rwTL&Z##u8Y?PHkJ_6aZACwdI-l@NF(ei9lN2OxDI6)E^^p-zn;&-m=JnX0y-cv
z1cUramB{_rB@B%{f^HOA62Fw(7R)n?fSR!`!C=Ri44Z1C8Aw7Hi|jO9EOdH^rvUcE
zCZK4^?*Xt%L)zbPb-Dp&tZq3}{Ws9z4;@S~0(3Bs++w@hhG68Fy3TpwlJFS1<Ah;7
zPLh0R5s`wT0IojQ|Ju29W{^D%!QR%8XcSW%6Y5u**JV0LgS=cfyeXgJbjY3=$%2{4
z_PPneJIBT%eYR!|Y5A!@EJ%{q$igOvTH-WB-tSGe<E2YWiIFshU!T7YE>#kFvmC0b
zswC9J(SbefA+!z|fnx|lmeSL=Q73GWHzMXRH0Wg`ZjU&b*!lTcci|S*|LIvk{Z5>+
z=)kgviC@;7GoH*J(x-LRP>ORSze4;1BFM$Z7w}o#cx1{1;3BX_NvSO*0o7++_dKjL
zJq{I5Fy}QPGH;<`ofTA84u`eiZZ5XK#>7PT5Sxe2AY2a)9z1xX-W||{Q*g?vkP7gd
z<wHqvU9}~qIgkQa;FRdwodW|AJt@B}s-PF($q*M@xze`f>SkHN!4LgC`tdV;V|Xfc
z;<$Kb75kJdu?weq6S*f=Fk#)s5yRp>=xZ|cCb8{kLsSu`lkH(|XGfcKetq@{>>I)m
zupk%LIXW6M+*MpsauKRS{B+px8Gpal8)O8G;G!XoEYpS9fg{+4D)2ptf_`Rl)B@JG
zZcrB!_jD&k!+&{6!Add+p=ot8l8HBo8<c;4&NQ3=h;0E9HswLU7te-ZCn%G}zCWjt
zaS-EKg#(k^LNEotk+d$X;WBt>>_s&-HHlG!8yp-_*9gb-YrA*~(KE@Nfke?ZE@i#l
ztUR=3g&d+gMiHFu0F(#?x8o8+%=ywUH1ENIJu)Q+lZ?ms0n&eEWYoSo5Yjsvz;fBk
zXhA(DJ~qS&YETX>ou_dLfc~&M_b4+;Pkw$;NB;hm6cPU^!utK!{@?z1Ua-CG-68j_
S*&;Of@4!Aym4rRU*Zvm)dwS&n

literal 0
HcmV?d00001

diff --git a/git-main/developer-guide/contribution-guidelines/index.html b/git-main/developer-guide/contribution-guidelines/index.html
index 12f6dbe..ac394e9 100644
--- a/git-main/developer-guide/contribution-guidelines/index.html
+++ b/git-main/developer-guide/contribution-guidelines/index.html
@@ -1138,7 +1138,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1148,7 +1148,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1159,11 +1159,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1180,7 +1180,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1201,7 +1201,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1222,7 +1222,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/firmware/building-and-flashing/index.html b/git-main/developer-guide/firmware/building-and-flashing/index.html
index f3db610..7705e23 100644
--- a/git-main/developer-guide/firmware/building-and-flashing/index.html
+++ b/git-main/developer-guide/firmware/building-and-flashing/index.html
@@ -1168,7 +1168,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1178,7 +1178,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1189,11 +1189,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1210,7 +1210,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1231,7 +1231,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1252,7 +1252,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/firmware/code-architecture/index.html b/git-main/developer-guide/firmware/code-architecture/index.html
index abcfc10..1adf812 100644
--- a/git-main/developer-guide/firmware/code-architecture/index.html
+++ b/git-main/developer-guide/firmware/code-architecture/index.html
@@ -1249,7 +1249,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1259,7 +1259,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1270,11 +1270,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1291,7 +1291,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1312,7 +1312,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1333,7 +1333,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/firmware/debugging/index.html b/git-main/developer-guide/firmware/debugging/index.html
index 2cb6c6c..e665fa3 100644
--- a/git-main/developer-guide/firmware/debugging/index.html
+++ b/git-main/developer-guide/firmware/debugging/index.html
@@ -1219,7 +1219,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1229,7 +1229,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1240,11 +1240,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1261,7 +1261,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1282,7 +1282,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1303,7 +1303,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/firmware/unit-tests/index.html b/git-main/developer-guide/firmware/unit-tests/index.html
index d6fa856..f3333e6 100644
--- a/git-main/developer-guide/firmware/unit-tests/index.html
+++ b/git-main/developer-guide/firmware/unit-tests/index.html
@@ -1153,7 +1153,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1163,7 +1163,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1174,11 +1174,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1195,7 +1195,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1216,7 +1216,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1237,7 +1237,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/rosplane/controller/controller-base/index.html b/git-main/developer-guide/rosplane/controller/controller-base/index.html
index 1927e8f..b66c95b 100644
--- a/git-main/developer-guide/rosplane/controller/controller-base/index.html
+++ b/git-main/developer-guide/rosplane/controller/controller-base/index.html
@@ -1179,7 +1179,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1189,7 +1189,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1200,11 +1200,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1221,7 +1221,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planner/" class="md-nav__link">
+      <a href="../../navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1242,7 +1242,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-manager/" class="md-nav__link">
+      <a href="../../navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1263,7 +1263,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-follower/" class="md-nav__link">
+      <a href="../../navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/rosplane/controller/controller-general-overview/index.html b/git-main/developer-guide/rosplane/controller/controller-general-overview/index.html
index 0b23f35..bbb045a 100644
--- a/git-main/developer-guide/rosplane/controller/controller-general-overview/index.html
+++ b/git-main/developer-guide/rosplane/controller/controller-general-overview/index.html
@@ -1179,7 +1179,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1189,7 +1189,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1200,11 +1200,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1221,7 +1221,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planner/" class="md-nav__link">
+      <a href="../../navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1242,7 +1242,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-manager/" class="md-nav__link">
+      <a href="../../navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1263,7 +1263,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-follower/" class="md-nav__link">
+      <a href="../../navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/rosplane/controller/controller-outline/index.html b/git-main/developer-guide/rosplane/controller/controller-outline/index.html
index 1d98434..191b948 100644
--- a/git-main/developer-guide/rosplane/controller/controller-outline/index.html
+++ b/git-main/developer-guide/rosplane/controller/controller-outline/index.html
@@ -1305,7 +1305,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1315,7 +1315,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1326,11 +1326,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1347,7 +1347,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planner/" class="md-nav__link">
+      <a href="../../navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1368,7 +1368,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-manager/" class="md-nav__link">
+      <a href="../../navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1389,7 +1389,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-follower/" class="md-nav__link">
+      <a href="../../navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/rosplane/controller/controller-software-architecture/index.html b/git-main/developer-guide/rosplane/controller/controller-software-architecture/index.html
index 02c1949..85ca8ad 100644
--- a/git-main/developer-guide/rosplane/controller/controller-software-architecture/index.html
+++ b/git-main/developer-guide/rosplane/controller/controller-software-architecture/index.html
@@ -1155,7 +1155,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1165,7 +1165,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1176,11 +1176,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1197,7 +1197,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planner/" class="md-nav__link">
+      <a href="../../navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1218,7 +1218,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-manager/" class="md-nav__link">
+      <a href="../../navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1239,7 +1239,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-follower/" class="md-nav__link">
+      <a href="../../navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/rosplane/controller/controller-state-machine/index.html b/git-main/developer-guide/rosplane/controller/controller-state-machine/index.html
index 3c23259..8a55c06 100644
--- a/git-main/developer-guide/rosplane/controller/controller-state-machine/index.html
+++ b/git-main/developer-guide/rosplane/controller/controller-state-machine/index.html
@@ -1197,7 +1197,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1207,7 +1207,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1218,11 +1218,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1239,7 +1239,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planner/" class="md-nav__link">
+      <a href="../../navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1260,7 +1260,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-manager/" class="md-nav__link">
+      <a href="../../navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1281,7 +1281,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-follower/" class="md-nav__link">
+      <a href="../../navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/rosplane/controller/controller-total-energy/index.html b/git-main/developer-guide/rosplane/controller/controller-total-energy/index.html
index 2c5ec69..64318e3 100644
--- a/git-main/developer-guide/rosplane/controller/controller-total-energy/index.html
+++ b/git-main/developer-guide/rosplane/controller/controller-total-energy/index.html
@@ -1155,7 +1155,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1165,7 +1165,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1176,11 +1176,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1197,7 +1197,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-planner/" class="md-nav__link">
+      <a href="../../navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1218,7 +1218,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-manager/" class="md-nav__link">
+      <a href="../../navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1239,7 +1239,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../path-planning/path-follower/" class="md-nav__link">
+      <a href="../../navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/rosplane/path-planning/path-planning-overview/index.html b/git-main/developer-guide/rosplane/navigation/navigation-overview/index.html
similarity index 93%
rename from git-main/developer-guide/rosplane/path-planning/path-planning-overview/index.html
rename to git-main/developer-guide/rosplane/navigation/navigation-overview/index.html
index caf4356..c1685d6 100644
--- a/git-main/developer-guide/rosplane/path-planning/path-planning-overview/index.html
+++ b/git-main/developer-guide/rosplane/navigation/navigation-overview/index.html
@@ -12,7 +12,7 @@
         <meta name="author" content="James Jackson, Daniel Koch, Ian Reid, Brandon Sutherland">
       
       
-        <link rel="canonical" href="http://rosflight.org/git-main/developer-guide/rosplane/path-planning/path-planning-overview/">
+        <link rel="canonical" href="http://rosflight.org/git-main/developer-guide/rosplane/navigation/navigation-overview/">
       
       
         <link rel="prev" href="../../parameter-management/">
@@ -26,7 +26,7 @@
     
     
       
-        <title>Path Planning Overview - ROSflight</title>
+        <title>Navigation Overview - ROSflight</title>
       
     
     
@@ -76,7 +76,7 @@
     <div data-md-component="skip">
       
         
-        <a href="#path-planning-overview" class="md-skip">
+        <a href="#navigation-overview" class="md-skip">
           Skip to content
         </a>
       
@@ -125,7 +125,7 @@
         <div class="md-header__topic" data-md-component="header-topic">
           <span class="md-ellipsis">
             
-              Path Planning Overview
+              Navigation Overview
             
           </span>
         </div>
@@ -1088,7 +1088,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1098,7 +1098,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="true">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1122,7 +1122,7 @@
           
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1133,7 +1133,7 @@
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1155,9 +1155,18 @@
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
       
         <li class="md-nav__item">
-  <a href="#changing-path-planning" class="md-nav__link">
+  <a href="#changing-the-navigation-stack" class="md-nav__link">
     <span class="md-ellipsis">
-      Changing Path Planning
+      Changing the Navigation Stack
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#running-the-navigation-stack" class="md-nav__link">
+    <span class="md-ellipsis">
+      Running the Navigation Stack
     </span>
   </a>
   
@@ -1285,9 +1294,18 @@
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
       
         <li class="md-nav__item">
-  <a href="#changing-path-planning" class="md-nav__link">
+  <a href="#changing-the-navigation-stack" class="md-nav__link">
+    <span class="md-ellipsis">
+      Changing the Navigation Stack
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#running-the-navigation-stack" class="md-nav__link">
     <span class="md-ellipsis">
-      Changing Path Planning
+      Running the Navigation Stack
     </span>
   </a>
   
@@ -1308,7 +1326,7 @@
                   
 
   
-    <a href="https://github.com/rosflight/rosflight_docs/edit/main/docs/developer-guide/rosplane/path-planning/path-planning-overview.md" title="Edit this page" class="md-content__button md-icon">
+    <a href="https://github.com/rosflight/rosflight_docs/edit/main/docs/developer-guide/rosplane/navigation/navigation-overview.md" title="Edit this page" class="md-content__button md-icon">
       
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4v-2m10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1 2.1 2.1Z"/></svg>
     </a>
@@ -1316,14 +1334,14 @@
   
 
 
-<h1 id="path-planning-overview">Path Planning Overview<a class="headerlink" href="#path-planning-overview" title="Permanent link">&para;</a></h1>
+<h1 id="navigation-overview">Navigation Overview<a class="headerlink" href="#navigation-overview" title="Permanent link">&para;</a></h1>
 <p>The path planning methods used in ROSplane is modeled after the architecture presented in <em>Small Unmanned Aircraft: Theory and Practice</em> by Dr. Randal Beard and Dr. Tim McLain.</p>
 <p>In their work, the path planning functionality of the aircraft is split into three main parts, as shown in Figure 1.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>This is not a full description of the architecture.
 For example, the state estimator is not shown, and not all of the inputs to each of the blocks is included.
-These elements were removed from the figure for clarity.</p>
+These elements were removed from the figure for simplicity.</p>
 </div>
 <table>
 <thead>
@@ -1345,14 +1363,18 @@ <h1 id="path-planning-overview">Path Planning Overview<a class="headerlink" href
 The job of the path follower is to control the course, airspeed, and altitude of the aircraft to follow these lines and orbits.</p>
 <p>For more information on each of these nodes, see the related documentation pages for the <a href="../path-planner/">path planner</a>, the <a href="../path-manager/">path manager</a>, and the <a href="../path-follower/">path follower</a>.
 See also chapters 10-13 of the <em>Small Unmanned Aircraft: Theory and Practice</em> book.</p>
-<h2 id="changing-path-planning">Changing Path Planning<a class="headerlink" href="#changing-path-planning" title="Permanent link">&para;</a></h2>
+<h2 id="changing-the-navigation-stack">Changing the Navigation Stack<a class="headerlink" href="#changing-the-navigation-stack" title="Permanent link">&para;</a></h2>
 <p>The path planner currently takes in a set of user-defined waypoints and follows those waypoints. 
 This is not useful in all contexts, since in many applications the aircraft needs to take in sensor data and create its own waypoints and paths.</p>
-<p>The modularity of this framework allows users to "plug in" their own algorithms for each of the blocks defined in Figure 1, instead of rewriting the whole path planning stack.</p>
 <p>For example, we could replace the path planner block with a vision-based guidance block.
 The vision-based-guidance block would make decisions based on visual data to create waypoints. 
 However, the interface between the path planner (now the visual-based guidance planner) and the path manager would remain the same.</p>
+<p>Similarly, the path manager could be adjusted to follow b-splines instead of straight lines and orbits as currently implemented, without affecting the general waypoint management (path planner) or the underlying path following control loops (path follower).</p>
+<p>The modularity of this framework allows users to "plug in" their own algorithms for each of the blocks defined in Figure 1, instead of rewriting the whole path planning stack.</p>
 <p>Chapter 13 of the <em>Small Unmanned Aircraft: Theory and Practice</em> book contains more detail on implementing a vision-based path planner.</p>
+<h2 id="running-the-navigation-stack">Running the Navigation Stack<a class="headerlink" href="#running-the-navigation-stack" title="Permanent link">&para;</a></h2>
+<p>To launch the navigation stack, you will need to launch 3 ROS2 nodes, one for each part of the navigation stack (path planner, manager, and follower).</p>
+<p>Remember to launch these nodes with the appropriate parameter launch file, as seen in the <code>rosplane.launch.py</code> file.</p>
 
 
 
diff --git a/git-main/developer-guide/rosplane/path-planning/path-follower/index.html b/git-main/developer-guide/rosplane/navigation/path-follower/index.html
similarity index 63%
rename from git-main/developer-guide/rosplane/path-planning/path-follower/index.html
rename to git-main/developer-guide/rosplane/navigation/path-follower/index.html
index 27b685f..946e422 100644
--- a/git-main/developer-guide/rosplane/path-planning/path-follower/index.html
+++ b/git-main/developer-guide/rosplane/navigation/path-follower/index.html
@@ -12,7 +12,7 @@
         <meta name="author" content="James Jackson, Daniel Koch, Ian Reid, Brandon Sutherland">
       
       
-        <link rel="canonical" href="http://rosflight.org/git-main/developer-guide/rosplane/path-planning/path-follower/">
+        <link rel="canonical" href="http://rosflight.org/git-main/developer-guide/rosplane/navigation/path-follower/">
       
       
         <link rel="prev" href="../path-manager/">
@@ -73,6 +73,11 @@
     <label class="md-overlay" for="__drawer"></label>
     <div data-md-component="skip">
       
+        
+        <a href="#path-follower" class="md-skip">
+          Skip to content
+        </a>
+      
     </div>
     <div data-md-component="announce">
       
@@ -1081,7 +1086,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1091,7 +1096,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="true">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1102,11 +1107,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../path-planning-overview/" class="md-nav__link">
+      <a href="../navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1171,6 +1176,19 @@
       <input class="md-nav__toggle md-toggle" type="checkbox" id="__toc">
       
       
+        
+      
+      
+        <label class="md-nav__link md-nav__link--active" for="__toc">
+          
+  
+  <span class="md-ellipsis">
+    Path Follower
+  </span>
+  
+
+          <span class="md-nav__icon md-icon"></span>
+        </label>
       
       <a href="./" class="md-nav__link md-nav__link--active">
         
@@ -1182,6 +1200,109 @@
 
       </a>
       
+        
+
+<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
+  
+  
+  
+    
+  
+  
+    <label class="md-nav__title" for="__toc">
+      <span class="md-nav__icon md-icon"></span>
+      Table of contents
+    </label>
+    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
+      
+        <li class="md-nav__item">
+  <a href="#overview" class="md-nav__link">
+    <span class="md-ellipsis">
+      Overview
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-follower-base" class="md-nav__link">
+    <span class="md-ellipsis">
+      Path Follower Base
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Path Follower Base">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#list-of-ros2-interfaces" class="md-nav__link">
+    <span class="md-ellipsis">
+      List of ROS2 Interfaces
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#interface-with-the-autopilot" class="md-nav__link">
+    <span class="md-ellipsis">
+      Interface with the Autopilot
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-follower-example" class="md-nav__link">
+    <span class="md-ellipsis">
+      Path Follower Example
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#parameters" class="md-nav__link">
+    <span class="md-ellipsis">
+      Parameters
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Parameters">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#list-of-parameters" class="md-nav__link">
+    <span class="md-ellipsis">
+      List of Parameters
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#modifying-the-path-follower" class="md-nav__link">
+    <span class="md-ellipsis">
+      Modifying the Path Follower
+    </span>
+  </a>
+  
+</li>
+      
+    </ul>
+  
+</nav>
+      
     </li>
   
 
@@ -1227,6 +1348,100 @@
   
   
   
+    
+  
+  
+    <label class="md-nav__title" for="__toc">
+      <span class="md-nav__icon md-icon"></span>
+      Table of contents
+    </label>
+    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
+      
+        <li class="md-nav__item">
+  <a href="#overview" class="md-nav__link">
+    <span class="md-ellipsis">
+      Overview
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-follower-base" class="md-nav__link">
+    <span class="md-ellipsis">
+      Path Follower Base
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Path Follower Base">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#list-of-ros2-interfaces" class="md-nav__link">
+    <span class="md-ellipsis">
+      List of ROS2 Interfaces
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#interface-with-the-autopilot" class="md-nav__link">
+    <span class="md-ellipsis">
+      Interface with the Autopilot
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-follower-example" class="md-nav__link">
+    <span class="md-ellipsis">
+      Path Follower Example
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#parameters" class="md-nav__link">
+    <span class="md-ellipsis">
+      Parameters
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Parameters">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#list-of-parameters" class="md-nav__link">
+    <span class="md-ellipsis">
+      List of Parameters
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#modifying-the-path-follower" class="md-nav__link">
+    <span class="md-ellipsis">
+      Modifying the Path Follower
+    </span>
+  </a>
+  
+</li>
+      
+    </ul>
   
 </nav>
                   </div>
@@ -1241,7 +1456,7 @@
                   
 
   
-    <a href="https://github.com/rosflight/rosflight_docs/edit/main/docs/developer-guide/rosplane/path-planning/path-follower.md" title="Edit this page" class="md-content__button md-icon">
+    <a href="https://github.com/rosflight/rosflight_docs/edit/main/docs/developer-guide/rosplane/navigation/path-follower.md" title="Edit this page" class="md-content__button md-icon">
       
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4v-2m10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1 2.1 2.1Z"/></svg>
     </a>
@@ -1249,9 +1464,158 @@
   
 
 
-  <h1>Path Follower</h1>
-
-
+<h1 id="path-follower">Path Follower<a class="headerlink" href="#path-follower" title="Permanent link">&para;</a></h1>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
+<p>The role of the path follower is to generate the correct airspeed, course, and altitude commands for the autopilot such that the aircraft follows the paths published by <code>path_manager</code>.</p>
+<p>More information on the <code>path_follower</code> can be found in <em>Small Unmanned Aircraft: Theory and Practice</em> by Dr. Randal Beard and Dr. Tim McLain.</p>
+<h2 id="path-follower-base">Path Follower Base<a class="headerlink" href="#path-follower-base" title="Permanent link">&para;</a></h2>
+<p>The path follower base contains all the ROS2 interfaces required for the path follower.
+A list of these interfaces is below.</p>
+<p>The <code>path_follower_base::follow</code> method is a virtual method that should be implemented by a derived class.
+The <code>path_follower_base</code> publishes the controller commands calculated by the implementation of <code>path_follower_base::follow</code>.</p>
+<h3 id="list-of-ros2-interfaces">List of ROS2 Interfaces<a class="headerlink" href="#list-of-ros2-interfaces" title="Permanent link">&para;</a></h3>
+<table>
+<thead>
+<tr>
+<th style="text-align: center;"><strong>ROS2 Interface</strong></th>
+<th style="text-align: center;"><strong>Topic or Service</strong></th>
+<th style="text-align: center;"><strong>Explanation</strong></th>
+<th style="text-align: center;"><strong>Message or Service Type</strong></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: center;"><code>vehicle_state_sub_</code></td>
+<td style="text-align: center;"><code>/estimated_state</code></td>
+<td style="text-align: center;">Subscribes to the estimated aircraft state</td>
+<td style="text-align: center;"><code>rosplane_msgs::msg::State</code></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>current_path_sub_</code></td>
+<td style="text-align: center;"><code>/current_path</code></td>
+<td style="text-align: center;">Subscribes to the current path messages published by <code>path_manager</code></td>
+<td style="text-align: center;"><code>rosplane_msgs::msg::CurrentPath</code></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>controller_commands_pub_</code></td>
+<td style="text-align: center;"><code>/controller_commands</code></td>
+<td style="text-align: center;">Publishes control commands to the autopilot</td>
+<td style="text-align: center;"><code>rosplane_msgs::msg::ControllerCommand</code></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>update_timer_</code></td>
+<td style="text-align: center;">--</td>
+<td style="text-align: center;">ROS2 timer that controls how frequently <code>controller_commands_pub_</code> publishes</td>
+<td style="text-align: center;">--</td>
+</tr>
+</tbody>
+</table>
+<h3 id="interface-with-the-autopilot">Interface with the Autopilot<a class="headerlink" href="#interface-with-the-autopilot" title="Permanent link">&para;</a></h3>
+<p>The <code>path_follower</code> node interfaces with the MAV autopilot by publishing to the <code>/controller_commands</code> topic.
+The <code>/controller_commands</code> topic contains the following information calculated by the <code>path_follower</code>:</p>
+<table>
+<thead>
+<tr>
+<th style="text-align: center;"><strong>Member</strong></th>
+<th style="text-align: center;"><strong>Description</strong></th>
+<th style="text-align: center;"><strong>Type / units</strong></th>
+<th style="text-align: center;"><strong>Required</strong></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: center;"><code>header</code></td>
+<td style="text-align: center;">Standard message header that contains a valid timestamp</td>
+<td style="text-align: center;"><code>std_msgs::msg::Header</code></td>
+<td style="text-align: center;">Yes</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>va_c</code></td>
+<td style="text-align: center;">Commanded airspeed</td>
+<td style="text-align: center;"><code>double</code>, m/s</td>
+<td style="text-align: center;">Yes</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>h_c</code></td>
+<td style="text-align: center;">Commanded altitude</td>
+<td style="text-align: center;"><code>double</code>, m</td>
+<td style="text-align: center;">Yes</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>chi_c</code></td>
+<td style="text-align: center;">Commanded course</td>
+<td style="text-align: center;"><code>double</code>, rad</td>
+<td style="text-align: center;">Yes</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>phi_ff</code></td>
+<td style="text-align: center;">Feedforward command (for orbits)</td>
+<td style="text-align: center;"><code>double</code>, rad</td>
+<td style="text-align: center;">No</td>
+</tr>
+</tbody>
+</table>
+<h2 id="path-follower-example">Path Follower Example<a class="headerlink" href="#path-follower-example" title="Permanent link">&para;</a></h2>
+<p>The <code>path_follower_example</code> class contains the implementation of the <code>path_follower_base::follow</code> method.
+This method contains the control command computations for straight line and orbit-type paths as outlined in <em>Small Unmanned Aircraft: Theory and Practice</em>.</p>
+<h2 id="parameters">Parameters<a class="headerlink" href="#parameters" title="Permanent link">&para;</a></h2>
+<p>See the <a href="../../parameter-management/">Parameter Management</a> page for more details on how parameter management works.</p>
+<h3 id="list-of-parameters">List of Parameters<a class="headerlink" href="#list-of-parameters" title="Permanent link">&para;</a></h3>
+<table>
+<thead>
+<tr>
+<th style="text-align: center;"><strong>Parameter</strong></th>
+<th style="text-align: center;"><strong>Explanation</strong></th>
+<th style="text-align: center;"><strong>Type / Units</strong></th>
+<th style="text-align: center;"><strong>Range</strong></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: center;"><code>chi_infty</code></td>
+<td style="text-align: center;">At infinity, the angle at which the aircraft will approach the desired line</td>
+<td style="text-align: center;">double (rad)</td>
+<td style="text-align: center;"><span class="arithmatex"><span class="MathJax_Preview">\frac{\pi}{2} \geq \chi^{\infty} &gt; 0.0</span><script type="math/tex">\frac{\pi}{2} \geq \chi^{\infty} > 0.0</script></span></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>k_path</code></td>
+<td style="text-align: center;">Constant that determines how quickly commanded course transitions from <span class="arithmatex"><span class="MathJax_Preview">\chi^{\infty}</span><script type="math/tex">\chi^{\infty}</script></span> to 0 during line following</td>
+<td style="text-align: center;">double</td>
+<td style="text-align: center;"><span class="arithmatex"><span class="MathJax_Preview">&gt; 0.0</span><script type="math/tex">> 0.0</script></span></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>k_orbit</code></td>
+<td style="text-align: center;">Constant that determines how quickly commanded course transitions from <span class="arithmatex"><span class="MathJax_Preview">\lambda \frac{\pi}{2}</span><script type="math/tex">\lambda \frac{\pi}{2}</script></span> to 0 during an orbit</td>
+<td style="text-align: center;">double</td>
+<td style="text-align: center;"><span class="arithmatex"><span class="MathJax_Preview">&gt; 0.0</span><script type="math/tex">> 0.0</script></span></td>
+</tr>
+</tbody>
+</table>
+<p>Since there are two different types of lines generated by the <code>path_manager</code> (straight lines and orbits), the <code>path_follower</code> uses different parameters to calculate the control output for each path type.</p>
+<p>For <strong>line following</strong>, <code>path_follower</code> uses </p>
+<ul>
+<li><code>chi_infty</code> and </li>
+<li><code>k_path</code> to compute the control commands.</li>
+</ul>
+<p>As described in <em>Small Unmanned Aircraft: Theory and Practice</em>, these two parameters define a vector field for the commanded course.
+The <code>chi_infty</code> parameter describes the angle at which the aircratft will approach a target line if the aircraft is infinitely far from the target line.
+For example, if <code>chi_infty</code> is set to <span class="arithmatex"><span class="MathJax_Preview">\frac{\pi}{2}</span><script type="math/tex">\frac{\pi}{2}</script></span>, then the aircraft will approach the target line at an angle perpindicular to the line when the aircraft is far away.</p>
+<p>The <code>k_path</code> parameter defines how quickly the vectors at <code>chi_infty</code> "smooth" into the target line.
+When <code>k_path</code> is large, the transition will be abrupt, and when <code>k_path</code> is small, the transition will be smoother.</p>
+<p>During <strong>orbit following</strong>, <code>path_follower</code> uses</p>
+<ul>
+<li><code>k_orbit</code> to compute the control commands.</li>
+</ul>
+<p>If the aircraft is very far away from the orbit, it will align itself so it flies directly at the center of the orbit.
+The <code>k_orbit</code> parameter is similar to the <code>k_path</code> parameter in that it determines how quickly the commanded angle of the aircraft will change from directly toward the center to the orbit direction.</p>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>When tuning, make sure you are changing the correct gains for the type of line (straight or orbit) the aircraft is tracking.
+<code>chi_infty</code> and <code>k_path</code> will not affect the orbit performance!</p>
+</div>
+<h2 id="modifying-the-path-follower">Modifying the Path Follower<a class="headerlink" href="#modifying-the-path-follower" title="Permanent link">&para;</a></h2>
+<p>Changes to any of the ROS2 interface should be done in the <code>path_follower_base</code>.</p>
+<p>Changes to how <code>path_follower</code> computes control commands to follow paths given by the <code>path_manager</code> should be done in the <code>path_manager_example</code>.</p>
 
 
 
diff --git a/git-main/developer-guide/rosplane/path-planning/path-manager/index.html b/git-main/developer-guide/rosplane/navigation/path-manager/index.html
similarity index 63%
rename from git-main/developer-guide/rosplane/path-planning/path-manager/index.html
rename to git-main/developer-guide/rosplane/navigation/path-manager/index.html
index 968df66..65ff11f 100644
--- a/git-main/developer-guide/rosplane/path-planning/path-manager/index.html
+++ b/git-main/developer-guide/rosplane/navigation/path-manager/index.html
@@ -12,7 +12,7 @@
         <meta name="author" content="James Jackson, Daniel Koch, Ian Reid, Brandon Sutherland">
       
       
-        <link rel="canonical" href="http://rosflight.org/git-main/developer-guide/rosplane/path-planning/path-manager/">
+        <link rel="canonical" href="http://rosflight.org/git-main/developer-guide/rosplane/navigation/path-manager/">
       
       
         <link rel="prev" href="../path-planner/">
@@ -75,6 +75,11 @@
     <label class="md-overlay" for="__drawer"></label>
     <div data-md-component="skip">
       
+        
+        <a href="#path-manager" class="md-skip">
+          Skip to content
+        </a>
+      
     </div>
     <div data-md-component="announce">
       
@@ -1083,7 +1088,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1093,7 +1098,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="true">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1104,11 +1109,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../path-planning-overview/" class="md-nav__link">
+      <a href="../navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1152,6 +1157,19 @@
       <input class="md-nav__toggle md-toggle" type="checkbox" id="__toc">
       
       
+        
+      
+      
+        <label class="md-nav__link md-nav__link--active" for="__toc">
+          
+  
+  <span class="md-ellipsis">
+    Path Manager
+  </span>
+  
+
+          <span class="md-nav__icon md-icon"></span>
+        </label>
       
       <a href="./" class="md-nav__link md-nav__link--active">
         
@@ -1163,6 +1181,118 @@
 
       </a>
       
+        
+
+<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
+  
+  
+  
+    
+  
+  
+    <label class="md-nav__title" for="__toc">
+      <span class="md-nav__icon md-icon"></span>
+      Table of contents
+    </label>
+    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
+      
+        <li class="md-nav__item">
+  <a href="#overview" class="md-nav__link">
+    <span class="md-ellipsis">
+      Overview
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-manager-base" class="md-nav__link">
+    <span class="md-ellipsis">
+      Path Manager Base
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Path Manager Base">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#list-of-ros2-interfaces" class="md-nav__link">
+    <span class="md-ellipsis">
+      List of ROS2 Interfaces
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#interface-with-the-path-follower" class="md-nav__link">
+    <span class="md-ellipsis">
+      Interface with the Path Follower
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-manager-example" class="md-nav__link">
+    <span class="md-ellipsis">
+      Path Manager Example
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#parameters" class="md-nav__link">
+    <span class="md-ellipsis">
+      Parameters
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Parameters">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#list-of-parameters" class="md-nav__link">
+    <span class="md-ellipsis">
+      List of Parameters
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#the-orbit_last-parameter" class="md-nav__link">
+    <span class="md-ellipsis">
+      The orbit_last Parameter
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#modifying-the-path-manager" class="md-nav__link">
+    <span class="md-ellipsis">
+      Modifying the Path Manager
+    </span>
+  </a>
+  
+</li>
+      
+    </ul>
+  
+</nav>
+      
     </li>
   
 
@@ -1229,6 +1359,109 @@
   
   
   
+    
+  
+  
+    <label class="md-nav__title" for="__toc">
+      <span class="md-nav__icon md-icon"></span>
+      Table of contents
+    </label>
+    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
+      
+        <li class="md-nav__item">
+  <a href="#overview" class="md-nav__link">
+    <span class="md-ellipsis">
+      Overview
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-manager-base" class="md-nav__link">
+    <span class="md-ellipsis">
+      Path Manager Base
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Path Manager Base">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#list-of-ros2-interfaces" class="md-nav__link">
+    <span class="md-ellipsis">
+      List of ROS2 Interfaces
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#interface-with-the-path-follower" class="md-nav__link">
+    <span class="md-ellipsis">
+      Interface with the Path Follower
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-manager-example" class="md-nav__link">
+    <span class="md-ellipsis">
+      Path Manager Example
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#parameters" class="md-nav__link">
+    <span class="md-ellipsis">
+      Parameters
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Parameters">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#list-of-parameters" class="md-nav__link">
+    <span class="md-ellipsis">
+      List of Parameters
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#the-orbit_last-parameter" class="md-nav__link">
+    <span class="md-ellipsis">
+      The orbit_last Parameter
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#modifying-the-path-manager" class="md-nav__link">
+    <span class="md-ellipsis">
+      Modifying the Path Manager
+    </span>
+  </a>
+  
+</li>
+      
+    </ul>
   
 </nav>
                   </div>
@@ -1243,7 +1476,7 @@
                   
 
   
-    <a href="https://github.com/rosflight/rosflight_docs/edit/main/docs/developer-guide/rosplane/path-planning/path-manager.md" title="Edit this page" class="md-content__button md-icon">
+    <a href="https://github.com/rosflight/rosflight_docs/edit/main/docs/developer-guide/rosplane/navigation/path-manager.md" title="Edit this page" class="md-content__button md-icon">
       
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4v-2m10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1 2.1 2.1Z"/></svg>
     </a>
@@ -1251,9 +1484,124 @@
   
 
 
-  <h1>Path Manager</h1>
-
-
+<h1 id="path-manager">Path Manager<a class="headerlink" href="#path-manager" title="Permanent link">&para;</a></h1>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
+<p>The path manager is responsible for calculating and publishing the current path to the path follower. 
+It is split into a base class and an inherited class.
+The base class handles the ROS2 interfaces (publishing and subscribing) while the inherited class manages the path, i.e., calculates the parameters for the current path.</p>
+<p>The path manager is designed this way so that the inherited class (how the paths are managed) can be replaced or rewritten without affecting the overlying ROS2 interface.</p>
+<p>Both the <code>path_manager_base</code> and the <code>path_manager_example</code> are included in the same ROS2 node when compiled, called <code>path_manager</code>.
+Parameters associated with the <code>path_manager_base</code> or the <code>path_manager_example</code> will therefore be visible under the <code>path_manager</code> ROS2 node.</p>
+<p>More details about the path manager can be found in <em>Small Unmanned Aircraft: Theory and Practice</em> by Dr. Randal Beard and Dr. Tim McLain.</p>
+<h2 id="path-manager-base">Path Manager Base<a class="headerlink" href="#path-manager-base" title="Permanent link">&para;</a></h2>
+<p>The path manager base contains all the ROS2 interfaces required for the path manager.
+A list of these interfaces is below.</p>
+<h3 id="list-of-ros2-interfaces">List of ROS2 Interfaces<a class="headerlink" href="#list-of-ros2-interfaces" title="Permanent link">&para;</a></h3>
+<table>
+<thead>
+<tr>
+<th style="text-align: center;"><strong>ROS2 Interface</strong></th>
+<th style="text-align: center;"><strong>Topic or Service</strong></th>
+<th style="text-align: center;"><strong>Explanation</strong></th>
+<th style="text-align: center;"><strong>Message or Service Type</strong></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: center;"><code>vehicle_state_sub_</code></td>
+<td style="text-align: center;"><code>/estimated_state</code></td>
+<td style="text-align: center;">Subscribes to the estimated aircraft state</td>
+<td style="text-align: center;"><code>rosplane_msgs::msg::State</code></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>new_waypoint_sub_</code></td>
+<td style="text-align: center;"><code>/waypoint_path</code></td>
+<td style="text-align: center;">Subscribes to the waypoint messages published by <code>path_planner</code></td>
+<td style="text-align: center;"><code>rosplane_msgs::msg::State</code></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>current_path_pub_</code></td>
+<td style="text-align: center;"><code>/current_path</code></td>
+<td style="text-align: center;">Publishes the parameters of the current path</td>
+<td style="text-align: center;"><code>rosplane_msgs::msg::CurrentPath</code></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>update_timer_</code></td>
+<td style="text-align: center;">--</td>
+<td style="text-align: center;">ROS2 timer that controls how frequently <code>current_path_pub_</code> publishes</td>
+<td style="text-align: center;">--</td>
+</tr>
+</tbody>
+</table>
+<h3 id="interface-with-the-path-follower">Interface with the Path Follower<a class="headerlink" href="#interface-with-the-path-follower" title="Permanent link">&para;</a></h3>
+<p>The <code>path_manager</code> node interfaces with the path follower by publishing to the <code>/current_path</code> topic.
+These messages contain information about the current trajectory, which are either straight lines or circles. </p>
+<p>Note that the only supported path types are straight lines and circles.
+Depending on how the <code>path_manager</code> is set up to manage the waypoints, this may not be suitable for your application.
+See "Modifying the Path Manager" for more information.
+For more information on the path follower, see the <a href="../path-follower/">Path Follwer</a> documentation.</p>
+<h2 id="path-manager-example">Path Manager Example<a class="headerlink" href="#path-manager-example" title="Permanent link">&para;</a></h2>
+<p>The <code>path_manager_example</code> class inherits from the <code>path_manager_base</code> class.
+Specifically, the <code>path_manager_example</code> overrides the <code>path_manager_base::manage</code> method to determine how the path is managed.</p>
+<p>In the current implementation, <code>path_manager_example</code> decides to manage a waypoint using straight lines and fillets, orbits, or Dubins paths based on the current state of the aircraft, the values of the current ROS2 parameters, and the waypoints given.
+For example, if the <code>use_chi</code> field on a Waypoint object (see <a href="../path-planner/">Path Planner</a> for more information) is set to <code>true</code>, then <code>path_manager_example</code> will use a Dubins path to navigate to the next waypoint.
+If <code>use_chi</code> is set to <code>false</code>, then <code>path_manager_example</code> will use straight lines when navigating in between waypoints and a fillet to manage the corners.
+See Figure 1 for an example of a real flight path flown using ROSplane with <code>chi_d</code> set to <code>false</code>.</p>
+<table>
+<thead>
+<tr>
+<th style="text-align: center;"><img alt="Example of flight path with straight lines and fillets" src="../../../../assets/path_planner_assets/Big_hourglass.png" title="Example of flight path with straight lines and fillets" /></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: center;"><img alt="Example of flight path with straight lines and fillets" src="../../../../assets/path_planner_assets/Big_hourglass_fillet.png" title="Example of flight path with straight lines and fillets" /></td>
+</tr>
+<tr>
+<td style="text-align: center;"><em>Example flight path from an actual flight test showing the straight lines and fillets path type</em></td>
+</tr>
+</tbody>
+</table>
+<p>Note that using fillets to manage the corners often means that the aircraft does not actually achieve the waypoint.
+If this is undesireable in your application, use Dubins paths or another method for the <code>path_manager</code>. </p>
+<h2 id="parameters">Parameters<a class="headerlink" href="#parameters" title="Permanent link">&para;</a></h2>
+<p>See the <a href="../../parameter-management/">Parameter Management</a> page for more details on how parameter management works.</p>
+<h3 id="list-of-parameters">List of Parameters<a class="headerlink" href="#list-of-parameters" title="Permanent link">&para;</a></h3>
+<table>
+<thead>
+<tr>
+<th style="text-align: center;"><strong>Parameter</strong></th>
+<th style="text-align: center;"><strong>Explanation</strong></th>
+<th style="text-align: center;"><strong>Type</strong></th>
+<th style="text-align: center;"><strong>Range</strong></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: center;"><code>R_min</code></td>
+<td style="text-align: center;">Minimum radius for orbit, fillet, and Dubins paths</td>
+<td style="text-align: center;">double</td>
+<td style="text-align: center;"><span class="arithmatex"><span class="MathJax_Preview">\geq</span><script type="math/tex">\geq</script></span> 0.0</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>orbit_last</code></td>
+<td style="text-align: center;">Specifies whether or not to orbit the last waypoint. If false, <code>param_manager</code> will fly a circuit</td>
+<td style="text-align: center;">bool</td>
+<td style="text-align: center;"><code>true</code> or <code>false</code></td>
+</tr>
+</tbody>
+</table>
+<h3 id="the-orbit_last-parameter">The <code>orbit_last</code> Parameter<a class="headerlink" href="#the-orbit_last-parameter" title="Permanent link">&para;</a></h3>
+<p>The <code>path_manager</code> node has a parameter named <code>orbit_last</code>.
+This parameter controls what happens as the aircraft is approaching the last waypoint in the set of waypoints published to the <code>path_manager</code>.
+If <code>orbit_last</code> is set to <code>true</code>, then <code>path_manager</code> will follow an orbit around the last waypoint.</p>
+<p>The direction of this waypoint (clockwise or counterclockwise) will be chosen based on which direction requires the least amount of turning.
+In other words, if the aircraft is angled slightly left as it approaches the waypoint, <code>path_manager</code> will choose to orbit the last waypoint counterclockwise (from a top-down perspective).
+If the aircraft is pointing slightly right as it approaches the waypoint, it will orbit the waypoint clockwise (from a top-down perspective).</p>
+<h2 id="modifying-the-path-manager">Modifying the Path Manager<a class="headerlink" href="#modifying-the-path-manager" title="Permanent link">&para;</a></h2>
+<p>Changes or additions to any ROS2 interfaces should be done in the <code>path_manager_base</code> field.</p>
+<p>Changes to how <code>path_manager</code> "manages" the waypoints should be done by overriding the <code>path_manager_base::manage</code> method.
+If you wish to change the way paths are defined, make sure that the <code>/current_path</code> topic is rewritten to contain the required information, and then make sure the <code>path_follower</code> knows how to handle the new definition.</p>
 
 
 
diff --git a/git-main/developer-guide/rosplane/path-planning/path-planner/index.html b/git-main/developer-guide/rosplane/navigation/path-planner/index.html
similarity index 83%
rename from git-main/developer-guide/rosplane/path-planning/path-planner/index.html
rename to git-main/developer-guide/rosplane/navigation/path-planner/index.html
index 1e4040d..4b4209a 100644
--- a/git-main/developer-guide/rosplane/path-planning/path-planner/index.html
+++ b/git-main/developer-guide/rosplane/navigation/path-planner/index.html
@@ -12,10 +12,10 @@
         <meta name="author" content="James Jackson, Daniel Koch, Ian Reid, Brandon Sutherland">
       
       
-        <link rel="canonical" href="http://rosflight.org/git-main/developer-guide/rosplane/path-planning/path-planner/">
+        <link rel="canonical" href="http://rosflight.org/git-main/developer-guide/rosplane/navigation/path-planner/">
       
       
-        <link rel="prev" href="../path-planning-overview/">
+        <link rel="prev" href="../navigation-overview/">
       
       
         <link rel="next" href="../path-manager/">
@@ -1088,7 +1088,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1098,7 +1098,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="true">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1109,11 +1109,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../path-planning-overview/" class="md-nav__link">
+      <a href="../navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1194,6 +1194,30 @@
     <nav class="md-nav" aria-label="Interfaces">
       <ul class="md-nav__list">
         
+          <li class="md-nav__item">
+  <a href="#about-waypoints" class="md-nav__link">
+    <span class="md-ellipsis">
+      About Waypoints
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="About Waypoints">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#notes-on-the-waypoint-object-fields" class="md-nav__link">
+    <span class="md-ellipsis">
+      Notes on the Waypoint object fields
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+        
           <li class="md-nav__item">
   <a href="#list-of-ros2-interfaces" class="md-nav__link">
     <span class="md-ellipsis">
@@ -1360,6 +1384,30 @@
     <nav class="md-nav" aria-label="Interfaces">
       <ul class="md-nav__list">
         
+          <li class="md-nav__item">
+  <a href="#about-waypoints" class="md-nav__link">
+    <span class="md-ellipsis">
+      About Waypoints
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="About Waypoints">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#notes-on-the-waypoint-object-fields" class="md-nav__link">
+    <span class="md-ellipsis">
+      Notes on the Waypoint object fields
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+        
           <li class="md-nav__item">
   <a href="#list-of-ros2-interfaces" class="md-nav__link">
     <span class="md-ellipsis">
@@ -1422,7 +1470,7 @@
                   
 
   
-    <a href="https://github.com/rosflight/rosflight_docs/edit/main/docs/developer-guide/rosplane/path-planning/path-planner.md" title="Edit this page" class="md-content__button md-icon">
+    <a href="https://github.com/rosflight/rosflight_docs/edit/main/docs/developer-guide/rosplane/navigation/path-planner.md" title="Edit this page" class="md-content__button md-icon">
       
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4v-2m10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1 2.1 2.1Z"/></svg>
     </a>
@@ -1430,12 +1478,12 @@
   
 
 
-<h1 id="path-planner">Path planner<a class="headerlink" href="#path-planner" title="Permanent link">&para;</a></h1>
+<h1 id="path-planner">Path Planner<a class="headerlink" href="#path-planner" title="Permanent link">&para;</a></h1>
 <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>The path planner is responsible for creating, managing, and publishing waypoints.
 In the current implementation, the path planner simply maintains a list of user-defined waypoints that the user can add to or clear.
 The path planner then controls when waypoints are published to the path manager.</p>
-<p>Another implementation of the path planner (as described in <a href="../path-planning-overview/">the overview</a>) could include a visual-based path planner.
+<p>Another implementation of the path planner (as described in <a href="../navigation-overview/">the overview</a>) could include a visual-based path planner.
 In this case, the path planner would receive sensor input and create and manage its own waypoints instead of a user-defined list of waypoints.
 However, this new path planner would still be responsible for creating and publishing waypoints.
 This ensures that the interface between the path planner and the path manager would stay the same, allowing for modularity in the path planner architecture.</p>
@@ -1444,9 +1492,83 @@ <h2 id="interfaces">Interfaces<a class="headerlink" href="#interfaces" title="Pe
 This node subscribes to the topics it needs, provides services available to the user and other nodes, and publishes waypoints to the path manager, called <code>path_manager</code>.</p>
 <p>The interface between <code>path_planner</code> and <code>path_manager</code> is the <code>/waypoint_path</code> topic,  which publishes messages with the <code>rosplane_msgs::msg::Waypoint</code> type.
 This message contains information about the waypoint's location in NED (from the origin) or GNSS (LLA) coordinates, the desired airspeed at the waypoint, and the desired heading of the aircraft at the waypoint.</p>
+<h3 id="about-waypoints">About Waypoints<a class="headerlink" href="#about-waypoints" title="Permanent link">&para;</a></h3>
+<p>The following table contains the data members of the <code>rosplane_msgs::msg::Waypoint</code> objects and a brief description.</p>
+<table>
+<thead>
+<tr>
+<th style="text-align: center;"><strong>Member</strong></th>
+<th style="text-align: center;"><strong>Description</strong></th>
+<th style="text-align: center;"><strong>Type</strong></th>
+<th style="text-align: center;"><strong>Required</strong></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: center;"><code>header</code></td>
+<td style="text-align: center;">Standard message header that contains a valid timestamp</td>
+<td style="text-align: center;"><code>std_msgs::msg::Header</code></td>
+<td style="text-align: center;">Yes</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>w</code></td>
+<td style="text-align: center;">Waypoint coordinates in NED or GNSS (LLA)</td>
+<td style="text-align: center;"><code>std::array&lt;float32, 3&gt;</code></td>
+<td style="text-align: center;">Yes</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>lla</code></td>
+<td style="text-align: center;">Flag to determine if the coordinates are passed in as NED or GNSS</td>
+<td style="text-align: center;"><code>bool</code></td>
+<td style="text-align: center;">Yes</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>chi_d</code></td>
+<td style="text-align: center;">Desired course at the waypoint</td>
+<td style="text-align: center;"><code>double</code></td>
+<td style="text-align: center;">No</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>use_chi</code></td>
+<td style="text-align: center;">Flag to use the <code>chi_d</code> value at the waypoint or not</td>
+<td style="text-align: center;"><code>bool</code></td>
+<td style="text-align: center;">No - defaults to <code>false</code></td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>va_d</code></td>
+<td style="text-align: center;">Desired airspeed at the waypoint</td>
+<td style="text-align: center;"><code>double</code></td>
+<td style="text-align: center;">Yes</td>
+</tr>
+<tr>
+<td style="text-align: center;"><code>clear_wp_list</code></td>
+<td style="text-align: center;">Clears all waypoints from <code>path_planner</code> and <code>path_manager</code></td>
+<td style="text-align: center;"><code>bool</code></td>
+<td style="text-align: center;">No</td>
+</tr>
+</tbody>
+</table>
+<h4 id="notes-on-the-waypoint-object-fields">Notes on the Waypoint object fields<a class="headerlink" href="#notes-on-the-waypoint-object-fields" title="Permanent link">&para;</a></h4>
+<p>The <code>w</code> field contains the coordinates of the waypoint in either NED coordinates (from the origin, defined as the place where ROSplane initialized) or GNSS coordinates given in LLA (latitude, longitude, and altitude).
+The GNSS coordinates are converted to NED coordinates by <code>path_planner</code> before sending them to <code>path_manager</code>.</p>
+<p>The <code>lla</code> field is a flag that tells <code>path_planner</code> if the coordinates provided are in the NED or world (GNSS) frame.
+Set it to <code>true</code> if the coordinates for the waypoint are given in GNSS coordinates.
+Note that GNSS and relative waypoints can be used together, meaning that one waypoint could be in the NED frame while the next one is in the global frame, since ROSplane converts global coordinates to the NED frame before publishing them to <code>path_manager</code>. </p>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>Make sure that the <code>lla</code> field is set correctly if you decide to use GNSS coordinates, or your waypoints will be incorrect.</p>
+</div>
+<p>The <code>chi_d</code> field controls the desired course at the waypoint.
+Note that this is only used if the <code>use_chi</code> flag is set to <code>true</code>. </p>
+<p>The <code>use_chi</code> field determines whether or not the <code>path_manager</code> should pay attention to the desired course (<code>chi_d</code>). 
+If <code>use_chi</code> is set to <code>true</code> then <code>path_manager</code> will use a Dubins path framework to manage the waypoint.
+If <code>use_chi</code> is set to <code>false</code>, then <code>path_manager</code> will ignore the desired course and will intead use straight lines and fillets to manage the transitions between waypoints.
+See the <a href="../path-manager/">Path Manager</a> documentation for more information on this behavior.</p>
+<p>The <code>clear_wp_list</code> is used internally by <code>path_planner</code> when the <code>/clear_waypoints</code> service is called.
+It is recommended to use the service call instead of using this field manually.</p>
 <div class="admonition warning">
 <p class="admonition-title">Warning</p>
-<p>The <code>w</code>, <code>va_d</code>, and <code>lla</code> fields must be valid for every waypoint message sent.
+<p>The <code>header</code>, <code>w</code>, <code>va_d</code>, and <code>lla</code> fields must be valid for every waypoint message sent.
 Failure to add these fields might crash the path planner or your aircraft.</p>
 </div>
 <h3 id="list-of-ros2-interfaces">List of ROS2 Interfaces<a class="headerlink" href="#list-of-ros2-interfaces" title="Permanent link">&para;</a></h3>
@@ -1526,8 +1648,12 @@ <h3 id="list-of-parameters">List of Parameters<a class="headerlink" href="#list-
 </tbody>
 </table>
 <h2 id="recommended-usage">Recommended Usage<a class="headerlink" href="#recommended-usage" title="Permanent link">&para;</a></h2>
-<p>We recommend using a YAML file and the <code>/load_mission_from_file</code> service to load and fly waypoints.
+<p>We recommend using a YAML file and the <code>/load_mission_from_file</code> service from the command line to load and fly waypoints.
 See the example mission YAML file located at <code>/path/to/rosplane/rosplane/params/fixedwing_mission.yaml</code>.</p>
+<p>To call the service, run
+<div class="highlight"><pre><span></span><code>ros2<span class="w"> </span>service<span class="w"> </span>call<span class="w"> </span>/load_mission_from_file<span class="w"> </span>rosflight_msgs::srv::ParamFile<span class="w"> </span><span class="s2">&quot;{filename: &lt;FILENAME&gt;}&quot;</span>
+</code></pre></div>
+where <code>&lt;FILENAME&gt;</code> is the path to the mission YAML file.</p>
 
 
 
diff --git a/git-main/developer-guide/rosplane/parameter-management/index.html b/git-main/developer-guide/rosplane/parameter-management/index.html
index 1bb9d3b..b9c13dc 100644
--- a/git-main/developer-guide/rosplane/parameter-management/index.html
+++ b/git-main/developer-guide/rosplane/parameter-management/index.html
@@ -18,7 +18,7 @@
         <link rel="prev" href="../controller/controller-total-energy/">
       
       
-        <link rel="next" href="../path-planning/path-planning-overview/">
+        <link rel="next" href="../navigation/navigation-overview/">
       
       
       <link rel="icon" href="../../../assets/favicon.ico">
@@ -1195,7 +1195,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1205,7 +1205,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1216,11 +1216,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1237,7 +1237,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../path-planning/path-planner/" class="md-nav__link">
+      <a href="../navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1258,7 +1258,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../path-planning/path-manager/" class="md-nav__link">
+      <a href="../navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1279,7 +1279,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../path-planning/path-follower/" class="md-nav__link">
+      <a href="../navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/developer-guide/style-guide/index.html b/git-main/developer-guide/style-guide/index.html
index 196b278..2be6c4d 100644
--- a/git-main/developer-guide/style-guide/index.html
+++ b/git-main/developer-guide/style-guide/index.html
@@ -1262,7 +1262,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1272,7 +1272,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1283,11 +1283,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1304,7 +1304,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1325,7 +1325,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1346,7 +1346,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/index.html b/git-main/index.html
index 2458470..0f89a1b 100644
--- a/git-main/index.html
+++ b/git-main/index.html
@@ -1144,7 +1144,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1154,7 +1154,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1165,11 +1165,11 @@
   
   
     <li class="md-nav__item">
-      <a href="developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1186,7 +1186,7 @@
   
   
     <li class="md-nav__item">
-      <a href="developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1207,7 +1207,7 @@
   
   
     <li class="md-nav__item">
-      <a href="developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1228,7 +1228,7 @@
   
   
     <li class="md-nav__item">
-      <a href="developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/search/search_index.json b/git-main/search/search_index.json
index 1dc53cf..d3a77a2 100644
--- a/git-main/search/search_index.json
+++ b/git-main/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to ROSflight","text":"<p>The ROS2 updates for ROSflight are still under development. Please use with discretion.</p>"},{"location":"#what-is-rosflight","title":"What is ROSflight?","text":"<p>ROSflight is a lean and adaptable autopilot system designed from the ground up with researchers in mind. Its purpose is to enable researchers to quickly and easily try out new ideas with minimal effort. Some of ROSflight's key feature are:</p> <ul> <li>Lightweight, modular, and well documented code that is easy to understand and modify.</li> <li>Most of the autopilot exists on a Linux computer rather than a microcontroller, enabling easier development with increased capabilities.</li> <li>Seamless switching between simulation and hardware: no part of the autopilot knows if it is running in simulation or not.</li> <li>Built on a ROS2 framework, allowing easy integration with ROS2 based projects.</li> </ul> <p>See the user guide for more details on ROSflight.</p>"},{"location":"#why-rosflight","title":"Why ROSflight?","text":"<p>There are a lot of excellent autopilots out there with a lot of great firmware options. Why did we feel like the world needed ROSflight? Because in our experience none of the other available options satisfied our research needs. Existing autopilots commonly used by researchers tend to have massive codebases under constant development that run primarily on microcontrollers.</p> <p>This presents a number of problems. First, we are limited in our ability to understand and control everything occurring within the autonomy stack, making much of the autopilot an untouchable black box. Second, we are limited to the abilities of microcontrollers and can't take advantage of the more powerful hardware and software that can be found on Linux computers. Third, maintaining up-to-date support for software or hardware projects becomes a lot of work as things are frequently changing.</p> <p>ROSflight is intended to fix these problems by being a lightweight, modular, and well documented codebase that offloads as much as possible to a ROS2 based framework running on a Linux computer.</p>"},{"location":"#our-vision","title":"Our Vision","text":"<p>Perhaps more important than what we are trying to accomplish is what we are not trying to accomplish. ROSflight is not intended to be a fully-featured autopilot with all the same functions of other autopilots, but instead serve as a core foundation that can easily be adapted to any use case.</p> <p>Therefore, one of our primary objectives is to avoid feature creep and remain lean. We hope that others will extend our code and build on top of it, and would love to hear about your successes. But for the most part, we will not be incorporating these new features back into the main project. Instead, we hope that ROSflight will remain a lean, core code base that will continue to serve as a launch pad for exciting new projects and applications.</p>"},{"location":"developer-guide/contribution-guidelines/","title":"Contribution Guidelines","text":"<p>ROSflight is intended to be a streamlined, bare-bones autopilot. We welcome any bug fixes, cleanup, or other contributions which do not add complexity or detract from the readability and simplified nature of the project. In an attempt to avoid \"feature creep,\" we will be very discriminatory in merging pull requests whose purpose is to simply add features. Forking the repository in order to add features is totally acceptable and encouraged, just recognize us as the original authors of the autopilot (per the agreement in the BSD-3 license).</p> <p>In addition, we strive to maintain a very high standard of quality in terms of code style, variable naming, and the like. By maintaining a high standard, we hope that the code will continue to be useful, understandable, and cohesive in nature. Please don't be offended if we ask you to modify the formatting of your code before approving a pull request.</p> <p>Although we strive for complete in-code documentation, in practice this sometimes gets left behind for the sake of rapid development. If you, as a potential developer, find some portion of documentation unsatisfactory, we welcome questions on the appropriate GitHub issues page or forum, and encourage you to submit pull requests which improve documentation. Several new developers have started with first improving the documentation to get a handle on how things work.</p>"},{"location":"developer-guide/contribution-guidelines/#key-goals-of-rosflight","title":"Key Goals of ROSflight","text":"<p>Here is a summary of the key goals and philosophies behind ROSflight. As you look to make contributions to the project, keep these in mind.</p> <ul> <li> <p>Only include the things that most people will need. The goal of this would be to do most of the work so people can get a MAV in the air quickly and easily, but not overcomplicate the code with features that only a small portion of users would need.</p> </li> <li> <p>Be modular and adaptable for many research-centric use cases. This will be accomplished by putting the majority of the autopilot in a well-designed ROS2 framework. That which needs to be on the microcontroller will need to be done so carefully with good coding practices. Additionally, microcontroller code that is the most likely to be expanded upon should include clear interfaces and instructions for doing so.</p> </li> <li> <p>Keep everything simple and well documented. The key goal here is to minimize the amount of time and effort it takes someone to go from knowing nothing about ROSflight to being able to implement their own features and making meaningful progress with their research.</p> </li> </ul>"},{"location":"developer-guide/contribution-guidelines/#communication","title":"Communication","text":"<p>There are two channels to communicate with the developer team. For bug reports, feature requests, and anything to do with code, please open an issue on the appropriate GitHub issue page. For questions and other discussions, please use the forum.</p>"},{"location":"developer-guide/style-guide/","title":"Style Guide","text":"<p>The focus of anyone contributing to this project should be to write code that is easily understood by anyone, including people who have little experience with ROSflight or coding in general. So, we ask that contributions adhere to the following style guidelines.</p>"},{"location":"developer-guide/style-guide/#comments","title":"Comments","text":"<p>Well written and clear code should be easy to understand even without comments. However, since this project is intended to be as accessible as possible, we ask that you write both clear code and clear comments. Don't use comments to explain code that would be difficult to understand without comments, but instead use them to make clear code even more understandable.</p>"},{"location":"developer-guide/style-guide/#doxygen","title":"Doxygen","text":"<p>Doxygen comments should be added pretty much anywhere where it makes sense. Please include at least a brief for anything you write. For methods and functions, also include explanations of all arguments and the return value. More detailed explanations are encouraged for non-trivial methods and objects.</p>"},{"location":"developer-guide/style-guide/#white-space-and-line-endings","title":"White Space and Line Endings","text":"<p>Please try not to commit anything that only changes white space or line endings. To check if that's going to happen, run <code>git diff --check</code> before you stage your files.</p>"},{"location":"developer-guide/style-guide/#code-style","title":"Code Style","text":"<p>ROSflight follows the ROS2 C++ style guide, with some more specific guidelines below. Please follow first the style guidelines below and then the ROS2 guidelines. A .clang-format file and format-correcting script is provided in most ROSflight repositories that can be used to auto-format your code to help you find things you might have missed. Format checks on pull requests using this .clang-format file may also exist.</p>"},{"location":"developer-guide/style-guide/#indentation","title":"Indentation","text":"<p>Indentation should be 2 spaces (no tabs). Case statements in switch blocks should not be indented, e.g.</p> <pre><code>switch (variable)\n{\ncase 1:\n  // do something\n  break;\ndefault:\n  break;\n}\n</code></pre>"},{"location":"developer-guide/style-guide/#spaces","title":"Spaces","text":"<p>There should be a space between <code>if</code>, <code>for</code>, or <code>while</code> and the condition, e.g. <code>while (true)</code>, not <code>while(true)</code>.</p>"},{"location":"developer-guide/style-guide/#naming-conventions","title":"Naming Conventions","text":"<ul> <li>Class names should be capitalized with no spaces (i.e. <code>StateManager</code>).</li> <li>Member variables should contain a post-pended underscore (i.e. <code>data_</code>).</li> <li>Member functions should be all lower case with underscores (i.e. <code>set_error()</code>).</li> <li>Boolean values should be assigned <code>true</code> or <code>false</code>, not <code>0</code> or <code>1</code>.</li> </ul>"},{"location":"developer-guide/style-guide/#function-arguments","title":"Function Arguments","text":"<p>Primitive data types (<code>int</code>, <code>float</code>, etc.) should always be passed by value. Other types (e.g. classes) should be passed by reference and should maintain proper const-correctness. Arguments that are modified by the function should be passed by pointer instead of reference, to make the fact that the argument will be changed clearer in the calling code. For example:</p> <pre><code>void do_something(float dt, const MyClass&amp; data, int* output);\n</code></pre> <p>This function would be called as</p> <pre><code>float dt = 0.01f;\nMyClass my_class;\nint value;\n\ndo_something(dt, my_class, &amp;value);\n</code></pre> <p>This makes it clear the <code>value</code> is modified by the function call.</p>"},{"location":"developer-guide/style-guide/#classes","title":"Classes","text":"<p>All modules should be defined as a self-contained class. All member variables should be declared as \"private,\" named with a post-pended underscore, and accessed through inline accessor functions. All accessible data should be encapsulated in a struct. For example, here is a snippet from the <code>Sensors</code> module in the firmware:</p> <pre><code>class Sensors\n{\npublic:\n  struct Data\n  {\n    vector_t accel = {0, 0, 0};\n    vector_t gyro = {0, 0, 0};\n    float imu_temperature = 0;\n    uint64_t imu_time = 0;\n\n    float diff_pressure_velocity = 0;\n    float diff_pressure = 0;\n    float diff_pressure_temp = 0;\n    bool diff_pressure_valid = false;\n\n    float baro_altitude = 0;\n    float baro_pressure = 0;\n    float baro_temperature = 0;\n    bool baro_valid = false;\n\n    float sonar_range = 0;\n    bool sonar_range_valid = false;\n\n    vector_t mag = {0, 0, 0};\n\n    bool baro_present = false;\n    bool mag_present = false;\n    bool sonar_present = false;\n    bool diff_pressure_present = false;\n  };\n\n  Sensors(ROSflight&amp; rosflight);\n\n  inline const Data &amp; data() const { return data_; }\n\nprivate:\n  Data data_;\n}\n</code></pre> <p>Note that <code>data_</code> is a private member variable, but the <code>Data</code> struct is declared publicly and <code>data_</code> is accessed through an <code>inline const</code> accessor to prevent another module from changing <code>data_</code>.</p>"},{"location":"developer-guide/style-guide/#enums","title":"Enums","text":"<p>Enums should be declared using the following style: <pre><code>enum ArmedState\n{\n  ARMED_STATE_INIT,\n  ARMED_STATE_DISARMED,\n  ARMED_STATE_ARMED\n};\n</code></pre></p> <p>The name of the enum should be in CamelCase, and the names of its members should be ALL_CAPS. Where practical, have the members of the enum begin with the name of the enum.</p>"},{"location":"developer-guide/style-guide/#structs","title":"Structs","text":"<p>Structs should be declared using the following style: <pre><code>struct SomeValue\n{\n  int v1;\n  int v2;\n};\n</code></pre> Struct type names should be in CamelCase.</p>"},{"location":"developer-guide/style-guide/#globals","title":"Globals","text":"<p>The use of global variables should be limited to when absolutely necessary (such as linking to interrupt routines or hardware peripherals). This should only occur in board support layers and not in the core ROSflight libary code.</p>"},{"location":"developer-guide/style-guide/#include-order","title":"Include Order","text":"<p>Include files at the top of your file in the following order:</p> <ol> <li>Standard library (e.g. <code>&lt;cstdint&gt;</code>)</li> <li>Files from external libraries included in the project (e.g. <code>&lt;breezystm32/breezystm32.h&gt;</code>, <code>&lt;mavlink/v1.0/common/mavlink.h&gt;</code>)</li> <li>Other header files from this project (e.g. <code>\"rosflight.h\"</code>)</li> <li>The header file for this specific source file</li> </ol> <p>Group the includes according to the above list with an empty line between each group. (For external libraries, you may subdivide group 2 into a group for each library.) The first two groups should use angle brackets (<code>&lt;&gt;</code>), and the last two groups should use quotation marks (<code>\"\"</code>). Files from external libraries should be namespaced by the library name (e.g. <code>&lt;breezystm32/breezystm32.h&gt;</code>, not <code>&lt;breezystm32.h&gt;</code>).</p> <p>Alphabetize the files within each group. Do not change the include order to fix build errors; if you have to do that it means you are not including a file somewhere that you should. Please fix it by including all the right files.</p> <p>Include C standard library headers using the C++ style (<code>#include &lt;cmath&gt;</code>) instead of the C style (<code>#include &lt;math.h&gt;</code>).</p> <p>For example, in <code>sensors.c</code> I might have: <pre><code>#include &lt;cstdbool&gt;\n#include &lt;cstdint&gt;\n\n#include &lt;breezystm32/breezystm32.h&gt;\n#include &lt;breezystm32/drv_mpu6050.h&gt;\n\n#include \"param.h\"\n\n#include \"sensors.h\"\n</code></pre></p>"},{"location":"developer-guide/style-guide/#namespacing","title":"Namespacing","text":"<p>All modules should be encapsulated in a package namespace that is unique and consistent within the package (like <code>rosflight_firmware</code> for anything in the firmware package).</p>"},{"location":"developer-guide/firmware/building-and-flashing/","title":"Building and Flashing the Firmware","text":"<p>This guide assumes you are running Ubuntu 22.04 LTS, which is the currently supported development environment.</p>"},{"location":"developer-guide/firmware/building-and-flashing/#installing-the-arm-embedded-toolchain","title":"Installing the ARM Embedded Toolchain","text":"<pre><code>sudo apt install gcc-arm-none-eabi\n</code></pre> <p>You can test the installation and check which version is installed by running <code>arm-none-eabi-gcc --version</code>.</p>"},{"location":"developer-guide/firmware/building-and-flashing/#building-the-firmware-from-source","title":"Building the Firmware from Source","text":"<p>Now that we have the compiler installed, simply clone the ROSflight firmware repository, pull down the submodules, and build:</p> <pre><code>git clone --recursive https://github.com/rosflight/rosflight_firmware\ncd rosflight_firmware\nmkdir build \ncd build \ncmake .. -DBUILD_VARMINT=TRUE\nmake\n</code></pre>"},{"location":"developer-guide/firmware/building-and-flashing/#flashing-newly-built-firmware","title":"Flashing Newly-Built Firmware","text":"<p>TODO</p> <p>Update this when hardware support is finalized.</p> <p>First, make sure you have configured your computer as described in the Serial Port Configuration section of the user guide.</p>"},{"location":"developer-guide/firmware/building-and-flashing/#f4","title":"F4","text":"<p>Flash the firmware to the board by running <code>make BOARD=REVO flash</code>. If necessary, specify the serial port with <code>make BOARD=REVO SERIAL_DEVICE=/dev/ttyACM0 flash</code>.</p>"},{"location":"developer-guide/firmware/code-architecture/","title":"Code Architecture","text":"<p>The firmware is divided into two main components: the core library, and a collection of board implementations. This division is intended to allow the same core flight code to run on any processor or platform, either an embedded flight controller or a desktop environment for a software-in-the-loop (SIL) simulation. The interface between these two components is called the hardware abstraction layer (HAL). This architecture is illustrated in the following diagram:</p> <p></p>"},{"location":"developer-guide/firmware/code-architecture/#firmware-core-library","title":"Firmware Core Library","text":"<p>The firmware core library consists of all the code in the <code>include</code> and <code>src</code> directories of the firmware repository. This includes the code for what is termed the \"flight stack,\" which consists of the core components (such as the estimator, controller, state manager, etc.) required for flight. It also includes the interface definition for the hardware abstraction layer, which is defined by the abstract <code>Board</code> class in <code>include/board.h</code>. The communications link (MAVLink) is also abstracted, with the interface defined by the <code>CommLink</code> class in <code>include/comm_link.h</code>. External libraries are contained in the <code>lib</code> folder.</p>"},{"location":"developer-guide/firmware/code-architecture/#board-abstraction","title":"Board Abstraction","text":"<p>The hardware abstraction implementations are contained in the <code>boards</code> directory, organized in subdirectories according to the hardware driver layer. Each board implementation is required to provide an implementation of the hardware abstraction layer interface, which is passed by reference to the flight stack. The Varmint implementation in the <code>boards/varmint</code> shows how this is done for an embedded flight controller. Examples of board implementations for SIL simulation are found in the <code>rosflight_sim</code> ROS2 package available here.</p> <p>The flight stack is encapsulated in the <code>ROSflight</code> class defined at <code>include/rosflight.h</code>. This class contains two public functions: <code>init()</code> and <code>run()</code>. Its constructor requires two arguments: an implementation of the <code>Board</code> interface, and an implementation of the <code>CommLink</code> interface.</p> <p>Each board implementation is required to implement the entire Board class.</p>"},{"location":"developer-guide/firmware/code-architecture/#comm-link-abstraction","title":"Comm Link Abstraction","text":"<p>The purpose of the comm link abstraction layer is to allow communication protocols other than MAVLink to be used if desired. The comm link abstraction implementations are contained in the <code>comms</code> directory, organized in subdirectories by protocol. The implementations translate between the messages that the firmware expects to send and receive, and the messages defined by the communication protocol. Currently, only MAVLink is implemented.</p>"},{"location":"developer-guide/firmware/code-architecture/#flight-stack","title":"Flight Stack","text":"<p>The flight stack is encapsulated by the <code>ROSflight</code> class defined in <code>include/rosflight.h</code>. It consists of a collection of modules. Each of these modules is implemented as a C++ class, and encapsulates a cohesive piece of the autopilot functionality. The following diagram illustrates these modules and the data flow between them. Rectangular blocks represent modules in the flight stack, and ellipses represent hardware functionality implemented in the board support layer:</p> <p></p> <p>We'll describe each of these modules in the following sections:</p>"},{"location":"developer-guide/firmware/code-architecture/#state-manager","title":"State Manager","text":"<p>This module is in charge of keeping track of the internal state (armed status, error codes, failsafe, etc.) of the vehicle. While only the comm manager data flow is illustrated on the diagram, all other modules query the state manager to determine the status and act appropriately based on that status.</p> <p>The operation of the state manager is defined by the following finite state machine:</p> <p></p> <p>The state manager also includes functionality for recovering from hard faults. In the case of a hard fault, the firmware writes a small amount of data to backup memory then reboots. This backup memory location is checked and then cleared after every reboot. The backup memory includes the armed state of the flight controller. On reboot, the firmware will initialize then, if this armed-state flag is set, immediately transition back into the armed state. This functionality allows for continued RC control in the case of a hard fault. Hard faults are not expected with the stable firmware code base, but this feature adds an additional layer of safety if experimental changes are being made to the firmware itself.</p>"},{"location":"developer-guide/firmware/code-architecture/#parameter-server","title":"Parameter Server","text":"<p>This module handles all parameters for the flight stack. It supports the getting and setting of integer and floating-point parameters, and the saving of these parameters to non-volatile memory. Setting and getting of parameters from the companion computer is done through the serial communication interface. While no other data flow lines are shown on the diagram, all of the other modules interact with the parameter server.</p>"},{"location":"developer-guide/firmware/code-architecture/#comm-manager","title":"Comm Manager","text":"<p>This module handles all serial communication between the flight controller and companion computer. This includes streaming data and receiving offboard control setpoints and other commands from the computer. This module primarily collects data from the sensors, estimator, state manager, and parameters modules, and sends offboard control setpoints to the command manager and parameter requests to the parameter server.</p> <p>The actual communication protocol used is abstracted by the interface in include/comm_link.h. A new protocol can be used by implementing a wrapper around the protocol that inherits from this interface. Currently, only MAVLink has been implemented. The implementation is found in comms/mavlink/mavlink.h and comms/mavlink/mavlink.cpp.</p>"},{"location":"developer-guide/firmware/code-architecture/#sensors","title":"Sensors","text":"<p>This module is in charge of managing the various sensors (IMU, magnetometer, barometer, differential pressure sensor, sonar altimeter, etc.). Its responsibilities include updating sensor data at appropriate rates, and computing and applying calibration parameters.</p>"},{"location":"developer-guide/firmware/code-architecture/#estimator","title":"Estimator","text":"<p>This module is responsible for estimating the attitude and attitude rates of the vehicle from the sensor data.</p>"},{"location":"developer-guide/firmware/code-architecture/#rc","title":"RC","text":"<p>The RC module is responsible for interpreting the RC signals coming from the transmitter via the receiver. This includes mapping channels to their appropriate functions and reversing directions if necessary.</p>"},{"location":"developer-guide/firmware/code-architecture/#command-manager","title":"Command Manager","text":"<p>The command manager combines inputs from the RC and comm manager modules to produce a control setpoint. Its main purpose is to handle the interaction between offboard commands and the RC safety pilot, as well as to enforce the failsafe command if the state manager reports failsafe mode.</p>"},{"location":"developer-guide/firmware/code-architecture/#controller","title":"Controller","text":"<p>The controller uses the inputs from the command manager and estimator to compute a control output. This control output is computed in a generic form (x, y, and z torques, and force F), and is later converted into actual motor commands by the mixer.</p>"},{"location":"developer-guide/firmware/code-architecture/#mixer","title":"Mixer","text":"<p>The mixer takes the generic outputs computed by the controller and maps them to actual motor commands depending on the configuration of the vehicle.</p>"},{"location":"developer-guide/firmware/debugging/","title":"Using an In-Circuit Debugger","text":"<p>TODO</p> <p>Update this when hardware support is finalized.</p> <p>Debugging an STM32-based board is accomplished with an ST-LINK/V2 in-circuit debugger and programmer. We have had the best luck with the official version from STMicroelectronics. These devices are reasonably priced, and are available directly from STMicroelectronics or from vendors such as Digi-Key, Mouser, and Newark.</p> <p>The following guide will show you how to get the in-circuit debugger running with either the Visual Studio Code or QtCreator IDE. Start with the steps in the General Setup section, then move on to either the VS Code or STM32cubeIDE sections depending on your choice of IDE.</p> <p>This guide assumes you are running Ubuntu 22.04 LTS, which is the currently supported development environment.</p>"},{"location":"developer-guide/firmware/debugging/#general-setup","title":"General Setup","text":"<p>Follow the guide in Building and Flashing to install the compiler toolchain.</p> <p>Also make sure you have configured your computer as described in the Serial Port Configuration section of the user guide.</p>"},{"location":"developer-guide/firmware/debugging/#connect-debugger-to-flight-controller","title":"Connect debugger to flight controller","text":"<p>The ST-LINK/V2 connects to the microcontroller using the Serial Wire Debug (SWD) interface. You will need to connect the <code>GND</code>, <code>NRST</code>, <code>SWDIO</code>, and <code>SWCLK</code> lines of the ST-LINK/V2 to your flight controller. On many F4 boards, these lines are pinned out through a 4-position JST SH connector, although that connector is not always populated. Refer to the documentation for your specific board for details.</p> <p>The official ST-LINK/V2 also needs a target voltage reference on pin 1 or 2, which for the F4 boards is 3.3V. However, there is no externally accessible 3.3V pinout on the F4 boards. An easy solution to this is to connect pin 19 (VDD 3.3V) of the ST-LINK/V2 to pin 1 or 2 of the ST-LINK/V2 (Target VCC) to provide the voltage reference. You will also need to power the board from another source, either through the USB port or over the servo rail. Note that this connection is not required for the cheap clone versions of the ST-LINK/V2.</p>"},{"location":"developer-guide/firmware/debugging/#vs-code","title":"VS Code","text":"<p>You can install Visual Studio Code by downloading the latest version from their website. Follow the steps below to configure debugging with the in-circuit debugger.</p> <p>You should open the root firmware directory for editing and debugging, e.g. <code>code /path/to/rosflight_firmware</code>.</p>"},{"location":"developer-guide/firmware/debugging/#install-openocd","title":"Install OpenOCD","text":"<p>OpenOCD (On-Chip Debugger) is the software that will control the debugger. Install from the <code>apt</code> repositories:</p> <pre><code>sudo apt install openocd\n</code></pre>"},{"location":"developer-guide/firmware/debugging/#install-cortex-debug-extension","title":"Install Cortex-Debug extension","text":"<p>The embedded debugging functionality is provided by the <code>Cortex-Debug</code> extension. Install using the VS Code GUI, or from VS Code press <code>Ctrl+P</code> then type <code>ext install marus25.cortex-debug</code>.</p> <p>Steps for configuring this extension are described next.</p>"},{"location":"developer-guide/firmware/debugging/#download-svd-file","title":"Download SVD file","text":"<p>A System View Description (SVD) file describes the configuration (CPU, peripherals, registers, etc.) of the microcontroller. The Cortex-Debug extension can make use of an SVD file to provide more detailed debugging information, such as the ability to inspect register values.</p> <p>SVD files can be downloaded from STMicroelectronics. The files for the F4 are contained in the ZIP file that can be downloaded here, and the relevant file is <code>STM32F405.svd</code>. The files for the F1 are contained in the ZIP file that can be downloaded here, and the relevant file is <code>STM32F103.svd</code>. Put those files in a convenient location.</p>"},{"location":"developer-guide/firmware/debugging/#configure-build-step","title":"Configure build step","text":"<p>You can configure VS Code to run <code>make</code> for you when you press <code>Ctrl+Shift+B</code>. To do this, put the following in <code>.vscode/tasks.json</code> inside your firmware working directory:</p> <pre><code>{\n  // See https://go.microsoft.com/fwlink/?LinkId=733558\n  // for the documentation about the tasks.json format\n  \"version\": \"2.0.0\",\n  \"tasks\": [\n    {\n      \"type\": \"shell\",\n      \"label\": \"make\",\n      \"command\": \"make\",\n      \"args\": [\"DEBUG=GDB\"],\n      \"group\": {\n        \"kind\": \"build\",\n        \"isDefault\": true\n      }\n    }\n  ]\n}\n</code></pre> <p>Note that by default, this will only build the F4 (Revo) firmware. To build the F1 firmware, you will need to edit this to add the argument <code>BOARD=NAZE</code>.</p>"},{"location":"developer-guide/firmware/debugging/#configure-debugging","title":"Configure debugging","text":"<p>To configure in-circuit debugging of F4 and F1 targets, put something like the following in <code>.vscode/launch.json</code> inside your firmware working repository:</p> <pre><code>{\n  // Use IntelliSense to learn about possible attributes.\n  // Hover to view descriptions of existing attributes.\n  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387\n  \"version\": \"0.2.0\",\n  \"configurations\": [\n    {\n      \"name\": \"STM32F405\",\n      \"type\": \"cortex-debug\",\n      \"request\": \"launch\",\n      \"servertype\": \"openocd\",\n      \"cwd\": \"${workspaceRoot}\",\n      \"executable\": \"${workspaceRoot}/boards/airbourne/build/rosflight_REVO_Debug.elf\",\n      \"device\": \"STM32F405\",\n      \"svdFile\": \"/path/to/STM32F405.svd\",\n      \"configFiles\": [\n        \"interface/stlink-v2.cfg\",\n        \"target/stm32f4x.cfg\"\n      ],\n      \"runToMain\": true\n    },\n    {\n      \"name\": \"STM32F103\",\n      \"type\": \"cortex-debug\",\n      \"request\": \"launch\",\n      \"servertype\": \"openocd\",\n      \"cwd\": \"${workspaceRoot}\",\n      \"executable\": \"${workspaceRoot}/boards/breezy/build/rosflight_NAZE_Debug.elf\",\n      \"device\": \"STM32F103\",\n      \"svdFile\": \"/path/to/STM32F103.svd\",\n      \"configFiles\": [\n        \"interface/stlink-v2.cfg\",\n        \"target/stm32f1x.cfg\"\n      ],\n      \"runToMain\": true\n    }\n  ]\n}\n</code></pre> <p>Be sure to edit the values of <code>\"svdFile\"</code> to point to the respective SVD files you downloaded earlier.</p> <p>To start debugging, enter the debug pane in VS Code, select the desired configuration, then click the green arrow to start debugging. The shortcut key <code>F5</code> will also launch the last-selected debug configuration.</p> <p>More details on the configuration and use of the <code>Cortex-Debug</code> extension can be found here and here.</p>"},{"location":"developer-guide/firmware/debugging/#stm32cubeide","title":"STM32cubeIDE","text":""},{"location":"developer-guide/firmware/unit-tests/","title":"Building and Running Unit Tests","text":"<p>Contributions will need to pass our continuous integration unit tests before merging. To test your contributions against these tests, you'll first need to install Eigen and gtest:</p> <pre><code>sudo apt install build-essential libgtest-dev libeigen3-dev cmake\n</code></pre>"},{"location":"developer-guide/firmware/unit-tests/#compile-gtest","title":"Compile gtest","text":"<p>You just downloaded a bunch of source files, which you now have to go build</p> <pre><code>cd /usr/src/gtest\nsudo cmake CMakeLists.txt\nsudo make\n</code></pre> <p>Copy the archive files you just built to the <code>/usr/lib</code> directory so CMake can find them later:</p> <pre><code>sudo cp ./lib/libgtest*.a /usr/lib\n</code></pre>"},{"location":"developer-guide/firmware/unit-tests/#run-the-test-script","title":"Run the Test Script","text":"<p>The simplest way to run the unit tests is to use the testing script. This script first checks that the firmware compiles, then runs the unit tests. This is the same script used on the continuous integration server, so this is a great way to check that your code will pass the tests before opening a pull request. Run the test script with</p> <pre><code>cd &lt;firmware_directory&gt;\n./scripts/run_tests.sh\n</code></pre>"},{"location":"developer-guide/firmware/unit-tests/#manually-build-and-run-the-unit-tests","title":"Manually Build and Run the Unit Tests","text":"<p>If you want to manually build and run the unit tests, first build them with the following commands:</p> <pre><code>cd &lt;firmware_directory&gt;\nmkdir build\ncd build\ncmake .. -DBUILD_TEST=TRUE\nmake\n</code></pre> <p>Then run them with:</p> <pre><code>./test/unit_tests\n</code></pre>"},{"location":"developer-guide/rosplane/parameter-management/","title":"Parameter Management","text":""},{"location":"developer-guide/rosplane/parameter-management/#overview","title":"Overview","text":"<p>In ROSplane, all internal variables are represented as ROS2 parameters. This enables easy loading, tuning, and saving parameters of various ROSplane modules without needing to rebuild. ROS2 parameters can also be changed dynamically, enabling live editing and tuning of the system. </p> <p>For a good introduction to ROS2 parameters and the CLI tools, see the ROS2 parameter CLI documentation. For an introduction to the parameter system using the ROS2 client libraries, see ROS2 parameter client libraries documentation.</p>"},{"location":"developer-guide/rosplane/parameter-management/#parameter-manager-class","title":"Parameter Manager class","text":"<p>A <code>param_manager</code> class has been created to manage the ROS interface required when dealing with parameters. Specifically, a <code>param_manager</code> object handles the declaration and updates of parameters. Since a base class publicly owns the <code>param_manager</code>, derived classes will have access to any parent class's parameters, if needed. This also allows derived classes to define parameters close to where they will be used in the derived class, helping with readability.</p> <p>For example, the <code>controller_base</code> class declares a <code>frequency</code> variable, which defines the rate of the control loops. This same parameter is needed in other derived classes, like the <code>controller_successive_loop</code> class. Since we declare the parameter in the <code>controller_base</code> class, the <code>controller_successive_loop</code> class will have access to the <code>frequency</code> parameter without having to redefine it.</p>"},{"location":"developer-guide/rosplane/parameter-management/#usage","title":"Usage","text":""},{"location":"developer-guide/rosplane/parameter-management/#declaration","title":"Declaration","text":"<p>To use the <code>param_manager</code> to define your own parameters, do the following:</p> <ol> <li>Declare an instance of <code>param_manager</code> in your class, or ensure that a parent class has a public or protected instance of <code>param_manager</code>.</li> <li>Initialize the <code>param_manager</code> object with a pointer to the ROS2 node object associated with the parameters.</li> <li>In the constructor, use <code>param_manager::declare_param(std::string &lt;PARAM_NAME&gt;, &lt;PARAM&gt;)</code> to declare parameters of type double, bool, or string, where <code>&lt;PARAM&gt;</code> is the default value for the parameter.<ul> <li>Use <code>param_manager::declare_int(std::string &lt;PARAM_NAME&gt;, &lt;PARAM&gt;)</code> to declare an integer parameter.</li> </ul> </li> <li>In the constructor, use <code>param_manager::set_parameters()</code> to load any parameters that have changed on launch to the <code>param_manager</code> object.</li> </ol> <p>Note</p> <p>The <code>param_manager::set_parameters()</code> call is important when a node is loaded with parameters from a file on launch. Not making this call will mean that the parameters stored in the <code>param_manager</code> object are out of sync with the ROS2 parameters.</p> <p>These steps will register your parameters with ROS2, allowing you to change them dynamically or load them from a launch file.</p>"},{"location":"developer-guide/rosplane/parameter-management/#using-parameters-in-code","title":"Using parameters in code","text":"<p>After declaring the parameters with <code>param_manager::declare_param</code> or <code>param_manager::declare_int</code>, you need to allocate variables in your code to hold the values of the parameters. Get the parameter value by using the appropriate function call:</p> <ul> <li><code>param_manager::get_double(std::string &lt;PARAM_NAME&gt;)</code></li> <li><code>param_manager::get_bool(std::string &lt;PARAM_NAME&gt;)</code></li> <li><code>param_manager::get_string(std::string &lt;PARAM_NAME&gt;)</code></li> <li><code>param_manager::get_int(std::string &lt;PARAM_NAME&gt;)</code></li> </ul> <p>Note that the return type of <code>param_manager::get_int</code> is <code>int_64</code>, since that is how ROS2 internally stores integers.</p>"},{"location":"developer-guide/rosplane/parameter-management/#defining-parameters-with-a-parameter-file","title":"Defining parameters with a parameter file","text":"<p>We recommend using a YAML file to hold all of the parameters for a given node. This file can be loaded at launch time so that all parameters are updated with the values in the launch file. This means you don't have to change the default values in code (which would require a rebuild) to make sure a node gets launched with the correct values.</p> <p>To do this, add the <code>parameters=[\"/path/to/parameter/file\"]</code> to a node's launch argument. See <code>rosplane.launch.py</code> for an example.</p>"},{"location":"developer-guide/rosplane/parameter-management/#updating-parameters","title":"Updating Parameters","text":"<p>Parameters can be updated from the command line using normal ROS2 commands. See the ROS2 parameter CLI tools documentation for more information on how to interface with these parameters from the command line.</p> <p>Note</p> <p>Be sure to create a callback for your parameter changes, especially if you use a <code>param_manager</code> object. ROS2 will send a list of changed parameters to this callback when the parameters are changed, allowing you to update the internally stored value in the <code>param_manager</code>. Otherwise, your internally stored values will be out of sync with the ROS2 parameters, and it will likely not function correctly. See the <code>controller_base</code> or <code>estimator_base</code> or <code>path_planner</code> code for an example of the callbacks.</p>"},{"location":"developer-guide/rosplane/controller/controller-base/","title":"Controller Base","text":""},{"location":"developer-guide/rosplane/controller/controller-base/#overview","title":"Overview","text":"<p>The controller base implements the basic ROS interfaces for the controller. This includes setting up subscribers, publishers and initializing parameter management. The idea of the base class, is that all interfacing with ROS and shared resources across all inheritance levels happens or are contained in this class.</p>"},{"location":"developer-guide/rosplane/controller/controller-base/#ros-interfaces","title":"ROS interfaces","text":"<p>The controller base has the following ROS interactions.</p> Figure 1: Controller's ROS interactions. <p>The controller has four ROS interfaces that are tracked as member variables of the class. These interfaces are the only points of contact that influence the every layer of the controller along side the node parameters. Each of the callbacks for the subscribers are also contained in <code>controller_base</code>.</p> ROS Interface Topic Explanation Message Type <code>actuators_pub_</code> <code>/command</code> Publishes the acutator commands for the aircraft. The publishing rate is controller by the <code>timer_</code> object. Command.msg <code>internals_pub_</code> <code>/controller_inners_debug</code> Publishes the intermediate values created by the outer control loops. Published simultaneously as the commands when there is at least one subscriber to the topic. ControllerInnersDebug.msg <code>controller_commands_sub_</code> <code>/controller_commands</code> Subscribes to the commands for the controller. ControllerCommands.msg <code>vehicle_state_sub_</code> <code>/estimated_state</code> Subscribes to the estimated state of the aircraft. State.msg <p>Note</p> <p>The command message is from the <code>rosflight_msgs</code> package not the <code>rosplane_msgs</code> package.</p>"},{"location":"developer-guide/rosplane/controller/controller-base/#parameter-management","title":"Parameter Management","text":"<p>See the Parameter Management page for more details on how parameter management works.</p>"},{"location":"developer-guide/rosplane/controller/controller-base/#list-of-parameters","title":"List of Parameters","text":"Parameter Explanation Range pwm_rad_e Radian to PWM conversion for the elevator. \\geq 1.0 (double) pwm_rad_a Radian to PWM conversion for the ailerons. \\geq 1.0 (double) pwm_rad_r Radian to PWM conversion for the rudder. \\geq 1.0 (double) frequency Frequency of the timer, effective control loop closure frequency. \\geq 100 (hertz, int)"},{"location":"developer-guide/rosplane/controller/controller-base/#modifying-controller-base","title":"Modifying Controller Base","text":"<p>The <code>controller_base</code> class should only contain things that are necessary for each layer of the controller. If you are considering adding something to the controller, but it only applies to one layer, perhaps reconsider. All ROS related items should also be stored here. For example, if you needed to use another topic subscription, the new subscriber should be created and stored in <code>controller_base</code>.</p> <p>As shown in the Controller Software Architecture page, you may need to modify the <code>main</code> function in <code>controller_base.cpp</code> to use a newly implemented controller.</p>"},{"location":"developer-guide/rosplane/controller/controller-general-overview/","title":"ROSplane Controller","text":""},{"location":"developer-guide/rosplane/controller/controller-general-overview/#overview","title":"Overview","text":"<p>The ROSplane controller generates the controller commands to achieve the commanded states that the path follower directs. The controller has the basic function of controlling roll, pitch, yaw, airspeed, course and altitude. Higher functions of controlling position and tracking paths is handled by other nodes, the path follower and manager specifically. To gain the best understanding of the Controller and its role, read chapter 1 of the UAV book, or the ROSplane Overview page.</p>"},{"location":"developer-guide/rosplane/controller/controller-general-overview/#interfaces","title":"Interfaces","text":"Figure 1: Controller's ROS interactions."},{"location":"developer-guide/rosplane/controller/controller-general-overview/#input","title":"Input","text":"<p>The controller receives controller commands using the ControllerCommands message on the <code>\\controller_commands</code> topic from the <code>path_follower</code> node.  This set of commands are outlined below, along with a short explanation of each.</p> Message Field Explanation Units header This contains time stamp information. Time in Seconds and Nanoseconds (int) va_c The commanded airspeed. Meters per second (float) h_c The commanded altitude. Meters (float) chi_c The commanded course. Radians (float) phi_ff Feedforward roll term (for orbits) Radians (float) aux[4] Four array of auxiliary commands None (float) aux_valid Indicates whether aux vector contains actual information. True/False (bool) <p>The controller uses these targets to control the aircraft. This drives the aircraft to approach and follow the path as the path_follower commands. See the Path Follower page for more information. See the Successive Loop Closure Controller Outline for more information on how these commands are used specifically.</p> <p>Note</p> <p>Poor path performance may be due to controller or the path follower, see the Tuning Guide in the User Guide section for more details.</p>"},{"location":"developer-guide/rosplane/controller/controller-general-overview/#output","title":"Output","text":"<p>The controller calculates the control surface outputs in percent deflection (based around zero) and throttle. It formats and the publishes these outputs in the Command message on the <code>/command</code> topic. There are a further four auxiliary channels that can be used in the Command message, however they are unused typically. A summary of the parts of the command message are as follows.</p> Message Field Explanation Units header This contains time stamp information. Time in Seconds and Nanoseconds (int) mode The control mode (used in multi-rotors) None (int) ignore A bitmask to ignore particular values. None (int) x Aileron Command Percent deflection in direction [-1.0, 1.0] (float) y Elevator Command Percent deflection in direction [-1.0, 1.0] (float) z Rudder Command Percent deflection in direction [-1.0, 1.0] (float) f Throttle Command Percent of full throttle [0.0, 1.0] (float) <p>These are passed to <code>rosflight_io</code>, which formats them into MAVLink messages and forwards them onto the FCU.</p> <p>Note</p> <p>For this to work the parameters on the <code>rosflight_firmware</code> must be set to work for an airplane. See the User Guide on first time start up or README.md for the repository for more details on firmware setup.</p>"},{"location":"developer-guide/rosplane/controller/controller-general-overview/#running-the-controller","title":"Running the Controller","text":"<p>As mentioned in the ROSplane ROS overview, the controller is in the main <code>rosplane</code> ROS package. The ROS executable is <code>rosplane_controller</code>, yielding the run command:</p> <p><code>ros2 run rosplane rosplane_controller</code></p> <p>The type of controller used is passed right after the executable name, substitute <code>control_type</code> for controller being used.</p> <p><code>ros2 run rosplane rosplane_controller control_type</code></p> <p>To pass a set of parameters for the controller from a yaml file using the <code>--ros-args</code> option.</p> <p><code>ros2 run rosplane rosplane_controller --ros-args --params-file path/to/params.yaml</code></p> <p>Putting it all together,</p> <p><code>ros2 run rosplane rosplane_controller control_type --ros-args --params-file path/to/params.yaml</code></p> <p>A table of arguments and parameter files that work out of the box is given in the following table.</p> <p>Note</p> <p>Filepaths will need to be altered to work.</p> <p>Note</p> <p>The most common way of running the controller is in through a launch file with the rest of the ROSplane pipeline running as well. See the ROSplane Overview in the Developer and User Guides for more details.</p> Argument Explanation Values --params-file The parameters file that contains the gains and other important parameters. <code>rosflight_ws/src/rosplane/rosplane/params/anaconda_autopilot_params.yaml</code>,<code>rosflight_ws/src/rosplane/rosplane/params/skyhunter_autopilot_params.yaml</code> control_type These arguements are passed directly to the main function defined in the controller. <code>default</code>, <code>total_energy</code>"},{"location":"developer-guide/rosplane/controller/controller-outline/","title":"Successive Loop Closure Controller","text":""},{"location":"developer-guide/rosplane/controller/controller-outline/#overview","title":"Overview","text":"<p>The control scheme used by default in ROSplane comes from the book Small Unmannded Aircraft: Theory and Practice by Randal Beard and Timothy McLain. A full and in depth description of the theory behind this controller is outlined in chapter 6. Additionally, many simplifing assumptions are made some of which will be mentioned, but the rationale not explored. These too are found in the book, in chapters 3, 4 and 5. A link to the most up to date book can be found on the GitHub page for the book. This section of the documentation is to briefly outline the important, practical parts of the controller to be useful in understanding how to tune or modify the existing code or algorithm for a developer. A good primer on PID control can be found here.</p> <p>The control algortihm is split into two parts: Lateral-directional Autopilot and Longitudinal Autopilot. The lateral and longitudinal dynamics are assumed to be decoupled as discussed in Section 6.1 of Small Unmannded Aircraft. This allows us to develop a controller for each set of dynamics to simplify the controller design.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#successive-loop-closure","title":"Successive Loop Closure","text":"<p>For a full discussion of PID successive loop closure, which is used heavily through out the entire controller, read section 6.1 in the book. One major assumption used is that the inner loops are much faster (more than ten times faster) than the outer loops. This means that the bandwidth seperation should be seperated by a factor of 10. See end of section 6.1.1 Course Hold using Commanded Roll in the book for a more thorough discussion. A significant advantage of successive loop closure is that gains are tuned independently. Starting from the inner loops, tune the response and then tune the outer loop.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#nomenclature","title":"Nomenclature","text":"Symbol Meaning Range \\large{\\boldsymbol{\\chi}} Course/Heading [-\\pi,\\pi) \\large{\\boldsymbol{\\phi}} Roll [-\\pi,\\pi) \\large{\\boldsymbol{\\theta}} Theta [-\\pi,\\pi) \\large{\\boldsymbol{\\psi}} Yaw [-\\pi,\\pi) \\large{\\boldsymbol{h}} Altitude \\large{p} Roll Rate \\large{q} Pitch Rate \\large{r} Yaw Rate \\large{V_a} Airspeed \\large{\\boldsymbol{\\delta_i}} Command percent defelection of control surface i [-1.0,1.0] \\large{\\boldsymbol{e_a}} Error in state variable a \\large{\\boldsymbol{a^c}} Commanded value of state variable a \\large{\\boldsymbol{k_{p_{a}}}} Proportional gain for state variable a \\large{\\boldsymbol{k_{d_{a}}}} Derivative gain for state variable a \\large{\\boldsymbol{k_{i_{a}}}} Integral gain for state variable a \\large{\\boldsymbol{p_{wo}}} Washout filter bandwidth \\large{\\boldsymbol{P}} Plant transfer function \\large{\\boldsymbol{s}} Laplace operator"},{"location":"developer-guide/rosplane/controller/controller-outline/#lateral-directional-autopilot","title":"Lateral-directional Autopilot","text":"<p>The autopilot uses induced roll to control changes in course. The Lateral-directional Autopilot also uses a yaw damper to damp the dutch roll mode that can be induced by changes in roll.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#course-loop","title":"Course Loop","text":"<p>In figure 1, the entire control loop for the course is shown. This loop allows for tracking of ramp and step commands in course. Since the inner loop is tuned first and influences the outer loop tune, we will discuss it first.</p> Figure 1: Lateral-directional Autopilot Control Loop"},{"location":"developer-guide/rosplane/controller/controller-outline/#inner-loop","title":"Inner Loop","text":"<p>The inner loop calculates the required percent deflection in the ailerons, \\boldsymbol{\\delta_a}, to acheive the commanded roll angle generated by the outer loop. This loop is a PD loop, meaning that it uses only a proportional and derivative control.</p> <p>Note</p> <p>That the derivative gain does not act on the rate of change of the error but of the direct roll rate, p.</p> <p>The proportional gain acts on the error given by the estimated roll and the commanded roll. This loop does not use integral contol to ensure that it closes much faster than the outer loop. This bandwidth seperation helps the controller perform smoothly. See the specific page on the Course Loop for details on tuning and common pitfalls. For more details on how the roll rate and the roll angle are calculated, see the Estimator page. The output for the inner loop is routed into the outer loop.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#outer-loop","title":"Outer Loop","text":"<p>The outer loop calculates the commanded roll angle, \\boldsymbol{\\phi}, based on the error in the course, \\boldsymbol{\\chi}. This is a PI loop, meaning that it uses only proportional and integral control. The proportional gain acts on the error between the estimated course \\boldsymbol{\\chi} and the commanded course \\boldsymbol{\\chi}. The integral gain acts on the same error, ensuring that errors in course are driven to zero.</p> <p>Note</p> <p>The PI loop allows for only constant error in ramp inputs (orbits) and for no error to step inputs (path following commands).</p> <p>See the specific page on the Course Loop for details on tuning and common pitfalls. For more details on how course is estimated and measured, see the Estimator page. These loops combine to give complete control of the course of the aircraft.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#yaw-damper","title":"Yaw Damper","text":"<p>The yaw damper allows for effective damping of undesirable yaw modes induced by rolling. This is done by using the rudder to control the yaw rate, r, to zero. Not all yaw rates should be controlled to zero since this would disallow turning. A washout filter is used to only damp high frequency yaw rates. In effect, this control only 'turns on' if the frequency of the yaw rate is high enough. For mor information see the Yaw Damper page.</p> Figure 2: Yaw Damper Control Loop"},{"location":"developer-guide/rosplane/controller/controller-outline/#longitudinal-autopilot","title":"Longitudinal Autopilot","text":"<p>The longitudinal autopilot controls the longitudinal dynamics of the aircraft. This means that the loop controls altitude, pitch and airspeed.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#altitude-loop","title":"Altitude Loop","text":"<p>The altitude loop utilizes successive loop closure to control altitude. It uses the elevator to control the pitch of the aircraft, and then controls using commanded pitch the altitude. This loop can track step and ramp commands.</p> Figure 3: Altitude Control Loop"},{"location":"developer-guide/rosplane/controller/controller-outline/#inner-loop_1","title":"Inner Loop","text":"<p>The inner loop controls the pitch, \\boldsymbol{\\theta}. It does so by calculating the necessary \\boldsymbol{\\delta_e} to acheive the commanded pitch. This is a PD loop, this means that there is often a small DC offset to the commanded pitch. This does not affect the performance of the overall altitude loop. Like the inner loop of the course control, the derivative gain acts on the measured pitch rate rather than the error derivative.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#outer-loop_1","title":"Outer Loop","text":"<p>The outer loop is a PI loop. It uses the error in the altitude, h, and integral of the error of altitude to drive the error to zero for steps and for ramps. The commanded altitude is capped using a scheme described in the Altitude Loop page. In practice, the altitude loop is often slower when the commanded altitude is descending and faster when ascending. This is because the airspeed is coupled to the altitude. While descending the controller will attempt to maintain airspeed. This can also result in more overshoot while descending.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#airspeed-loop","title":"Airspeed Loop","text":"<p>The Airspeed loop is a PI loop. It reacts to the straight forward error in commanded airspeed V_a^c given by the waypoint mission. It generates the required throttle, \\delta_t, to acheive the commanded airspeed. This is suffecient because of the natural damping of the drag on the aircraft. In practice, the loop performs well, but is prone to small fluctuations (on the order of \\pm 1 \\frac{m}{s}) due to the differential pressure sensor fluctuating because of wind and other disturbances.</p> Figure 4: Airspeed using throttle control loop"},{"location":"developer-guide/rosplane/controller/controller-outline/#controller-outputs","title":"Controller Outputs","text":"<p>What the entire controller outputs is a set of 4 control efforts that correspond to the 4 major control surfaces on the aircraft. These are the elevator, ailerons, rudder and the throttle. The controller can easily be switched to outputing up to 8 outputs, using the aux channels of the Commands Message. These outputs are fed directly to rosflight_io and then passed along to the microcontroller and finally actuated on the physical or simulated aircraft. The controller is the exposed portion of ROSplane to ROSflight.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#important-notes","title":"Important Notes","text":"<p>The controller does not directly control the position. In the ROSplane overview page, it shows how the Path Follower feeds into the controller. The Path Follwer generates commands that result in the position control of the aircraft. For a better understanding of this realtionship visit the Path Follower page.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#software-architecture","title":"Software Architecture","text":"<p>The Successive Loop Closure Controller (SLCC) inherits from the state machine class, (see Software Architecture for more details) and implements the state function for each of the states. This state function is then populated with the desired control during each phase of flight (see State Machine for more details on control during each state). The state functions split control into longitudinal and lateral control, this allows for inheritance of this class an only override longitudinal or lateral control (see Total Energy Control for an example of how this is done).</p> Figure 5: An example of an implementation of a state function, in this case the altitude hold state. <p>The lateral and longitudinal control functions activate particular control loops necessary.</p> Figure 6: An example of an implementation of a lateral and longitudinal control, in this case during the altitude hold state. <p>Each control loop gets its own function and it follows a specific format. This format is pictured below, but a full outline is given in the .cpp file for the SLCC.</p> <p>Note</p> <p>All of the PID is implemented but the gains if not using a particular control (proportional/derivative/integral) are zero.</p> Figure 7: An example of an implementation of a control loop, in this case the roll loop (inner course loop)."},{"location":"developer-guide/rosplane/controller/controller-outline/#parameters","title":"Parameters","text":"<p>These values are typically held in a .yaml file. For the default values, check the .cpp file.</p> Parameter Explanation Range max_takeoff_throttle Trottle saturation level during the takeoff zone. (0.0, 1.0) (double) c_kp The proportional gain on the outer course loop. \\geq 0.0 (double) c_kd The derivative gain on the outer course loop. \\leq 0.0 (double) c_ki The integral gain on the outer course loop. \\geq 0.0 (double) max_roll Commanded roll saturation limit. \\geq 0.0 (double)(degrees) cmd_takeoff_pitch Commanded pitch while in takeoff state. \\geq 0.0 (double)(degrees) r_kp The proportional gain on the inner course loop. \\geq 0.0 (double) r_kd The derivative gain on the inner course loop. \\geq 0.0 (double) r_ki The integral gain on the inner course loop. \\geq 0.0 (double) max_a Saturation limit for the ailerons \\geq 0.0 (double) trim_a Trim value for the ailerons. \\geq 0.0 (double) a_kp The proportional gain on the outer altitude loop. \\geq 0.0 (double) a_kd The derivative gain on the outer altitude loop. \\geq 0.0 (double) a_ki The integral gain on the outer altitude loop. \\geq 0.0 (double) max_pitch Commanded pitch saturation limit. \\geq 0.0 (double)(degrees) p_kp The proportional gain on the inner altitude loop. \\leq 0.0 (double) p_kd The derivative gain on the inner altitude loop. \\leq 0.0 (double) p_ki The integral gain on the inner altitude loop. \\leq 0.0 (double) max_e Saturation limit for the elevator \\geq 0.0 (double) trim_e Trim value for the elevator. \\geq 0.0 (double) y_pwo The yaw damper washout filter cutoff frequency. \\leq 0.0 (double)(radians/s) y_kr Control gain on yaw damper. \\leq 0.0 (double) a_t_kp The proportional gain on the airspeed loop. \\geq 0.0 (double) a_t_kd The derivative gain on the airspeed loop. \\geq 0.0 (double) a_t_ki The integral gain on the airspeed loop. \\geq 0.0 (double) max_t Saturation limit for the throttle. \\geq 0.0 (double) trim_t Trim value for the throttle. \\geq 0.0 (double) tau Dirty derivative low pass filter gain for airspeed. \\geq 0.0 (double)"},{"location":"developer-guide/rosplane/controller/controller-software-architecture/","title":"Controller Software Architecture","text":""},{"location":"developer-guide/rosplane/controller/controller-software-architecture/#overview","title":"Overview","text":"<p>The controller makes use of inheritance to make the controller more modular. This creates a hierarchy of classes that each take on a responsibility. This means that a user that modifies the controller only has to inherit from a particular class make the modifications only to the portions of the code that matter to them, and then continue to use the other parts of the controller. An example of this is provided in the code. The total energy controller exemplifies this by inheriting and only changing just a few key functions. The aim of this architecture is to make the developer's job easier.</p>"},{"location":"developer-guide/rosplane/controller/controller-software-architecture/#inheritance-scheme","title":"Inheritance Scheme","text":"<p>The controller starts off with the <code>controller_base</code> class. This contains all of the interface with ROS. The next layer, <code>controller_state_machine</code>, implements a basic state machine for the controller. These states control which commands are happening at what time. An example of how this may be used is, ensuring the aircraft is at altitude before attempting major maneuvers. Following the state machine is the actual control scheme. By default we use a successive loop closure scheme, <code>controller_successive_loop</code>. This layer calculates the control errors and necessary actuator deflections to track commands.</p> <p> Figure 1: Controller class inheritance structure. <p></p> <p>This scheme was chosen to limit code duplication. A composition structure would have resulted in code duplication between controllers. Guides on how and where to modify each part of this structure can be found on the respective pages in the Developer Guide. This page does go over the basics of how to implement a controller changes in terms of overall architecture.</p>"},{"location":"developer-guide/rosplane/controller/controller-software-architecture/#implementing-a-new-controller","title":"Implementing A New Controller","text":"Figure 2: Options for implementing a new controller. <p>The total energy controller in the <code>rosplane</code> package, shows in a practical way how to implement a new controller. This section is meant to only give a high level overview of how this can be done. The first step is to identify where your changes should be made. This means determining which class the change belongs in. Consult the class pages for more information on where the best fit for your controller would be. The next step is to define a new class that inherits from class you are changing. Override the functions of interest. Next if the inherited class is not at the bottom of the inheritance chain, you will have to modify (duplicate but only change the inheritance, this is to not break default behavior) the controller classes further down the chain to inherit from your class rather than the original. This is to avoid a multiple inheritance problem (inheritance diamond).</p> <p>To add your new controller as an option to be launched you will need to make a few edits. To be clear, you add your new final controller, (<code>new_controller</code> or <code>copy_of_controller</code> in the diagram) as an option. These edits are as follows:</p> <ul> <li>Add new controller to the CMakeLists.txt.<ul> <li>The best examples are found in the CMakeLists.txt.</li> <li>Be sure to include the <code>.cpp</code> files.</li> </ul> </li> </ul> <p> Figure 3: Location in <code>CMakeLists.txt</code> to add the new controller's <code>.cpp</code> file(s). <p></p> <ul> <li>First import the new controller by adding its header file to <code>controller_base.cpp</code>.</li> </ul> <p> Figure 4: Location in <code>controller_base.cpp</code> to import new controller's header file. <p></p> <ul> <li>Next you need to add the new controller as an option to the <code>main</code> function. The argument to the main function is the name/activation string for the control. This is passed in on launch of ROSplane (see Launching ROSplane in the User Guide for more details).</li> </ul> <p> Figure 5: Location in <code>controller_base.cpp</code> to add option to select control type. <p></p> <p>If this is done correctly, then you should be able to simply change between control schemes with only an argument to a launch file. This will allow for easier testing where you can use a more tested controller initially and but swap to a new controller when convenient.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/","title":"Controller State Machine","text":""},{"location":"developer-guide/rosplane/controller/controller-state-machine/#state-machine-overview","title":"State Machine Overview","text":"<p>The controller state machine uses discrete states to turn on and off particular controls for a more stable flight. These regimes are designed so that particular mission objectives are only activated when particular conditions are met. In the default implementation this is controlled based on the aircraft's altitude. Though, in practice these states could be effected by any input from a ROS topic. The states are pictured below, and the differences in state are explored in the next section.</p> Figure 1: Controller state machine."},{"location":"developer-guide/rosplane/controller/controller-state-machine/#states","title":"States","text":"<p>This section describes all of the states and what control is active during that phase of flight.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/#takeoff","title":"Takeoff","text":"<p>In the takeoff state, the commanded airspeed is set to cruise, the commanded pitch is held constant and roll is controlled to zero. This results in a steady takeoff directly along the runway. The deactivation of course control means that the aircraft will not attempt to maneuver while too close to the ground. The takeoff regime is only below a certain cutoff altitude. After passing this threshold it moves into the climb state.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/#climb","title":"Climb","text":"<p>The climb state commands altitude and airspeed as normal, but still controls roll to zero. This means that the aircraft will proceed directly ahead until it is withing a cutoff (see Params section) of commanded altitude. Deactivating course control allows for the aircraft to gain enough altitude to be clear of all obstacles before attempting to follow the waypoint mission. Once within a cutoff of the commanded altitude, the state transitions to altitude hold. If the aircraft dips beneath the takeoff threshold, it will enter the takeoff state again.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/#altitude-hold","title":"Altitude Hold","text":"<p>In altitude hold all control loops are closed normally.  The aircraft will fly the waypoint mission as normal. If the aircraft dips beneath the takeoff cutoff, the state transitions to takeoff again.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/#code-architecture","title":"Code Architecture","text":"<p>The state machine's architecture allows for different aspects of the control to be modified. It simply defines a virtual method to be implemented by a child that will control during the particular state the aircraft is in. The state method is implemented in the child, only using the controls necessary for that phase of flight (see the Architecture section of the Successive Loop Closure).</p> Figure 2: Code snippet from the state machine."},{"location":"developer-guide/rosplane/controller/controller-state-machine/#parameters","title":"Parameters","text":"Parameter Explanation Range alt_toz The altitude of the takeoff zone cutoff. \\geq 0.0 (double) alt_hz The altitude command saturation limit, and difference required to transition into altitude hold. \\geq 0.0 (double)"},{"location":"developer-guide/rosplane/controller/controller-total-energy/","title":"Total Energy Controller","text":""},{"location":"developer-guide/rosplane/controller/controller-total-energy/#overview","title":"Overview","text":"<p>The total energy control system approach (TECS) differs from the successive loop closure controller in its control of airspeed and altitude. It does this by calculating the total energy of the system, both potential and kinetic and controlling it to the desired energy. A more in depth treatment of of TECS see Section 6.2 in the UAV book.</p> <p>The TECS controller has been included in ROSplane not only to provide control of the aircraft but to also demonstrate how to easily modify the controller (see Software Architecture and the following section for more details). The TECS controller calculates the desired kinetic and potential energy, using references from the commanded airspeed and altitude. It then calculates the current kinetic and potential energies and finds the kinetic and potential errors. It combines these errors, and the throttle control loop uses a PI loop to drive this total energy error to zero. The energy errors are also used to find a balance error. This is the error in the ratio of potential to kinetic energy. Pitch is then controlled by a PI loop to drive the balance error to zero. Essentially the throttle allows for the total energy to rise as it adds or allows drag to subtract energy from the system. The pitch loop controls how much of that input energy is in potential versus kinetic energy</p> <p>This approach can have advantages because it deals with the coupling of airspeed and altitude. In the successive loop closure controller (SLCC), it assumes a decoupling of airspeed and altitude which can present tuning issues, though they are not insurmountable.</p>"},{"location":"developer-guide/rosplane/controller/controller-total-energy/#software-architecture","title":"Software Architecture","text":"<p>The TECS controller provides an excellent template on implementing a new controller. Since the changes to the total energy controller are only in the longitudinal control and the rest are the same as the SLCC it inherits directly from <code>controller_successive_loop</code> and only overrides the longitudinal functions for each state.</p> Figure 1: Total Energy Controller's overriden longitudinal control for the altitude hold state."},{"location":"developer-guide/rosplane/controller/controller-total-energy/#parameters","title":"Parameters","text":"Parameter Explanation Range e_kp Total energy error proportional gain, used in throttle control. \\geq 0.0 (double) e_ki Total energy error integral gain, used in throttle control. \\geq 0.0 (double) e_kd Total energy error derivative gain, used in throttle control. \\geq 0.0 (double) l_kp Balance energy error proportional gain, used in throttle control. \\geq 0.0 (double) l_ki Balance energy error integral gain, used in throttle control. \\geq 0.0 (double) l_kd Balance energy error derivative gain, used in throttle control. \\geq 0.0 (double) mass The mass of the aircraft, allowing for calculation of energies. \\geq 0.0 (double)(kg) gravity The gravity experienced by the aircraft, allowing for calculation of potential energy. \\geq 0.0 (double)(\\frac{m}{s}) max_alt_error This is the maximum error in altitude that the total energy loop will use to calculate energy error. \\geq 0.0 (double)(meters)"},{"location":"developer-guide/rosplane/path-planning/path-planner/","title":"Path planner","text":""},{"location":"developer-guide/rosplane/path-planning/path-planner/#overview","title":"Overview","text":"<p>The path planner is responsible for creating, managing, and publishing waypoints. In the current implementation, the path planner simply maintains a list of user-defined waypoints that the user can add to or clear. The path planner then controls when waypoints are published to the path manager.</p> <p>Another implementation of the path planner (as described in the overview) could include a visual-based path planner. In this case, the path planner would receive sensor input and create and manage its own waypoints instead of a user-defined list of waypoints. However, this new path planner would still be responsible for creating and publishing waypoints. This ensures that the interface between the path planner and the path manager would stay the same, allowing for modularity in the path planner architecture.</p>"},{"location":"developer-guide/rosplane/path-planning/path-planner/#interfaces","title":"Interfaces","text":"<p>The path planner is implemented as a standalone ROS2 node, called <code>path_planner</code>. This node subscribes to the topics it needs, provides services available to the user and other nodes, and publishes waypoints to the path manager, called <code>path_manager</code>.</p> <p>The interface between <code>path_planner</code> and <code>path_manager</code> is the <code>/waypoint_path</code> topic,  which publishes messages with the <code>rosplane_msgs::msg::Waypoint</code> type. This message contains information about the waypoint's location in NED (from the origin) or GNSS (LLA) coordinates, the desired airspeed at the waypoint, and the desired heading of the aircraft at the waypoint.</p> <p>Warning</p> <p>The <code>w</code>, <code>va_d</code>, and <code>lla</code> fields must be valid for every waypoint message sent. Failure to add these fields might crash the path planner or your aircraft.</p>"},{"location":"developer-guide/rosplane/path-planning/path-planner/#list-of-ros2-interfaces","title":"List of ROS2 Interfaces","text":"ROS2 Interface Topic or Service Explanation Message or Service Type <code>waypoint_publisher_</code> <code>/waypoint_path</code> Publishes the waypoints to the <code>path_manager</code> <code>rosplane_msgs::msg::Waypoint</code> <code>state_subscription_</code> <code>/estimated_state</code> Subscribes to the estimated state of the aircraft <code>rosplane_msgs::msg::State</code> <code>next_waypoint_service_</code> <code>/publish_next_waypoint</code> Publishes the next stored waypoint <code>std_msgs::srv::Trigger</code> <code>add_waypoint_service_</code> <code>/add_waypoint</code> Adds a new waypoint to list and optionally publishes it <code>rosplane_msgs::srv::AddWaypoint</code> <code>clear_waypoint_service_</code> <code>/clear_waypoints</code> Clears the list of waypoints from the path planner and publishes a clear waypoint command to the <code>path_manager</code> <code>std_msgs::srv::Trigger</code> <code>print_waypoints_service_</code> <code>/print_waypoints</code> Prints the saved waypoints to the terminal. Can be useful when debugging <code>std_msgs::srv::Trigger</code> <code>load_mission_service_</code> <code>/load_mission_from_file</code> Loads a mission from a YAML file <code>rosflight_msgs::srv::ParamFile</code>"},{"location":"developer-guide/rosplane/path-planning/path-planner/#parameters","title":"Parameters","text":"<p>See the Parameter Management page for more details on how parameter management works.</p>"},{"location":"developer-guide/rosplane/path-planning/path-planner/#list-of-parameters","title":"List of Parameters","text":"Parameter Explanation Type Range <code>num_waypoints_to_publish_at_start</code> Number of waypoints to immediately publish at launch. If no waypoints are added, it will not publish any. int \\geq 0"},{"location":"developer-guide/rosplane/path-planning/path-planner/#recommended-usage","title":"Recommended Usage","text":"<p>We recommend using a YAML file and the <code>/load_mission_from_file</code> service to load and fly waypoints. See the example mission YAML file located at <code>/path/to/rosplane/rosplane/params/fixedwing_mission.yaml</code>.</p>"},{"location":"developer-guide/rosplane/path-planning/path-planning-overview/","title":"Path Planning Overview","text":"<p>The path planning methods used in ROSplane is modeled after the architecture presented in Small Unmanned Aircraft: Theory and Practice by Dr. Randal Beard and Dr. Tim McLain.</p> <p>In their work, the path planning functionality of the aircraft is split into three main parts, as shown in Figure 1.</p> <p>Note</p> <p>This is not a full description of the architecture. For example, the state estimator is not shown, and not all of the inputs to each of the blocks is included. These elements were removed from the figure for clarity.</p> Figure 1: Path planning architecture - based on Figure 1.1 in Small Unmanned Aircraft: Theory and Practice <p>The high-level path planning is done by the path planner node. The path planner's job is to manage, create, and publish waypoints. Those waypoints are published to the path manager node. The path manager's job is to determine and calculate the appropriate line segments and orbits needed to complete the waypoints. The path manager then publishes these straight lines and waypoints to the path follower.  The job of the path follower is to control the course, airspeed, and altitude of the aircraft to follow these lines and orbits.</p> <p>For more information on each of these nodes, see the related documentation pages for the path planner, the path manager, and the path follower. See also chapters 10-13 of the Small Unmanned Aircraft: Theory and Practice book.</p>"},{"location":"developer-guide/rosplane/path-planning/path-planning-overview/#changing-path-planning","title":"Changing Path Planning","text":"<p>The path planner currently takes in a set of user-defined waypoints and follows those waypoints.  This is not useful in all contexts, since in many applications the aircraft needs to take in sensor data and create its own waypoints and paths.</p> <p>The modularity of this framework allows users to \"plug in\" their own algorithms for each of the blocks defined in Figure 1, instead of rewriting the whole path planning stack.</p> <p>For example, we could replace the path planner block with a vision-based guidance block. The vision-based-guidance block would make decisions based on visual data to create waypoints.  However, the interface between the path planner (now the visual-based guidance planner) and the path manager would remain the same.</p> <p>Chapter 13 of the Small Unmanned Aircraft: Theory and Practice book contains more detail on implementing a vision-based path planner.</p>"},{"location":"user-guide/autonomous-flight/","title":"Autonomous Flight","text":"<p>To perform autonomous flight with ROSflight, we need to send control commands from our companion computer to the firmware. This can be done with ROSplane or ROScopter, which already have completed autonomy stacks developed specifically for ROSflight. We recommend starting with one of these autonomy stacks and building on them to suit your needs. If using a multirotor, follow the ROScopter setup guide to get started. If using a fixed-wing, follow the ROSplane setup guide.</p> <p>However, ROSplane and ROScopter are optional and an entirely different autonomy stack can be used if desired. To use a different autonomy stack, follow this guide.</p>"},{"location":"user-guide/autonomous-flight/#provide-control-from-a-companion-computer","title":"Provide Control from a Companion Computer","text":"<p>Control setpoints are sent to the flight controller by publishing to the <code>/command</code> topic that is advertised by the <code>rosflight_io</code> node. This topic accepts messages of type <code>rosflight_msgs/Command</code>, which have the following structure:</p> <pre><code>std_msgs/Header header\nuint8 mode\nuint8 ignore\nfloat32 x\nfloat32 y\nfloat32 z\nfloat32 f\n</code></pre> <p>The <code>header</code> field is a standard ROS2 message header. The <code>x</code>, <code>y</code>, <code>z</code>, and <code>f</code> fields are the control setpoint values, which are interpreted according to the <code>mode</code> and <code>ignore</code> fields.</p> <p>The following table describes the different values the <code>mode</code> field can take, as well as how the setpoint values are interpreted for each of these modes:</p> Value Enum x y z F 0 <code>MODE_PASS_THROUGH</code> aileron deflection (-1 to 1) elevator deflection (-1 to 1) rudder deflection (-1 to 1) throttle (0 to 1) 1 <code>MODE_ROLLRATE_PITCHRATE_YAWRATE_THROTTLE</code> roll rate (rad/s) pitch rate (rad/s) yaw rate (rad/s) throttle (0 to 1) 2 <code>MODE_ROLL_PITCH_YAWRATE_THROTTLE</code> roll angle (rad) pitch angle (rad) yaw rate (rad/s) throttle (0 to 1) <p>The <code>MODE_PASS_THROUGH</code> mode is used for fixed-wing vehicles to directly specify the control surface deflections and throttle, while the <code>MODE_ROLLRATE_PITCHRATE_YAWRATE_THROTTLE</code> and <code>MODE_ROLL_PITCH_YAWRATE_THROTTLE</code> modes are used for multirotor vehicles to specify the attitude rates or angles, respectively.</p> <p>The <code>ignore</code> field is used if you want to specify control setpoints for some, but not all, of the axes. For example, I may want to specify throttle setpoints to perform altitude hold, while still letting the RC pilot specify the attitude setpoints. The <code>ignore</code> field is a bitmask that can be populated by combining the following values:</p> Value Enum Result 0 <code>IGNORE_NONE</code> Ignore none of the fields (default) 1 <code>IGNORE_X</code> Ignore the <code>x</code> field 2 <code>IGNORE_Y</code> Ignore the <code>y</code> field 4 <code>IGNORE_Z</code> Ignore the <code>z</code> field 8 <code>IGNORE_F</code> Ignore the <code>F</code> field <p>For the previous example, I would set the <code>ignore</code> field to a value of <pre><code>ignore = IGNORE_X | IGNORE_Y | IGNORE_Z\n</code></pre></p> <p>The best practice is to use enum names rather than the actual numeric values for the <code>mode</code> and <code>ignore</code> fields. For example, to specify a multirotor attitude angle command in C++ I might have: <pre><code>#include &lt;rclcpp/rclcpp.hpp&gt;\n#include &lt;rosflight_msgs/msg/command.hpp&gt;\n\nrosflight_msgs::msg::Command msg;\nmsg.header.stamp = node-&gt;get_clock()-&gt;now();\nmsg.mode = rosflight_msgs::msg::Command::MODE_ROLL_PITCH_YAWRATE_THROTTLE;\nmsg.ignore = rosflight_msgs::msg::Command::IGNORE_NONE;\nmsg.x = 0.0;\nmsg.y = 0.0;\nmsg.z = 0.0;\nmsg.f = 0.6;\n</code></pre></p> <p>In Python I might have: <pre><code>import rclpy\nfrom rosflight_msgs.msg import Command\n\nmsg = Command()\nmsg.header.stamp = node.get_clock().now().to_msg()\nmsg.mode = Command.MODE_ROLL_PITCH_YAWRATE_THROTTLE\nmsg.ignore = Command.IGNORE_NONE\nmsg.x = 0.0\nmsg.y = 0.0\nmsg.z = 0.0\nmsg.f = 0.6\n</code></pre> I would then publish this message to the <code>/command</code> topic to forward it to the embedded flight controller.</p> <p>Note</p> <p>If the flight controller does not receive a new command for a defined period of time, it will ignore the old commands and revert to RC control. The length of this timeout period is set by the <code>OFFBOARD_TIMEOUT</code> parameter.</p>"},{"location":"user-guide/flight-controller-setup/","title":"Flight Controller Setup","text":"<p>Note</p> <p>This page contains instructions for flashing pre-built firmware binaries. For instructions on building and flashing from source, see Building and Flashing in the Developer Guide.</p>"},{"location":"user-guide/flight-controller-setup/#compatible-hardware","title":"Compatible Hardware","text":"<p>Currently, the ROSflight firmware only supports an in-development board from AeroVironment, the Varmint. This board is not yet commercially available, but plans are for it to start being sold early 2024.</p> <p>We also plan to add support for the CubePilot Orange, which uses the same H7 processor as the Varmint.</p>"},{"location":"user-guide/flight-controller-setup/#serial-port-configuration","title":"Serial Port Configuration","text":"<p>Tip</p> <p>You can see which groups you are a member of by running <code>groups $USER</code> on the command line.</p> <p>The following bullet point is necessary:</p> <ul> <li>Be sure your user is in the <code>dialout</code> and <code>plugdev</code> groups so you have access to the serial ports. You will need to log out and back in for these changes to take effect. <pre><code>sudo usermod -aG dialout,plugdev $USER\n</code></pre></li> </ul> <p>If you experience issues, you may need one or both of the next two bullet points:</p> <ul> <li> <p>Temporarily stop the modem-manager (Sometimes, Linux thinks the device is a modem -- this command will be effective until next boot, or until you run the command again with <code>start</code> in place of <code>stop</code>) <pre><code>sudo systemctl stop ModemManager.service\n</code></pre></p> </li> <li> <p>Add the custom udev rule so Linux handles the flight controller properly (copy the following as <code>/etc/udev/rules.d/45-stm32dfu.rules</code>) <pre><code># DFU (Internal bootloader for STM32 MCUs)\nSUBSYSTEM==\"usb\", ATTRS{idVendor}==\"0483\", ATTRS{idProduct}==\"df11\", MODE=\"0664\", GROUP=\"plugdev\"\n</code></pre></p> </li> </ul> <p>Tip</p> <p>You can permanently disable the ModemManager if you do not need it, then you won't have to disable it every time you reboot: <pre><code>sudo systemctl disable ModemManager.service\n</code></pre> Replace <code>disable</code> with <code>enable</code> to revert (i.e. if you find some other program you use needs access to it). Or you can uninstall it entirely from your system: <pre><code>sudo apt purge modemmanager\n</code></pre></p>"},{"location":"user-guide/flight-controller-setup/#flashing-firmware","title":"Flashing Firmware","text":"<p>TODO</p> <p>Update flashing instructions.</p>"},{"location":"user-guide/flight-controller-setup/#f4-boards","title":"F4 Boards","text":"<ul> <li>Install the dfu-util utility</li> </ul> <pre><code>sudo apt install dfu-util\n</code></pre> <ul> <li>Download the latest rosflight-F4.bin file, found here</li> <li>Put the board in bootloader mode (short the boot pins while restarting the board by cycling power)</li> </ul> <p>Tip</p> <p>dfu-util auto-detects F4-based boards. Try <code>dfu-util -l</code> to make sure your board is in bootloader mode</p> <ul> <li>Flash the firmware to the device <pre><code>    dfu-util -a 0 -s 0x08000000 -D rosflight-F4.bin\n</code></pre></li> </ul>"},{"location":"user-guide/getting-started/","title":"Getting Started","text":"<p>Reading through the pages in this user guide in order should provide you with the information you need to get a vehicle flying with ROSflight. The following is a summary of the steps you'll need to follow to get your vehicle set up, with links to the corresponding documentation pages:</p> <ol> <li>Set up your hardware (fixed-wing or multirotor platform, flight controller, and companion computer)</li> <li>Flash your flight controller with the latest ROSflight firmware</li> <li>Set up your RC transmitter</li> <li>Set up ROS2 on your companion computer</li> <li>Configure the flight controller for your setup: the configuration checklists below should help guide you through this process</li> <li>Run through your preflight checks</li> <li>Tune the firmware attitude controller gains (multirotors only)</li> <li>Set up autonomous flight via offboard control (optional)</li> </ol>"},{"location":"user-guide/getting-started/#configuration-checklist","title":"Configuration Checklist","text":"<p>The following checklists should help you get a new vehicle set up for the first time. This checklist assumes that your hardware is already set up correctly.</p>"},{"location":"user-guide/getting-started/#general-setup","title":"General Setup","text":"<ol> <li>Set the <code>FIXED_WING</code> parameter (<code>1</code> if a fixed-wing, <code>0</code> if a multirotor)</li> <li>Set the <code>RC_TYPE</code> parameter (<code>0</code> if PPM, <code>1</code> if SBUS)</li> <li>Set the <code>MIXER</code> parameter to the appropriate value described in the Hardware Setup page</li> <li>Set the <code>MOTOR_PWM_UPDATE</code> parameter (typically <code>490</code> for SimonK ESCs, <code>50</code> for standard servos)</li> <li>Make sure your RC transmitter is set up correctly</li> <li>Set up your RC switches<ul> <li>If you want to arm/disarm using a switch, set the <code>ARM_CHANNEL</code> parameter to the appropriate channel (0-indexed)</li> <li>If you want to use a switch to enable RC override, set the <code>RC_ATT_OVRD_CHN</code> and <code>RC_THR_OVRD_CHN</code> parameters to the appropriate channel(s) (0-indexed). If you want complete control (attitude and throttle) when you flip the switch, set both these parameters to the same channel.</li> </ul> </li> <li>Calibrate your IMU: start <code>rosflight_io</code>, then run <code>ros2 service call /calibrate_imu std_srvs/srv/Trigger</code></li> <li>Complete the multirotor-specific or fixed-wing-specific checklist below</li> <li>Save the parameters (<code>ros2 service call /param_write std_srvs/srv/Trigger</code>)</li> <li>You'll probably want to save a backup of your parameters (call <code>ros2 service call /param_save_to_file rosflight_msgs/srv/ParamFile \"{filename: \"params.yml\"}\"</code>)</li> <li>Make sure you run through the Preflight Checklist before flying</li> </ol>"},{"location":"user-guide/getting-started/#multirotor-specific-setup","title":"Multirotor-specific Setup","text":"<p>Danger</p> <p>IMPORTANT: Remove all props from the vehicle when calibrating ESCs!!!</p> <ol> <li> <p>Calibrate ESCs</p> <ol> <li>Make sure <code>MOTOR_MIN_PWM</code> and <code>MOTOR_MAX_PWM</code> are correct (usually <code>1000</code> and <code>2000</code>)</li> <li>Set <code>MIXER</code> param to <code>0</code> (ESC calibration mixer)</li> <li>Set <code>ARM_SPIN_MOTORS</code> to <code>0</code></li> <li> <p>Perform ESC calibration. For standard ESCs:</p> <ol> <li>With power disconnected from the motors, arm the flight controller</li> <li>Set throttle to maximum</li> <li>Connect power to the motors</li> <li>Drop the throttle to minimum</li> </ol> </li> <li> <p>Set the <code>MIXER</code> parameter back to the appropriate value for your vehicle (see the Hardware Setup page)</p> </li> <li>Set <code>ARM_SPIN_MOTORS</code> back to <code>1</code></li> </ol> </li> <li> <p>The <code>ARM_SPIN_MOTORS</code> parameter should be set to <code>1</code> so the motors spin slowly when armed. The idle throttle setting can be adjusted with the <code>MOTOR_IDLE_THR</code> parameter.</p> </li> <li>You'll most likely want to set the <code>CAL_GYRO_ARM</code> param to <code>1</code> to enable calibrating gyros before arming</li> <li>Set the <code>RC_ATT_MODE</code> parameter to set RC control mode (<code>0</code> for rate mode, <code>1</code> for angle mode [default])</li> <li>Set torque offsets as described in the RC trim calculation section of the Improving Firmware Performance page</li> <li>Set the <code>FAILSAFE_THR</code> parameter to specify the throttle level the MAV will hold if the transimtter disconnects. Set the parameter to <code>0</code> if you just want the MAV to drop, otherwise determine the amount of throttle required to hover the MAV and set the parameter comfortably below that. DO NOT set it above, as this will result in a runaway MAV. We recommended that you test the throttle level in an enclosed space by powering off the transmitter while hovering, if you set this parameter above 0.</li> <li>Tune the controller gains as described in the Multirotor gain tuning section of the Improving Firmware Performance page</li> </ol>"},{"location":"user-guide/getting-started/#fixed-wing-specific-setup","title":"Fixed-Wing-Specific Setup","text":"<ol> <li>Reverse servo directions if necessary using the <code>AIL_REV</code>, <code>ELEVATOR_REV</code>, and <code>RUDDER_REV</code> parameters (<code>1</code> to reverse, <code>0</code> to keep current direction)</li> <li>You'll most likely want to set the <code>ARM_SPIN_MOTORS</code> parameter to <code>0</code> so that the prop doesn't spin at a minimum throttle setting when you arm, especially if you'll be doing hand launching</li> </ol>"},{"location":"user-guide/hardware-setup/","title":"Hardware Setup","text":""},{"location":"user-guide/hardware-setup/#parts-list","title":"Parts List","text":"<p>To use ROSflight to its full potential, you will need the following system components. Some components are mounted on your MAV (Miniature Aerial Vehicle), while others are on the ground. ROSflight supports both multirotor and fixed-wing vehicles.</p> <p>Mounted on the MAV</p> <ol> <li>Aircraft Frame, Motor(s), ESC(s), Battery and Propeller(s)</li> <li>Flight Controller (FC)</li> <li>Vibration Isolation for FC</li> <li>Any external sensors</li> <li>R/C Receiver</li> <li>Companion Computer</li> <li>Wi-Fi Antenna, or access of some kind to ground-station, wireless network (e.g. Ubiquiti Bullet)</li> </ol> <p>Ground Station</p> <ol> <li>Ground-Station, Wireless Network (e.g. Wi-Fi Router, Ubiquiti Rocket)</li> <li>R/C transmitter</li> <li>Laptop or base station computer</li> <li>Joystick (Xbox controller)</li> </ol>"},{"location":"user-guide/hardware-setup/#frame-motors-escs-battery-and-propeller","title":"Frame, Motors, ESCs, Battery, and Propeller","text":"<p>We do not officially support any specific multirotor or airplane frame, motor, ESC, Battery or Propeller combination. There are a lot of great resources for building your own MAV, and there are a lot of great kits out there that have all of these parts.</p> <p>If you are designing your own multirotor or airplane, you may want to look at ecalc, an online tool which can help you design a proper ESC/Battery/Motor/Propeller system for your MAV.</p> <p>Some things to keep in mind as you design or build your MAV.</p> <ul> <li>Most kits do not include space for a companion computer, cameras, laser scanners or other sensors. Be sure to think about where these components are going to go, and how their placement will affect the CG of the MAV.</li> <li>You will likely also need to customize the power circuitry of your MAV to provide power to your companion computer at some specific voltage. Many people like to separate the power electronics (the ESCs and motors), from the computer and companion sensors. This can really come in handy if you are trying to develop code on the MAV, because you can have the computer on and sensors powered, and not worry at all about propellers turning on and causing injury as you move the aircraft about by hand. We will talk about this more when we talk about wiring up your MAV.</li> <li>Cheap propellers can cause a huge amount of vibration. Consider buying high-quality propellers, doing a propeller balance, or both. RCGroups, DIY Drones and Youtube have some awesome guides on how to do propeller balancing.</li> <li>ESCs will need to be calibrated from 2000 to 1000 us</li> </ul>"},{"location":"user-guide/hardware-setup/#flight-controller","title":"Flight Controller","text":"<p>TODO</p> <p>Update recommended hardware once supported hardware has been finalized.</p>"},{"location":"user-guide/hardware-setup/#external-sensors","title":"External Sensors","text":"<p>Additional Sensors you may want for your ROSflight setup include:</p> <ul> <li>Sonar</li> <li>GPS</li> <li>Digital Airspeed Sensor (Pitot Tube)</li> </ul>"},{"location":"user-guide/hardware-setup/#vibration-isolation","title":"Vibration Isolation","text":"<p>It is really important to isolate your flight controller from vehicle vibrations, such as those caused by propellers and motors. We recommend using small amounts of Kyosho Zeal to mount a fiberglass plate holding the FC to the MAV. You may also want to try adding mass to the flight control board. We have accomplished this by gluing steel washers to the fiberglass mounting plate.</p> <p></p> <p>You may need to experiment with the amount of gel you use, how far apart the gel is spaced, and the amount of mass added to the FC mounting plate. The interaction of these factors is difficult to predict, therefore it takes a little bit of experimentation to get it right.</p>"},{"location":"user-guide/hardware-setup/#companion-computer","title":"Companion Computer","text":"<p>The only requirement for the companion computer is that it runs Linux (usually an Ubuntu LTS version, but using Docker on other distributions is also an option), ROS2, has at least one USB port, and can be carried by the aircraft. We have had success with the following companion computers, but by no means is this a comprehensive list; it is more by way of suggestion.</p> <ul> <li>NVIDIA Jetson</li> <li>MSI CUBI</li> <li>Intel NUC</li> <li>Rasberry Pi 3</li> </ul>"},{"location":"user-guide/hardware-setup/#wi-fi","title":"Wi-Fi","text":"<p>You will need Wi-Fi to communicate with your MAV when it is in the air. Because ROS2 communicates over UDP, it is very easy to use ROS2 to view what is going on in your MAV while it is flying by sending commands and reading sensor data. For most applications, a standard Wi-Fi router and dongle will suffice. For long-range applications, you may want to look into Ubiquiti point-to-point Wi-Fi. (We have seen ranges over a mile with these networks.)</p>"},{"location":"user-guide/hardware-setup/#rc-transmitter-and-receiver","title":"RC Transmitter and Receiver","text":"<p>For RC Control, you will need a transmitter with between 6 and 8 channels. Any additional channels will be wasted. We require RC control for safe operation, and only support arming and disarming via RC control.</p> <p>ROSflight only supports PPM (pulse position modulation) and SBUS receivers. Individual channel PWM outputs are not supported. Any configurations with PPM or SBUS and 6-8 channels will be sufficient.</p>"},{"location":"user-guide/hardware-setup/#laptop-or-base-station-computer","title":"Laptop or Base Station Computer","text":"<p>You will need a laptop which can run ROS2 to communicate with the MAV over the ground station wireless network. To do this natively you'll want a recent Ubuntu LTS version, but this can also be done with Docker containers from pretty much any Linux distribution. Linux within a virtual machine can also work, but is not recommended. </p>"},{"location":"user-guide/hardware-setup/#joystick","title":"Joystick","text":"<p>A joystick is used for software-in-the-loop (SIL) simulations. The joystick is not technically a required component because it is possible to control your MAV from the command line, but it makes things much easier. Our first recommendation is to use the same transmitter you use for hardware as a joystick by plugging it into the computer via USB. We support Taranis QX7 transmitters, Radiomaster TX16s transmitters, RealFlight controllers, and XBOX controllers. Other joysticks can be used, but you may need to create custom axis and button mappings within the ROSflight joystick utility.</p>"},{"location":"user-guide/hardware-setup/#battery-monitor","title":"Battery Monitor","text":"<p>A battery monitor is an analog sensor that provides battery voltage and/or battery current information. This data can be used to prevent power loss in air or to measure system load. The sensor outputs an analog voltage proportional to the battery voltage and/or current through the battery. Most flight controllers come equipped with a built-in battery monitor, but if not, small PCB sensors are also available that can be connected to the flight controller.</p> <p>For ROSflight to use a battery monitor, an appropriate multiplier must be set. ROSflight multiplies the analog signal from the monitor by the multiplier to get the final reading. The monitor datasheet should contain the information needed to get the multiplier. For example, the datasheet for the AttoPilot 50V/90A sensor states that it outputs 63.69 mV / V. To get the original battery voltage, the multiplier must be 1/.06369, or 15.7. The multipliers for the voltage and current are set separately, with the <code>BATT_VOLT_MULT</code> and <code>BATT_CURR_MULT</code> parameters, respectively.</p> <p>ROSflight applies a simple low-pass filter to remove noise from the voltage and current measurements. These filters are configurable via the <code>BATT_VOLT_ALPHA</code> and <code>BATT_CURR_ALPHA</code> parameters. The alpha value for a given cutoff frequency \\(a\\), can be calulated with: \\( \\alpha =  e ^ {-.01a} \\). As battery voltages do not typically change quickly, the default of 0.995 usually suffices.</p> <p>More information on battery monitor hardware, including determinining appropriate multipliers and creating a simple DIY monitor, can be found on the OpenPilot Wiki.</p>"},{"location":"user-guide/hardware-setup/#wiring-diagram","title":"Wiring Diagram","text":"<p>Below is an example wiring diagram for a multirotor using an MSI Cubi as a companion computer. This diagram also includes the motor power switch, which allows for the sensors, flight controller, and companion computer to be powered on while the motors are off. This is a safer way to test sensors, code, etc. as the motors are unable to spin while the switch is off.</p> <p></p> <p>Your needs will likely be slightly different than what is shown. This is meant as an example only and can be adapted to fit your needs.</p>"},{"location":"user-guide/hardware-setup/#motor-layouts","title":"Motor Layouts","text":"<p>The desired mixer can be chosen by setting the <code>MIXER</code> parameter to the following values:</p> # Mixer 0 ESC calibration 1 Quad + 2 Quad X 3 Hex + 4 Hex X 5 Octo + 6 Octo X 7 Y6 8 X8 9 Tricopter 10 Fixed-wing (traditional AETR) <p>The associated motor layouts are shown below for each mixer. The ESC calibration mixer directly outputs the throttle command equally to each motor, and can be used for calibrating the ESCs.</p> <p></p> <p></p>"},{"location":"user-guide/hardware-setup/#connecting-to-the-flight-controller","title":"Connecting to the Flight Controller","text":"<p>The flight controller communicates with the companion computer over a serial link. ROSflight only supports one serial connection at a time and by default should be the serial link connected to the USB connector on the board.</p>"},{"location":"user-guide/hardware-setup/#using-secondary-serial-links","title":"Using Secondary Serial Links","text":"<p>In the case of an F4 flight controller, which has a USB peripheral, the highest bandwidth connection will be the USB connector. However, UART3 can also be used to communicate with the companion computer if you desire a more secure connection (micro USB connectors have been known to disconnect in high vibrations).</p> <p>If a USB connection is detected on the USB peripheral, ROSflight will direct all communication through this port. However, if the <code>PARAM_SERIAL_DEVICE</code> parameter is set to <code>3</code> and the <code>PARAM_BAUD_RATE</code> parameter is set properly, then UART3 will be enabled when the USB connection is absent.</p>"},{"location":"user-guide/improving-firmware-performance/","title":"Improving Firmware Performance","text":"<p>ROSflight supplies several methods to improve the performance of your aircraft. Tuning gains, adding feed-forward torques, and tuning the estimator are three ways to get your aircraft flying great!</p>"},{"location":"user-guide/improving-firmware-performance/#gain-tuning","title":"Gain Tuning","text":"<p>Because there are a wide variety of multirotors out there, no one set of PID controller gains will be optimal for all vehicles. The default set of gains is relatively conservative for most platforms, and should be somewhat airworthy in most cases. However, depending on the inertia-to-torque ratio on your MAV, you may have to change these gains considerably. There are some great tutorials online on multirotor gain tuning; this is another tried-and-true method used to great effect at BYU.</p> <p>If you are unfamiliar with PIDs, you should probably go read about them before trying to tune a multirotor. Getting an understanding for what is going on will definitely guide your decision making process as you try to find better gains.</p> <p>While tuning controller gains, it is very likely that the multirotor will oscillate out of control. To handle this scenario, we generally add what we call \"training wheels\" to the multirotors we are tuning. These amount to thin carbon rods in the shape of an X zip-tied to the landing gear. This widens out the base of the multirotor so if you come down on a hard oscillation, chances are the vehicle will land upright, hopefully without a prop strike, or worse, battery damage with a thermal runaway event. If the battery is not tucked inside the main frame, it is wise to add some foam as protection to the battery.</p> <p>Here is a video of a maiden flight of ROSflight with \"training wheels\" attached.</p> <p>Now, for the procedure on tuning.</p>"},{"location":"user-guide/improving-firmware-performance/#tuning-roll-and-pitch-angles","title":"Tuning Roll and Pitch angles","text":"<p>Here is a flowchart describing my PID tuning process for roll and pitch:</p> <p></p> <p>You may want to do another D-tuning iteration. Additionally, sometimes it is helpful to do a little tweaking on roll and pitch separately to eek out a little more performance from the differences in roll and pitch dynamics of your vehicle.</p> <p>Notice that we did not include any <code>I</code> tuning. As a general rule, try to keep the <code>I</code> gain as low as possible. It will always slow your response rate to input, and it can induce low frequency oscillations.</p> <p>You should only have <code>I</code> gain on roll and pitch if one of the following is true:</p> <ol> <li>You expect your CG to change, and/or</li> <li>You expect your rotor geometry to change</li> </ol> <p>Both of these are pretty rare. Instead, use your RC transmitter to trim the aircraft so it hovers with no stick input. In the RC trim calculation section, we will use the RC trim to calculate a feed-forward torque on the roll, pitch and yaw rates.</p>"},{"location":"user-guide/improving-firmware-performance/#tuning-yaw-rate","title":"Tuning Yaw rate","text":"<p>Dynamically and algorithmically, using a <code>D</code> gain in yaw-rate control has no significant advantage. Controlling with derivative requires differentiating gyro measurements, which tends to be pretty noisy. In our experience, putting <code>D</code> in rate controllers on multirotors has always decreased performance.</p> <p>Tuning yaw rate is generally pretty easy. Basically, keep cranking it up until you feel like it's \"locked in\". Sometimes, a little bit of <code>I</code> (on the order of 0.1P) can help with this as well.</p> <p>The problem with too much <code>P</code> on yaw rate generally manifests itself in motor saturation. Some, especially larger, multirotors have problems getting enough control authority in yaw with the propellers being aligned flat. After you are done tuning, you might want to look at a plot of motor commands during a fairly aggressive flight. Underactuated yaw will be pretty obvious in these plots, because you will see the motor commands railing. To fix this, you can put shims between the arm mounts and the motors to tilt the motors just a little bit in the direction of yaw for that motor.</p>"},{"location":"user-guide/improving-firmware-performance/#rc-trim","title":"RC trim","text":"<p>In the vast majority of cases, your multirotor will not be built perfectly. The CG could be slightly off, or your motors, speed controllers and propellers could be slightly different. One way to fix this is by adding an integrator. Integrators get rid of static offsets such as those just mentioned. However, as explained above, integrators also always slow vehicle response. In our case, since this offset is going to be constant, we can instead find a \"feed-forward\", or equilibrium offset, torque that you need to apply to hover without drift.</p> <p>Use the RC transmitter to find the \"equilibrium torques\" about the x, y, and z axes to keep the multirotor level. This is done by trimming the aircraft with the RC trims. These are usually the little switches next to the sticks on your transmitter. Adjust these until you can hover the multirotor without touching the sticks.</p> <p>Next, land the multirotor, disarm, center the sticks and perform a trim calibration with <code>ros2 service call /calibrate_rc_trim std_srvs/srv/Trigger</code>. ROSflight then uses the trim settings on your transmitter to find these feed-forward, or equilibrium, torques that need to be applied post-controller to keep the multirotor level. These torques will be applied to all future commands (both from the companion computer and RC), so you will need to zero out your transmitter trims after calibration.</p>"},{"location":"user-guide/improving-firmware-performance/#estimator-tuning","title":"Estimator Tuning","text":"<p>ROSflight uses a non-linear complementary filter, based on the quaternion implementation of \"Non-linear complementary filters on the special orthogonal group\" by Robert Mahony<sup>1</sup>,  to estimate attitude and angular rates. The implementation has been improved with suggestions from \"Attitude Representation and Kinematic Propagation for Low-Cost UAVs\" by Robert Casey<sup>2</sup>. A write-up of the derivation and implementation details can be found in the LaTeX report in <code>reports/estimator.tex</code>. (You'll need to be able to compile LaTeX sources to view the PDF).</p> <p>In addition to the complementary filter, accelerometer and gyro measurements are filtered using a simple low-pass filter (LPF) to cut out noise from vibrations. A block diagram of the estimator is shown below for reference. y_{gyro} and y_{acc} are gyro and accelerometer measurements, respectively and \\beta_{gyro} is the estimated gyro biases.</p> <p></p>"},{"location":"user-guide/improving-firmware-performance/#tuning-the-low-pass-filter-gains","title":"Tuning the Low-Pass Filter Gains","text":"<p>The <code>ACC_LPF_ALPHA</code> and <code>GYRO_LPF_ALPHA</code> parameters are used in the following low-pass-filter implementation (see lines <code>98-106</code> of <code>estimator.c</code>):</p> x_t = (1-\\alpha)y_t + \\alpha x_{t-1} <p>where y_t is the measurement and x_t is the filtered value. Lowering \\alpha will reduce lag in response, so if you feel like your MAV is sluggish despite all attempts at controller gain tuning, consider reducing \\alpha. Reducing \\alpha too far, however will result in a lot of noise from the sensors making its way into the motors. This can cause motors to get really hot, so make sure you check motor temperature if you are changing the low-pass filter constants.</p>"},{"location":"user-guide/improving-firmware-performance/#tuning-the-complementary-filter","title":"Tuning the Complementary Filter","text":"<p>The complementary filter has two gains, k_p and k_i. For a complete understanding of how these work, we recommend reading the Mahony Paper, or the technical report in the reports folder. In short, k_p can be thought of as the strength of accelerometer measurements in the filter, and the k_i gain is the integral constant on the gyro bias. These values should probably not be changed. Before you go changing these values, make sure you completely understand how they work in the filter.</p> <p>If you do decide to change these values, you should stick to the following rule of thumb.</p> k_i \\approx \\tfrac{k_p}{10}."},{"location":"user-guide/improving-firmware-performance/#external-attitude-measurements","title":"External Attitude Measurements","text":"<p>Because the onboard attitude estimator uses only inertial measurements, the estimates can deviate from truth. This is especially true during extended periods of accelerated flight, during which the gravity vector cannot be measured. Attitude measurements from an external source can be applied to the filter to help improve performance. These external attitude measurements might come from a higher-level estimator running on the companion computer that fuses additional information from GPS, vision, or a motion capture system.</p> <p>To send these updates to the flight controller, publish a <code>geometry_msgs/Quaternion</code> message to the <code>external_attitude</code> topic to which <code>rosflight_io</code> subscribes. The degree to which this update will be trusted is tuned with the <code>FILTER_KP_EXT</code> parameter.</p> <ol> <li> <p>Mahony, R., Hamel, T. and Pflimlin, J. (2008). Nonlinear Complementary Filters on the Special Orthogonal Group. IEEE Transactions on Automatic Control, 53(5), pp.1203-1218.\u00a0\u21a9</p> </li> <li> <p>Casey, R., Karpenko, M., Curry, R. and Elkaim, G. (2013). Attitude Representation and Kinematic Propagation for Low-Cost UAVs. AIAA Guidance, Navigation, and Control (GNC) Conference.\u00a0\u21a9</p> </li> </ol>"},{"location":"user-guide/overview/","title":"Overview","text":""},{"location":"user-guide/overview/#main-components-of-rosflight","title":"Main Components of ROSflight","text":"<p>ROSflight is intended to be used with both a typical flight controller and a companion Linux computer. Although it can be used with just a flight controller, this setup will not offer most of the advantages of ROSflight.</p> <p>Note</p> <p>To avoid confusion, we try to consistently use the following terminology:</p> <ul> <li>Flight controller: The embedded board that runs the ROSflight firmware and performs I/O with sensors and ESCs</li> <li>Companion computer: A Linux computer, running ROS2, that is mounted on the vehicle and has a physical, serial connection with the flight controller</li> <li>Offboard control (setpoints): The control setpoints passed from the companion computer to the flight controller. The control is \"offboard\" from the perspective of the flight controller, even though the computer providing those commands is mounted onboard the vehicle.</li> </ul> <p>The following figure illustrates the interactions between the major components of the system:</p> <p></p>"},{"location":"user-guide/overview/#firmware","title":"Firmware","text":"<p>The ROSflight firmware is the low level microcontroller code that runs on the flight controller. This communicates directly with sensors and actuators and serves as the bridge between hardware and higher level software. The firmware itself is designed to do as little as possible, offloading most of the work to the companion computer.</p> <p>Although higher level control is offloaded to the companion computer, enough control and functionality is included in the firmware to enable a safety pilot to fly the UAV through any portion of the flight with or without an operating companion computer.</p>"},{"location":"user-guide/overview/#rosflight-io","title":"ROSflight IO","text":"<p>ROSflight IO is a ROS2 node that runs on the companion computer that communicates directly with the firmware over a serial connection. This serves as the bridge between the firmware and the rest of ROS2 network.</p>"},{"location":"user-guide/overview/#rosplane-and-roscopter","title":"ROSplane and ROScopter","text":"<p>ROSplane and ROScopter are ROS2 based autonomy stacks that run on the companion computer and do most of the heavy computation of the autopilot. Each portion of their autonomy stacks are organized into highly modular ROS nodes that can be easily swapped out with custom nodes.</p> <p>ROSplane and ROScopter are not required for using ROSflight and you could choose to use an entirely different autonomy stack if you so desired.</p>"},{"location":"user-guide/overview/#rc-safety-pilot","title":"RC Safety Pilot","text":"<p>ROSflight is designed for use with offboard control from experimental and research code. As such, it provides several mechanisms for an RC safety pilot to intervene if something goes wrong with the control setpoints coming from the companion computer:</p> <ul> <li>RC override switch: The safety pilot can flip a switch on the transmitter to take back RC control. Attitude and throttle override can be mapped independently, meaning you can choose one or the other, put them on separate switches, or put them both on the same switch. Details on these switches are provided on the RC configuration page.</li> <li>Stick deviations: If a stick is deviated from its center position, then that channel is overridden by RC control. This allows the safety pilot to take control without flipping a switch. This may be useful to provide a momentary correction on a single axis. The fraction of stick travel needed to activate the RC override is controlled by the <code>RC_OVRD_DEV</code> parameter. The <code>OVRD_LAG_TIME</code> parameter controls the amount of time that the override remains active after the sticks return to center.</li> <li>Minimum throttle: By default, the flight controller takes the minimum of the two throttle commands from RC and offboard control setpoints. This allows the safety pilot to drop the throttle quickly if needed. This behavior can be turned on or off with the <code>MIN_THROTTLE</code> parameter.</li> </ul>"},{"location":"user-guide/overview/#arming-errors-failsafe","title":"Arming, Errors &amp; Failsafe","text":"<p>The flight controller can only be armed and disarmed via RC control. Two mechanisms are provided: sticks (left stick down and right to arm, down and left to disarm) and switch. Only one of these options can be active at a time. Details on configuration are given on the RC configuration page.</p> <p>The firmware runs a number of error checks before allowing the flight controller to arm. Completing the configuration checklist on the Getting Started page should avoid these errors. In addition to a few internal health checks, the following conditions are checked:</p> <ul> <li>Mixer: Valid mixer must have been selected (see the Hardware Setup documentation page)</li> <li>IMU calibration: The IMU must have been calibrated since firmware was flashed (it is recommended that you recalibrate often)</li> <li>RC: There must be an active RC connection</li> </ul> <p>In addition to the error checking before arming, the flight controller enters a failsafe mode if the RC connection is lost during flight while armed. While in failsafe mode the flight controller commands level flight with the throttle value defined by the <code>FAILSAFE_THR</code> parameter.</p> <p>The following is a simplified version of the finite state machine that defines logic used for the arming, error checks, and failsafe operations:</p> <p></p> <p>The state manager also includes functionality for recovering from hard faults if one were to occur, although this is unlikely with unmodified firmware. If a hard fault occurs while the flight controller is armed, the firmware has the ability to immediately rearm after rebooting to enable continued RC control of the vehicle for recovery.</p>"},{"location":"user-guide/overview/#leds","title":"LEDs","text":"<p>The meaning of the various LEDs is summarized in the following table. The colors of the LEDs may change depending on your specific board:</p> LED On Off Slow Blink Fast Blink Power (Blue) Board powered - - - Info (Green) RC control Offboard control - - Warning (Red) Armed Disarmed Error (disarmed) Failsafe (armed)"},{"location":"user-guide/parameter-configuration/","title":"Parameters","text":"<p>The ROSflight firmware has several dozen parameters which it uses to customize performance. Parameters are considered semi-static variables. That is, parameters do not change during flight, but they may change between vehicles. Examples of parameters you may wish to change are:</p> <ul> <li>Fixed-wing vehicle flag</li> <li>PID gains</li> <li>Mixer choice</li> <li>IMU low-pass filter constant</li> <li>RC receiver type (PPM or SBUS)</li> </ul> <p>and so on. Access to all parameters is enabled via ROS2 services advertised by <code>rosflight_io</code> while the flight controller is connected.</p>"},{"location":"user-guide/parameter-configuration/#parameter-interface","title":"Parameter Interface","text":""},{"location":"user-guide/parameter-configuration/#getting-parameter-values","title":"Getting Parameter Values","text":"<p>Sometimes it is handy to ask the flight controller what the current value of a parameter is. This is accomplished using the <code>param_get</code> service. As an example, let's retrieve the roll angle controller proportional (P) gain.</p> <pre><code>ros2 service call /param_get rosflight_msgs/srv/ParamGet \"{name: \"PID_ROLL_ANG_P\"}\"\n</code></pre> <p>You should get a response similar to the following (this happens to be the default value with floating-point error):</p> <pre><code>exists: True\nvalue: 0.15000000596\n</code></pre>"},{"location":"user-guide/parameter-configuration/#changing-parameters","title":"Changing Parameters","text":"<p>Parameters are changed via the <code>param_set</code> service. As an example, let's change the roll angle controller P gain. (I will assume that the flight controller is connected and <code>rosflight_io</code> is running in the root namespace.)</p> <pre><code>ros2 service call /param_set rosflight_msgs/srv/ParamSet \"{name: \"PID_ROLL_ANG_P\", value: 0.08}\"\n</code></pre> <p>You should get a prompt from <code>rosflight_io</code> saying <pre><code>[ INFO] [1491672408.585339558]: Parameter PID_ROLL_ANG_P has new value 0.08\n[ WARN] [1491672408.585508849]: There are unsaved changes to onboard parameters\n</code></pre></p> <p>Notice that the parameters have been set, but not saved. Parameter changes take effect immediately, however they will not persist over a reboot unless you write them to the non-volatile memory. This brings us to the next task.</p>"},{"location":"user-guide/parameter-configuration/#writing-parameters","title":"Writing Parameters","text":"<p>To ensure that parameter values persist between reboots, you must write the parameters to the non-volatile memory. This is done by calling <code>param_write</code></p> <pre><code>ros2 service call /param_write std_srvs/srv/Trigger\n</code></pre> <p><code>rosflight_io</code> should then respond with <pre><code>[ INFO] [1491672597.123201952]: Param write succeeded\n[ INFO] [1491672597.123452908]: Onboard parameters have been saved\n</code></pre></p> <p>Warning</p> <p>It is highly recommended that you write parameters before arming and flying the vehicle. Among other things, this will ensure that in the rare case that a hard fault is encountered and the flight controller must reboot during flight, the correct configuration will be loaded on reboot.</p> <p>Error</p> <p>Parameter writing can only happen if the flight controller is disarmed. If the param write failed for some reason, you may want to make sure your FC is disarmed and try again.</p>"},{"location":"user-guide/parameter-configuration/#backing-up-and-loading-parameters-from-file","title":"Backing Up and Loading Parameters from File","text":"<p>It is good practice to back up your parameter configuration in case you have to re-flash your firmware or you want to share configurations between vehicles. We can do this via the <code>param_save_to_file</code> and <code>param_load_from_file</code> services.</p> <p>First, let's back up our current parameter configuration:</p> <pre><code>ros2 service call /param_save_to_file rosflight_msgs/srv/ParamFile \"{filename: \"~/parameters.yaml\"}\"\n</code></pre> <p>Parameters are saved in YAML format. You must also specify the absolute file name of where you would like your parameters to be saved. The current active set of parameters will be saved, regardless of what is saved in non-volatile memory on the flight controller.</p> <p>Now, let's say we want to re-load this parameter file <pre><code>ros2 service call /param_load_from_file rosflight_msgs/srv/ParamFile \"{filename: \"~/parameters.yml\"}\"\n</code></pre> Again, you must specify the absolute file name of the file to be loaded.</p>"},{"location":"user-guide/parameter-configuration/#fixed-wing-parameter-configuration","title":"Fixed-Wing Parameter Configuration","text":"<p>Because ROSflight ships with default parameters for multirotors, you will probably want to change the following parameters if you want to fly a fixed-wing aircraft.</p> Parameter Description Type Fixed-Wing Value MOTOR_PWM_UPDATE Refresh rate of motor commands to motors and servos (Hz) - See motor documentation int 50 ARM_SPIN_MOTORS Enforce MOTOR_IDLE_PWM int false MOTOR_IDLE_THR min throttle command sent to motors when armed (Set above 0.1 to spin when armed) float 0.1 ARM_CHANNEL RC switch channel mapped to arming [0 indexed, -1 to disable] int 4 FIXED_WING switches on passthrough commands for fixed-wing operation int true MIXER Which mixer to choose - See Mixer documentation int 10 ELEVATOR_REV reverses elevator servo output int 0/1 AIL_REV reverses aileron servo output int 0/1 RUDDER_REV reverses rudder servo output int 0/1 CAL_GYRO_ARM Calibrate gyros when arming - generally only for multirotors int false"},{"location":"user-guide/parameter-configuration/#description-of-all-parameters","title":"Description of all Parameters","text":"<p>This is a list of all ROSflight parameters, including their types, default values, and minimum and maximum recommended values:</p> Parameter Description Type Default Value Min Max BAUD_RATE Baud rate of MAVlink communication with companion computer int 921600 9600 921600 SERIAL_DEVICE Serial Port (for supported devices) int 0 0 3 SYS_ID Mavlink System ID int 1 1 255 STRM_HRTBT Rate of heartbeat stream (Hz) int 1 0 1000 STRM_STATUS Rate of status stream (Hz) int 10 0 1000 STRM_ATTITUDE Rate of attitude stream (Hz) int 200 0 1000 STRM_IMU Rate of IMU stream (Hz) int 250 0 1000 STRM_MAG Rate of magnetometer stream (Hz) int 50 0 75 STRM_BARO Rate of barometer stream (Hz) int 50 0 100 STRM_AIRSPEED Rate of airspeed stream (Hz) int 50 0 50 STRM_SONAR Rate of sonar stream (Hz) int 40 0 40 STRM_SERVO Rate of raw output stream int 50 0 490 STRM_RC Rate of raw RC input stream int 50 0 50 STRM_GNSS Maximum rate of GNSS data streaming. Higher values allow for lower latency int 1000 0 1000 STRM_GNSS_FULL Maximum rate of fully detailed GNSS data streaming int 0 0 10 STRM_BATTERY Rate of battery status stream int 0 0 50 PARAM_MAX_CMD saturation point for PID controller output float 1.0 0 1.0 PID_ROLL_RATE_P Roll Rate Proportional Gain float 0.070f 0.0 1000.0 PID_ROLL_RATE_I Roll Rate Integral Gain float 0.000f 0.0 1000.0 PID_ROLL_RATE_D Roll Rate Derivative Gain float 0.000f 0.0 1000.0 PID_PITCH_RATE_P Pitch Rate Proportional Gain float 0.070f 0.0 1000.0 PID_PITCH_RATE_I Pitch Rate Integral Gain float 0.0000f 0.0 1000.0 PID_PITCH_RATE_D Pitch Rate Derivative Gain float 0.0000f 0.0 1000.0 PID_YAW_RATE_P Yaw Rate Proportional Gain float 0.25f 0.0 1000.0 PID_YAW_RATE_I Yaw Rate Integral Gain float 0.0f 0.0 1000.0 PID_YAW_RATE_D Yaw Rate Derivative Gain float 0.0f 0.0 1000.0 PID_ROLL_ANG_P Roll Angle Proportional Gain float 0.15f 0.0 1000.0 PID_ROLL_ANG_I Roll Angle Integral Gain float 0.0f 0.0 1000.0 PID_ROLL_ANG_D Roll Angle Derivative Gain float 0.05f 0.0 1000.0 PID_PITCH_ANG_P Pitch Angle Proportional Gain float 0.15f 0.0 1000.0 PID_PITCH_ANG_I Pitch Angle Integral Gain float 0.0f 0.0 1000.0 PID_PITCH_ANG_D Pitch Angle Derivative Gain float 0.05f 0.0 1000.0 X_EQ_TORQUE Equilibrium torque added to output of controller on x axis float 0.0f -1.0 1.0 Y_EQ_TORQUE Equilibrium torque added to output of controller on y axis float 0.0f -1.0 1.0 Z_EQ_TORQUE Equilibrium torque added to output of controller on z axis float 0.0f -1.0 1.0 PID_TAU Dirty Derivative time constant - See controller documentation float 0.05f 0.0 1.0 MOTOR_PWM_UPDATE Overrides default PWM rate specified by mixer if non-zero - Requires reboot to take effect int 0 0 490 MOTOR_IDLE_THR min throttle command sent to motors when armed (Set above 0.1 to spin when armed) float 0.1 0.0 1.0 FAILSAFE_THR Throttle sent to motors in failsafe condition (set just below hover throttle) float 0.3 0.0 1.0 ARM_SPIN_MOTORS Enforce MOTOR_IDLE_THR int true 0 1 FILTER_INIT_T Time in ms to initialize estimator int 3000 0 100000 FILTER_KP estimator proportional gain - See estimator documentation float 0.5f 0 10.0 FILTER_KI estimator integral gain - See estimator documentation float 0.01f 0 1.0 FILTER_KP_COR estimator proportional gain on external attitude correction - See estimator documentation float 10.0f 0 1.0 FILTER_ACCMARGIN allowable accel norm margin around 1g to determine if accel is usable float 0.1f 0 1.0 FILTER_QUAD_INT Perform a quadratic averaging of LPF gyro data prior to integration (adds ~20 us to estimation loop on F1 processors) int 1 0 1 FILTER_MAT_EXP 1 - Use matrix exponential to improve gyro integration (adds ~90 us to estimation loop in F1 processors) 0 - use euler integration int 1 0 1 FILTER_USE_ACC Use accelerometer to correct gyro integration drift (adds ~70 us to estimation loop) int 1 0 1 CAL_GYRO_ARM True if desired to calibrate gyros on arm int false 0 1 GYROXY_LPF_ALPHA Low-pass filter constant on gyro X and Y axes - See estimator documentation float 0.3f 0 1.0 GYROZ_LPF_ALPHA Low-pass filter constant on gyro Z axis - See estimator documentation float 0.3f 0 1.0 ACC_LPF_ALPHA Low-pass filter constant on all accel axes - See estimator documentation float 0.5f 0 1.0 GYRO_X_BIAS Constant x-bias of gyroscope readings float 0.0f -1.0 1.0 GYRO_Y_BIAS Constant y-bias of gyroscope readings float 0.0f -1.0 1.0 GYRO_Z_BIAS Constant z-bias of gyroscope readings float 0.0f -1.0 1.0 ACC_X_BIAS Constant x-bias of accelerometer readings float 0.0f -2.0 2.0 ACC_Y_BIAS Constant y-bias of accelerometer readings float 0.0f -2.0 2.0 ACC_Z_BIAS Constant z-bias of accelerometer readings float 0.0f -2.0 2.0 ACC_X_TEMP_COMP Linear x-axis temperature compensation constant float 0.0f -2.0 2.0 ACC_Y_TEMP_COMP Linear y-axis temperature compensation constant float 0.0f -2.0 2.0 ACC_Z_TEMP_COMP Linear z-axis temperature compensation constant float 0.0f -2.0 2.0 MAG_A11_COMP Soft iron compensation constant float 1.0f -999.0 999.0 MAG_A12_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A13_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A21_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A22_COMP Soft iron compensation constant float 1.0f -999.0 999.0 MAG_A23_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A31_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A32_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A33_COMP Soft iron compensation constant float 1.0f -999.0 999.0 MAG_X_BIAS Hard iron compensation constant float 0.0f -999.0 999.0 MAG_Y_BIAS Hard iron compensation constant float 0.0f -999.0 999.0 MAG_Z_BIAS Hard iron compensation constant float 0.0f -999.0 999.0 BARO_BIAS Barometer measurement bias (Pa) float 0.0f 0 inf GROUND_LEVEL Altitude of ground level (m) float 1387.0f -1000 10000 DIFF_PRESS_BIAS Differential Pressure Bias (Pa) float 0.0f -10 10 RC_TYPE Type of RC input 0 - PPM, 1 - SBUS int 0 0 1 BATT_VOLT_MULT Battery monitor voltage multiplier float 0 0 inf BATT_CURR_MULT Battery monitor current multiplier float 0 0 inf BATT_VOLT_ALPHA Batter monitor voltage filter alpha. Values closer to 1 smooth the signal more. float 0.995 0 1 BATT_CURR_ALPHA Battery monitor current filter alpha. Values closer to 1 smooth the signal more. float 0.995 0 1 RC_X_CHN RC input channel mapped to x-axis commands [0 - indexed] int 0 0 3 RC_Y_CHN RC input channel mapped to y-axis commands [0 - indexed] int 1 0 3 RC_Z_CHN RC input channel mapped to z-axis commands [0 - indexed] int 3 0 3 RC_F_CHN RC input channel mapped to F-axis commands [0 - indexed] int 2 0 3 RC_ATT_OVRD_CHN RC switch mapped to attitude override [0 indexed, -1 to disable] int 4 4 7 RC_THR_OVRD_CHN RC switch channel mapped to throttle override [0 indexed, -1 to disable] int 4 4 7 RC_ATT_CTRL_CHN RC switch channel mapped to attitude control type [0 indexed, -1 to disable] int -1 4 7 ARM_CHANNEL RC switch channel mapped to arming (only if PARAM_ARM_STICKS is false) [0 indexed, -1 to disable] int -1 4 7 RC_NUM_CHN number of RC input channels int 6 1 8 SWITCH_5_DIR RC switch 5 toggle direction int 1 -1 1 SWITCH_6_DIR RC switch 6 toggle direction int 1 -1 1 SWITCH_7_DIR RC switch 7 toggle direction int 1 -1 1 SWITCH_8_DIR RC switch 8 toggle direction int 1 -1 1 RC_OVRD_DEV RC stick deviation from center for override float 0.1 0.0 1.0 OVRD_LAG_TIME RC stick deviation lag time before returning control (ms) int 1000 0 100000 MIN_THROTTLE Take minimum throttle between RC and computer at all times int true 0 1 RC_ATT_MODE Attitude mode for RC sticks (0: rate, 1: angle). Overridden if RC_ATT_CTRL_CHN is set. int 1 0 1 RC_MAX_ROLL Maximum roll angle command sent by full deflection of RC sticks float 0.786f 0.0 3.14159 RC_MAX_PITCH Maximum pitch angle command sent by full stick deflection of RC sticks float 0.786f 0.0 3.14159 RC_MAX_ROLLRATE Maximum roll rate command sent by full stick deflection of RC sticks float 3.14159f 0.0 9.42477796077 RC_MAX_PITCHRATE Maximum pitch command sent by full stick deflection of RC sticks float 3.14159f 0.0 3.14159 RC_MAX_YAWRATE Maximum pitch command sent by full stick deflection of RC sticks float 1.507f 0.0 3.14159 MIXER Which mixer to choose - See Mixer documentation int Mixer::INVALID_MIXER 0 10 FIXED_WING switches on pass-through commands for fixed-wing operation int false 0 1 ELEVATOR_REV reverses elevator servo output int 0 0 1 AIL_REV reverses aileron servo output int 0 0 1 RUDDER_REV reverses rudder servo output int 0 0 1 FC_ROLL roll angle (deg) of flight controller wrt aircraft body float 0.0f 0 360 FC_PITCH pitch angle (deg) of flight controller wrt aircraft body float 0.0f 0 360 FC_YAW yaw angle (deg) of flight controller wrt aircraft body float 0.0f 0 360 ARM_THRESHOLD RC deviation from max/min in yaw and throttle for arming and disarming check (us) float 0.15 0 500 OFFBOARD_TIMEOUT Timeout in milliseconds for offboard commands, after which RC override is activated int 100 0 100000"},{"location":"user-guide/preflight-checks/","title":"Pre-Flight Checklist","text":"<p>This is an example of a ROSflight pre-flight checklist. You will likely need to augment this with checks specific to both (a) your hardware and (b) the code running on your companion computer.</p>"},{"location":"user-guide/preflight-checks/#before-powering-up-motors","title":"Before powering up motors","text":"<ul> <li> ROS2 is running on the companion computer, communicating with the base station</li> <li> <code>rosflight_io</code> reports no errors</li> <li> Sensors are calibrated and publishing<ul> <li> IMU (re-calibrate every flight): <code>ros2 service call /calibrate_imu std_srvs/srv/Trigger</code></li> <li> Barometer: <code>ros2 service call /calibrate_baro std_srvs/srv/Trigger</code></li> <li> Sonar (if attached)</li> <li> Airspeed (if attached)</li> </ul> </li> <li> Estimated attitude is being published and looks accurate</li> <li> Published outputs look reasonable</li> <li> Parameter Check (if using a fixed-wing, there are about 8 parameters you will need to change from default)</li> <li> RC communication</li> <li> Failsafe behavior</li> <li> Arming and disarming</li> <li> RC override behavior</li> <li> RC range test</li> <li> Wire-wiggle test (wiggle all wires to look for bad connections)</li> <li> If desired, logging is turned on (e.g. recording a ros2 bag)</li> </ul>"},{"location":"user-guide/preflight-checks/#after-powering-up-motors","title":"After Powering Up Motors","text":"<p>Danger</p> <p>Be sure the flight controller is disarmed before powering up motors!!!</p> <ul> <li> Arm/Disarm test</li> <li> Propeller spin test (check directions and response to stick inputs)</li> <li> Control surface test (fixed-wing)</li> <li> Response to offboard controls</li> </ul>"},{"location":"user-guide/rc-configuration/","title":"RC Configuration","text":""},{"location":"user-guide/rc-configuration/#binding-your-transmitter-to-your-receiver","title":"Binding your Transmitter to your Receiver","text":"<p>Follow the instructions in your user manual to bind your transmitter to your RC receiver. You may also be able to find a guide on YouTube with instructions; just search for your particular transmitter and receiver model.</p>"},{"location":"user-guide/rc-configuration/#rc-transmitter-calibration","title":"RC Transmitter Calibration","text":"<p>To avoid confusion and to reduce code complexity in the firmware source code, ROSflight does not perform software calibration of RC transmitters. This means that RC calibration must be done on the transmitter itself, as opposed to in software. This is pretty straight-forward for most modern transmitters.</p>"},{"location":"user-guide/rc-configuration/#configure-the-full-stick-output-for-each-channel","title":"Configure the full stick output for each channel","text":"<p>The easiest way to do this is to enter the \"Servo Setup\" Menu (for Spektrum transmitters) and change the servo travel variable. You can watch the raw RC readings from the flight controller by echoing the rc_raw topic from <code>rosflight_io</code></p> <pre><code>ros2 topic echo /rc_raw\n</code></pre> <ul> <li>Center both sticks on your transmitter</li> <li>Apply subtrim until the first four channels all read 1500 exactly (or as close as possible--some RC receivers are worse than others and cannot exactly output 1500 us)</li> <li>Set the channel endpoints so that maximum stick deflections result in readings of 1000 and 2000 us.</li> </ul>"},{"location":"user-guide/rc-configuration/#configure-stick-directions-for-roll-pitch-and-yaw-channels","title":"Configure stick directions for roll, pitch, and yaw channels.","text":"<p>You now have to make sure your RC transmitter is sending commands consistent with the north-east-down (NED) frame assumed by ROSflight.</p> <p>You may find this graphic helpful. It shows all the basic stick positions, and the associated output from the first four channels when looking at a raw AETR (aileron, elevator, throttle, rudder) RC signal from <code>rosflight_io</code>. Make sure that the stick output is in the correct direction.</p> <p></p> <p>It should be noted that channel assignment can be modified via the <code>RC_*_CHN</code> parameters. So, if you are using something other than AETR assignment, the channel index for each stick may be different, but the direction should be the same.</p>"},{"location":"user-guide/rc-configuration/#switch-configuration","title":"Switch Configuration","text":"<p>Switches can be configured for the following functions. To disable a switch for a specific, default function, set the corresponding parameter to <code>-1</code>. Be sure to check that the switch directions operate as you intend, and reverse them in your transmitter if necessary.</p>"},{"location":"user-guide/rc-configuration/#safety-pilot-configuration","title":"Safety Pilot Configuration","text":"<p>The <code>RC_ATT_OVRD_CHN</code> parameter maps a switch to override attitude commands with RC control. The <code>RC_THR_OVRD_CHN</code> parameter maps a switch to override throttle commands with RC control. To override both with a single switch, set both parameters to the same value (this is the default behavior).</p>"},{"location":"user-guide/rc-configuration/#arming","title":"Arming","text":"<p>By default, arming is done with the sticks (left stick down and right to arm, down and left to disarm). To use a switch instead, set the <code>ARM_CHANNEL</code> parameter to the desired channel. Setting an arming switch disables arming with the sticks.</p>"},{"location":"user-guide/rc-configuration/#flight-mode","title":"Flight Mode","text":"<p>If desired, you can map a switch to select between attitude control types (angle and rate) in flight by setting the <code>RC_ATT_CTRL_CHN</code> parameter to the desired channel. This can be useful if, for example, you are learning rate mode but want to be able to switch back to attitude mode to help stabilize the vehicle. This feature is disabled by default.</p>"},{"location":"user-guide/ros2-setup/","title":"Installing/Setting up ROS2","text":"<p>You will need to get ROS2 on both the companion computer and the base station laptop. This can be done with a native installation or with Docker. To install ROS2 natively, Check out the official ROS2 Installation page for details. Make sure to install both the <code>ros-humble-desktop</code> and <code>ros-dev-tools</code> packages, or the equivalent packages for your version of ROS2. <code>ros-humble-ros-base</code> can be used instead of <code>ros-humble-desktop</code> if you don't need GUI tools or the simulation.</p> <p>We support all fixed-release ROS2 versions that are not EOL, which currently includes ROS2 Humble and ROS2 Iron. ROS2 Rolling is not fixed-release and is therefore not officially supported. </p>"},{"location":"user-guide/ros2-setup/#installing-rosflight","title":"Installing ROSflight","text":"<p>You will need to install the ROSflight packages on both the companion computer and the base station computer. The companion computer will run the node that actually communicates with the flight controller over a serial connection, while the base station needs the message and service definitions to be able to call services or subscribe and publish to topics.</p>"},{"location":"user-guide/ros2-setup/#from-source","title":"From Source","text":"<p>First, set up a ROS2 workspace:</p> <pre><code>mkdir -p ~/rosflight_ws/src\ncd ~/rosflight_ws/src\n</code></pre> <p>Next, download the source code into your workspace (include the <code>--recursive</code> argument to download the necessary submodules):</p> <pre><code>git clone --recursive https://github.com/rosflight/rosflight_ros_pkgs.git\n</code></pre> <p>Install dependencies: <pre><code>sudo rosdep init\nrosdep update\nrosdep install --from-path . -y --ignore-src\n</code></pre></p> <p>Note</p> <p>Gazebo does not have an arm64 build target. If using a companion computer with arm64 architecture, append <code>--skip-keys=\"gazebo_dev gazebo_plugins gazebo_ros gazebo\"</code> to the <code>rosdep install</code> command above. This will skip installing Gazebo and the compilation of rosflight_sim, which currently requires Gazebo.</p> <p>Build the packages: <pre><code>cd ~/rosflight_ws\ncolcon build\n</code></pre></p> <p>Source the setup file and set it to be sourced automatically: <pre><code>source ~/rosflight_ws/install/setup.bash\necho \"source ~/rosflight_ws/install/setup.bash\" &gt;&gt; ~/.bashrc\n</code></pre></p> <p>Note</p> <p>You'll also need to source the file at <code>/usr/share/gazebo/setup.sh</code> if you plan to use the Gazebo simulator.</p>"},{"location":"user-guide/ros2-setup/#running-rosflight_io","title":"Running rosflight_io","text":"<p>The <code>rosflight_io</code> node is the bridge between ROS2 and the MAVLink communication with the flight controller. This node must be run on the computer that has the physical serial connection to your flight controller. To run this node, use something like the following command: <pre><code>ros2 run rosflight_io rosflight_io --ros-args -p port:=/dev/ttyUSB0\n</code></pre> Replace <code>/dev/ttyUSB0</code> with the port your flight controller is connected to.</p>"},{"location":"user-guide/ros2-setup/#using-a-docker-container-to-run-ros2","title":"Using a Docker Container to run ROS2","text":"<p>Note</p> <p>This guide was written for using Linux as the host machine, but theoretically you should be able to use Docker to do the same thing on Mac or Windows. However, the specifics of the commands may be different. Please refer to the Docker documentation for information on how to use Docker on a non-Linux system.</p> <p>Tip</p> <p>This guide was written using ROS2 Humble Docker images, but any distribution of ROS can be used. Just replace <code>humble</code> with the name of the distribution you want to use.</p> <p>If you aren't running a compatible version of Linux for ROS2, don't want to make changes to your system, want to be able to easily switch between ROS verions, or just want to containerize your applications, then you can use Docker containers. To get started, install Docker Engine, sometimes referred to as Docker server.</p> <p>Docker works by running self-contained systems called containers, which act kind of like a separate computer system but without all the overhead of a full virtual machine. Docker containers are based on Docker images, which provide the initial operating system, files, and programs for the Docker container. Fortunately, the developers of ROS provide Docker images for nearly all versions of ROS, which makes it very easy to get any version of ROS up and running on your system very quickly.</p> <ul> <li>To start a Docker container with ROS run this command: <pre><code>docker run -it ros:humble\n</code></pre></li> </ul> <p>Once completed, you should enter a bash terminal in a fresh installation of Ubuntu and ROS! However, the container does not have access to any USB devices, source files on your system, or your network to be able to communicate with different computers. To do these things we'll need to add more arguments to the <code>docker run</code> command.</p> <ul> <li> <p>To give access to source file on your system, mount a folder on your system to the docker container with the <code>-v</code> argument: <pre><code>docker run -it -v /folder_to_mount_from_host:/location_to_mount_folder_in_container ros:humble\n</code></pre></p> </li> <li> <p>To give access to a USB device, you need to mount the location of the USB device and give the container sudo access to your host system with <code>--privileged</code>: <pre><code>docker run -it -v /dev/usb_to_mount:/dev/USB --privileged ros:humble\n</code></pre></p> </li> <li> <p>You can also mount the entire <code>/dev</code> folder to the container if you want to simplify the process of giving access to USB devices by not needing to know the address of the USB device beforehand. However, the more resources you give to the container, the less secure it is: <pre><code>docker run -it -v /dev:/dev --privileged ros:humble\n</code></pre></p> </li> <li> <p>To give access to your network, specify the network to use as the host's network with <code>--network host</code>. <pre><code>docker run -it --network host ros:humble\n</code></pre></p> </li> </ul> <p>It is worth noting that every time you use the <code>docker run</code> command, a new container with those specific arguments are created. So, if you want a container with access to all those things, you need to use all the arguments at once.</p> <ul> <li>As an example, if I wanted to make a ROS2 Humble container with access to a USB device at <code>/dev/ttyUSB0</code>, access to my host network, access to the source files at <code>~/rosflight_ws</code>, and give the container a convenient name of <code>rosflight</code> with the <code>--name</code> argument, I would use this command: <pre><code>docker run --name rosflight -it -v /dev/ttyUSB0:/dev/ttyUSB0 --privileged --network host -v ~/rosflight_ws:/root/rosflight_ws ros:humble\n</code></pre></li> </ul> <p>Something the previous commands don't include is the ability to render GUI tools (like rqt_graph and Gazebo). Being able to render GUI tools can be done a number of ways, but an easy way is to give the container access to your system's X11 windowing system. Note that this isn't the most secure method and doesn't include GPU acceleration. (For more information about including GPU acceleration, refer to the guide found here.)</p> <ul> <li> <p>To give access to the host's windowing system, use the following commands. Note that the base Docker image is <code>osrf/ros:humble-desktop-full</code>, as <code>ros:humble</code> doesn't include GUI tools in the image. Also, <code>xhost +local:root</code> needs to be run once per login session and is not persistent. <pre><code>xhost +local:root\ndocker run -it --env=\"DISPLAY\" --env=\"QT_X11_NO_MITSHM=1\" --volume=\"/tmp/.X11-unix:/tmp/.X11-unix:rw\" osrf/ros:humble-desktop-full\n</code></pre></p> </li> <li> <p>To create a GUI enabled ROS container named <code>rosflight</code> with access to the host network, source files found at <code>~/rosflight_ws</code>, and a USB device, use this command: <pre><code>xhost +local:root\ndocker run --name rosflight -it -v /dev/ttyUSB0:/dev/ttyUSB0 --privileged --network host -v ~/rosflight_ws:/rosflight_ws --env=\"DISPLAY\" --env=\"QT_X11_NO_MITSHM=1\" --volume=\"/tmp/.X11-unix:/tmp/.X11-unix:rw\" osrf/ros:humble-desktop-full\n</code></pre></p> </li> </ul> <p>Warning</p> <p>During testing, we found some strange behavior with ROS when running a GUI enabled container on a system with ROS already installed. If you need a GUI enabled system, try to do so on a system without ROS installed (or at the very least avoid sourcing/using ROS on your system). Also avoid having multiple GUI enabled containers running at once.</p> <p>Some other useful Docker commands:</p> <ul> <li> <p>To see all containers that exist on your system and their names: <pre><code>docker ps -a\n</code></pre></p> </li> <li> <p>To start a container named <code>rosflight</code> that was previously created with the <code>docker run</code> command: <pre><code>docker start -i rosflight\n</code></pre></p> </li> <li> <p>To open another bash terminal in a container named <code>rosflight</code> that is already running: <pre><code>docker exec -it rosflight bash\n</code></pre></p> </li> <li> <p>To delete a container named <code>rosflight</code>: <pre><code>docker rm rosflight\n</code></pre></p> </li> </ul> <p>You should now be able to create Docker containers with everything you need to run ROSflight! Docker is a very powerful tool and there is much more you can do with Docker to improve your development workflow. However, we're not interested in making an exhaustive Docker guide so please refer to the Docker documentation or other online guides to learn more.</p>"},{"location":"user-guide/roscopter-setup/","title":"ROScopter","text":"<p>ROScopter is still under development. Check the github repo for the latest instructions.</p>"},{"location":"user-guide/rosplane-setup/","title":"ROSplane Setup","text":"<p>ROSplane v2.0.0-beta is now available! Check the github repo for the latest instructions.</p> <p>ROSplane is a basic fixed-wing autopilot build around ROS2 for use with the ROSflight autopilot. It is built according to the methods published in Small Unmanned Aircraft: Theory and Practice by Dr. Randy Beard and Dr. Tim McLain.</p>"},{"location":"user-guide/rosplane-setup/#requirements","title":"Requirements","text":"<p>ROSplane requires a working ROS2 installation on a companion computer. ROSplane will most often be used in conjunction with the ROSflight firmware and the firmware interface (aka <code>rosflight_ros_pkgs</code>).</p> <p>Follow the instructions on ROS2 Setup to install and set up ROS2 and <code>rosflight_ros_pkgs</code>.</p>"},{"location":"user-guide/rosplane-setup/#installation","title":"Installation","text":"<p>You will need to install ROSplane on the companion computer.</p> <p>First, navigate to the src directory of the ROS2 workspace and clone the git repository:</p> <pre><code>cd /path/to/rosflight_ws/src\ngit clone https://github.com/rosflight/rosplane.git\n</code></pre> <p>Note</p> <p>Your <code>rosflight_ws</code> file structure should now look like: <pre><code>rosflight_ws\n  \u2514\u2500\u2500 src \n    \u251c\u2500\u2500 rosflight_ros_pkgs\n    \u2514\u2500\u2500 rosplane \n</code></pre></p> <p>Then navigate to the top of the <code>rosflight_ws</code> directory and build:</p> <pre><code>cd ..\ncolcon build\n</code></pre> <p>Next, source the <code>rosflight_ws</code> install files. If you already added the source command to your <code>.bashrc</code> from the ROS2 Setup page, then you can skip this step.</p> <pre><code># source the install file\nsource install/setup.bash\n\n# add it to your .bashrc\necho \"source install/setup.bash &gt;&gt; $HOME/.bashrc\"\n</code></pre> <p>Note that sourcing the <code>setup.bash</code> file in the <code>rosflight_ws</code> directory will install all ROS2 packages in any subdirectories.</p>"},{"location":"user-guide/rosplane-setup/#running-rosplane-sil","title":"Running ROSplane SIL","text":"<p>A controller or a simulated controller can be used to fly the aircraft in simulation. See the <code>README.md</code> file for the <code>rosflight_ros_pkgs</code> package for more information on RC controll in simulation.</p>"},{"location":"user-guide/rosplane-setup/#launching","title":"Launching","text":""},{"location":"user-guide/rosplane-setup/#recommended-method","title":"Recommended Method","text":"<p>A convenience bash script has been included that uses tmux to launch Gazebo, an instance of the ROSflight firmware, and ROSplane. Note that this requires tmux, so you may need to install it with <code>sudo apt install tmux</code>. Run <pre><code>./src/rosplane/rosplane/scripts/rosplane_gcs_launch.sh\n</code></pre> from the <code>rosflight_ws</code> directory. Note that the script needs options specified, so it will fail. However,it will print out the required configuration options. See the script for more information.</p>"},{"location":"user-guide/rosplane-setup/#alternative-method","title":"Alternative Method","text":"<p>Alternatively, you can run each of the commands in the bash script individually: <pre><code># Terminal 1 - Launches Gazebo and a simulated instance of the firmware\nros2 launch rosflight_sim fixedwing.launch.py\n\n# Terminal 2 - Runs rosflight_io configured for SIL to interface with the firmware\nros2 run rosflight_io rosflight_io --ros-args -p udp:=true\n\n# Terminal 3 - Launches rosplane with the Anaconda aerodynamic coefficients\nros2 launch rosplane_sim sim.launch.py aircraft:=anaconda\n</code></pre></p> <p>You can also replace the first two commands above with the convenience launch file that does both: <pre><code>ros2 launch rosflight_sim fixedwing_sim_io_joy.launch.py aircraft:=anaconda\n</code></pre> Remember to launch ROSplane if you use this method.</p>"},{"location":"user-guide/rosplane-setup/#additional-setup","title":"Additional Setup","text":""},{"location":"user-guide/rosplane-setup/#recommended-method_1","title":"Recommended Method","text":"<p>If this is your first time launching ROSplane, make sure to run the convenience launch script to initialize the firmware parameters and calibrate the IMU. <pre><code>ros2 launch rosflight_sim fixedwing_init_firmware.launch.py\n</code></pre></p>"},{"location":"user-guide/rosplane-setup/#alternative-method_1","title":"Alternative Method","text":"<p>Alternatively, you can run the following commands to initialize firmware parameters and calibrate the IMU. Firmware parameters should first be loaded using <pre><code>ros2 service call /param_load_from_file rosflight_msgs/srv/ParamFile \"filename: /path/to/rosflight_ws/src/rosflight_ros_pkgs/rosflight_sim/params/fixedwing_firmware.yaml\"\n</code></pre></p> <p>The IMU should then be calibrated to remove the random biases generated at startup. Note that the random number generator used to create these biases is seeded with a constant value, so this calibration should only need to be performed once. See the code to change the way these biases are calculated. <pre><code>ros2 service call /calibrate_imu std_srvs/srv/Trigger\n</code></pre></p> <p>After calibrating, write the parameters to a file using: <pre><code>ros2 service call /param_write std_srvs/srv/Trigger\n</code></pre> This command will create a directory named <code>rosflight_memory</code> where the parameters are written. The ROSflight firmware will automatically check if the <code>rosflight_memory</code> directory is present when launched and will use those parameters if available.</p> <p>Note</p> <p>The ROSflight firmware will only look for the <code>rosflight_memory</code> directory in the directory where the launch command is run. You must launch <code>rosflight_sim</code> in the same directory to use the saved parameters; otherwise, reload and re-write the parameters.</p>"},{"location":"user-guide/rosplane-setup/#flying-in-sim","title":"Flying in Sim","text":"<p>Once you have the simulation booted up, use channel 4 of a connected transmitter to arm. If you are using a simulated transmitter, use <code>ros2 service call /toggle_arm std_srvs/srv/Trigger</code> to toggle arm/disarm.</p> <p>After arming, the plane will operate under RC control. Verify that the commands are working and that the aircraft is responding as expected.</p> <p>To fly autonomously, use channel 5 to disable RC override. If using a simulated transmitter, use <code>ros2 service call /toggle_override std_srvs/srv/Trigger</code> to toggle RC override on/off.</p> <p>The plane should then take off or fly autonomously in the Gazebo simulator!</p>"},{"location":"user-guide/rosplane-setup/#running-rosplane-on-hardware","title":"Running ROSplane on Hardware","text":"<p>Ensure <code>rosflight_io</code> is running on the companion computer, and that the flight controller is connects to the companion computer.</p> <p>Launch ROSplane using <pre><code>ros2 launch rosplane rosplane.launch.py\n</code></pre></p> <p>Arm the aircraft using channel 4 of the safety RC transmitter. When ready to let ROSplane take control, use channel 5 of the RC transmitter to disable RC override.</p> <p>Warning</p> <p>Disabling RC override on hardware will turn control over to ROSplane. A safety pilot should always be ready to take control, especially when running untested code.</p>"},{"location":"user-guide/rosplane-setup/#flying-waypoint-missions-in-sim-and-hardware","title":"Flying Waypoint Missions (in sim and hardware)","text":"<p>Autonomous waypoint missions can easily be flown using ROSplane. The waypoints of a mission are controlled by the <code>path_planner</code> node. These waypoints are sent to the <code>path_manager</code> node. Low level path-following is done by the <code>path_follower</code> node. See \"Small Unmanned Aircraft: Theory and Practice\" by Dr. Randy Beard and Dr. Tim McLain for more information on the architecture. See Path Planning for more information on how to use and tune the path planner, manager, and follower.</p>"},{"location":"user-guide/rosplane-setup/#adding-waypoints","title":"Adding waypoints","text":""},{"location":"user-guide/rosplane-setup/#recommended-method_2","title":"Recommended Method","text":"<p>ROSplane initializes with no waypoints added to the <code>path_planner</code>. We recommend using a mission .yaml file (an example mission can be found in <code>rosplane/params/fixedwing_mission.yaml</code>). Loading the mission can be done using </p> <pre><code>ros2 service call /load_mission_from_file rosflight_msgs/srv/ParamFile \"{filename: &lt;FILENAME&gt;}\"\n</code></pre> <p>where <code>FILENAME</code> is the absolute path to the mission .yaml file. Note that the origin (0,0,0) is placed at the GNSS location where ROSplane was initialized.</p> <p>Note</p> <p>All waypoints must include a valid <code>[X, Y, Z]</code>, <code>va_d</code>, and <code>lla</code> values.</p>"},{"location":"user-guide/rosplane-setup/#alternative-method_2","title":"Alternative Method","text":"<p>Alternatively, you can add a waypoint one at a time by calling the appropriate service</p> <pre><code>ros2 service call /add_waypoint rosplane_msgs/srv/AddWaypoint \"{w: [X, Y, Z], chi_d: CHI_D, lla: USE_LLA, use_chi: USE_CHI, va_d: VA_D}\"\n</code></pre> <p>where <code>[X, Y, Z]</code> is the NED position of the waypoint from the origin (in meters) OR the GNSS location of the waypoint (LLA), <code>CHI_D</code> is the desired heading at the waypoint, and <code>VA_D</code> is the airspeed at the waypoint. Set the <code>lla</code> field to <code>true</code> if the waypoint <code>[X, Y, Z]</code> field is given in GNSS coordinates and <code>false</code> if given in NED coordinates. Corners in the path are controlled by <code>USE_CHI</code>, where a value of <code>True</code> will cause ROSplane to use a Dubins path planner and a value of <code>False</code> will cause a fillet path planner to be used. Adding waypoints can be done at any time, even after loading from a file.</p> <p>Clearing waypoints can be done using  <pre><code>ros2 service call /clear_waypoints std_msgs/srv/Trigger\n</code></pre></p>"},{"location":"user-guide/rosplane-setup/#publishing-waypoints","title":"Publishing Waypoints","text":"<p>The <code>path_planner</code> node automatically publishes a small number of waypoints (default is 3) at the beginning of this mission. This number is controlled by the <code>num_waypoints_to_publish_at_start</code> ROS2 parameter. </p> <p>Additional waypoints can be published using  <pre><code>ros2 service call /publish_next_waypoint std_srvs/srv/Trigger\n</code></pre></p>"},{"location":"user-guide/running-gazebo-simulation/","title":"Running Simulations in Gazebo","text":"<p>ROSflight comes with a useful tool allowing it to perform software-in-the-loop (SIL) simulations of the ROSflight firmware in Gazebo.</p>"},{"location":"user-guide/running-gazebo-simulation/#architecture-of-the-sil-simulation","title":"Architecture of the SIL Simulation","text":"<p>To best mimic the hardware experience of ROSflight, the SIL plugin for Gazebo actually implements the firmware source code as a library. We just implemented a different \"board layer\" which uses gazebo instead of hardware calls for things like <code>imu_read()</code> and <code>pwm_write()</code>. Instead of a serial link over USB to the flight controller, we use a UDP connection bouncing off of localhost to communicate between <code>rosflight_io</code> and the firmware. This means the interface to the SIL plugin is identical to that of hardware. <code>rosflight_io</code> is the main gateway to the firmware in simulation, just as it is in hardware.</p> <p>The following table summarizes the correlation between connections in hardware and simulation:</p> Connection Type Hardware Simulation Serial communications to <code>rosflight_io</code> USB / UART UDP RC PPM Receiver ROS2 <code>RC</code> topic (<code>rosflight_msgs/RCRaw</code>) Motors PWM Gazebo Plugin Sensors SPI/I2C Gazebo Plugin"},{"location":"user-guide/running-gazebo-simulation/#quick-start-guide-to-sil-simulation","title":"Quick-Start Guide to SIL Simulation","text":"<p>Note</p> <p>To simulate a fixed-wing mav, just change all instances of <code>multirotor</code> in the steps below to <code>fixedwing</code>.</p> <ul> <li> <p>Setup ROSflight with the ROS2 Setup guide, making sure to install the <code>-desktop</code> package of ROS2, not the <code>-ros-base</code>.</p> </li> <li> <p>Source the Gazebo setup file if you haven't added it to <code>~/.bashrc</code>: <pre><code>source /usr/share/gazebo/setup.sh\n</code></pre></p> </li> <li> <p>Launch Gazebo with the ROSflight SIL: <pre><code>ros2 launch rosflight_sim multirotor.launch.py\n</code></pre></p> </li> <li> <p>Gazebo should now be running, and you should have the following <code>rqt_graph</code>.</p> </li> </ul> <p></p> <ul> <li> <p>At this point, you can't actually do anything because there is no RC connection and no <code>rosflight_io</code> to talk to the firmware. Let's start by running a <code>rosflight_io</code> node. In a separate terminal, run: <pre><code>ros2 run rosflight_io rosflight_io --ros-args -p udp:=true\n</code></pre></p> <ul> <li>The <code>udp</code> parameter tells <code>rosflight_io</code> to simulate a serial connection over UDP rather than using the USB connection to hardware</li> </ul> </li> </ul> <p>Your <code>rqt_graph</code> should look something like the following image. This looks funny because ROS2 doesn't actually know that there is a UDP connection between <code>rosflight_io</code> and gazebo. There is one, though, and you can test it by echoing any of the topics published by <code>rosflight_io</code>.</p> <p></p> <ul> <li>Start up a simulated RC connection. The easiest way to do this is with the ROSflight utility <code>rc_joy.py</code>. Connect a joystick to the computer (or transmitter) and run:      <pre><code>ros2 run rosflight_sim rc_joy.py --ros-args --remap /RC:=/multirotor/RC\n</code></pre>     This simulates the RC connection in hardware. If everything is mapped correctly, you should now be able to arm, disarm and fly the aircraft in simulation!</li> </ul> <p>Tip</p> <p>To start the Gazebo sim, rosflight_io node, and rc_joy.py utility all at once, run this command instead of the three commands individually: <pre><code>ros2 launch rosflight_sim multirotor_sim_io_joy.launch.py    \n</code></pre></p> <p>Note</p> <p>It is much easier to fly with a real transmitter than with an Xbox-type controller. FrSky Taranis QX7 transmitters, Radiomaster TX16s transmitters, and RealFlight controllers are also supported. Non-Xbox joysticks may have incorrect mappings. If your joystick does not work, and you write your own mapping, please contribute back your new joystick mapping!</p> <p>Remember, the SIL tries its best to replicate hardware. That means you have to calibrate and set parameters in the same way you do in hardware. See the Hardware Setup and Parameter Configuration pages in this documentation for instructions on how to perform all preflight configuration before the aircraft will arm. You can also run  <pre><code>ros2 launch rosflight_sim multirotor_init_firmware.launch.py\n</code></pre> to load all required parameters and perform initial calibrations for a quick simulation setup.</p>"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to ROSflight","text":"<p>The ROS2 updates for ROSflight are still under development. Please use with discretion.</p>"},{"location":"#what-is-rosflight","title":"What is ROSflight?","text":"<p>ROSflight is a lean and adaptable autopilot system designed from the ground up with researchers in mind. Its purpose is to enable researchers to quickly and easily try out new ideas with minimal effort. Some of ROSflight's key feature are:</p> <ul> <li>Lightweight, modular, and well documented code that is easy to understand and modify.</li> <li>Most of the autopilot exists on a Linux computer rather than a microcontroller, enabling easier development with increased capabilities.</li> <li>Seamless switching between simulation and hardware: no part of the autopilot knows if it is running in simulation or not.</li> <li>Built on a ROS2 framework, allowing easy integration with ROS2 based projects.</li> </ul> <p>See the user guide for more details on ROSflight.</p>"},{"location":"#why-rosflight","title":"Why ROSflight?","text":"<p>There are a lot of excellent autopilots out there with a lot of great firmware options. Why did we feel like the world needed ROSflight? Because in our experience none of the other available options satisfied our research needs. Existing autopilots commonly used by researchers tend to have massive codebases under constant development that run primarily on microcontrollers.</p> <p>This presents a number of problems. First, we are limited in our ability to understand and control everything occurring within the autonomy stack, making much of the autopilot an untouchable black box. Second, we are limited to the abilities of microcontrollers and can't take advantage of the more powerful hardware and software that can be found on Linux computers. Third, maintaining up-to-date support for software or hardware projects becomes a lot of work as things are frequently changing.</p> <p>ROSflight is intended to fix these problems by being a lightweight, modular, and well documented codebase that offloads as much as possible to a ROS2 based framework running on a Linux computer.</p>"},{"location":"#our-vision","title":"Our Vision","text":"<p>Perhaps more important than what we are trying to accomplish is what we are not trying to accomplish. ROSflight is not intended to be a fully-featured autopilot with all the same functions of other autopilots, but instead serve as a core foundation that can easily be adapted to any use case.</p> <p>Therefore, one of our primary objectives is to avoid feature creep and remain lean. We hope that others will extend our code and build on top of it, and would love to hear about your successes. But for the most part, we will not be incorporating these new features back into the main project. Instead, we hope that ROSflight will remain a lean, core code base that will continue to serve as a launch pad for exciting new projects and applications.</p>"},{"location":"developer-guide/contribution-guidelines/","title":"Contribution Guidelines","text":"<p>ROSflight is intended to be a streamlined, bare-bones autopilot. We welcome any bug fixes, cleanup, or other contributions which do not add complexity or detract from the readability and simplified nature of the project. In an attempt to avoid \"feature creep,\" we will be very discriminatory in merging pull requests whose purpose is to simply add features. Forking the repository in order to add features is totally acceptable and encouraged, just recognize us as the original authors of the autopilot (per the agreement in the BSD-3 license).</p> <p>In addition, we strive to maintain a very high standard of quality in terms of code style, variable naming, and the like. By maintaining a high standard, we hope that the code will continue to be useful, understandable, and cohesive in nature. Please don't be offended if we ask you to modify the formatting of your code before approving a pull request.</p> <p>Although we strive for complete in-code documentation, in practice this sometimes gets left behind for the sake of rapid development. If you, as a potential developer, find some portion of documentation unsatisfactory, we welcome questions on the appropriate GitHub issues page or forum, and encourage you to submit pull requests which improve documentation. Several new developers have started with first improving the documentation to get a handle on how things work.</p>"},{"location":"developer-guide/contribution-guidelines/#key-goals-of-rosflight","title":"Key Goals of ROSflight","text":"<p>Here is a summary of the key goals and philosophies behind ROSflight. As you look to make contributions to the project, keep these in mind.</p> <ul> <li> <p>Only include the things that most people will need. The goal of this would be to do most of the work so people can get a MAV in the air quickly and easily, but not overcomplicate the code with features that only a small portion of users would need.</p> </li> <li> <p>Be modular and adaptable for many research-centric use cases. This will be accomplished by putting the majority of the autopilot in a well-designed ROS2 framework. That which needs to be on the microcontroller will need to be done so carefully with good coding practices. Additionally, microcontroller code that is the most likely to be expanded upon should include clear interfaces and instructions for doing so.</p> </li> <li> <p>Keep everything simple and well documented. The key goal here is to minimize the amount of time and effort it takes someone to go from knowing nothing about ROSflight to being able to implement their own features and making meaningful progress with their research.</p> </li> </ul>"},{"location":"developer-guide/contribution-guidelines/#communication","title":"Communication","text":"<p>There are two channels to communicate with the developer team. For bug reports, feature requests, and anything to do with code, please open an issue on the appropriate GitHub issue page. For questions and other discussions, please use the forum.</p>"},{"location":"developer-guide/style-guide/","title":"Style Guide","text":"<p>The focus of anyone contributing to this project should be to write code that is easily understood by anyone, including people who have little experience with ROSflight or coding in general. So, we ask that contributions adhere to the following style guidelines.</p>"},{"location":"developer-guide/style-guide/#comments","title":"Comments","text":"<p>Well written and clear code should be easy to understand even without comments. However, since this project is intended to be as accessible as possible, we ask that you write both clear code and clear comments. Don't use comments to explain code that would be difficult to understand without comments, but instead use them to make clear code even more understandable.</p>"},{"location":"developer-guide/style-guide/#doxygen","title":"Doxygen","text":"<p>Doxygen comments should be added pretty much anywhere where it makes sense. Please include at least a brief for anything you write. For methods and functions, also include explanations of all arguments and the return value. More detailed explanations are encouraged for non-trivial methods and objects.</p>"},{"location":"developer-guide/style-guide/#white-space-and-line-endings","title":"White Space and Line Endings","text":"<p>Please try not to commit anything that only changes white space or line endings. To check if that's going to happen, run <code>git diff --check</code> before you stage your files.</p>"},{"location":"developer-guide/style-guide/#code-style","title":"Code Style","text":"<p>ROSflight follows the ROS2 C++ style guide, with some more specific guidelines below. Please follow first the style guidelines below and then the ROS2 guidelines. A .clang-format file and format-correcting script is provided in most ROSflight repositories that can be used to auto-format your code to help you find things you might have missed. Format checks on pull requests using this .clang-format file may also exist.</p>"},{"location":"developer-guide/style-guide/#indentation","title":"Indentation","text":"<p>Indentation should be 2 spaces (no tabs). Case statements in switch blocks should not be indented, e.g.</p> <pre><code>switch (variable)\n{\ncase 1:\n  // do something\n  break;\ndefault:\n  break;\n}\n</code></pre>"},{"location":"developer-guide/style-guide/#spaces","title":"Spaces","text":"<p>There should be a space between <code>if</code>, <code>for</code>, or <code>while</code> and the condition, e.g. <code>while (true)</code>, not <code>while(true)</code>.</p>"},{"location":"developer-guide/style-guide/#naming-conventions","title":"Naming Conventions","text":"<ul> <li>Class names should be capitalized with no spaces (i.e. <code>StateManager</code>).</li> <li>Member variables should contain a post-pended underscore (i.e. <code>data_</code>).</li> <li>Member functions should be all lower case with underscores (i.e. <code>set_error()</code>).</li> <li>Boolean values should be assigned <code>true</code> or <code>false</code>, not <code>0</code> or <code>1</code>.</li> </ul>"},{"location":"developer-guide/style-guide/#function-arguments","title":"Function Arguments","text":"<p>Primitive data types (<code>int</code>, <code>float</code>, etc.) should always be passed by value. Other types (e.g. classes) should be passed by reference and should maintain proper const-correctness. Arguments that are modified by the function should be passed by pointer instead of reference, to make the fact that the argument will be changed clearer in the calling code. For example:</p> <pre><code>void do_something(float dt, const MyClass&amp; data, int* output);\n</code></pre> <p>This function would be called as</p> <pre><code>float dt = 0.01f;\nMyClass my_class;\nint value;\n\ndo_something(dt, my_class, &amp;value);\n</code></pre> <p>This makes it clear the <code>value</code> is modified by the function call.</p>"},{"location":"developer-guide/style-guide/#classes","title":"Classes","text":"<p>All modules should be defined as a self-contained class. All member variables should be declared as \"private,\" named with a post-pended underscore, and accessed through inline accessor functions. All accessible data should be encapsulated in a struct. For example, here is a snippet from the <code>Sensors</code> module in the firmware:</p> <pre><code>class Sensors\n{\npublic:\n  struct Data\n  {\n    vector_t accel = {0, 0, 0};\n    vector_t gyro = {0, 0, 0};\n    float imu_temperature = 0;\n    uint64_t imu_time = 0;\n\n    float diff_pressure_velocity = 0;\n    float diff_pressure = 0;\n    float diff_pressure_temp = 0;\n    bool diff_pressure_valid = false;\n\n    float baro_altitude = 0;\n    float baro_pressure = 0;\n    float baro_temperature = 0;\n    bool baro_valid = false;\n\n    float sonar_range = 0;\n    bool sonar_range_valid = false;\n\n    vector_t mag = {0, 0, 0};\n\n    bool baro_present = false;\n    bool mag_present = false;\n    bool sonar_present = false;\n    bool diff_pressure_present = false;\n  };\n\n  Sensors(ROSflight&amp; rosflight);\n\n  inline const Data &amp; data() const { return data_; }\n\nprivate:\n  Data data_;\n}\n</code></pre> <p>Note that <code>data_</code> is a private member variable, but the <code>Data</code> struct is declared publicly and <code>data_</code> is accessed through an <code>inline const</code> accessor to prevent another module from changing <code>data_</code>.</p>"},{"location":"developer-guide/style-guide/#enums","title":"Enums","text":"<p>Enums should be declared using the following style: <pre><code>enum ArmedState\n{\n  ARMED_STATE_INIT,\n  ARMED_STATE_DISARMED,\n  ARMED_STATE_ARMED\n};\n</code></pre></p> <p>The name of the enum should be in CamelCase, and the names of its members should be ALL_CAPS. Where practical, have the members of the enum begin with the name of the enum.</p>"},{"location":"developer-guide/style-guide/#structs","title":"Structs","text":"<p>Structs should be declared using the following style: <pre><code>struct SomeValue\n{\n  int v1;\n  int v2;\n};\n</code></pre> Struct type names should be in CamelCase.</p>"},{"location":"developer-guide/style-guide/#globals","title":"Globals","text":"<p>The use of global variables should be limited to when absolutely necessary (such as linking to interrupt routines or hardware peripherals). This should only occur in board support layers and not in the core ROSflight libary code.</p>"},{"location":"developer-guide/style-guide/#include-order","title":"Include Order","text":"<p>Include files at the top of your file in the following order:</p> <ol> <li>Standard library (e.g. <code>&lt;cstdint&gt;</code>)</li> <li>Files from external libraries included in the project (e.g. <code>&lt;breezystm32/breezystm32.h&gt;</code>, <code>&lt;mavlink/v1.0/common/mavlink.h&gt;</code>)</li> <li>Other header files from this project (e.g. <code>\"rosflight.h\"</code>)</li> <li>The header file for this specific source file</li> </ol> <p>Group the includes according to the above list with an empty line between each group. (For external libraries, you may subdivide group 2 into a group for each library.) The first two groups should use angle brackets (<code>&lt;&gt;</code>), and the last two groups should use quotation marks (<code>\"\"</code>). Files from external libraries should be namespaced by the library name (e.g. <code>&lt;breezystm32/breezystm32.h&gt;</code>, not <code>&lt;breezystm32.h&gt;</code>).</p> <p>Alphabetize the files within each group. Do not change the include order to fix build errors; if you have to do that it means you are not including a file somewhere that you should. Please fix it by including all the right files.</p> <p>Include C standard library headers using the C++ style (<code>#include &lt;cmath&gt;</code>) instead of the C style (<code>#include &lt;math.h&gt;</code>).</p> <p>For example, in <code>sensors.c</code> I might have: <pre><code>#include &lt;cstdbool&gt;\n#include &lt;cstdint&gt;\n\n#include &lt;breezystm32/breezystm32.h&gt;\n#include &lt;breezystm32/drv_mpu6050.h&gt;\n\n#include \"param.h\"\n\n#include \"sensors.h\"\n</code></pre></p>"},{"location":"developer-guide/style-guide/#namespacing","title":"Namespacing","text":"<p>All modules should be encapsulated in a package namespace that is unique and consistent within the package (like <code>rosflight_firmware</code> for anything in the firmware package).</p>"},{"location":"developer-guide/firmware/building-and-flashing/","title":"Building and Flashing the Firmware","text":"<p>This guide assumes you are running Ubuntu 22.04 LTS, which is the currently supported development environment.</p>"},{"location":"developer-guide/firmware/building-and-flashing/#installing-the-arm-embedded-toolchain","title":"Installing the ARM Embedded Toolchain","text":"<pre><code>sudo apt install gcc-arm-none-eabi\n</code></pre> <p>You can test the installation and check which version is installed by running <code>arm-none-eabi-gcc --version</code>.</p>"},{"location":"developer-guide/firmware/building-and-flashing/#building-the-firmware-from-source","title":"Building the Firmware from Source","text":"<p>Now that we have the compiler installed, simply clone the ROSflight firmware repository, pull down the submodules, and build:</p> <pre><code>git clone --recursive https://github.com/rosflight/rosflight_firmware\ncd rosflight_firmware\nmkdir build \ncd build \ncmake .. -DBUILD_VARMINT=TRUE\nmake\n</code></pre>"},{"location":"developer-guide/firmware/building-and-flashing/#flashing-newly-built-firmware","title":"Flashing Newly-Built Firmware","text":"<p>TODO</p> <p>Update this when hardware support is finalized.</p> <p>First, make sure you have configured your computer as described in the Serial Port Configuration section of the user guide.</p>"},{"location":"developer-guide/firmware/building-and-flashing/#f4","title":"F4","text":"<p>Flash the firmware to the board by running <code>make BOARD=REVO flash</code>. If necessary, specify the serial port with <code>make BOARD=REVO SERIAL_DEVICE=/dev/ttyACM0 flash</code>.</p>"},{"location":"developer-guide/firmware/code-architecture/","title":"Code Architecture","text":"<p>The firmware is divided into two main components: the core library, and a collection of board implementations. This division is intended to allow the same core flight code to run on any processor or platform, either an embedded flight controller or a desktop environment for a software-in-the-loop (SIL) simulation. The interface between these two components is called the hardware abstraction layer (HAL). This architecture is illustrated in the following diagram:</p> <p></p>"},{"location":"developer-guide/firmware/code-architecture/#firmware-core-library","title":"Firmware Core Library","text":"<p>The firmware core library consists of all the code in the <code>include</code> and <code>src</code> directories of the firmware repository. This includes the code for what is termed the \"flight stack,\" which consists of the core components (such as the estimator, controller, state manager, etc.) required for flight. It also includes the interface definition for the hardware abstraction layer, which is defined by the abstract <code>Board</code> class in <code>include/board.h</code>. The communications link (MAVLink) is also abstracted, with the interface defined by the <code>CommLink</code> class in <code>include/comm_link.h</code>. External libraries are contained in the <code>lib</code> folder.</p>"},{"location":"developer-guide/firmware/code-architecture/#board-abstraction","title":"Board Abstraction","text":"<p>The hardware abstraction implementations are contained in the <code>boards</code> directory, organized in subdirectories according to the hardware driver layer. Each board implementation is required to provide an implementation of the hardware abstraction layer interface, which is passed by reference to the flight stack. The Varmint implementation in the <code>boards/varmint</code> shows how this is done for an embedded flight controller. Examples of board implementations for SIL simulation are found in the <code>rosflight_sim</code> ROS2 package available here.</p> <p>The flight stack is encapsulated in the <code>ROSflight</code> class defined at <code>include/rosflight.h</code>. This class contains two public functions: <code>init()</code> and <code>run()</code>. Its constructor requires two arguments: an implementation of the <code>Board</code> interface, and an implementation of the <code>CommLink</code> interface.</p> <p>Each board implementation is required to implement the entire Board class.</p>"},{"location":"developer-guide/firmware/code-architecture/#comm-link-abstraction","title":"Comm Link Abstraction","text":"<p>The purpose of the comm link abstraction layer is to allow communication protocols other than MAVLink to be used if desired. The comm link abstraction implementations are contained in the <code>comms</code> directory, organized in subdirectories by protocol. The implementations translate between the messages that the firmware expects to send and receive, and the messages defined by the communication protocol. Currently, only MAVLink is implemented.</p>"},{"location":"developer-guide/firmware/code-architecture/#flight-stack","title":"Flight Stack","text":"<p>The flight stack is encapsulated by the <code>ROSflight</code> class defined in <code>include/rosflight.h</code>. It consists of a collection of modules. Each of these modules is implemented as a C++ class, and encapsulates a cohesive piece of the autopilot functionality. The following diagram illustrates these modules and the data flow between them. Rectangular blocks represent modules in the flight stack, and ellipses represent hardware functionality implemented in the board support layer:</p> <p></p> <p>We'll describe each of these modules in the following sections:</p>"},{"location":"developer-guide/firmware/code-architecture/#state-manager","title":"State Manager","text":"<p>This module is in charge of keeping track of the internal state (armed status, error codes, failsafe, etc.) of the vehicle. While only the comm manager data flow is illustrated on the diagram, all other modules query the state manager to determine the status and act appropriately based on that status.</p> <p>The operation of the state manager is defined by the following finite state machine:</p> <p></p> <p>The state manager also includes functionality for recovering from hard faults. In the case of a hard fault, the firmware writes a small amount of data to backup memory then reboots. This backup memory location is checked and then cleared after every reboot. The backup memory includes the armed state of the flight controller. On reboot, the firmware will initialize then, if this armed-state flag is set, immediately transition back into the armed state. This functionality allows for continued RC control in the case of a hard fault. Hard faults are not expected with the stable firmware code base, but this feature adds an additional layer of safety if experimental changes are being made to the firmware itself.</p>"},{"location":"developer-guide/firmware/code-architecture/#parameter-server","title":"Parameter Server","text":"<p>This module handles all parameters for the flight stack. It supports the getting and setting of integer and floating-point parameters, and the saving of these parameters to non-volatile memory. Setting and getting of parameters from the companion computer is done through the serial communication interface. While no other data flow lines are shown on the diagram, all of the other modules interact with the parameter server.</p>"},{"location":"developer-guide/firmware/code-architecture/#comm-manager","title":"Comm Manager","text":"<p>This module handles all serial communication between the flight controller and companion computer. This includes streaming data and receiving offboard control setpoints and other commands from the computer. This module primarily collects data from the sensors, estimator, state manager, and parameters modules, and sends offboard control setpoints to the command manager and parameter requests to the parameter server.</p> <p>The actual communication protocol used is abstracted by the interface in include/comm_link.h. A new protocol can be used by implementing a wrapper around the protocol that inherits from this interface. Currently, only MAVLink has been implemented. The implementation is found in comms/mavlink/mavlink.h and comms/mavlink/mavlink.cpp.</p>"},{"location":"developer-guide/firmware/code-architecture/#sensors","title":"Sensors","text":"<p>This module is in charge of managing the various sensors (IMU, magnetometer, barometer, differential pressure sensor, sonar altimeter, etc.). Its responsibilities include updating sensor data at appropriate rates, and computing and applying calibration parameters.</p>"},{"location":"developer-guide/firmware/code-architecture/#estimator","title":"Estimator","text":"<p>This module is responsible for estimating the attitude and attitude rates of the vehicle from the sensor data.</p>"},{"location":"developer-guide/firmware/code-architecture/#rc","title":"RC","text":"<p>The RC module is responsible for interpreting the RC signals coming from the transmitter via the receiver. This includes mapping channels to their appropriate functions and reversing directions if necessary.</p>"},{"location":"developer-guide/firmware/code-architecture/#command-manager","title":"Command Manager","text":"<p>The command manager combines inputs from the RC and comm manager modules to produce a control setpoint. Its main purpose is to handle the interaction between offboard commands and the RC safety pilot, as well as to enforce the failsafe command if the state manager reports failsafe mode.</p>"},{"location":"developer-guide/firmware/code-architecture/#controller","title":"Controller","text":"<p>The controller uses the inputs from the command manager and estimator to compute a control output. This control output is computed in a generic form (x, y, and z torques, and force F), and is later converted into actual motor commands by the mixer.</p>"},{"location":"developer-guide/firmware/code-architecture/#mixer","title":"Mixer","text":"<p>The mixer takes the generic outputs computed by the controller and maps them to actual motor commands depending on the configuration of the vehicle.</p>"},{"location":"developer-guide/firmware/debugging/","title":"Using an In-Circuit Debugger","text":"<p>TODO</p> <p>Update this when hardware support is finalized.</p> <p>Debugging an STM32-based board is accomplished with an ST-LINK/V2 in-circuit debugger and programmer. We have had the best luck with the official version from STMicroelectronics. These devices are reasonably priced, and are available directly from STMicroelectronics or from vendors such as Digi-Key, Mouser, and Newark.</p> <p>The following guide will show you how to get the in-circuit debugger running with either the Visual Studio Code or QtCreator IDE. Start with the steps in the General Setup section, then move on to either the VS Code or STM32cubeIDE sections depending on your choice of IDE.</p> <p>This guide assumes you are running Ubuntu 22.04 LTS, which is the currently supported development environment.</p>"},{"location":"developer-guide/firmware/debugging/#general-setup","title":"General Setup","text":"<p>Follow the guide in Building and Flashing to install the compiler toolchain.</p> <p>Also make sure you have configured your computer as described in the Serial Port Configuration section of the user guide.</p>"},{"location":"developer-guide/firmware/debugging/#connect-debugger-to-flight-controller","title":"Connect debugger to flight controller","text":"<p>The ST-LINK/V2 connects to the microcontroller using the Serial Wire Debug (SWD) interface. You will need to connect the <code>GND</code>, <code>NRST</code>, <code>SWDIO</code>, and <code>SWCLK</code> lines of the ST-LINK/V2 to your flight controller. On many F4 boards, these lines are pinned out through a 4-position JST SH connector, although that connector is not always populated. Refer to the documentation for your specific board for details.</p> <p>The official ST-LINK/V2 also needs a target voltage reference on pin 1 or 2, which for the F4 boards is 3.3V. However, there is no externally accessible 3.3V pinout on the F4 boards. An easy solution to this is to connect pin 19 (VDD 3.3V) of the ST-LINK/V2 to pin 1 or 2 of the ST-LINK/V2 (Target VCC) to provide the voltage reference. You will also need to power the board from another source, either through the USB port or over the servo rail. Note that this connection is not required for the cheap clone versions of the ST-LINK/V2.</p>"},{"location":"developer-guide/firmware/debugging/#vs-code","title":"VS Code","text":"<p>You can install Visual Studio Code by downloading the latest version from their website. Follow the steps below to configure debugging with the in-circuit debugger.</p> <p>You should open the root firmware directory for editing and debugging, e.g. <code>code /path/to/rosflight_firmware</code>.</p>"},{"location":"developer-guide/firmware/debugging/#install-openocd","title":"Install OpenOCD","text":"<p>OpenOCD (On-Chip Debugger) is the software that will control the debugger. Install from the <code>apt</code> repositories:</p> <pre><code>sudo apt install openocd\n</code></pre>"},{"location":"developer-guide/firmware/debugging/#install-cortex-debug-extension","title":"Install Cortex-Debug extension","text":"<p>The embedded debugging functionality is provided by the <code>Cortex-Debug</code> extension. Install using the VS Code GUI, or from VS Code press <code>Ctrl+P</code> then type <code>ext install marus25.cortex-debug</code>.</p> <p>Steps for configuring this extension are described next.</p>"},{"location":"developer-guide/firmware/debugging/#download-svd-file","title":"Download SVD file","text":"<p>A System View Description (SVD) file describes the configuration (CPU, peripherals, registers, etc.) of the microcontroller. The Cortex-Debug extension can make use of an SVD file to provide more detailed debugging information, such as the ability to inspect register values.</p> <p>SVD files can be downloaded from STMicroelectronics. The files for the F4 are contained in the ZIP file that can be downloaded here, and the relevant file is <code>STM32F405.svd</code>. The files for the F1 are contained in the ZIP file that can be downloaded here, and the relevant file is <code>STM32F103.svd</code>. Put those files in a convenient location.</p>"},{"location":"developer-guide/firmware/debugging/#configure-build-step","title":"Configure build step","text":"<p>You can configure VS Code to run <code>make</code> for you when you press <code>Ctrl+Shift+B</code>. To do this, put the following in <code>.vscode/tasks.json</code> inside your firmware working directory:</p> <pre><code>{\n  // See https://go.microsoft.com/fwlink/?LinkId=733558\n  // for the documentation about the tasks.json format\n  \"version\": \"2.0.0\",\n  \"tasks\": [\n    {\n      \"type\": \"shell\",\n      \"label\": \"make\",\n      \"command\": \"make\",\n      \"args\": [\"DEBUG=GDB\"],\n      \"group\": {\n        \"kind\": \"build\",\n        \"isDefault\": true\n      }\n    }\n  ]\n}\n</code></pre> <p>Note that by default, this will only build the F4 (Revo) firmware. To build the F1 firmware, you will need to edit this to add the argument <code>BOARD=NAZE</code>.</p>"},{"location":"developer-guide/firmware/debugging/#configure-debugging","title":"Configure debugging","text":"<p>To configure in-circuit debugging of F4 and F1 targets, put something like the following in <code>.vscode/launch.json</code> inside your firmware working repository:</p> <pre><code>{\n  // Use IntelliSense to learn about possible attributes.\n  // Hover to view descriptions of existing attributes.\n  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387\n  \"version\": \"0.2.0\",\n  \"configurations\": [\n    {\n      \"name\": \"STM32F405\",\n      \"type\": \"cortex-debug\",\n      \"request\": \"launch\",\n      \"servertype\": \"openocd\",\n      \"cwd\": \"${workspaceRoot}\",\n      \"executable\": \"${workspaceRoot}/boards/airbourne/build/rosflight_REVO_Debug.elf\",\n      \"device\": \"STM32F405\",\n      \"svdFile\": \"/path/to/STM32F405.svd\",\n      \"configFiles\": [\n        \"interface/stlink-v2.cfg\",\n        \"target/stm32f4x.cfg\"\n      ],\n      \"runToMain\": true\n    },\n    {\n      \"name\": \"STM32F103\",\n      \"type\": \"cortex-debug\",\n      \"request\": \"launch\",\n      \"servertype\": \"openocd\",\n      \"cwd\": \"${workspaceRoot}\",\n      \"executable\": \"${workspaceRoot}/boards/breezy/build/rosflight_NAZE_Debug.elf\",\n      \"device\": \"STM32F103\",\n      \"svdFile\": \"/path/to/STM32F103.svd\",\n      \"configFiles\": [\n        \"interface/stlink-v2.cfg\",\n        \"target/stm32f1x.cfg\"\n      ],\n      \"runToMain\": true\n    }\n  ]\n}\n</code></pre> <p>Be sure to edit the values of <code>\"svdFile\"</code> to point to the respective SVD files you downloaded earlier.</p> <p>To start debugging, enter the debug pane in VS Code, select the desired configuration, then click the green arrow to start debugging. The shortcut key <code>F5</code> will also launch the last-selected debug configuration.</p> <p>More details on the configuration and use of the <code>Cortex-Debug</code> extension can be found here and here.</p>"},{"location":"developer-guide/firmware/debugging/#stm32cubeide","title":"STM32cubeIDE","text":""},{"location":"developer-guide/firmware/unit-tests/","title":"Building and Running Unit Tests","text":"<p>Contributions will need to pass our continuous integration unit tests before merging. To test your contributions against these tests, you'll first need to install Eigen and gtest:</p> <pre><code>sudo apt install build-essential libgtest-dev libeigen3-dev cmake\n</code></pre>"},{"location":"developer-guide/firmware/unit-tests/#compile-gtest","title":"Compile gtest","text":"<p>You just downloaded a bunch of source files, which you now have to go build</p> <pre><code>cd /usr/src/gtest\nsudo cmake CMakeLists.txt\nsudo make\n</code></pre> <p>Copy the archive files you just built to the <code>/usr/lib</code> directory so CMake can find them later:</p> <pre><code>sudo cp ./lib/libgtest*.a /usr/lib\n</code></pre>"},{"location":"developer-guide/firmware/unit-tests/#run-the-test-script","title":"Run the Test Script","text":"<p>The simplest way to run the unit tests is to use the testing script. This script first checks that the firmware compiles, then runs the unit tests. This is the same script used on the continuous integration server, so this is a great way to check that your code will pass the tests before opening a pull request. Run the test script with</p> <pre><code>cd &lt;firmware_directory&gt;\n./scripts/run_tests.sh\n</code></pre>"},{"location":"developer-guide/firmware/unit-tests/#manually-build-and-run-the-unit-tests","title":"Manually Build and Run the Unit Tests","text":"<p>If you want to manually build and run the unit tests, first build them with the following commands:</p> <pre><code>cd &lt;firmware_directory&gt;\nmkdir build\ncd build\ncmake .. -DBUILD_TEST=TRUE\nmake\n</code></pre> <p>Then run them with:</p> <pre><code>./test/unit_tests\n</code></pre>"},{"location":"developer-guide/rosplane/parameter-management/","title":"Parameter Management","text":""},{"location":"developer-guide/rosplane/parameter-management/#overview","title":"Overview","text":"<p>In ROSplane, all internal variables are represented as ROS2 parameters. This enables easy loading, tuning, and saving parameters of various ROSplane modules without needing to rebuild. ROS2 parameters can also be changed dynamically, enabling live editing and tuning of the system. </p> <p>For a good introduction to ROS2 parameters and the CLI tools, see the ROS2 parameter CLI documentation. For an introduction to the parameter system using the ROS2 client libraries, see ROS2 parameter client libraries documentation.</p>"},{"location":"developer-guide/rosplane/parameter-management/#parameter-manager-class","title":"Parameter Manager class","text":"<p>A <code>param_manager</code> class has been created to manage the ROS interface required when dealing with parameters. Specifically, a <code>param_manager</code> object handles the declaration and updates of parameters. Since a base class publicly owns the <code>param_manager</code>, derived classes will have access to any parent class's parameters, if needed. This also allows derived classes to define parameters close to where they will be used in the derived class, helping with readability.</p> <p>For example, the <code>controller_base</code> class declares a <code>frequency</code> variable, which defines the rate of the control loops. This same parameter is needed in other derived classes, like the <code>controller_successive_loop</code> class. Since we declare the parameter in the <code>controller_base</code> class, the <code>controller_successive_loop</code> class will have access to the <code>frequency</code> parameter without having to redefine it.</p>"},{"location":"developer-guide/rosplane/parameter-management/#usage","title":"Usage","text":""},{"location":"developer-guide/rosplane/parameter-management/#declaration","title":"Declaration","text":"<p>To use the <code>param_manager</code> to define your own parameters, do the following:</p> <ol> <li>Declare an instance of <code>param_manager</code> in your class, or ensure that a parent class has a public or protected instance of <code>param_manager</code>.</li> <li>Initialize the <code>param_manager</code> object with a pointer to the ROS2 node object associated with the parameters.</li> <li>In the constructor, use <code>param_manager::declare_param(std::string &lt;PARAM_NAME&gt;, &lt;PARAM&gt;)</code> to declare parameters of type double, bool, or string, where <code>&lt;PARAM&gt;</code> is the default value for the parameter.<ul> <li>Use <code>param_manager::declare_int(std::string &lt;PARAM_NAME&gt;, &lt;PARAM&gt;)</code> to declare an integer parameter.</li> </ul> </li> <li>In the constructor, use <code>param_manager::set_parameters()</code> to load any parameters that have changed on launch to the <code>param_manager</code> object.</li> </ol> <p>Note</p> <p>The <code>param_manager::set_parameters()</code> call is important when a node is loaded with parameters from a file on launch. Not making this call will mean that the parameters stored in the <code>param_manager</code> object are out of sync with the ROS2 parameters.</p> <p>These steps will register your parameters with ROS2, allowing you to change them dynamically or load them from a launch file.</p>"},{"location":"developer-guide/rosplane/parameter-management/#using-parameters-in-code","title":"Using parameters in code","text":"<p>After declaring the parameters with <code>param_manager::declare_param</code> or <code>param_manager::declare_int</code>, you need to allocate variables in your code to hold the values of the parameters. Get the parameter value by using the appropriate function call:</p> <ul> <li><code>param_manager::get_double(std::string &lt;PARAM_NAME&gt;)</code></li> <li><code>param_manager::get_bool(std::string &lt;PARAM_NAME&gt;)</code></li> <li><code>param_manager::get_string(std::string &lt;PARAM_NAME&gt;)</code></li> <li><code>param_manager::get_int(std::string &lt;PARAM_NAME&gt;)</code></li> </ul> <p>Note that the return type of <code>param_manager::get_int</code> is <code>int_64</code>, since that is how ROS2 internally stores integers.</p>"},{"location":"developer-guide/rosplane/parameter-management/#defining-parameters-with-a-parameter-file","title":"Defining parameters with a parameter file","text":"<p>We recommend using a YAML file to hold all of the parameters for a given node. This file can be loaded at launch time so that all parameters are updated with the values in the launch file. This means you don't have to change the default values in code (which would require a rebuild) to make sure a node gets launched with the correct values.</p> <p>To do this, add the <code>parameters=[\"/path/to/parameter/file\"]</code> to a node's launch argument. See <code>rosplane.launch.py</code> for an example.</p>"},{"location":"developer-guide/rosplane/parameter-management/#updating-parameters","title":"Updating Parameters","text":"<p>Parameters can be updated from the command line using normal ROS2 commands. See the ROS2 parameter CLI tools documentation for more information on how to interface with these parameters from the command line.</p> <p>Note</p> <p>Be sure to create a callback for your parameter changes, especially if you use a <code>param_manager</code> object. ROS2 will send a list of changed parameters to this callback when the parameters are changed, allowing you to update the internally stored value in the <code>param_manager</code>. Otherwise, your internally stored values will be out of sync with the ROS2 parameters, and it will likely not function correctly. See the <code>controller_base</code> or <code>estimator_base</code> or <code>path_planner</code> code for an example of the callbacks.</p>"},{"location":"developer-guide/rosplane/controller/controller-base/","title":"Controller Base","text":""},{"location":"developer-guide/rosplane/controller/controller-base/#overview","title":"Overview","text":"<p>The controller base implements the basic ROS interfaces for the controller. This includes setting up subscribers, publishers and initializing parameter management. The idea of the base class, is that all interfacing with ROS and shared resources across all inheritance levels happens or are contained in this class.</p>"},{"location":"developer-guide/rosplane/controller/controller-base/#ros-interfaces","title":"ROS interfaces","text":"<p>The controller base has the following ROS interactions.</p> Figure 1: Controller's ROS interactions. <p>The controller has four ROS interfaces that are tracked as member variables of the class. These interfaces are the only points of contact that influence the every layer of the controller along side the node parameters. Each of the callbacks for the subscribers are also contained in <code>controller_base</code>.</p> ROS Interface Topic Explanation Message Type <code>actuators_pub_</code> <code>/command</code> Publishes the acutator commands for the aircraft. The publishing rate is controller by the <code>timer_</code> object. Command.msg <code>internals_pub_</code> <code>/controller_inners_debug</code> Publishes the intermediate values created by the outer control loops. Published simultaneously as the commands when there is at least one subscriber to the topic. ControllerInnersDebug.msg <code>controller_commands_sub_</code> <code>/controller_commands</code> Subscribes to the commands for the controller. ControllerCommands.msg <code>vehicle_state_sub_</code> <code>/estimated_state</code> Subscribes to the estimated state of the aircraft. State.msg <p>Note</p> <p>The command message is from the <code>rosflight_msgs</code> package not the <code>rosplane_msgs</code> package.</p>"},{"location":"developer-guide/rosplane/controller/controller-base/#parameter-management","title":"Parameter Management","text":"<p>See the Parameter Management page for more details on how parameter management works.</p>"},{"location":"developer-guide/rosplane/controller/controller-base/#list-of-parameters","title":"List of Parameters","text":"Parameter Explanation Range pwm_rad_e Radian to PWM conversion for the elevator. \\geq 1.0 (double) pwm_rad_a Radian to PWM conversion for the ailerons. \\geq 1.0 (double) pwm_rad_r Radian to PWM conversion for the rudder. \\geq 1.0 (double) frequency Frequency of the timer, effective control loop closure frequency. \\geq 100 (hertz, int)"},{"location":"developer-guide/rosplane/controller/controller-base/#modifying-controller-base","title":"Modifying Controller Base","text":"<p>The <code>controller_base</code> class should only contain things that are necessary for each layer of the controller. If you are considering adding something to the controller, but it only applies to one layer, perhaps reconsider. All ROS related items should also be stored here. For example, if you needed to use another topic subscription, the new subscriber should be created and stored in <code>controller_base</code>.</p> <p>As shown in the Controller Software Architecture page, you may need to modify the <code>main</code> function in <code>controller_base.cpp</code> to use a newly implemented controller.</p>"},{"location":"developer-guide/rosplane/controller/controller-general-overview/","title":"ROSplane Controller","text":""},{"location":"developer-guide/rosplane/controller/controller-general-overview/#overview","title":"Overview","text":"<p>The ROSplane controller generates the controller commands to achieve the commanded states that the path follower directs. The controller has the basic function of controlling roll, pitch, yaw, airspeed, course and altitude. Higher functions of controlling position and tracking paths is handled by other nodes, the path follower and manager specifically. To gain the best understanding of the Controller and its role, read chapter 1 of the UAV book, or the ROSplane Overview page.</p>"},{"location":"developer-guide/rosplane/controller/controller-general-overview/#interfaces","title":"Interfaces","text":"Figure 1: Controller's ROS interactions."},{"location":"developer-guide/rosplane/controller/controller-general-overview/#input","title":"Input","text":"<p>The controller receives controller commands using the ControllerCommands message on the <code>\\controller_commands</code> topic from the <code>path_follower</code> node.  This set of commands are outlined below, along with a short explanation of each.</p> Message Field Explanation Units header This contains time stamp information. Time in Seconds and Nanoseconds (int) va_c The commanded airspeed. Meters per second (float) h_c The commanded altitude. Meters (float) chi_c The commanded course. Radians (float) phi_ff Feedforward roll term (for orbits) Radians (float) aux[4] Four array of auxiliary commands None (float) aux_valid Indicates whether aux vector contains actual information. True/False (bool) <p>The controller uses these targets to control the aircraft. This drives the aircraft to approach and follow the path as the path_follower commands. See the Path Follower page for more information. See the Successive Loop Closure Controller Outline for more information on how these commands are used specifically.</p> <p>Note</p> <p>Poor path performance may be due to controller or the path follower, see the Tuning Guide in the User Guide section for more details.</p>"},{"location":"developer-guide/rosplane/controller/controller-general-overview/#output","title":"Output","text":"<p>The controller calculates the control surface outputs in percent deflection (based around zero) and throttle. It formats and the publishes these outputs in the Command message on the <code>/command</code> topic. There are a further four auxiliary channels that can be used in the Command message, however they are unused typically. A summary of the parts of the command message are as follows.</p> Message Field Explanation Units header This contains time stamp information. Time in Seconds and Nanoseconds (int) mode The control mode (used in multi-rotors) None (int) ignore A bitmask to ignore particular values. None (int) x Aileron Command Percent deflection in direction [-1.0, 1.0] (float) y Elevator Command Percent deflection in direction [-1.0, 1.0] (float) z Rudder Command Percent deflection in direction [-1.0, 1.0] (float) f Throttle Command Percent of full throttle [0.0, 1.0] (float) <p>These are passed to <code>rosflight_io</code>, which formats them into MAVLink messages and forwards them onto the FCU.</p> <p>Note</p> <p>For this to work the parameters on the <code>rosflight_firmware</code> must be set to work for an airplane. See the User Guide on first time start up or README.md for the repository for more details on firmware setup.</p>"},{"location":"developer-guide/rosplane/controller/controller-general-overview/#running-the-controller","title":"Running the Controller","text":"<p>As mentioned in the ROSplane ROS overview, the controller is in the main <code>rosplane</code> ROS package. The ROS executable is <code>rosplane_controller</code>, yielding the run command:</p> <p><code>ros2 run rosplane rosplane_controller</code></p> <p>The type of controller used is passed right after the executable name, substitute <code>control_type</code> for controller being used.</p> <p><code>ros2 run rosplane rosplane_controller control_type</code></p> <p>To pass a set of parameters for the controller from a yaml file using the <code>--ros-args</code> option.</p> <p><code>ros2 run rosplane rosplane_controller --ros-args --params-file path/to/params.yaml</code></p> <p>Putting it all together,</p> <p><code>ros2 run rosplane rosplane_controller control_type --ros-args --params-file path/to/params.yaml</code></p> <p>A table of arguments and parameter files that work out of the box is given in the following table.</p> <p>Note</p> <p>Filepaths will need to be altered to work.</p> <p>Note</p> <p>The most common way of running the controller is in through a launch file with the rest of the ROSplane pipeline running as well. See the ROSplane Overview in the Developer and User Guides for more details.</p> Argument Explanation Values --params-file The parameters file that contains the gains and other important parameters. <code>rosflight_ws/src/rosplane/rosplane/params/anaconda_autopilot_params.yaml</code>,<code>rosflight_ws/src/rosplane/rosplane/params/skyhunter_autopilot_params.yaml</code> control_type These arguements are passed directly to the main function defined in the controller. <code>default</code>, <code>total_energy</code>"},{"location":"developer-guide/rosplane/controller/controller-outline/","title":"Successive Loop Closure Controller","text":""},{"location":"developer-guide/rosplane/controller/controller-outline/#overview","title":"Overview","text":"<p>The control scheme used by default in ROSplane comes from the book Small Unmannded Aircraft: Theory and Practice by Randal Beard and Timothy McLain. A full and in depth description of the theory behind this controller is outlined in chapter 6. Additionally, many simplifing assumptions are made some of which will be mentioned, but the rationale not explored. These too are found in the book, in chapters 3, 4 and 5. A link to the most up to date book can be found on the GitHub page for the book. This section of the documentation is to briefly outline the important, practical parts of the controller to be useful in understanding how to tune or modify the existing code or algorithm for a developer. A good primer on PID control can be found here.</p> <p>The control algortihm is split into two parts: Lateral-directional Autopilot and Longitudinal Autopilot. The lateral and longitudinal dynamics are assumed to be decoupled as discussed in Section 6.1 of Small Unmannded Aircraft. This allows us to develop a controller for each set of dynamics to simplify the controller design.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#successive-loop-closure","title":"Successive Loop Closure","text":"<p>For a full discussion of PID successive loop closure, which is used heavily through out the entire controller, read section 6.1 in the book. One major assumption used is that the inner loops are much faster (more than ten times faster) than the outer loops. This means that the bandwidth seperation should be seperated by a factor of 10. See end of section 6.1.1 Course Hold using Commanded Roll in the book for a more thorough discussion. A significant advantage of successive loop closure is that gains are tuned independently. Starting from the inner loops, tune the response and then tune the outer loop.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#nomenclature","title":"Nomenclature","text":"Symbol Meaning Range \\large{\\boldsymbol{\\chi}} Course/Heading [-\\pi,\\pi) \\large{\\boldsymbol{\\phi}} Roll [-\\pi,\\pi) \\large{\\boldsymbol{\\theta}} Theta [-\\pi,\\pi) \\large{\\boldsymbol{\\psi}} Yaw [-\\pi,\\pi) \\large{\\boldsymbol{h}} Altitude \\large{p} Roll Rate \\large{q} Pitch Rate \\large{r} Yaw Rate \\large{V_a} Airspeed \\large{\\boldsymbol{\\delta_i}} Command percent defelection of control surface i [-1.0,1.0] \\large{\\boldsymbol{e_a}} Error in state variable a \\large{\\boldsymbol{a^c}} Commanded value of state variable a \\large{\\boldsymbol{k_{p_{a}}}} Proportional gain for state variable a \\large{\\boldsymbol{k_{d_{a}}}} Derivative gain for state variable a \\large{\\boldsymbol{k_{i_{a}}}} Integral gain for state variable a \\large{\\boldsymbol{p_{wo}}} Washout filter bandwidth \\large{\\boldsymbol{P}} Plant transfer function \\large{\\boldsymbol{s}} Laplace operator"},{"location":"developer-guide/rosplane/controller/controller-outline/#lateral-directional-autopilot","title":"Lateral-directional Autopilot","text":"<p>The autopilot uses induced roll to control changes in course. The Lateral-directional Autopilot also uses a yaw damper to damp the dutch roll mode that can be induced by changes in roll.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#course-loop","title":"Course Loop","text":"<p>In figure 1, the entire control loop for the course is shown. This loop allows for tracking of ramp and step commands in course. Since the inner loop is tuned first and influences the outer loop tune, we will discuss it first.</p> Figure 1: Lateral-directional Autopilot Control Loop"},{"location":"developer-guide/rosplane/controller/controller-outline/#inner-loop","title":"Inner Loop","text":"<p>The inner loop calculates the required percent deflection in the ailerons, \\boldsymbol{\\delta_a}, to acheive the commanded roll angle generated by the outer loop. This loop is a PD loop, meaning that it uses only a proportional and derivative control.</p> <p>Note</p> <p>That the derivative gain does not act on the rate of change of the error but of the direct roll rate, p.</p> <p>The proportional gain acts on the error given by the estimated roll and the commanded roll. This loop does not use integral contol to ensure that it closes much faster than the outer loop. This bandwidth seperation helps the controller perform smoothly. See the specific page on the Course Loop for details on tuning and common pitfalls. For more details on how the roll rate and the roll angle are calculated, see the Estimator page. The output for the inner loop is routed into the outer loop.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#outer-loop","title":"Outer Loop","text":"<p>The outer loop calculates the commanded roll angle, \\boldsymbol{\\phi}, based on the error in the course, \\boldsymbol{\\chi}. This is a PI loop, meaning that it uses only proportional and integral control. The proportional gain acts on the error between the estimated course \\boldsymbol{\\chi} and the commanded course \\boldsymbol{\\chi}. The integral gain acts on the same error, ensuring that errors in course are driven to zero.</p> <p>Note</p> <p>The PI loop allows for only constant error in ramp inputs (orbits) and for no error to step inputs (path following commands).</p> <p>See the specific page on the Course Loop for details on tuning and common pitfalls. For more details on how course is estimated and measured, see the Estimator page. These loops combine to give complete control of the course of the aircraft.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#yaw-damper","title":"Yaw Damper","text":"<p>The yaw damper allows for effective damping of undesirable yaw modes induced by rolling. This is done by using the rudder to control the yaw rate, r, to zero. Not all yaw rates should be controlled to zero since this would disallow turning. A washout filter is used to only damp high frequency yaw rates. In effect, this control only 'turns on' if the frequency of the yaw rate is high enough. For mor information see the Yaw Damper page.</p> Figure 2: Yaw Damper Control Loop"},{"location":"developer-guide/rosplane/controller/controller-outline/#longitudinal-autopilot","title":"Longitudinal Autopilot","text":"<p>The longitudinal autopilot controls the longitudinal dynamics of the aircraft. This means that the loop controls altitude, pitch and airspeed.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#altitude-loop","title":"Altitude Loop","text":"<p>The altitude loop utilizes successive loop closure to control altitude. It uses the elevator to control the pitch of the aircraft, and then controls using commanded pitch the altitude. This loop can track step and ramp commands.</p> Figure 3: Altitude Control Loop"},{"location":"developer-guide/rosplane/controller/controller-outline/#inner-loop_1","title":"Inner Loop","text":"<p>The inner loop controls the pitch, \\boldsymbol{\\theta}. It does so by calculating the necessary \\boldsymbol{\\delta_e} to acheive the commanded pitch. This is a PD loop, this means that there is often a small DC offset to the commanded pitch. This does not affect the performance of the overall altitude loop. Like the inner loop of the course control, the derivative gain acts on the measured pitch rate rather than the error derivative.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#outer-loop_1","title":"Outer Loop","text":"<p>The outer loop is a PI loop. It uses the error in the altitude, h, and integral of the error of altitude to drive the error to zero for steps and for ramps. The commanded altitude is capped using a scheme described in the Altitude Loop page. In practice, the altitude loop is often slower when the commanded altitude is descending and faster when ascending. This is because the airspeed is coupled to the altitude. While descending the controller will attempt to maintain airspeed. This can also result in more overshoot while descending.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#airspeed-loop","title":"Airspeed Loop","text":"<p>The Airspeed loop is a PI loop. It reacts to the straight forward error in commanded airspeed V_a^c given by the waypoint mission. It generates the required throttle, \\delta_t, to acheive the commanded airspeed. This is suffecient because of the natural damping of the drag on the aircraft. In practice, the loop performs well, but is prone to small fluctuations (on the order of \\pm 1 \\frac{m}{s}) due to the differential pressure sensor fluctuating because of wind and other disturbances.</p> Figure 4: Airspeed using throttle control loop"},{"location":"developer-guide/rosplane/controller/controller-outline/#controller-outputs","title":"Controller Outputs","text":"<p>What the entire controller outputs is a set of 4 control efforts that correspond to the 4 major control surfaces on the aircraft. These are the elevator, ailerons, rudder and the throttle. The controller can easily be switched to outputing up to 8 outputs, using the aux channels of the Commands Message. These outputs are fed directly to rosflight_io and then passed along to the microcontroller and finally actuated on the physical or simulated aircraft. The controller is the exposed portion of ROSplane to ROSflight.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#important-notes","title":"Important Notes","text":"<p>The controller does not directly control the position. In the ROSplane overview page, it shows how the Path Follower feeds into the controller. The Path Follwer generates commands that result in the position control of the aircraft. For a better understanding of this realtionship visit the Path Follower page.</p>"},{"location":"developer-guide/rosplane/controller/controller-outline/#software-architecture","title":"Software Architecture","text":"<p>The Successive Loop Closure Controller (SLCC) inherits from the state machine class, (see Software Architecture for more details) and implements the state function for each of the states. This state function is then populated with the desired control during each phase of flight (see State Machine for more details on control during each state). The state functions split control into longitudinal and lateral control, this allows for inheritance of this class an only override longitudinal or lateral control (see Total Energy Control for an example of how this is done).</p> Figure 5: An example of an implementation of a state function, in this case the altitude hold state. <p>The lateral and longitudinal control functions activate particular control loops necessary.</p> Figure 6: An example of an implementation of a lateral and longitudinal control, in this case during the altitude hold state. <p>Each control loop gets its own function and it follows a specific format. This format is pictured below, but a full outline is given in the .cpp file for the SLCC.</p> <p>Note</p> <p>All of the PID is implemented but the gains if not using a particular control (proportional/derivative/integral) are zero.</p> Figure 7: An example of an implementation of a control loop, in this case the roll loop (inner course loop)."},{"location":"developer-guide/rosplane/controller/controller-outline/#parameters","title":"Parameters","text":"<p>These values are typically held in a .yaml file. For the default values, check the .cpp file.</p> Parameter Explanation Range max_takeoff_throttle Trottle saturation level during the takeoff zone. (0.0, 1.0) (double) c_kp The proportional gain on the outer course loop. \\geq 0.0 (double) c_kd The derivative gain on the outer course loop. \\leq 0.0 (double) c_ki The integral gain on the outer course loop. \\geq 0.0 (double) max_roll Commanded roll saturation limit. \\geq 0.0 (double)(degrees) cmd_takeoff_pitch Commanded pitch while in takeoff state. \\geq 0.0 (double)(degrees) r_kp The proportional gain on the inner course loop. \\geq 0.0 (double) r_kd The derivative gain on the inner course loop. \\geq 0.0 (double) r_ki The integral gain on the inner course loop. \\geq 0.0 (double) max_a Saturation limit for the ailerons \\geq 0.0 (double) trim_a Trim value for the ailerons. \\geq 0.0 (double) a_kp The proportional gain on the outer altitude loop. \\geq 0.0 (double) a_kd The derivative gain on the outer altitude loop. \\geq 0.0 (double) a_ki The integral gain on the outer altitude loop. \\geq 0.0 (double) max_pitch Commanded pitch saturation limit. \\geq 0.0 (double)(degrees) p_kp The proportional gain on the inner altitude loop. \\leq 0.0 (double) p_kd The derivative gain on the inner altitude loop. \\leq 0.0 (double) p_ki The integral gain on the inner altitude loop. \\leq 0.0 (double) max_e Saturation limit for the elevator \\geq 0.0 (double) trim_e Trim value for the elevator. \\geq 0.0 (double) y_pwo The yaw damper washout filter cutoff frequency. \\leq 0.0 (double)(radians/s) y_kr Control gain on yaw damper. \\leq 0.0 (double) a_t_kp The proportional gain on the airspeed loop. \\geq 0.0 (double) a_t_kd The derivative gain on the airspeed loop. \\geq 0.0 (double) a_t_ki The integral gain on the airspeed loop. \\geq 0.0 (double) max_t Saturation limit for the throttle. \\geq 0.0 (double) trim_t Trim value for the throttle. \\geq 0.0 (double) tau Dirty derivative low pass filter gain for airspeed. \\geq 0.0 (double)"},{"location":"developer-guide/rosplane/controller/controller-software-architecture/","title":"Controller Software Architecture","text":""},{"location":"developer-guide/rosplane/controller/controller-software-architecture/#overview","title":"Overview","text":"<p>The controller makes use of inheritance to make the controller more modular. This creates a hierarchy of classes that each take on a responsibility. This means that a user that modifies the controller only has to inherit from a particular class make the modifications only to the portions of the code that matter to them, and then continue to use the other parts of the controller. An example of this is provided in the code. The total energy controller exemplifies this by inheriting and only changing just a few key functions. The aim of this architecture is to make the developer's job easier.</p>"},{"location":"developer-guide/rosplane/controller/controller-software-architecture/#inheritance-scheme","title":"Inheritance Scheme","text":"<p>The controller starts off with the <code>controller_base</code> class. This contains all of the interface with ROS. The next layer, <code>controller_state_machine</code>, implements a basic state machine for the controller. These states control which commands are happening at what time. An example of how this may be used is, ensuring the aircraft is at altitude before attempting major maneuvers. Following the state machine is the actual control scheme. By default we use a successive loop closure scheme, <code>controller_successive_loop</code>. This layer calculates the control errors and necessary actuator deflections to track commands.</p> <p> Figure 1: Controller class inheritance structure. <p></p> <p>This scheme was chosen to limit code duplication. A composition structure would have resulted in code duplication between controllers. Guides on how and where to modify each part of this structure can be found on the respective pages in the Developer Guide. This page does go over the basics of how to implement a controller changes in terms of overall architecture.</p>"},{"location":"developer-guide/rosplane/controller/controller-software-architecture/#implementing-a-new-controller","title":"Implementing A New Controller","text":"Figure 2: Options for implementing a new controller. <p>The total energy controller in the <code>rosplane</code> package, shows in a practical way how to implement a new controller. This section is meant to only give a high level overview of how this can be done. The first step is to identify where your changes should be made. This means determining which class the change belongs in. Consult the class pages for more information on where the best fit for your controller would be. The next step is to define a new class that inherits from class you are changing. Override the functions of interest. Next if the inherited class is not at the bottom of the inheritance chain, you will have to modify (duplicate but only change the inheritance, this is to not break default behavior) the controller classes further down the chain to inherit from your class rather than the original. This is to avoid a multiple inheritance problem (inheritance diamond).</p> <p>To add your new controller as an option to be launched you will need to make a few edits. To be clear, you add your new final controller, (<code>new_controller</code> or <code>copy_of_controller</code> in the diagram) as an option. These edits are as follows:</p> <ul> <li>Add new controller to the CMakeLists.txt.<ul> <li>The best examples are found in the CMakeLists.txt.</li> <li>Be sure to include the <code>.cpp</code> files.</li> </ul> </li> </ul> <p> Figure 3: Location in <code>CMakeLists.txt</code> to add the new controller's <code>.cpp</code> file(s). <p></p> <ul> <li>First import the new controller by adding its header file to <code>controller_base.cpp</code>.</li> </ul> <p> Figure 4: Location in <code>controller_base.cpp</code> to import new controller's header file. <p></p> <ul> <li>Next you need to add the new controller as an option to the <code>main</code> function. The argument to the main function is the name/activation string for the control. This is passed in on launch of ROSplane (see Launching ROSplane in the User Guide for more details).</li> </ul> <p> Figure 5: Location in <code>controller_base.cpp</code> to add option to select control type. <p></p> <p>If this is done correctly, then you should be able to simply change between control schemes with only an argument to a launch file. This will allow for easier testing where you can use a more tested controller initially and but swap to a new controller when convenient.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/","title":"Controller State Machine","text":""},{"location":"developer-guide/rosplane/controller/controller-state-machine/#state-machine-overview","title":"State Machine Overview","text":"<p>The controller state machine uses discrete states to turn on and off particular controls for a more stable flight. These regimes are designed so that particular mission objectives are only activated when particular conditions are met. In the default implementation this is controlled based on the aircraft's altitude. Though, in practice these states could be effected by any input from a ROS topic. The states are pictured below, and the differences in state are explored in the next section.</p> Figure 1: Controller state machine."},{"location":"developer-guide/rosplane/controller/controller-state-machine/#states","title":"States","text":"<p>This section describes all of the states and what control is active during that phase of flight.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/#takeoff","title":"Takeoff","text":"<p>In the takeoff state, the commanded airspeed is set to cruise, the commanded pitch is held constant and roll is controlled to zero. This results in a steady takeoff directly along the runway. The deactivation of course control means that the aircraft will not attempt to maneuver while too close to the ground. The takeoff regime is only below a certain cutoff altitude. After passing this threshold it moves into the climb state.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/#climb","title":"Climb","text":"<p>The climb state commands altitude and airspeed as normal, but still controls roll to zero. This means that the aircraft will proceed directly ahead until it is withing a cutoff (see Params section) of commanded altitude. Deactivating course control allows for the aircraft to gain enough altitude to be clear of all obstacles before attempting to follow the waypoint mission. Once within a cutoff of the commanded altitude, the state transitions to altitude hold. If the aircraft dips beneath the takeoff threshold, it will enter the takeoff state again.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/#altitude-hold","title":"Altitude Hold","text":"<p>In altitude hold all control loops are closed normally.  The aircraft will fly the waypoint mission as normal. If the aircraft dips beneath the takeoff cutoff, the state transitions to takeoff again.</p>"},{"location":"developer-guide/rosplane/controller/controller-state-machine/#code-architecture","title":"Code Architecture","text":"<p>The state machine's architecture allows for different aspects of the control to be modified. It simply defines a virtual method to be implemented by a child that will control during the particular state the aircraft is in. The state method is implemented in the child, only using the controls necessary for that phase of flight (see the Architecture section of the Successive Loop Closure).</p> Figure 2: Code snippet from the state machine."},{"location":"developer-guide/rosplane/controller/controller-state-machine/#parameters","title":"Parameters","text":"Parameter Explanation Range alt_toz The altitude of the takeoff zone cutoff. \\geq 0.0 (double) alt_hz The altitude command saturation limit, and difference required to transition into altitude hold. \\geq 0.0 (double)"},{"location":"developer-guide/rosplane/controller/controller-total-energy/","title":"Total Energy Controller","text":""},{"location":"developer-guide/rosplane/controller/controller-total-energy/#overview","title":"Overview","text":"<p>The total energy control system approach (TECS) differs from the successive loop closure controller in its control of airspeed and altitude. It does this by calculating the total energy of the system, both potential and kinetic and controlling it to the desired energy. A more in depth treatment of of TECS see Section 6.2 in the UAV book.</p> <p>The TECS controller has been included in ROSplane not only to provide control of the aircraft but to also demonstrate how to easily modify the controller (see Software Architecture and the following section for more details). The TECS controller calculates the desired kinetic and potential energy, using references from the commanded airspeed and altitude. It then calculates the current kinetic and potential energies and finds the kinetic and potential errors. It combines these errors, and the throttle control loop uses a PI loop to drive this total energy error to zero. The energy errors are also used to find a balance error. This is the error in the ratio of potential to kinetic energy. Pitch is then controlled by a PI loop to drive the balance error to zero. Essentially the throttle allows for the total energy to rise as it adds or allows drag to subtract energy from the system. The pitch loop controls how much of that input energy is in potential versus kinetic energy</p> <p>This approach can have advantages because it deals with the coupling of airspeed and altitude. In the successive loop closure controller (SLCC), it assumes a decoupling of airspeed and altitude which can present tuning issues, though they are not insurmountable.</p>"},{"location":"developer-guide/rosplane/controller/controller-total-energy/#software-architecture","title":"Software Architecture","text":"<p>The TECS controller provides an excellent template on implementing a new controller. Since the changes to the total energy controller are only in the longitudinal control and the rest are the same as the SLCC it inherits directly from <code>controller_successive_loop</code> and only overrides the longitudinal functions for each state.</p> Figure 1: Total Energy Controller's overriden longitudinal control for the altitude hold state."},{"location":"developer-guide/rosplane/controller/controller-total-energy/#parameters","title":"Parameters","text":"Parameter Explanation Range e_kp Total energy error proportional gain, used in throttle control. \\geq 0.0 (double) e_ki Total energy error integral gain, used in throttle control. \\geq 0.0 (double) e_kd Total energy error derivative gain, used in throttle control. \\geq 0.0 (double) l_kp Balance energy error proportional gain, used in throttle control. \\geq 0.0 (double) l_ki Balance energy error integral gain, used in throttle control. \\geq 0.0 (double) l_kd Balance energy error derivative gain, used in throttle control. \\geq 0.0 (double) mass The mass of the aircraft, allowing for calculation of energies. \\geq 0.0 (double)(kg) gravity The gravity experienced by the aircraft, allowing for calculation of potential energy. \\geq 0.0 (double)(\\frac{m}{s}) max_alt_error This is the maximum error in altitude that the total energy loop will use to calculate energy error. \\geq 0.0 (double)(meters)"},{"location":"developer-guide/rosplane/navigation/navigation-overview/","title":"Navigation Overview","text":"<p>The path planning methods used in ROSplane is modeled after the architecture presented in Small Unmanned Aircraft: Theory and Practice by Dr. Randal Beard and Dr. Tim McLain.</p> <p>In their work, the path planning functionality of the aircraft is split into three main parts, as shown in Figure 1.</p> <p>Note</p> <p>This is not a full description of the architecture. For example, the state estimator is not shown, and not all of the inputs to each of the blocks is included. These elements were removed from the figure for simplicity.</p> Figure 1: Path planning architecture - based on Figure 1.1 in Small Unmanned Aircraft: Theory and Practice <p>The high-level path planning is done by the path planner node. The path planner's job is to manage, create, and publish waypoints. Those waypoints are published to the path manager node. The path manager's job is to determine and calculate the appropriate line segments and orbits needed to complete the waypoints. The path manager then publishes these straight lines and waypoints to the path follower.  The job of the path follower is to control the course, airspeed, and altitude of the aircraft to follow these lines and orbits.</p> <p>For more information on each of these nodes, see the related documentation pages for the path planner, the path manager, and the path follower. See also chapters 10-13 of the Small Unmanned Aircraft: Theory and Practice book.</p>"},{"location":"developer-guide/rosplane/navigation/navigation-overview/#changing-the-navigation-stack","title":"Changing the Navigation Stack","text":"<p>The path planner currently takes in a set of user-defined waypoints and follows those waypoints.  This is not useful in all contexts, since in many applications the aircraft needs to take in sensor data and create its own waypoints and paths.</p> <p>For example, we could replace the path planner block with a vision-based guidance block. The vision-based-guidance block would make decisions based on visual data to create waypoints.  However, the interface between the path planner (now the visual-based guidance planner) and the path manager would remain the same.</p> <p>Similarly, the path manager could be adjusted to follow b-splines instead of straight lines and orbits as currently implemented, without affecting the general waypoint management (path planner) or the underlying path following control loops (path follower).</p> <p>The modularity of this framework allows users to \"plug in\" their own algorithms for each of the blocks defined in Figure 1, instead of rewriting the whole path planning stack.</p> <p>Chapter 13 of the Small Unmanned Aircraft: Theory and Practice book contains more detail on implementing a vision-based path planner.</p>"},{"location":"developer-guide/rosplane/navigation/navigation-overview/#running-the-navigation-stack","title":"Running the Navigation Stack","text":"<p>To launch the navigation stack, you will need to launch 3 ROS2 nodes, one for each part of the navigation stack (path planner, manager, and follower).</p> <p>Remember to launch these nodes with the appropriate parameter launch file, as seen in the <code>rosplane.launch.py</code> file.</p>"},{"location":"developer-guide/rosplane/navigation/path-follower/","title":"Path Follower","text":""},{"location":"developer-guide/rosplane/navigation/path-follower/#overview","title":"Overview","text":"<p>The role of the path follower is to generate the correct airspeed, course, and altitude commands for the autopilot such that the aircraft follows the paths published by <code>path_manager</code>.</p> <p>More information on the <code>path_follower</code> can be found in Small Unmanned Aircraft: Theory and Practice by Dr. Randal Beard and Dr. Tim McLain.</p>"},{"location":"developer-guide/rosplane/navigation/path-follower/#path-follower-base","title":"Path Follower Base","text":"<p>The path follower base contains all the ROS2 interfaces required for the path follower. A list of these interfaces is below.</p> <p>The <code>path_follower_base::follow</code> method is a virtual method that should be implemented by a derived class. The <code>path_follower_base</code> publishes the controller commands calculated by the implementation of <code>path_follower_base::follow</code>.</p>"},{"location":"developer-guide/rosplane/navigation/path-follower/#list-of-ros2-interfaces","title":"List of ROS2 Interfaces","text":"ROS2 Interface Topic or Service Explanation Message or Service Type <code>vehicle_state_sub_</code> <code>/estimated_state</code> Subscribes to the estimated aircraft state <code>rosplane_msgs::msg::State</code> <code>current_path_sub_</code> <code>/current_path</code> Subscribes to the current path messages published by <code>path_manager</code> <code>rosplane_msgs::msg::CurrentPath</code> <code>controller_commands_pub_</code> <code>/controller_commands</code> Publishes control commands to the autopilot <code>rosplane_msgs::msg::ControllerCommand</code> <code>update_timer_</code> -- ROS2 timer that controls how frequently <code>controller_commands_pub_</code> publishes --"},{"location":"developer-guide/rosplane/navigation/path-follower/#interface-with-the-autopilot","title":"Interface with the Autopilot","text":"<p>The <code>path_follower</code> node interfaces with the MAV autopilot by publishing to the <code>/controller_commands</code> topic. The <code>/controller_commands</code> topic contains the following information calculated by the <code>path_follower</code>:</p> Member Description Type / units Required <code>header</code> Standard message header that contains a valid timestamp <code>std_msgs::msg::Header</code> Yes <code>va_c</code> Commanded airspeed <code>double</code>, m/s Yes <code>h_c</code> Commanded altitude <code>double</code>, m Yes <code>chi_c</code> Commanded course <code>double</code>, rad Yes <code>phi_ff</code> Feedforward command (for orbits) <code>double</code>, rad No"},{"location":"developer-guide/rosplane/navigation/path-follower/#path-follower-example","title":"Path Follower Example","text":"<p>The <code>path_follower_example</code> class contains the implementation of the <code>path_follower_base::follow</code> method. This method contains the control command computations for straight line and orbit-type paths as outlined in Small Unmanned Aircraft: Theory and Practice.</p>"},{"location":"developer-guide/rosplane/navigation/path-follower/#parameters","title":"Parameters","text":"<p>See the Parameter Management page for more details on how parameter management works.</p>"},{"location":"developer-guide/rosplane/navigation/path-follower/#list-of-parameters","title":"List of Parameters","text":"Parameter Explanation Type / Units Range <code>chi_infty</code> At infinity, the angle at which the aircraft will approach the desired line double (rad) \\frac{\\pi}{2} \\geq \\chi^{\\infty} &gt; 0.0 <code>k_path</code> Constant that determines how quickly commanded course transitions from \\chi^{\\infty} to 0 during line following double &gt; 0.0 <code>k_orbit</code> Constant that determines how quickly commanded course transitions from \\lambda \\frac{\\pi}{2} to 0 during an orbit double &gt; 0.0 <p>Since there are two different types of lines generated by the <code>path_manager</code> (straight lines and orbits), the <code>path_follower</code> uses different parameters to calculate the control output for each path type.</p> <p>For line following, <code>path_follower</code> uses </p> <ul> <li><code>chi_infty</code> and </li> <li><code>k_path</code> to compute the control commands.</li> </ul> <p>As described in Small Unmanned Aircraft: Theory and Practice, these two parameters define a vector field for the commanded course. The <code>chi_infty</code> parameter describes the angle at which the aircratft will approach a target line if the aircraft is infinitely far from the target line. For example, if <code>chi_infty</code> is set to \\frac{\\pi}{2}, then the aircraft will approach the target line at an angle perpindicular to the line when the aircraft is far away.</p> <p>The <code>k_path</code> parameter defines how quickly the vectors at <code>chi_infty</code> \"smooth\" into the target line. When <code>k_path</code> is large, the transition will be abrupt, and when <code>k_path</code> is small, the transition will be smoother.</p> <p>During orbit following, <code>path_follower</code> uses</p> <ul> <li><code>k_orbit</code> to compute the control commands.</li> </ul> <p>If the aircraft is very far away from the orbit, it will align itself so it flies directly at the center of the orbit. The <code>k_orbit</code> parameter is similar to the <code>k_path</code> parameter in that it determines how quickly the commanded angle of the aircraft will change from directly toward the center to the orbit direction.</p> <p>Note</p> <p>When tuning, make sure you are changing the correct gains for the type of line (straight or orbit) the aircraft is tracking. <code>chi_infty</code> and <code>k_path</code> will not affect the orbit performance!</p>"},{"location":"developer-guide/rosplane/navigation/path-follower/#modifying-the-path-follower","title":"Modifying the Path Follower","text":"<p>Changes to any of the ROS2 interface should be done in the <code>path_follower_base</code>.</p> <p>Changes to how <code>path_follower</code> computes control commands to follow paths given by the <code>path_manager</code> should be done in the <code>path_manager_example</code>.</p>"},{"location":"developer-guide/rosplane/navigation/path-manager/","title":"Path Manager","text":""},{"location":"developer-guide/rosplane/navigation/path-manager/#overview","title":"Overview","text":"<p>The path manager is responsible for calculating and publishing the current path to the path follower.  It is split into a base class and an inherited class. The base class handles the ROS2 interfaces (publishing and subscribing) while the inherited class manages the path, i.e., calculates the parameters for the current path.</p> <p>The path manager is designed this way so that the inherited class (how the paths are managed) can be replaced or rewritten without affecting the overlying ROS2 interface.</p> <p>Both the <code>path_manager_base</code> and the <code>path_manager_example</code> are included in the same ROS2 node when compiled, called <code>path_manager</code>. Parameters associated with the <code>path_manager_base</code> or the <code>path_manager_example</code> will therefore be visible under the <code>path_manager</code> ROS2 node.</p> <p>More details about the path manager can be found in Small Unmanned Aircraft: Theory and Practice by Dr. Randal Beard and Dr. Tim McLain.</p>"},{"location":"developer-guide/rosplane/navigation/path-manager/#path-manager-base","title":"Path Manager Base","text":"<p>The path manager base contains all the ROS2 interfaces required for the path manager. A list of these interfaces is below.</p>"},{"location":"developer-guide/rosplane/navigation/path-manager/#list-of-ros2-interfaces","title":"List of ROS2 Interfaces","text":"ROS2 Interface Topic or Service Explanation Message or Service Type <code>vehicle_state_sub_</code> <code>/estimated_state</code> Subscribes to the estimated aircraft state <code>rosplane_msgs::msg::State</code> <code>new_waypoint_sub_</code> <code>/waypoint_path</code> Subscribes to the waypoint messages published by <code>path_planner</code> <code>rosplane_msgs::msg::State</code> <code>current_path_pub_</code> <code>/current_path</code> Publishes the parameters of the current path <code>rosplane_msgs::msg::CurrentPath</code> <code>update_timer_</code> -- ROS2 timer that controls how frequently <code>current_path_pub_</code> publishes --"},{"location":"developer-guide/rosplane/navigation/path-manager/#interface-with-the-path-follower","title":"Interface with the Path Follower","text":"<p>The <code>path_manager</code> node interfaces with the path follower by publishing to the <code>/current_path</code> topic. These messages contain information about the current trajectory, which are either straight lines or circles. </p> <p>Note that the only supported path types are straight lines and circles. Depending on how the <code>path_manager</code> is set up to manage the waypoints, this may not be suitable for your application. See \"Modifying the Path Manager\" for more information. For more information on the path follower, see the Path Follwer documentation.</p>"},{"location":"developer-guide/rosplane/navigation/path-manager/#path-manager-example","title":"Path Manager Example","text":"<p>The <code>path_manager_example</code> class inherits from the <code>path_manager_base</code> class. Specifically, the <code>path_manager_example</code> overrides the <code>path_manager_base::manage</code> method to determine how the path is managed.</p> <p>In the current implementation, <code>path_manager_example</code> decides to manage a waypoint using straight lines and fillets, orbits, or Dubins paths based on the current state of the aircraft, the values of the current ROS2 parameters, and the waypoints given. For example, if the <code>use_chi</code> field on a Waypoint object (see Path Planner for more information) is set to <code>true</code>, then <code>path_manager_example</code> will use a Dubins path to navigate to the next waypoint. If <code>use_chi</code> is set to <code>false</code>, then <code>path_manager_example</code> will use straight lines when navigating in between waypoints and a fillet to manage the corners. See Figure 1 for an example of a real flight path flown using ROSplane with <code>chi_d</code> set to <code>false</code>.</p> Example flight path from an actual flight test showing the straight lines and fillets path type <p>Note that using fillets to manage the corners often means that the aircraft does not actually achieve the waypoint. If this is undesireable in your application, use Dubins paths or another method for the <code>path_manager</code>. </p>"},{"location":"developer-guide/rosplane/navigation/path-manager/#parameters","title":"Parameters","text":"<p>See the Parameter Management page for more details on how parameter management works.</p>"},{"location":"developer-guide/rosplane/navigation/path-manager/#list-of-parameters","title":"List of Parameters","text":"Parameter Explanation Type Range <code>R_min</code> Minimum radius for orbit, fillet, and Dubins paths double \\geq 0.0 <code>orbit_last</code> Specifies whether or not to orbit the last waypoint. If false, <code>param_manager</code> will fly a circuit bool <code>true</code> or <code>false</code>"},{"location":"developer-guide/rosplane/navigation/path-manager/#the-orbit_last-parameter","title":"The <code>orbit_last</code> Parameter","text":"<p>The <code>path_manager</code> node has a parameter named <code>orbit_last</code>. This parameter controls what happens as the aircraft is approaching the last waypoint in the set of waypoints published to the <code>path_manager</code>. If <code>orbit_last</code> is set to <code>true</code>, then <code>path_manager</code> will follow an orbit around the last waypoint.</p> <p>The direction of this waypoint (clockwise or counterclockwise) will be chosen based on which direction requires the least amount of turning. In other words, if the aircraft is angled slightly left as it approaches the waypoint, <code>path_manager</code> will choose to orbit the last waypoint counterclockwise (from a top-down perspective). If the aircraft is pointing slightly right as it approaches the waypoint, it will orbit the waypoint clockwise (from a top-down perspective).</p>"},{"location":"developer-guide/rosplane/navigation/path-manager/#modifying-the-path-manager","title":"Modifying the Path Manager","text":"<p>Changes or additions to any ROS2 interfaces should be done in the <code>path_manager_base</code> field.</p> <p>Changes to how <code>path_manager</code> \"manages\" the waypoints should be done by overriding the <code>path_manager_base::manage</code> method. If you wish to change the way paths are defined, make sure that the <code>/current_path</code> topic is rewritten to contain the required information, and then make sure the <code>path_follower</code> knows how to handle the new definition.</p>"},{"location":"developer-guide/rosplane/navigation/path-planner/","title":"Path Planner","text":""},{"location":"developer-guide/rosplane/navigation/path-planner/#overview","title":"Overview","text":"<p>The path planner is responsible for creating, managing, and publishing waypoints. In the current implementation, the path planner simply maintains a list of user-defined waypoints that the user can add to or clear. The path planner then controls when waypoints are published to the path manager.</p> <p>Another implementation of the path planner (as described in the overview) could include a visual-based path planner. In this case, the path planner would receive sensor input and create and manage its own waypoints instead of a user-defined list of waypoints. However, this new path planner would still be responsible for creating and publishing waypoints. This ensures that the interface between the path planner and the path manager would stay the same, allowing for modularity in the path planner architecture.</p>"},{"location":"developer-guide/rosplane/navigation/path-planner/#interfaces","title":"Interfaces","text":"<p>The path planner is implemented as a standalone ROS2 node, called <code>path_planner</code>. This node subscribes to the topics it needs, provides services available to the user and other nodes, and publishes waypoints to the path manager, called <code>path_manager</code>.</p> <p>The interface between <code>path_planner</code> and <code>path_manager</code> is the <code>/waypoint_path</code> topic,  which publishes messages with the <code>rosplane_msgs::msg::Waypoint</code> type. This message contains information about the waypoint's location in NED (from the origin) or GNSS (LLA) coordinates, the desired airspeed at the waypoint, and the desired heading of the aircraft at the waypoint.</p>"},{"location":"developer-guide/rosplane/navigation/path-planner/#about-waypoints","title":"About Waypoints","text":"<p>The following table contains the data members of the <code>rosplane_msgs::msg::Waypoint</code> objects and a brief description.</p> Member Description Type Required <code>header</code> Standard message header that contains a valid timestamp <code>std_msgs::msg::Header</code> Yes <code>w</code> Waypoint coordinates in NED or GNSS (LLA) <code>std::array&lt;float32, 3&gt;</code> Yes <code>lla</code> Flag to determine if the coordinates are passed in as NED or GNSS <code>bool</code> Yes <code>chi_d</code> Desired course at the waypoint <code>double</code> No <code>use_chi</code> Flag to use the <code>chi_d</code> value at the waypoint or not <code>bool</code> No - defaults to <code>false</code> <code>va_d</code> Desired airspeed at the waypoint <code>double</code> Yes <code>clear_wp_list</code> Clears all waypoints from <code>path_planner</code> and <code>path_manager</code> <code>bool</code> No"},{"location":"developer-guide/rosplane/navigation/path-planner/#notes-on-the-waypoint-object-fields","title":"Notes on the Waypoint object fields","text":"<p>The <code>w</code> field contains the coordinates of the waypoint in either NED coordinates (from the origin, defined as the place where ROSplane initialized) or GNSS coordinates given in LLA (latitude, longitude, and altitude). The GNSS coordinates are converted to NED coordinates by <code>path_planner</code> before sending them to <code>path_manager</code>.</p> <p>The <code>lla</code> field is a flag that tells <code>path_planner</code> if the coordinates provided are in the NED or world (GNSS) frame. Set it to <code>true</code> if the coordinates for the waypoint are given in GNSS coordinates. Note that GNSS and relative waypoints can be used together, meaning that one waypoint could be in the NED frame while the next one is in the global frame, since ROSplane converts global coordinates to the NED frame before publishing them to <code>path_manager</code>. </p> <p>Note</p> <p>Make sure that the <code>lla</code> field is set correctly if you decide to use GNSS coordinates, or your waypoints will be incorrect.</p> <p>The <code>chi_d</code> field controls the desired course at the waypoint. Note that this is only used if the <code>use_chi</code> flag is set to <code>true</code>. </p> <p>The <code>use_chi</code> field determines whether or not the <code>path_manager</code> should pay attention to the desired course (<code>chi_d</code>).  If <code>use_chi</code> is set to <code>true</code> then <code>path_manager</code> will use a Dubins path framework to manage the waypoint. If <code>use_chi</code> is set to <code>false</code>, then <code>path_manager</code> will ignore the desired course and will intead use straight lines and fillets to manage the transitions between waypoints. See the Path Manager documentation for more information on this behavior.</p> <p>The <code>clear_wp_list</code> is used internally by <code>path_planner</code> when the <code>/clear_waypoints</code> service is called. It is recommended to use the service call instead of using this field manually.</p> <p>Warning</p> <p>The <code>header</code>, <code>w</code>, <code>va_d</code>, and <code>lla</code> fields must be valid for every waypoint message sent. Failure to add these fields might crash the path planner or your aircraft.</p>"},{"location":"developer-guide/rosplane/navigation/path-planner/#list-of-ros2-interfaces","title":"List of ROS2 Interfaces","text":"ROS2 Interface Topic or Service Explanation Message or Service Type <code>waypoint_publisher_</code> <code>/waypoint_path</code> Publishes the waypoints to the <code>path_manager</code> <code>rosplane_msgs::msg::Waypoint</code> <code>state_subscription_</code> <code>/estimated_state</code> Subscribes to the estimated state of the aircraft <code>rosplane_msgs::msg::State</code> <code>next_waypoint_service_</code> <code>/publish_next_waypoint</code> Publishes the next stored waypoint <code>std_msgs::srv::Trigger</code> <code>add_waypoint_service_</code> <code>/add_waypoint</code> Adds a new waypoint to list and optionally publishes it <code>rosplane_msgs::srv::AddWaypoint</code> <code>clear_waypoint_service_</code> <code>/clear_waypoints</code> Clears the list of waypoints from the path planner and publishes a clear waypoint command to the <code>path_manager</code> <code>std_msgs::srv::Trigger</code> <code>print_waypoints_service_</code> <code>/print_waypoints</code> Prints the saved waypoints to the terminal. Can be useful when debugging <code>std_msgs::srv::Trigger</code> <code>load_mission_service_</code> <code>/load_mission_from_file</code> Loads a mission from a YAML file <code>rosflight_msgs::srv::ParamFile</code>"},{"location":"developer-guide/rosplane/navigation/path-planner/#parameters","title":"Parameters","text":"<p>See the Parameter Management page for more details on how parameter management works.</p>"},{"location":"developer-guide/rosplane/navigation/path-planner/#list-of-parameters","title":"List of Parameters","text":"Parameter Explanation Type Range <code>num_waypoints_to_publish_at_start</code> Number of waypoints to immediately publish at launch. If no waypoints are added, it will not publish any. int \\geq 0"},{"location":"developer-guide/rosplane/navigation/path-planner/#recommended-usage","title":"Recommended Usage","text":"<p>We recommend using a YAML file and the <code>/load_mission_from_file</code> service from the command line to load and fly waypoints. See the example mission YAML file located at <code>/path/to/rosplane/rosplane/params/fixedwing_mission.yaml</code>.</p> <p>To call the service, run <pre><code>ros2 service call /load_mission_from_file rosflight_msgs::srv::ParamFile \"{filename: &lt;FILENAME&gt;}\"\n</code></pre> where <code>&lt;FILENAME&gt;</code> is the path to the mission YAML file.</p>"},{"location":"user-guide/autonomous-flight/","title":"Autonomous Flight","text":"<p>To perform autonomous flight with ROSflight, we need to send control commands from our companion computer to the firmware. This can be done with ROSplane or ROScopter, which already have completed autonomy stacks developed specifically for ROSflight. We recommend starting with one of these autonomy stacks and building on them to suit your needs. If using a multirotor, follow the ROScopter setup guide to get started. If using a fixed-wing, follow the ROSplane setup guide.</p> <p>However, ROSplane and ROScopter are optional and an entirely different autonomy stack can be used if desired. To use a different autonomy stack, follow this guide.</p>"},{"location":"user-guide/autonomous-flight/#provide-control-from-a-companion-computer","title":"Provide Control from a Companion Computer","text":"<p>Control setpoints are sent to the flight controller by publishing to the <code>/command</code> topic that is advertised by the <code>rosflight_io</code> node. This topic accepts messages of type <code>rosflight_msgs/Command</code>, which have the following structure:</p> <pre><code>std_msgs/Header header\nuint8 mode\nuint8 ignore\nfloat32 x\nfloat32 y\nfloat32 z\nfloat32 f\n</code></pre> <p>The <code>header</code> field is a standard ROS2 message header. The <code>x</code>, <code>y</code>, <code>z</code>, and <code>f</code> fields are the control setpoint values, which are interpreted according to the <code>mode</code> and <code>ignore</code> fields.</p> <p>The following table describes the different values the <code>mode</code> field can take, as well as how the setpoint values are interpreted for each of these modes:</p> Value Enum x y z F 0 <code>MODE_PASS_THROUGH</code> aileron deflection (-1 to 1) elevator deflection (-1 to 1) rudder deflection (-1 to 1) throttle (0 to 1) 1 <code>MODE_ROLLRATE_PITCHRATE_YAWRATE_THROTTLE</code> roll rate (rad/s) pitch rate (rad/s) yaw rate (rad/s) throttle (0 to 1) 2 <code>MODE_ROLL_PITCH_YAWRATE_THROTTLE</code> roll angle (rad) pitch angle (rad) yaw rate (rad/s) throttle (0 to 1) <p>The <code>MODE_PASS_THROUGH</code> mode is used for fixed-wing vehicles to directly specify the control surface deflections and throttle, while the <code>MODE_ROLLRATE_PITCHRATE_YAWRATE_THROTTLE</code> and <code>MODE_ROLL_PITCH_YAWRATE_THROTTLE</code> modes are used for multirotor vehicles to specify the attitude rates or angles, respectively.</p> <p>The <code>ignore</code> field is used if you want to specify control setpoints for some, but not all, of the axes. For example, I may want to specify throttle setpoints to perform altitude hold, while still letting the RC pilot specify the attitude setpoints. The <code>ignore</code> field is a bitmask that can be populated by combining the following values:</p> Value Enum Result 0 <code>IGNORE_NONE</code> Ignore none of the fields (default) 1 <code>IGNORE_X</code> Ignore the <code>x</code> field 2 <code>IGNORE_Y</code> Ignore the <code>y</code> field 4 <code>IGNORE_Z</code> Ignore the <code>z</code> field 8 <code>IGNORE_F</code> Ignore the <code>F</code> field <p>For the previous example, I would set the <code>ignore</code> field to a value of <pre><code>ignore = IGNORE_X | IGNORE_Y | IGNORE_Z\n</code></pre></p> <p>The best practice is to use enum names rather than the actual numeric values for the <code>mode</code> and <code>ignore</code> fields. For example, to specify a multirotor attitude angle command in C++ I might have: <pre><code>#include &lt;rclcpp/rclcpp.hpp&gt;\n#include &lt;rosflight_msgs/msg/command.hpp&gt;\n\nrosflight_msgs::msg::Command msg;\nmsg.header.stamp = node-&gt;get_clock()-&gt;now();\nmsg.mode = rosflight_msgs::msg::Command::MODE_ROLL_PITCH_YAWRATE_THROTTLE;\nmsg.ignore = rosflight_msgs::msg::Command::IGNORE_NONE;\nmsg.x = 0.0;\nmsg.y = 0.0;\nmsg.z = 0.0;\nmsg.f = 0.6;\n</code></pre></p> <p>In Python I might have: <pre><code>import rclpy\nfrom rosflight_msgs.msg import Command\n\nmsg = Command()\nmsg.header.stamp = node.get_clock().now().to_msg()\nmsg.mode = Command.MODE_ROLL_PITCH_YAWRATE_THROTTLE\nmsg.ignore = Command.IGNORE_NONE\nmsg.x = 0.0\nmsg.y = 0.0\nmsg.z = 0.0\nmsg.f = 0.6\n</code></pre> I would then publish this message to the <code>/command</code> topic to forward it to the embedded flight controller.</p> <p>Note</p> <p>If the flight controller does not receive a new command for a defined period of time, it will ignore the old commands and revert to RC control. The length of this timeout period is set by the <code>OFFBOARD_TIMEOUT</code> parameter.</p>"},{"location":"user-guide/flight-controller-setup/","title":"Flight Controller Setup","text":"<p>Note</p> <p>This page contains instructions for flashing pre-built firmware binaries. For instructions on building and flashing from source, see Building and Flashing in the Developer Guide.</p>"},{"location":"user-guide/flight-controller-setup/#compatible-hardware","title":"Compatible Hardware","text":"<p>Currently, the ROSflight firmware only supports an in-development board from AeroVironment, the Varmint. This board is not yet commercially available, but plans are for it to start being sold early 2024.</p> <p>We also plan to add support for the CubePilot Orange, which uses the same H7 processor as the Varmint.</p>"},{"location":"user-guide/flight-controller-setup/#serial-port-configuration","title":"Serial Port Configuration","text":"<p>Tip</p> <p>You can see which groups you are a member of by running <code>groups $USER</code> on the command line.</p> <p>The following bullet point is necessary:</p> <ul> <li>Be sure your user is in the <code>dialout</code> and <code>plugdev</code> groups so you have access to the serial ports. You will need to log out and back in for these changes to take effect. <pre><code>sudo usermod -aG dialout,plugdev $USER\n</code></pre></li> </ul> <p>If you experience issues, you may need one or both of the next two bullet points:</p> <ul> <li> <p>Temporarily stop the modem-manager (Sometimes, Linux thinks the device is a modem -- this command will be effective until next boot, or until you run the command again with <code>start</code> in place of <code>stop</code>) <pre><code>sudo systemctl stop ModemManager.service\n</code></pre></p> </li> <li> <p>Add the custom udev rule so Linux handles the flight controller properly (copy the following as <code>/etc/udev/rules.d/45-stm32dfu.rules</code>) <pre><code># DFU (Internal bootloader for STM32 MCUs)\nSUBSYSTEM==\"usb\", ATTRS{idVendor}==\"0483\", ATTRS{idProduct}==\"df11\", MODE=\"0664\", GROUP=\"plugdev\"\n</code></pre></p> </li> </ul> <p>Tip</p> <p>You can permanently disable the ModemManager if you do not need it, then you won't have to disable it every time you reboot: <pre><code>sudo systemctl disable ModemManager.service\n</code></pre> Replace <code>disable</code> with <code>enable</code> to revert (i.e. if you find some other program you use needs access to it). Or you can uninstall it entirely from your system: <pre><code>sudo apt purge modemmanager\n</code></pre></p>"},{"location":"user-guide/flight-controller-setup/#flashing-firmware","title":"Flashing Firmware","text":"<p>TODO</p> <p>Update flashing instructions.</p>"},{"location":"user-guide/flight-controller-setup/#f4-boards","title":"F4 Boards","text":"<ul> <li>Install the dfu-util utility</li> </ul> <pre><code>sudo apt install dfu-util\n</code></pre> <ul> <li>Download the latest rosflight-F4.bin file, found here</li> <li>Put the board in bootloader mode (short the boot pins while restarting the board by cycling power)</li> </ul> <p>Tip</p> <p>dfu-util auto-detects F4-based boards. Try <code>dfu-util -l</code> to make sure your board is in bootloader mode</p> <ul> <li>Flash the firmware to the device <pre><code>    dfu-util -a 0 -s 0x08000000 -D rosflight-F4.bin\n</code></pre></li> </ul>"},{"location":"user-guide/getting-started/","title":"Getting Started","text":"<p>Reading through the pages in this user guide in order should provide you with the information you need to get a vehicle flying with ROSflight. The following is a summary of the steps you'll need to follow to get your vehicle set up, with links to the corresponding documentation pages:</p> <ol> <li>Set up your hardware (fixed-wing or multirotor platform, flight controller, and companion computer)</li> <li>Flash your flight controller with the latest ROSflight firmware</li> <li>Set up your RC transmitter</li> <li>Set up ROS2 on your companion computer</li> <li>Configure the flight controller for your setup: the configuration checklists below should help guide you through this process</li> <li>Run through your preflight checks</li> <li>Tune the firmware attitude controller gains (multirotors only)</li> <li>Set up autonomous flight via offboard control (optional)</li> </ol>"},{"location":"user-guide/getting-started/#configuration-checklist","title":"Configuration Checklist","text":"<p>The following checklists should help you get a new vehicle set up for the first time. This checklist assumes that your hardware is already set up correctly.</p>"},{"location":"user-guide/getting-started/#general-setup","title":"General Setup","text":"<ol> <li>Set the <code>FIXED_WING</code> parameter (<code>1</code> if a fixed-wing, <code>0</code> if a multirotor)</li> <li>Set the <code>RC_TYPE</code> parameter (<code>0</code> if PPM, <code>1</code> if SBUS)</li> <li>Set the <code>MIXER</code> parameter to the appropriate value described in the Hardware Setup page</li> <li>Set the <code>MOTOR_PWM_UPDATE</code> parameter (typically <code>490</code> for SimonK ESCs, <code>50</code> for standard servos)</li> <li>Make sure your RC transmitter is set up correctly</li> <li>Set up your RC switches<ul> <li>If you want to arm/disarm using a switch, set the <code>ARM_CHANNEL</code> parameter to the appropriate channel (0-indexed)</li> <li>If you want to use a switch to enable RC override, set the <code>RC_ATT_OVRD_CHN</code> and <code>RC_THR_OVRD_CHN</code> parameters to the appropriate channel(s) (0-indexed). If you want complete control (attitude and throttle) when you flip the switch, set both these parameters to the same channel.</li> </ul> </li> <li>Calibrate your IMU: start <code>rosflight_io</code>, then run <code>ros2 service call /calibrate_imu std_srvs/srv/Trigger</code></li> <li>Complete the multirotor-specific or fixed-wing-specific checklist below</li> <li>Save the parameters (<code>ros2 service call /param_write std_srvs/srv/Trigger</code>)</li> <li>You'll probably want to save a backup of your parameters (call <code>ros2 service call /param_save_to_file rosflight_msgs/srv/ParamFile \"{filename: \"params.yml\"}\"</code>)</li> <li>Make sure you run through the Preflight Checklist before flying</li> </ol>"},{"location":"user-guide/getting-started/#multirotor-specific-setup","title":"Multirotor-specific Setup","text":"<p>Danger</p> <p>IMPORTANT: Remove all props from the vehicle when calibrating ESCs!!!</p> <ol> <li> <p>Calibrate ESCs</p> <ol> <li>Make sure <code>MOTOR_MIN_PWM</code> and <code>MOTOR_MAX_PWM</code> are correct (usually <code>1000</code> and <code>2000</code>)</li> <li>Set <code>MIXER</code> param to <code>0</code> (ESC calibration mixer)</li> <li>Set <code>ARM_SPIN_MOTORS</code> to <code>0</code></li> <li> <p>Perform ESC calibration. For standard ESCs:</p> <ol> <li>With power disconnected from the motors, arm the flight controller</li> <li>Set throttle to maximum</li> <li>Connect power to the motors</li> <li>Drop the throttle to minimum</li> </ol> </li> <li> <p>Set the <code>MIXER</code> parameter back to the appropriate value for your vehicle (see the Hardware Setup page)</p> </li> <li>Set <code>ARM_SPIN_MOTORS</code> back to <code>1</code></li> </ol> </li> <li> <p>The <code>ARM_SPIN_MOTORS</code> parameter should be set to <code>1</code> so the motors spin slowly when armed. The idle throttle setting can be adjusted with the <code>MOTOR_IDLE_THR</code> parameter.</p> </li> <li>You'll most likely want to set the <code>CAL_GYRO_ARM</code> param to <code>1</code> to enable calibrating gyros before arming</li> <li>Set the <code>RC_ATT_MODE</code> parameter to set RC control mode (<code>0</code> for rate mode, <code>1</code> for angle mode [default])</li> <li>Set torque offsets as described in the RC trim calculation section of the Improving Firmware Performance page</li> <li>Set the <code>FAILSAFE_THR</code> parameter to specify the throttle level the MAV will hold if the transimtter disconnects. Set the parameter to <code>0</code> if you just want the MAV to drop, otherwise determine the amount of throttle required to hover the MAV and set the parameter comfortably below that. DO NOT set it above, as this will result in a runaway MAV. We recommended that you test the throttle level in an enclosed space by powering off the transmitter while hovering, if you set this parameter above 0.</li> <li>Tune the controller gains as described in the Multirotor gain tuning section of the Improving Firmware Performance page</li> </ol>"},{"location":"user-guide/getting-started/#fixed-wing-specific-setup","title":"Fixed-Wing-Specific Setup","text":"<ol> <li>Reverse servo directions if necessary using the <code>AIL_REV</code>, <code>ELEVATOR_REV</code>, and <code>RUDDER_REV</code> parameters (<code>1</code> to reverse, <code>0</code> to keep current direction)</li> <li>You'll most likely want to set the <code>ARM_SPIN_MOTORS</code> parameter to <code>0</code> so that the prop doesn't spin at a minimum throttle setting when you arm, especially if you'll be doing hand launching</li> </ol>"},{"location":"user-guide/hardware-setup/","title":"Hardware Setup","text":""},{"location":"user-guide/hardware-setup/#parts-list","title":"Parts List","text":"<p>To use ROSflight to its full potential, you will need the following system components. Some components are mounted on your MAV (Miniature Aerial Vehicle), while others are on the ground. ROSflight supports both multirotor and fixed-wing vehicles.</p> <p>Mounted on the MAV</p> <ol> <li>Aircraft Frame, Motor(s), ESC(s), Battery and Propeller(s)</li> <li>Flight Controller (FC)</li> <li>Vibration Isolation for FC</li> <li>Any external sensors</li> <li>R/C Receiver</li> <li>Companion Computer</li> <li>Wi-Fi Antenna, or access of some kind to ground-station, wireless network (e.g. Ubiquiti Bullet)</li> </ol> <p>Ground Station</p> <ol> <li>Ground-Station, Wireless Network (e.g. Wi-Fi Router, Ubiquiti Rocket)</li> <li>R/C transmitter</li> <li>Laptop or base station computer</li> <li>Joystick (Xbox controller)</li> </ol>"},{"location":"user-guide/hardware-setup/#frame-motors-escs-battery-and-propeller","title":"Frame, Motors, ESCs, Battery, and Propeller","text":"<p>We do not officially support any specific multirotor or airplane frame, motor, ESC, Battery or Propeller combination. There are a lot of great resources for building your own MAV, and there are a lot of great kits out there that have all of these parts.</p> <p>If you are designing your own multirotor or airplane, you may want to look at ecalc, an online tool which can help you design a proper ESC/Battery/Motor/Propeller system for your MAV.</p> <p>Some things to keep in mind as you design or build your MAV.</p> <ul> <li>Most kits do not include space for a companion computer, cameras, laser scanners or other sensors. Be sure to think about where these components are going to go, and how their placement will affect the CG of the MAV.</li> <li>You will likely also need to customize the power circuitry of your MAV to provide power to your companion computer at some specific voltage. Many people like to separate the power electronics (the ESCs and motors), from the computer and companion sensors. This can really come in handy if you are trying to develop code on the MAV, because you can have the computer on and sensors powered, and not worry at all about propellers turning on and causing injury as you move the aircraft about by hand. We will talk about this more when we talk about wiring up your MAV.</li> <li>Cheap propellers can cause a huge amount of vibration. Consider buying high-quality propellers, doing a propeller balance, or both. RCGroups, DIY Drones and Youtube have some awesome guides on how to do propeller balancing.</li> <li>ESCs will need to be calibrated from 2000 to 1000 us</li> </ul>"},{"location":"user-guide/hardware-setup/#flight-controller","title":"Flight Controller","text":"<p>TODO</p> <p>Update recommended hardware once supported hardware has been finalized.</p>"},{"location":"user-guide/hardware-setup/#external-sensors","title":"External Sensors","text":"<p>Additional Sensors you may want for your ROSflight setup include:</p> <ul> <li>Sonar</li> <li>GPS</li> <li>Digital Airspeed Sensor (Pitot Tube)</li> </ul>"},{"location":"user-guide/hardware-setup/#vibration-isolation","title":"Vibration Isolation","text":"<p>It is really important to isolate your flight controller from vehicle vibrations, such as those caused by propellers and motors. We recommend using small amounts of Kyosho Zeal to mount a fiberglass plate holding the FC to the MAV. You may also want to try adding mass to the flight control board. We have accomplished this by gluing steel washers to the fiberglass mounting plate.</p> <p></p> <p>You may need to experiment with the amount of gel you use, how far apart the gel is spaced, and the amount of mass added to the FC mounting plate. The interaction of these factors is difficult to predict, therefore it takes a little bit of experimentation to get it right.</p>"},{"location":"user-guide/hardware-setup/#companion-computer","title":"Companion Computer","text":"<p>The only requirement for the companion computer is that it runs Linux (usually an Ubuntu LTS version, but using Docker on other distributions is also an option), ROS2, has at least one USB port, and can be carried by the aircraft. We have had success with the following companion computers, but by no means is this a comprehensive list; it is more by way of suggestion.</p> <ul> <li>NVIDIA Jetson</li> <li>MSI CUBI</li> <li>Intel NUC</li> <li>Rasberry Pi 3</li> </ul>"},{"location":"user-guide/hardware-setup/#wi-fi","title":"Wi-Fi","text":"<p>You will need Wi-Fi to communicate with your MAV when it is in the air. Because ROS2 communicates over UDP, it is very easy to use ROS2 to view what is going on in your MAV while it is flying by sending commands and reading sensor data. For most applications, a standard Wi-Fi router and dongle will suffice. For long-range applications, you may want to look into Ubiquiti point-to-point Wi-Fi. (We have seen ranges over a mile with these networks.)</p>"},{"location":"user-guide/hardware-setup/#rc-transmitter-and-receiver","title":"RC Transmitter and Receiver","text":"<p>For RC Control, you will need a transmitter with between 6 and 8 channels. Any additional channels will be wasted. We require RC control for safe operation, and only support arming and disarming via RC control.</p> <p>ROSflight only supports PPM (pulse position modulation) and SBUS receivers. Individual channel PWM outputs are not supported. Any configurations with PPM or SBUS and 6-8 channels will be sufficient.</p>"},{"location":"user-guide/hardware-setup/#laptop-or-base-station-computer","title":"Laptop or Base Station Computer","text":"<p>You will need a laptop which can run ROS2 to communicate with the MAV over the ground station wireless network. To do this natively you'll want a recent Ubuntu LTS version, but this can also be done with Docker containers from pretty much any Linux distribution. Linux within a virtual machine can also work, but is not recommended. </p>"},{"location":"user-guide/hardware-setup/#joystick","title":"Joystick","text":"<p>A joystick is used for software-in-the-loop (SIL) simulations. The joystick is not technically a required component because it is possible to control your MAV from the command line, but it makes things much easier. Our first recommendation is to use the same transmitter you use for hardware as a joystick by plugging it into the computer via USB. We support Taranis QX7 transmitters, Radiomaster TX16s transmitters, RealFlight controllers, and XBOX controllers. Other joysticks can be used, but you may need to create custom axis and button mappings within the ROSflight joystick utility.</p>"},{"location":"user-guide/hardware-setup/#battery-monitor","title":"Battery Monitor","text":"<p>A battery monitor is an analog sensor that provides battery voltage and/or battery current information. This data can be used to prevent power loss in air or to measure system load. The sensor outputs an analog voltage proportional to the battery voltage and/or current through the battery. Most flight controllers come equipped with a built-in battery monitor, but if not, small PCB sensors are also available that can be connected to the flight controller.</p> <p>For ROSflight to use a battery monitor, an appropriate multiplier must be set. ROSflight multiplies the analog signal from the monitor by the multiplier to get the final reading. The monitor datasheet should contain the information needed to get the multiplier. For example, the datasheet for the AttoPilot 50V/90A sensor states that it outputs 63.69 mV / V. To get the original battery voltage, the multiplier must be 1/.06369, or 15.7. The multipliers for the voltage and current are set separately, with the <code>BATT_VOLT_MULT</code> and <code>BATT_CURR_MULT</code> parameters, respectively.</p> <p>ROSflight applies a simple low-pass filter to remove noise from the voltage and current measurements. These filters are configurable via the <code>BATT_VOLT_ALPHA</code> and <code>BATT_CURR_ALPHA</code> parameters. The alpha value for a given cutoff frequency \\(a\\), can be calulated with: \\( \\alpha =  e ^ {-.01a} \\). As battery voltages do not typically change quickly, the default of 0.995 usually suffices.</p> <p>More information on battery monitor hardware, including determinining appropriate multipliers and creating a simple DIY monitor, can be found on the OpenPilot Wiki.</p>"},{"location":"user-guide/hardware-setup/#wiring-diagram","title":"Wiring Diagram","text":"<p>Below is an example wiring diagram for a multirotor using an MSI Cubi as a companion computer. This diagram also includes the motor power switch, which allows for the sensors, flight controller, and companion computer to be powered on while the motors are off. This is a safer way to test sensors, code, etc. as the motors are unable to spin while the switch is off.</p> <p></p> <p>Your needs will likely be slightly different than what is shown. This is meant as an example only and can be adapted to fit your needs.</p>"},{"location":"user-guide/hardware-setup/#motor-layouts","title":"Motor Layouts","text":"<p>The desired mixer can be chosen by setting the <code>MIXER</code> parameter to the following values:</p> # Mixer 0 ESC calibration 1 Quad + 2 Quad X 3 Hex + 4 Hex X 5 Octo + 6 Octo X 7 Y6 8 X8 9 Tricopter 10 Fixed-wing (traditional AETR) <p>The associated motor layouts are shown below for each mixer. The ESC calibration mixer directly outputs the throttle command equally to each motor, and can be used for calibrating the ESCs.</p> <p></p> <p></p>"},{"location":"user-guide/hardware-setup/#connecting-to-the-flight-controller","title":"Connecting to the Flight Controller","text":"<p>The flight controller communicates with the companion computer over a serial link. ROSflight only supports one serial connection at a time and by default should be the serial link connected to the USB connector on the board.</p>"},{"location":"user-guide/hardware-setup/#using-secondary-serial-links","title":"Using Secondary Serial Links","text":"<p>In the case of an F4 flight controller, which has a USB peripheral, the highest bandwidth connection will be the USB connector. However, UART3 can also be used to communicate with the companion computer if you desire a more secure connection (micro USB connectors have been known to disconnect in high vibrations).</p> <p>If a USB connection is detected on the USB peripheral, ROSflight will direct all communication through this port. However, if the <code>PARAM_SERIAL_DEVICE</code> parameter is set to <code>3</code> and the <code>PARAM_BAUD_RATE</code> parameter is set properly, then UART3 will be enabled when the USB connection is absent.</p>"},{"location":"user-guide/improving-firmware-performance/","title":"Improving Firmware Performance","text":"<p>ROSflight supplies several methods to improve the performance of your aircraft. Tuning gains, adding feed-forward torques, and tuning the estimator are three ways to get your aircraft flying great!</p>"},{"location":"user-guide/improving-firmware-performance/#gain-tuning","title":"Gain Tuning","text":"<p>Because there are a wide variety of multirotors out there, no one set of PID controller gains will be optimal for all vehicles. The default set of gains is relatively conservative for most platforms, and should be somewhat airworthy in most cases. However, depending on the inertia-to-torque ratio on your MAV, you may have to change these gains considerably. There are some great tutorials online on multirotor gain tuning; this is another tried-and-true method used to great effect at BYU.</p> <p>If you are unfamiliar with PIDs, you should probably go read about them before trying to tune a multirotor. Getting an understanding for what is going on will definitely guide your decision making process as you try to find better gains.</p> <p>While tuning controller gains, it is very likely that the multirotor will oscillate out of control. To handle this scenario, we generally add what we call \"training wheels\" to the multirotors we are tuning. These amount to thin carbon rods in the shape of an X zip-tied to the landing gear. This widens out the base of the multirotor so if you come down on a hard oscillation, chances are the vehicle will land upright, hopefully without a prop strike, or worse, battery damage with a thermal runaway event. If the battery is not tucked inside the main frame, it is wise to add some foam as protection to the battery.</p> <p>Here is a video of a maiden flight of ROSflight with \"training wheels\" attached.</p> <p>Now, for the procedure on tuning.</p>"},{"location":"user-guide/improving-firmware-performance/#tuning-roll-and-pitch-angles","title":"Tuning Roll and Pitch angles","text":"<p>Here is a flowchart describing my PID tuning process for roll and pitch:</p> <p></p> <p>You may want to do another D-tuning iteration. Additionally, sometimes it is helpful to do a little tweaking on roll and pitch separately to eek out a little more performance from the differences in roll and pitch dynamics of your vehicle.</p> <p>Notice that we did not include any <code>I</code> tuning. As a general rule, try to keep the <code>I</code> gain as low as possible. It will always slow your response rate to input, and it can induce low frequency oscillations.</p> <p>You should only have <code>I</code> gain on roll and pitch if one of the following is true:</p> <ol> <li>You expect your CG to change, and/or</li> <li>You expect your rotor geometry to change</li> </ol> <p>Both of these are pretty rare. Instead, use your RC transmitter to trim the aircraft so it hovers with no stick input. In the RC trim calculation section, we will use the RC trim to calculate a feed-forward torque on the roll, pitch and yaw rates.</p>"},{"location":"user-guide/improving-firmware-performance/#tuning-yaw-rate","title":"Tuning Yaw rate","text":"<p>Dynamically and algorithmically, using a <code>D</code> gain in yaw-rate control has no significant advantage. Controlling with derivative requires differentiating gyro measurements, which tends to be pretty noisy. In our experience, putting <code>D</code> in rate controllers on multirotors has always decreased performance.</p> <p>Tuning yaw rate is generally pretty easy. Basically, keep cranking it up until you feel like it's \"locked in\". Sometimes, a little bit of <code>I</code> (on the order of 0.1P) can help with this as well.</p> <p>The problem with too much <code>P</code> on yaw rate generally manifests itself in motor saturation. Some, especially larger, multirotors have problems getting enough control authority in yaw with the propellers being aligned flat. After you are done tuning, you might want to look at a plot of motor commands during a fairly aggressive flight. Underactuated yaw will be pretty obvious in these plots, because you will see the motor commands railing. To fix this, you can put shims between the arm mounts and the motors to tilt the motors just a little bit in the direction of yaw for that motor.</p>"},{"location":"user-guide/improving-firmware-performance/#rc-trim","title":"RC trim","text":"<p>In the vast majority of cases, your multirotor will not be built perfectly. The CG could be slightly off, or your motors, speed controllers and propellers could be slightly different. One way to fix this is by adding an integrator. Integrators get rid of static offsets such as those just mentioned. However, as explained above, integrators also always slow vehicle response. In our case, since this offset is going to be constant, we can instead find a \"feed-forward\", or equilibrium offset, torque that you need to apply to hover without drift.</p> <p>Use the RC transmitter to find the \"equilibrium torques\" about the x, y, and z axes to keep the multirotor level. This is done by trimming the aircraft with the RC trims. These are usually the little switches next to the sticks on your transmitter. Adjust these until you can hover the multirotor without touching the sticks.</p> <p>Next, land the multirotor, disarm, center the sticks and perform a trim calibration with <code>ros2 service call /calibrate_rc_trim std_srvs/srv/Trigger</code>. ROSflight then uses the trim settings on your transmitter to find these feed-forward, or equilibrium, torques that need to be applied post-controller to keep the multirotor level. These torques will be applied to all future commands (both from the companion computer and RC), so you will need to zero out your transmitter trims after calibration.</p>"},{"location":"user-guide/improving-firmware-performance/#estimator-tuning","title":"Estimator Tuning","text":"<p>ROSflight uses a non-linear complementary filter, based on the quaternion implementation of \"Non-linear complementary filters on the special orthogonal group\" by Robert Mahony<sup>1</sup>,  to estimate attitude and angular rates. The implementation has been improved with suggestions from \"Attitude Representation and Kinematic Propagation for Low-Cost UAVs\" by Robert Casey<sup>2</sup>. A write-up of the derivation and implementation details can be found in the LaTeX report in <code>reports/estimator.tex</code>. (You'll need to be able to compile LaTeX sources to view the PDF).</p> <p>In addition to the complementary filter, accelerometer and gyro measurements are filtered using a simple low-pass filter (LPF) to cut out noise from vibrations. A block diagram of the estimator is shown below for reference. y_{gyro} and y_{acc} are gyro and accelerometer measurements, respectively and \\beta_{gyro} is the estimated gyro biases.</p> <p></p>"},{"location":"user-guide/improving-firmware-performance/#tuning-the-low-pass-filter-gains","title":"Tuning the Low-Pass Filter Gains","text":"<p>The <code>ACC_LPF_ALPHA</code> and <code>GYRO_LPF_ALPHA</code> parameters are used in the following low-pass-filter implementation (see lines <code>98-106</code> of <code>estimator.c</code>):</p> x_t = (1-\\alpha)y_t + \\alpha x_{t-1} <p>where y_t is the measurement and x_t is the filtered value. Lowering \\alpha will reduce lag in response, so if you feel like your MAV is sluggish despite all attempts at controller gain tuning, consider reducing \\alpha. Reducing \\alpha too far, however will result in a lot of noise from the sensors making its way into the motors. This can cause motors to get really hot, so make sure you check motor temperature if you are changing the low-pass filter constants.</p>"},{"location":"user-guide/improving-firmware-performance/#tuning-the-complementary-filter","title":"Tuning the Complementary Filter","text":"<p>The complementary filter has two gains, k_p and k_i. For a complete understanding of how these work, we recommend reading the Mahony Paper, or the technical report in the reports folder. In short, k_p can be thought of as the strength of accelerometer measurements in the filter, and the k_i gain is the integral constant on the gyro bias. These values should probably not be changed. Before you go changing these values, make sure you completely understand how they work in the filter.</p> <p>If you do decide to change these values, you should stick to the following rule of thumb.</p> k_i \\approx \\tfrac{k_p}{10}."},{"location":"user-guide/improving-firmware-performance/#external-attitude-measurements","title":"External Attitude Measurements","text":"<p>Because the onboard attitude estimator uses only inertial measurements, the estimates can deviate from truth. This is especially true during extended periods of accelerated flight, during which the gravity vector cannot be measured. Attitude measurements from an external source can be applied to the filter to help improve performance. These external attitude measurements might come from a higher-level estimator running on the companion computer that fuses additional information from GPS, vision, or a motion capture system.</p> <p>To send these updates to the flight controller, publish a <code>geometry_msgs/Quaternion</code> message to the <code>external_attitude</code> topic to which <code>rosflight_io</code> subscribes. The degree to which this update will be trusted is tuned with the <code>FILTER_KP_EXT</code> parameter.</p> <ol> <li> <p>Mahony, R., Hamel, T. and Pflimlin, J. (2008). Nonlinear Complementary Filters on the Special Orthogonal Group. IEEE Transactions on Automatic Control, 53(5), pp.1203-1218.\u00a0\u21a9</p> </li> <li> <p>Casey, R., Karpenko, M., Curry, R. and Elkaim, G. (2013). Attitude Representation and Kinematic Propagation for Low-Cost UAVs. AIAA Guidance, Navigation, and Control (GNC) Conference.\u00a0\u21a9</p> </li> </ol>"},{"location":"user-guide/overview/","title":"Overview","text":""},{"location":"user-guide/overview/#main-components-of-rosflight","title":"Main Components of ROSflight","text":"<p>ROSflight is intended to be used with both a typical flight controller and a companion Linux computer. Although it can be used with just a flight controller, this setup will not offer most of the advantages of ROSflight.</p> <p>Note</p> <p>To avoid confusion, we try to consistently use the following terminology:</p> <ul> <li>Flight controller: The embedded board that runs the ROSflight firmware and performs I/O with sensors and ESCs</li> <li>Companion computer: A Linux computer, running ROS2, that is mounted on the vehicle and has a physical, serial connection with the flight controller</li> <li>Offboard control (setpoints): The control setpoints passed from the companion computer to the flight controller. The control is \"offboard\" from the perspective of the flight controller, even though the computer providing those commands is mounted onboard the vehicle.</li> </ul> <p>The following figure illustrates the interactions between the major components of the system:</p> <p></p>"},{"location":"user-guide/overview/#firmware","title":"Firmware","text":"<p>The ROSflight firmware is the low level microcontroller code that runs on the flight controller. This communicates directly with sensors and actuators and serves as the bridge between hardware and higher level software. The firmware itself is designed to do as little as possible, offloading most of the work to the companion computer.</p> <p>Although higher level control is offloaded to the companion computer, enough control and functionality is included in the firmware to enable a safety pilot to fly the UAV through any portion of the flight with or without an operating companion computer.</p>"},{"location":"user-guide/overview/#rosflight-io","title":"ROSflight IO","text":"<p>ROSflight IO is a ROS2 node that runs on the companion computer that communicates directly with the firmware over a serial connection. This serves as the bridge between the firmware and the rest of ROS2 network.</p>"},{"location":"user-guide/overview/#rosplane-and-roscopter","title":"ROSplane and ROScopter","text":"<p>ROSplane and ROScopter are ROS2 based autonomy stacks that run on the companion computer and do most of the heavy computation of the autopilot. Each portion of their autonomy stacks are organized into highly modular ROS nodes that can be easily swapped out with custom nodes.</p> <p>ROSplane and ROScopter are not required for using ROSflight and you could choose to use an entirely different autonomy stack if you so desired.</p>"},{"location":"user-guide/overview/#rc-safety-pilot","title":"RC Safety Pilot","text":"<p>ROSflight is designed for use with offboard control from experimental and research code. As such, it provides several mechanisms for an RC safety pilot to intervene if something goes wrong with the control setpoints coming from the companion computer:</p> <ul> <li>RC override switch: The safety pilot can flip a switch on the transmitter to take back RC control. Attitude and throttle override can be mapped independently, meaning you can choose one or the other, put them on separate switches, or put them both on the same switch. Details on these switches are provided on the RC configuration page.</li> <li>Stick deviations: If a stick is deviated from its center position, then that channel is overridden by RC control. This allows the safety pilot to take control without flipping a switch. This may be useful to provide a momentary correction on a single axis. The fraction of stick travel needed to activate the RC override is controlled by the <code>RC_OVRD_DEV</code> parameter. The <code>OVRD_LAG_TIME</code> parameter controls the amount of time that the override remains active after the sticks return to center.</li> <li>Minimum throttle: By default, the flight controller takes the minimum of the two throttle commands from RC and offboard control setpoints. This allows the safety pilot to drop the throttle quickly if needed. This behavior can be turned on or off with the <code>MIN_THROTTLE</code> parameter.</li> </ul>"},{"location":"user-guide/overview/#arming-errors-failsafe","title":"Arming, Errors &amp; Failsafe","text":"<p>The flight controller can only be armed and disarmed via RC control. Two mechanisms are provided: sticks (left stick down and right to arm, down and left to disarm) and switch. Only one of these options can be active at a time. Details on configuration are given on the RC configuration page.</p> <p>The firmware runs a number of error checks before allowing the flight controller to arm. Completing the configuration checklist on the Getting Started page should avoid these errors. In addition to a few internal health checks, the following conditions are checked:</p> <ul> <li>Mixer: Valid mixer must have been selected (see the Hardware Setup documentation page)</li> <li>IMU calibration: The IMU must have been calibrated since firmware was flashed (it is recommended that you recalibrate often)</li> <li>RC: There must be an active RC connection</li> </ul> <p>In addition to the error checking before arming, the flight controller enters a failsafe mode if the RC connection is lost during flight while armed. While in failsafe mode the flight controller commands level flight with the throttle value defined by the <code>FAILSAFE_THR</code> parameter.</p> <p>The following is a simplified version of the finite state machine that defines logic used for the arming, error checks, and failsafe operations:</p> <p></p> <p>The state manager also includes functionality for recovering from hard faults if one were to occur, although this is unlikely with unmodified firmware. If a hard fault occurs while the flight controller is armed, the firmware has the ability to immediately rearm after rebooting to enable continued RC control of the vehicle for recovery.</p>"},{"location":"user-guide/overview/#leds","title":"LEDs","text":"<p>The meaning of the various LEDs is summarized in the following table. The colors of the LEDs may change depending on your specific board:</p> LED On Off Slow Blink Fast Blink Power (Blue) Board powered - - - Info (Green) RC control Offboard control - - Warning (Red) Armed Disarmed Error (disarmed) Failsafe (armed)"},{"location":"user-guide/parameter-configuration/","title":"Parameters","text":"<p>The ROSflight firmware has several dozen parameters which it uses to customize performance. Parameters are considered semi-static variables. That is, parameters do not change during flight, but they may change between vehicles. Examples of parameters you may wish to change are:</p> <ul> <li>Fixed-wing vehicle flag</li> <li>PID gains</li> <li>Mixer choice</li> <li>IMU low-pass filter constant</li> <li>RC receiver type (PPM or SBUS)</li> </ul> <p>and so on. Access to all parameters is enabled via ROS2 services advertised by <code>rosflight_io</code> while the flight controller is connected.</p>"},{"location":"user-guide/parameter-configuration/#parameter-interface","title":"Parameter Interface","text":""},{"location":"user-guide/parameter-configuration/#getting-parameter-values","title":"Getting Parameter Values","text":"<p>Sometimes it is handy to ask the flight controller what the current value of a parameter is. This is accomplished using the <code>param_get</code> service. As an example, let's retrieve the roll angle controller proportional (P) gain.</p> <pre><code>ros2 service call /param_get rosflight_msgs/srv/ParamGet \"{name: \"PID_ROLL_ANG_P\"}\"\n</code></pre> <p>You should get a response similar to the following (this happens to be the default value with floating-point error):</p> <pre><code>exists: True\nvalue: 0.15000000596\n</code></pre>"},{"location":"user-guide/parameter-configuration/#changing-parameters","title":"Changing Parameters","text":"<p>Parameters are changed via the <code>param_set</code> service. As an example, let's change the roll angle controller P gain. (I will assume that the flight controller is connected and <code>rosflight_io</code> is running in the root namespace.)</p> <pre><code>ros2 service call /param_set rosflight_msgs/srv/ParamSet \"{name: \"PID_ROLL_ANG_P\", value: 0.08}\"\n</code></pre> <p>You should get a prompt from <code>rosflight_io</code> saying <pre><code>[ INFO] [1491672408.585339558]: Parameter PID_ROLL_ANG_P has new value 0.08\n[ WARN] [1491672408.585508849]: There are unsaved changes to onboard parameters\n</code></pre></p> <p>Notice that the parameters have been set, but not saved. Parameter changes take effect immediately, however they will not persist over a reboot unless you write them to the non-volatile memory. This brings us to the next task.</p>"},{"location":"user-guide/parameter-configuration/#writing-parameters","title":"Writing Parameters","text":"<p>To ensure that parameter values persist between reboots, you must write the parameters to the non-volatile memory. This is done by calling <code>param_write</code></p> <pre><code>ros2 service call /param_write std_srvs/srv/Trigger\n</code></pre> <p><code>rosflight_io</code> should then respond with <pre><code>[ INFO] [1491672597.123201952]: Param write succeeded\n[ INFO] [1491672597.123452908]: Onboard parameters have been saved\n</code></pre></p> <p>Warning</p> <p>It is highly recommended that you write parameters before arming and flying the vehicle. Among other things, this will ensure that in the rare case that a hard fault is encountered and the flight controller must reboot during flight, the correct configuration will be loaded on reboot.</p> <p>Error</p> <p>Parameter writing can only happen if the flight controller is disarmed. If the param write failed for some reason, you may want to make sure your FC is disarmed and try again.</p>"},{"location":"user-guide/parameter-configuration/#backing-up-and-loading-parameters-from-file","title":"Backing Up and Loading Parameters from File","text":"<p>It is good practice to back up your parameter configuration in case you have to re-flash your firmware or you want to share configurations between vehicles. We can do this via the <code>param_save_to_file</code> and <code>param_load_from_file</code> services.</p> <p>First, let's back up our current parameter configuration:</p> <pre><code>ros2 service call /param_save_to_file rosflight_msgs/srv/ParamFile \"{filename: \"~/parameters.yaml\"}\"\n</code></pre> <p>Parameters are saved in YAML format. You must also specify the absolute file name of where you would like your parameters to be saved. The current active set of parameters will be saved, regardless of what is saved in non-volatile memory on the flight controller.</p> <p>Now, let's say we want to re-load this parameter file <pre><code>ros2 service call /param_load_from_file rosflight_msgs/srv/ParamFile \"{filename: \"~/parameters.yml\"}\"\n</code></pre> Again, you must specify the absolute file name of the file to be loaded.</p>"},{"location":"user-guide/parameter-configuration/#fixed-wing-parameter-configuration","title":"Fixed-Wing Parameter Configuration","text":"<p>Because ROSflight ships with default parameters for multirotors, you will probably want to change the following parameters if you want to fly a fixed-wing aircraft.</p> Parameter Description Type Fixed-Wing Value MOTOR_PWM_UPDATE Refresh rate of motor commands to motors and servos (Hz) - See motor documentation int 50 ARM_SPIN_MOTORS Enforce MOTOR_IDLE_PWM int false MOTOR_IDLE_THR min throttle command sent to motors when armed (Set above 0.1 to spin when armed) float 0.1 ARM_CHANNEL RC switch channel mapped to arming [0 indexed, -1 to disable] int 4 FIXED_WING switches on passthrough commands for fixed-wing operation int true MIXER Which mixer to choose - See Mixer documentation int 10 ELEVATOR_REV reverses elevator servo output int 0/1 AIL_REV reverses aileron servo output int 0/1 RUDDER_REV reverses rudder servo output int 0/1 CAL_GYRO_ARM Calibrate gyros when arming - generally only for multirotors int false"},{"location":"user-guide/parameter-configuration/#description-of-all-parameters","title":"Description of all Parameters","text":"<p>This is a list of all ROSflight parameters, including their types, default values, and minimum and maximum recommended values:</p> Parameter Description Type Default Value Min Max BAUD_RATE Baud rate of MAVlink communication with companion computer int 921600 9600 921600 SERIAL_DEVICE Serial Port (for supported devices) int 0 0 3 SYS_ID Mavlink System ID int 1 1 255 STRM_HRTBT Rate of heartbeat stream (Hz) int 1 0 1000 STRM_STATUS Rate of status stream (Hz) int 10 0 1000 STRM_ATTITUDE Rate of attitude stream (Hz) int 200 0 1000 STRM_IMU Rate of IMU stream (Hz) int 250 0 1000 STRM_MAG Rate of magnetometer stream (Hz) int 50 0 75 STRM_BARO Rate of barometer stream (Hz) int 50 0 100 STRM_AIRSPEED Rate of airspeed stream (Hz) int 50 0 50 STRM_SONAR Rate of sonar stream (Hz) int 40 0 40 STRM_SERVO Rate of raw output stream int 50 0 490 STRM_RC Rate of raw RC input stream int 50 0 50 STRM_GNSS Maximum rate of GNSS data streaming. Higher values allow for lower latency int 1000 0 1000 STRM_GNSS_FULL Maximum rate of fully detailed GNSS data streaming int 0 0 10 STRM_BATTERY Rate of battery status stream int 0 0 50 PARAM_MAX_CMD saturation point for PID controller output float 1.0 0 1.0 PID_ROLL_RATE_P Roll Rate Proportional Gain float 0.070f 0.0 1000.0 PID_ROLL_RATE_I Roll Rate Integral Gain float 0.000f 0.0 1000.0 PID_ROLL_RATE_D Roll Rate Derivative Gain float 0.000f 0.0 1000.0 PID_PITCH_RATE_P Pitch Rate Proportional Gain float 0.070f 0.0 1000.0 PID_PITCH_RATE_I Pitch Rate Integral Gain float 0.0000f 0.0 1000.0 PID_PITCH_RATE_D Pitch Rate Derivative Gain float 0.0000f 0.0 1000.0 PID_YAW_RATE_P Yaw Rate Proportional Gain float 0.25f 0.0 1000.0 PID_YAW_RATE_I Yaw Rate Integral Gain float 0.0f 0.0 1000.0 PID_YAW_RATE_D Yaw Rate Derivative Gain float 0.0f 0.0 1000.0 PID_ROLL_ANG_P Roll Angle Proportional Gain float 0.15f 0.0 1000.0 PID_ROLL_ANG_I Roll Angle Integral Gain float 0.0f 0.0 1000.0 PID_ROLL_ANG_D Roll Angle Derivative Gain float 0.05f 0.0 1000.0 PID_PITCH_ANG_P Pitch Angle Proportional Gain float 0.15f 0.0 1000.0 PID_PITCH_ANG_I Pitch Angle Integral Gain float 0.0f 0.0 1000.0 PID_PITCH_ANG_D Pitch Angle Derivative Gain float 0.05f 0.0 1000.0 X_EQ_TORQUE Equilibrium torque added to output of controller on x axis float 0.0f -1.0 1.0 Y_EQ_TORQUE Equilibrium torque added to output of controller on y axis float 0.0f -1.0 1.0 Z_EQ_TORQUE Equilibrium torque added to output of controller on z axis float 0.0f -1.0 1.0 PID_TAU Dirty Derivative time constant - See controller documentation float 0.05f 0.0 1.0 MOTOR_PWM_UPDATE Overrides default PWM rate specified by mixer if non-zero - Requires reboot to take effect int 0 0 490 MOTOR_IDLE_THR min throttle command sent to motors when armed (Set above 0.1 to spin when armed) float 0.1 0.0 1.0 FAILSAFE_THR Throttle sent to motors in failsafe condition (set just below hover throttle) float 0.3 0.0 1.0 ARM_SPIN_MOTORS Enforce MOTOR_IDLE_THR int true 0 1 FILTER_INIT_T Time in ms to initialize estimator int 3000 0 100000 FILTER_KP estimator proportional gain - See estimator documentation float 0.5f 0 10.0 FILTER_KI estimator integral gain - See estimator documentation float 0.01f 0 1.0 FILTER_KP_COR estimator proportional gain on external attitude correction - See estimator documentation float 10.0f 0 1.0 FILTER_ACCMARGIN allowable accel norm margin around 1g to determine if accel is usable float 0.1f 0 1.0 FILTER_QUAD_INT Perform a quadratic averaging of LPF gyro data prior to integration (adds ~20 us to estimation loop on F1 processors) int 1 0 1 FILTER_MAT_EXP 1 - Use matrix exponential to improve gyro integration (adds ~90 us to estimation loop in F1 processors) 0 - use euler integration int 1 0 1 FILTER_USE_ACC Use accelerometer to correct gyro integration drift (adds ~70 us to estimation loop) int 1 0 1 CAL_GYRO_ARM True if desired to calibrate gyros on arm int false 0 1 GYROXY_LPF_ALPHA Low-pass filter constant on gyro X and Y axes - See estimator documentation float 0.3f 0 1.0 GYROZ_LPF_ALPHA Low-pass filter constant on gyro Z axis - See estimator documentation float 0.3f 0 1.0 ACC_LPF_ALPHA Low-pass filter constant on all accel axes - See estimator documentation float 0.5f 0 1.0 GYRO_X_BIAS Constant x-bias of gyroscope readings float 0.0f -1.0 1.0 GYRO_Y_BIAS Constant y-bias of gyroscope readings float 0.0f -1.0 1.0 GYRO_Z_BIAS Constant z-bias of gyroscope readings float 0.0f -1.0 1.0 ACC_X_BIAS Constant x-bias of accelerometer readings float 0.0f -2.0 2.0 ACC_Y_BIAS Constant y-bias of accelerometer readings float 0.0f -2.0 2.0 ACC_Z_BIAS Constant z-bias of accelerometer readings float 0.0f -2.0 2.0 ACC_X_TEMP_COMP Linear x-axis temperature compensation constant float 0.0f -2.0 2.0 ACC_Y_TEMP_COMP Linear y-axis temperature compensation constant float 0.0f -2.0 2.0 ACC_Z_TEMP_COMP Linear z-axis temperature compensation constant float 0.0f -2.0 2.0 MAG_A11_COMP Soft iron compensation constant float 1.0f -999.0 999.0 MAG_A12_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A13_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A21_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A22_COMP Soft iron compensation constant float 1.0f -999.0 999.0 MAG_A23_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A31_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A32_COMP Soft iron compensation constant float 0.0f -999.0 999.0 MAG_A33_COMP Soft iron compensation constant float 1.0f -999.0 999.0 MAG_X_BIAS Hard iron compensation constant float 0.0f -999.0 999.0 MAG_Y_BIAS Hard iron compensation constant float 0.0f -999.0 999.0 MAG_Z_BIAS Hard iron compensation constant float 0.0f -999.0 999.0 BARO_BIAS Barometer measurement bias (Pa) float 0.0f 0 inf GROUND_LEVEL Altitude of ground level (m) float 1387.0f -1000 10000 DIFF_PRESS_BIAS Differential Pressure Bias (Pa) float 0.0f -10 10 RC_TYPE Type of RC input 0 - PPM, 1 - SBUS int 0 0 1 BATT_VOLT_MULT Battery monitor voltage multiplier float 0 0 inf BATT_CURR_MULT Battery monitor current multiplier float 0 0 inf BATT_VOLT_ALPHA Batter monitor voltage filter alpha. Values closer to 1 smooth the signal more. float 0.995 0 1 BATT_CURR_ALPHA Battery monitor current filter alpha. Values closer to 1 smooth the signal more. float 0.995 0 1 RC_X_CHN RC input channel mapped to x-axis commands [0 - indexed] int 0 0 3 RC_Y_CHN RC input channel mapped to y-axis commands [0 - indexed] int 1 0 3 RC_Z_CHN RC input channel mapped to z-axis commands [0 - indexed] int 3 0 3 RC_F_CHN RC input channel mapped to F-axis commands [0 - indexed] int 2 0 3 RC_ATT_OVRD_CHN RC switch mapped to attitude override [0 indexed, -1 to disable] int 4 4 7 RC_THR_OVRD_CHN RC switch channel mapped to throttle override [0 indexed, -1 to disable] int 4 4 7 RC_ATT_CTRL_CHN RC switch channel mapped to attitude control type [0 indexed, -1 to disable] int -1 4 7 ARM_CHANNEL RC switch channel mapped to arming (only if PARAM_ARM_STICKS is false) [0 indexed, -1 to disable] int -1 4 7 RC_NUM_CHN number of RC input channels int 6 1 8 SWITCH_5_DIR RC switch 5 toggle direction int 1 -1 1 SWITCH_6_DIR RC switch 6 toggle direction int 1 -1 1 SWITCH_7_DIR RC switch 7 toggle direction int 1 -1 1 SWITCH_8_DIR RC switch 8 toggle direction int 1 -1 1 RC_OVRD_DEV RC stick deviation from center for override float 0.1 0.0 1.0 OVRD_LAG_TIME RC stick deviation lag time before returning control (ms) int 1000 0 100000 MIN_THROTTLE Take minimum throttle between RC and computer at all times int true 0 1 RC_ATT_MODE Attitude mode for RC sticks (0: rate, 1: angle). Overridden if RC_ATT_CTRL_CHN is set. int 1 0 1 RC_MAX_ROLL Maximum roll angle command sent by full deflection of RC sticks float 0.786f 0.0 3.14159 RC_MAX_PITCH Maximum pitch angle command sent by full stick deflection of RC sticks float 0.786f 0.0 3.14159 RC_MAX_ROLLRATE Maximum roll rate command sent by full stick deflection of RC sticks float 3.14159f 0.0 9.42477796077 RC_MAX_PITCHRATE Maximum pitch command sent by full stick deflection of RC sticks float 3.14159f 0.0 3.14159 RC_MAX_YAWRATE Maximum pitch command sent by full stick deflection of RC sticks float 1.507f 0.0 3.14159 MIXER Which mixer to choose - See Mixer documentation int Mixer::INVALID_MIXER 0 10 FIXED_WING switches on pass-through commands for fixed-wing operation int false 0 1 ELEVATOR_REV reverses elevator servo output int 0 0 1 AIL_REV reverses aileron servo output int 0 0 1 RUDDER_REV reverses rudder servo output int 0 0 1 FC_ROLL roll angle (deg) of flight controller wrt aircraft body float 0.0f 0 360 FC_PITCH pitch angle (deg) of flight controller wrt aircraft body float 0.0f 0 360 FC_YAW yaw angle (deg) of flight controller wrt aircraft body float 0.0f 0 360 ARM_THRESHOLD RC deviation from max/min in yaw and throttle for arming and disarming check (us) float 0.15 0 500 OFFBOARD_TIMEOUT Timeout in milliseconds for offboard commands, after which RC override is activated int 100 0 100000"},{"location":"user-guide/preflight-checks/","title":"Pre-Flight Checklist","text":"<p>This is an example of a ROSflight pre-flight checklist. You will likely need to augment this with checks specific to both (a) your hardware and (b) the code running on your companion computer.</p>"},{"location":"user-guide/preflight-checks/#before-powering-up-motors","title":"Before powering up motors","text":"<ul> <li> ROS2 is running on the companion computer, communicating with the base station</li> <li> <code>rosflight_io</code> reports no errors</li> <li> Sensors are calibrated and publishing<ul> <li> IMU (re-calibrate every flight): <code>ros2 service call /calibrate_imu std_srvs/srv/Trigger</code></li> <li> Barometer: <code>ros2 service call /calibrate_baro std_srvs/srv/Trigger</code></li> <li> Sonar (if attached)</li> <li> Airspeed (if attached)</li> </ul> </li> <li> Estimated attitude is being published and looks accurate</li> <li> Published outputs look reasonable</li> <li> Parameter Check (if using a fixed-wing, there are about 8 parameters you will need to change from default)</li> <li> RC communication</li> <li> Failsafe behavior</li> <li> Arming and disarming</li> <li> RC override behavior</li> <li> RC range test</li> <li> Wire-wiggle test (wiggle all wires to look for bad connections)</li> <li> If desired, logging is turned on (e.g. recording a ros2 bag)</li> </ul>"},{"location":"user-guide/preflight-checks/#after-powering-up-motors","title":"After Powering Up Motors","text":"<p>Danger</p> <p>Be sure the flight controller is disarmed before powering up motors!!!</p> <ul> <li> Arm/Disarm test</li> <li> Propeller spin test (check directions and response to stick inputs)</li> <li> Control surface test (fixed-wing)</li> <li> Response to offboard controls</li> </ul>"},{"location":"user-guide/rc-configuration/","title":"RC Configuration","text":""},{"location":"user-guide/rc-configuration/#binding-your-transmitter-to-your-receiver","title":"Binding your Transmitter to your Receiver","text":"<p>Follow the instructions in your user manual to bind your transmitter to your RC receiver. You may also be able to find a guide on YouTube with instructions; just search for your particular transmitter and receiver model.</p>"},{"location":"user-guide/rc-configuration/#rc-transmitter-calibration","title":"RC Transmitter Calibration","text":"<p>To avoid confusion and to reduce code complexity in the firmware source code, ROSflight does not perform software calibration of RC transmitters. This means that RC calibration must be done on the transmitter itself, as opposed to in software. This is pretty straight-forward for most modern transmitters.</p>"},{"location":"user-guide/rc-configuration/#configure-the-full-stick-output-for-each-channel","title":"Configure the full stick output for each channel","text":"<p>The easiest way to do this is to enter the \"Servo Setup\" Menu (for Spektrum transmitters) and change the servo travel variable. You can watch the raw RC readings from the flight controller by echoing the rc_raw topic from <code>rosflight_io</code></p> <pre><code>ros2 topic echo /rc_raw\n</code></pre> <ul> <li>Center both sticks on your transmitter</li> <li>Apply subtrim until the first four channels all read 1500 exactly (or as close as possible--some RC receivers are worse than others and cannot exactly output 1500 us)</li> <li>Set the channel endpoints so that maximum stick deflections result in readings of 1000 and 2000 us.</li> </ul>"},{"location":"user-guide/rc-configuration/#configure-stick-directions-for-roll-pitch-and-yaw-channels","title":"Configure stick directions for roll, pitch, and yaw channels.","text":"<p>You now have to make sure your RC transmitter is sending commands consistent with the north-east-down (NED) frame assumed by ROSflight.</p> <p>You may find this graphic helpful. It shows all the basic stick positions, and the associated output from the first four channels when looking at a raw AETR (aileron, elevator, throttle, rudder) RC signal from <code>rosflight_io</code>. Make sure that the stick output is in the correct direction.</p> <p></p> <p>It should be noted that channel assignment can be modified via the <code>RC_*_CHN</code> parameters. So, if you are using something other than AETR assignment, the channel index for each stick may be different, but the direction should be the same.</p>"},{"location":"user-guide/rc-configuration/#switch-configuration","title":"Switch Configuration","text":"<p>Switches can be configured for the following functions. To disable a switch for a specific, default function, set the corresponding parameter to <code>-1</code>. Be sure to check that the switch directions operate as you intend, and reverse them in your transmitter if necessary.</p>"},{"location":"user-guide/rc-configuration/#safety-pilot-configuration","title":"Safety Pilot Configuration","text":"<p>The <code>RC_ATT_OVRD_CHN</code> parameter maps a switch to override attitude commands with RC control. The <code>RC_THR_OVRD_CHN</code> parameter maps a switch to override throttle commands with RC control. To override both with a single switch, set both parameters to the same value (this is the default behavior).</p>"},{"location":"user-guide/rc-configuration/#arming","title":"Arming","text":"<p>By default, arming is done with the sticks (left stick down and right to arm, down and left to disarm). To use a switch instead, set the <code>ARM_CHANNEL</code> parameter to the desired channel. Setting an arming switch disables arming with the sticks.</p>"},{"location":"user-guide/rc-configuration/#flight-mode","title":"Flight Mode","text":"<p>If desired, you can map a switch to select between attitude control types (angle and rate) in flight by setting the <code>RC_ATT_CTRL_CHN</code> parameter to the desired channel. This can be useful if, for example, you are learning rate mode but want to be able to switch back to attitude mode to help stabilize the vehicle. This feature is disabled by default.</p>"},{"location":"user-guide/ros2-setup/","title":"Installing/Setting up ROS2","text":"<p>You will need to get ROS2 on both the companion computer and the base station laptop. This can be done with a native installation or with Docker. To install ROS2 natively, Check out the official ROS2 Installation page for details. Make sure to install both the <code>ros-humble-desktop</code> and <code>ros-dev-tools</code> packages, or the equivalent packages for your version of ROS2. <code>ros-humble-ros-base</code> can be used instead of <code>ros-humble-desktop</code> if you don't need GUI tools or the simulation.</p> <p>We support all fixed-release ROS2 versions that are not EOL, which currently includes ROS2 Humble and ROS2 Iron. ROS2 Rolling is not fixed-release and is therefore not officially supported. </p>"},{"location":"user-guide/ros2-setup/#installing-rosflight","title":"Installing ROSflight","text":"<p>You will need to install the ROSflight packages on both the companion computer and the base station computer. The companion computer will run the node that actually communicates with the flight controller over a serial connection, while the base station needs the message and service definitions to be able to call services or subscribe and publish to topics.</p>"},{"location":"user-guide/ros2-setup/#from-source","title":"From Source","text":"<p>First, set up a ROS2 workspace:</p> <pre><code>mkdir -p ~/rosflight_ws/src\ncd ~/rosflight_ws/src\n</code></pre> <p>Next, download the source code into your workspace (include the <code>--recursive</code> argument to download the necessary submodules):</p> <pre><code>git clone --recursive https://github.com/rosflight/rosflight_ros_pkgs.git\n</code></pre> <p>Install dependencies: <pre><code>sudo rosdep init\nrosdep update\nrosdep install --from-path . -y --ignore-src\n</code></pre></p> <p>Note</p> <p>Gazebo does not have an arm64 build target. If using a companion computer with arm64 architecture, append <code>--skip-keys=\"gazebo_dev gazebo_plugins gazebo_ros gazebo\"</code> to the <code>rosdep install</code> command above. This will skip installing Gazebo and the compilation of rosflight_sim, which currently requires Gazebo.</p> <p>Build the packages: <pre><code>cd ~/rosflight_ws\ncolcon build\n</code></pre></p> <p>Source the setup file and set it to be sourced automatically: <pre><code>source ~/rosflight_ws/install/setup.bash\necho \"source ~/rosflight_ws/install/setup.bash\" &gt;&gt; ~/.bashrc\n</code></pre></p> <p>Note</p> <p>You'll also need to source the file at <code>/usr/share/gazebo/setup.sh</code> if you plan to use the Gazebo simulator.</p>"},{"location":"user-guide/ros2-setup/#running-rosflight_io","title":"Running rosflight_io","text":"<p>The <code>rosflight_io</code> node is the bridge between ROS2 and the MAVLink communication with the flight controller. This node must be run on the computer that has the physical serial connection to your flight controller. To run this node, use something like the following command: <pre><code>ros2 run rosflight_io rosflight_io --ros-args -p port:=/dev/ttyUSB0\n</code></pre> Replace <code>/dev/ttyUSB0</code> with the port your flight controller is connected to.</p>"},{"location":"user-guide/ros2-setup/#using-a-docker-container-to-run-ros2","title":"Using a Docker Container to run ROS2","text":"<p>Note</p> <p>This guide was written for using Linux as the host machine, but theoretically you should be able to use Docker to do the same thing on Mac or Windows. However, the specifics of the commands may be different. Please refer to the Docker documentation for information on how to use Docker on a non-Linux system.</p> <p>Tip</p> <p>This guide was written using ROS2 Humble Docker images, but any distribution of ROS can be used. Just replace <code>humble</code> with the name of the distribution you want to use.</p> <p>If you aren't running a compatible version of Linux for ROS2, don't want to make changes to your system, want to be able to easily switch between ROS verions, or just want to containerize your applications, then you can use Docker containers. To get started, install Docker Engine, sometimes referred to as Docker server.</p> <p>Docker works by running self-contained systems called containers, which act kind of like a separate computer system but without all the overhead of a full virtual machine. Docker containers are based on Docker images, which provide the initial operating system, files, and programs for the Docker container. Fortunately, the developers of ROS provide Docker images for nearly all versions of ROS, which makes it very easy to get any version of ROS up and running on your system very quickly.</p> <ul> <li>To start a Docker container with ROS run this command: <pre><code>docker run -it ros:humble\n</code></pre></li> </ul> <p>Once completed, you should enter a bash terminal in a fresh installation of Ubuntu and ROS! However, the container does not have access to any USB devices, source files on your system, or your network to be able to communicate with different computers. To do these things we'll need to add more arguments to the <code>docker run</code> command.</p> <ul> <li> <p>To give access to source file on your system, mount a folder on your system to the docker container with the <code>-v</code> argument: <pre><code>docker run -it -v /folder_to_mount_from_host:/location_to_mount_folder_in_container ros:humble\n</code></pre></p> </li> <li> <p>To give access to a USB device, you need to mount the location of the USB device and give the container sudo access to your host system with <code>--privileged</code>: <pre><code>docker run -it -v /dev/usb_to_mount:/dev/USB --privileged ros:humble\n</code></pre></p> </li> <li> <p>You can also mount the entire <code>/dev</code> folder to the container if you want to simplify the process of giving access to USB devices by not needing to know the address of the USB device beforehand. However, the more resources you give to the container, the less secure it is: <pre><code>docker run -it -v /dev:/dev --privileged ros:humble\n</code></pre></p> </li> <li> <p>To give access to your network, specify the network to use as the host's network with <code>--network host</code>. <pre><code>docker run -it --network host ros:humble\n</code></pre></p> </li> </ul> <p>It is worth noting that every time you use the <code>docker run</code> command, a new container with those specific arguments are created. So, if you want a container with access to all those things, you need to use all the arguments at once.</p> <ul> <li>As an example, if I wanted to make a ROS2 Humble container with access to a USB device at <code>/dev/ttyUSB0</code>, access to my host network, access to the source files at <code>~/rosflight_ws</code>, and give the container a convenient name of <code>rosflight</code> with the <code>--name</code> argument, I would use this command: <pre><code>docker run --name rosflight -it -v /dev/ttyUSB0:/dev/ttyUSB0 --privileged --network host -v ~/rosflight_ws:/root/rosflight_ws ros:humble\n</code></pre></li> </ul> <p>Something the previous commands don't include is the ability to render GUI tools (like rqt_graph and Gazebo). Being able to render GUI tools can be done a number of ways, but an easy way is to give the container access to your system's X11 windowing system. Note that this isn't the most secure method and doesn't include GPU acceleration. (For more information about including GPU acceleration, refer to the guide found here.)</p> <ul> <li> <p>To give access to the host's windowing system, use the following commands. Note that the base Docker image is <code>osrf/ros:humble-desktop-full</code>, as <code>ros:humble</code> doesn't include GUI tools in the image. Also, <code>xhost +local:root</code> needs to be run once per login session and is not persistent. <pre><code>xhost +local:root\ndocker run -it --env=\"DISPLAY\" --env=\"QT_X11_NO_MITSHM=1\" --volume=\"/tmp/.X11-unix:/tmp/.X11-unix:rw\" osrf/ros:humble-desktop-full\n</code></pre></p> </li> <li> <p>To create a GUI enabled ROS container named <code>rosflight</code> with access to the host network, source files found at <code>~/rosflight_ws</code>, and a USB device, use this command: <pre><code>xhost +local:root\ndocker run --name rosflight -it -v /dev/ttyUSB0:/dev/ttyUSB0 --privileged --network host -v ~/rosflight_ws:/rosflight_ws --env=\"DISPLAY\" --env=\"QT_X11_NO_MITSHM=1\" --volume=\"/tmp/.X11-unix:/tmp/.X11-unix:rw\" osrf/ros:humble-desktop-full\n</code></pre></p> </li> </ul> <p>Warning</p> <p>During testing, we found some strange behavior with ROS when running a GUI enabled container on a system with ROS already installed. If you need a GUI enabled system, try to do so on a system without ROS installed (or at the very least avoid sourcing/using ROS on your system). Also avoid having multiple GUI enabled containers running at once.</p> <p>Some other useful Docker commands:</p> <ul> <li> <p>To see all containers that exist on your system and their names: <pre><code>docker ps -a\n</code></pre></p> </li> <li> <p>To start a container named <code>rosflight</code> that was previously created with the <code>docker run</code> command: <pre><code>docker start -i rosflight\n</code></pre></p> </li> <li> <p>To open another bash terminal in a container named <code>rosflight</code> that is already running: <pre><code>docker exec -it rosflight bash\n</code></pre></p> </li> <li> <p>To delete a container named <code>rosflight</code>: <pre><code>docker rm rosflight\n</code></pre></p> </li> </ul> <p>You should now be able to create Docker containers with everything you need to run ROSflight! Docker is a very powerful tool and there is much more you can do with Docker to improve your development workflow. However, we're not interested in making an exhaustive Docker guide so please refer to the Docker documentation or other online guides to learn more.</p>"},{"location":"user-guide/roscopter-setup/","title":"ROScopter","text":"<p>ROScopter is still under development. Check the github repo for the latest instructions.</p>"},{"location":"user-guide/rosplane-setup/","title":"ROSplane Setup","text":"<p>ROSplane v2.0.0-beta is now available! Check the github repo for the latest instructions.</p> <p>ROSplane is a basic fixed-wing autopilot build around ROS2 for use with the ROSflight autopilot. It is built according to the methods published in Small Unmanned Aircraft: Theory and Practice by Dr. Randy Beard and Dr. Tim McLain.</p>"},{"location":"user-guide/rosplane-setup/#requirements","title":"Requirements","text":"<p>ROSplane requires a working ROS2 installation on a companion computer. ROSplane will most often be used in conjunction with the ROSflight firmware and the firmware interface (aka <code>rosflight_ros_pkgs</code>).</p> <p>Follow the instructions on ROS2 Setup to install and set up ROS2 and <code>rosflight_ros_pkgs</code>.</p>"},{"location":"user-guide/rosplane-setup/#installation","title":"Installation","text":"<p>You will need to install ROSplane on the companion computer.</p> <p>First, navigate to the src directory of the ROS2 workspace and clone the git repository:</p> <pre><code>cd /path/to/rosflight_ws/src\ngit clone https://github.com/rosflight/rosplane.git\n</code></pre> <p>Note</p> <p>Your <code>rosflight_ws</code> file structure should now look like: <pre><code>rosflight_ws\n  \u2514\u2500\u2500 src \n    \u251c\u2500\u2500 rosflight_ros_pkgs\n    \u2514\u2500\u2500 rosplane \n</code></pre></p> <p>Then navigate to the top of the <code>rosflight_ws</code> directory and build:</p> <pre><code>cd ..\ncolcon build\n</code></pre> <p>Next, source the <code>rosflight_ws</code> install files. If you already added the source command to your <code>.bashrc</code> from the ROS2 Setup page, then you can skip this step.</p> <pre><code># source the install file\nsource install/setup.bash\n\n# add it to your .bashrc\necho \"source install/setup.bash &gt;&gt; $HOME/.bashrc\"\n</code></pre> <p>Note that sourcing the <code>setup.bash</code> file in the <code>rosflight_ws</code> directory will install all ROS2 packages in any subdirectories.</p>"},{"location":"user-guide/rosplane-setup/#running-rosplane-sil","title":"Running ROSplane SIL","text":"<p>A controller or a simulated controller can be used to fly the aircraft in simulation. See the <code>README.md</code> file for the <code>rosflight_ros_pkgs</code> package for more information on RC controll in simulation.</p>"},{"location":"user-guide/rosplane-setup/#launching","title":"Launching","text":""},{"location":"user-guide/rosplane-setup/#recommended-method","title":"Recommended Method","text":"<p>A convenience bash script has been included that uses tmux to launch Gazebo, an instance of the ROSflight firmware, and ROSplane. Note that this requires tmux, so you may need to install it with <code>sudo apt install tmux</code>. Run <pre><code>./src/rosplane/rosplane/scripts/rosplane_gcs_launch.sh\n</code></pre> from the <code>rosflight_ws</code> directory. Note that the script needs options specified, so it will fail. However,it will print out the required configuration options. See the script for more information.</p>"},{"location":"user-guide/rosplane-setup/#alternative-method","title":"Alternative Method","text":"<p>Alternatively, you can run each of the commands in the bash script individually: <pre><code># Terminal 1 - Launches Gazebo and a simulated instance of the firmware\nros2 launch rosflight_sim fixedwing.launch.py\n\n# Terminal 2 - Runs rosflight_io configured for SIL to interface with the firmware\nros2 run rosflight_io rosflight_io --ros-args -p udp:=true\n\n# Terminal 3 - Launches rosplane with the Anaconda aerodynamic coefficients\nros2 launch rosplane_sim sim.launch.py aircraft:=anaconda\n</code></pre></p> <p>You can also replace the first two commands above with the convenience launch file that does both: <pre><code>ros2 launch rosflight_sim fixedwing_sim_io_joy.launch.py aircraft:=anaconda\n</code></pre> Remember to launch ROSplane if you use this method.</p>"},{"location":"user-guide/rosplane-setup/#additional-setup","title":"Additional Setup","text":""},{"location":"user-guide/rosplane-setup/#recommended-method_1","title":"Recommended Method","text":"<p>If this is your first time launching ROSplane, make sure to run the convenience launch script to initialize the firmware parameters and calibrate the IMU. <pre><code>ros2 launch rosflight_sim fixedwing_init_firmware.launch.py\n</code></pre></p>"},{"location":"user-guide/rosplane-setup/#alternative-method_1","title":"Alternative Method","text":"<p>Alternatively, you can run the following commands to initialize firmware parameters and calibrate the IMU. Firmware parameters should first be loaded using <pre><code>ros2 service call /param_load_from_file rosflight_msgs/srv/ParamFile \"filename: /path/to/rosflight_ws/src/rosflight_ros_pkgs/rosflight_sim/params/fixedwing_firmware.yaml\"\n</code></pre></p> <p>The IMU should then be calibrated to remove the random biases generated at startup. Note that the random number generator used to create these biases is seeded with a constant value, so this calibration should only need to be performed once. See the code to change the way these biases are calculated. <pre><code>ros2 service call /calibrate_imu std_srvs/srv/Trigger\n</code></pre></p> <p>After calibrating, write the parameters to a file using: <pre><code>ros2 service call /param_write std_srvs/srv/Trigger\n</code></pre> This command will create a directory named <code>rosflight_memory</code> where the parameters are written. The ROSflight firmware will automatically check if the <code>rosflight_memory</code> directory is present when launched and will use those parameters if available.</p> <p>Note</p> <p>The ROSflight firmware will only look for the <code>rosflight_memory</code> directory in the directory where the launch command is run. You must launch <code>rosflight_sim</code> in the same directory to use the saved parameters; otherwise, reload and re-write the parameters.</p>"},{"location":"user-guide/rosplane-setup/#flying-in-sim","title":"Flying in Sim","text":"<p>Once you have the simulation booted up, use channel 4 of a connected transmitter to arm. If you are using a simulated transmitter, use <code>ros2 service call /toggle_arm std_srvs/srv/Trigger</code> to toggle arm/disarm.</p> <p>After arming, the plane will operate under RC control. Verify that the commands are working and that the aircraft is responding as expected.</p> <p>To fly autonomously, use channel 5 to disable RC override. If using a simulated transmitter, use <code>ros2 service call /toggle_override std_srvs/srv/Trigger</code> to toggle RC override on/off.</p> <p>The plane should then take off or fly autonomously in the Gazebo simulator!</p>"},{"location":"user-guide/rosplane-setup/#running-rosplane-on-hardware","title":"Running ROSplane on Hardware","text":"<p>Ensure <code>rosflight_io</code> is running on the companion computer, and that the flight controller is connects to the companion computer.</p> <p>Launch ROSplane using <pre><code>ros2 launch rosplane rosplane.launch.py\n</code></pre></p> <p>Arm the aircraft using channel 4 of the safety RC transmitter. When ready to let ROSplane take control, use channel 5 of the RC transmitter to disable RC override.</p> <p>Warning</p> <p>Disabling RC override on hardware will turn control over to ROSplane. A safety pilot should always be ready to take control, especially when running untested code.</p>"},{"location":"user-guide/rosplane-setup/#flying-waypoint-missions-in-sim-and-hardware","title":"Flying Waypoint Missions (in sim and hardware)","text":"<p>Autonomous waypoint missions can easily be flown using ROSplane. The waypoints of a mission are controlled by the <code>path_planner</code> node. These waypoints are sent to the <code>path_manager</code> node. Low level path-following is done by the <code>path_follower</code> node. See \"Small Unmanned Aircraft: Theory and Practice\" by Dr. Randy Beard and Dr. Tim McLain for more information on the architecture. See Path Planning for more information on how to use and tune the path planner, manager, and follower.</p>"},{"location":"user-guide/rosplane-setup/#adding-waypoints","title":"Adding waypoints","text":""},{"location":"user-guide/rosplane-setup/#recommended-method_2","title":"Recommended Method","text":"<p>ROSplane initializes with no waypoints added to the <code>path_planner</code>. We recommend using a mission .yaml file (an example mission can be found in <code>rosplane/params/fixedwing_mission.yaml</code>). Loading the mission can be done using </p> <pre><code>ros2 service call /load_mission_from_file rosflight_msgs/srv/ParamFile \"{filename: &lt;FILENAME&gt;}\"\n</code></pre> <p>where <code>FILENAME</code> is the absolute path to the mission .yaml file. Note that the origin (0,0,0) is placed at the GNSS location where ROSplane was initialized.</p> <p>Note</p> <p>All waypoints must include a valid <code>[X, Y, Z]</code>, <code>va_d</code>, and <code>lla</code> values.</p>"},{"location":"user-guide/rosplane-setup/#alternative-method_2","title":"Alternative Method","text":"<p>Alternatively, you can add a waypoint one at a time by calling the appropriate service</p> <pre><code>ros2 service call /add_waypoint rosplane_msgs/srv/AddWaypoint \"{w: [X, Y, Z], chi_d: CHI_D, lla: USE_LLA, use_chi: USE_CHI, va_d: VA_D}\"\n</code></pre> <p>where <code>[X, Y, Z]</code> is the NED position of the waypoint from the origin (in meters) OR the GNSS location of the waypoint (LLA), <code>CHI_D</code> is the desired heading at the waypoint, and <code>VA_D</code> is the airspeed at the waypoint. Set the <code>lla</code> field to <code>true</code> if the waypoint <code>[X, Y, Z]</code> field is given in GNSS coordinates and <code>false</code> if given in NED coordinates. Corners in the path are controlled by <code>USE_CHI</code>, where a value of <code>True</code> will cause ROSplane to use a Dubins path planner and a value of <code>False</code> will cause a fillet path planner to be used. Adding waypoints can be done at any time, even after loading from a file.</p> <p>Clearing waypoints can be done using  <pre><code>ros2 service call /clear_waypoints std_msgs/srv/Trigger\n</code></pre></p>"},{"location":"user-guide/rosplane-setup/#publishing-waypoints","title":"Publishing Waypoints","text":"<p>The <code>path_planner</code> node automatically publishes a small number of waypoints (default is 3) at the beginning of this mission. This number is controlled by the <code>num_waypoints_to_publish_at_start</code> ROS2 parameter. </p> <p>Additional waypoints can be published using  <pre><code>ros2 service call /publish_next_waypoint std_srvs/srv/Trigger\n</code></pre></p>"},{"location":"user-guide/running-gazebo-simulation/","title":"Running Simulations in Gazebo","text":"<p>ROSflight comes with a useful tool allowing it to perform software-in-the-loop (SIL) simulations of the ROSflight firmware in Gazebo.</p>"},{"location":"user-guide/running-gazebo-simulation/#architecture-of-the-sil-simulation","title":"Architecture of the SIL Simulation","text":"<p>To best mimic the hardware experience of ROSflight, the SIL plugin for Gazebo actually implements the firmware source code as a library. We just implemented a different \"board layer\" which uses gazebo instead of hardware calls for things like <code>imu_read()</code> and <code>pwm_write()</code>. Instead of a serial link over USB to the flight controller, we use a UDP connection bouncing off of localhost to communicate between <code>rosflight_io</code> and the firmware. This means the interface to the SIL plugin is identical to that of hardware. <code>rosflight_io</code> is the main gateway to the firmware in simulation, just as it is in hardware.</p> <p>The following table summarizes the correlation between connections in hardware and simulation:</p> Connection Type Hardware Simulation Serial communications to <code>rosflight_io</code> USB / UART UDP RC PPM Receiver ROS2 <code>RC</code> topic (<code>rosflight_msgs/RCRaw</code>) Motors PWM Gazebo Plugin Sensors SPI/I2C Gazebo Plugin"},{"location":"user-guide/running-gazebo-simulation/#quick-start-guide-to-sil-simulation","title":"Quick-Start Guide to SIL Simulation","text":"<p>Note</p> <p>To simulate a fixed-wing mav, just change all instances of <code>multirotor</code> in the steps below to <code>fixedwing</code>.</p> <ul> <li> <p>Setup ROSflight with the ROS2 Setup guide, making sure to install the <code>-desktop</code> package of ROS2, not the <code>-ros-base</code>.</p> </li> <li> <p>Source the Gazebo setup file if you haven't added it to <code>~/.bashrc</code>: <pre><code>source /usr/share/gazebo/setup.sh\n</code></pre></p> </li> <li> <p>Launch Gazebo with the ROSflight SIL: <pre><code>ros2 launch rosflight_sim multirotor.launch.py\n</code></pre></p> </li> <li> <p>Gazebo should now be running, and you should have the following <code>rqt_graph</code>.</p> </li> </ul> <p></p> <ul> <li> <p>At this point, you can't actually do anything because there is no RC connection and no <code>rosflight_io</code> to talk to the firmware. Let's start by running a <code>rosflight_io</code> node. In a separate terminal, run: <pre><code>ros2 run rosflight_io rosflight_io --ros-args -p udp:=true\n</code></pre></p> <ul> <li>The <code>udp</code> parameter tells <code>rosflight_io</code> to simulate a serial connection over UDP rather than using the USB connection to hardware</li> </ul> </li> </ul> <p>Your <code>rqt_graph</code> should look something like the following image. This looks funny because ROS2 doesn't actually know that there is a UDP connection between <code>rosflight_io</code> and gazebo. There is one, though, and you can test it by echoing any of the topics published by <code>rosflight_io</code>.</p> <p></p> <ul> <li>Start up a simulated RC connection. The easiest way to do this is with the ROSflight utility <code>rc_joy.py</code>. Connect a joystick to the computer (or transmitter) and run:      <pre><code>ros2 run rosflight_sim rc_joy.py --ros-args --remap /RC:=/multirotor/RC\n</code></pre>     This simulates the RC connection in hardware. If everything is mapped correctly, you should now be able to arm, disarm and fly the aircraft in simulation!</li> </ul> <p>Tip</p> <p>To start the Gazebo sim, rosflight_io node, and rc_joy.py utility all at once, run this command instead of the three commands individually: <pre><code>ros2 launch rosflight_sim multirotor_sim_io_joy.launch.py    \n</code></pre></p> <p>Note</p> <p>It is much easier to fly with a real transmitter than with an Xbox-type controller. FrSky Taranis QX7 transmitters, Radiomaster TX16s transmitters, and RealFlight controllers are also supported. Non-Xbox joysticks may have incorrect mappings. If your joystick does not work, and you write your own mapping, please contribute back your new joystick mapping!</p> <p>Remember, the SIL tries its best to replicate hardware. That means you have to calibrate and set parameters in the same way you do in hardware. See the Hardware Setup and Parameter Configuration pages in this documentation for instructions on how to perform all preflight configuration before the aircraft will arm. You can also run  <pre><code>ros2 launch rosflight_sim multirotor_init_firmware.launch.py\n</code></pre> to load all required parameters and perform initial calibrations for a quick simulation setup.</p>"}]}
\ No newline at end of file
diff --git a/git-main/sitemap.xml b/git-main/sitemap.xml
index 88d2bf2..79ab79a 100644
--- a/git-main/sitemap.xml
+++ b/git-main/sitemap.xml
@@ -2,157 +2,157 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>http://rosflight.org/git-main/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/contribution-guidelines/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/style-guide/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/firmware/building-and-flashing/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/firmware/code-architecture/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/firmware/debugging/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/firmware/unit-tests/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/rosplane/parameter-management/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/rosplane/controller/controller-base/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/rosplane/controller/controller-general-overview/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/rosplane/controller/controller-outline/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/rosplane/controller/controller-software-architecture/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/rosplane/controller/controller-state-machine/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/developer-guide/rosplane/controller/controller-total-energy/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
-         <loc>http://rosflight.org/git-main/developer-guide/rosplane/path-planning/path-follower/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <loc>http://rosflight.org/git-main/developer-guide/rosplane/navigation/navigation-overview/</loc>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
-         <loc>http://rosflight.org/git-main/developer-guide/rosplane/path-planning/path-manager/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <loc>http://rosflight.org/git-main/developer-guide/rosplane/navigation/path-follower/</loc>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
-         <loc>http://rosflight.org/git-main/developer-guide/rosplane/path-planning/path-planner/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <loc>http://rosflight.org/git-main/developer-guide/rosplane/navigation/path-manager/</loc>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
-         <loc>http://rosflight.org/git-main/developer-guide/rosplane/path-planning/path-planning-overview/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <loc>http://rosflight.org/git-main/developer-guide/rosplane/navigation/path-planner/</loc>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/autonomous-flight/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/flight-controller-setup/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/getting-started/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/hardware-setup/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/improving-firmware-performance/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/overview/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/parameter-configuration/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/preflight-checks/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/rc-configuration/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/ros2-setup/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/roscopter-setup/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/rosplane-setup/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>http://rosflight.org/git-main/user-guide/running-gazebo-simulation/</loc>
-         <lastmod>2024-06-18</lastmod>
+         <lastmod>2024-06-24</lastmod>
          <changefreq>daily</changefreq>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/git-main/sitemap.xml.gz b/git-main/sitemap.xml.gz
index e12abe5e2bda3b033cde2d8da57ae17f762b505d..80d9d7f11402f61e60382fee27fcb329b0e052eb 100644
GIT binary patch
literal 545
zcmV++0^a=}iwFn+w|Hg(|8r?{Wo=<_E_iKh0Nq#1j@vK{yzf^8zAMTGi=r(O@2y|Z
zegGrWvQRx-iHe(ked##a`d0K(EaQu1dL+zH=FmF4{tSL|##~&A$L4vvYc?27>RhzP
z=G)gV>SOcTJ{@ZI1!=?JSdPs=G=A24nx<`WgaO8~P1)*V27V~|7Sy}#r>1?{@HH>6
zjIP(gC)3_m$*J_-*@3Q0SVt;=i~68v%z6qG3aM-NyZwvWeNg)shTLK+m>D2i>@)so
zJ8=GT(5uM8MZb~xcUm2u(Weo!vek8{O^TG=sS@XJ33(T>NTFZo;_)^XLb-Q2OpsBZ
zs`K-Asvvf%XJP|Ch*QC}h6=J7xMmF1EN>q=JXLEY=DtRT5Ec?suM8VKMARc>2uS=Q
zKm>~cBZ(7nHP7Td=G9Q0px}c@u^2IfSBX39+2QmcvQnkF%RPvil6so$K%@)*O&b9r
z&tzc_vtN{mOKPqxdl4ro!r57v{}xw6x&E+{GXf2&=PgPT@0WBTOIMYzV~)o6tD}}T
z2~a7;6jCi}K?>l!yjE+&MXI9!<`#+OvlBOnOxOuvJV5TQZCXl-T^MsZ&q=-?I20Fb
zpE7%kK>-5ZdskXf{c{}RTI`*zdGSC2%ro9yWI*%12%wyexGXbbFUB|+VbVx~y2<_b
jLk{5@<Lt~9e&H#p;zITR>07?uI8W_w*E+rEd=~%!I$sJ}

literal 540
zcmV+%0^|K3iwFn+&TwV||8r?{Wo=<_E_iKh0Nq%@j@uv*z3*2<z7w)hRc))pd+Qgp
zAAs=~qXOfFA#VEh9qeSATh&Wd?27?E(0gO%4fg5vhj+UR#AGp?o9F$Z*+J0Q+hESk
zx36EsOY_=3opN*uXvg4?&do?PeU@^b=Y6sSUQKC_(a5An?j(5|l!yJNrhVG+RTfxV
z%XM<7+uJG;)8MQbX<5Qp5?<LLPqJVhr>I08`}TM^eh`O`;`xOkx3LG99#t?fM0jg^
zW!?28A4XO#@}11z)9T>@4kw7hWZQ$(7%18<6UT2IayCG!g?^%|gIl{2%7cx5RuN>E
ztt<OfsL+dniH+Q;P6g*02o?3nIio4Z`rbniT{fo1*yq3yf<)EiE5jzI0?0{4<$?Ht
zS3w!@5U4s4i+Q4R5FeVNQwcUA#Xx|loItLy7Yp-7WMQUK<u;-w;XuU>s&wH$X(L6z
zGg;VX-WMTpN|nqq*9v``Mp2rf6wIYJuq>Qe;|8>>#b^^!mfnV>l#}xRUWame*P}9F
zK#w_z6<Go2^|5&LU!Xiyz}x^)*&tjmB0*mP<59(asoJ%K*!n5rr3Cr@{UJDe2aN2Q
z8Y&P_k$L?7I^tX$tjST8A2c;Ek8pR95%l*|0p+Nxi!vjQ)ffjOG)`1eHMyTf>LHxh
e^N~?Mp+k|Z&+Z@X<>kh4YJUNhd7>4I7XSe0$O#Pq

diff --git a/git-main/user-guide/autonomous-flight/index.html b/git-main/user-guide/autonomous-flight/index.html
index 6d2ecce..3e402fc 100644
--- a/git-main/user-guide/autonomous-flight/index.html
+++ b/git-main/user-guide/autonomous-flight/index.html
@@ -1133,7 +1133,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1143,7 +1143,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1154,11 +1154,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1175,7 +1175,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1196,7 +1196,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1217,7 +1217,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/flight-controller-setup/index.html b/git-main/user-guide/flight-controller-setup/index.html
index de30cae..cc8b631 100644
--- a/git-main/user-guide/flight-controller-setup/index.html
+++ b/git-main/user-guide/flight-controller-setup/index.html
@@ -1166,7 +1166,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1176,7 +1176,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1187,11 +1187,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1208,7 +1208,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1229,7 +1229,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1250,7 +1250,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/getting-started/index.html b/git-main/user-guide/getting-started/index.html
index 80543a2..70e0fc5 100644
--- a/git-main/user-guide/getting-started/index.html
+++ b/git-main/user-guide/getting-started/index.html
@@ -1166,7 +1166,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1176,7 +1176,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1187,11 +1187,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1208,7 +1208,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1229,7 +1229,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1250,7 +1250,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/hardware-setup/index.html b/git-main/user-guide/hardware-setup/index.html
index f254a09..d22aafe 100644
--- a/git-main/user-guide/hardware-setup/index.html
+++ b/git-main/user-guide/hardware-setup/index.html
@@ -1271,7 +1271,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1281,7 +1281,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1292,11 +1292,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1313,7 +1313,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1334,7 +1334,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1355,7 +1355,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/improving-firmware-performance/index.html b/git-main/user-guide/improving-firmware-performance/index.html
index a2a72ee..234dacc 100644
--- a/git-main/user-guide/improving-firmware-performance/index.html
+++ b/git-main/user-guide/improving-firmware-performance/index.html
@@ -1208,7 +1208,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1218,7 +1218,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1229,11 +1229,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1250,7 +1250,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1271,7 +1271,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1292,7 +1292,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/overview/index.html b/git-main/user-guide/overview/index.html
index ebf3b09..266fe4e 100644
--- a/git-main/user-guide/overview/index.html
+++ b/git-main/user-guide/overview/index.html
@@ -1193,7 +1193,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1203,7 +1203,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1214,11 +1214,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1235,7 +1235,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1256,7 +1256,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1277,7 +1277,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/parameter-configuration/index.html b/git-main/user-guide/parameter-configuration/index.html
index 9c28975..697a4b4 100644
--- a/git-main/user-guide/parameter-configuration/index.html
+++ b/git-main/user-guide/parameter-configuration/index.html
@@ -1193,7 +1193,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1203,7 +1203,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1214,11 +1214,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1235,7 +1235,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1256,7 +1256,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1277,7 +1277,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/preflight-checks/index.html b/git-main/user-guide/preflight-checks/index.html
index e48de8b..713d9b8 100644
--- a/git-main/user-guide/preflight-checks/index.html
+++ b/git-main/user-guide/preflight-checks/index.html
@@ -1142,7 +1142,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1152,7 +1152,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1163,11 +1163,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1184,7 +1184,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1205,7 +1205,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1226,7 +1226,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/rc-configuration/index.html b/git-main/user-guide/rc-configuration/index.html
index b449fbf..6bdabb7 100644
--- a/git-main/user-guide/rc-configuration/index.html
+++ b/git-main/user-guide/rc-configuration/index.html
@@ -1208,7 +1208,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1218,7 +1218,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1229,11 +1229,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1250,7 +1250,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1271,7 +1271,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1292,7 +1292,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/ros2-setup/index.html b/git-main/user-guide/ros2-setup/index.html
index db5461b..f202887 100644
--- a/git-main/user-guide/ros2-setup/index.html
+++ b/git-main/user-guide/ros2-setup/index.html
@@ -1166,7 +1166,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1176,7 +1176,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1187,11 +1187,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1208,7 +1208,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1229,7 +1229,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1250,7 +1250,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/roscopter-setup/index.html b/git-main/user-guide/roscopter-setup/index.html
index 238082f..2d5cb27 100644
--- a/git-main/user-guide/roscopter-setup/index.html
+++ b/git-main/user-guide/roscopter-setup/index.html
@@ -1094,7 +1094,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1104,7 +1104,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1115,11 +1115,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1136,7 +1136,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1157,7 +1157,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1178,7 +1178,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/git-main/user-guide/rosplane-setup/index.html b/git-main/user-guide/rosplane-setup/index.html
index d69f790..ff91012 100644
--- a/git-main/user-guide/rosplane-setup/index.html
+++ b/git-main/user-guide/rosplane-setup/index.html
@@ -1298,7 +1298,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1308,7 +1308,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1319,11 +1319,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1340,7 +1340,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1361,7 +1361,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1382,7 +1382,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1758,7 +1758,7 @@ <h2 id="flying-waypoint-missions-in-sim-and-hardware">Flying Waypoint Missions (
 These waypoints are sent to the <code>path_manager</code> node.
 Low level path-following is done by the <code>path_follower</code> node.
 See "Small Unmanned Aircraft: Theory and Practice" by Dr. Randy Beard and Dr. Tim McLain for more information on the architecture.
-See <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/">Path Planning</a> for more information on how to use and tune the path planner, manager, and follower.</p>
+See <a href="../../developer-guide/rosplane/navigation/navigation-overview/">Path Planning</a> for more information on how to use and tune the path planner, manager, and follower.</p>
 <h3 id="adding-waypoints">Adding waypoints<a class="headerlink" href="#adding-waypoints" title="Permanent link">&para;</a></h3>
 <h4 id="recommended-method_2">Recommended Method<a class="headerlink" href="#recommended-method_2" title="Permanent link">&para;</a></h4>
 <p>ROSplane initializes with no waypoints added to the <code>path_planner</code>.
diff --git a/git-main/user-guide/running-gazebo-simulation/index.html b/git-main/user-guide/running-gazebo-simulation/index.html
index a70cded..a225928 100644
--- a/git-main/user-guide/running-gazebo-simulation/index.html
+++ b/git-main/user-guide/running-gazebo-simulation/index.html
@@ -1142,7 +1142,7 @@
             
   
   <span class="md-ellipsis">
-    Path Planning
+    Navigation
   </span>
   
 
@@ -1152,7 +1152,7 @@
         <nav class="md-nav" data-md-level="3" aria-labelledby="__nav_3_4_3_label" aria-expanded="false">
           <label class="md-nav__title" for="__nav_3_4_3">
             <span class="md-nav__icon md-icon"></span>
-            Path Planning
+            Navigation
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
@@ -1163,11 +1163,11 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planning-overview/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/navigation-overview/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
-    Path Planning Overview
+    Navigation Overview
   </span>
   
 
@@ -1184,7 +1184,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-planner/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-planner/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1205,7 +1205,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-manager/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-manager/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1226,7 +1226,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../developer-guide/rosplane/path-planning/path-follower/" class="md-nav__link">
+      <a href="../../developer-guide/rosplane/navigation/path-follower/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/versions.json b/versions.json
index 854a098..502eacd 100644
--- a/versions.json
+++ b/versions.json
@@ -8,8 +8,8 @@
     "version": "v1.3",
     "title": "v1.3",
     "aliases": [
-      "ROS1",
-      "latest"
+      "latest",
+      "ROS1"
     ]
   }
 ]