Skip to content

Selcuk

sselcuk requested to merge github/fork/serkanxselcuk/selcuk into master

Enclosure_Bopla:Bopla_Filotec_F10xx_80 added.

Datasheet: https://www.bopla.de/fileadmin/products/Alle_Filotec/97118080_F_1048-80.pdf

image

Enclosure reference lines are helpfull to design boards.
So, pcb designer can see, where board edges (Edge.Cuts),
mounting holes and connectors must be placed while designing in pcbnew.

After symbols for mechanic included (on planing), developers can see at BOM list,
what they must buy to build device.
It would be useful to calculate sum of product costs (or use KiCost).
Developers can plan not only PCB, all parts for a device using KiCad.

Guidelines for Enclosures:
1. EN 81386-2 standards designator for covering objects 'N'. So, reference names will be (e.g. N1, N2, N3)
2. If not different specified in Datasheet, footprint origin must be set to mittle point.
3. Placement type of enclosure footprint is "visual" (Footprint properties > Properties > Placement type),
   becouse enclosures will not be placed on PCB using automated pick&place machines.
4. All dimensions must be on F.Fab layer including texts, out of reference name.
5. No text is allowed in board area of enclosure.
6. if possible, place no text at possible connector side of enclosure.
7. Library names: "Enclosure_[Manufacturer]".
8. footprint names: "[Manufacturer]_[Serie]_[ProductName]".
9. If manufacturer sell enclosure as one part (e.g. Top, buttom and front covers), all must be sketched in one footprint/symbol;
   if manufacturer sell enclosure as different parts, all parts are different footprints/symbols.
   Becouse user can decide if he wants to buy all parts of enclosure.

Thanks for creating a pull request to contribute to the KiCad libraries! To speed up integration of your PR, please check the following items:

  • Provide a URL to a datasheet for the footprint(s) you are contributing
  • An example screenshot image is very helpful
  • If there are matching symbol or 3D model pull requests, provide link(s) as appropriate
  • Check the output of the Travis automated check scripts - fix any errors as required

Merge request reports