Hardware Development Guidelines

Overview

This guide refers to practices that is followed for hardware projects. It contains 3 sections:

Each of the sections refer to a different stage of hardware development.

The repository of a hardware project must include:

License file for example, CERN Open Hardware Licence Version 2 - Strongly Reciprocal
Libre Space Foundation Contribution Guide
Git ignore files for different kind of programms, like KiCad, FreeCAD and QUCS.
In case of CAD files, e.g. FreeCAD, it is recommended to use Git LFS
For project management follow, recommended Mode of Operation for Libre Space Foundation projects
An (under test) method to keep track of issues with epics and/or milestones is followed at SIDLOC project - issue and some notes

KiCad workflow for multiple boards is under test in SIDLOC project and here is the description of method
FreeCAD workflow uses Git LFS - File Locking

An inventory with electronic parts is kept in LSF lab. For that reason it is recommended to select parts from inventory that the threshold of minimum order is above 20 (more details TBA)
Parts like MCUs, PSUs etc are preferred to re-used for all the projects
Preferred vendors
For Board to wire connectors the Molex - PicoBlade and Hirose - DF11 series are preferred
A Libre Space Foundation KiCad Library exists. It is advised to use parts from it (or KiCAD libs). In case that a part does not exist a merge request in to library is more than welcome
To export a BOM, for e.g. Mouser, use either bom_csv_grouped_by_value and from generated .csv use the second table of follow a guide: The Generation of Bill of Material Files

The release scheme is under development and testing in SatNOGS COMMS project

Preferred vendors are to be followed
Tag a release on the hardware repository and write all production details like this .
Ping people with access according to Procurement policy.
Note: Stencil size (maximum) 180x220 mm (due to stencil printer)

Libre Space Foundation uses hackerspace.gr laboratory with:

TBD

TBD