← Back to team overview

kicad-developers team mailing list archive

Re: Dealing with multifunction pins (Symbol)

 

Augusto,

Most of this is going to be addressed during the next development cycle
when the new symbol library and schematic file format are implemented.
At the moment, there is no plan at this time to allow for resizing
symbols in schematics.  Since symbols will be embedded in the schematic,
resizing will be possible.  Thank you for your input.

Cheers,

Wayne

On 1/30/2018 10:01 AM, Augusto Fraga Giachero wrote:
> Hi,
> 
> I've been designing schematics with some stm32 parts using the standard
> Kicad libraries, and a lot of these microcontrollers has 10+ functions
> multiplexed in each I/O pin. In the standard library the symbols
> displays all possible configurations available to each pin, I understand
> the motivation of this choice (not having to refer to the datasheet
> every time you want choose an I/O for some specific functionality), but
> this results in very large symbols occupying the page.
> 
> I've come with a idea (which probably isn't new) to deal with this problem:
> * You can select what functions you will use from a list for each pin
> and only that will be displayed in the schematic;
> * You can then resize the symbol accordingly directly in the schematic;
> * While this wouldn't require any modification to the library symbol
> file format as the description string of each pin already carries all
> the necessary information, the .sch file format would probably be
> changed and would not have backwards compatibility.
> 
> This may not be easy to implement as with the way eeschema handles
> symbols today and the issues I've cited above, I would like hear about
> your suggestions.
> 
> Thanks,
> Augusto Fraga Giachero.
> 
> 
> _______________________________________________
> 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


Follow ups

References