Must home axis first: 25.000 25.000 259.627 [2268.955] with IDEAMAKER

General Discussion
1

Hi I point out a problem between klipper and idea maker. meanwhile my system . done like this:
Latest firmware version v0.10.0-464-g7f9ea231
core system XY
tm2209

dual extruder system

sensorless system

rasberry 4 b 4 giga memory

KlipperScreen**
v0.2.3-14-geedf544

moonraker
v0.7.1-586-ga8b9fc0

mainsail
v2.2.0

I tried in infinite ways acting on the macros on start_print and end_print etc., but the problem that is created when starting the second print does not go away. that is, when at the end of the print you perform a second new print the stepper motors do not activate causing the problem Must home axis first: 25.000 25.000 259.627 [2268.955].

this problem is between klipper and ideamaker using for example simplify3d does not arise the defect. I do not understand what is ineesca in the gcode of the press, but the stepper motors do not want to ignite. if I manually turn on with the string SET_STEPPER_ENABLE STEPPER=stepper_x ENABLE=1 then the problem is solved and the press starts.

finally I tried to eliminate M84 in the ideamaker end_print and in this case the engines are turned on, in the next print and then the print starts not presenting the problem of home failed.

2

If you issue a M84 the steppers are turned off and a reliable position is lost. In this case you need to home again. This is intended behavior.

3

hello, ok but if the same process I do using simplify 3d, everything is fine even leaving M84 in end_print

the fact is that it does not come home in the next new print, the engines do not enable so it can not be done the return home

if I use ideamaker the stepper motors do not activate in the new print and the return home fails, while if I use for example simplify3d everything is fine

4

Can you share the start and end gcode scrips of both of the slicers you use?

5

for single extruder :

start_print

G28
G90
M82
SET_LED LED=my_neopixel RED=1 GREEN=1 BLUE=1

M300 S440 P200
M300 S660 P250
M300 S880 P300
SET_PIN PIN=BEEPER_pin VALUE=0
SET_GCODE_OFFSET Z=0
BED_MESH_PROFILE LOAD=vetro_temperatura_ambiente

G1 Z15.0 F300
G1 X40 Y40 F3000
G92 E0
G1 F140 E29
G1 X20 Y0 F140 E40
G92 E0
G1 F{travel_xy_speed}
M117 Printing…
OFFSET_NYLON

end_print

M104 S0 T0; Spegnere estrusore

M104 S0 T1; Spegnere estrusore

M140 S0 ; Spegnere piatto

M106 S0 ; Object fan off

G1 E1 F200 ; Ritrae un poco di filamento

G1 X25 Y25 F3000

G90

G1 Z260 F600

M300 S440 P200

M300 S660 P250

M300 S880 P300

SET_LED LED=my_neopixel RED=0 GREEN=0 BLUE=0

SET_GCODE_OFFSET Z_ADJUST=0

BED_MESH_CLEAR

M84

6

I assume this are the scrips of the ideamaker.
As @Sineos already said, the M84 at the very end puts the steppers into a mode, where the position is not guaranteed any more.
So the printer is homed at the start of the next print.

Are you sure the M84 is at the end of the S3D end code.

Any how, it is always better to home the printer at every start of a new print.

7

yes sure, I’m using pretty much the same script on ideamaker and simplify3d except for small exceptions. M84 in simplify3d does not create problems at the new next printing, the stepper motors are enabled and then the home is done. in ideamaker no if I leave M84 at the end creates problems of enabling stepper engines in the next print and then the home is not done

the strange thing is that the engines do not turn on even if I create a macro to force the ignition

I noticed that if for example in mainsail I delete the print just performed and I run it again then the engines can turn on and the home is done

8

Please post a small file sliced with S3D and the same with IM.

9

ideamaker.zip (174.8 KB)
simplify3d.zip (70.1 KB)

10

Interesting, indeed both should turn off the stepper motors and force a homing.
If only the IM file is doing it, then IM is behaving correctly and S3D is not.

With M84, you are actively telling Klipper to turn off the steppers and this forces you to home. Remove the M84 if you do not want this behavior.

Edit: Please post a klippy.log file of an S3D print with this M84 command

11

meanwhile I attach the log file of the prints made with simplify3d. the prints were carried out successfully, no problem. keep in mind that I did all the new system installation I put from scratch os 32 bit raspberry, klipper mainsail moonraker etc so I’m sure the machine is at the top. the configuration of the printer file.cfg is not definitive are always in the experimental phase, the configuration of the printer file.cfg is not definitive are always in the experimental phase, the machine is complete with everything from the filament sensor to the webcam resonance and so on

klippy.zip (1.4 MB)

here is the klipper log idea maker file, when I launched the second next print the engines were turned off they did not start and therefore the home procedure was not performed and the system went wrong. I confirm that with idea maker a problem arises when you immediately perform a second print, the machine can not start the stepper engines and the home is not possible to run it.the two prints must be made in succession one after the other …

klipper log idea maker.zip (1.7 MB)

system
system1358×1406 117 KB

12

I also tried to configure everything using fluidd, clean installation from scratch. the problem remains not solved could be related to the firmware klipper against the slicer

in log fluidd I see an operating system error:

Starting heater checks for extruder

Starting heater checks for extruder1

Starting heater checks for heater_bed

Write g-code response

Traceback (most recent call last):

File “/home/pi/klipper/klippy/gcode.py”, line 446, in _respond_raw

os.write(self.fd, (msg+"\n").encode())

OSError: [Errno 11] Resource temporarily unavailable

Stats 11572.0: gcodein=0 mcu: mcu_awake=0.000 mcu_task_avg=0.000000 mcu_task_stddev=0.000000 bytes_write=3147 bytes_read=6172 bytes_retransmit=9 bytes_invalid=0 send_seq=263 receive_seq=263 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=167998452 heater_bed: target=0 temp=0.0 pwm=0.000 sysload=0.23 cputime=452.166 memavail=3565144 print_time=0.020 buffer_time=0.000 print_stall=0 extruder: target=0 temp=0.0 pwm=0.000 extruder1: target=0 temp=0.0 pwm=0.000

13

Sorry, no further idea.

14

don’t worry, I continue the tests as soon as I have results I attach them here. for now thanks

15

I update the situation. I updated to the final version the configuration mainsail klipper operating system … now the printer works well when a print with M84 in the final script is finished (and then the engines shut down), immediately restarting a new print the G28 command is executed well and then the new print proceeds well.

version mainsal system:

klipper
v0.10.0-494-gd3c4ba48

KlipperScreen
v0.2.3-14-geedf544

moonraker
v0.7.1-589-g4bed314

mainsail
v2.2.1

Sistema
Pacchetti SO update

trying everything with the fluidd system 1.82 all updated, the problem related to M84 is not solved , when I start a new print immediately the G28 command does not start and printing does not start. with Fluidd the problem is not solved…