#unload macro moving out of range

13 messages · Page 1 of 1 (latest)

rigid fractal
#

i discovered something which could be a bug.
as far as I know, unload and load macros are supposed to be used while the printer is in idle mode. my intension this time was to change nozzles, so i set the kinematic position so i can move the z axis down. the motors for x and y were not engaged.
i have unloaded the filament of T1 with the nozzle tip forming macro was active. the console gave me the following:

Move out of range: 557.678 250.000 350.000 [-40.800]
19:11
Move out of range: 557.678 250.000 350.000 [-40.800]
19:11
Move out of range: 557.678 250.000 350.000 [-40.800]
19:11
Move out of range: 557.678 250.000 350.000 [-40.800]
19:11
Move out of range: 557.678 250.000 350.000 [-40.800]
19:11
RatOS: Filament unloaded! Please inspect the tip of the filament before reloading.
19:11
RatOS: Unloading filament from nozzle to cooling zone... Please wait!
19:11
RatOS | TEMPERATURE_WAIT: Temperature for toolhead T1 reached.
19:11
RatOS: please wait...
19:11
RatOS | TEMPERATURE_WAIT: Waiting for sensor: extruder1, MINIMUM: 220
19:11
RatOS: Heating T1 to 220C... Please wait.
19:11
Extruder extruder1 already active
19:11

INFO

Learn more about the RatOS Filament Macros
19:11
RatOS: WARNING: ONLY USE SET_CENTER_KINEMATIC_POSITION FOR DEBUGGING PURPOSES. YOU'RE OVERRIDING THE INTERNAL POSITIONING STATE OF THE PRINTER. PROCEED WITH CAUTION AND DO A PROPER G28 WHEN DONE.```

is that a bug that it moves out of range while not doing anything or what happened here? the kinematic set position at this time was 125/250/350 xyz
fossil spireBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

naive shale
#

never ever set the kinematic position

#

if you use it turn the motors off afterwards before you do anything else

rigid fractal
#

ok, so this error appears only because i havent done the M84 command after moving down the printbed?

naive shale
#

set kinematic position is only meant for debugging and testing purposes, it messes with the coordinate system, especially on the idex. it is not meant for normal use

#

if you use it turn the motors off afterwars

rigid fractal
#

yes, i am aware of that. i guess the error came because the M84 was not done before doing anything else. set kinematic position was just the fastest way to move the bed down.

#

so, the solution is: always M84 (turn off the motors) after set kinematic position

naive shale
#

yes

fossil spireBOT
rich spindle