kicad-developers team mailing list archive

["mitjan696-ubuntu@xxxxxxxxxxx" <mitjan696-ubuntu@xxxxxxxxxxx>]

 Hi!
This would also enable fully automated PDN analysis (e.g. a voltage regulator could have property "V_OUT" with value "5.0" on the output pin. An IC connected to this net would have the property "I_IN" with value "0.2" and property "V_IN_MIN" with value "4.5". When PCB would be done then outside tool could parse pcb and sch files and get all required info to do the PDN - at least the DC part of it).

    On Friday, 4 January 2019, 19:56:10 CET, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:  
 
 I'm willing to add properties which are already defined to pins.  There
has been talk about adding about adding electrical constraints for
advance ERC testing to symbols but that will not be part of the v6
implementation of the new file format.  It's going to be a lot of work
to implement the features we've added to v6 so this would be outside the
scope of the first version of the new file format.  I'm certainly open
to discussing this as part of a later version of kicad.

On 1/2/19 3:52 PM, mark.vandoesburg@xxxxxxxxx wrote:
> One thing I would like to have is user defined pin properties, just like
> the part properties. Currently I use the BOM generator to generate a
> software header file from the netlist. I have to use an additional file
> to store the information I need. It would be nice if this information
> can be stored in the symbol. This could be any kind of information, for
> example bank number or clock region for an FPGA. Or driver strenght/speed
> setting for a microcontroller.
> 
> regards,
> 
> Mark.
> 
> Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
> 
>     I have updated and published the symbol file format[1] for comment.
>     Hopefully there isn't too much to change.  The only thing to really
>     finalize is the internal units.  The initial concept was unitless but
>     the more I think about it and discuss with other developers, it makes
>     more sense to use units for the following reasons:
> 
>     1. It's easier to visualize in your head how the symbols on a given page
>     size will layout.
> 
>     2. Converting from other file formats (Eagle, Altium, etc) will be
>     easier since most if not all of them have a defined unit.
> 
>     I'm thinking 10u (or possibly 100u) will make a good internal units
>     value.  Once we nail down the units, I will update the file format
>     document accordingly.
> 
>     Please keep in mind that this is the symbol library file format document
>     so things like constraints belong in the schematic file format.  I will
>     be posting the schematic file format as soon as I finish updating it.
> 
>     Cheers,
> 
>     Wayne
> 
>     [1]:
>     https://docs.google.com/document/d/1lyL_8FWZRouMkwqLiIt84rd2Htg4v1vz8_2MzRKHRkc/edit
> 
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     Post to    : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     More help  : https://help.launchpad.net/ListHelp
> 

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