Provide a reference table displaying what nozzle size to use for what commonly used package
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Hi, i took me a while to figure out (not really correctly) what nozzle to use for what package size, it would be good to provide some reference table in docs so every new user don't need to experiment/ask/search what to use. Since using incorrect nozzle will lead to higher pick up failure rate, i think this info should be provided somewhere in setup page like "Running First Job" section or so...
Example:
| Imperial | Metric | Suggested nozzle |
|---|---|---|
| 0201 | 0603 | Not supported |
| 0402 | 1005 | n045 |
| 0603 | 1608 | n045 |
| 0805 | 2012 | n14 |
| 1206 | 3216 | ??? |
| 1210 | 3225 | ??? |
| 1812 | 3246 | ??? |
| 2010 | 5025 | ??? |
| 1512 | 6332 | ??? |
| SOIC16 | - | n24 |
(Filled in nozzle sizes are my wild guess so pls correct those since i have no idea...)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the “Running First Job” setup page linked in the issue and review the existing documentation structure for where a nozzle reference belongs. Verify the supported package sizes and appropriate nozzle choices with project sources before adding the table; done means the setup documentation gives new users a reliable reference without guesswork.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100