MEP EP#257: Viciously Different Creams

<h4><a href="https://macrofab.com/blog/mep-ep257-viciously-different-creams">MEP EP#257: Viciously Different Creams</a><br></h4><h4>Parker</h4> <ul> <li aria-level="1"><a href="https://www.reddit.com/r/electronics/comments/kbbous/accidentally_ordered_some_0201_capacitors_instead/" target="_blank" rel="noopener">The ole ordered a 0603 and it was metric instead resulting in an 0201 imperial chip component.</a> <ul> <li aria-level="2">0.6mm x 0.3mm = 0.024” x 0.012”</li> <li aria-level="2">0201 imperial chip size only size that does not match the actual size <ul> <li aria-level="3">Imperial 0201 is 24mil x 12mil... not 20mil x 10mil like the name implies</li> <li aria-level="3">Imperial 0603 is 60mil x 30mil </li> </ul> </li> <li aria-level="2">0603 metric is the only standard metric size that has the same size code as an imperial one!</li> <li aria-level="2">Does anyone actually use the metric sizing for chip components? </li> </ul> </li> </ul> <h4>Stephen</h4> <ul> <li aria-level="1">Hardware v software - Features and their impact <ul> <li aria-level="2">Hardware <ul> <li aria-level="3">needs a lot of motivation to make a feature. It is slow and deliberate. Removing features is a big deal</li> <li aria-level="3">features by default cannot break the device unless extreme cases are encountered</li> </ul> </li> <li aria-level="2">Software is "easier" to flip the switch on features. <ul> <li aria-level="3">Have to consider all the ways this will break things.</li> </ul> </li> </ul> </li> <li aria-level="1">Kicad - Panelization <ul> <li aria-level="2">Moving between layers has hotkeys - yay</li> <li aria-level="2">Middle mouse now by default pans and wheel is zoom</li> <li aria-level="2">Snap to points is huge</li> <li aria-level="2">Creating arrays actually creates arrays <ul> <li aria-level="3">There are pluses and minuses to this.</li> <li aria-level="3">Ref Des is maintained!</li> <li aria-level="3">Changes to one board are not copied!</li>