Go to file
debian 1b22d32501 5537T315 mcmaster wrong part 2019-12-07 20:19:32 -07:00
3dprints updates to bom 2019-12-07 20:00:04 -07:00
assemblies Update assemblies and BOM due to #66 2018-11-29 14:47:10 +02:00
docs Add wiki pages and OHAI 2019-11-26 10:16:16 -07:00
releases/3.1-pre-release Add satnogs-rotator 3.1-pre-release release files 2019-11-26 10:10:32 -07:00
rotator_parts Resolve issue #66 2018-11-29 13:50:24 +02:00
shared Change the length due to changes in motor mount 2018-08-18 11:51:03 +03:00
.gitignore Ignore spread sheet back up files 2018-08-16 12:36:52 +03:00
CONTRIBUTING.md Update files after gitlab migration 2017-09-19 12:04:21 +03:00
LICENSE Update README with license notice 2015-04-24 13:02:06 +03:00
README.md fork 2019-11-28 17:39:14 -07:00
part-number-list.ods Update assemblies and BOM due to #66 2018-11-29 14:47:10 +02:00
rotator-bom.ods 5537T315 mcmaster wrong part 2019-12-07 20:19:32 -07:00


SpaceCruft! SatNOGS Rotator

SatNOGS Rotator

Hardware for SatNOGS Rotator. This repository includes all needed source files for 3D printed (and other) parts of SatNOGS Rotator.


More information can be found in our wiki.

Repository policy - Naming Convention

According to F3 - Form, Fit and function and Part number, wiki page some rules build about the naming convention and versioning:

  • C, custom parts, placed in rotator_parts file
  • H, hardware parts, placed in shared file
  • A, assemblies, placed in assemblies file
  • All used part numbers are placed in part-number-list spreadsheet.
  • Start the number from 1000, e.g. C1000-1.
  • Dash -1 (odd), are parts from same family for example M5 screws with same DIN and different lengths.
  • Dash -2 (even), are parts from same family but all features are mirrored.
  • Small changes in the part (fit - aspect), not affect the part number but affected the variant (-n).
  • Big changes in the part or assembly (form and function aspect), affect the part number, make a new one and replace or remove the old one.
  • When a part is ready, in the commit message only this part and the message contains the revision of the part and a release note about the changes. If needed update the drawing inside the freecad. Then commit all sub-assemblies and the main assembly which affected by the part or parts.
  • In order to add a new part take a new part number according to the part number list (spreadsheet).
  • When a part or assembly isn't ready for release, in commit message add WIP, work in progress, write the changes must be done, refers to the issue.
  • When all parts and assemblies are ready and working properly, a release is done with tagging the last commit and a file with all fabrication files like *.stl, *.step, *.pdf (for drawings), .dxf (for 2D parts) are generated which each file is naming with pn_revN.
  • Master branch is most times under active development, so expect things to break.
  • Assembly is broken down to specific groups, sub-assemlies. The first priority of assembly levels is to help the designer in design process and not in the real assembly. The second priority is to make assemblies that helps in assembly process. We never work on very large assemblies, due to limitation in CAD program.
  • Try to use a coordinate system that is fit in the main assembly.
  • Drawing revision does not exist, only part or assembly revision is modified. When a small change is done in drawing for example in text the revision isn't change because the part or assembly isn't change.


The main repository lives on Gitlab and all Merge Request should happen there.


Libre Space Foundation Licensed under the CERN OHLv1.2.