TSYSGroupBOD/TSYSGroupHandbook
2
0
Fork 0
Code Pull Requests Actions Packages Projects Releases Activity

welcome to the single unified handbook... monorepo for the win

Browse Source
This commit is contained in:
Charles N Wyble - admin
2021-05-16 12:54:15 -05:00
parent 82701c1249
commit e6549eccbe
96 changed files with 5971 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
src/CTO/AvionicsGroundStation.vym Normal file
View File

Binary file not shown.

1
src/CTO/CTO.md Normal file
View File

@@ -0,0 +1 @@
# CTO

674
src/CTO/LICENSE Normal file
View File

@@ -0,0 +1,674 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<https://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.

106
src/CTO/LabComponentInventory.md Normal file
View File

@@ -0,0 +1,106 @@
# Lab Component Inventory
| Drawer # | Contents | Source|
|---|---|---|
| 1 | Jumper Wires F2F 6" |to be identified|
| 2 | Jumper Wires F2F 6" |to be identified|
| 3 | Jumper Wires M2M 6" |to be identified|
| 4 | Jumper Wires M2M 6" |to be identified|
| 5 | Jumper Wires M2F 6" |to be identified|
| 6 | Mixed Jumper Wires M2M 6" |to be identified|
| 7 | Header Strips|to be identified|
| 8 | Heatshrink Tubing|https://www.harborfreight.com/120-piece-heat-shrink-tubing-set-67530.html|
| 9 | Heatshrink Tubing|""|
| 10 | Heatshrink Tubing|""|
| 11 | Wire Connector Butt Splice| https://www.harborfreight.com/30-pack-watertight-heat-shrink-butt-connectors-66729.html |
| 12| Zipties| https://www.homedepot.com/p/Commercial-Electric-4-in-Cable-Tie-Natural-1000-Pack-GT-100M/203531927|
| 13| Push Buttons| amz,ck|
| 14| LED Screen|unknown origin|
| 15| Relays | amz but no specific link|
| 16| Sound | ck |
| 17| Diodes | https://www.amazon.com/gp/product/B007L4DX6Q/ref=ppx_yo_dt_b_asin_title_o04_s01?ie=UTF8&psc=1|
| 18| Crystal Oscillators | https://www.amazon.com/gp/product/B07C4WN68Z/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 |
| 19| Switches | ck |
| 20| Empty Drawer | n/a |
| 21| Empty Drawer | n/a |
| 22| Empty Drawer | n/a |
| 23| Empty Drawer | n/a |
| 24| Empty Drawer | n/a |
| 25| Empty Drawer | n/a |
| 26| Empty Drawer | n/a |
| 27| Empty Drawer | n/a |
| 28| Empty Drawer | n/a |
| 29| Empty Drawer | n/a |
| 30| Empty Drawer | n/a |
| 31| USB to DB9 | https://www.altex.com/manhattan-18-usb-to-serial-converter |
| 32| LiPO Batteries | misc |
| 33| LED assortment | https://www.amazon.com/gp/product/B005GL9ENC/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1 ck|
| 34| Dual Row DIP IC Socket Adaptor Assortment | https://www.amazon.com/gp/product/B07CFWWQ1M/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 |
| 35| Inductors | https://www.amazon.com/gp/product/B085Y6XJL1/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 |
| 36| Elenco CK Kit Electronic components not otherwise categorized| ck |
| 37| Resistors | https://www.amazon.com/gp/product/B0002HBQHW/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1 |
| 38| Resistors | ""|
| 39| Empty Drawer | "" |
| 40| LED | amz |
| 41| USBA-proprietary | misc|
| 42| USBA-proprietary| misc |
| 43| USB (misc to misc) | misc |
| 44| Electrical Clip Assortment | https://www.harborfreight.com/28-piece-electrical-clip-set-67589.html?_br_psugg_q=electrical+connectors |
| 45| Test Leads | https://www.harborfreight.com/18-inch-low-voltage-multi-colored-test-leads-66717.html |
| 46| USBA-Mini | misc |
| 47| USBA-Micro| misc |
| 48| Empty Drawer | n/a |
| 49| Empty Drawer | n/a |
| 50|Empty Drawer | n/a |
| 51|Empty Drawer | n/a |
| 52|Empty Drawer | n/a |
| 53|Empty Drawer | n/a |
| 54| Misc electronics/Rpi etc | misc |
| 55| Empty Drawer | n/a|
| 56| Wifi components | misc |
| 57| USB networking devices | misc|
| 58| Electrical Terminals | https://www.harborfreight.com/150-piece-terminal-and-connector-set-67683.html |
| 59| Electrical Terminals | "" |
| 60| Electrical Terminals | "" |
| 61| misc electronic components to be identified | amz |
| 62| misc electronic components to be identified | amz |
| 63| Wire| misc electronic components to be identified |
| 64| empty drawer| n/a|
| 65| empty drawer| n/a |
| 66| empty drawer| n/a |
| 67| empty drawer| n/a |
| 68| empty drawer| n/a |
| 69| screw terminals | misc electronic components to be identified |
| 70| misc electronic components to be identified | |
| 71| servos | unknown |
| 72| servos | unknown |
| 73| motors | unknown |
| 74| Transitors | https://www.amazon.com/gp/product/B00D8J4EZ2/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 |
| 75| Transistors| "" |
| 76| Transistors | "" |
| 77| Capacitors | https://www.amazon.com/gp/product/B004YHZDW0/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1 |
| 78| Capacitors | "" |
| 79| Capacitors | "" |
| 80| mystery component | amz
| 81| mystery component | amz
| 82| empty drawer | n/a
| 83| empty drawer | n/a
| 84| empty drawer | n/a
| 85| empty drawer | n/a
| 86| empty drawer | n/a
| 87| empty drawer | n/a
| 88| empty drawer | n/a
| 89| empty drawer | n/a
| 90| empty drawer | n/a
| 91| empty drawer | n/a
| 92| empty drawer | n/a
| 93| empty drawer | n/a
| 94| empty drawer | n/a
| 95| LED Strip Connectors | misc |
| 96| empty drawerSoldering drawer:
Hako 599B: https://www.hakko.com/english/products/hakko_599b.html
smd testing : https://www.adafruit.com/product/1359Lab Shopping List
## To Order online:
* magnetizer/demagnetizer

66
src/CTO/LinksFromEngineeringEmails.md Normal file
View File

@@ -0,0 +1,66 @@
Link collection from emails
## Batteries
* <https://www.nasa.gov/pdf/287383main_RP-08-75%2006-069-I%20NASA%20Aerospace%20Flight%20Battery%20Program%20_Part%20I-Volume%20II_FINAL_7-10-08_.pdf>
## Lorawan
* <https://www.thethingsnetwork.org/article/ground-breaking-world-record-lorawan-packet-received-at-702-km-436-miles-distance>
* <https://youtu.be/adhWIo-7gr4>
## Parafoil
* <https://www.nps.edu/documents/106608270/107784480/Fields+-+Lower+Stratospheric+Deployment+Testing+of+a+Ram-Air+Parafoil+System.pdf/be8ab409-185b-495b-8a18-5546be31b288>
* <http://www.sjsu.edu/people/nikos.mourtos/docs/Benton.S12.pdf>
* <https://www.google.com/search?rlz=1CDGOYI_enUS805US805&hl=en-US&ei=myTqW5atLoqsjwTTgruwCQ&ins=false&q=high+altitude+balloon+parafoil+return+filetype%3Apdf&oq=high+altitude+balloon+parafoil+return+filetype%3Apdf&gs_l=mobile-gws-wiz-serp.3...1966.5964..6035...0.0..0.205.1692.0j11j1......0....1.........33i299j33i160.s48wBBrSxoA>
* <http://mindworks.shoutwiki.com/wiki/Guided_Parafoil_System>
* <https://scholar.sun.ac.za/bitstream/handle/10019.1/85757/vanderkolf_flight_2013.pdf?sequence=2&isAllowed=y>
* <https://www.google.com/search?q=parafoil+guidance+navigation+control&rlz=1CDGOYI_enUS805US805&oq=parafoil+guidance+navigation+control&aqs=chrome..69i57.12019j0j9&hl=en-US&sourceid=chrome-mobile&ie=UTF-8>
* <https://www.google.com/search?q=autonomous+parafoil+balloon&rlz=1CDGOYI_enUS805US805&oq=autonomous+parafoil+balloon&aqs=chrome..69i57j69i60j69i61.11987j1j4&hl=en-US&sourceid=chrome-mobile&ie=UTF-8>
* <https://hal.archives-ouvertes.fr/hal-01853228/document>
* <https://mospace.umsystem.edu/xmlui/bitstream/handle/10355/64176/Thesis_2018_Herrington.pdf?sequence=1&isAllowed=y>
## Envelope
* <https://www.google.com/search?rlz=1CDGOYI_enUS805US805&hl=en-US&ei=m1TqW5TXFKTHjgSBmp3wCQ&ins=false&q=super+pressure+balloon+calculator&oq=super+pressure+balloon+calculator&gs_l=mobile-gws-wiz-serp.3...8931.10259..10506...0.0..0.138.1037.0j8......0....1.........0i71j35i304i39j30i10j33i10.BxG5bln1yuw>
* <https://github.com/stanford-ssi/balloons-Parafoil?files=1>
* <https://www.google.com/search?q=winzen+engineering&rlz=1CDGOYI_enUS805US805&oq=winzen+engineering&aqs=chrome..69i57.3827j1j9&hl=en-US&sourceid=chrome-mobile&ie=UTF-8>
* <https://www.google.com/search?q=ukhas+super+pressure.&rlz=1CDGOYI_enUS805US805&oq=ukhas+super+pressure.&aqs=chrome..69i57.7282j0j4&hl=en-US&sourceid=chrome-mobile&ie=UTF-8>
## General talent and links of interest
* <http://tt7hab.blogspot.com/?m=1>
* <https://stanfordssi.org/teams/balloons>
## FAA Regulations
* <https://www.law.cornell.edu/cfr/text/14/part-101>
## Satcom
* <http://www.rock7mobile.com/>
## Ads-b
* <https://www.aopa.org/news-and-media/all-news/2017/january/19/ads-b-requirement-clarified-for-nonelectrical-aircraft>
* <https://commons.erau.edu/cgi/viewcontent.cgi?article=3674&context=space-congress-proceedings>
* <https://uavionix.com/uas/>
## Avionics / Ground station
* <http://wiki.glidernet.org/esp32-ogn-tracker>
* <https://www.google.com/search?q=mavlink+lora&rlz=1CDGOYI_enUS805US805&oq=mavlink+lora&aqs=chrome..69i57j0.4939j1j4&hl=en-US&sourceid=chrome-mobile&ie=UTF-8>
* <https://www.google.com/search?q=ardupilot+lora&rlz=1CDGOYI_enUS805US805&oq=ardupilot+lora&aqs=chrome..69i57.4479j0j9&hl=en-US&sourceid=chrome-mobile&ie=UTF-8>
* <https://www.google.com/search?rlz=1CDGOYI_enUS805US805&hl=en-US&biw=375&bih=638&ei=K2TzW4_NMevMjgTKjL6IBA&ins=false&q=mavlink+lora+high+altitude&oq=mavlink+lora+high+altitude&gs_l=mobile-gws-wiz-serp.3..33i299l2.13851.18077..18247...0.0..0.297.2190.0j13j1......0....1.........0i22i30j33i160.BK3CXBmeiAo>
* <https://github.com/Octanis1/Octanis1-Field-Station>
* <https://wiki.octanis.org/orb/fieldbasestation>
## Questions asked
* On Nov 12, 2018, at 16:56, Mark S Harris <marksharristx@gmail.com> wrote:
> The balloon is likely to be more stable than the parafoil. So part of my concern was maintainomg that kind of pointing accuracy on the parafoil. In addition I didn't think the parafoil was going to be air bourne that long.
>
> Any idea on time from being dropped to landing? And of that, how much time is it in freefall before it needs to be up and running and extending the parafoil and then time to when control is needed?
>

11
src/CTO/RPi Information Normal file
View File

@@ -0,0 +1,11 @@
# RPi details
The Raspberry Pi 2 initially featured a 900 MHz 32-bit quad-core ARM Cortex-A7 processor with 1 GB RAM. Later versions featured a 1.2 GHz 64-bit quad-core ARM Cortex-A53 processor.
-----
The Raspberry Pi 3 Model B was released with a 1.2 GHz 64-bit quad core ARM Cortex-A53 processor. The Raspberry Pi 3 Model B+ was launched with a faster 1.4 GHz processor.
-----
The Raspberry Pi 4 Model B was released with a 1.5 GHz 64-bit quad core ARM Cortex-A72 processor.

28
src/CTO/cuda.md Normal file
View File

@@ -0,0 +1,28 @@
# Cuda notes for tsys
## Introduction
This is the first cut of CUDA notes for tsys. Eary research, link dump etc.
## OKR
Objectives/key results for CUDA
## Areas to explore
* CUDA clustering
* mixed gpu gens/archs
## Links
* <https://www.google.com/search?client=firefox-b-e&q=ubuntu+20.04+cuda+cross+compile&oq=ubuntu+20.04+cuda+cross+compile&aqs=heirloom-srp>..
* <https://www.google.com/search?q=cuda+jenkins&oq=cuda+jenkins&aqs=chrome..69i57.2296j0j7&sourceid=chrome&ie=UTF-8>
* <https://www.google.com/search?client=firefox-b-e&q=cuda+build+server>
* <https://www.google.com/search?client=firefox-b-e&ei=cFxIYKzcDJaStAaMsKrICA&q=cuda+ci+server&oq=cuda+ci+server&gs_lcp=Cgdnd3Mtd2l6EAM6BwgAEEcQsANQ3idYmShg3SloAnACeACAAYYDiAH6BJIBBzAuMi4wLjGYAQCgAQGqAQdnd3Mtd2l6yAEIuAECwAEB&sclient=gws-wiz&ved=0ahUKEwis1PyjgqXvAhUWCc0KHQyYCokQ4dUDCA4&uact=5>
* <https://www.vitaarca.net/post/tech/install-cuda-and-cudnn-to-ubuntu-server/>
* <https://stackoverflow.com/questions/63309619/is-it-possible-to-build-an-nvidia-cuda-based-image-on-a-server-without-a-gpu>
* <https://jupyterhub.readthedocs.io/en/latest/>
* <https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html>
* <https://crosstool-ng.github.io/docs/>

38
src/CTO/suboTodo Normal file
View File

@@ -0,0 +1,38 @@
## Device fleet management
### Backend:
- https://resin.io/how-it-works/
- https://www.digitalocean.com/community/tutorials/how-to-set-up-a-private-docker-registry-on-ubuntu-14-04
- https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-getting-startedr
### Client side
- http://www.berryterminal.com/doku.php/berryboot
- http://www.berryterminal.com/doku.php/berryboot/adding_custom_distributions
- http://blog.hypriot.com/downloads/
- http://blog.hypriot.com/
- http://blog.hypriot.com/post/heavily-armed-after-major-upgrade-raspberry-pi-with-docker-1-dot-5-0/
### Telemetry
- https://richardstechnotes.wordpress.com/2015/12/26/iot-streaming-with-mqtt-and-apache-nifi/
- https://github.com/richards-tech/RTMQTT
- https://github.com/richards-tech/RTNiFiStreamProcessors
- https://github.com/richards-tech/RTIMULib2
- http://cpham.perso.univ-pau.fr/LORA/RPIgateway.html
- http://www.dragino.com/products/module/item/106-lora-gps-hat.html
- http://wiki.dragino.com/index.php?title=Lora/GPS_HAT#Example1_--_Use_with_LMIC_library_for_LoraWAN_compatible
- http://www.eleduino.com/Dragino-Lora-GPS_HAT-for-Raspberry-Pi-p10580.html
- http://www.aliexpress.com/store/product/Long-distance-wireless-433-868-915Mhz-Lora-and-GPS-Expansion-Board-for-Raspberry-Pi/1390863_32672385182.html
### Cross compile for pi and make custom images.
- http://rpi-cloud.com/guide-install-jenkins-on-rpi/
- http://software-novotny.de/raspberry-pi-remote-compilation-with-jenkins
- http://watchmysys.com/blog/tag/cross-compile/
- https://github.com/andrius/build-raspbian-image
- https://github.com/debian-pi/raspbian-ua-netinst
http://csis.org/files/attachments/151216_Unmanned_Systems.pdf

136
src/CTO/team-hweng/SupplyChain/HwEngSupplyChain.md Normal file
View File

@@ -0,0 +1,136 @@
---
title: "TSYS Group - Engineering Documentation - Team Hardware- Supply Chain"
---
# Team HwEng - Supply Chain
## Introduction
This article covers the high level overview of the hardware supply chain for all aspects of
the orbiter:
* orbiter envelope
* orbiter parafoil
* orbiter part 101 requirements
* orbiter cutdown
* ads
* orbiter avionics
* arduino
* pi
* ground station hardware for receiving avionics data
## Pi Systems and USB accessories
* raspberry pi
* subopi1
* MorsePOD M6
* subopi2
* Lora Concentrator Pi Hat (Rak 833, 915mhz, SPI, FCC: 2AF6B-RAK833)
* Arduino Uno connected to motor shield connected to
* Servo
* subopi3
* USB Lora Concentrator
* subopi4
* Dragino Lora/GPS hat
* subopi5
* SenseHAT
* Seeduino LorawanGPS connected to
* IMU
* Motor Controller
* subopi6
* SenseHAT
* Seeduino LorawanGPS connected to
* IMU
* Motor Controller
## Orbiter Envelope
Much to write here, very soon.
## Orbiter parafoil
Much to write here, very soon.
## Orbiter Part 101 requirements
### Reflector
Much to write here, very soon.
### Redundancy
Much to write here, very soon.
### Orbiter Cutdowon
Much to write here, very soon.
## Orbiter Avionics - Seeduino
This is the core of the "smarts" (electronic) system for the orbiter. It's where all domain awarness and decision making happens (along with communication), and is subject to full regulatory review/compliance requirements.
It must do very few things, and it must do them perfectly.
It will be running FreeRTOS, with a handful of custom routines.
* The POC utilizes Seedunio LoraWANGPS boards:
* <https://www.seeedstudio.com/Seeeduino-LoRaWAN-W-GPS-p-2781.html>
* With the following groove boards connected to the seeduino:
* IMU: <https://www.seeedstudio.com/Grove-IMU-10DOF-p-2386.html>
* Motor driver board: <https://www.seeedstudio.com/Grove-I2C-Motor-Driver-L298P-p-4534.html> (or very similar , need to confirm)
* Motors (need to document)
### Power Management
* Core power control:
This is where the batteries, cells, load all comes together:
* <http://www.switchdoc.com/sunairplus-solar-power-controllerdata-collector/>
### Hardware Watchdog
This is a critical fail safe component, and will reboot the seeduino or pi automatically if countdown timer expires:
* <https://shop.switchdoc.com/collections/break-out-boards/products/switchdoc-labs-dual-watchdog-timer-board-for-arduino-raspberry-pi>
## Orbiter Avionics - Raspberry pi
The pi is essentially a large disk (for geospatial db, holding avionics firmware, holding log data etc) and beefy CPU (for geospatial lookups, processing ads-b data, perhaps some data crunching for local optimizations based on weather) attached to the avionics. The pi is important, but not completely critical. It can crash (and if not fixed by watchdog) can remain offline and the orbiter can come in for service safely. We will utilize best practices with the pi, to ensure it's as reliable/avaiable as possible.
In poc the pi will be attached via USB (and also serving as a host for the arduino for firware updates of the avionics ), in prototype/prod it will be on an integrated board as a Pi CM.
* Payload power control:
Control of the power payload, on a geospatial basis, in a black box/non customer changeable is also super critical, and will likely receive the second most regulatory scruity.
This is used for power cycling the payload for regulatory compliance (geofence):
* <https://shop.switchdoc.com/collections/break-out-boards/products/usb-powercontrol-board-v2-w-grove-control-usb-to-usb-solid-state-relay-for-raspberry-pi-and-arduinos-v2>
* SenseHat
We have a SenseHat on the raspberry pi, to provide additional sensor data, as a second source of data for comparsion purposes/redundancy.
## Ground Station
From a hardware perspective, not too much involved here. The lora concentrators we have
for modulating/demodulating lora packets are:
(attached via USB)
* <https://github.com/RAKWireless>
* <https://github.com/RAKWireless/RAK831-LoRaGateway-RPi>
* <https://store.rakwireless.com/products/rak831-gateway-module?variant=22375114801252>
and
(pi hat)

108
src/CTO/team-hweng/Tooling/HwEngTooling.md Normal file
View File

@@ -0,0 +1,108 @@
---
title: "TSYS Group - Engineering Documentation - Team Hardware- Tooling"
---
# Team HwEng - Tooling
## Introduction
This article covers the support stack of software and hardware used by the hardware engineering
team to develop the orbiter.
Topics covered by this documentation:
* Computer Systems
* Dev/qa/prod systems
* (Custom) Hardware machines/tools for prototypes
* Envelope Sealer
* Inflator
* Pressure chamber
* Reflow Oven
* RF Testing chamber
* Environmental Testing - Temperature
* Environmental Testing - UV
* Software
See the following links for the software setup guides
- <https://git.turnsys.com/TSGTechops/docs-techops/src/branch/master/TSYS-DevEnv-VsCode.md>
- <https://git.turnsys.com/mrcharles/dotfiles/src/branch/master/README.md>
## Computer Systems
* Raspberry Pi
* subobench (all lab equipment with a digital interface is attached to this). Documented on discourse.
* x86 servers
* subodev We develop workloads here. Once a day update or so. (After any needed iterations on our dev workstations)
* suboqa We run qa/unit/integration/burn in etc tests here on all workloads. Expect once a week updates or so.
* suboprod We run production workloads here. All things on here should be expected to come under regulatory review. May be considered a system of record, need to ponder. This is CUDA enabled (quadro). Expected to be under cluster control (slurm).
* Tegra cluster
* suboprod01-05
## (custom) tooling for prototypes
### Envelope Heat Sealer
* Overview
This is used for assembling the envelopes. It's a customized heat sealer, controlled by an Arduino for precision temperature control.
* Bill of Materials
### Inflator
* Overview
This is used for inflating the envelopes once they've been assembled (in particular for leak detection).
It's a customized pump , controlled by an Arduino for precision pressure control.
* Bill of Materials
### Pressure chamber
* Overview
* Bill of Materials
### Reflow Oven
* Overview
This is used
* Bill of Materials
### Cameo Silhouette
* Overview
This is used to (primarily) make solder stencils for PCB re-work we will be doing on prototypes.
### RF Testing Chamber
We will do as much EMC testing in house as we can. This will save us 10s of thousands of dollars
and will increase our first pass chances at the FCC certified lab immensely. We can also rent out the chamber when we aren't using it.
* Major components
* Considerations/concerns
* Budget/BoM
### Environmental Testing
We will do as much environmental testing in house as we can. Need to research if any external testing is required by regulation, but currently (03/03/2021) I'm un-aware of any that is required.
Of course we will test extensively , for robustness etc.
* Major components
* Considerations/concerns
* Budget/BoM
#### UV
#### Extreme cold

244
src/CTO/team-sweng/SupplyChain/SwEngSupplyChain.md Normal file
View File

@@ -0,0 +1,244 @@
---
title: "TSYS Group - Engineering Documentation - Team Software - Supply Chain"
---
# Team SwEng - Supply Chain
## Version
* 1.0 published 03/11/2021 at 08:30 CST
## Introduction
This article covers the high level overview of the software supply chain for the orbiter, ground station, operations center.
It touches very briefly on the hardware that will be used in the proof of concept. We have a separate article, that goes into far more detail about the hardware.
This article also doesn't touch on the software tooling (compilers and such), which is extensive and is documented in another article.
## Avionics - Seeduino
This is the core of the software system for the orbiter. It's where the magic happens, and is subject to full regulatory review/compliance requirements. It must do very few things, and it must do them perfectly.
This is all going to be custom code.
### Main board
* The proof of concept utilizes Seeduino LoraWANGPS boards:
Overview: <https://www.seeedstudio.com/Seeeduino-LoRaWAN-W-GPS-p-2781.html>
Technical Documentation: <https://wiki.seeedstudio.com/Seeeduino_LoRAWAN/> (unfortunately no ability to deep link on that page, so read it over for example code of Lora send/receive, battery checking etc)
* The boards will be running all code via FreeRTOS:
* <https://www.freertos.org/FreeRTOS-quick-start-guide.html>
* <https://wiki.seeedstudio.com/Software-FreeRTOS/>
* <https://github.com/Seeed-Studio/Seeed_Arduino_FreeRTOS>
* <https://github.com/Seeed-Studio/Seeed_Arduino_ooFreeRTOS>
FreeRTOS will need to interface with the following groove boards connected to the Seeduino via i2c:
(see <https://wiki.seeedstudio.com/Arduino_Software_I2C_user_guide/> for notes on multiple i2c)
### IMU
* This is where all the sensor data will come from.
* IMU:
<https://www.seeedstudio.com/Grove-IMU-10DOF-p-2386.html>
<https://wiki.seeedstudio.com/Grove-IMU_10DOF/>
<https://github.com/Seeed-Studio/Seeed_Arduino_IMU10DOF>
* Functions
* ReadPitch
* ReadYaw
* ReadRoll
* ReadTime
* ReadTemp
* ...(etc) (whatever the board can provide) (maybe a single function that takes an argument, whatever)
### Parafoil Control
* Control of the parafoil is critical, and will likely receive the most regulatory scrutiny.
* Motor driver board:
<https://wiki.seeedstudio.com/Grove-I2C_Motor_Driver_V1.3/>
<https://github.com/Seeed-Studio/Grove_I2C_Motor_Driver_v1_3/>
* Functions
* OrbiterOperateParafoil (left,right,up,down) [to operate the parafoil motors]
* OrbiterCutDown
* EnvelopePop
* DeployParafoil
* OrbiterSelfDestruct
### Power Management
Where the batteries, cells, load all comes together. The below board will be interfaced to (for data reading purposes) from the Seeduino via (I believe GPIO, but maybe i2c (check the docs)):
<http://www.switchdoc.com/sunairplus-solar-power-controllerdata-collector/>
* Functions
* ReadVoltage
* ReadCurrent
* ReadAmps
* ReadChargeLevel
* ... (etc)
### Telemetry
This key data:
* Charge levels
* Full IMU data
* Full sensor data (light,temp,etc)
needs to be broadcast to:
* Ground stations (via lora)
* other aircraft (via ads-b)
* Functions:
* (future, we have no ads-b currently) ADS-B(send) [for sending data over ads-b]
* (future, we have no ads-b currently) ADS-B(receive) [for receiving (listening) data over ads-b] (all smarts for processing would be on pi)
* lora(send) [to dump out telemetry to ground stations]
* lora(receive) [to receive operator instructions]
* IMU Sensor Read (logs to memory buffer in pi, so tile38 can read)
* IMU Sensor Send (broadcast on air)
* Data Logging
* GPS Read
* GPS Send
* Charge Status
* Voltage of Battery
Technical Documentation for the above, along with example code : <https://wiki.seeedstudio.com/Seeeduino_LoRAWAN/> (unfortunately no ability to deep link on that page, so read it over for example code of Lora send/receive, battery checking etc)
### Overhead / Housekeeping
Various things will be needed for regular management/housekeeping duties.
* Functions:
* TickleTheTail [keep the watchdog from activating]
<https://shop.switchdoc.com/collections/break-out-boards/products/switchdoc-labs-dual-watchdog-timer-board-for-arduino-raspberry-pi>>
is the hardware watchdog timer that we have in the shop.
This will be used to supervise/recover both the arduino and the pi.
## Avionics - Raspberry pi
The pi is essentially a large disk (for geo spatial db, holding avionics firmware, holding log data etc) and beefy CPU (for geo spatial lookups, processing ads-b data, perhaps some data crunching for local optimizations based on weather) attached to the avionics. The pi is important, but not completely critical. It can crash (and if not fixed by watchdog) can remain offline and the orbiter can come in for service safely. We will utilize best practices with the pi, to ensure it's as reliable/available as possible.
In poc the pi will be attached via USB (and also serving as a host for the arduino for firmware updates of the avionics ), in prototype/prod it will be on an integrated board as a Pi CM.
### Payload Power Management
Control of the power payload, on a geo fence basis, in a black box/non customer changeable is also super critical, and will likely receive the second most regulatory scrutiny.
In the prototype, the geo fence will utilize this board to cut/restore power:
<https://shop.switchdoc.com/collections/break-out-boards/products/usb-powercontrol-board-v2-w-grove-control-usb-to-usb-solid-state-relay-for-raspberry-pi-and-arduinos-v2>
* Functions
* Payload Power On
* Payload Power Off
* Payload Location Lookup
### geo gencing
<https://tile38.com/>
This will be utilized for geo-fencing. The pi will periodic query
GPS (or just read off the serial feed from the arduino) and cut off power to the payload (and restore it) at appropriate locations.
### operating system
Most likely will utilize a combination of
* balena os https://www.balena.io/os/
* openmtc https://www.openmtc.org/
### avionics updating
Updating the seeduino firmware image in flight, Will utilize the
* arduino-cli
system.
## Ground Station Avionics
This will be a relatively simple system, designed todo two functions:
* Receive lora broadcasts
* Convert the lora data to IP packets and push the packets to a bus for listeners to consume.
The ground station avionics software will do nothing else.
For receiving broadcasts:
* <https://github.com/RAKWireless>
* <https://github.com/RAKWireless/RAK831-LoRaGateway-RPi>
* For converting lora packets to IP and relaying data to an endpoint: <https://www.chirpstack.io/gateway-bridge/gateway/raspberrypi/>
* General lorawan software
<https://github.com/Lora-net>
* relaying to timeseries database
<https://github.com/mhe/mqtt2influxdb>
## Operations Center / Device fleet management
We must implement one bus listener: the Ops Center. Other parties may implement additional listeners as needed.
Primary software packages involved:
* <https://nasa.github.io/openmct/>
* <https://www.chirpstack.io/>
* Balena
* <https://www.balena.io/os/?>
* <https://www.balena.io/engine/?>
* <https://www.balena.io/open/?>
* <https://github.com/balena-io/open-balena?d_id=7632b330-6018-41b8-82ca-e5fab4fabf15R>
### Backend
### Client side
* <http://www.berryterminal.com/doku.php/berryboot>
* <http://www.berryterminal.com/doku.php/berryboot/adding_custom_distributions>
### Telemetry
* <https://richardstechnotes.wordpress.com/2015/12/26/iot-streaming-with-mqtt-and-apache-nifi/>
* <https://github.com/richards-tech/RTMQTT>
* <https://github.com/richards-tech/RTNiFiStreamProcessors>
* <https://github.com/richards-tech/RTIMULib2>
* <http://cpham.perso.univ-pau.fr/LORA/RPIgateway.html>
* <http://www.dragino.com/products/module/item/106-lora-gps-hat.html>
* <http://wiki.dragino.com/index.php?title=Lora/GPS_HAT#Example1_--_Use_with_LMIC_library_for_LoraWAN_compatible>
* <http://www.eleduino.com/Dragino-Lora-GPS_HAT-for-Raspberry-Pi-p10580.html>
* <http://www.aliexpress.com/store/product/Long-distance-wireless-433-868-915Mhz-Lora-and-GPS-Expansion-Board-for-Raspberry-Pi/1390863_32672385182.html>
* <http://csis.org/files/attachments/151216_Unmanned_Systems.pdf>
## Ground Station Payload
This will be written up later, and is for a dedicated payload team to worry about.
For knowledge capture purposes, some things to consider:
* <https://github.com/jhshi/openofdm>
* <https://openofdm.readthedocs.io/en/latest/overview.html>
* <https://news.ycombinator.com/item?id=25814237>
* <https://www.nuand.com/bladeRF-wiphy/>
* <https://news.ycombinator.com/item?id=24273919>
* <https://github.com/open-sdr/openwifi>

226
src/CTO/team-sweng/Tooling/SwEngTooling.md Normal file
View File

@@ -0,0 +1,226 @@
---
title: "TSYS Group - Engineering Documentation - Team Software - Tooling"
---
# Team SwEng - Tooling
## Introduction
This article covers the tools and support stack/systems used by the software engineering team at Suborbital Systems. It should be read by everyone in the engineering organization.
## Sw Engineering Systems
* Build/dev/test systems
* buildbox (All compiles happen here (either directly or via jenkins invoking)
* subodev / suboqa (All dev/testing is done on these systems, in particular for hardware engineering test suite iteration etc)
* Production systems
* suboprod (All production workloads, validations, simulations run here, cuda enabled for speed. May use docker in future to allow easy sharing of cuda card and versioning workloads)
* suboprod01-05 (cuda tk1 cluster)
* opc01/02 (op center systems)
## General Information
* All systems have NTP sync time, and working DNS
* All systems have an MOTD covering the basics and pointers to detailed documentation
* All systems have /subo mounted via NFS
### /subo directory
localuser@buildbox:~$ ls /subo/
SupplyChain Tooling
localuser@buildbox:~$
* **SupplyChain** is for upstream software that is used in deliverables produced by engineering. It would also contain any libraries/custom software etc that engineering produces
* **Tooling** is for off the shelf , upstream, vendor software that is used to support engineering operations. Things like (cross) compilers, custom builds of software etc go in it.
Each directory has the same top-level layout:
```bash
SupplyChain:
bin lib scripts src
Tooling:
bin lib scripts src
```
* bin is for installed packages (either stand alone (go/java) executables , or compiled software distributions) (with sub directories off of bin for each package, even if it's a single executable (we like clean systems and toolboxes))
```bash
root@buildbox:/subo/Tooling/bin# ls team-sweng/
arduino-cli
root@buildbox:/subo/Tooling/bin# ls team-sweng/arduino-cli/
arduino-cli
root@buildbox:/subo/Tooling/bin#
```
This is then referenced in /etc/profile as part of the path:
```bash
export PATH="/subo/Tooling/bin/team-mecheng/openvsp/OpenVSP-3.23.0-Linux:\
/subo/Tooling/lib/miniconda/bin:\
/subo/Tooling/bin/team-sweng/arduino-cli:\
$PATH"
localuser@buildbox:~$ echo $PATH
/subo/Tooling/bin/team-mecheng/openvsp/OpenVSP-3.23.0-Linux:/subo/Tooling/lib/miniconda/bin:/subo/Tooling/bin/team-mecheng/openvsp/OpenVSP-3.23.0-Linux:/subo/Tooling/lib/miniconda/bin:/subo/Tooling/bin/team-sweng/arduino-cli:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
localuser@buildbox:~$
```
We will probably create a /subo/bin directory and symlink things to it and add that to the path (if/when the $PATH environment variable becomes too long)
The path in /etc/profile must be updated on subodev/qa/prod when new software is built on buildbox (and installed to /subo/..../bin)
* lib is for any non apt-get installed libraries needed for anything we are building from source
* src is for the (typically) git clone/checkout of upstream software, with a sub directory for each package, just like bin.
* scripts is for scripts (see immediately below for two key scripts)
### Dependency tracking
```bash
root@buildbox:/subo/Tooling/scripts# ls
install-build-deps.sh install-runtime-deps.sh
root@buildbox:/subo/Tooling/scripts#
```
* Tracking Build Dependencies
If you apt-get a package/packages to make cmake/configure work, capture it in
**install-build-deps.sh**
* Tracking Runtime Dependencies
If you apt-get a package/packages to make cmake/configure work, capture it in
**install-runtime-deps.sh**
## Cross Compilers
### Cross compile for pi and make custom images
* <http://rpi-cloud.com/guide-install-jenkins-on-rpi/>
* <http://software-novotny.de/raspberry-pi-remote-compilation-with-jenkins>
* <http://watchmysys.com/blog/tag/cross-compile/>
* <https://github.com/andrius/build-raspbian-image>
* <https://github.com/debian-pi/raspbian-ua-netinst>
* atmel (arduino mega/uno)
* Documentation: <https://medium.com/swlh/how-to-create-an-automated-build-pipeline-for-your-arduino-project-1df9826f2a5e>
* Location on buildbox:
```bash
/subo/Tooling/src/team-sweng/cross-compile/rpi
```
* pi
* Documentation: <https://www.raspberrypi.org/documentation/linux/kernel/building.md> and
<https://blog.kitware.com/cross-compiling-for-raspberry-pi/>
* Location on buildbox:
```bash
/subo/Tooling/src/team-sweng/cross-compile/rpi
```
which contains the current checkout (as of 03/02/2021)
* cortex (m0)
* Documentation: <https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm>
* Location on buildbox:
```bash
/subo/Tooling/src/team-sweng/cross-compile/cortexm0
root@buildbox:/subo/Tooling/src/team-sweng/cross-compile/cortexm0 ls
binutils-gdb gcc newlib-cygwin
root@buildbox:/subo/Tooling/src/team-sweng/cross-compile/cortexm0
```
* crosstool-ng
* Documentation: <http://crosstool-ng.github.io/docs/install/>
* Location on buildobx:
```bash
/subo/Tooling/src/team-sweng/cross-compile/crosstool-ng
```
which may well prove easier/better than the raw cloned sources enumerated in the last bullet point.
* nvidia
We will be making extensive use of Nvidia systems at subo, especially in R&d (for engineering/validation etc)
* Documentation: * <https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/> and * <https://elinux.org/Jetson/Installing_CUDA>
Also see below under Software Development Kits , the CUDA bullet.
## Regular Compilers
buildbox is Ubuntu 20.04 and has bison/flex/autoconf/gcc/g++/build-essential (etc etc) via apt-get install as of 03/02/2021. run apt-get update/upgrade at any time (since anything regulatory scope, we build/install/version lock in /subo/....)
## Meta tooling
* distcc ?
* ccache ?
* ninja make?
## Software Development Kits
* CUDA / JetPack
* <https://developer.nvidia.com/cuda-downloads>
* <https://developer.nvidia.com/embedded/jetpack>
So this will be a bit tricky. We have three CUDA targets:
1 suboprod vm (hosted on pfv-vmsrv-02)
```bash
root@pfv-vmsrv-02:~# lspci |grep -i nv
01:00.0 VGA compatible controller: NVIDIA Corporation GF104GLM [Quadro 3000M] (rev a1)
```
2 jetson nano (<https://developer.nvidia.com/embedded/jetson-nano-developer-kit>) (this might? use cuda)
3 suboprod01-05 (tk1) (kepler)
* <https://developer.nvidia.com/blog/jetson-tk1-mobile-embedded-supercomputer-cuda-everywhere/>
(this uses cuda actual)
* <https://developer.nvidia.com/embedded-computing>
* <https://developer.nvidia.com/embedded/jetson-developer-kits>
* <http://mercury.pr.erau.edu/~siewerts/cec450/documents/Jetson/Tegra_Linux_Driver_Package_Developers_Guide.pdf>
Charles may tackle this, either way it's a (for now) low priority as far as tooling goes for
software engineering tooling. On the other hand, hardware/mechanical engineering will have much greater need for this stack for simulations/validation etc (for example <https://developer.nvidia.com/blog/drop-in-acceleration-gnu-octave/>).
## Editor
We use VSCode as our standard editor with the following extensions:
* for bash <https://marketplace.visualstudio.com/items?itemName=lizebang.bash-extension-pack>
* for arduino <https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.vscode-arduino>
* for cortex <https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug>
* vim
* arm
* etc
Essentially each developer will setup whatever environment they need to be most productive.
It is a highly personal, subjective, task specific etc. We offer the above
as general guidance that @ReachableCEO has found useful as he works the entire stack in VsCode.
We strongly recommend using VsCode, any other environments will be fully unsupported by Suborbital Systems.

109
src/CTO/team-sweng/Tooling/Tooling Task List.md Normal file
View File

@@ -0,0 +1,109 @@
# Tooling Task List
## Add architecture-specific directories to file tree
### Various cross-compiler parts
-----
From <https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm>, you can find the following:
### GNU C/C++ Compiler
You can find the sources to Arm Embedded GCC at [git://gcc.gnu.org/git/gcc.git](git://gcc.gnu.org/git/gcc.git). All contributions are made to trunk. Patches are cherry-picked as needed to the Arm embedded branches.
### Binutils
You can find the sources to Arm Embedded Binutils at [git://sourceware.org/git/binutils-gdb.git](git://sourceware.org/git/binutils-gdb.git). All embedded branches are under [users/ARM/embedded-binutils-[version]-branch](users/ARM/embedded-binutils-[version]-branch). Contribution is similar to GCC.
### GDB
You can find the sources to Arm Embedded Binutils at [users/ARM/embedded-binutils-[version]-branch](git://sourceware.org/git/binutils-gdb.git). All embedded branches are at [users/ARM/embedded-gdb-[version]-branch](users/ARM/embedded-gdb-[version]-branch). You can contribute in the same way that you contribute to GCC.
### Newlib
You can find the sources at [users/ARM/embedded-gdb-[version]-branch](users/ARM/embedded-gdb-[version]-branch). We contribute to master, and the toolchain is based on master branch.
-----
### crosstool-NG [http://crosstool-ng.org/#download_and_usage](http://crosstool-ng.org/#download_and_usage)
x86 install (buildbox)
### Arduino-cli
x86 - RPi cluster install (into /subo/arm directory), deploying Uno and Mega Arduinos)
### Cross-compilers
x86-to-ARM cross-compiler (gcc, binutils, gdb), deploying RPi
x86-to-M0 cross-compiler (gcc, binutils, gdb), deploying M0
x86-to-AVR cross-compiler (gcc, etc.?), deploying Uno, Mega
### CUDA / JetPack (low priority)
suboprod
jetson nano
suboprod[n] - 01 through 05
### Configure Jenkins
-----
## Avionics - Seeeduino
### Install FreeRTOS
### IMU - Interface with
Multiple i2c
IMU
Functions - ReadPitch, ReadYaw, ReadRoll, ReadTime, ReadTemp, etc.
### Parafoil Control
Motor driver board drivers
Functions - OrbiterOperateParafoil (motor left, right, up, down), OrbiterCutDown, EnvelopePop, DeployParafoil, OrbiterSelfDestruct
### Power Management
Functions - ReadVoltage, ReadCurrent, ReadAmps, ReadChargeLevel, etc.
### Telemetry
Key data - Charge levels, Full IMU data, Full sensor data (light, temp, etc.)
Broadcast to ground stations (via lora), other aircraft (via ads-b)
Functions
> Future, no ads-b yet, ADS-B(send), ADS-B(receive)
>
> Lora(send), lora(receive), IMU Sensor Read, IMU
Sensor Send, Data Logging, GPS Read, GPS Send, Charge Status, Battery Voltage
### Overhead / Housekeeping
Functions - TickleTheTail
## Avionics - Raspberry Pi
Payload Power Management
### Functions - Payload Power On, Payload PowerOff, Payload Location Lookup
### Geo Fencing obtain tile38 data
### Operating System - Balena OS, Openmtc
### Avionics Updating will use Arduino-cli
## Ground Station Avionics
### Receive lora broadcasts
### Convert lora data to IP packets, push packets to a bus
### Set up chirpserver
### Set up openmtc