Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

Adding QFN-56-1EP_8x8mm_P0.5mm_EP4.3x4.3mm #476

Merged
merged 7 commits into from
Jan 3, 2020

Conversation

ki5libs
Copy link
Contributor

@ki5libs ki5libs commented Dec 31, 2019

Adding QFN-56-1EP_8x8mm_P0.5mm_EP4.3x4.3mm

@codeclimate
Copy link

codeclimate bot commented Dec 31, 2019

Code Climate has analyzed commit 9ba7b21 and detected 0 issues on this pull request.

View more on Code Climate.

@evanshultz
Copy link
Collaborator

  1. Please link to page 40 since that's the package drawing.
  2. Give tolerances as shown in the datasheet. For example, pkg_width: 7.85 .. 8.0 .. 8.15.
  3. Make sure you're entering the values from the table in the document. The pad size values in the script aren't even the nominal values.
  4. The biggest issue is that you're using the wrong YAML file. Put the package info into https://github.com/pointhi/kicad-footprint-generator/tree/083b79e039dbef88f4b39ce28bf0a064d957311c/scripts/Packages/Package_NoLead__DFN_QFN_LGA_SON/size_definitions (under the qfn folder in this case). Then generate the footprint using kicad-footprint-generator/scripts/Packages/Package_NoLead__DFN_QFN_LGA_SON/ipc_noLead_generator.py.

@evanshultz evanshultz self-assigned this Jan 3, 2020
@ki5libs
Copy link
Contributor Author

ki5libs commented Jan 3, 2020

Hi @evanshultz

sorry for inconvenient, I really confused the old and the new generators. Hope it's much better now. I'm only not sure about thermal vias. Datasheet tells that it should be 0,3-0,4mm diameter, but for me it looks not the drill size but the whole ring diameter. May be I'm not right, but other case it looks too big.

@ki5libs
Copy link
Contributor Author

ki5libs commented Jan 3, 2020

Another issue - I've got errors during Travis checking:
https://travis-ci.org/KiCad/kicad-footprints/builds/632431076?utm_source=github_status&utm_medium=notification
And I have no idea how to fix it.

@evanshultz
Copy link
Collaborator

Thanks!

  1. Note 2 on page 40 indicates that lead width min should be 0.15mm. So why does that not match the table. It's confusing to me. Do you know how to reconcile that?
  2. 0.2mm will be fine. That's the common size in this library. We aren't strictly following the datasheet footprint because we're using our script.
  3. Those errors are, unfortunately, normal. Our check script hasn't learned the newer way the script builds footprints with thermal vias.

Also note that I asked for an updated screenshot in the footprint PR.

@ki5libs
Copy link
Contributor Author

ki5libs commented Jan 3, 2020

I've updated screenshots. But unfortunately I couldn't say anything about Note 2. I didn't understand what it tries to tell so I just took table values. By the way dimension X on page 41 (pad width) is 0.28mm whereas generated value is 0.25 mm.

@evanshultz
Copy link
Collaborator

Thanks for the screenshots.

Let's adjust the terminal width min to 0.15mm and add a note in the YAML file stating the table and note have different minimum values. Then re-generate the footprint and we may be good to merge.

Our script generates footprints according to IPC 7351 based on the package drawing. It does not know or care about the recommended footprint.

@ki5libs
Copy link
Contributor Author

ki5libs commented Jan 3, 2020

Done. But looks like it has no influence to the result of generation

@evanshultz
Copy link
Collaborator

I'm not surprised there is no change, but glad you checked it. Thanks!

@evanshultz evanshultz merged commit 7f99c05 into pointhi:master Jan 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants