[Request] Tool info for overlays

[ggppjj]

If this is a feature request describe it here

Add tool change and current tool information to the overlay variable tokens, for MMU and multiple extruder printers. {current_tool} for the tool at the time of snapshot, {tool_changes} for the current number of tool changes so far.

Version of Octolapse

Octolapse Version: 0.4.1

Version of OctoPrint

OctoPrint Version: 1.7.3

When you ran into the problem, did you have diagnostic logging enabled?

Diagnostic Logging was Enabled: ___REPLACE_THIS__YES_OR_NO

What were you doing when the problem occurred

1. ___REPLACE_THIS__STEP_ONE_GOES_HERE
2. ___REPLACE_THIS__STEP_TWO_GOES_HERE
3. __REPLACE_THIS__STEP...

What should have happened?

___REPLACE_THIS__PUT_YOUR_DESCRIPTION_HERE

What happened instead?

___REPLACE_THIS__PUT_YOUR_DESCRIPTION_HERE

Operating System running OctoPrint and Octolapse

OS Name: ___REPLACE_THIS__OS_NAME_GOES_HERE Os Version: ___REPLACE_THIS__OS_VERSION_GOES_HERE

Printer model & used firmware incl. version

Printer Model: ___REPLACE_THIS__PRINTER_MODEL_GOES_HERE Printer Firmware Version: ___REPLACE_THIS__PRINTER_FIRMWARE_VERSION_GOES_HERE

Browser and version of browser, operating system running browser

Browser: ___REPLACE_THIS__BROWSER_VERSION_GOES_HERE Browser OS: ___REPLACE_THIS__BROWSER_OS_GOES_HERE

Link to the gcode file you were printing when the problem occurred

Link to Gcode File: ___REPLACE_THIS__GCODE_FILE_LINK_GOES_HERE

Link to settings.json

Link to settings.json with all passwords removed: ___REPLACE_THIS__SETTINGS_JSON_LINK_GOES_HERE

Link to plugin_octolapse.log

Link to plugin_octolapse.log: LINK_GOES_HERE

Link to octoprint.log

Link to octoprint.log: ___REPLACE_THIS__LINK_GOES_HERE

Link to contents of Javascript console in the browser

Link to javascript console output: ___REPLACE_THIS__LINK_GOES_HERE

Screenshots and/or videos of the problem:

Screenshot/Video Links: ___REPLACE_THIS__LINKs_GO_HERE

Please consider becoming a patron

If you like this project, please support my work by becoming a patron, and consider adding a 'star' to the repository. It takes a lot of time and effort to maintain the project and respond to issues. The cost of test prints, software, cameras, printer parts, etc. can quickly add up, so every bit helps.

You can find various videos and tutorials by subscribing to my Youtube channel. You can also follow me on Twitter.

[INSOMNIAC84]

just wanted to add a +1 Although: Aren't those variables populated by comments/parameters in the GCode? If i understand this right, that would mean the selected tool could be implemented rather easy, but for the toolchange count, something would have to be placed into the gcode comments via custom gcode settings on the slicer?

[ggppjj]

The tool changes are in Gcode, but a count isn't. I don't actually know how Octolapse works, I would assume tool change count would need either the current count to be emitted through Gcode also or if possible, for Octolapse to keep its own count.

[FormerLurker]

Interesting request. I've got a bunch of new tokens in the devel branch, and it wouldn't be too difficult to add this. Adding this to the milestones.