New release: 1.3.7

Blog
1

After several months of work I’m happy to present you OctoPrint 1.3.7. This a true maintenance release again, consisting of various improvements and fixes. It was made possible only through your continued support of my work 💕.

Some highlights from the release notes:

  • OctoPrint will now detect prints from SD started through your printer’s built-in controller, if the firmware fulfills a couple of requirements:
    • it must send a “File opened: …” message on start of the print
    • it must respond to an immediately sent M27 with SD printing byte <current>/<total>
    • it must stay responsive during ongoing print to allow for regular M27 polls (or push those automatically) or M25 to pause/cancel the print through OctoPrint.
    • when the print is done or gets cancelled it must must send Done printing file or respond to M27 with Not SD printing. Additionally there’s now support for SD status autoreport capabilities by the firmware.

  • The serial settings got an UI overhaul to be hopefully less cluttered and overwhelming. Serial related settings that so far were located in the “Features” section of the settings were moved to “Serial Connection” were they make more sense.

  • The log management has been extracted into its own bundled plugin and now allows log level management. That is especially interesting to quickly get more detailed logs of specific components in case of bug reports and seeking support but can also help tremendously during plugin development.

  • A new bundled plugin “Printer Safety Check” will try to identify printer/printer firmware with known safety issues such as missing thermal runaway protection on connection and display warning if such a printer is detected. Read more about it here.

  • OctoPrint now has native support for the following @ commands that can be used in your GCODE files, scripts and basically everywhere where you’d send a command through OctoPrint to the printer: @pause (pauses the print), @resume (resumes the print), @cancel or @abort (cancels the print). More commands can be added through the plugin hooks octoprint.comm.protocol.atcommand.*.

  • GCODE commands sent through the system now have tags attached that can be utilized by plugins to detect the origin of commands (streamed vs file vs GCODE script vs user input vs plugin), the point where it entered the system and so on. A new logger octoprint.util.comm.command_phases was added that when switched to DEBUG will log the lifecycle of the commands through the communication layer including tags to octoprint.log.

  • Disabled plugins now will not only stay deactivated, they won’t even get imported into the system at all anymore to avoid any kind of issues caused by them.

  • Of course there were also quite a number of bugs fixed reported for earlier versions, e.g. auto connect on startup not working if AUTO was set as port, wrong queuing order of cancel script & first line from a printed file on quick start-cancel-start scenarios and incorrect behaviour if a print got cancelled by an error reported from the firmware, plus various fixes of typos and grammar in the documentation.

  • … and much more

As always this is only a small excerpt, the full list of changes can of course be found in the Changelog.

Also see Further Information and Links below for more information, where to find help and how to roll back.

And last but not least a special Thank you! to everyone who reported back on the release candidates this time: aaronkeck, akurz42, andrivet, anthonyst91, arhi, b-morgan, BryanSmithDev, chippypilot, ChrisHeerschap, Crowlord, dforsi, drdelaney, FormerLurker, goeland86, inspiredbylife, jbjones27, jesasi, jneilliii, JohnOCFII, kantlivelong, lnx13, makaper, markwal, MiquelAdell, ml0w, mmotley999, mrhanman, SCiunczyk, tdub415, tedder42, thatjoshguy, wescrockett.

Further Information

It may take up to 24h for your update notification to pop up, so don’t be alarmed if it doesn’t show up immediately after reading this. You can force the update however via Settings > Software Update > Advanced options > Force check for update.

If you get an error about “no suitable distribution” during update, please read this.

If you have any problems with your OctoPrint installation, please seek support on the community forum.

Links

This is a companion discussion topic for the original entry at https://octoprint.org/blog/2018/04/09/new-release-1.3.7/
5 Likes