Basic Information:
Printer Model: Geeetech i3
MCU / Printerboard: GT2560
Host / SBC raspberry pi 4, mainsailos
klippy.log (1015.0 KB)
klippy.log
Fill out above information and in all cases attach your klippy.log
file (use zip to compress it, if too big). Pasting your printer.cfg
is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
…
Hello
I installed the klipper firmware on a GEEETech i3 printer. Then I made a mainsailOS on an sd card with an imager. Mainsail sees the printer, but when I warm up the extruder or the bed, mainsail and the firmware restart.
It worked with Merlin firmware and octoprint.
hcet14
January 2, 2025, 2:11pm
2
...
Stats 5681.0: gcodein=0 mcu: mcu_awake=0.010 mcu_task_avg=0.000093 mcu_task_stddev=0.000073 bytes_write=2532 bytes_read=8044 bytes_retransmit=9 bytes_invalid=6 send_seq=228 receive_seq=228 retransmit_seq=2 srtt=0.010 rttvar=0.005 rto=0.031 ready_bytes=0 upcoming_bytes=0 freq=16000333 heater_bed: target=50 temp=20.1 pwm=1.000 sysload=0.00 cputime=2.229 memavail=3487540 print_time=20.220 buffer_time=0.000 print_stall=0 extruder: target=200 temp=18.9 pwm=1.000
Stats 5682.0: gcodein=0 mcu: mcu_awake=0.010 mcu_task_avg=0.000093 mcu_task_stddev=0.000073 bytes_write=2577 bytes_read=8164 bytes_retransmit=9 bytes_invalid=6 send_seq=233 receive_seq=233 retransmit_seq=2 srtt=0.010 rttvar=0.004 rto=0.026 ready_bytes=0 upcoming_bytes=0 freq=16000333 heater_bed: target=50 temp=19.7 pwm=1.000 sysload=0.00 cputime=2.250 memavail=3487304 print_time=20.220 buffer_time=0.000 print_stall=0 extruder: target=200 temp=18.6 pwm=1.000
Stats 5683.0: gcodein=0 mcu: mcu_awake=0.010 mcu_task_avg=0.000093 mcu_task_stddev=0.000073 bytes_write=2615 bytes_read=8288 bytes_retransmit=9 bytes_invalid=6 send_seq=236 receive_seq=236 retransmit_seq=2 srtt=0.010 rttvar=0.005 rto=0.029 ready_bytes=0 upcoming_bytes=0 freq=16000338 heater_bed: target=50 temp=20.3 pwm=1.000 sysload=0.00 cputime=2.272 memavail=3487304 print_time=20.220 buffer_time=0.000 print_stall=0 extruder: target=200 temp=18.4 pwm=1.000
Stats 5684.0: gcodein=0 mcu: mcu_awake=0.010 mcu_task_avg=0.000093 mcu_task_stddev=0.000075 bytes_write=2650 bytes_read=8426 bytes_retransmit=9 bytes_invalid=6 send_seq=239 receive_seq=239 retransmit_seq=2 srtt=0.009 rttvar=0.005 rto=0.028 ready_bytes=0 upcoming_bytes=0 freq=16000338 heater_bed: target=50 temp=19.1 pwm=1.000 sysload=0.00 cputime=2.294 memavail=3487304 print_time=20.220 buffer_time=0.000 print_stall=0 extruder: target=200 temp=17.2 pwm=1.000
Stats 5685.0: gcodein=0 mcu: mcu_awake=0.010 mcu_task_avg=0.000093 mcu_task_stddev=0.000075 bytes_write=2677 bytes_read=8536 bytes_retransmit=9 bytes_invalid=6 send_seq=242 receive_seq=242 retransmit_seq=2 srtt=0.010 rttvar=0.004 rto=0.026 ready_bytes=0 upcoming_bytes=0 freq=16000337 heater_bed: target=50 temp=19.7 pwm=1.000 sysload=0.00 cputime=2.315 memavail=3487304 print_time=20.220 buffer_time=0.000 print_stall=0 extruder: target=200 temp=18.4 pwm=1.000
Heater extruder no longer approaching target 200.000
Stats 5686.0: gcodein=0 mcu: mcu_awake=0.010 mcu_task_avg=0.000093 mcu_task_stddev=0.000075 bytes_write=2738 bytes_read=8675 bytes_retransmit=9 bytes_invalid=6 send_seq=248 receive_seq=248 retransmit_seq=2 srtt=0.009 rttvar=0.004 rto=0.027 ready_bytes=0 upcoming_bytes=0 freq=16000335 heater_bed: target=50 temp=20.3 pwm=1.000 sysload=0.00 cputime=2.339 memavail=3487304 print_time=20.220 buffer_time=0.000 print_stall=0 extruder: target=200 temp=18.6 pwm=1.000
Heater extruder not heating at expected rate
Transition to shutdown state: Heater extruder not heating at expected rate
See the 'verify_heater' section in docs/Config_Reference.md
for the parameters that control this check.
...
Hotend and bed get the command to heat up, but Klipper gets the information: They don’t. So the thermal runaway protection kicks in.
The MCU may be back-powered by the Pi, and there is no proper power for bed and hotend (printer turned off) as both do not heat.
1 Like
I used this file for the setup, unfortunately it doesn’t work.
Thank you, I can access the mainsail in a browser, as soon as I heat the extruder or bad, the printer turns off and the firmware restarts.
My first printer, approx. I used it 1 month ago with marlin. I am still inexperienced in 3d printing and printer settings. If you could advise me on what to change in the settings, I would appreciate it.
These look ok.
Check for the powering. Do the motors move (homing)?
hcet14
January 2, 2025, 7:32pm
7
So assuming your printer is electrically ok and your printer.cfg is faulty, you may go the Marlin reverse way.
https://ww1.microchip.com/downloads/aemDocuments/documents/OTH/ProductDocuments/DataSheets/ATmega640-1280-1281-2560-2561-Datasheet-DS40002211A.pdf figure 1-1 or 1-3 is your ATmega2560 (MCU on your printer board) package (have a look at your printer board or post a picture).
Marlin uses the numbering of the package, Klipper uses the port names (e.g. 1(Marlin)=PG5(Klipper)). Marlin/Marlin/src/pins/mega/pins_GT2560_REV_A.h at bugfix-2.1.x · MarlinFirmware/Marlin · GitHub is the pin definition in Marlin. Check your printer.cfg if you use the right heater_pin(s).
Sineos
January 2, 2025, 9:51pm
8
balu999:
GEEETech i3
Given this information and the GT2560_REV_A data is correct, then the pins in your configuration should be correct.
As indicated by @EddyMI3D , check for the correct powering of the board. Measure the supply voltage and check if there is any power at the respective heater pins when the heaters are turned on.
Nem mozognak a motorok, ma e
klippy.log (1).txt (159.8 KB)
llenőriztem.
Ignore my previous comment, I did a wrong test , I was stupid and didn’t turn on the printer .
So the motors go in the x, z, y direction as well. However, on the x axis, when it moves to the right, the printhead hits the z axis (there is no limit switch there, then I will put one there). The klippy log still shows an error when heating the bed and the extruder.
balu999
January 6, 2025, 11:11am
11
the printer works, it doesn’t print well yet, I’m testing the settings.
if someone has a similar problem, I will send the printer.cfg