delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2018/02/01/07:42:52

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Thu, 1 Feb 2018 13:30:33 +0100
From: Josef Wolf <jw AT raven DOT inka DOT de>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] geda and sub-distribution unt planning?
Message-ID: <20180201123033.GA11796@raven.inka.de>
Mail-Followup-To: Josef Wolf <jw AT raven DOT inka DOT de>, geda-user AT delorie DOT com
References: <20180131142114 DOT GE9539 AT raven DOT inka DOT de>
MIME-Version: 1.0
In-Reply-To: <20180131142114.GE9539@raven.inka.de>
User-Agent: Mutt/1.5.24 (2015-08-30)
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

First of all, I'd like to thank to all who responsed. Very much constructive
and informative content there. I'm not replying to the responses separately
because I don't want to pollute the list with lots of short mails with little
context. Instead, I try to summarize the responses and keep the thread compact.

First, I want to clarify what kind of output (besides the schematic) I'd like
to generate:

1. Drawings, how the components are located on the hat rails. Something like
   http://www.treesoft.de/fileadmin/bilder/zusatzmodule/verteilungsbau-assistent/120-Screenshot-Verteilerbau-Aufbaupl%C3%A4ne.jpg
   Maybe with some more detail.

2. Drawings of terminal blocs. Something like this:
   https://knx-user-forum.de/filedata/fetch?id=1163441&d=1512064723

3. Labels for the components and terminal blocks

I'm not sure whether PCB would be the right tool. After all, routing is not a
primary concern here. Every netlist should have its own layer. netlists with
more than two connections can be frobidden and (automatically?) split into
multiple netlists by using something like
https://www.phoenixcontact.com/assets/images_ed/global/web_gallery/pic_gall_a_0076793_int.jpg
IMHO, this should be possible as a postprocess step without invoking PCB at
all.

For most parts, placing components could be done by specifying the hat rail
and the position on it and an attribute. Something like hat-rail=F3-R4-T5 for
the fifth position on row 4 in field 3.
Netlists could also contain such an attribute for inserted terminal blocks
when the net is automatically split (as mentioned above).


But how to handle parts which load constraints onto other parts like phase
rails:
https://www.hager.de/modulargeraete/leitungsschutzschalter/anschlusstechnik-fuer-modulargeraetesystem/kdn163a/931829.htm
You don't want such parts to be visible in the schematic. But on the assembly
drawing, such parts are very important. Could this be handled by some
attribute+postprocess?


The https://qelectrotech.org project looks very promising, since:

1. it seems to know about special properties of PE, N and such things.
2. it already contains many of the components for hat rails.

But qelectrotech seems to cover only schematic and postprocessing seems to be
very limited. Unfortunately, almost all of the project is in french which
sounds pretty much like klingon to me =:-().

-- 
Josef Wolf
jw AT raven DOT inka DOT de

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019