MarlinFirmware / MarlinFirmware/MarlinDocumentation

Suggestion: M593 Input Shaping Calibration Tower Slicer G-Code

Open
#604 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
398
Forks
878
Avg merge
1d 16h
Merged PRs (30d)
1

Description

When using the ringing_tower.stl method to calibrate Input Shaping, the following code is recommended:

M593 F{(layer_num < 2 ? 0 : 15 + 45.0 * (layer_num - 2) / 297)} ; Hz Input Shaping Test

While this does work, it causes the Input Shaping value to change over the entire model with a set value only showing up on a single line. Picking the "best' layer is very difficult.

I instead used this:

{if (layer_num - 2) % 25 == 0}
; Layer {layer_num} ({layer_z}mm)
M593 F{30 + 2 * (layer_num - 2) / 25}
{endif}

This sets the value for the entire tier instead, giving ~5mm of model to analyze and compare against the other layers. In my case I found values below 30 were just, well bad, so I started at 30 and went up to 52 in intervals of 2. Once I got a range that looked "best" then I could print the model again with better refinement.

This was done with an if instead of inline in order to allow multiple settings - for instance different ranges for the X and Y.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the documentation section for the ringing_tower.stl Input Shaping calibration method and its current M593 example. Compare the proposed tier-based example with the surrounding instructions; done means the calibration guidance explains how to evaluate larger constant-value tiers and supports the multiple-settings context described in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.