diff --git a/.travis.yml b/.travis.yml
index 574a2d4e..262284cd 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -21,4 +21,4 @@ before_install:
# Build the website
script:
- ./hugo
- - htmlproofer ./public --external_only --only_4xx
\ No newline at end of file
+ - htmlproofer ./public --external_only --only_4xx --url-ignore "/www.digikey.com/"
diff --git a/config.toml b/config.toml
index 3740aa9b..7c8f49a4 100644
--- a/config.toml
+++ b/config.toml
@@ -26,10 +26,6 @@ disablePathToLower = true
[[params.social]]
title = "github"
url = "https://github.com/KiCad"
-[[params.social]]
- title = "google-plus"
- url = "https://plus.google.com/111133613917552048578"
-
[[menu.main]]
name = "Blog"
diff --git a/content/blog/kicad-hackathon-july-2016-at-cern.adoc b/content/blog/kicad-hackathon-july-2016-at-cern.adoc
index c57acc93..0f11ba43 100644
--- a/content/blog/kicad-hackathon-july-2016-at-cern.adoc
+++ b/content/blog/kicad-hackathon-july-2016-at-cern.adoc
@@ -17,17 +17,16 @@ at CERN for a KiCad hackathon the week of July 4th to July 10th organized
by CERN's Javier Serrano. There was even enough time to take a trip to
visit the KiCad project founder Jean-Pierre Charras.
-It would be a gross understatement to say that a good time was had by all.
+It would be a gross understatement to say that a good time was had by all.
Many new and existing developement topics were discussed and a lot of KiCad hacking
took place during the week. Much hacking was done to improve the
push and shove router, improve user experience, improve the
coverage and accuracy of the geometry library, create a schematic
-I/O plugin architecture, and finalize the
-http://docs.kicad-pcb.org/doxygen/v5_road_map.html[version
-5 stable release road map].
+I/O plugin architecture, and finalize the version 5 stable release
+road map.
-There was also working demo and hacking on a new feature created by the CERN developers
-Tom Wlostowski and Maciej (Orson) Suminski which was kept under wraps and an unexpected
+There was also working demo and hacking on a new feature created by the CERN developers
+Tom Wlostowski and Maciej (Orson) Suminski which was kept under wraps and an unexpected
urprise for everyone outside of CERN including the project leader. Expect a big announcement in
the not too distant future as this feature nears a level of maturity to be
committed to the
diff --git a/content/blog/project-leader-announcement.adoc b/content/blog/project-leader-announcement.adoc
index 7e80f9b4..01e56d4e 100644
--- a/content/blog/project-leader-announcement.adoc
+++ b/content/blog/project-leader-announcement.adoc
@@ -13,12 +13,12 @@ categories = [
:iconsdir: /img/icons/
For those of you who did not have the good fortune to attend
-https://kicad-kicon.com/[KiCon], (more on that in a later post) there was
+https://kicad-kicon.com/[KiCon] (more on that in a later post), there was
a major project announcement made by the project leader during the
https://www.youtube.com/watch?v=nL0yTvJKA5c&feature=youtu.be[keynote talk].
The KiCad project is excited to announce that the lead developer, Wayne
-Stambaugh has been hired by https://www.wit.com[WIT] to work full time
-on KiCad. On behalf of The KiCad development team and it's users, we
-would like to say thank you to WIT for it's commitment to the project.
+Stambaugh, has been hired by https://www.wit.com[WIT] to work full time
+on KiCad. On behalf of The KiCad development team and its users, we
+would like to say thank you to WIT for its commitment to the project.
We are looking forward to the additional development manpower this will
-provide and we hope we can help WIT achieve it's goals.
+provide and we hope we can help WIT achieve its goals.
diff --git a/content/blog/release-5.1.4.adoc b/content/blog/release-5.1.4.adoc
new file mode 100644
index 00000000..662143a6
--- /dev/null
+++ b/content/blog/release-5.1.4.adoc
@@ -0,0 +1,45 @@
++++
+title = "KiCad 5.1.4 Release"
+date = "2019-08-13"
+draft = false
+aliases = [
+ "/post/release-5.1.4/"
+]
+categories = [
+ "Release Notes"
+]
++++
+
+:icons: fonts
+:iconsdir: /img/icons/
+
+The KiCad project is proud to announce the latest series 5 stable
+release of KiCad. The 5.1.4 stable version contains critical bug
+fixes and other minor improvements since the 5.1.2 and 5.1.3 releases.
+It also includes improved footprint, symbol, and 3D model libraries,
+translations, and documentation. A list of all of the fixed bugs
+since the 5.1.2 and 5.1.3 releases can be found on the
+https://launchpad.net/kicad/+milestone/5.1.3[KiCad 5.1.3 milestone page]
+and the https://launchpad.net/kicad/5.0/5.1.4[KiCad 5.1.4 milestone page].
+This release contains several critical bug fixes so please consider
+upgrading as soon as possible.
+
+If you are wondering why there was no "official" 5.1.3 release,
+there was a serious issue after 5.1.3 was tagged and some users
+had downloaded the unreleased 5.1.3 builds from the KiCad build
+server. The only way to prevent install conflicts was to create
+a new 5.1.4 tag with the bug fix and spin new builds. The KiCad
+project would like to apologize for any inconvenience this may
+have caused.
+
+
+Version 5.1.4 is made from the
+https://code.launchpad.net/~kicad-product-committers/kicad/+git/product-git/+ref/5.1[lp:kicad/5.1]
+branch with some cherry picked changes from the development branch.
+
+Packages for Windows, MacOS, and Linux are available or will be
+in the very near future. See the
+link:/download[KiCad download page] for guidance.
+
+Thank you to all developers, packagers, librarians, document writers,
+translators, and everyone else who helped make this release possible.
diff --git a/content/contribute/developers.adoc b/content/contribute/developers.adoc
index 8fb91045..db77f035 100644
--- a/content/contribute/developers.adoc
+++ b/content/contribute/developers.adoc
@@ -30,8 +30,8 @@ are available in the
link:https://help.launchpad.net/YourAccount/NewAccount[Launchpad user tutorial].
The official road map is available online as the
-http://docs.kicad-pcb.org/doxygen/v5_road_map.html[version
-5 road map] in the doxygen docs. The CERN team also have their own
+http://docs.kicad-pcb.org/doxygen/v6_road_map.html[version
+6 road map] in the doxygen docs. The CERN team also have their own
road map available at
http://www.ohwr.org/projects/cern-kicad/wiki/WorkPackages[CERN KiCad
work packages]. You might use this to get a feeling of where KiCad is
@@ -148,10 +148,10 @@ mean helps you keep control of that. Please refrain of doing
`git commit -a` or `git add .` unless you know exactly what you changed.
It is also useful to run `git diff --cached` to see what's staged for
-commit before commiting, if you added files you didn't mean to you can
+commit before committing, if you added files you didn't mean to you can
remove them from the staging area by running `git reset bad-file.cpp`
-If you realized a mistake right after you commited, be it in a file
+If you realized a mistake right after you committed, be it in a file
change, or you forgot a file, or the description has an error or a
typo, as long as you haven't pushed your changes yet you can make your
changes and then run `git commit --amend`, this will show you the
@@ -173,7 +173,7 @@ code.
It will often happen that someone else with push access to the
official KiCad repository will push changes in between the time you
-commited your changes and you decide to push/submit yours for
+committed your changes and you decide to push/submit yours for
consideration. In that case if you try to run `git pull`, by default
git will generate a merge commit, which is undesirable fluff and tends
to pollute the commit history. In those cases you want to run
diff --git a/content/discover/in-the-media.adoc b/content/discover/in-the-media.adoc
index 82073941..70eadffd 100644
--- a/content/discover/in-the-media.adoc
+++ b/content/discover/in-the-media.adoc
@@ -9,6 +9,8 @@ title = "In the Media"
**KiCad has been featured in the following blog posts, press and media:**
+https://techexplorations.com/blog-wayne-stambaugh/[Tech Explorations Interview with KiCad Project Lead Developer] (9-MAY-2019)
+
https://hackaday.com/2019/04/30/kicad-community-shines-at-first-ever-kicon/[KiCad Community Shines at First Ever KiCon] (30-APR-2019)
https://blog.aisler.net/supporting-kicad-d94ea84eb87?fbclid=IwAR17m6vuxNntbYNC_65gknUnfm0urGvC3jN9kRATw69AUboUdH3OvoRE-8U[Aisler Supporting KiCad] (4-FEB-2019)
diff --git a/content/download/debian.adoc b/content/download/debian.adoc
index 844526a2..c1784fe1 100644
--- a/content/download/debian.adoc
+++ b/content/download/debian.adoc
@@ -6,63 +6,194 @@ weight = 10
:icons: fonts
:iconsdir: /img/icons/
-== Debian Stable (Stretch)
+== Basic Information
-{{< repology debian_stable_backports >}}
+The information further down about the available KiCad packages might not
+always be fully up to date and correct due ongoing development. For getting an
+overview about the current most recent version for the KiCad packages within
+the various Debian releases please have a look at
+https://packages.debian.org/search?lang=en&keywords=kicad[package.debian.org].
-{{< repology debian_stable >}}
+Please note that Debian stable releases don't get updates for existing
+packages except security updates. Packages within the Stable releases usually
+get newer and recent versions through backports repositories. KiCad is
+here no special case.
-The release 4.0.5 is available for Debian
-https://packages.debian.org/stretch/kicad[stable/stretch], the backported
-version 5.0.1 is available in
-https://packages.debian.org/stretch-backports/kicad[stretch-backports].
+To be able to install versions from a official Debian Backport repository you
+need to extend your `sources.list` configuration if not yet happen. If you are
+running Debian Buster please create a file
+`/etc/apt/sources.lists.d/buster-backports.list` if you don't have an similar
+entry already.
-You can install it with the following commands in a terminal, otherwise you can
-use any of the package managers you like:
+[source,bash]
+----
+# /etc/apt/sources.lists.d/buster-backports.list
+deb http://deb.debian.org/debian buster-backports main contrib non-free
+----
+
+If your system is still running Debian Stretch create a similar file (if not
+done somehow already or created by the installer similar)
+`/etc/apt/sources.lists.d/stretch-backports.list`
+like above except the content is pointing to stretch-backports.
[source,bash]
+----
+# /etc/apt/sources.lists.d/stretch-backports.list
+deb http://deb.debian.org/debian stretch-backports main contrib non-free
+----
+
+Once you've added one of these files you need to update the database of the
+package managing system so your preferred package manager is knowing about
+the new added source and the package versions from there.
+
+[source,bash]
+----
sudo apt update
+----
+
+For more information about backports you might want to visit the Debian Wiki
+site about https://wiki.debian.org/Backports[Backports] and / or also the
+https://backports.debian.org/Instructions/[Backports website].
+
+=== Other KiCad related packages and their relations
+
+For more flexibility the various KiCad packages are provided by also various
+binary packages you might want need to install beside the `kicad` main package
+that is containing the KiCad applications. For example there are existing
+dedicated packages for the footprints, symbols, templates and 3D-models and
+also KiCad documentation related packages which aren't necessarily
+automatically get installed (depends on the configuration of your system) if
+you install the `kicad` package.
+
+If you are looking for all KiCad related packages you can search for them
+simply by your preferred package manager tool, e.g. by `apt`.
+
+[source,bash]
+----
+sudo apt search kicad*
+----
+
+For a useful working with KiCad you will need to have installed the following
+packages: `kicad` and `kicad-libraries` and sometimes also the package
+`kicad-demos`.
+Typically these packages get installed automatically if you haven't changed the
+system default on installing of recommended packages. Please don't install the
+package `kicad-common` directly, it's a transitional package and will go away,
+it can get removed if you've installed this.
+
+You can get more information about the relation between the various `kicad`
+packages in Debian please have a look at a graphic on the
+https://wiki.debian.org/KiCad[Debian wiki page] for KiCad packages.
+
+'''
+
+=== KiCad packages within the Debian releases
+
+==== Debian Old-Old-Stable (Codename Jessie)
+
+WARNING: The Jessie release isn't supported any more and wont get updates, please
+upgrade your system to at least Debian Stretch!
+
+'''
+
+==== Debian Old-Stable (Codename Stretch)
+
+===== https://packages.debian.org/stretch-backports-sloppy/kicad[*Old-Stable* (Backports)]
+
+Version: 5.1.4
+
+====== Installation
+
+[source.bash]
+----
+sudo apt install -t stretch-backports kicad
+----
+
+Please ensure you have updated the local database of the package management
+system before installing!
+
+TIP: Keep in mind that this version can't provide all functions of KiCad as
+the required packages for this are too old in Stretch or not available!
+Especially the support for Python scripting is limited to Python 2! Some
+external AddOns wont work.
+
+'''
+
+===== https://packages.debian.org/stretch/kicad[*Old-Stable* (Release)]
+
+Version: {{< repology debian_oldstable >}}
+
+====== Installation
+
+[source.bash]
+----
sudo apt install kicad
+----
+
+''''
+
+==== Debian Stable (Codename Buster)
+
+===== https://packages.debian.org/buster/kicad[Stable (Backports)]
+
+Version: {{< repology debian_stable_backports >}}
+
+====== Installation
-Offline docs are available in separate packages named for example
-`kicad-doc-en`. You can search for them with _apt_ or _apt-cache_ for example.
+Please ensure you have updated the local database of the package management
+system before proceed.
[source.bash]
-apt search kicad-doc
-# or alternatively if you are on wheezy
-apt-cache search kicad-doc
+----
+sudo apt install -t buster-backports kicad
+----
-== Debian Old-Stable (Jessie)
+===== https://packages.debian.org/buster/kicad[Stable (Release)]
-{{< repology debian_oldstable_backports >}}
+Version: {{< repology debian_stable >}}
-{{< repology debian_oldstable >}} (KiCad's 2014 stable release)
+'''
-The 2014 stable release bzr4027 of KiCad is available in the official Debian
-repositories for https://packages.debian.org/jessie/kicad[oldstable/jessie].
+====== Installation
-It is not recommended for new designs. Please use the packages from the
-backport repository for actual versions. Follow the instructions on the
-https://wiki.debian.org/Backports[Debian Wiki] to add the Backport repository
-to your sources and install the KiCad packages from
-https://packages.debian.org/jessie-backports-sloppy/kicad[jessie-backports-sloppy].
+[source.bash]
+----
+sudo apt install kicad
+----
+
+'''
+
+==== Debian Testing (Bulleseye)
+
+Version: {{< repology debian_testing >}}
+
+===== Installation
-== Debian Unstable (Sid)
+[source.bash]
+----
+sudo apt install kicad
+----
+
+'''
-{{< repology debian_unstable >}}
+==== Debian Unstable (Sid)
-The current upstream release is available for Debian
-https://packages.debian.org/sid/kicad[unstable/sid].
+Version: {{< repology debian_unstable >}}
-== Debian Testing (Buster)
+===== Installation
+
+[source.bash]
+sudo apt install kicad
-{{< repology debian_testing >}}
+'''
-The current upstream release is available for Debian
-https://packages.debian.org/testing/kicad[testing/buster].
+==== Debian Experimental
+There might sometimes some pre versions of upcoming releases available in
+experimental. These are usually no nightly but a RC (Release Candidate)
+versions!
-== Build from Source
+=== Build KiCad from Source
You can find the instructions to build from source
link:http://docs.kicad-pcb.org/doxygen/md_Documentation_development_compiling.html#build_linux[here].
If you use Debian stable with actual packages from Backports or you working
@@ -74,8 +205,10 @@ Ensure you have installed some build dependencies at least before you try to
start own builds:
[source.bash]
+----
sudo apt install cmake doxygen libboost-context-dev libboost-dev \
libboost-system-dev libboost-test-dev libcairo2-dev libcurl4-openssl-dev \
libgl1-mesa-dev libglew-dev libglm-dev libngspice-dev liboce-foundation-dev \
liboce-ocaf-dev libssl-dev libwxbase3.0-dev libwxgtk3.0-dev python-dev \
python-wxgtk3.0-dev swig wx-common
+----
diff --git a/content/download/fedora.adoc b/content/download/fedora.adoc
index 42f8ef65..416c6af2 100644
--- a/content/download/fedora.adoc
+++ b/content/download/fedora.adoc
@@ -10,9 +10,9 @@ weight = 20
{{< repology fedora_rawhide >}}
-{{< repology fedora_29 >}}
+{{< repology fedora_30 >}}
-{{< repology fedora_28 >}}
+{{< repology fedora_29 >}}
In general, latest Fedora releases ship the stable versions of KiCad as they are
released.
diff --git a/content/download/osx.adoc b/content/download/osx.adoc
index 862e92a6..2743a229 100644
--- a/content/download/osx.adoc
+++ b/content/download/osx.adoc
@@ -16,16 +16,16 @@ If you run macOS 10.14, use the download with 10_14 in its name. If you run 10.1
== Stable Release
-Current Version: *5.1.2*
+Current Version: *5.1.4*
++++
macOS 10.14
Download mirrors
@@ -33,13 +33,13 @@ Current Version: *5.1.2*
++++
-macOS 10.11-10.13
+macOS 10.12-10.13
Download mirrors
diff --git a/content/download/source.adoc b/content/download/source.adoc
index ebc8d381..9f486b48 100644
--- a/content/download/source.adoc
+++ b/content/download/source.adoc
@@ -25,17 +25,17 @@ project templates.
== Stable Release
-Current Version: *5.1.0*
+Current Version: *5.1.4*
Tarballs intended to be used by packagers:
-* link:https://launchpad.net/kicad/5.0/5.1.0/+download/kicad-5.1.0.tar.xz[Source code]
-* link:https://kicad-downloads.s3.cern.ch/docs/kicad-doc-5.1.0.tar.gz[Precompiled docs], https://github.com/KiCad/kicad-doc/releases/tag/5.1.0[doc sources]
-* link:https://github.com/KiCad/kicad-i18n/releases/tag/5.1.0[i18n (translations)]
-* link:https://github.com/KiCad/kicad-symbols/releases/tag/5.1.0[symbols]
-* link:https://github.com/KiCad/kicad-footprints/releases/tag/5.1.0[footprints]
-* link:https://github.com/KiCad/kicad-packages3D/releases/tag/5.1.0[packages3D]
-* link:https://github.com/KiCad/kicad-templates/releases/tag/5.1.0[templates]
+* link:https://launchpad.net/kicad/5.0/5.1.4/+download/kicad-5.1.4.tar.xz[Source code]
+* link:https://kicad-downloads.s3.cern.ch/docs/kicad-doc-5.1.4.tar.gz[Precompiled docs], https://github.com/KiCad/kicad-doc/releases/tag/5.1.4[doc sources]
+* link:https://github.com/KiCad/kicad-i18n/releases/tag/5.1.4[i18n (translations)]
+* link:https://github.com/KiCad/kicad-symbols/releases/tag/5.1.4[symbols]
+* link:https://github.com/KiCad/kicad-footprints/releases/tag/5.1.4[footprints]
+* link:https://github.com/KiCad/kicad-packages3D/releases/tag/5.1.4[packages3D]
+* link:https://github.com/KiCad/kicad-templates/releases/tag/5.1.4[templates]
As a packager, please work to enable all the build options, that is
all the scripting options, OCE or OCC and ngspice. With recent
diff --git a/content/download/windows.adoc b/content/download/windows.adoc
index e96ca66d..6c7dde84 100644
--- a/content/download/windows.adoc
+++ b/content/download/windows.adoc
@@ -11,18 +11,18 @@ link:/help/system-requirements/[System Requirements] for more details.
== Stable Release
-Current Version: *5.1.2*
+Current Version: *5.1.4*
++++
64-bit (recommended)
Download mirrors
@@ -33,13 +33,13 @@ Current Version: *5.1.2*
32-bit
Download mirrors
diff --git a/content/external-tools/stepup.adoc b/content/external-tools/stepup.adoc
index 5332e5e6..1ca3f58d 100644
--- a/content/external-tools/stepup.adoc
+++ b/content/external-tools/stepup.adoc
@@ -12,4 +12,4 @@ Main features:
* Load kicad board and parts in FreeCAD and export it to STEP (or IGES) models
* Load `kicad_mod` footprint in FreeCAD to easy and precisely align the mechanical model to kicad footprint
* Pull a pcb edge from a `kicad_pcb` board, edit it in FreeCAD Sketcher and push it back to kicad
-* Pusk & pull 3D models positions between FreeCAD and KiCAD
+* Push & pull 3D models positions between FreeCAD and KiCAD
diff --git a/content/help/system-requirements.adoc b/content/help/system-requirements.adoc
index e09bb5a7..74a90720 100644
--- a/content/help/system-requirements.adoc
+++ b/content/help/system-requirements.adoc
@@ -13,17 +13,21 @@ toc::[]
== Common System Requirements (hardware specs)
-* Pentium-compatible PC (Pentium IV, Athlon or more-recent system recommended);
+* Supported Processor Architectures
+** Intel (or compatible) 32 and 64 bit.
+** PowerPC 32 and 64 bit.
+** ARM 32 and 64 bit.
+** MIPS 64 bit.
-* 512 MB RAM (1024 MB RAM recommended);
+* 1GB RAM (2G RAM recommended);
-* Up to 5GB available hard disk space;
+* Up to 10GB available hard disk space;
-* Screen resolution of 1024x768 works but, 1280x1024 or higher is recommended,
- with at least 16K colors (with 1024x768 some buttons may result hidden but
- corresponding commands should be reachable via menu anyway).
+* Screen resolution of 1280x1024 works but 1920x1080 or higher is recommended, with at
+ least 16K colors. At lower resolutions toolbar buttons may be hidden but corresponding
+ commands should be reachable via menu.
-* Graphic card with at least OpenGL 2.1, with hardware shaders. Check
+* Graphics card with OpenGL 2.1 or greater that supports hardware shaders. Check
the OpenGL specs of the card:
** Intel: no cards that came before the HD-Graphics series, regardless of the name including "HD".
Intel cards that are reported working starts from model HD2000 and higher.
@@ -40,14 +44,15 @@ See: http://kicad-pcb.org/help/known-system-related-issues/ for software specifi
== Specific System Requirements
-KiCad supports major operating systems that remain supported by their developers. After the operating systems'
-respective companies stop releasing updates for the system, KiCad will not be specifically tested with the
-old system. Older operating systems may continue to work with KiCad beyond this time but bugs must be reproduced on a supported operating system before they will be addressed by KiCad.
+KiCad supports major operating systems that remain supported by their developers. After the
+operating systems' respective organizations stop releasing updates for the system, KiCad will
+not be specifically tested with the unsupported system. Unsupported operating systems may
+continue to work with KiCad beyond this time but bugs must be reproduced on a supported operating
+system before they will be addressed by KiCad.
=== Windows
-The software prerequisites for installing KiCad on a Windows
-system are as follows:
+The software prerequisites for installing KiCad on a Windows system are as follows:
[%header,width="50%",cols="10,^2"]
|===
@@ -77,9 +82,8 @@ The software prerequisites for installing on a macOS system are as follows:
=== GNU/Linux
The following Linux distribution versions have been tested and are known to be working.
-Issues or bugs that occur on an unsupported platform must be
-reproduced on an officially supported distribution and window manager before they will
-be addressed by KiCad.
+Issues or bugs that occur on an unsupported platform must be reproduced on an officially
+supported distribution and window manager before they will be addressed by KiCad.
==== Tested Distributions
@@ -92,26 +96,31 @@ be addressed by KiCad.
|Ubuntu 18.10|1-Apr-2019
|Debian 9 (Stretch)|approx 2020
|Debian 10 (Buster)|approx 2022
-|Fedora 29|approx May 2019
+|Fedora 29|approx November 2019
+|Fedora 30|approx May 2020
|===
[%hardbreaks]
==== Additional Linux Considerations
-Linux also allows the user to select their window manager. There are many esoteric
-window managers available for Linux and some may have unexpected behavior. KiCad officially
-supports the following window managers:
+Linux allows users to select their preferred window manager. There are many esoteric window
+managers available for Linux and some may have unexpected behavior. KiCad officially supports
+the following window managers:
* Metacity (used by GNOME 2 and GNOME flashback)
-* Mutter (when used with an X11 backend)
-* KWin (when used with an X11 backend)
+* Mutter (GNOME 3)
+* KWin (KDE)
* Xfwm (used by XFCE)
+* i3 (Arch Linux)
+* Unity (Ubuntu prior to 18.04)
==== Graphical Windowing Backend
-KiCad officially supports the X11 backend. Users who choose to use Wayland will run in
-a compatibility layer called link:https://wayland.freedesktop.org/xserver.html[XWayland].
+Regardless of the window manager, KiCad officially only supports the X11 backend. Users who
+choose to use Wayland will have to run KiCad in the compatibility layer
+link:https://wayland.freedesktop.org/xserver.html[XWayland].
Issues or bugs encountered while using XWayland must be reproduced under X11 before they
-will be addressed by KiCad.
+will be addressed by KiCad. Bugs that cannot be reproduced on X11 should be reported to
+the link:https://gitlab.freedesktop.org/wayland/wayland/issues[Wayland bug tracker].
=== Other OSes
diff --git a/content/help/tutorials.adoc b/content/help/tutorials.adoc
index 950f1fd4..8cfae77a 100644
--- a/content/help/tutorials.adoc
+++ b/content/help/tutorials.adoc
@@ -22,6 +22,8 @@ Several text-based tutorials as well as video tutorials have been put together b
- http://babryce.com/kicad/tutorial.html[B. A. Bryce's Tutorial]
- http://happyrobotlabs.com/posts/tutorials/tutorial-3d-kicad-parts-using-openscad-and-wings3d/[Happy Robot Labs: 3D KiCad Parts Using OpenSCAD and Wings3D]
- http://stffrdhrn.github.io/electronics/2015/04/28/simulating_kicad_schematics_in_spice.html[Simulating KiCad Schematics in Spice]
+- https://thestumbler.io/projs/modelrr/03-spice-and-kicad.html[Spice and Kicad - Making Kicad 5.0 play nice with Spice]
+- https://www.woolseyworkshop.com/2019/07/01/performing-a-circuit-simulation-in-kicad/[Performing A Circuit Simulation In KiCad]
- https://www.mikrocontroller.net/wikifiles/a/ab/HierarchicalSchematicsAsBuildingblocksAtKiCad_RevC-EN_06May2015.pdf[Hierarchical schematics as schematic buildingblocks] by Bernd Wiebus. (https://www.mikrocontroller.net/wikifiles/7/79/HierarchischeSchaltplaeneAlsBausteineInKicad_RevC_23Dec2013.pdf[Original in german])
- https://www.mikrocontroller.net/wikifiles/6/64/Kicad-Wings3D_Leaflet_25April2013.pdf[Notes on using Wings3D] by Bernd Wiebus (https://www.mikrocontroller.net/wikifiles/0/02/Kicad-Wings3D_Merkzettel_29November2012.pdf[Original in german])
- https://flyingcarsandstuff.com/2016/10/kicad-techniques-tips-and-work-arounds/[Kicad: Techniques, Tips and Work-arounds]
diff --git a/content/help/upgrading.adoc b/content/help/upgrading.adoc
index e69e4ad7..69bdd7a0 100644
--- a/content/help/upgrading.adoc
+++ b/content/help/upgrading.adoc
@@ -1,12 +1,12 @@
+++
title = "Upgrading"
-[menu.main]
- parent = "Help"
- name = "Upgrading"
-weight = 40
aliases = [
"/help/migration/"
]
+[menu.main]
+ parent = "Help"
+ name = "Upgrading"
+ weight = 40
+++
Newer versions of KiCad bring changes to file formats and functionality. While effort is made to maintain compatibility, there may ultimately be changes that must made
@@ -17,42 +17,40 @@ Information on upgrading from 4.0 to 5.0 can be found in the
http://docs.kicad-pcb.org/5.0.2/en/kicad/kicad.html#upgrading_from_version_4_to_version_5[KiCad help manual].
-== Upgrade from any version before 4.0 (also known as "old-stable") to 4.0
+== Upgrade from any version before 4.0 (also known as "old-stable")
-There is likely to be some issues if you want to migrate designs from the old stable, revision around bzr revision 4022, which had a particular annoying bug, where layer names were translated, which they should never have been.
+=== Issues are fixed in 5.1.1
+
+Note that the issues referenced below are resolved by the upcoming KiCad version 5.1.1. Layer names will be translated to the standard English names on opening and will be written out as English when the file is saved.
=== Layernames are translated
-This issue arises if you used a "old stable" version with a language other than English.
+There is a known issue when migrating designs from the old stable, revision around bzr revision 4022, where layer names were translated, which they should never have been. This issue arises if you used KiCad localized for Italian, French or Polish.
-You need to edit all `.kicad_pcb` files with a text editor (notepad, ...) and change the layer names from Italian/French to their English counterparts. Below is the correspondance of the layer names. Caution: there are more instances to replace than just the layer list. Be sure that you don't miss any.
+To resolve this issue, you will to edit all `.kicad_pcb` files with a text editor (notepad, ...) and change the layer names from Italian/French/Polish to their English counterparts. Below is the correspondance of the layer names. Caution: there are more instances to replace than just the layer list. Be sure that you don't miss any.
==== New English names
----
(layers
- (15 F.Cu signal)
- (0 B.Cu signal)
- (16 B.Adhes user)
- (17 F.Adhes user)
- (18 B.Paste user)
- (19 F.Paste user)
- (20 B.SilkS user)
- (21 F.SilkS user)
- (22 B.Mask user)
- (23 F.Mask user)
- (24 Dwgs.User user)
- (25 Cmts.User user)
- (26 Eco1.User user)
- (27 Eco2.User user)
- (28 Edge.Cuts user)
+ (32 B.Adhes user)
+ (33 F.Adhes user)
+ (34 B.Paste user)
+ (35 F.Paste user)
+ (36 B.SilkS user)
+ (37 F.SilkS user)
+ (38 B.Mask user)
+ (39 F.Mask user)
+ (40 Dwgs.User user)
+ (41 Cmts.User user)
+ (42 Eco1.User user)
+ (43 Eco2.User user)
+ (44 Edge.Cuts user)
)
----
==== Obsolete Italian names
----
(layers
- (15 Rame.Fronte signal)
- (0 Rame.Retro signal)
(16 Adesivo.Retro user)
(17 Adesivo.Fronte user)
(18 Pasta.Retro user)
@@ -72,8 +70,6 @@ You need to edit all `.kicad_pcb` files with a text editor (notepad, ...) and ch
==== Obsolete French names
----
(layers
- (15 Front signal)
- (0 Back signal)
(16 Dessous.Adhes user)
(17 Dessus.Adhes user)
(18 Dessous.Pate user)
@@ -90,6 +86,25 @@ You need to edit all `.kicad_pcb` files with a text editor (notepad, ...) and ch
)
----
+==== Obsolete Polish names
+----
+(layers
+ (16 Kleju_Dolna user)
+ (17 Kleju_Gorna user)
+ (18 Pasty_Dolna user)
+ (19 Pasty_Gorna user)
+ (20 Opisowa_Dolna user)
+ (21 Opisowa_Gorna user)
+ (22 Maski_Dolna user)
+ (23 Maski_Gorna user)
+ (24 Rysunkowa user)
+ (25 Komentarzy user)
+ (26 ECO1 user)
+ (27 ECO2 user)
+ (28 Krawedziowa user)
+)
+----
+
=== Schematic libraries are updated
Be aware that the schematic libries has gotten an overhaul (still in
diff --git a/content/klc/F4.4.adoc b/content/klc/F4.4.adoc
index 99d750de..0a6329e5 100644
--- a/content/klc/F4.4.adoc
+++ b/content/klc/F4.4.adoc
@@ -9,9 +9,9 @@ In such cases the datasheet will usually specify the quantity, size and position
In addition to manufacturer requirements, a number of extra conventions should be followed when creating thermal vias.
. Thermal vias must share the same pad number as the pad on which they are placed
-. Where thermal vias are connected to a pad on the `F.Cu` layer, a copper pad on the `B.Cu` layer should be added, to provide thermal relief for the via. This pad must be large enough to fully surround the via(s) with a margin of `>= 0.5mm`. __Note: If the datasheet gives conflicting advice to the placement of this pad on the `B.Cu` layer, then the datasheet instruction should be given preference.__
+. Where thermal vias are connected to a pad on the `F.Cu` layer, a copper pad on the `B.Cu` layer should be added, to provide thermal relief for the via. `B.Mask` is not to be enabled on the `B.Cu` pad so mask is present. This pad must be large enough to fully surround the via(s) with a margin of `>= 0.5mm`. __Note: If the datasheet gives conflicting advice to the placement of this pad on the `B.Cu` layer, then the datasheet instruction should be given preference.__
[start=3]
. Unless instructed by the datasheet, solder paste must not be placed over the thermal via(s). This can cause solder to wick into the via during reflow, and cause solder joint issues.
. When submitting a footprint with thermal vias, the suffix `_ThermalVias` should be added to the footprint name
-. If it does not already exist, a second version of the footprint without the thermal vias should be added. __Note: This second version should not have the `_ThermalVias` suffix in the footprint name.__
\ No newline at end of file
+. If it does not already exist, a second version of the footprint without the thermal vias should be added. __Note: This second version should not have the `_ThermalVias` suffix in the footprint name.__
diff --git a/content/klc/F5.1.adoc b/content/klc/F5.1.adoc
index 5fa4aa6c..8c15ef89 100644
--- a/content/klc/F5.1.adoc
+++ b/content/klc/F5.1.adoc
@@ -14,16 +14,17 @@ The following elements must be provided on the silkscreen.
. Reference Designator must be drawn on `F.SilkS` layer
.. Text size = `1.00mm`
.. Text thickness = `0.15mm`
+. Silkscreen line width is between {`0.10mm` and `0.15mm`} as per IPC-7351C:
+.. Silkscreen line width should nominally be `0.12mm`
+.. `0.1mm` is allowed for high density designs
+.. `0.15mm` is allowed for low density designs
. Silkscreen must not be placed over pads or areas of exposed copper
- * Clearance between silkscreen and exposed copper elements must be at least `0.2mm` or more than the pad mask expansion (whichever is greater).
+.. Clearance between silkscreen and exposed copper elements is recommended to be 0.2mm.
+.. Clearance must be at least the silkscreen line width or pad mask expansion, whichever is greater.
. For SMD footprints, silkscreen must be fully visible after boards assembly (no silkscreen allowed under component)
. For THT components, silkscreen may be placed under component to aid in assembly process
-. Silkscreen line width is between {`0.10mm` and `0.15mm`} as per IPC-7351C:
- * Silkscreen line width should nominally be `0.12mm`
- * `0.1mm` is allowed for high density designs
- * `0.15mm` is allowed for low density designs
. Pin-1 designator is provided on the `F.SilkS` layer
. Pin-1 designator must be visible after board assembly
{{< klcimg src="F5.1a" title="Silkscreen layer examples" >}}
-{{< klcimg src="F5.1b" title="More silkscreen layer examples" >}}
\ No newline at end of file
+{{< klcimg src="F5.1b" title="More silkscreen layer examples" >}}
diff --git a/content/klc/F6.3.adoc b/content/klc/F6.3.adoc
index 10735460..d79e40bd 100644
--- a/content/klc/F6.3.adoc
+++ b/content/klc/F6.3.adoc
@@ -14,7 +14,7 @@ Surface mount pads have specific requirements for PCB design.
.. `B.Paste` - Back solderpaste (stencil openings)
. Pads with specific stencil aperture design requirements require special attention (see details below)
-## Requirements for solderpaste
+*Requirements for solderpaste*
Many components (IC packages in particular) have specific design requirements for solderpaste (stencil) design. These requirements are often found in the footprint datasheet or an associated technical document.
@@ -36,7 +36,7 @@ Custom stencil openings are accommodated as follows:
{{< klcimg src="F6.3b" title="Resulting stencil openings shown in footprint editor" >}}
{{< klcimg src="F6.3c" title="Result stencil openings shown in 3D viewer">}}
-## Size of exposed pads
+*Size of exposed pads*
The following rules apply for finding the correct pad size for parts including an exposed pad.
@@ -45,7 +45,7 @@ The following rules apply for finding the correct pad size for parts including a
.. It is not allowed to use a footprint pad smaller than the minimum size of the package pad.
.. Soldermask defined pas are to be used if the suggested footprint uses a pad larger than the maximum size of the package pad. (Meaning: copper can cover a larger area, but the exposed copper is still within the package pads tolerance range.)
-## Clearance requirement between exposed pads and normal pads
+*Clearance requirement between exposed pads and normal pads*
. There should be clearance of at least 0.2mm between the exposed pad and the normal pads.
. This clearance applies only to the area free of soldermask. (The clearance for soldermask defined pads is the spacing between the normal pads and the soldermask cutout of the exposed pad.)
diff --git a/content/klc/F7.7.adoc b/content/klc/F7.7.adoc
index 6f62c30d..a2c39554 100644
--- a/content/klc/F7.7.adoc
+++ b/content/klc/F7.7.adoc
@@ -1,5 +1,5 @@
+++
-brief = "Oval holes (Plated Milled Slots)"
+brief = "Oval holes (plated milled slots)"
+++
The sizes for oval holes must be chosen such that there is 0.2mm clearance between the maximum lead size and the hole in all directions.
diff --git a/content/klc/F9.1.adoc b/content/klc/F9.1.adoc
index 91d03dcd..f8b75d3c 100644
--- a/content/klc/F9.1.adoc
+++ b/content/klc/F9.1.adoc
@@ -2,9 +2,9 @@
brief = "Footprint meta-data is filled in as appropriate"
+++
-. **Documentation** field contains comma-separated device information. Where appropriate, a URL to the footprint datasheet should be included.
+. **Reference** field must be set to `REF**`
+. **Value** and **Footprint Name** fields must match footprint filename (ignoring the `.kicad_mod` extension)
+. **Description** field contains comma-separated device information. Where appropriate, a URL to the footprint datasheet should be included.
. **Keywords** field contains space-separated keyword values
-. **Ref** field must be set to `REF**`
-. **Value** field must match footprint filename (ignoring the `.kicad_mod` extension)
{{< klcimg src="F9.1a" title="Footprint Properties dialog" >}}
diff --git a/content/klc/S2.1.adoc b/content/klc/S2.1.adoc
index 07b56588..68531b93 100644
--- a/content/klc/S2.1.adoc
+++ b/content/klc/S2.1.adoc
@@ -2,14 +2,15 @@
brief = "General symbol naming guidelines"
+++
-. Library naming should not be duplicated in footprint name
+. Library name should not be duplicated in symbol name
. If symbol with same name exists for multiple manufacturers, the manufacturer name is written first
. Specific manufacturer name (for atomic parts)
. Type of symbol (for generic parts)
.. May be shortened for common components (e.g. `Conn` for `Connector`)
.. Reference designator may be substituted for common components (e.g. `D`, `C`, `LED`)
-. Part name should include extension for specific footprint if required (e.g. `SOIC`)
+. Part name should include extension for specific footprint if the same part is produced by multiple manufacturers that have conflicting package name suffixes (e.g. `SOIC`)
+.. The pin number may be appended if there are multiple package possibilities (e.g. `SOIC8`)
. Any modification of the original symbol, indicated by appending the reason (e.g. different pin ordering - `Q_NPN_CBE`, `Q_NPN_BCE`)
. Indicate quantity of elements for symbol arrays (e.g. resistor array with 8 elements - `Resistor_x8`)
. Add suffixes for symbol variations
-.. For multi unit variants of typically single unit symbols add the suffix `_Split`
+.. For multi-unit variants of typically single-unit symbols add the suffix `_Split`
diff --git a/content/klc/S4.1.adoc b/content/klc/S4.1.adoc
index 7276616a..dfce4a3f 100644
--- a/content/klc/S4.1.adoc
+++ b/content/klc/S4.1.adoc
@@ -2,10 +2,11 @@
brief = "General pin requirements"
+++
-. Using a `100mil` (`2.54mm`) grid, pin origin must lie on grid node (IEC-60617)
+. Using a `100mil` (`2.54mm`) grid, pin origin must lie on a grid node (IEC-60617)
. Pins should have a length of at least `100mil` (`2.54mm`)
-* Shorter pins may be allowed to accommodate simple symbols for discrete devices such as resistors, capacitors, etc.
-. Pin length must not exceed `300mil` (`7.62mm`)
-. Pin length can be incremented in steps of `50mil` (`1.27mm`) as required, whilst meeting the absolute length limits as specified above
+* Pin length can be increased in steps of `50mil` (`1.27mm`)
+* The number of characters in the pin number determine a pin's length. When there are two characters in the pin number then 100mil (`2.54mm`) long pins should be used, when three characters then 150mil (`3.81mm`) long pins should be used, etc.
+* Pin length must not exceed 300mil (7.62mm)
+* Shorter pins are allowed on simple symbols for discrete devices such as resistors, capacitors, etc.
+* All pins on a symbol must have the same length
. Pin numbers must be unique (no two pins may have the same number)
-
diff --git a/content/libraries/klc.adoc b/content/libraries/klc.adoc
index a307599e..2f980538 100644
--- a/content/libraries/klc.adoc
+++ b/content/libraries/klc.adoc
@@ -13,7 +13,7 @@ aliases = [ "/klc/" ]
toc::[]
-**link:/libraries/klc/history/[Revision: 3.0.18]**
+**link:/libraries/klc/history/[Revision: 3.0.21]**
---
diff --git a/content/libraries/klc_history.adoc b/content/libraries/klc_history.adoc
index d4d3ad4e..ccf9b50f 100644
--- a/content/libraries/klc_history.adoc
+++ b/content/libraries/klc_history.adoc
@@ -5,10 +5,21 @@ url = "/libraries/klc/history/"
+++
---
-== 3.0.19 - 2019-05-04
+== 3.0.21 - 2019-09-01
* Clarify rules regarding NC pins
* Clarify when they may be omitted
- * Clarify that they must be hidden when
+ * Clarify handling of hidden NC pins
+* Clarify handling of hidden pins
+
+== 3.0.20 - 2019-06-30
+* Update F9.1 screenshots and terms to match current GUI
+
+== 3.0.19 - 2019-06-19
+* Clarify symbol naming for symbols with multiple manufactureres with different package suffixes (S2.1)
+* Added more details on silk-to-pad clearance (F5.1)
+* Specified that thermal pads with vias need a bottom copper pad (F4.4)
+* Expanded details for selecting pin length (S4.1)
+* Minor edits for style, wording, and grammar
== 3.0.18 - 2019-02-15
* Document rules for overlapping/duplicate graphic elements (new rule F5.4)
diff --git a/content/libraries/third_party.adoc b/content/libraries/third_party.adoc
index 9991030a..38d0f1bb 100644
--- a/content/libraries/third_party.adoc
+++ b/content/libraries/third_party.adoc
@@ -20,4 +20,11 @@ link:https://www.digikey.com[Digi-Key] maintains an atomic parts library for KiC
== SparkFun
-link:https://sparkfun.com[SparkFun Electronics] provide KiCad library files for many of their products on their link:https://github.com/sparkfun/SparkFun-KiCad-Libraries[GitHub page]. These libraries are based on the SparkFun Eagle libraries.
\ No newline at end of file
+link:https://sparkfun.com[SparkFun Electronics] provide KiCad library files for many of their products on their link:https://github.com/sparkfun/SparkFun-KiCad-Libraries[GitHub page]. These libraries are based on the SparkFun Eagle libraries.
+
+== SnapEDA
+
+link:https://www.snapeda.com[SnapEDA] provides KiCad symbol and footprint libraries for their
+customers. The libraries are freely available and can be found on their
+link:https://www.snapeda.com/kicad[KiCad library page]. The library license can be found on their
+link:https://www.snapeda.com/about/terms[terms of service page].
diff --git a/content/made-with-kicad/axiom.adoc b/content/made-with-kicad/axiom.adoc
new file mode 100644
index 00000000..2e2786b2
--- /dev/null
+++ b/content/made-with-kicad/axiom.adoc
@@ -0,0 +1,9 @@
++++
+title = "Axiom motor controller"
+projectimage = "/img/madewithkicad/Axiom-motor-controller.png"
+projectdeveloper = "EV Power Designs Inc."
+projecturl = "http://www.powerdesigns.ca"
++++
+
+Axiom is a high power, high performance 100kW+ motor controller based upon the link:https://vesc-project.com/[VESC platform] for compatibility with firmware and GUI.
+It is designed for driving 650V 600A IGBTs and comes with many safety features.
diff --git a/content/made-with-kicad/electrosmart-ecg.adoc b/content/made-with-kicad/electrosmart-ecg.adoc
deleted file mode 100644
index b8894681..00000000
--- a/content/made-with-kicad/electrosmart-ecg.adoc
+++ /dev/null
@@ -1,9 +0,0 @@
-+++
-title = "Electrosmart ECG"
-projectimage = "/img/madewithkicad/ElectrosmartECG.jpg"
-projectdeveloper = "Palta Tech"
-projecturl = "http://www.paltatech.com/electrosmart/"
-type = "made-with-kicad"
-+++
-
-12 lead ECG with an ARM Cortex M3, USB and Bluetooth, developed and sold in partnership with Eccosur.
diff --git a/content/made-with-kicad/electrosmart-iti.adoc b/content/made-with-kicad/electrosmart-iti.adoc
deleted file mode 100644
index 781f5f27..00000000
--- a/content/made-with-kicad/electrosmart-iti.adoc
+++ /dev/null
@@ -1,11 +0,0 @@
-+++
-title = "Electronic Industrial Temperature Interface"
-projectimage = "/img/madewithkicad/EITI.jpg"
-projectdeveloper = "Palta Tech"
-projecturl = "http://www.paltatech.com/eiti/"
-+++
-
-EITI is an I/O module for a PLC/MODBUS based design.
-The board measures temperature signals, communicate via a RX or TX 4-20mA current loop signal
-and communicate with other devices over MODBUS. This allows a PLC to interface with
-many common analog signals.
diff --git a/content/made-with-kicad/scopefun.adoc b/content/made-with-kicad/scopefun.adoc
new file mode 100644
index 00000000..a68eae91
--- /dev/null
+++ b/content/made-with-kicad/scopefun.adoc
@@ -0,0 +1,8 @@
++++
+title = "ScopeFun"
+projectimage = "/img/madewithkicad/scopefun.jpg"
+projectdeveloper = "Dejan Priversek and David Kosenina"
+projecturl = "https://www.scopefun.com"
++++
+
+ScopeFun in an open source, all-in-one instrumentation platform. It includes an oscilloscope, arbitrary waveform generator, spectrum analyzer, logic analyzer, and digital pattern generator.
\ No newline at end of file
diff --git a/layouts/section/download.html b/layouts/section/download.html
index 035401f9..73cad203 100644
--- a/layouts/section/download.html
+++ b/layouts/section/download.html
@@ -22,7 +22,7 @@
{{ .Title }}
- KiCad 5.1.2 was released in April 2019. See the announcement on the blog. Details on the availability for your platform can be seen for each of the platforms below.
+ KiCad 5.1.4 was released in August 2019. See the announcement on the blog. Details on the availability for your platform can be seen for each of the platforms below.
Select your operating system or distribution
diff --git a/static/img/klc/F9.1a.png b/static/img/klc/F9.1a.png
index 2810642f..533b558f 100644
Binary files a/static/img/klc/F9.1a.png and b/static/img/klc/F9.1a.png differ
diff --git a/static/img/madewithkicad/Axiom-motor-controller.png b/static/img/madewithkicad/Axiom-motor-controller.png
new file mode 100644
index 00000000..e3abd5fd
Binary files /dev/null and b/static/img/madewithkicad/Axiom-motor-controller.png differ
diff --git a/static/img/madewithkicad/EITI.jpg b/static/img/madewithkicad/EITI.jpg
deleted file mode 100644
index 50ccfb0a..00000000
Binary files a/static/img/madewithkicad/EITI.jpg and /dev/null differ
diff --git a/static/img/madewithkicad/ElectrosmartECG.jpg b/static/img/madewithkicad/ElectrosmartECG.jpg
deleted file mode 100644
index 543ed6c0..00000000
Binary files a/static/img/madewithkicad/ElectrosmartECG.jpg and /dev/null differ
diff --git a/static/img/madewithkicad/VESC-controller.jpg b/static/img/madewithkicad/VESC-controller.jpg
deleted file mode 100644
index a8e4adf9..00000000
Binary files a/static/img/madewithkicad/VESC-controller.jpg and /dev/null differ
diff --git a/static/img/madewithkicad/scopefun.jpg b/static/img/madewithkicad/scopefun.jpg
new file mode 100644
index 00000000..d5113365
Binary files /dev/null and b/static/img/madewithkicad/scopefun.jpg differ
CERN
-
+
Futureware