-
Notifications
You must be signed in to change notification settings - Fork 430
Populate IC sockets by default #388
Comments
So the idea is to populate the sockets with the IC. @poeschlr said that it is better to have a whole model with the socket+ic because adding the IC model will need to shift it up (considering the Z axis) and it is not a good practice to store this kind of data there. What do you think? So, adding on top of the @poeschlr idea, if the whole model with the socket+ic is a good idea, the footprint should reference both socket and socket+ic models keeping the preview of the first disabled. |
I agree with your original idea: I understand that we generally want our 3D models to not require an offset (a model should be made to fit its footprint, after all), but adding a second model reference with a Z offset to make an IC fit in a socket seems fine to me. The only problem I could imagine would be that if we change the height of the socket model, the footprint would have to be changed as well to update the offset of the IC model. But that seems unlikely, and it wouldn't be a big issue anyway since the symbols and footprints in question are script-generated. In short, I don't see a problem with your original idea, I see a problem with KLC forbidding it. |
@easyw could i get your expert opinion on that? |
@poeschlr |
Looking at this wishlist item I think we would have to revise the KLC for offset of the "extra elements" (dips for sockets, batteries, cards etc) since these might make sense to reuse for multiple batteryholders etc |
I still think that sockets should come with the IC considering the 3D model. I agree that the schematic and BOM will be better (complete) if you add both symbols on the schematic. My thought process it something like this:
The offsets rule should be an exception for sockets. For the end-user, everything will be there by default. If he doesn't want the IC on top of the socket it is just a matter of disabling it on the footprint properties. |
Referencing an idea here KiCad/kicad-footprints#866. but I still think that it is an issue for the footprint repo.
The text was updated successfully, but these errors were encountered: