Best way to use datasheet field in symbol and footprint

[AdriZ]

Hi,
My library is done with a different symbol for each part number.
Where do you recommend to fill the datasheet field: in the symbol, the footprint or both?
If both, is there a possibility to synchronise them?

Thanks,
AdriZ

[retiredfeline]

Symbol. Footprints are often common to a lot of devices so you would end up with a footprint for every model if you put the datasheet field there.

[AdriZ]

OK, thank you.
For the moment the only footprints that are shared between component have the same datasheet (one resistance family for example).

If I put the datasheet only in the symbol, will it be accessible from the PCB Editor and from the PDF assembly file?

[paulvdh]

In KiCad, the schematic is always the primary source source for information. Symbols fields added to schematic symbols are also visible inside the PCB editor. If you view the properties of a footprint in the PCB editor, there is a globe next to the text string and it opens the datasheet when you click on it, but it does not have a direct hotkey as in the schematic editor.

[AdriZ]

That is just perfect!
Thanks a lot!

[paulvdh]

Another method is to:

1. Select a footprint on the PCB. Due to cross probing, the schematic symbol that corresponds to the footprint is also selected.
2. Make the schematic editor the active program ( hover and scroll wheel or click on the title bar).
3. In the schematic editor, press the d hotkey to show the datasheet.

[AdriZ]

Useful trick! Thank you.

[Piotr]

@AdriZ

For the moment the only footprints that are shared between component have the same datasheet

You must be at the beginning of library building. You should expect that you will have for example:

• many totally different ICs all in SO8 (different OpAms, RS485 driver, DCDC converter, analog swiches, and many more),
• many Wurth ferrite beads with separate datasheet for each,
• Schottky and standard diodes in SMA footprints,

and more.

[AdriZ]

You’re right. But it also depends on what we impose on ourselves.
I could say one footprint for one common datasheet (I won’t do that because the datasheet only on symbols solved my issue).

In my precedent company we did one partnum = one symbol = one footprint.
It has some advantages: it is very tidy, you can adjust a footprint for a specific component without impacting the other ones, it is less error-prone. The drawback is, obviously, more work.