Re: [Kicad-developers] How do we envision Pad Stacks?

[ja...@veith.net]

On 11.06.20 17:16, Wayne Stambaugh wrote:

I thought at one time we had an initial proposal document written for
pad stacks but I cannot seem to find it.  I thought it was either Orson
or Tom who wrote it but maybe I'm remembering this wrong.  If not, we
need to create one to make sure we have it well defined before any
implementation can be done.


When I asked Orson some weeks ago, he responded that there is no
such document

Expedition supports a separate pad stack library what contains drills,
drill symbols, THT and SMD pads and combinations of them (pad stacks). 
All footprints link to this padstacks similar Kicad link from symbol to 
footprint. This way padstacks are not defined in footprints what allows 
footprints to  change pads automatically (wave, reflow or other needs). 
Once placed, the footprint link to padastack can be altered to special 
design needs


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Project Setup for Development and Beginner recommended beginner work on eeschema

[ja...@veith.net]

Hello Rico,

compiling for Ubuntu stable 18.04 seems to be most easy and I started my 
first patch without using any IDE. Others have VS code , QT creator or 
Eclipse in use. Eclipse was also the recommendation of Seth Hilbrand. I 
also have the CDT running with GCC hello world including the debugger. 
Unfortunately successful kicad project import met further obstacles for 
the moment why I still compile in terminal command line and cannot use 
advanced IDE power


Janvi

On 14.04.20 21:07, Rico Schmitt wrote:

Dear Devs,

I would like to join your efforts in further developing Kicad. I would 
like to ask what kind of IDE or general development environment you use 
for developing Kicad. Maybe someone can offer his setup as a starting 
point, I would love NOT to spend to many hours getting everything set 
up. I am working on Linux (mostly Debian based). I am able to build the 
latest release.


My long term goal is to improve Eeschema sheets. So I am looking for 
some smaller fixes that have to be done in this area to get into the code.


Thanks
Rico

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Padstack support #2402

[ja...@veith.net]

V6 Roadmap indicates "initial technical spec drafted" by Orson
Is this document anywhere online for reading ?  

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Cryptic characters in source

[ja...@veith.net]

On 08.02.20 22:39, Brian Piccioni wrote:
Perhaps I misunderstand but I don't see anything (screen grab from 
notepad++ on Windows 10)


Sorry - did not recognize that its always EOL -
somebody simply opened in a Windows editor ...



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] How to access the fbp sources

[ja...@veith.net]

To access the fbp sources I tried to install the wxFormbuilder for 
Ubuntu 18.04LTS. As there seems neither distro version nor Debian 
packages I used the github repo with v3.9.0:


>sudo apt install libwxgtk3.0-dev libwxgtk-media3.0-dev meson
>sudo apt install libcanberra-gtk-module libcanberra-gtk3-module
>git clone --recursive --depth=1 
https://github.com/wxFormBuilder/wxFormBuilder

>cd wxFormBuilder
>meson _build --prefix $PWD/_install
>ninja -C _build install

went through without errors. After this, invoking
./_install/bin/wxformbuilder generates numerous errors:

19:08:05: Error: Could not set current working directory (error 2: No 
such file or directory)
19:08:05: Error: 
/home/jv/wxFormBuilder/_install/lib/wxformbuilder/libforms.so: cannot 
open shared object file: No such fil
19:08:05: Error: Error loading library 
/home/jv/wxFormBuilder/_install/lib/wxformbuilder/libforms 

19:08:05: Error: Could not set current working directory (error 2: No 
such file or directory)


libforms.so is available in path 
_install/lib/x86_64-linux.gnu/wxformbuilder while wxFormBuilder searches 
path without x86_64-linux.gnu. Any help on how to go on appreciated.


Thanks,
Jürgen




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Back annotate references from PCB

[ja...@veith.net]

> On 01.12.19 21:06, Jon Evans wrote:


1) 
some cases (critical controlled impedance, small BGA decoupling, etc) we 
may decide during layout that it is best to switch to the "high density" 
(minimal pad size) version of the 0402.


This is alternate footprint. Implementation by reference in new symbol 
library would allow things like automatic footprint change for reflow / 
wave soldering if component pushed from front to back. Schematic is not 
affected and no need for backannotate. Data source should be symbol 
library rather than pcb. Allow workflow using footprints not defined in 
approved symbol lib is a further source for individual issues in the 
design. Kicad also always need generic workflow but avoid discussion 
about atomic lib here.
2) similarly, we might have a design with 0402 passives that we 
determine during layout needs to switch to 0201 in some cases to make 
proper layout possible.


This is a device change what affects schematic BOM. Probably it is 
useful to have a device change dialog for devices using same inherited 
drawable symbol (typical value change) whith/whithout copper changes. 
For intuitive use I would search this dialog in eeschema and it could be 
similar useful than text editor search by regex. For exmaple 
change all pullup resistors from 4k7 to 1k.


Today typical 4k hi-res screens are in use for CAD. I always have the 
schematic on the screen beside PCB while routing. No need for reverse 
workflow. A powerful cross-probe highlight zoom/pan  is the better boost 
of productivity in this stage of the design. Agree with Brian, also my 
circuits have many changes while routing. This may be diffrent for 
contract PCB people what receive "ready" schematic from designer. PCB is 
another view of your schematic what always gives you diffrent insights 
and reasons not to follow the classical waterfall design workflow.


IMHO back annotate is usefull in 4 cases what all belong to the nice to 
have category. Same things can be done already without backannotation 
with only little manual work.


1) Pin swap: For example between the 2 inputs of a 7400 NAND gate
will only change 2 pin numbers in schematic. Using uC/FPGA with visible 
PinNames, these should also change using back annotation.


2) Gate swap: For example swap 2 (of four) NAND gates of a 7400
will change 2x3 pin numbers in schematic. Although Eagle and other Ecad 
is doing so, I would prefer not using A,B,C,D,E suffix to reference.  We 
see the gate position inside IC by pin numbers and all gates including 
power box may have the same reference. Warnings for unused gates is a 
matter of schematic DRC.


3) Intercomponent swap. For example if you have several 7400 in your 
circuit and change two gates between diffrent components. This is 
similar to 2 but reference change (not only reference suffix) is required.


4) geo or partitial manual renumber

Assume all, backanotate only needs Reference, PinNumber, PinName.
I dont see any disadvantage if backannotation writes changes to file(s) 
what are executed later on demand like forward annotate or netload is 
now. This allows to try several swap configurations and then 
backannotate after decision for best variant is done.


best
Jan

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Back annotate references from PCB

[ja...@veith.net]

> On 22.11.19 21:12, Wayne Stambaugh wrote:

What Jeff described is the simplest case.  Where things really get
interesting is when you start sharing schematic files between projects.


Imho multiple use of a schematic requires separate instance data. 
Similar problem for the recently discussed variant/do not fit where

the values are different instead reference designators. Could imagine
both, e.g. a filter circuit used multiple times for different frequency
whether its on the same board or not. If used outside project, the 
project file could link instance data to schematic. Penalty is not 
having complete schematics in one file.




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] suggestion: draw text selection as simple rectangle

[ja...@veith.net]

On 20.11.19 20:37, Jonatan Liljedahl wrote:

  If yes, does it need to be configurable?


We had a color blind fellow designer. The schematic entry
(ACE-Plus) derived its colors from the library
- no chance for user setup ...

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [Discussion] PCB Calculator: Resistor calculator

[ja...@veith.net]

Recently there was a user with similar wish in the forum
for E12 parallel/serial calculator (what is your lower tab ?)

You will find another code for E values <12 on my web page as E96
from the IN30TCD page are already available with many values:

www.veith.net/e12calc.htm


>Seth Hilbrand wrote
>
>Then, you should have the option for 2x/3x/4x resistors in the 
>calculation result.


Combinations with two/three/four considered automatically if its worth.
See the description on how the formats for parallel serial are shown.
Should be easy to convert from Java to C. I rarely used for inductors 
and capacitors as they have typical higher tolerance what normally does 
not need exact match for the design. Would prefer a separate tab for 
filter design and AC calculations


rgds
Janvi


On 13.11.19 20:23, kaj...@cox.net wrote:

Dmitry,

I find your English perfect and your calculator a good start.

Personally, I use calculators when I cannot do something in my head 
easily or fast.


On that note, in the upper block, I would recommend:

- also calculate second component when first value and result are given

- given voltage across components, calculate power dissipation, voltage 
across each, etc.


- how about adding combination circuits RC, LC, LCR, etc. and 
calculating corner frequency, impedance, etc.


You can search online electronic calculators to find more ideas to make 
it more advanced.


That would be my wish list. Thank you for considering.

Martin

On November 13, 2019 at 12:54 PM Dmitry Rezvanov 
mailto:dmitry.rezva...@yandex.ru>> wrote:



Hello, everyone.

Now I'm working on the resistor/capacitor/inductor calculator.
In the attachment - very preliminary version of the design.
Upper block - for calculating result from two known values.
Lower block - vice versa, for finding the configuration and values of
two components for target value.
Please, don't hit me too hard, I did this while crossing the Ballmer Peak.
I really hope for feedback and opinion.

P.S. And sorry for my bad English. English isn't my native language, so
I swear, I try to work on it every day.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net 


Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Should gerber files in protel format use same name? (PATCH?)

[ja...@veith.net]

Alexander Shuklin  schrieb:
>>"they demand drill files to be same precision as gerbers (for example
>>4:5). Can you confirm that proper Excellon format should be 3:3 
>>precision"


jp charras  schrieb:
>Excellon files have no way to specify the format actually used
>in files.

As I have access to commercial Gerber Tool at work, I recently did some 
tests for importing diffrent Excellon format precision into GerbView:
7+8 digit formats (seems possible but no standard (???) and) are not 
detected automatically by GerbView. 6 digit formats 3.3 or 2.4 or 4.2 
always import correct with or without leading zero supression or 
step Another thing I found, that the (old header) G81 FMT1 
instruction generates error message while G05 FMT2 equivalent does not 
(but both behave well). If anybody is interested in test file data I can 
dig for them or generate new test files



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Do Not Fit

[ja...@veith.net]

pls allow some comments to Olivers do not fit suggestions. We recently 
stumbled accidently above Kicad after quarrels with commercial tools and 
found its push & shoove capabilites are a remarkable and motivating 
feature.


Experience shows, that the „do not fit“ feature is much more complex. 
Unfortunately PCB do not have interface standards for contract assembly 
and soldering in comparison to Gerber for etching or CNC drilling. 
Therefore cooperation with non black belted contract manufactureres is 
always painful. For this reason, we run our own SMD pick & place machines.


„Do not fit“ components are nothing else than changed value properties 
of components. E.g. variant A has no R100 and value of R100=DNF, variant 
B with R100=1k, variant C with R100 =4k7. Shure this decision is in the 
responsibility of the design engineer. To decide this inside schematic 
will end up in complex variant manager tools. Variants become instances 
of schematic. This raises more questions what beginners hardly 
understand. Finally we recognize that variants are not only a question 
of assembly but of component purchasing, stock keeping and so on. This 
leads to the blueprint V6 library format discussion what is much more 
complex.


I dont offer contract assembly and all designs are own and drawn by 
diffrent CAD. After struggling years with Excel BOM and insufficient CSV 
macros like many other contract manufacturers, we started 
https://sourceforge.net/projects/cad2board/ Up on today Qt is only 
compiled and tested for windows, cannot read Kicad input and output 
format is limited to our Heeb pick & place machines  (today ATN 
innoplacer Berlin) So is of little consequence for Kicad but solution 
works comfortable here. We have complex variant managers but do not use. 
Variant decisions are executed at latest possible moment. Eg. the reel 
with CPU crystals run unexpected empty and there are a few more boards 
to populate. It is one click to take out this component from project 
temporarily without saving and continue assembly if I decide to complete 
the few crystals by hand while board testing. Same way we manage all 
variants and „DNF“ components permanently inside pick2place project 
files. They can be merged any time with updates from full size BOM. To 
understand Olivers efforts: The disadvantage of this solution is a 
possibly inaccurate schematics not representing all details of any 
specific variant.


Happy routing
Janvi

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp