MLAB wiki

User Tools

Site Tools

Trace: • rules
en:rules

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:rules [2022/03/08 21:58] – [Manual module creation] kakliken:rules [2023/02/03 00:14] (current) – [Sizes] kaklik
Line 1: Line 1:
-FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)//+FIXME **This page is not fully translated, yet. Please help complete the translation.**\\ //(remove this paragraph once the translation is finished)//
  
 ====== Rules for designing new modules ====== ====== Rules for designing new modules ======
  
-This page serves as a wiki complement to an original article [[http://www.mlab.cz/Articles/HowTo/Rules/DOC/HTML/Rules.cs.html|Proposed rules and standard procedures]]. It also serves as a site for placing additional rules of module design, which are not dealt with in the article.+This page serves as a wiki complement to an original article [[http://home.mlab.cz/Articles/HowTo/Rules/DOC/HTML/Rules.cs.html|Proposed rules and standard procedures]]. It also serves as a site for placing additional rules of module design, which are not dealt with in the article.
  
-The module design itself uses a following [[en:tools|software tools]].+The module design itself uses the following [[en:tools|software tools]].
  
 ===== Identification of modules ===== ===== Identification of modules =====
  
-Each modules has to carry a unambiguous identification mark consisting of its name, version and module revision - e.g. [[cs:jtagft2232v|JTAGFT2232V02A]].+Each module has to carry an unambiguous identification mark consisting of its name, version, and module revision - e.g. [[cs:jtagft2232v|JTAGFT2232V02A]].
  
   - JTAGFT2232 -  the name of the module, depicting the nature of the module (here probably a J-tag programmer with FTDI FT2232 chip).   - JTAGFT2232 -  the name of the module, depicting the nature of the module (here probably a J-tag programmer with FTDI FT2232 chip).
Line 15: Line 15:
   - A - the module’s revision (in this case there were not corrections of any mistakes)   - A - the module’s revision (in this case there were not corrections of any mistakes)
  
-Furthermore there are modules with green non-soldering mask and white print and modules with white mask and green print. This kind of module identification was introduced by [[http://www.ust.cz/|UST]] company, which produces modules for MLAB. The meaning of the above-mentioned colour identification is as follows:+Furthermore, there are modules with green non-soldering mask and white print and modules with white mask and green print. This kind of module identification was introduced by [[http://www.ust.cz/|UST]] company, which produces modules for MLAB. The meaning of the above-mentioned colour identification is as follows:
  
  
   * **Green mask and white print** - a prototype module, often made only in one or few pieces serving as testing samples   * **Green mask and white print** - a prototype module, often made only in one or few pieces serving as testing samples
-  * **White mask and black print** - a production version made in large quantities. Compared to the green version, it may contain tiny changes changes even if the module’s identification mark is identical.+  * **White mask and black print** - a production version made in large quantities. Compared to the green version, it may contain tiny changes even if the module’s identification mark is identical.
  
 ===== Creating a new module ===== ===== Creating a new module =====
 +
 +==== Using a GitHub template ====
 +
 +The probably simplest way how to make a new module structure is to create a new repository based on the [[https://github.com/mlab-modules/MODUL01 | GitHub MLAB module template repository]].
 +
 +The template repository should be used in [[https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template | the standard GitHub way]].
 +
 ==== Using a mlabgen script ==== ==== Using a mlabgen script ====
  
Line 42: Line 49:
 If for some reason, you are reluctant to use MLABgen for the creation of the basic directory structure, it is necessary to comply with the following rules:  If for some reason, you are reluctant to use MLABgen for the creation of the basic directory structure, it is necessary to comply with the following rules: 
  
-In the appropriate folder category, we create a folder with the name of the new module using the format ''NAMEVERREV’’ . Inside the folder, we create the following directory structure (obligatory folders/files are marked with an asterisk):+In the appropriate folder category, we create a folder with the name of the new module using the format of ''NAMEVERREV''. Inside the folder, we create the following directory structure (obligatory folders/files are marked with an asterisk): 
  
-'' 
   <NAMEVERREV>*   <NAMEVERREV>*
   ├── doc*   ├── doc*
Line 73: Line 80:
   ├── <NAMEVERREV>.json*   ├── <NAMEVERREV>.json*
   └── sw   └── sw
-      └── <NAMEVERREV>_exmalpe.py''+      └── <NAMEVERREV>_exmalpe.py
  
 The file ''<NAMEVERREV.json>'' should contain the information concerning the module. The file ''<NAMEVERREV.json>'' should contain the information concerning the module.
Line 108: Line 115:
 {{:low_power_connectors.png?direct&400|}}  {{:low_power_connectors.png?direct&400|}} 
  
-**Power supply connectors are doubled in order to allow smyčkování napájení (??).** +**Power supply connectors are doubled in order to allow power looping** 
-==== Externí napájecí zdroje ====+==== External power sources ====
  
 For power supply with higher powers, the FASTON connectors or WAGO256 terminal blocks are used. For power supply with higher powers, the FASTON connectors or WAGO256 terminal blocks are used.
Line 162: Line 169:
 ==== Sizes ==== ==== Sizes ====
  
-MLAB modules are designed in 10.16 mm raster (400 mils) and their sizes exceed 200 mils - 10 mils from the centres of the corner holes. Each module is 10 mils smaller in size compared to the exact raster due to production tolerances (otherwise it might not be possible to fit two modules next to each other on a base board). To make it possible to fit modules next to each other, it is necessary to make each size smaller by 0.254 mm (10 mils). For mounting on the [[en:albase1521|ALBASE]], we use M3 screws of 12 mm in length - that is why it is necessary to have four 3 mm diameters openings on each PCB.+MLAB modules are designed in 10.16 mm raster (400 mils) and their sizes exceed 200 mils - 10 mils from the centers of the corner holes. Each module is 10 mils smaller in size than the exact raster due to production tolerances (otherwise it might not be possible to fit two modules next to each other on a baseboard). To make it possible to fit modules next to each other, it is necessary to make each size smaller by 0.254 mm (10 mils). For mounting on the [[en:albase1521|ALBASE]], we use M3 screws of 12 mm in length - that is why it is necessary to have four 3 mm diameter openings on each PCB.
  
-An example of a module occupying 3 openings on the ALBASE:+An example of a module occupying 3 openings on the [[en:albase1521|ALBASE]]:
  
-{{ :cs:modul.png?400 |}}+{{ :mlab_module_geometry_example.png?direct&600 |}}
  
  
-   Length of the edge = 4x10.16 - 0.254 -0.254 = 40.132 mm +   * Length of the edge: 4x10.16 - 0.254 -0.254 = 40.132 mm 
-   Screws’ pitch = 3x10.16 = 30.48 mm +   * Screws’ pitch: 3x10.16 = 30.48 mm 
-   The distance of screw opening from the base’s edge = 5.08 - 0.254 = 4.826 mm +   * The distance of the screw hole center from the base’s edge: 5.08 - 0.254 = 4.826 mm 
-   Screw opening’s diameter = 3 mm+   * Screw hole diameter: 3 mm (MLAB footprint)
  
 ==== Edge screws ==== ==== Edge screws ====
en/rules.1646776720.txt.gz · Last modified: 2022/03/08 21:58 by kaklik