ID:	5647
From:	pc...@cuvoodoo.info
Date:	Mon, 16 May 2022 12:25:41 +0200
Subject:	[pcb-rnd] RFC: multi-sheet netlist
replies:	5648 from Gabriel Paubert <pa...@iram.es> , 5649 from rn...@igor2.repo.hu , 5651 from ka...@aspodata.se

--aYQiniFx0v78ja+N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

gEDA/gschem and lepton-eda/schematic support hierarchical design (with multiple/sub-sheets).
this is explained in http://wiki.geda-project.org/geda:faq-gschem?s[]=gtag&s[]=sch#can_gschem_do_hierarchical_designs_with_sub_sheets and an example is shipped with these software in gTAG.sch.

I tried for the first time this feature because may schematic became too large, unreadable (on one sheet), and parts are just repeated (e.g. multiple ports).
but I have an issue with how netlist are handled with subsheets.
I attached a basic example.
In the tEDAx netlist, components have a unique refdes, using the "_sheet-refdes_/" prefix/path.
pcb-rnd treats the name as a string, and does not have the concept of hierarchical design/name.
thus when I reuse a component (with the same refdes) on multiple sheets (because the connection of one of the pins only makes sense in this sheet), then pcb-rnd imports multiple times the footprint (one for each name, which includes the path).
this component re-use also applies to multi-part symbols (e.g. dual-opamp).

the same prefixing is applied to netnames.
thus the GND symbols (using the GND netname) are not interconnected across sheets (this also applies to the provided gTAG.sch example).

a kind of solution is to use pins on the symbol for the subsheet, and use and INPUT/OUTPUT symbols in the subsheet.
but doing it for all nets (e.g. VCC/GND) just clutters the sheet symbol, and kind of goes against the concept of defining/using netnames.
plus, this does not solve the refdes reuse issue.

for now my solution is to use a netlist intermediate (pcb-rnd will not import the schematic directly), and have a script that removes all prefix/path.
but maybe I just did not understand correctly how to do proper hierarchical design (I really did not find a lot of documentation).
maybe tEDAx can be extended to integrate the concept, or interpret the '/' in the name.
any comments/suggestion is welcome.

--aYQiniFx0v78ja+N
Content-Type: application/x-bzip2
Content-Disposition: attachment; filename="subsheet_examples.tar.bz2"
Content-Transfer-Encoding: base64

QlpoNjFBWSZTWbFDzXEABXz/lN4wBIBQY//ivqnfiP/v/+oEQAAIgAhQBH7kRUpRJVDQJUoD
QyZA0aaAABoaNANAAAaHDTTIxGE0wEMAmmEYJiZDTI0NAJEQhqmNUAeo000AAPSaAGg0DT0g
HDTTIxGE0wEMAmmEYJiZDTI0NAFSSaaTSAJppiaZQyaZMQZAG1GIPUaGnrR8H4uzt+/ljhjf
aVVUrWQjn8GJMEe6M4KUlZIPfymv8U3nuM6/2CA4aD462MJU4tc+422www5Yp4enXcLEGJcJ
MSlXPriHmwNTQLmaRa9eIvxyOdFkfLHvd7aXViLWlEqllS0lKSpSihSqiH3VaoPL3Mujy25K
q+CYokvCoVSSimcj56jHmWMqF+VTYpfZqyi9VehhF1tV6W2OQ1HAiAbE2AxsZJBEDGDaQKrQ
NmQxhp3Tf8+7V9ty6UzyMCtnYiLOpXIOOsyAzu4zsNZv/vzEpXM2ZnfL5qtG4Zj3fFThjvKi
2tpG7HH0NZDL1dSLTEjSTBrrDBNjYmMZAqyIkYIJlwK0LJKlqiqhF1JFqKgzLSG7no8DnasT
GtNGVbc+pTYphdlY0xRrTYupqzkgZgTGFsqLKkFipW1MskgeBNQN5GxDR8p+qyNkVGOCMkbs
1NYu4GcZ4LReX+zpeOnZ4sAzSiTTCyTcssnRasYRpIziGOb0WjRSGaB6VNE54NJAmohZlWqC
LKhgMWptqMctizlXMzZNZ4jPEd6+mnsNZap6G3eVKXNrapTgazbVTO6MYZ3uUXjSMXVFFLzO
KLUjJQm5TKkNL2kU0sSbEKqqqMwUHCxYtFfRCLUgbDLKktGJBcGSwbWLlDRk0TfIsUxaVUxi
MYkxrQYy92cpF2Jdpf+vIczq8Mdv9xYpdY6PQdfn83WqJ+Z7Ds29I4nY3R9Z+h8YyPDu7C/t
efOyi6GMu223DRBAxkg4SHoAgg+gH1uDBuDLky05I9x6nRGUdHpdv0Dqc0aPfHD2/HaV9xyX
oFGk+4sDk/KWlHeNqUhpSkRnUz1NuqrjVYocfE34Ott2cGXEd2TBnFpHqRvycBqfgO5/2fQc
M429I5uOcAriM5RyPqekpq9cZRyb1YedU4R7UnPZ/mRSP90jqpkU14zKfk7s26Xkst5HftGy
o14ulGRk5bydY4o3AmkdKEBBYJVEKkUBVdAkfID0vKq9YFpxVECyEQwXG83TfVJ8k5OQyPFr
zTdijvmWxJRzNSsW2KP4vGN9qxNczeGy0eEW7uxm+EVuTJ4zfLd83YjHVz9xvodOqTyJP/F3
JFOFCQsUPNcQ

--aYQiniFx0v78ja+N--

Mailing list archives : pcb-rnd

Navigation