All posts by Jonathan

Auf Wiedersehen

I’ve been lead programmer for the Fritzing application for 5 1/2 years and sole programmer for most of the last four. In that time I’ve closed more than a thousand issues; composed a couple thousand forum replies; pushed nearly 5000 commits; and cranked out more than 50 releases.

One can only run full-tilt for so long; it’s time for me to take a sabbatical. Before I go, I’d like to thank Reto and André for originating the project; Reto (and the government of Brandenburg) for the grants that gave the project such a strong start; and my past and present colleagues for putting so much of themselves into the work–the list is too long to display them all.

Finally, I’d like to thank the everyone in the Fritzing community for your enthusiastic (and early) adoption of our continual work-in-progress, and for your great patience with what has effectively been a distributed QA software releasing methodology. If I could, I’d buy you all a beer.

With warm regards from chilly Berlin,

– jc


0.8.6 schematics

We just released Fritzing 0.8.6. Aside from some bug fixes and a few new features,  it mostly addresses schematic view. To display the changes, here are  two images of the stepper motor example.  The first is from 0.8.5 and the second is from 0.8.6. They are both zoomed to 100%.


The most obvious change is that the grid size has gone from 7.5 mm to 0.1 inches. This will save some trees when you print. It also means we are using the same grid across all three views. But more important than the particular grid size is that all parts that ship with Fritzing now conform to it. This means that schematic diagrams will look much neater. In the past, there were a couple of competing standards (plus a few oddballs), so schematic diagrams tended to be pretty ragged.

In addition we have revised a number of schematic part images to bring them more in line with general usage.

So what happens if you load an existing sketch into 0.8.6? If you didn’t draw any wires in schematic view, Fritzing assumes you are not particularly invested in the current state of that view, and will use the new standard. But if there are schematic wires, Fritzing will give you a choice: open the sketch read-only and see the original schematic, or convert to the new standard.

The conversion process will change parts, but beyond some adjustment for the new part sizes, the wires will not be rerouted. So you will probably have some straightening out to do. Custom schematic images are not converted. I would suggest you use the Parts Editor to give the custom part a new schematic image. To assist you with this, if you switch to schematic view in the Parts Editor, under the File menu there is a Convert schematic to 0.1 grid option. This option will generate a standard rectangle-form schematic based on the existing part.

We hope you like the newly cleaned view.












1000 new parts!


Well, almost 1000–certainly 900+. The image above is just a small fraction of the set of new parts available in Fritzing 0.8.1. The parts all come originally from the open source SparkFun Eagle Library (thank you SparkFun!) and the conversion was carried out partly by program, and partly by hand. You can thank our illustrator Fabian for so many beautiful breadboard view images. This new heatsink is one of my favorites:









Originally we intended to ship these parts with a new Parts Bin UI to make it easier to navigate through them all. Alas, the Fritzing project being perpetually undermanned–and the demand for these parts being so high–we decided to put off the UI work until later. So the new parts simply arrive in nine shiny new Parts Bin containers, with nine new tabs to click in the Parts Bin window. Another shortcoming is that the new parts have not been completely integrated (from a database point-of-view), so part-swapping is mostly not possible between core parts and the new parts.

But we have a good workaround for these missing features. The Parts Bin search function (the topmost tab in the Parts Bin window) is quite effective for finding parts, especially since we have added a new ‘and’ search. Just separate the terms with spaces; the image below shows an ‘and’ search for parts matching both ‘db’ and ’25’.










The other goal we didn’t reach in this release was to enforce a single schematic-view image standard (based on a 0.1 inch grid), instead of the current hodge-podge (the majority based on a 7.5mm grid). The new parts all use the new standard, and we plan to convert the rest of the core parts in the next release or so. In the image below, examples from the old ‘standard’ are on the left, examples of the the new standard are on the right (the image is zoomed to 200%).


Despite the work we left unfinished, the addition of a thousand new parts is quite a big step forward for Fritzing. We hope you find these parts as useful as we already have.


— Your Fritzing Team

276-150 in 0.8.1

276-150 stripboard










By popular demand, the RadioShack 276-150 stripboard has been added to release 0.8.1. However, you won’t find it as a separate part in the Parts Bin. To access it, drag-and-drop the regular stripboard part into your sketch, then find the ‘layouts’ drop-down in the Inspector and select the 276-150 option.

This may seem a little indirect, but here is the logic: our stripboard strips now run both horizontally and vertically (before they ran only horizontally). This means it’s now possible to cut/uncut strips into arrangements which we call layouts. The 276-150 is one of these layouts, but since we have had so many requests for it, we decided to “store” the layout with Fritzing so people don’t have to make it from scratch each time.

It would be easy to store other layouts with Fritzing. If you have a favorite stripboard layout that you think people would like to use, make the layout on a stripboard in a Fritzing sketch, and email the resulting file to info:at: fritzing :dot: org. In the email, tell us what part you’ve represented or why the layout is so useful. You may see that layout in a subsequent release of Fritzing.


— Your Fritzing Team


0.8.0 Released

Today we released a new Fritzing version, 0.8.0. Download it here. In previous releases of Fritzing, you could only look at the board from above, in the new release you can also look at the board from below. Furthermore, you can now place any part–THT or SMD–on either side of a double-sided PCB.

To control the point-of-view, we added a new button to the toolbar. Just click to toggle  the viewpoint from above to below, and back again.


Here is an example sketch, first viewed from above:


Now, after toggling the button, viewed from below:


You use the current point-of-view to determine on which side of a board a new part or trace will be placed–if you are currently viewing from below, then dragging in a THT part from the Parts Bin means you are pushing the part in from underneath.

You can also use the Both/Top/Bottom activation toggle to control the side on which a new part or trace is placed. So even if you are viewing from below, if only the top side is active, new parts will be placed on the top.

But don’t worry if you get it wrong or change your mind–the Inspector now has a “layer” widget to let you change whether a part is placed on the top or bottom side.

And that leads us to another feature of this release. The Inspector now has a ‘placement’ section that contains a number of controls. You can use these controls to set a part’s location, rotation, lock state, and top-or-bottom state. (In addition to the location control, we have added some basic alignment functions–top, left, right, bottom, center–to the Part menu.)

Inspector styling has been improved so that it’s clearer when a control is disabled, and when a combo-box will accept text entry (as opposed to being a pure drop-down).

You will find that it’s generally easier to select parts that are underneath other parts, in both PCB and Schematic views (and in PCB view, switching the point-of-view gives you another way to reach hard-to-click items).

Thanks to sponsorship from Analog Devices Inc., rotation and flip are now enabled for all parts in Schematic view. Additionally, part text elements in Schematic view will preserve their orientation under these transforms. Stay tuned for some other ADI-sponsored features in upcoming releases.

You can find a more complete list of changes here.

We hope you will enjoy version 0.8.0.

— Your Fritzing Team

PS. Inevitably with all the changes, there are going to be new bugs. Since the Forum is currently in a transitional state, please use our issue tracker to report problems. Take a quick look to see whether your issue has already been reported (and add a comment if you have something new to relate). If you don’t see a relevant existing issue, then click the “new issue” button to make a new report.

gitzing Fritzing

Back in 2008, we had to make a decision about source control. We were then using googlecode with Subversion. The Fritzing application had been built in Java on top of a couple of frameworks that were in turn sitting on top of the Eclipse framework, but we had decided to switch to Qt and C++ (and looking back, we have absolutely no regrets about that).

The question was whether to switch source control as well, and I remember Brendan arguing that we should go over to git, but at the time googlecode didn’t support it and git was still a bit of a new kid on the block, so we made the conservative choice and stuck with Subversion.

The world looks different in 2013, and we are belatedly moving our repository to git. We are remaining with googlecode because our issue tracker is a very rich resource which is nicely integrated with source control, and there didn’t seem to be a way to move it elsewhere without losing that coupling.

The old svn repository is still available at, and for that reason (and because we tried it, and it didn’t go so well), we decided not to convert the Subversion history, just the latest trunk code. This will also make cloning a lot quicker. You can clone the code using: git clone

There are a number of different workflow styles possible using git. For the moment, if you have made code changes you would like to see in the core, add an issue to the issue tracker, and attach a git patch.

Cheers and a happy May Day.


Still Using OS X 10.5?

Qt, the GUI framework underlying Fritzing, has recently released their next generation framework (Qt 5.0). The new framework only supports OS X 10.6 and up, and does not support the Power PC architecture. We are contemplating a move to the new framework, and wondered how many OS X 10.5 and/or Power PC Fritzing users would be left behind. Please let us know.


— Your Fritzing Team.

a little something for the new year

2013 rings in a new Fritzing autorouter. Here are the before-and-after pictures:

Autorouter results from versions 0.7.10 and 0.7.11

The upper image is the Timer example using the old autorouter (version 0.7.10) followed by a Design Rules Check (DRC). The lower image is the same example using the new autorouter (version 0.7.11) again followed by a DRC. The old autorouter was unable to fully route the board, and the DRC found overlaps around the jumpers the autorouter placed. The new autorouter completely routed the board and the DRC found no overlaps.

For the cognoscenti out there, the new version is an A* maze router with rip-up-and-reroute. In practice (and compared with the old autorouter) this means:

  • The new router does not have trouble with diagonals.
  • The new router does not limit the search in the same way as the old router, so it finds routes that the old router missed.
  • After running the new autorouter, the DRC will usually not complain–or at least will only complain a little.
  • In schematic view, traces from different nets no longer overlap lengthwise (well, much less frequently than before).
  • In schematic view, if a connection can’t be routed directly, the autorouter will try to place net labels.
  • No more red dots (unconnected zero-length traces)
  • Routing is not optimal–there are lots of unnecessary zig-zags–so you will want to do some manual rerouting after the autorouter finishes. We’ll be working on this going forward.
  • The new router is much slower than the old one (can’t win ’em all…).

As an extra holiday bonus–and because the DRC and autorouter no longer depend on straight lines–curvy wires are now enabled in PCB and schematic view. Here is a hand-routed example (at least for now, the autorouter can only use straight lines):

Curvy Parking Assistant

A hand-routed version of the Parking Assistant example

Happy 2013,

— Your Fritzing Team.

New Design Rules Check (DRC)

compare drc

Hello Fritzing Fans,

We’re using images from a PCB design by Bob64 (who we thank for giving us permission) to illustrate the new DRC (Design Rules Check). On the left is the DRC from version 0.7.9 and earlier. In the middle is the same file using the DRC from version 0.7.10.  The image on the right is a close-up from the upper region of the middle image so you can see the new highlighting.

The new DRC has no trouble dealing with diagonal lines or rotated pinheaders. The tradeoff is that it is quite a bit slower than the old DRC (it puts up a progress bar while in process), but is much more accurate.

This means the results are much more specific, and we now display these in a modeless dialog. In other words, you can work with the PCB layout while the highlighting remains visible–you can see where you need to make changes, and make them on the spot. Here is what the dialog looks like after we run the DRC on the board illustrated above:

drc dialog

When you click on an entry in the list, the referenced parts are selected, thus making it easier to see where the problem is.

Hope you enjoy using it as much as we enjoyed building it.


The Fritzing Team.

New Parts Editor released

Hello Fritzing Fans,

We have decided to release the new Parts Editor in two phases. The first phase, included in the latest release (0.7.9), is already easier to use  and more powerful than the old Parts Editor, but you still have to do a lot of preliminary work using an SVG editor like Inkscape, Illustrator, or CorelDRAW. In the next phase we hope to eliminate much of the need to use these programs.

How to start

The new approach is very different from that of the old Parts Editor, and explaining that difference is the purpose of this document. The first big change is that you cannot create a new part from scratch–you must begin with a part that already exists. So the best thing to do is to find a part that is pretty close to what you eventually want. If your part is really different from anything else, then just to try to match the number of connectors. For example, if your part needs 39 pins, then start with a generic IC part, change it to a SIP (single inline package) and give it 39 pins. Though finding a part to begin with may seem like a burden, it will save you effort as you go through the process.

You can open the new parts editor by right-clicking a part in a sketch and choosing the ‘Edit’ option; choosing ‘Edit’ from the Part menu; right clicking a part in the Parts Bin and choosing the ‘Edit’ option; or using the Parts Bin drop down menu.

Six views

The new Parts Editor no longer tries to display everything in a single view.  Instead, it works like the sketch window which has multiple tabs with only one tab visible at a time.  In the new Parts Editor there are six tabs: Breadboard view, Schematic view, PCB view, Icon view, Metadata view, and Connectors view. As you might expect, the first four views are for the part images; the Metadata view is where you enter the part’s title, author, and other properties; and the Connectors view is for editing connector metadata, and for adding or removing connectors. For the latter, you just type in the number of connectors you want.

Loading new images

To load the SVGs for your part, switch to the appropriate view, and use File > Load image for view. As before, you can load SVGs in all views and gEDA .fp files and KICAD .mod files in PCB view only. To create an SVG for any view, you must use an external SVG editor (Inkscape, Illustrator, CorelDRAW, or a text editor) to layout the elements that will be used as connectors. The SVG example below uses <circle> elements for connectors.

Loading PNG or JPG images directly is possible, but since these become SVG images with only a single element, there is no way to place individual connectors. We also  discourage the use of PNG and JPG because these are raster-based rather than vector-based, so they don’t look good when scaled. If you still prefer to use PNG or JPG, we recommend that for now you open them in an external SVG editor and add connector elements there (see below for more about ‘connector elements’). Save the result as an SVG, and use that in the Parts Editor.  In phase 2 you will be able to add connector elements directly in the Parts Editor.

Since you have already begun with a part, it may be that you will only have to load a single image for a particular view–you do not have to replace all the images in the original part.

It is still necessary to prepare SVGs for PCB view by grouping elements in layers: copper0, silkscreen, copper1, etc. (Layering will be handled in the phase 2 parts editor.) The best way to understand the layers is to open up one of the core pcb svg files, For example have a look at the file crystal_hc49U.svg. Silkscreen layer has four while lines, the two copper layers share a pair of circles as connector elements.

<?xml version="1.0" encoding="UTF-8"?>
<svg baseProfile="tiny" height="0.20306in" version="1.2" viewBox="0 0 46684 20306" width="0.46684in" xmlns="">
    <desc>Fritzing footprint SVG</desc>
    <g id="silkscreen">
        <line stroke="white" stroke-width="1000" x1="1000" x2="45684" y1="1000" y2="1000"/>
        <line stroke="white" stroke-width="1000" x1="45684" x2="45684" y1="1000" y2="19306"/>
        <line stroke="white" stroke-width="1000" x1="45684" x2="1000" y1="19306" y2="19306"/>
        <line stroke="white" stroke-width="1000" x1="1000" x2="1000" y1="19306" y2="1000"/>
    <g id="copper1"><g id="copper0">
        <circle cx="13736" cy="10153" fill="none" id="connector0pin" r="2750" stroke="rgb(255, 191, 0)" stroke-width="2000"/>
        <circle cx="32948" cy="10153" fill="none" id="connector1pin" r="2750" stroke="rgb(255, 191, 0)" stroke-width="2000"/>

Sometimes you will want to reuse the breadboard image as your icon image. There is a shortcut for this under File > Reuse breadboard image. You can also find the options: File > Reuse schematic image, and File > Reuse PCB image.

For certain parts–like a breadboard–there is only one view image. For technical reasons, you have to tell the Parts Editor this is what you want.  Use View > Make only this view visible from the current view (one of Breadboard, Schematic, or PCB) to make the part invisible in the other two views.

Undo, save, show in folder

The next big difference from the old Parts Editor is that undo is always available, even after loading view images. Furthermore, you can save your changes at any point and keep working–the new Parts Editor is less like a dialog and more like a full document window.

If you start with a core part (i.e. a part from the Fritzing distro), saving is equivalent to “Save As”. A new part will be created in your local storage area (explained below) and added to the “My Parts” Bin. If you are editing a custom part that was in a sketch, the part will be updated whenever you save (core parts are not updated). If you want the new part to display in the My Parts Bin the next time you run Fritzing, remember to save the bin (use the drop down menu at the upper left of the bin). If you start editing from a part in the My Parts Bin you have a choice between Save (which will overwrite the part), and Save As (which will create a new part and add it to the My Parts Bin).

On Windows the local storage folder is something like C:\Users\[username]\AppData\Roaming\Fritzing\parts\user\, and SVGs are stored in C:\Users\[username]\AppData\Roaming\Fritzing\parts\svg\user\. On Linux and Mac this would be ~/.config/Fritzing/parts/user/ and ~/.config/Fritzing/parts/svg/user/.

To find the SVG image for the current view on the desktop, choose File > Show in Folder. On Mac and Windows this will open a folder on your desktop with the SVG file selected. Under Linux you get the folder but no file selection (if anyone has advice about how to get selection to work, we would be grateful).

Associating a connector with its SVG counterpart

The next task will be to associate each connector with its counterpart in the SVG for each view. This is handled very differently from before. For an example, I am going to use images from a part created by Shunichi Yamamoto (who graciously gave us permission to include them in this tutorial, and who also helped beta test the new Parts Editor).

The new part will have 39 pins, so we begin with a Generic IC part and drag it into an empty sketch. There we use the Inspector to change it a to SIP and give it 39 pins. Then we open that in the new Parts Editor with a right-click.

starting up

Next we load the new breadboard image using File > Load image for view.  In the Tools widget at the upper right, you see a list of connectors. Choose one to make it the current or active connector. If it has already been associated with an SVG element, that element will display a marquee highlight. Since we are just starting out, we will choose pin1 which is not currently associated with any SVG element.


To create the actual association click the “Select graphic” button over in the Connectors widget. This basically puts you in a “mode” that lasts until the next time you mouse down. If you want to escape the mode, click anywhere outside the part or use the escape key. You can only make the association when you are in this mode (this keeps you from accidentally associating a connector to a graphic when you didn’t intend to).

In the mode, move your mouse over the SVG. As you do so, different SVG elements will highlight. It is often the case that any given mouse location can refer to multiple SVG elements (or groups of elements). Use the mouse wheel to highlight other elements above or beneath the currently highlighted one (in the z-order). If you are already on the bottom layer then the next wheel “downward” will make the element flash white; a similar white flash will occur if you are already at the top layer and wheel “upward”. In other words, the flash signifies you can’t move any further in the z-order in that direction.

Here are three highlights from the same mouse position, using the mouse wheel:


The first highlight is the one we want so we mouse down when the wheel gets us back to that small rectangle. Now the element has a marquee to show that it is the current pin, and you also see the terminal point as a crosshair which defaults to the center. The terminal point is the place where a wire attaches to the connector.


After associating pin2 and pin3 we have:


Adjusting terminal points

In PCB and Breadboard view the terminal point is usually the center of the connector so you don’t have to do any thing else.  But in schematic view the terminal point is usually near the end of the connector. So let’s go to schematic view.  We start with the original SVG image. Note how the connectors are already showing their anchor points. Pin3 is the current connector.


Now we load the new schematic image and start associating pins.


Here is what the Connectors widget looks like with pin3 as the current connector:


Notice that since we have selected graphics for three of the connectors, those connectors are checked in the connector list.

You can use the buttons or spinners to adjust the terminal point. Here is a close up after hitting the W button, and clicking the X spinner twice (look at the pin marked ‘AN2’):


You can also drag the terminal point directly by mousing down on it when its SVG element is highlighted.

Setting internal connections

An internal connection is when a two or more connectors in a part are already connected, for example the GND connectors on the Arduino UNO. You can specify and edit internal connections by clicking on the “Set internal connections” checkbox in the Connectors widget–it’s beneath the connectors list (you can see it in the image of the Connectors widget, above). Since we are talking about the Arduino UNO, here is what it looks like when Set internal connections is checked:


The green lines represent the internal connections. To remove an internal connection, right-click the line and choose “Remove internal connection”. To add a new connection, just drag a line out from one connector to another.

Known limitations

The following feature are due in phase two:

  • adding holes
  • mixing THT and SMD connectors–for now you must start with an SMD part to create a new SMD part, and start with a through-hole part to create a new through-hole part.
  • control over SVG element layering
  • direct manipulation of SVG elements
  • setting up parts with bendable legs.

Bye for now

That’s pretty much the phase one story. We hope you like what you’ve seen. Stay tuned for phase two.


— The Fritzing Team