Re: [Kicad-developers] Migrating old designs best practice

2017-12-06 Thread Diego Herranz
Thanks for the tip. I'll use it to check schematics wiring. Diego On Sun, Nov 26, 2017 at 6:53 PM, jp charras wrote: > Le 26/11/2017 à 19:15, Diego Herranz a écrit : > > It's interesting that only happen if I rescue symbols. > > > > Anyway, thanks for the help and I'll keep an eye on properly w

Re: [Kicad-developers] Migrating old designs best practice

2017-11-26 Thread jp charras
Le 26/11/2017 à 19:15, Diego Herranz a écrit : > It's interesting that only happen if I rescue symbols. > > Anyway, thanks for the help and I'll keep an eye on properly wired schematics > to see if all goes OK. > > Thanks, > Diego To seen if your wires are OK, try to create a netlist: The firs

Re: [Kicad-developers] Migrating old designs best practice

2017-11-26 Thread Diego Herranz
It's interesting that only happen if I rescue symbols. Anyway, thanks for the help and I'll keep an eye on properly wired schematics to see if all goes OK. Thanks, Diego On Sun, Nov 26, 2017 at 5:23 PM, José Ignacio wrote: > This might be related to the wire optimizer/junction management code.

Re: [Kicad-developers] Migrating old designs best practice

2017-11-26 Thread José Ignacio
This might be related to the wire optimizer/junction management code. Eeschema used to allow degenerate connections like that, where an L was superimposed to a wire, connecting into a junction. On Sun, Nov 26, 2017 at 4:59 AM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > Please ignore

Re: [Kicad-developers] Migrating old designs best practice

2017-11-26 Thread Diego Herranz
Please ignore the previous attachments. They should have been these. Thanks. On Sun, Nov 26, 2017 at 10:55 AM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > Hi, Nick > > Changes like: (- is removed, + added) > > -Wire Wire Line > - 12550 700 12600 700 > > -Wire Wire Line > - 12700 700

Re: [Kicad-developers] Migrating old designs best practice

2017-11-26 Thread Diego Herranz
Hi, Nick Changes like: (- is removed, + added) -Wire Wire Line - 12550 700 12600 700 -Wire Wire Line - 12700 700 12700 700 Wire Wire Line - 22250 14500 22250 11600 + 22250 9200 22250 14600 - Wire Wire Line - 22250 9200 22250 14600 - Wire Wire Line - 22700 750 15350 750 Wire Wire Line -

Re: [Kicad-developers] Migrating old designs best practice

2017-11-25 Thread hauptmech
On 26/11/17 04:00, Wayne Stambaugh wrote: On 11/24/2017 05:01 PM, hauptmech wrote: On 25/11/17 02:14, Wayne Stambaugh wrote: This is *the* fatal flaw with the cache library.  User's assume it is stale symbols or a temporary copy.  It is not.  It is a snapshot of the current library symbols link

Re: [Kicad-developers] Migrating old designs best practice

2017-11-25 Thread Nick Østergaard
What modifications are made to the wires? 2017-11-25 21:28 GMT+01:00 Diego Herranz : > Hi, > > Related to this, I'm migrating an old design (~2 month old nightly) to the > current master. First I faced some problem with '/' characters ( > https://lists.launchpad.net/kicad-developers/msg31705.html

Re: [Kicad-developers] Migrating old designs best practice

2017-11-25 Thread Diego Herranz
Hi, Related to this, I'm migrating an old design (~2 month old nightly) to the current master. First I faced some problem with '/' characters ( https://lists.launchpad.net/kicad-developers/msg31705.html) but there have been some improvements since then so I'm trying again. When opening the schema

Re: [Kicad-developers] Migrating old designs best practice

2017-11-25 Thread Wayne Stambaugh
On 11/24/2017 05:01 PM, hauptmech wrote: > On 25/11/17 02:14, Wayne Stambaugh wrote: >> This is *the* fatal flaw with the cache library.  User's assume it is >> stale symbols or a temporary copy.  It is not.  It is a snapshot of the >> current library symbols linked to the symbols in the schematic.

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread hauptmech
On 25/11/17 02:14, Wayne Stambaugh wrote: This is *the* fatal flaw with the cache library. User's assume it is stale symbols or a temporary copy. It is not. It is a snapshot of the current library symbols linked to the symbols in the schematic. It gets refreshed every time the schematic is sa

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread hauptmech
On 25/11/17 03:26, Rene Pöschl wrote: On 24/11/17 12:38, hauptmech wrote: On 24 Nov 2017 10:52 pm, "Rene Pöschl" wrote: On 24/11/17 04:47, hauptmech wrote: I can confirm unconnected wires. It may be worth noting that I did not preserve the -cache.lib file when I archived the design. I also

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread Rene Pöschl
On 24/11/17 12:38, hauptmech wrote: On 24 Nov 2017 10:52 pm, "Rene Pöschl" wrote: On 24/11/17 04:47, hauptmech wrote: I can confirm unconnected wires. It may be worth noting that I did not preserve the -cache.lib file when I archived the design. I also had an issue with an old asymmetric dio

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread Wayne Stambaugh
This is *the* fatal flaw with the cache library. User's assume it is stale symbols or a temporary copy. It is not. It is a snapshot of the current library symbols linked to the symbols in the schematic. It gets refreshed every time the schematic is saved. Once you delete this file or keep an o

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread Nick Østergaard
But still, you are required to save the cache file if you want portability. The decision to use the word cache was probably not so good, because it makes people think they should not back it up. But this is how it works, so pull it out of your ignorefile. Lets be pleased that the new schematic for

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread hauptmech
One the one hand, yes, if there is a cache file you can take advantage of the fact that it is a stale copy of the old parts. On the other hand, since caches are, by definition, temporary copies of data, they don't get versioned or archived in my projects. (The kicad libraries, and binaries, were t

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread hauptmech
On 24 Nov 2017 10:52 pm, "Rene Pöschl" wrote: On 24/11/17 04:47, hauptmech wrote: > I can confirm unconnected wires. It may be worth noting that I did not > preserve the -cache.lib file when I archived the design. > > I also had an issue with an old asymmetric diode footprint having its > anode

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread Rene Pöschl
On 24/11/17 04:47, hauptmech wrote: I can confirm unconnected wires. It may be worth noting that I did not preserve the -cache.lib file when I archived the design. I also had an issue with an old asymmetric diode footprint having its anode and cathode reversed when I used it in a new design. If

Re: [Kicad-developers] Migrating old designs best practice

2017-11-24 Thread Nick Østergaard
This would haven been resolved if you kept the cache lib, IIRC. Den 24. nov. 2017 4.48 AM skrev "hauptmech" : > I can confirm unconnected wires. It may be worth noting that I did not > preserve the -cache.lib file when I archived the design. > > I also had an issue with an old asymmetric diode fo

Re: [Kicad-developers] Migrating old designs best practice

2017-11-23 Thread hauptmech
I can confirm unconnected wires. It may be worth noting that I did not preserve the -cache.lib file when I archived the design. I also had an issue with an old asymmetric diode footprint having its anode and cathode reversed when I used it in a new design. If pin numbers in the library got swa

Re: [Kicad-developers] Migrating old designs best practice

2017-11-23 Thread Wayne Stambaugh
I stand corrected. I just looked and pin numbers are checked by position so swapped pins should get rescued. What isn't rescued is pins that changed length which is a bit surprising since that would possibly leave unconnected wires. I'm not sure why it was done this way but I guess I'll have to

Re: [Kicad-developers] Migrating old designs best practice

2017-11-23 Thread Nick Østergaard
Maybe I am mistaken then. 2017-11-23 13:21 GMT+01:00 Wayne Stambaugh : > On 11/22/2017 11:02 PM, hauptmech wrote: > > When opening an old design I noticed that the C and R symbol pin nodes > > changed position (I'm guessing other symbols as well), breaking the > > schematic. Did the people who ch

Re: [Kicad-developers] Migrating old designs best practice

2017-11-23 Thread Wayne Stambaugh
On 11/22/2017 11:02 PM, hauptmech wrote: > When opening an old design I noticed that the C and R symbol pin nodes > changed position (I'm guessing other symbols as well), breaking the > schematic. Did the people who changed these symbols have a plan for > migrating old designs? Is the 'rescue' supp

Re: [Kicad-developers] Migrating old designs best practice

2017-11-22 Thread Nick Østergaard
The cache library and the rescue dialog should take care of this. 2017-11-23 5:02 GMT+01:00 hauptmech : > When opening an old design I noticed that the C and R symbol pin nodes > changed position (I'm guessing other symbols as well), breaking the > schematic. Did the people who changed these symb

[Kicad-developers] Migrating old designs best practice

2017-11-22 Thread hauptmech
When opening an old design I noticed that the C and R symbol pin nodes changed position (I'm guessing other symbols as well), breaking the schematic. Did the people who changed these symbols have a plan for migrating old designs? Is the 'rescue' supposed to handle this? ___