Added Microchip MIC4605-xYM gatedrivers #53

Open
M3gaFr3ak wants to merge 6 commits from M3gaFr3ak/master into master
M3gaFr3ak commented 2020-04-01 21:18:55 +00:00 (Migrated from github.com)
Digikey Links: https://www.digikey.de/product-detail/en/MIC4605-1YM/MIC4605-1YM-ND/5049499?utm_campaign=buynow&WT.z_cid=ref_octopart_dkc_buynow&utm_medium=aggregator&curr=eur&site=us&utm_source=octopart https://www.digikey.de/product-detail/en/MIC4605-2YM-TR/576-4463-1-ND/4505750?utm_campaign=buynow&WT.z_cid=ref_octopart_dkc_buynow&utm_medium=aggregator&curr=eur&site=us&utm_source=octopart Parts exist in multiple packaging sizes with the same package (both are soic, but are available as TR, TR2 etc; is all the same component) EDIT: apparently github added my latest commits to the PR?!
issus commented 2020-04-04 13:50:55 +00:00 (Migrated from github.com)

Did you want the Maxim parts in the library? Will they meet requirements?

Did you want the Maxim parts in the library? Will they meet requirements?
M3gaFr3ak commented 2020-04-04 13:57:01 +00:00 (Migrated from github.com)

At the moment they reference the wrong footprint (the one from the related issue)

At the moment they reference the wrong footprint (the one from the related issue)
M3gaFr3ak commented 2020-04-04 15:55:08 +00:00 (Migrated from github.com)
Fixed the footprint. Maxim items: https://www.digikey.com/product-detail/en/maxim-integrated/MAX15062AATA-T/MAX15062AATA-TCT-ND/5022173 https://www.digikey.com/product-detail/en/maxim-integrated/MAX15062BATA-T/MAX15062BATA-TCT-ND/5022174 https://www.digikey.com/product-detail/en/maxim-integrated/MAX15062CATA-T/MAX15062CATA-TCT-ND/5022175
issus (Migrated from github.com) reviewed 2020-05-13 17:00:23 +00:00
issus (Migrated from github.com) left a comment

TDFN package should have some silkcsreen on the body line to show these pads belong to the same part.
Footprint has a bottom courtyard layer, which isn't necessary.
Courtyards are more than 0.2mm from the extents of the pads/body.

Schematics in general: should not have a footprint linked.

SCH - DRIVER - GATE - MICROCHIP MIC4605-1YM.SchLib
Symbol can be made smaller, with a 1 grid line gap between VDD/HI as there is with LI/VSS. Lineup HI/HO and LI/LO to show the 'flow' through the IC.

SCH - DRIVER - GATE - MICROCHIP MIC4605-2YM.SchLib
See above. I'd line up PWM with HS and compress the symbol down

SCH - POWER - SWITCHMODE - MAXIM MAX15062AATA.SCHLIB
SCH - POWER - SWITCHMODE - MAXIM MAX15062BATA.SCHLIB
VOUT should be top right. - VOUT, gap (or 2 gaps), LX.
VCC should probably go on the lower right side, or below EN/UVLO, as it's just a bypass pin and not a voltage input pin.

SCH - POWER - SWITCHMODE - MAXIM MAX15062CATA.SCHLIB
See above. FB pin goes below the LX pin with at least 2 gaps.

TDFN package should have some silkcsreen on the body line to show these pads belong to the same part. Footprint has a bottom courtyard layer, which isn't necessary. Courtyards are more than 0.2mm from the extents of the pads/body. Schematics in general: should not have a footprint linked. **SCH - DRIVER - GATE - MICROCHIP MIC4605-1YM.SchLib** Symbol can be made smaller, with a 1 grid line gap between VDD/HI as there is with LI/VSS. Lineup HI/HO and LI/LO to show the 'flow' through the IC. **SCH - DRIVER - GATE - MICROCHIP MIC4605-2YM.SchLib** See above. I'd line up PWM with HS and compress the symbol down **SCH - POWER - SWITCHMODE - MAXIM MAX15062AATA.SCHLIB** **SCH - POWER - SWITCHMODE - MAXIM MAX15062BATA.SCHLIB** VOUT should be top right. - VOUT, gap (or 2 gaps), LX. VCC should probably go on the lower right side, or below EN/UVLO, as it's just a bypass pin and not a voltage input pin. **SCH - POWER - SWITCHMODE - MAXIM MAX15062CATA.SCHLIB** See above. FB pin goes below the LX pin with at least 2 gaps.
This pull request can be merged automatically.
You are not authorized to merge this pull request.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin M3gaFr3ak/master:M3gaFr3ak/master
git checkout M3gaFr3ak/master
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AllSpice-Demos/Altium-Celestial-library#53
No description provided.