Multiple schematic pages in one project

[PaulieT]

Hi Group,
Is there a way to create multiple page schematics without the project being hierarchical?

Thanks,
Paul

[Rene_Poschl]

Kicad currently has no support for flat multi page schematics.

The workaround is to have a root page that includes your pages and use global labels to connect everything up.

[PaulieT]

Thanks Rene,

Is there anything that describes how to do that?

Paul

[maui]

Multiple sheets at same hierarchy level

I’ve been unsuccessful in finding a good solution to making clean schematics on eeschema when number of connections increase. I haven’t found this covered on the forums. At work, I use schematics where a single component with 1000+ pins won’t fit on a single page. (Large components span multiple schematic symbols.) On KiCad, I can’t seem to fit even relatively simple designs. On KiCad I use hierarchy, but I find that I often can’t fit a level of hierarchy in one page. I’ve thought hard abo…

[Rene_Poschl]

Not very hard to be honest. (For completely flat schematics as requested by you. The problem starts if you want to mix hierarchical design with flat design at any level of the hierarchy.)

In your main schematic add a new hierarchical sheet and give it a suitable name.
Switch into it (double click does the trick) and design what you want in this page. Take care that you use global labels where you need to connect to other pages. (global labels are power symbols and of course the global labels found in the right toolbar)

to get back out of the sheet use either the hierarchy navigator or the “get out of the sheet” tool found in the top toolbar.

Repeat this for every page you need. You can even add as many sheets as you want right at the start.

[PaulieT]

Thanks Rene,

I’ll give it a try.

Paul

[Rene_Poschl]

@Russ

hierarchical design with flat design

Any good documentation or websites for understanding these two methods?

I don’t know of a good website explaining these in general. KiCads docu naturally explains the hierarchical approach. But i doubt they explain why one would want to use it.

---

My personal view:

Hierarchical design makes it possible to have multiple levels of abstraction in the same schematic. The root sheet shows the system level. Every level below gets into more details for each of the submodules shown in the level above.

---

A flat design simply is a design that lacks any hierarchical elements. You simply have multiple pages that connect to each other via so called labels.

---

Both options have their merits. I personally favor the hierarchical approach. (One of my best examples of the use for hierarchical design is this: https://github.com/TERA-TU-Graz/BatteryManagement_2017/tree/master/HW/projects/fennek_2017_18/BMS/measurement_and_balancing/bms_board_V6-1__12s_fennek2017)