v0.2.3-beta

Fixed several issues, typos, and added some improved error messages.

• Fixed several issues dealing with initial installation
• Fix some gcode parsing issues (+ symbol in front of parameter, some other items). Octolapse still does not correctly parse commands with extra/missing spaces, but this will hopefully be fixed in the next release.
• The 'latest snapshot image' that is displayed in the Octolapse tab initially looked like an error message. It has been replaced with an image that says 'Welcome to Octolapse'
• More fixes for the 'Load Default Settings' option.
• Shortened and combined the snapshot gcode sequence so that it could be completed with fewer M400s and less gcode.
• The GUI was not refreshing when Octolapse was enabled, this has been fixed.
• In some cases the timelapse didn't initialize properly and threw exceptions regarding null variables.
• In some rare cases a few gcodes were missed during the start of a new print, which prevented Octolapse from properly detecting the position, resulting in no snapshots being taken. This is under observation.
• Octoprint 1.3.7rc3 fixes an error in Octolapse that caused some Repetier firmware lock up for a long time (600 seconds). This is under observation. Please first upgrade OctoPrint to at least 1.3.7rc3 before using Repetier firmware (Wanhao Duplicator i3, Monoprice Maker Select v2, etc.)
• Added asynchronous logging. VERY large logs were affecting printing performance, occasionally leaving blobs on the print. This will benefit most hardware, especially when multiple cores are used.

v0.2.2-beta

New Features:

• Octolapse no longer needs to pause the print to take a snapshot due to some excellent new features in OctoPrint v1.3.7.
• Control the current profile from the main tab
• Enable/disable info panels from the main tab
• Added position restrictions with intersection calculation to the snapshot profiles.
• Many new print profile settings
• Better handling and messaging for start-up errors, printer disconnects, canceled prints, etc.
• Better gcode compatibility
• More rendering options including custom filename templates
• Fewer bugs
• Much more

This version requires OctoPrint v1.3.7 or higher.

Beta

This version is more stable, has better print quality, and offers more features than the Alpha release. Still haven't been able to test on any printers other than the Mk2S.

Initial Release

Release v0.0.1-alpha

This is the first release of Octolapse (this name may change), and is in Alpha state with both known and unknown issues. Use at your own risk.

Known issues

Restore All Default Settings

If you use the 'Restore All Default Settings' button, make sure you reboot Octoprint. I'm working on this bug.

Original Prusa Firmware 3.0.12

If you are using an Original Prusa printer, there is a possible issue in the firmware 3.0.12 (linear advance update). Here is the relevant workaround:

Note from foosel: There does exist a workaround in OctoPrint for this (since it's happened in the past with other firmware variants), users can tell OctoPrint to "simulate" an ok after resends by enabling Settings > Serial communication > Advanced options > Simulate an additional ok for resend requests, but that has to be done manually.

Unfortunately this workaround may cause some print quality issues during the resend, since I had some seemingly random overextursion in a test print after implementing the workaround. I've not verified that it's due to the workaround, but I will try to do this soon. I expect this bug to be fixed in the next firmware release.

G92

This command has been implemented, but not extremely well tested. In fact, I'm not sure if I completely understand the expected behavior of this command in all cases, so my implementation is most likely incorrect. I've tested a lot of gcode that included G92 for extruder position, but not X,Y,Z, so beware.

Test Mode

Occationally I've noticed that my plugin might miss the first few gcodes sent to the printer. This has only ever affected me while using the debugger, but I think it's possible that it could happen during a test print. This can have the effect of letting commands that should be suppressed/rewritten slip past my routines and make it to the printer. I'm looking into this.

There are probably other commands that should be suppressed/rewritten that are not included. If you find any let me know.

Non-Cartesian printers

These are not currently supported. I hope to include support for these at some point, but I don't own one to test on currently.

Floating Point Math

I've noticed some areas where floating point math may cause problems, but I have not resolved all of them. They could prevent proper extruder monitoring/zhop detection in some cases, and I'm working to fix this.

Logging

It's possible that some of the logging options aren't doing exactly what they say. I did some refactoring that didn't quite work as expected and will have to review the logging code.