The people who actually need instructions for filing a bug report do not read instructions.

Ho-ly these are exciting news! I love the direction KiCAD is taking. Bigger players need to watch their backs!

Just started to use it for the first time with the help of the introduction manual. Great tool! Thank you!

Really love to see that full pad stacks, schematic variants and outjobs are on their way to stable release, great work! Also I'm looking forward for custom grids, especially polar grids. You have some nice selling points for the next two version, keep up your great work =)

Is the git integration being worked on? That was not mentioned in the status update. I just tested in version 8 and it does not seem complete, I will try in nightly, but automatically git fetch seems to be missing even on kicad start or refresh.

How is pin/gate swapping still not implemented? It's one of the most basic features you can imagine. Granted, unlike in Eagle, KiCad wires can change nets much more easily, but I cannot think of a project with logic gates where I didn't need to swap gates and pins. The "KiCad" way seems to be to select and mirror the gate, but that falls apart when there are input-output pairs in level shifters, isolators and bus transceivers. By the looks of it, don't hold your breath that these concepts will be represented in KiCad.

So excited for KiCAD 9! Y'all are doing amazing work.

Hi! Nice video. But the link or slides is not working, it would be super nice if someone fixed it. Thanks :)

Could you make a iPad version of Kincaid? I like iPads because they bust my creativity, especially with the pencil like user interface

A shame it has no GUI. That will deter 99.999999999999% of the users

Database libraries functionality has what has been holding me back from adopting kicad. Must say that I’m a little disappointed that 3d models of components seems to be overlooked in this presentation as 3d modesl are a key part of the EDA ecosystem now. kicad seems to have a schizophrenic model of what a component should be and its relationships. Like why does the 3d model get associated with a footprint. They are independent items that interface at a planar pcb level. I might have a components that looks like a baby elephant and a gazelle that have a SOT-23 footprint. A component has: A one to many relationship to a schematic symbol A one to many relationship to pcb footprint A many to one relationship to a data sheet (one data sheet cover multiple variants do a component) A one to many relationship to 3d model A one to many relationship with suppliers A one to on relationship with a suppliers part number A one to one relationship to a part of the contract manufacturers part And some cases these relationships have co-dependencies like: pin numbers/ labels for schematic and pcb footprints. 3d models and footrpints have a co-dependency on origin and orientation. Until a model of the component can be established and published prior to making changes then to the software, the results of new changes will be ad-how at best. How can software developers ensure that the changes they are making are compatable with different workflows if there is no documented model of a compoennt and its relationships and ensure forwards compatability. Ad-hoc changes to the software that break workflows will frustrate the user base no end!! Thank you for the presentation, we need to talk about these things and have a plan forward.

Delighted to hear about ODB++. At this date, I'm surprised a PCBA company would demand this format, but it happened to me once last year.

Is there an analog equivalent to d_process?

I Love KiCad Best regard From TamilNadu Agastinraj S

You are best ever 🙏 Thanks alot

I love KiCAD SO much! Since i got my ZX-Spectrum ages ago i basically live between a computer and a chair and in all these years i've never seen a program that well made - it's super friendly to newcomers and is intuitive, UI is simple and easy to understand. And yet it's a very powerful tool that supports even more complexity via plugins and scripting (hope you guys finish polishing it). Much love from a fan <3

Can this support arbitrary library hierarchies? so I can finally have separate nested folders for each of something like "connectors -> jst -> sh -> smd -> right angle -> [actual list of connector components]" instead of making convoluted component names so they get alphabetically sorted?

I love KiCAD! You can't beat the price. Please don't forget the support the team and donate...

If you want to learn more about ngspice simulation in KiCad 8. Holger has started a video series of tutorials: kzbin.info/www/bejne/pKfXqpWLndSHhbM

I think we need to pitch in for a new laptop for Wayne :)

“EasyEDA project importer” - please no. There are no decent EasyEDA schematics out there. They all look like shit. All this will do is get people to get their broken designs into KiCad. Yuck. If anything, if your design is worth importing into KiCad, it’s worth redrawing properly in KiCad.

This is great, I always had an issue with the KiCad library.

I’m very happy to start simulating in KiCad! Thanks guys, keep it up 😃

It is unfortunate that it is not clear which parts of the presentation relate to ngspice, which parts relate to KiCad 8, and which parts relate to both working in conjunction (KiCad GUI with ngspice). Also, it would be helpful to have a link to a Git repository containing KiCad projects with the Schematics+ngspice models from the presentation.

Interesting feature could be Team working capabilities for a very large design, ok ok it sounds crazy and not easy but I mean something you can work on the PCB and another one is changing the schematic, then the working team connected receive the notification instantly that someone has changed some parts and needs attention before to push into the repository or blindly kick off others works out.

Awesome, it keeps getting better, those v9 features also look extremely useful.

I am glad database is there this was the limiting feature which made my colleagues stay away for long. Also Kicad + Octopart or Digikey API will be just cherry on top.

Watch out for 'Flux' and the AI related features coming through, albeit on a handful of commercial packages. Altium is way ahead on BOM generation. On the other hand KiCAD wipes the floor (IMO) with ANY package older than 10 years!

I do hope you guys will eventually look at your renderer again. Not having control over the z-layer order of symbol components has been frustrating when wanting symbols to have lines draw over one another in a particular order.

Ah, it's supposed to be pronounced "Kee-cad". I always say it "Kiy-cad".

Ok, how about adding simulation of PCB traces and SI in KiCAD ?

In the introduction, one should directly say: "zone fills are generated based on custom rules where they apply, and thus such rules do not need to be considered in the context of DRC checks again. Otherwise, frankly, that would be a bug." 22:00 the name of the example (PTH in pad) is pin-in-paste for through-hole reflow. 24:30 oddly enough, 'F*' does not seem to apply to F.Cu, so it neither allows influencing zone fill with graphic items, nor can an error be generated when silkscreen is e.g. on RF traces sensitive to extra dielectric on top. 26:00 I keep pressing CTRL+F and wonder why no search bar pops up in the syntax help. I then keep copying the help text to notepad++... 34:46 custom rule for length matching: what you cannot do right now is e.g. to have a single rule that uses regex on the net class name to grab a length spec from that string, which would be cool

That's a serious upgrade. Well done. I wish to see a version of kicad that's self hosted and runs in a browser. Sometimes I need to work remotely, and something like easyEDA makes a lot of sense.

Kicad has gone from strength to strength in recent years. Shows what can happen when people get behind OSS.

Thank you for your work, it's truly an incredible piece of software!

I'm hyped for the V9!!

The software is getting to the point I'm starting to consider it a good alternative to Altium... V9 roadmap makes it even more so... you're on a roll! You've reached that point where the software is good enough for serious professional use and that gives you money and resources to make it even better and so forth... last few meters to go and you'll be the new standard! Keep it up everyone!

Good stuff!

Looking forward to Kicad 8!

Looks interesting but I can't read the slides.

I wish it would be possible to migrate mentor/siemens Pads project into Kicad. Siemens software is such a crap!

Thank you your presentation. I found my fault of Our my db integration problem. The value attribute was not turning on automatically. I found my fault. I used {... : "true",}. But I was should {.... : true, }

How to install kicad V8.0?

These yearly conferences are totally nuts and one of my favourites on KZbin. OpenWRT has done this too ...are you listening FreeCad?

Would have been much better with pictures illustrating functions. Anyway thanks to the team. Waiting impatiently version 8 :)

I would recommend to add the presented Rules in the kicad rules example section

Thank you for all your work!

I have a wish list (thumbs up if you agree ;-) ): - Combine fills with different settings - Overwrite properties like thermal gap for the whole footprint - Stop changing GUI symbols over and over again - Change properties of many symbols/footprints if they are common (dont populate, width of graphic elements, etc) - Net tie on inner layers - Draw grid on top! Its hidden when more layers are activated. Which makes it almost useless. - When changing a net, and opening the dropdown list, have the old entry selected, so you dont have to scroll, when changing from GND1 to GND2. - clearance properties for a track - catch mouse pointer on pick point (corners) with more range (without really clicking on it) - circle as track! There is an option to make a track out of a circle, but it does not work. - Easy change of layer, of every element, even if in groups or selecetions of many kinds. (If different layers, ignore, and set to new layer) - When selecting lines in the schematic, highlight them in the PCB editor - When footprint created, make it available in symboleditor! - make filter in footprint library browser find a certain footprint. Cant find a footprint without selecting its parent folder! - Grouping of smybols in schematics - Make it more visible if in group (PCB editor) - Rounting of multiple tracks at once - Mirroring of more than one footprint. Also on a group. - When minimizing and maximising the schematic editor, let it maximize in the previous position. - ratsnest line between different layers should start from via, and not from the nearest point of the "wrong" layer, as the via would be the point we trace from. - When placing via is active, show before placing, if it could be placed at the place where the mouse points to - show footprint that is selected with arrow keys in the browser - option to have certain symbols not beeing "annotation reset"

PLEASE do not add new features! Make those existing features work effciently without bugs! And please dont alter the appearance of the buttons over and over again.

Ian you will earn my greatest gratitude if you decide to add gEDA/PCB import. There are some old and important projects that I really need to get into KiCad. I could not get any of the existing scripts to work. Plus gEDA is not running on modern Linux distributions any more. So I hope you decide to fill those boxes. :D