After clicking the print button, a print stop will appear immediately

Basic Information:

Printer Model: V-Core 3.1
MCU / Printerboard: Octopus v1.1
Host / SBC: RPi4B
klippy.log
klippy (3).log (311.3 KB)

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:

Sorry, because I am Taiwanese, so the following content is translated using GOOGLE

My problem is that after I successfully uploaded the sliced ​​file, when I clicked to print, it immediately displayed a message that the print was terminated. I searched many places and still don’t know what the problem is.

start g-code:
START_PRINT EXTRUDER_TEMP={first_layer_temperature[0]} EXTRUDER_OTHER_LAYER_TEMP={nozzle_temperature[0]} BED_TEMP=[bed_temperature_initial_layer_single] CHAMBER_TEMP={overall_chamber_temperature} TOTAL_LAYER_COUNT={total_layer_count} X0={adaptive_bed_mesh_min[0]} Y0={adaptive_bed_mesh_min[1]} X1={adaptive_bed_mesh_max[0]} Y1={adaptive_bed_mesh_max[1]}


555.gcode (3.7 MB)

Hello @yimin !

Have you tried a different gcode file?

I tried 3 programs
superslicer, Prusa Slicer, Orca Slicer
I also tried different models, but the results were the same.

When I test this line alone, it works fine.
START_PRINT EXTRUDER_TEMP=240 BED_TEMP=80

I don’t think it has to do with the start code.

...
Stats 390.7: gcodein=0  mcu: mcu_awake=0.002 mcu_task_avg=0.000006 mcu_task_stddev=0.000004 bytes_write=87028 bytes_read=70380 bytes_retransmit=9 bytes_invalid=0 send_seq=3983 receive_seq=3983 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=179999662 rpi: mcu_awake=0.001 mcu_task_avg=0.000017 mcu_task_stddev=0.000019 bytes_write=1182 bytes_read=5760 bytes_retransmit=0 bytes_invalid=0 send_seq=161 receive_seq=161 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=49997252 adj=49998411 toolboard_t0: mcu_awake=0.002 mcu_task_avg=0.000014 mcu_task_stddev=0.000010 bytes_write=25157 bytes_read=48763 bytes_retransmit=9 bytes_invalid=0 send_seq=2135 receive_seq=2135 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=63999274 adj=63999595 Octopus_V1.1_F446: temp=28.4 EBB42_v1.2_T0: temp=33.0 raspberry_pi: temp=35.0  heater_bed: target=0 temp=28.5 pwm=0.000 sysload=0.17 cputime=8.529 memavail=3407540 print_time=387.424 buffer_time=0.000 print_stall=0 extruder: target=0 temp=26.0 pwm=0.000
Post-processing started via RatOS CLI: ['ratos', 'postprocess', '--non-interactive', '--allow-unknown-generator', '/home/pi/printer_data/gcodes/555.gcode']
Stats 391.7: gcodein=0  mcu: mcu_awake=0.002 mcu_task_avg=0.000006 mcu_task_stddev=0.000004 bytes_write=87174 bytes_read=70713 bytes_retransmit=9 bytes_invalid=0 send_seq=3994 receive_seq=3994 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=179999649 rpi: mcu_awake=0.001 mcu_task_avg=0.000017 mcu_task_stddev=0.000019 bytes_write=1188 bytes_read=5776 bytes_retransmit=0 bytes_invalid=0 send_seq=162 receive_seq=162 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=49997268 adj=49998312 toolboard_t0: mcu_awake=0.002 mcu_task_avg=0.000014 mcu_task_stddev=0.000010 bytes_write=25163 bytes_read=48866 bytes_retransmit=9 bytes_invalid=0 send_seq=2136 receive_seq=2136 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=63999270 adj=63999534 Octopus_V1.1_F446: temp=28.5 EBB42_v1.2_T0: temp=33.4 raspberry_pi: temp=35.5  heater_bed: target=0 temp=28.5 pwm=0.000 sysload=0.17 cputime=8.571 memavail=3398048 print_time=387.424 buffer_time=0.000 print_stall=0 extruder: target=0 temp=26.2 pwm=0.000
Stats 392.7: gcodein=0  mcu: mcu_awake=0.002 mcu_task_avg=0.000006 mcu_task_stddev=0.000004 bytes_write=87320 bytes_read=71046 bytes_retransmit=9 bytes_invalid=0 send_seq=4005 receive_seq=4005 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=179999642 rpi: mcu_awake=0.001 mcu_task_avg=0.000012 mcu_task_stddev=0.000016 bytes_write=1194 bytes_read=5805 bytes_retransmit=0 bytes_invalid=0 send_seq=163 receive_seq=163 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=49997283 adj=49998304 toolboard_t0: mcu_awake=0.002 mcu_task_avg=0.000014 mcu_task_stddev=0.000010 bytes_write=25169 bytes_read=48983 bytes_retransmit=9 bytes_invalid=0 send_seq=2137 receive_seq=2137 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=63999266 adj=63999502 Octopus_V1.1_F446: temp=28.3 EBB42_v1.2_T0: temp=33.2 raspberry_pi: temp=36.0  heater_bed: target=0 temp=28.6 pwm=0.000 sysload=0.17 cputime=8.606 memavail=3398780 print_time=387.424 buffer_time=0.000 print_stall=0 extruder: target=0 temp=26.1 pwm=0.000
Print aborted: 
Stats 393.7: gcodein=0  mcu: mcu_awake=0.002 mcu_task_avg=0.000006 mcu_task_stddev=0.000004 bytes_write=87466 bytes_read=71423 bytes_retransmit=9 bytes_invalid=0 send_seq=4016 receive_seq=4016 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=179999637 rpi: mcu_awake=0.001 mcu_task_avg=0.000012 mcu_task_stddev=0.000016 bytes_write=1200 bytes_read=5821 bytes_retransmit=0 bytes_invalid=0 send_seq=164 receive_seq=164 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=49997297 adj=49998265 toolboard_t0: mcu_awake=0.002 mcu_task_avg=0.000014 mcu_task_stddev=0.000010 bytes_write=25175 bytes_read=49101 bytes_retransmit=9 bytes_invalid=0 send_seq=2138 receive_seq=2138 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=63999261 adj=63999459 Octopus_V1.1_F446: temp=28.3 EBB42_v1.2_T0: temp=33.2 raspberry_pi: temp=36.0  heater_bed: target=0 temp=28.6 pwm=0.000 sysload=0.17 cputime=8.671 memavail=3405588 print_time=387.424 buffer_time=0.000 print_stall=0 extruder: target=0 temp=26.1 pwm=0.000
...

It happens directly after the Post-process of the gcode file.

What is interesting:

  • I do not know of any genuine Klipper message that reads “Print aborted”
  • At least in the logs, there is no macro that would generate this message
  • The colon in "Print aborted: " suggests that there should be a reason provided

Maybe try contacting the RatRig team to see what could be causing this. I have no idea.

Finally, I reinstalled the entire system and everything was back to normal. Thank you very much for your help.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.