Printer wont start printing

General Discussion
1

Basic Information:

Printer Model: Ender3
MCU / Printerboard: Skr E2 V2
klippy.log

Describe your issue: Hello , since today when i’m clicking on print (I’m Using octopy) , Nothing will react , it will change the name displayed in the “state” section , but that’s it , the printer won’t heat up , won’t move , and there is not any report there …

There is the last line of the log file

Starting heater checks for heater_bed
Starting heater checks for extruder

2

[gcode_macro START_PRINT]
gcode:
{% set BED_TEMP = params.BED_TEMP|default(60)|float %}
{% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(190)|float %}
# Start bed heating
M140 S{BED_TEMP}
# Use absolute coordinates
G90
# Home the printer
G28
# Move the nozzle near the bed
G1 Z5 F3000
# Move the nozzle very close to the bed
G1 Z0.15 F300
# Wait for bed to reach temperature
M190 S{BED_TEMP}
# Set and wait for nozzle to reach temperature
M109 S{EXTRUDER_TEMP}

Here is my Start Gcode

3

Is the printer turned on?
Creality printer suffer from the issue of backpowering. That makes the LCD lit, but the printer wont work.

4

It is, it will react from control panel or temperature panel

1 Like
5

Can you please share the klippy.log?

6

Klippy.log (8.3 KB)

7

You have these issues:

Must home axis first: 10.000 0.000 -0.014 [0.000]
Must home axis first: 10.000 0.000 -0.014 [0.000]
Must home axis first: 0.000 10.000 0.000 [0.000]

and

Got EOF when reading from device
Timeout with MCU 'mcu' (eventtime=1556.409791)
Transition to shutdown state: Lost communication with MCU 'mcu'

You may take care to run a G28 before any move.

You also may check the USB connection.

How does the Gcode file you want to print looks like? (You may attach it as a zipped file)

8

I know, it will react from the control panel, so no usb trouble

The gcode is perfectly fine, I have already printed it with this configuration

9

Are you searching for support or are you here to tell us that everything is working?
As @EddyMI3D already pointed out:

  • According to your log, you did not home (G28) before you start printing
  • Your start gcode contains a G28

So @EddyMI3D question for a example gcode file is absolutely valid, since apparently something is wrong.

1 Like
10

Looking for help, but since I’m not on my printer’s network i can’t give you those gcode.

But those gcode were working, already tried to home before clicking on print, and also tried to heat bed and nozzle before, nothing changed.

The home error you have seen its due a move I’ve tried by control panel but i forgot to home before.

11

Well, then we should get a klippy.log that actually shows this behavior. Try

  1. sudo service klipper stop
  2. rm /tmp/klippy.log # or wherever you have the klippy.log
  3. sudo service klipper start
  4. Connect octoprint and start a print
  5. Wait
  6. Post the new klippy.log
12

klippy.log (5.9 KB)
here it is

13

The log is strange. Klipper seems to have correctly started but it seems somehow dead. No status messages, no temperature, just nothing.

No idea currently. Maybe completely power off the board and the RPi but this is kind of a long shot

14

Still Nothing

And the log are exactly the same

15

Anyone have any other idea to test ?

16

So please upload a gcode file you want to print.

17

CE3_xyzcalibration-cube-1.gcode (217.6 KB)
Here it is

18 
G92 E0
G92 E0
G1 F2700 E-5  ; <-  Retraction
;LAYER_COUNT:54
;LAYER:0
M107
G0 F6000 X82.399 Y98.887 Z0.2
G0 X78.501 Y108.018
;TYPE:SKIRT
G1 F2700 E0
G1 F1200 X78.51 Y107.353 E0.0282

There is a retraction of 5 millimeters at the start but no de-retraction.

So the printer has to print 66 lines of code to get out some filament from the nozzle.

19

Okey about that, but, what about before?
It won’t make any move, not any heating, not homing, not any error, nothing happens

20

Have you restarted Klipper?