You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.
I need help in order to create footprint from here.
ds:
By SMD_chip_package_rlc-etc.py script and editing size_resistor.yaml , pads created are not as datasheet recommends.
Also by editing smd_chip_resistors_smd.csv and running script, footprint created was ok but has main differences from other resistors.
How should i proceed?
Edit my confusion is, should this be named as R_2818_7146Metric as current resistors are with the default pad layout presented ,
and R_Shunt_Vishay_WHSP2818 with _ViaReception and _PadReception ( maybe? )
So 3 footprints total.
The text was updated successfully, but these errors were encountered:
I think there is no need for a _Via?? variant. That is something the pcb-designer should take care of.
You already found the correct generator. The pad-sizes it outputs are different from manufacturer recommendations because it builds them according to the IPC spec.
Are there other 2818 shunts available from other vendors? If yes, we should start to compare them.
A quick search only resulted in this: https://www.seielect.com/catalog/sei-hcsm.pdf
Currently I think a generic R_2818_7146Metric is the way to go.
Hi everyone.
I need help in order to create footprint from here.
ds:
By
SMD_chip_package_rlc-etc.py
script and editingsize_resistor.yaml
, pads created are not as datasheet recommends.Also by editing
smd_chip_resistors_smd.csv
and running script, footprint created was ok but has main differences from other resistors.How should i proceed?
Edit my confusion is, should this be named as
R_2818_7146Metric
as current resistors are with the default pad layout presented ,and
R_Shunt_Vishay_WHSP2818
with_ViaReception
and_PadReception
( maybe? )So 3 footprints total.
The text was updated successfully, but these errors were encountered: