kicad / kicad-templates Goto Github PK

The following files in this repo:

• kicad.pro
• gost_landscape.kicad_wks
• gost_portrait.kicad_wks
• pagelayout_default.kicad_wks
• pagelayout_logo.kicad_wks

Are also in main KiCad repo. Is there are supposed to be duplicate ?

Thanks,

From #5:

• None of the templates use hierarchical sheets.
• The following don't have the headers in a box on the schematic: BeagleBone-Black-Cape, minnowboard-ls-lure, raspberrypi_hat, raspberrypi-gpio, raspberrypi-gpio-40pin, stm32f100-discovery-shield, ti-stellaris-boosterpack40_min.
• The following board doesn't open in v4: minnowboard-ls-lure.
• raspberrypi_hat has a symbol called 40HAT which is rather non-descriptive. What if another version of the Rasp Pi had a different pinout? Or another template needed a 40-pin header? Contrast this with raspberrypi-gpio-40pin (and the templates above) which uses a generic header.
• Similarly, ti-stellaris-boosterpack40_min also has specific named headers instead of generic ones.
• raspberrypi_hat board could also include the locations of the camera and display cutout on some info layer as a guide. It also has horrible settings for clearance and min width for the zones.
• raspberrypi-gpio board has a text note that P1 should be on the bottom of the board, so why isn't it placed there? For whatever reason it's on the top. raspberrypi-gpio-40pin does this properly.
• Only a few of the board templates indicate which side of the board should be up (or against the mother board?) when the shield is used. Or which side the headers go on. Is this kind of information important enough to be documented on each board?
• stm32f100-discovery-shield has a zone poured. Perhaps it's better to leave that all up to the user.

There is no official guide on how to create a KiCad template. The only documentation about it is a small description about the needed files here.

Maybe adding a section in KLC for templates? That would be very useful for people creating new templates as well as for people using them. There is no convention for the names of libs/footprint/3D arquives. Each template has a different naming schema and that makes it confusing for new template development.

How do we best convert these templates over to use the new footprints?
Do we need to manually run the remap process on these? (should they first be made to use the new library to ensure that remapping works?)

I have a macrofab kicad template design in google drive here is the link
i don't understand github this is compressed in 7zip & windows 10.
kicad 4.07

https://drive.google.com/open?id=12R0N_3MhzhpNaGwH8O7papERemE6tAa-

KiCad thinks CMakeModules is a template and tries to open icon and html from it

19:37:49: Kann Datei './kicad-templates/CMakeModules/meta/icon.png' nicht öffnen (Fehler 2: Datei oder Verzeichnis nicht gefunden)
19:37:49: Konnte das Bild aus der Datei "./Kicad/kicad-templates/CMakeModules/meta/icon.png" nicht laden.
19:37:49: Kann Datei './kicad-templates/CMakeModules/meta/info.html' nicht öffnen (Fehler 2: Datei oder Verzeichnis nicht gefunden)

Probably templates should get a .template suffix in the future to distinguish them from normal directories

Hi Templateers-

As part of the Great KiCad GitLab migration of 2019, I am testing the movement of open issues and PRs from GitHub to GitLab.

Here's what we know so far:

• Open Pull Requests will transfer to GitLab without moving the source of the PR. That means pull requests will become GitLab Merge Requests that are referenced to the user's GitHub repository
• Open Issues will transfer to GitLab issues
• Closed/Resolved PRs and Issues will also transfer

In order to facilitate the transfer, it will be helpful if you can do two things:

• Open a GitLab account (these can use your GitHub OAuth)
• Set your GitHub email to public
• Please let me know who the responsible parties are for the templates repository

The second point is critical because the migration script will only link users whose e-mail addresses match. If the script can't see your GitHub e-mail address, the issue will be tied to the KiCad-Bot that performs the migration.

It will greatly assist my testing for bugs if you could do the two steps above as soon as possible.

Thank you-
Seth

The Raspberry pi hat template specifies R23 and R24 (part of the ideal diode back circuit to prevent back powering) as 22R resistors. This much, much too low - 230mA is being pulled through the transistor, through the resistor to ground! Way over the 1/16w spec for an 0402 resistor.

If you look at the official Raspberry Pi documentation, it recommends 47K as a value for these resistors: https://github.com/raspberrypi/hats/blob/master/zvd-circuit.png

This resistor value should be changed to something more sensible - is it possible the unit (K) has been missed out of the schematic?

I can confirm this issue affects the actual hardware produced using this template - we designed a hat around it and and after a little while, burned out these resistors.