Note: When adding the logging macros with the script, it is recommended to skip at least 10-15 lines
Installation instructions can be found here: https://github.com/T9Air/Klipper_Power_Resume/blob/main/Docs/Installation.md
NOTE: You must have VIRTUAL_SDCARD enabled
You can find the instructions on how to use the interface over here: https://github.com/T9Air/Klipper_Power_Resume/blob/main/Docs/Usage.md
- Fixed #58
- Use SET_GCODE_OFFSET to change the z-position when homing on the print itself. This should speed up making a _restarted file
- User can choose to just log every layer
- When adding the log macros, the logging only starts after the first G0 or G1 command
- Logging how many bytes of the gcode file were run, not what line the file is up to
- When adding logs, the command is more explicit than
sed
, enabling added features in the future
- Cleaned up the root directory and moved these files into subdirectories:
- Logger.cfg and all the macros scripts went into one directory
- The log files went into a separate directory
- Created a minimum amount of lines that can be skipped: 5
- Avoids #53
- Log the current speed, revert back from v3.2.2
- Log the current extrusion value
- Subtract all extrusions by the saved extrusion value when making a _restarted file
- 2 log files are used
- When restarting, ask User for the speed, instead of logging the speed during the print
- Fixed 2 errors:
- Get "ome: command not found" when going back to menu.sh
- When giving a file without the .gcode extension, but the file has a "." in the name, it does not add .gcode to the end of the extension, and therefore can not find the file
- The speed is logged, and used in the _restarted file
- In the install script, only add [include logger.cfg] to printer.cfg if it is not already there
- The gcode to move to the last known position has been changed to have the z axis moved separately than the x & y axes
- After creating a _restarted file, user can start the print from the interface
- When interface first opened, if the print has been cancelled, the interface asks whether to make a _restarted file or not
- User can now home on the print itself, instead of just in the corner
- Fixed bug in make_restarted_file.sh where if files do not exist, the script will still run
- Logging and unlogging done through shell scripts instead of a Python script
- Use gcode_shell_command instead of the previous klipper-extras repo that was in use
- When logging during printing, each axis is logged on its own line
- Made a new install script
- Updated uninstall script
- Can fully uninstall directly from the interface
- Ask the user how many lines skipped in make_restarted_file.sh
- User can create and edit custom start gcode files from the interface
- Added checks to add_logs.sh and make_restarted_file.sh to see if the user added .gcode in the filename, and act accordingly
- Allow user to use a custom gcode file as the start gcode
- Deprecated the post-processing script for Cura
- Deprecated the Python script to make a _restarted file
- Created the command line interface with these basic features
- Add the logging gcode to the gcode files
- Make a _restarted file just by inputting basic information
- Used the install script from v1.1.0 with minor changes
- An uninstall script
- Added an install script
- Still no interface for other features, and creating a _restarted file is still complicated
- All basic functionality is working, without an interface
- No scripts for installation
- Creating a _restarted file is complicated