Version 1.5.1 is mostly a bugfix release. Below are release notes with the links to the exact issues fixed:

Release Notes – cirQWizard – Version 1.5.1

Bug

  • [CQ-92] – Stop button on tool paths generation pane doesn't stop generation
  • [CQ-130] – Firmware update instability
  • [CQ-131] – Check for non-empty settings is broken
  • [CQ-134] – ExcellonParser fails with NPE if no tool is specified

New Feature

  • [CQ-133] – Support for R command in Excellon files

Version 1.5.0 comes with the long promised copper rub out feature. That’s an additional step which you can choose to perform after insulation milling (it’s skipped by default – check the new Copper rub out section in the Settings to turn it on).

As opposed to insulation milling, which simply isolates traces on the copper layer, this step completely removes copper from the places on the board, where it’s not supposed to be according to the layout. This is often required in circuits, involving radio frequencies or high voltages – unconnected copper alters electrical features of the board in undesired way.

The implementation may not win the prettiest algorithm contest. It might not be the fastest algorithm on Earth either. But at least it’s here today and it gets the job done. We’ll address algorithm inefficiencies later down the road.

This version addresses user interface usability issues which were raised by our users. It rearranges controls in a way that keeps intuitive step-by-step wizard approach appreciated by those who are just getting their feet wet in PCB milling, but allows for greater flexibility required by more experienced users.

So, the major new features are:

  • Breadcrumb bar navigation, allowing for direct jumps between application screens (no more Go back, Go back, Go back clicking to get to the screen you want to return to)
  • Manual control popover accessible from every screen of application, allowing to move machine’s axes as you please
  • Predefined locations – in addition to already existing Far away, there’s now also Tool change location. Both of them with all three coordinates: X, Y and Z.
  • Settings popover accessible from operations screens – you can now change all the settings related to the operation you are currently performing right from the operation screen. No need to go back to settings anymore to change additional passes overlap or pre-feed delay!

This version has also seen major code refactoring, paving a way for new exciting features, which were held back by growing code complexity.

These two versions add a possibility to send G-code to the machine directly from cirQWizard. This functionality can be accessed from Manual Control → Direct GCode control.

Version 1.3.10 had a build issue which resulted in broken functionality of firmware flashing. This was fixed in 1.3.11.

Below are release notes for version 1.3.10:

Release Notes – cirQWizard – Version 1.3.10

New Feature

  • [CQ-83] – Possibility to send GCode directly to the machine

We’ve been in such a hurry to release these versions that we didn’t even blog about them. So, here go the release notes for all these versions. We’ll try not to postpone blogging about new releases going forward.

Version 1.3.2

Bug

  • [CQ-99] – Arcs not supported in contour milling layer
  • [CQ-100] – Oval apertures not supported on solder paste layer

Version 1.3.3

Improvement

  • [CQ-102] – Support for LP parameter in gerbers

Version 1.3.4

Bug

  • [CQ-69] – Running gcode without connected machine doesn't produce an error
  • [CQ-103] – Flash width is not taken into account when board's zero point is calculated

Improvement

  • [CQ-89] – Improvements of tool path merge algorithm

Version 1.3.5

Bug

  • [CQ-107] – NPE in Region.getMin()

Improvement

  • [CQ-106] – Support for decimal point in Excellon files

Version 1.3.6

Bug

  • [CQ-2] – Incorrect order of screens when drilling holes
  • [CQ-86] – Zoom shortcuts do not work on Linux
  • [CQ-104] – Tool paths around polygonal apertures do not take into account tool diameter
  • [CQ-108] – Additional passes feature broken
  • [CQ-109] – Parts of tool paths sometimes disappear during merge

Improvement

  • [CQ-76] – Separate feed for arcs

New Feature

  • [CQ-21] – Reset settings to default

Version 1.3.7

Version 1.3.6 was unintentionally released with Mac OS X version built with Java 8. This version corrects this mistake with all of the platforms using Java 7 for build.

Version 1.3.8

Bug

  • [CQ-105] – In some cases program generates incorrect toolpaths
  • [CQ-110] – Elapsed time message on machining screen doesn't show hours
  • [CQ-111] – Application icon disappeared

Version 1.3.9

Bug

  • [CQ-113] – Phantom tool paths on solder paste layer

New Feature

  • [CQ-3] – Visual guidance on offset selection screen

Version 1.3.1 is mostly a bug fix release. Here is the list of things fixed in this version:

Bug

  • [CQ-17] – Exception on start up when using autodetect
  • [CQ-30] – Select all command on drilling screen selects holes irrespective of their diameter
  • [CQ-77] – Tabbing out of "Tool diameter" on machining screen doesn't trigger regeneration
  • [CQ-85] – Tool paths cache invalidation is inconsistent
  • [CQ-90] – Tool paths not regenerated when changing number of passes
  • [CQ-93] – NPE in SerialInterfaceFactory.getSerialInterfaces()
  • [CQ-96] – Empty lines in excellon file cause parser to fail

Improvement

  • [CQ-70] – Better visibility for "Go" button on machining screen
  • [CQ-91] – Relabel "Lower & Test" button

Task

  • [CQ-95] – Add target that runs the application to the build.xml

Version 1.3.0 is a feature release, which adds a possibility to request milling tool path generation algorithm to make several passes around traces (or only around pads). This hopefully should decrease the possibility of solder bridges between pads or between pads and ground plane.

Additional passes considerably increase milling time, regardless of whether it’s pads only or entire traces. But hopefully, there will be more time gained by not having to troubleshoot bridges.

The relevant settings in the Insulation milling tab are:

Setting Meaning
Additional passes Number of additional passes to be generated
Additional passes overlap The overlap between previous pass and each successive pass
Additional passes around pads only Whether to generate additional passes around all traces, or around pads only

For now, as this feature isn’t yet thoroughly tested, the default value for Additional passes is 0, which effectively disables it. Feel free to experiment and let us know which settings you like most!

As a next step in our effort to make cirQWizard even more open and transparent we’ve migrated to publicly available issue tracking system.

The system can be accessed at https://cirqwizard.atlassian.net/ There you can find detailed information about issues addressed in each release, issues scheduled for the next releases, new features we are thinking about and all those annoying bugs no one has time to fix ;)

What’s even better, after simple registration procedure everyone can contribute to the project – you can comment on issues, vote for them so that we know which issues are important to you, create new issues reporting bugs you’ve encountered or suggesting new great features!

Help us make cirQWizard even more awesome!

As the community of cirQWizard users grows, we feel it’s the right time to add another communication channel to keep everyone up to date on what we have done and what we are up to. So, from now on here we will be blogging about things happening to cirQWizard – new releases, known problems and workarounds, useful hints and whatever comes to our mind and we feel is appropriate to share.

Needless to say, your comments are much appreciated! Feel free to share your thoughts in comments section below every article.

So, today the news is that the version 1.2.2 is out. That’s a bug-fix release. The most important bug fixed there was the one that was causing missing segments of the tool paths during generation. This was caused by insufficient memory available to cirQWizard to utilize all of the available CPU cores. Now the application attempts to reprocess failed part of the board. You would see progress indicator jumping chaotically, as this happening. If this happens to you, you would know cirQWizard is running low on memory. Then it doesn’t make sense to run that many processing threads. To make more efficient use of your resources you can go to Settings→Application and decrease Processing threads value. With a bit of trial and error you can find a value, that would work well for you.

We’re setting up a public access to the issue tracking system we use to develop cirQWizard. This would give everyone interested in depth information about what exactly was included in the released versions, as well as what we are working on at the moment and what we are thinking about. Stay tuned!