X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com Date: Wed, 24 Feb 2016 11:53:38 +0100 From: "Smilie (smilie AT posteo DOT de) [via geda-help AT delorie DOT com]" To: geda-help AT delorie DOT com Subject: Re: [geda-help] little Question.... Message-ID: <20160224115338.01a77f66@debian> In-Reply-To: <79675336-4E8E-4312-A7AD-F9569FACD2E9@noqsi.com> References: <20160222220125 DOT 1dd46469 AT debian DOT olsr> <20160223140911 DOT 022af707 AT debian> <20160223185632 DOT 29ed2a79 AT debian> <79675336-4E8E-4312-A7AD-F9569FACD2E9 AT noqsi DOT com> Organization: Individuum auf blauem Planet X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u1OArlPh015807 Reply-To: geda-help AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-help AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Thanks for puzzeling. (: It is my dirty English and my confused head. Sorry for that. The way to make a proper product have so much possibilities for fails, slips, bloopers, adversitys, misfortunes, misadventures and mishaps, because that i will go every time strait forward. Not forward than sideways and than finally forward but under no circumstances i will go backward. But why you do that? """ The pins2gsch script converts a "tab-separated value" (TSV) file into a pseudo-schematic. """ What ist that? Or is this only my misunderstanding? Yes, i search a possibility to go forward, because i make so much faults if the day is long. I spend so much time for controlling and correction. I search for a possibility to have a more intuitive tool and fore more automatism. The first idea was to attach to the connector a symbol like an io.sym with attribs like a net=GND and a additional name like netname, pinname or pin-alias. With this input i want to go in a shell-script. --------------------------------------------------------------------------------------- #For now a make is so: gnetlist -g geda *.sch -o out.net Connector=`cat out.net | grep =CONNECTOR | cut --delimiter=' ' --field=1 | sort -n` echo "Connector "$Connector | sed 's/ /\n,/g' > out.csv for conn in $Connector; do touch tmp.csv echo "" >> out.csv echo $st >> out.csv echo "PIN ,Beschreibung" >> out.csv IFS=' ' for conn1 in `cat out.net | grep $st | grep -v device= `; do IFS=':' var1=true for conn2 in st1 ; do if var1; then var1=false Name=$st2 else IFS=',' for conn3 in $conn2; do pin="" pin=`echo $conn3 | grep $conn | sed "s/$conn//1" | tr '\n' ' ' | sed 's/ //g'` if ["$pin" != "" ] ; then echo $pin","$Bezeichnung >> tmp.csv fi done fi done done ... ... ... --------------------------------------------------------------------------------------- the result ist something like this: --------------------------------------------------------------------------------------- Steckverbinder ,CONN1 ,CONN2 ,CONN3 ,CONN4 ,CONN6 ,CONN7 ,CONN8 CONN1 PIN ,Beschreibung 1,M_EOC 2,M_DOUT 3,M_DIN 5,M_SCLK 6,Vee 7,GND 8,GND 9,Vdd CONN2 PIN ,Beschreibung 1,P_mg2_s+ 2,P_mg2_s- 3,P_mg4_+ 4,P_mg2_- 5,P_mf2_s+ 6,P_mf2_s- 7,P_mg4_+ 8,P_mf2_- 9,P_mg3_s+ 10,P_mg3_s- 11,P_mg4_+ 12,P_mg3_- 13,P_mg4_s+ 14,P_mg4_s- 15,P_mg4_+ 16,P_mg4_- 17,T_m2_+ 18,T_m2_- 19,T_m3_+ 20,T_m3_- 21,T_m4_+ 22,T_m4_- CONN3 PIN ,Beschreibung 1,unnamed_net21 2,unnamed_net22 3,unnamed_net23 4,unnamed_net24 5,unnamed_net25 6,unnamed_net26 7,unnamed_net27 8,unnamed_net28 9,unnamed_net29 CONN4 PIN ,Beschreibung 1,unnamed_net21 2,unnamed_net22 3,unnamed_net23 4,unnamed_net24 5,unnamed_net25 6,unnamed_net26 7,unnamed_net27 8,unnamed_net28 9,unnamed_net29 CONN6 PIN ,Beschreibung 1,A_INT3 2,A_MOSI 3,A_MISO 4,A_RESET 5,A_SCK 6,+5V 7,PGND 8,PGND 9,Valve/Heater+ CONN7 PIN ,Beschreibung 1,P_ag1_s+ 2,P_ag1_s- 3,P_af1_+ 4,P_af1_+ 5,P_af1_s+ 6,P_af1_s- 7,P_ag1_- 8,P_af1_- 9,T_ah1_- 10,T_ah1_+ 11,T_ah2_- 12,T_ah2_+ 13,T_av1_- 14,T_av1_+ 15,T_at1_- 16,T_at1_+ 17,Valve/Heater+ 18,Valve/Heater+ 19,Valve- 20,Heater- CONN8 PIN ,Beschreibung 1,PGND 2,PGND 3,PGND 4,PGND 5,+5V 6,+5V 7,Valve/Heater+ 8,Valve/Heater+ 9,CAN1H 10,CAN1L 11,CAN0H 12,CAN0L 13,Valve/Heater+ 14,+3.3V_CAN1 15,+3.3V_CAN0 ----------------------------------------------------------------------------------------------- Am Tue, 23 Feb 2016 19:26:26 -0700 schrieb John Doty : > On Feb 23, 2016, at 10:56 AM, Smilie (smilie AT posteo DOT de) [via > geda-help AT delorie DOT com] wrote: > > > Am Tue, 23 Feb 2016 08:03:14 -0700 > > schrieb John Doty : > > > >> On Feb 23, 2016, at 6:09 AM, Smilie (smilie AT posteo DOT de) [via > >> geda-help AT delorie DOT com] wrote: > >> > >>> Ah, i see. > >>> > >>> > >>> i have connected a line from GND.sym direct to one of the GND-Pins > >>> and the other GND-Pin works also. > >> > >> What are you trying to do here? > > > > > > I want do write a script for automatic generation a spreadsheet with > > all pin-names for any connector. I try to generate it from the > > netlist-stuff. > > But it does not work if i have only one potential. > > The test with netname also does not work. > > OK, I’m puzzled. The IO symbols don’t represent physical pins on > connectors. They represent logical connections within a set of > schematics. What are you doing with them? > > For connector pin lists, I work in the other direction, generating a > pseudo-schematic from a table of pins rather than generating a table > from a schematic. See > http://www.gedasymbols.org/user/john_doty/tools/pins2gsch.html > > > > > > > >> > >> What these symbols do is to give a net a name. That’s all. Naing > >> the net connected to a pin GND connects it to all other nets named > >> GND. If you have more than one such symbol, and the names don’t > >> match, gnetlist will choose the first one it sees. > >> > >> Is your net connected to anything? > >> > >>> > >>> It is a bug? > >>> I broke my head.... > >>> > >>> Thanks for helping me. > >>> > >>> > >>> > >>> > >>> Am Tue, 23 Feb 2016 10:20:16 +0000 > >>> schrieb "Peter Clifton (petercjclifton AT googlemail DOT com) [via > >>> geda-help AT delorie DOT com]" : > >>> > >>>> Sorry I'm not currently able to check this out, but I recall that > >>>> gnetlist has (in the past, and possibly currently), not worked > >>>> properly in the case where only IO symbols with net=....:1 > >>>> attributes (but no actual components). > >>>> > >>>> My recollection is not that clear, but try adding a dummy > >>>> component (perhaps a resistor), with one pin connected on your > >>>> schematic where you join PGND and your IO sym. Don't need to > >>>> give it a footprint (but you will probably get complaints from > >>>> pcb about the missing component). > >>>> > >>>> If this makes the connection appear in pcb, let us know - and > >>>> I'll see if anyone working on the gEDA side of things has any > >>>> ideas for a fix, or better work around. > >>>> > >>>> I have an idea that I've made some boards with netlists that > >>>> featured Rdummy1 Rdummy2 etc.... and I think I was working around > >>>> the same issue you describe. > >>>> > >>>> Peter > >>>> On 22 Feb 2016 21:03, "Smilie (smilie AT posteo DOT de) [via > >>>> geda-help AT delorie DOT com]" wrote: > >>>> > >>>>> Hallo Guys, > >>>>> > >>>>> i have a problem with my net or netname-attributes. > >>>>> > >>>>> I have a connector with some io-1.sym's with attributes like > >>>>> this: net="abcd:1". > >>>>> Than i have a PGND.sym connected to the other io-1.sym's. > >>>>> They have also the attribs net="abcd:1". > >>>>> > >>>>> I wont tho have a connection between the connector and the pgnd > >>>>> but there is no connection in pcb. > >>>>> > >>>>> What is wrong? > >>>>> > >>>>> Thanks for helping me. > >>>>> > >>> > >>> > >> > >> John Doty Noqsi Aerospace, Ltd. > >> http://www.noqsi.com/ > >> jpd AT noqsi DOT com > >> > >> > > > > > > > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > >