X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20210112; t=1679071490;
	h=mime-version:message-id:in-reply-to:date:subject:to:user-agent
	:references:from:from:to:cc:subject:date:message-id:reply-to;
	bh=Hjuz0xuRkAZ+LIso175rFrqpFCy23Glp8Ahdq8WHxLU=;
	b=fPF6fIdlma6KPtwEh7wnKChZ9nQoM6GvNBCcTp4srXtaRiMlDbSK113aurlElU4Jn0
	wLFYjYTJYWO1+Z+1coOmLjZvygZ2s3t9JzVpqO9SolpTJlabdJXJt0lhCjPXlyQXEcVN
	hQfDitvRDcpMd4GX0Sh9GZfwABlNa9s3eTCERXuDalVpbt6qFF0HaVRapiLifVkC3EsB
	uBGvydpeSzFDS++B/YRxiXSG3nKs+USZvpg/r0ZGfeEP/wxa3jqvoT2c1AX87cB+/E+w
	Gg+Ht690m5eSnZ/5DPB6dpI50l+mkDnWUWRL8vx4GkwLg+LYP/IsfDdjgtGwxnkFkR66
	e3SA==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20210112; t=1679071490;
	h=mime-version:message-id:in-reply-to:date:subject:to:user-agent
	:references:from:x-gm-message-state:from:to:cc:subject:date
	:message-id:reply-to;
	bh=Hjuz0xuRkAZ+LIso175rFrqpFCy23Glp8Ahdq8WHxLU=;
	b=YoOPDhbhD31SYrc4O28B6DlvaV+CmhSW86+/MZwaj+wuV9DtJjimwnFD/5i2RGHjgf
	SQUZgM3avLn6AZS5cWP2oCsZDpODY+u0ewIxd7xvL3I6bhDeTKnEfHNvop81FW6X7Pvo
	/SPCT9XkLv6z+h6l3CDUWQAVDbhE1BMjrC/N77jRpRCFW4c4MklPMmSOeXP5ZIddjtxA
	0Yftkg9A64bhPNd7YOVoCHCuc55UaXqfsbompOdIRY/3U3/Zt5spphDRKsy5KEUTeZHP
	LYv7lhPrnY4r0daP0wF9gyYf7j2MUgrkDWPU1CVBoEMOZn/uWxYEqrxjajT2iekhb7nW
	ok2w==
X-Gm-Message-State:	AO0yUKXu5PblCLH+zJmPURilW7b/YZ0G6qioYwE7IeAFt7EG/S5VgsU5
	M2ZUG9JLwdX8+GhdsIqd3Z2lI+YCKas=
X-Google-Smtp-Source:	AK7set/sR4ag0PC1/be6qLuUQN4zdyBIhgj1LCkmkFKrKzZ9bsgcrHrlqSUT5OHHmgqgWLVF6HCLPg==
X-Received:	by 2002:ac2:5fd0:0:b0:4e8:3ea0:cf37 with SMTP id q16-20020ac25fd0000000b004e83ea0cf37mr5168820lfg.34.1679071489150;
	Fri, 17 Mar 2023 09:44:49 -0700 (PDT)
From:	"vzh (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Google-Original-From:	vzh <vzh AT lepton>
References:	<20230314184208 DOT 7302885F61C5 AT turkos DOT aspodata DOT se>
User-agent:	mu4e 1.8.11; emacs 28.2
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] tools for sub pcbs
Date:	Fri, 17 Mar 2023 19:33:56 +0300
In-reply-to:	<20230314184208.7302885F61C5@turkos.aspodata.se>
Message-ID:	<87y1nvz5s0.fsf@lepton.mail-host-address-is-not-set>
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Hi Karl,

"karl AT aspodata DOT se [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> writes:

> Since it is not complicated to make heirarchical
> design in lepton/gschem I want to make the same
> thing happen at the pcb side.
>
> E.g. let's say I want to do something like
>  https://aspodata.se/git/openhw/boards_arm_aspo/stm32f100_styrkort/
> which is constructed of six blocks:
>  system power relay analog serial and 1w_bus
> and the power block is made up of a few sub sheets for different
> voltages.
>
> Now I'd like to take a ready made pcb design for 3.3, 5V and the 12V 
> switch block and load them into the pcb sub design for power.
> That is doable, you just have to add the refdes source sym to all
> components within the sub design and since this is a two layer 
> prototype design I might want to place the components on both sides
> to save space.
>
>   For theese uses I've made
> https://aspodata.se/git/openhw/bin/get_sub_pcbs.pl
> to collect all sub pcb designs and adjust their refdes'
> and https://aspodata.se/git/openhw/bin/pcb_ch_side.pl
> to place a specific pcb design on the other side of the board.
>
> Theese programs is just for testing out the possibilities and see what 
> is possible. And now I would like to see if there is interests in 
> getting them integrated into lepton/gschem/pcb to enhence the pcb
> workflow with hierarchical design.
>
> I guess that pcb_ch_side.pl is preferably rewritten as a pcb plugin
> so that anyone can turn a buffer so one can apply it on the "other" side
> of the board, so I might need some help guiding me rewrite it.
>
> I don't know the best way to handle the collect sub pcb parts.
> One could possible enhance {lepton,g}sch2pcb so it does the sub pcb 
> collection, just as it collects the footprints today; or one could
> similarily change the import schematics function in pcb, suggestions
> are welcome.

We suffer from the same problem: the lack of testing and collaboration.
You may read it as: "lack of man power in our (particular) projects".
I'm still slowly working on lepton side to refactor sch2pcb and make it
(maybe much) simpler.  At least, to make code testable.  Though better
would be to replace it with something more capable.

Please see here:

https://github.com/lepton-eda/lepton-eda/pull/1008

Best regards,
  Vladimir

- Raw text -