A lot of the board houses out there including Seeed and ITead studios have a fixed size for circuit boards before the price goes up. A one-inch square board costs the same as a much larger 5cm x 5cm board, making panelized PCBs a great way to get more boards for the same amount of money. Trying to panelize a board in Eagle with copy and paste is a chore without the right tools, though, so we’re happy to see a great panelization tutorial from [Victor].
To panelize one of his boards for a PCB order, [Victor] used one of Eagle’s User Language Programs to duplicate the part names on the additional boards. After that, it was a simple matter of running a CAM job to generate the necessary Gerber files.
Of course once the boards arrive, you’ll have to cut them apart from each other. This can be done with everything from a Dremel to a hack saw to a metal shear, but we’re wondering what other Hackaday readers are using to cut up PCBs. Leave a note in the comments with your preferred method of depanelization.
Ever so slowly, we’re inching towards a world of Internet-based electronic design tools. The state of these tools, including Upverter and other cloud-based solutions, hasn’t been all that great until now; with any new piece of schematic capture and PCB layout software, the libraries will be woefully inadequate in the beginning. This is about to change, because circuits.io is now allowing Eagle libraries to be imported.
As you may well be aware, Eagle is the de facto standard for homebrew and hobbyist schematic capture and board layout software. Even though Eagle isn’t open source and is limited to rather small PCBs with the free version, somehow Eagle has retained its popularity, most likely due to the huge number of component libraries available.
By allowing users and designers to import Eagle libraries, the folks at circuits.io are capitalizing on a huge amount of work done by designers and engineers over the years in creating custom Eagle parts for just about every component imaginable. It’s a great accomplishment for the circuits.io team and a boon for anyone wanting to move their PCB design tools over to the cloud.
It’s a simple fact that for every circuit you design, someone else has done it before. If you’re working on a high altitude balloon project, there’s already a project out there with a microcontroller, barometric pressure sensor, and an SD card somewhere out there in a corner of the Internet. Google will only help so much if you want to copy these previous builds, which led [Ben] to come up with a better solution. He took dozens of building blocks for basic digital projects and put them all into one really great interface called HackEDA.
The premise is simple: most electronic projects are just electronic Lego. You connect your microcontroller to a sensor, add in a battery, throw in a few caps and resistors for good measure, and hopefully everything will work. HackEDA takes all those basic building blocks – microcontrollers, power sources, and sensors – and creates a custom Eagle schematic with all the parts your project needs
HackEDA is still very much in beta, so there aren’t a whole lot of building blocks to choose from. That said, being able to generate an Eagle schematic with all the parts necessary for your next project is a boon. With this, all you need for a final circuit board is to create a new board file, hit the autorouter, and spend a half hour fixing whatever mess the autorouter made.
[Christian Aurich] wanted to use his Eagle CAD circuit board design in a proper CAD program in order to design enclosures. There are already a few options along these lines, but they didn’t quite fit his needs so he developed a script to import Eagle boards into FreeCAD. The script is packaged as a python macro for FreeCAD.
In describing the shortcomings of what’s already out there [Christian] does mention the use of EagleUp to model boards in Google SketchUp. But he feels the way the data is produced by SketchUp makes these models work well with 3D printing, but says they’re not easy to use with mechanical design CAD software. He also feels that the photo-realistic renderings are useless when developing enclosures.
It’s worth mentioning that this approach is only possible because CadSoft’s migration to XML makes it dead simple to get at the data.
There’s a lot of ways to burn up your time when designing PCBs, but renaming components can be one of the most frustrating. [Joe Pinzone] wrote in with his solution to the problem. Instead of hunting for each part on the schematic to change them one at a time, he makes a list of the substitutions and then uses a script to make all the changes in the XML files. He didn’t publish a post about his work, but you’ll find the source code he wrote embedded after the break.
The straw that finally broke the camel’s back was a project that included about two hundred components which didn’t seem to have a naming order that made any sense with the actual values of the components. The script is written in C++ (for Windows but [Joe] says this should be easily ported to other systems as well). To use it he creates a CSV file with the current component names in the first column. He then goes through and types what he wants for the new name in the second column. This CSV, along with the BRD and SCH files are then given as inputs for the script (through selecting them all and dragging to the script or as CLI arguments) and it automatically makes the changes.
Of course this is only possible because Cadsoft transitioned to using XML files in Eagle 6.
Continue reading “Renaming parts in Eagle CAD by editing the XML directly”
[Svofski’s] latest hack seeks to do no more than look cool on his desk. We’d say mission accomplished. He doesn’t even need anyone around to be proud of the small round CRT display unit he put together. Just having it hum away next to him will be more than enough to keep him going when regular work gets a bit tedious.
One of the biggest challenges when working with a cathode ray tube is the supply. He compares the requirements with that of Nixie tubes, and this is quite a bit more challenging since he wants to generate the 750V from a 12V DC source. To pull it off he hand wound his own transformer. There are two secondary coils, one for the cathode heater and the other as the supply. You can see a brief clip of the unit in action after the break.
Take note of the PCB section of his writeup. He took a meandering route through several different software packages before printing the board. It started with Eagle, moved to freerouting.net, which produced a Specctra file that he converted to gEDA using a Python script.
Continue reading “Custom circuit drives a small round CRT display”
When working on his quadcopter project [Matt] decided it would be best to build a robust controller for the device. He had never sent off a PCB design for fabrication, but took the plunge and ended up with a compact and reliable PCB on the first try.
One of the first things that comes to mind when we hear about quadcopter controllers are the feedback sensors. The accelerometers which are used for these projects generally come in a DFN or QFN package. This means there are no legs. Instead the chip has pads on the bottom of the package making it a lot more difficult to solder. [Matt] side-stepped this issue by using an IMU board which already has the sensors in place and offered a 0.1″ SIL pin header to use as an interface. This is simple to roll into the design, along with all of the other connectors for motor control, power, etc. He grabbed a copy of Eagle Lite to do the layout, and used OSH Park to get the boards fabricated. He was surprised that everything worked on the first try. Thanks to his planning it fits inside of a plastic food container where it should be able to ride out most minor crashes with ease.