And for that particular case you will also need to add the missing pins as one of the components has more of them. (KiCad has no way to assign multiple pads to a single pin)
Of course, I understand personal preference but I need to underline one thing, this is actually not automation. Everything is under your control, version control systems just helps you to apply your style with some neat tools. Otherwise you have control over your projects. (Think about KiCad itself, without a version control system, it would be a mess to work on it)
Also, I guess you always work on your own projects as the only developer/designer? Because I’ve seen a lot of mistakes with this copy/rename method in the past that I can not count. With version control systems at least you can catch the crack early and fix it. Otherwise a lot of design could be disappear in the void. I saw a lot of lost souls 
)
Cheers,
That’s true. I need to adopt on new system and not system to adopt me.
You did that only once when you create part.
…but still get it big enough to be readable. But hope that hieararhic sheet works here. In eagle is unusable. I don’t know if there is better. For example if you mage graphic equiliser you have 8 same circuits (filters) and mainboard. But that 8 circuit have different component values. I didn’t try but I assume that I will need to make 8 subcircuits.
There are missunderstanding. For example pic16F88 have C2OUT/TOCKI/AN4/RA4 pin. I like to have only RA4 visible on symbol but to be able to somehow list all other functions(C2OUT/TOCKI/AN4)
Yes I’m the only developer. I like to have folder for project and inside that the subfolders for revisions. So if I open even the file explorer and open the folder I see how many and what versions I have. I think using git or svn that is not possible.
But just now seems that there are another issue with that. If I have project with two boards and schematics seems that is not allowed to have in same folder. For example remote control. It’s one project but have two devices one for sending and one for receiving. Seems that I need to put them in separate folder.
The current official stand point is that each KiCad project has one PCB.
Some time ago I did a short experiment with a completely fictive multi board project, just to see what happens.
This was over a year ago, and unfortunately I did not make notes.
I think what I did was:
- Create a few KiCad projects in the same directory, One project for each PCB.
- Create a “root” project, and add the schematic files of the other projects as hierarchical sheets into the root project.
This way it seemed to be possible to work on the complete schematic in the “root” project, use the hierarchy to switch between the different sub projects, and do ERC checking over the whole project.
When you want to work on a single PCB, then you can close Eeschema and double click on one of the other projects to make it active.
It all seemed to work, but it was a short test and there may be dragons about.
In 5.99 this is possible with one subsheet file, 8 instances and sheet variables. See New string replacement options for kicad assets.
For the layout you would need the Replicate Layout plugin, Replicate layout: Action plugin, but unfortunately it doesn’t work with 5.99, only with 5.1 AFAIK (@MitjaN can give details about that).
Are you going to print it to paper? If not, you could as well choose A3 or something similarly large page layout and fit more into one page. And even then it may be possible to print to A4 or Letter. But as was said, using hierarchical sheets may be a good solution because it makes you to split the schematic into functional parts and may enhance readability.
2 Likes
I did try example but I can’t got it how its worked and probably there are something broken for 5.99. If I open PCB I see dividers as expected. If I open SCH and hit F8 the dividers are updated and both came same. Actually I don’t get how Resistor plus/minus is linked to child.
You don’t need to. Think a version control system as a time machine. You can browse all of your revisions with a single click, command etc. I don’t think you always need all of your revisions at the same time. You would just need it to check, compare or go back to something. If you need a certain revision, you always can export that revision. But again, I don’t think you would need it anyway.
You don’t need to rename anything, or copy them into the right folder. Everything flows like you develop. You just make sure it is recorded at important points, like right before PCB production.
This way you can keep some of your fancy unrealistic design trials as separate branches. Who knows maybe you would want to continue it some day?
Never needed two PCB’s in a project. I designed some products even with 7 different PCB’s and never needed one. They are always different PCB projects.
If they are different form factor PCB’s with completely same schematics, you can have the schematics subsheet as like a git submodule and then use different PCB projects sharing the same schematics. Think it like an Eagle module.
The question is what project is.
I call RemoteControll as project. And that project have Transmitter and Receiver. In Kicad seems that I need to make two projects for that. One is RemoteControll.Transmitter and other is RemoteControll.Receiver
I finally got understand how they work. But seems not possible to make BOM from schematic. (but it’s ok from PCB)
For me these are two subprojects of a parent project. Since the schematics designs will be different, it wouldn’t hurt to make them separate projects. (Like I said, shared subsheets also could be used)
KiCad does not need to manage the connection between those projects, other than shared components as libraries. The rest should be a topic of some other system, like a Project Management or ERP/MRP.
These are all personal preferences and I’m glad we have tools to satisfy them.
Hi
I have the same thoughts. Although he Kicad Libs are extremely good, I only work from my own checked Libs. I use this “https://www.compuphase.com/electronics/kicadlibrarian_en.htm” to copy from an existing Kicad to my own library, after checking and/or altering. If it doesn’t exist I will generate footprint using program from here “pcblibraries.com”. I also have multiple components for resistors so I can embed the manufaturer/supplier number ie 1K,0402, 2K,0402 etc.
Actually there is a bug (other than the BOM thing), it’s no wonder you didn’t get it working at first. I’ll report it.
I look that video and like it. But I think that doesn’t work on 5.99. (Can’t try didn’t managed to compile on linux)
I think, you just need to have a faith in the git/svn/ and other SCCM, use it and see all your problems could be done in so many ways include your own ways. There so many people and industries use them, and your issue isn’t rare. You will find it out. Otherwise, you would hate these tools. 
Hi
I was using on nightlies earlier in the year, so assumed it was still OK. I am on W10, so can’t help with Linux.
Paul
I still don’t know if in eagle you can have pin numbers at schematic. For LM7805 I have never show pin numbers but for microcontroler always. If I know that it is 44 pin case and see that pin I am interested is 35 I can easily find it. If I would have only its name finding it seems for me much more complicated.
Me too. And except one, old big schematic (about 1995) all others fit in one page (sometimes crowded).
I have two KiCad installations at two PCs. Working one with only my libraries in list (I install KiCad with all libraries). Reference one with default installation. At this second, before each installation I delete everything (meens including User\AppData\Roaming\kicad (Windows, I don’t know how in other systems). I use this second one for example when need to check something to report a bug. After having some my symbols I have no need to copy other symbols from KiCad libraries. When I need a footprint I find it at second PC and then copy right file at first PC, then rename and modify according to my needs.
See https://gitlab.com/kicad/code/kicad/-/issues/6408 which was fixed by @JeffYoung. You can now try again (with the next nightly build which includes that commit). The BOM issue must be tested separately.
EDIT: there’s another bug in BOM generation. I should remember to report it later…