From ef7e286755d8ba6d972bdfaeede6eed403372ee2 Mon Sep 17 00:00:00 2001 From: "D.R.racer" Date: Thu, 2 Mar 2023 15:55:08 +0100 Subject: [PATCH] Set cutting current after planning cutting move Should apply the correct cutting current now (MoveToSlot sets its own current which needs to be overriden for cutting) --- src/logic/cut_filament.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/logic/cut_filament.cpp b/src/logic/cut_filament.cpp index 926639b..f3d51cb 100644 --- a/src/logic/cut_filament.cpp +++ b/src/logic/cut_filament.cpp @@ -106,12 +106,12 @@ bool CutFilament::StepInner() { case ProgressCode::DisengagingIdler: if (mi::idler.Disengaged()) { state = ProgressCode::PerformingCut; - // set highest available current for the Selector - ms::selector.SetCurrents(mg::globals.CutIRunCurrent(), config::selector.iHold); // lower move speed savedSelectorFeedRate_mm_s = mg::globals.SelectorFeedrate_mm_s().v; mg::globals.SetSelectorFeedrate_mm_s(mg::globals.SelectorHomingFeedrate_mm_s().v); MoveSelector(cutSlot); // let it cut :) + // set highest available current for the Selector - should be placed after the planned move because the move sets the default running current + ms::selector.SetCurrents(mg::globals.CutIRunCurrent(), config::selector.iHold); } break; case ProgressCode::PerformingCut: