If you don’t see your favorite electronics surplus store on the list, please add it! Several of these “junk shops” close every year due to rising rents and competition online. Anything we can do to keep them in business will benefit the maker community. One way to do this is by making sure that folks know that these resources exist, and this is where I hope the wiki will help.
I want to express my sincere gratitude to everyone who has been contributing to the wiki. In particular, thanks for making it one of the best directories of electronics surplus stores on the web!
I am pleased to announce that the MightyOhm Wiki is now online and open to the public.
While there isn’t a ton of content yet, my hope is that the wiki will become a useful means to share information and resources relevant to the site. At the moment, there are pages for electronics vendors, hardware/software tools, and PCB manufacturers.
Another page I have been working on for a while is the surplus directory, which lists surplus electronics stores around the country. If you have a favorite surplus goldmine in your area, please create an account and add it to the wiki!
When you finish a PCB design, you typically use the CAM export function of your layout tool to generate a set of gerber files to send to the PCB manufacturer. To avoid errors in the finished board, it’s usually a good idea to review the files before you click send.
Enter gerbv, a free, open source gerber viewer that is available for many platforms, including Debian and OS X (via fink).
I recently upgraded to version 2.0 (I was using the really outdated version 1.0 on Macports) and I am really impressed by the improvements in the GUI and overall usability.
Let’s say you are designing a printed circuit board in Eagle, and you need to place a component that you’ve never used before. In Eagle, before you can use a new component, you need a land pattern, a schematic symbol, and a mapping between them to fully define the part. Often, you can search through Eagle’s included libraries and find what you need (or something close enough). But what if that fails?
The symbol and pin definitions are usually pretty easy – just copy the datasheet. The hard part is the land pattern: the collection of copper traces, soldermask openings, silkscreen, and other features that define the part on the PCB.
To come up with a land pattern, you usually have a few options:
Someone else may have done you a big favor by creating a part definition and uploading it to the Eagle library directory. Caveat: Use it at your own risk. Surface mount parts tend to be particularly hard to use right out of the box – often someone else’s land pattern won’t even pass your DRC. Whose process were they using, anyway??
Look through the datasheet for the part to try and find a recommended land pattern. (Good luck! Increasingly these are not included, but may be somewhere else on the manufacturer’s website. Google is your friend!)
Take a guess based on the geometry of the part, assuming you have a mechanical drawing or a physical sample somewhere.
Skip 1-3 and use an IPC-7351 land pattern generator.
IPC-7351 is a standard for printed circuit board land pattern designs. The standard attempts to, well, standardize land patterns to try to discourage every PCB designer from having his or her own custom library of land patterns. IPC takes known good land patterns and combines them with accepted manufacturing tolerances to produce a land pattern that will work for most people most of the time. Increasingly you will see references to IPC-7351 in datasheets instead of a land pattern drawing, so access to the standard is becoming more important over time.
The calculator is somewhat tricky to use but if you click the right buttons you can get something like what is shown below (click to enlarge).
X and Y are the dimensions of the recommended pads for an 8-lead Thin SOT-23, which happens to be the package for the LT3464.
With this information, you can return to Eagle and create a land pattern for your device. PCB Matrix will also sell you premade Eagle libraries, but from their site it was not clear how much they cost. Based on their other products, my guess is several hundred dollars and a yearly maintenance contract – I’ll draw my own, thanks.
Unfortunately, the calculator is Windows only, so Mac guys like me need to use VMware Fusion or similar to use it. Can someone create a web version, please?