Rationale behind setting part height, not package height

[JW]

Hi all, I can't quite get my head around this but I'm sure there must be a good reason.

What is the rationale behind setting the component height, in the part, rather than the package?

I've seen it before where packages have the same footprint, but different height - so I understand why you want to be able to set the part height, but to me a more logical approach is to set a height in the package, and allow a height to be set in the part. If the part height is left empty, then it'll pick the height from the package.

Or maybe this functionality is already there, and I'm just not seeing it, quite the possibility!

[mark maker]

Agree. Same can be said for the Speed %.

I would even go so far and say these should  only be settable on the Package. If you have different package heights, name them differently.

_Mark

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/7ec3b49b-9ada-4e59-8b24-d1d3146b23fan%40googlegroups.com.

[JW]

Re speed, yes - spot on. I've had a couple of cases where large packages shift on the nozzle under high acceleration and need to be slowed down, but same problem - end up needing to do this at part level, not package level.

I'll raise a detailed issue in Github later on.

[vespaman]

While I can see the benefit of a having height on both part and package, I don't think forcing this into only the package is a good thing. 

There will be a lot more packages to manage, and also one have to create/find packages when e.g. substituting a component for a similar. Especially worrisome for 0402/0603 etc.

Also adding more data into the package name means that also height needs to go onto the OCR labels, which is perhaps not interesting in most cases.

- Micael

[Michael Anton]

The commercial machines I've used consider a different height to be a different package.  It's much nicer to relate the package type to a given part number, rather than having to worry about setting the height for each part on the PCB.  I can't think of a good reason that one would want to do the latter.  Now, if the height came from the specified package type initially, but could be overridden, then that might be handy.