# Parameter Philosophy On this page, I explain my thought process in detail.\ The goal is not to define a universal rule, but to make my decisions transparent — so you, as the reader, can clearly understand how I arrived at these parameters. I still keep cutting theory in mind — but I don’t treat it as the final authority.\ My decisions are driven primarily by what I observe in real cuts on this specific setup. Many of my decisions come from asking questions like:\ \&#xNAN;*“Theory suggests this — but what actually happens if I push beyond it?”* In practice, this often leads to parameters that differ significantly from charts, calculators, or manufacturer recommendations.\ These differences are intentional. They result from exploring the limits of a specific machine, setup, and cutting strategy, rather than staying strictly within generalized assumptions. When observation and theory do not fully align, I do not ignore either one.\ I use the gap between them to deepen my understanding, refine the parameters, and better predict how the machine will behave next time. This way of thinking is not guaranteed to hold in every situation, and it may evolve or break under different conditions.\ Part of the reason for documenting it here is to revisit these decisions over time and see where they continue to work — and where they do not. While this approach may appear riskier on paper, it is intended to reduce risk in practice by avoiding blind parameter choices and replacing them with conscious, reasoned decisions. *** ### How I treat charts, calculators, and recommendations I see charts, calculators, and manufacturer recommendations as **rough orientation**. They are useful for: * understanding general relationships * avoiding clearly unreasonable values * providing a sanity check But they are often: * conservative * generalized * based on assumptions that do not fully apply to desktop CNC machines For that reason, I do not treat published values as limits.\ They are starting points — sometimes very loose ones. It is not unusual that my working parameters differ by a large margin from published recommendations.\ This does not mean those recommendations are wrong.\ It means they were not written for *this* machine, *this* setup, and *this* way of cutting. *** ### **What this looks like in practice** Much of the thinking described on this page comes from long, repetitive cutting tests. {% columns %} {% column %}
{% endcolumn %} {% column %}
{% endcolumn %} {% endcolumns %} *** ### Overruling factors Not all influences on a cut are equally important at all times.\ In many situations, a single factor becomes dominant and effectively overrules normal parameter trade-offs. When this happens, other parameters can no longer be adjusted freely.\ They must be adapted around this dominant constraint, even if that leads to values that look unusual on paper. **Typical overruling factors can include:** * tool stiffness at very small diameters * cutting forces exceeding machine rigidity * controller limits such as data starvation in segment-heavy motion * dynamic motion limits in tight circular toolpaths Once an overruling factor is identified, parameter choices stop being a balancing exercise and become a constraint-driven problem. *** ### My view on parameters: This section describes how I personally think about cutting parameters.\ It shows how I prioritize them, how I weigh them against each other, and how I deliberately adjust (“play with”) them to understand the limits of a cut. From here on, each parameter is described from **my point of view**, not as a general rule. #### Spindle Speed I generally try to maximize spindle speed to reach an efficient cutting regime. I reduce spindle speed only when there is a clear reason — for example when surface speed becomes too high for dry cutting and heat starts to dominate. For that reason, spindle speed is often the first parameter I set to its maximum when exploring a new tool or operation. *** #### Surface Speed I mainly use surface speed as a verification tool rather than a parameter I actively tune.\ As long as it is within a reasonable range, it plays a minor role in my decision-making. If cutting behavior is clean and stable outside typical surface speed recommendations, I do not deliberately adjust parameters just to move back into a suggested window. *** #### Feed per Tooth Feed per tooth is critical for chip formation.\ I primarily use it to ensure that the tool is actually cutting rather than rubbing. In my setups, cutting forces are mainly controlled through **tool engagement** (stepdown, stepover, ramp angle), not by reducing feed per tooth or feedrate.\ Because engagement is often chosen very lightly — due to the category of machine I am using — this leads to feed per tooth values that are significantly higher than many published recommendations. This difference remains even when chip thinning compensation is considered.\ In very small engagements and tight toolpaths, effective chip formation is often no longer well described by typical data sheets or simplified compensation models. For that reason, I accept feed per tooth values that look high on paper, as long as cutting behavior is stable, chips are clearly formed, and the machine responds predictably. {% hint style="info" %} **Chip thinning (short note)** When radial engagement is small, the tool does not bite deeply into the material, even if feed per tooth looks reasonable on paper.\ Chip thinning compensation increases feed per tooth so real chips are formed instead of rubbing. Most models assume moderate engagement and do not fully describe very small engagements. {% endhint %} *** #### Feedrate Feedrate is not chosen directly.\ It is calculated to reach the intended **feed per tooth**. If this results in a feedrate that is impractically high, I step back and adapt parameters to reduce it — while trying to preserve chip formation. One important limitation on the Snapmaker platform is the controller’s block-per-second limit.\ Very high feedrates combined with fine toolpaths can exceed this limit and lead to data starvation. This can be mitigated later in CAM through tolerance and smoothing settings, but feedrate still plays a major role. I accept a certain amount of data starvation as a deliberate trade-off.\ Rather than forcing overly complex solutions, I tolerate this limitation as long as cutting behavior remains stable and predictable. {% hint style="info" %} **Data starvation (short note)** When toolpaths consist of many small segments, the controller may not receive motion commands fast enough.\ This can limit the actual feedrate, even if higher values are programmed. On the Snapmaker, this typically results in **smooth feedrate reduction rather than motion jumps**.\ While preferable to sudden jerks, it is still a factor to consider when choosing feedrates and toolpath complexity. {% endhint %} *** #### Stepdown Stepdown is one of my most important parameters for controlling cutting load. Instead of reducing feed per tooth to make a cut feel safer, I usually reduce stepdown.\ This keeps chip formation intact while lowering overall cutting forces in a controlled and predictable way. *** #### Stepover I prefer smaller stepover values because they lead to more predictable cutting forces.\ Compared to full slotting, smaller stepover reduces force variation and makes cutting behavior easier to control. There are cases where I use full slotting, but in those situations I adapt other parameters to reduce overall load. In general, I value predictable engagement over cutting strategies that introduce sudden force changes. *** #### Ramp Angle I use very shallow ramp angles, even if this approaches light cutting or brief rubbing during entry. The reason is simple: steep ramps can cause sudden force spikes, which I deliberately try to avoid. A shallow ramp increases engagement gradually, keeping cutting forces predictable and entry behavior calm. *** #### Ramp Feedrate I rarely adjust ramp feedrate separately.\ When ramp angles are shallow, ramping behaves very similarly to normal cutting. I consider reducing ramp feedrate only in special cases, such as helix ramps with many short segments that may cause data starvation. *** #### Plunge Feedrate I avoid direct plunging wherever possible. When a straight downward plunge is unavoidable, I use a very low plunge feedrate.\ Direct plunges are mechanically unfavorable and introduce high axial load with poor chip evacuation, so I treat them as a last resort. *** #### Engagement (overall) I control cutting forces primarily through engagement geometry — stepdown, stepover, and ramp angle — not by starving the tool of feed. *** #### Final note These views reflect experience, observation, and mistakes along the way.\ They are shared to make my reasoning understandable and reusable — not as rules to follow blindly. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://miwicnc.gitbook.io/miwicnc/cutting-parameters/parameter-philosophy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.