Jump to content
  • 0

Voron 2.4 print start location


nannyogg82

Question

Hi, first time post here. I bought a Voron 2.4 kit a few months ago and have finally got it completed. But now I am having issues with the print start location.

So far I have only managed to actually start a print once. But it wasn't adhering. Between this failed print and trying again, I reset the Z offset and I also installed Klipper Screen, and every time since then I have tried to start a print, the print head lowers itself over the Z endstop as pictured and tries to print there. This happens with both Super Slicer and Cura. You can actually see the damage on the printhead due to banging against the Z endstop.

Does anyone have any suggestions of how to fix this? I have tried looking in the config file but I am at a bit of a loss.

image0.jpeg

image1.jpeg

Link to comment
Share on other sites

Recommended Posts

  • 0
17 minutes ago, nannyogg82 said:

It couldn’t be the firmware on the Octopus board could it?

If your printer is moving then the firmware should be fine.

Try going through your printer.cfg. Each motor has a section [stepper_x], [stepper_y] and [stepper_z]. within the X and Y sections you need to uncomment (remove the "#") for the lines that match your build.

##--------------------------------------------------------------------

##  Uncomment below for 250mm build
#position_endstop: 250
#position_max: 250

##  Uncomment for 300mm build
#position_endstop: 300
#position_max: 300

##  Uncomment for 350mm build
#position_endstop: 350
#position_max: 350

If the config file doesn't specify these values then Klipper assumes that your printer homes at 0,0.

Link to comment
Share on other sites

  • 0
1 minute ago, atrushing said:

If your printer is moving then the firmware should be fine.

Try going through your printer.cfg. Each motor has a section [stepper_x], [stepper_y] and [stepper_z]. within the X and Y sections you need to uncomment (remove the "#") for the lines that match your build.

##--------------------------------------------------------------------

##  Uncomment below for 250mm build
#position_endstop: 250
#position_max: 250

##  Uncomment for 300mm build
#position_endstop: 300
#position_max: 300

##  Uncomment for 350mm build
#position_endstop: 350
#position_max: 350

If the config file doesn't specify these values then Klipper assumes that your printer homes at 0,0.

I checked that earlier. Was all good. The confit file should be the same as the very first time I managed to get it to print. I’m flummoxed 

Link to comment
Share on other sites

  • 0
27 minutes ago, nannyogg82 said:

I’m flummoxed

The config was the trickiest part of the build for me..

If the machine is physically working and it homes correctly, then it might be worth going back to a fresh config. Copy your current printer.cfg out. Load in a stock config. Then open both of them side by side and edit the new config from top to bottom with values from your current printer.cfg.

This lets you sanity check everything and see the default values while you go.

If you upload your current printer.cfg we can try to give it a look over.

Link to comment
Share on other sites

  • 0
1 minute ago, atrushing said:

The config was the trickiest part of the build for me..

If the machine is physically working and it homes correctly, then it might be worth going back to a fresh config. Copy your current printer.cfg out. Load in a stock config. Then open both of them side by side and edit the new config from top to bottom with values from your current printer.cfg.

This lets you sanity check everything and see the default values while you go.

If you upload your current printer.cfg we can try to give it a look over.

 

# This file contains common pin mappings for the BigTreeTech Octopus V1.
# To use this config, the firmware should be compiled for the STM32F446 with a "32KiB bootloader"
# Enable "extra low-level configuration options" and select the "12MHz crystal" as clock reference

# after running "make", copy the generated "klipper/out/klipper.bin" file to a
# file named "firmware.bin" on an SD card and then restart the OctoPus with that SD card.

# See docs/Config_Reference.md for a description of parameters.

## Voron Design VORON2 250/300/350mm BigTreeTech OctoPus V1 TMC2209 UART config

## *** THINGS TO CHANGE/CHECK: ***
## MCU paths                            [mcu] section
## Thermistor types                     [extruder] and [heater_bed] sections - See https://www.klipper3d.org/Config_Reference.html#common-thermistors for common thermistor types
## Z Endstop Switch location            [safe_z_home] section
## Homing end position                  [gcode_macro G32] section
## Z Endstop Switch  offset for Z0      [stepper_z] section
## Probe points                         [quad_gantry_level] section
## Min & Max gantry corner postions     [quad_gantry_level] section
## PID tune                             [extruder] and [heater_bed] sections
## Probe pin                            [probe] section
## Fine tune E steps                    [extruder] section

[mcu]
##  Obtain definition by "ls -l /dev/serial/by-id/" then unplug to verify
##--------------------------------------------------------------------
serial: /dev/serial/by-id/usb-Klipper_stm32f446xx_2F0029000A50315939343520-if00 
restart_method: command
##--------------------------------------------------------------------

[include mainsail.config]

[printer]
kinematics: corexy
max_velocity: 300  
max_accel: 3000             #Max 4000
max_z_velocity: 15          #Max 15 for 12V TMC Drivers, can increase for 24V
max_z_accel: 350
square_corner_velocity: 5.0

#####################################################################
#   X/Y Stepper Settings
#####################################################################

##  B Stepper - Left
##  Connected to MOTOR_0
##  Endstop connected to DIAG_0
[stepper_x]
step_pin: PF13
dir_pin: PF12
enable_pin: !PF14
rotation_distance: 40
microsteps: 32
full_steps_per_rotation:200  #set to 400 for 0.9 degree stepper
endstop_pin: PG6
position_min: 0
##--------------------------------------------------------------------

##  Uncomment below for 250mm build
#position_endstop: 250
#position_max: 250

##  Uncomment for 300mm build
#position_endstop: 300
#position_max: 300

##  Uncomment for 350mm build
position_endstop: 350
position_max: 350

##--------------------------------------------------------------------
homing_speed: 25   #Max 100
homing_retract_dist: 5
homing_positive_dir: true

##  Make sure to update below for your relevant driver (2208 or 2209)
[tmc2209 stepper_x]
uart_pin: PC4
interpolate: false
run_current: 0.8
sense_resistor: 0.110
stealthchop_threshold: 0

##  A Stepper - Right
##  Connected to MOTOR_1
##  Endstop connected to DIAG_1
[stepper_y]
step_pin: PG0
dir_pin: !PG1
enable_pin: !PF15
rotation_distance: 40
microsteps: 32
full_steps_per_rotation:200  #set to 400 for 0.9 degree stepper
endstop_pin: PG9
position_min: 0
##--------------------------------------------------------------------

##  Uncomment for 250mm build
#position_endstop: 250
#position_max: 250

##  Uncomment for 300mm build
#position_endstop: 300
#position_max: 300

##  Uncomment for 350mm build
position_endstop: 350
position_max: 350

##--------------------------------------------------------------------
homing_speed: 25  #Max 100
homing_retract_dist: 5
homing_positive_dir: true

##  Make sure to update below for your relevant driver (2208 or 2209)
[tmc2209 stepper_y]
uart_pin: PD11
interpolate: false
run_current: 0.8
sense_resistor: 0.110
stealthchop_threshold: 0
 
#####################################################################
#   Z Stepper Settings
#####################################################################

## Z0 Stepper - Front Left
##  Connected to MOTOR_2
##  Endstop connected to DIAG_2
[stepper_z]
step_pin: PF11
dir_pin: PG3
enable_pin: !PG5
rotation_distance: 40
gear_ratio: 80:16
microsteps: 32
endstop_pin: PG10
##  Z-position of nozzle (in mm) to z-endstop trigger point relative to print surface (Z0)
##  (+) value = endstop above Z0, (-) value = endstop below
##  Increasing position_endstop brings nozzle closer to the bed
##  After you run Z_ENDSTOP_CALIBRATE, position_endstop will be stored at the very end of your config
#position_endstop: -0.5
##--------------------------------------------------------------------

##  Uncomment below for 250mm build
#position_max: 210

##  Uncomment below for 300mm build
#position_max: 260

##  Uncomment below for 350mm build
position_max: 330

##--------------------------------------------------------------------
position_min: -5
homing_speed: 8
second_homing_speed: 3
homing_retract_dist: 3

##  Make sure to update below for your relevant driver (2208 or 2209)
[tmc2209 stepper_z]
uart_pin: PC6
interpolate: false
run_current: 0.8
sense_resistor: 0.110
stealthchop_threshold: 0

##  Z1 Stepper - Rear Left
##  Connected to MOTOR_3
[stepper_z1]
step_pin: PG4
dir_pin: !PC1
enable_pin: !PA0
rotation_distance: 40
gear_ratio: 80:16
microsteps: 32

##  Make sure to update below for your relevant driver (2208 or 2209)
[tmc2209 stepper_z1]
uart_pin: PC7
interpolate: false
run_current: 0.8
sense_resistor: 0.110
stealthchop_threshold: 0

##  Z2 Stepper - Rear Right
##  Connected to MOTOR_4
[stepper_z2]
step_pin: PF9
dir_pin: PF10
enable_pin: !PG2
rotation_distance: 40
gear_ratio: 80:16
microsteps: 32

##  Make sure to update below for your relevant driver (2208 or 2209)
[tmc2209 stepper_z2]
uart_pin: PF2
interpolate: false
run_current: 0.8
sense_resistor: 0.110
stealthchop_threshold: 0

##  Z3 Stepper - Front Right
##  Connected to MOTOR_5
[stepper_z3]
step_pin: PC13
dir_pin: !PF0
enable_pin: !PF1
rotation_distance: 40
gear_ratio: 80:16
microsteps: 32

##  Make sure to update below for your relevant driver (2208 or 2209)
[tmc2209 stepper_z3]
uart_pin: PE4
interpolate: false
run_current: 0.8
sense_resistor: 0.110
stealthchop_threshold: 0


#####################################################################
#   Extruder
#####################################################################

##  Connected to MOTOR_6
##  Heater - HE0
##  Thermistor - T0
[extruder]
step_pin: PE2
dir_pin: PE3
enable_pin: !PD4
##  Update value below when you perform extruder calibration
##  If you ask for 100mm of filament, but in reality it is 98mm:
##  rotation_distance = <previous_rotation_distance> * <actual_extrude_distance> / 100
##  22.6789511 is a good starting point
rotation_distance: 23.132530122   #Bondtech 5mm Drive Gears
##  Update Gear Ratio depending on your Extruder Type
##  Use 50:17 for Afterburner/Clockwork (BMG Gear Ratio)
##  Use 80:20 for M4, M3.1
gear_ratio: 50:17               #BMG Gear Ratio
microsteps: 32
full_steps_per_rotation: 200    #200 for 1.8 degree, 400 for 0.9 degree
nozzle_diameter: 0.400
filament_diameter: 1.75
heater_pin: PA2
## Check what thermistor type you have. See https://www.klipper3d.org/Config_Reference.html#common-thermistors for common thermistor types.
## Use "Generic 3950" for NTC 100k 3950 thermistors
sensor_type: Generic 3950
sensor_pin: PF4
min_temp: 10
max_temp: 270
max_power: 1.0
min_extrude_temp: 20
#control = pid
#pid_kp = 26.213
#pid_ki = 1.304
#pid_kd = 131.721
##  Try to keep pressure_advance below 1.0
#pressure_advance: 0.05
##  Default is 0.040, leave stock
#pressure_advance_smooth_time: 0.040

##  E0 on MOTOR6
##  Make sure to update below for your relevant driver (2208 or 2209)
[tmc2209 extruder]
uart_pin: PE1
interpolate: false
run_current: 0.5
sense_resistor: 0.110
stealthchop_threshold: 0


#####################################################################
#   Bed Heater
#####################################################################

##  SSR Pin - HE1
##  Thermistor - TB
[heater_bed]
##  Uncomment the following line if using the default SSR wiring from the docs site
heater_pin: PA3
##  Other wiring guides may use BED_OUT to control the SSR. Uncomment the following line for those cases
#heater_pin: PA1
## Check what thermistor type you have. See https://www.klipper3d.org/Config_Reference.html#common-thermistors for common thermistor types.
## Use "Generic 3950" for Keenovo heaters
sensor_type: Generic 3950
sensor_pin: PF3
##  Adjust Max Power so your heater doesn't warp your bed. Rule of thumb is 0.4 watts / cm^2 .
max_power: 0.6
min_temp: 0
max_temp: 120
#control: pid
#pid_kp: 58.437
#pid_ki: 2.347
#pid_kd: 363.769

#####################################################################
#   Probe
#####################################################################

##  Inductive Probe
##  This probe is not used for Z height, only Quad Gantry Leveling
[probe]

#--------------------------------------------------------------------

## Select the probe port by type:
## For the PROBE port. Will not work with Diode. May need pull-up resistor from signal to 24V.
#pin: ~!PB7
## For the DIAG_7 port. NEEDS BAT85 DIODE! Change to !PG15 if probe is NO.
pin: PG15
## For Octopus Pro PROBE port; NPN and PNP proximity switch types can be set by jumper
#pin: ~!PC5

#--------------------------------------------------------------------

x_offset: 0
y_offset: 25.0
z_offset: 0
speed: 10.0
samples: 3
samples_result: median
sample_retract_dist: 3.0
samples_tolerance: 0.006
samples_tolerance_retries: 3

#####################################################################
#   Fan Control
#####################################################################

##  Print Cooling Fan - FAN0
[fan]
pin: PA8
kick_start_time: 0.5
##  Depending on your fan, you may need to increase this value
##  if your fan will not start. Can change cycle_time (increase)
##  if your fan is not able to slow down effectively
off_below: 0.10


##  Hotend Fan - FAN1
[heater_fan hotend_fan]
pin: PE5
max_power: 1.0
kick_start_time: 0.5
heater: extruder
heater_temp: 50.0
##  If you are experiencing back flow, you can reduce fan_speed
#fan_speed: 1.0

##  Controller fan - FAN2
[controller_fan controller_fan]
pin: PD12
kick_start_time: 0.5
heater: heater_bed

##  Exhaust fan - FAN3
#[heater_fan exhaust_fan]
#pin: PD13
#max_power: 1.0
#shutdown_speed: 0.0
#kick_start_time: 5.0
#heater: heater_bed
#heater_temp: 60
#fan_speed: 1.0

#####################################################################
#   LED Control
#####################################################################

## Chamber Lighting - HE2 Connector (Optional)
#[output_pin caselight]
#pin: PB10
#pwm:true
#shutdown_value: 0
#value:1
#cycle_time: 0.01

#####################################################################
#   Homing and Gantry Adjustment Routines
#####################################################################

[idle_timeout]
timeout: 1800

[safe_z_home]
##  XY Location of the Z Endstop Switch
##  Update -10,-10 to the XY coordinates of your endstop pin 
##  (such as 157,305) after going through Z Endstop Pin
##  Location Definition step.
home_xy_position:234,350
speed:100
z_hop:10


##  Use QUAD_GANTRY_LEVEL to level a gantry.
##  Min & Max gantry corners - measure from nozzle at MIN (0,0) and 
##  MAX (250, 250), (300,300), or (350,350) depending on your printer size
##  to respective belt positions
[quad_gantry_level]

#--------------------------------------------------------------------
##  Gantry Corners for 250mm Build
##  Uncomment for 250mm build
#gantry_corners:
#   -60,-10
#   310, 320
##  Probe points
#points:
#   50,25
#   50,175
#   200,175
#   200,25
    
##  Gantry Corners for 300mm Build
##  Uncomment for 300mm build
#gantry_corners:
#   -60,-10
#   360,370
##  Probe points
#points:
#   50,25
#   50,225
#   250,225
#   250,25

##  Gantry Corners for 350mm Build
##  Uncomment for 350mm build
gantry_corners:
   -60,-10
   410,420
##  Probe points
points:
   50,25
   50,275
   300,275
   300,25

#--------------------------------------------------------------------
speed: 100
horizontal_move_z: 10
retries: 5
retry_tolerance: 0.0075
max_adjust: 10

########################################
# EXP1 / EXP2 (display) pins
########################################

[board_pins]
aliases:
    # EXP1 header
    EXP1_1=PE8, EXP1_2=PE7,
    EXP1_3=PE9, EXP1_4=PE10,
    EXP1_5=PE12, EXP1_6=PE13,    # Slot in the socket on this side
    EXP1_7=PE14, EXP1_8=PE15,
    EXP1_9=<GND>, EXP1_10=<5V>,

    # EXP2 header
    EXP2_1=PA6, EXP2_2=PA5,
    EXP2_3=PB1, EXP2_4=PA4,
    EXP2_5=PB2, EXP2_6=PA7,      # Slot in the socket on this side
    EXP2_7=PC15, EXP2_8=<RST>,
    EXP2_9=<GND>, EXP2_10=<5V>

#####################################################################
#   Displays
#####################################################################

##  Uncomment the display that you have
#--------------------------------------------------------------------


##  RepRapDiscount 128x64 Full Graphic Smart Controller
#[display]
#lcd_type: st7920
#cs_pin: EXP1_4
#sclk_pin: EXP1_5
#sid_pin: EXP1_3
#menu_timeout: 40
#encoder_pins: ^EXP2_5, ^EXP2_3
#click_pin: ^!EXP1_2

#[output_pin beeper]
#pin: EXP1_1

#--------------------------------------------------------------------


##  mini12864 LCD Display
#[display]
#lcd_type: uc1701
#cs_pin: EXP1_3
#a0_pin: EXP1_4
#rst_pin: EXP1_5
#encoder_pins: ^EXP2_5, ^EXP2_3
#click_pin: ^!EXP1_2
#contrast: 63
#spi_software_miso_pin: EXP2_1
#spi_software_mosi_pin: EXP2_6
#spi_software_sclk_pin: EXP2_2

##  To control Neopixel RGB in mini12864 display
#[neopixel btt_mini12864]
#pin: EXP1_6
#chain_count: 3
#initial_RED: 0.1
#initial_GREEN: 0.5
#initial_BLUE: 0.0
#color_order: RGB

##  Set RGB values on boot up for each Neopixel. 
##  Index 1 = display, Index 2 and 3 = Knob
#[delayed_gcode setdisplayneopixel]
#initial_duration: 1
#gcode:
#        SET_LED LED=btt_mini12864 RED=1 GREEN=1 BLUE=1 INDEX=1 TRANSMIT=0
#        SET_LED LED=btt_mini12864 RED=1 GREEN=0 BLUE=0 INDEX=2 TRANSMIT=0
#        SET_LED LED=btt_mini12864 RED=1 GREEN=0 BLUE=0 INDEX=3 

#--------------------------------------------------------------------


#####################################################################
#   Macros
#####################################################################

[gcode_macro G32]
gcode:
    SAVE_GCODE_STATE NAME=STATE_G32
    G90
    G28
    QUAD_GANTRY_LEVEL
    G28
    ##  Uncomment for for your size printer:
    #--------------------------------------------------------------------
    ##  Uncomment for 250mm build
    #G0 X125 Y125 Z30 F3600
    
    ##  Uncomment for 300 build
    #G0 X150 Y150 Z30 F3600
    
    ##  Uncomment for 350mm build
    G0 X175 Y175 Z30 F3600
    #--------------------------------------------------------------------
    RESTORE_GCODE_STATE NAME=STATE_G32


#   Use PRINT_START for the slicer starting script - please customise for your slicer of choice
[gcode_macro PRINT_START]
gcode:
    G32                            ; home all axes
    G90                            ; absolute positioning
    G1 Z20 F3000                   ; move nozzle away from bed
   

#   Use PRINT_END for the slicer ending script - please customise for your slicer of choice
[gcode_macro PRINT_END]
gcode:
    # safe anti-stringing move coords
    {% set th = printer.toolhead %}
    {% set x_safe = th.position.x + 20 * (1 if th.axis_maximum.x - th.position.x > 20 else -1) %}
    {% set y_safe = th.position.y + 20 * (1 if th.axis_maximum.y - th.position.y > 20 else -1) %}
    {% set z_safe = [th.position.z + 2, th.axis_maximum.z]|min %}
    
    SAVE_GCODE_STATE NAME=STATE_PRINT_END
    
    M400                           ; wait for buffer to clear
    G92 E0                         ; zero the extruder
    G1 E-5.0 F1800                 ; retract filament
    
    TURN_OFF_HEATERS
    
    G90                                      ; absolute positioning
    G0 X{x_safe} Y{y_safe} Z{z_safe} F20000  ; move nozzle to remove stringing
    G0 X{th.axis_maximum.x//2} Y{th.axis_maximum.y - 2} F3600  ; park nozzle at rear
    M107                                     ; turn off fan
    
    BED_MESH_CLEAR
    RESTORE_GCODE_STATE NAME=STATE_PRINT_END

#*# <---------------------- SAVE_CONFIG ---------------------->
#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.
#*#
#*# [heater_bed]
#*# control = pid
#*# pid_kp = 39.888
#*# pid_ki = 1.773
#*# pid_kd = 224.371
#*#
#*# [extruder]
#*# control = pid
#*# pid_kp = 22.985
#*# pid_ki = 1.161
#*# pid_kd = 113.778
#*#
#*# [stepper_z]
#*# position_endstop = 1.196
 

 

Link to comment
Share on other sites

  • 0

nannyog82...

Before you go farting around with Klipper, I think it would be wise to determine whether the problem is with you printer or with the slicer software, and maybe you have and I'm on the wrong track. I know you already tried with SS and Cura but I just want to confirm.

If you do a home x,y,z (G28).  Are you able to do a (G90 then G0 X0 Y0 Z100 F5000) to move the printhead to 0,0,100? Or any absolute or relative manual move using the console?

If you can manually move the printhead with G-Codes from the console (command line) then I don't think the printer is your problem.

If you can't move it or it moves to the incorrect position... then it's definitely the printer.

So... Can you move the print head manually?

 

Link to comment
Share on other sites

  • 0
6 minutes ago, Penatr8tor said:

nannyog82...

Before you go farting around with Klipper, I think it would be wise to determine whether the problem is with you printer or with the slicer software, and maybe you have and I'm on the wrong track. I know you already tried with SS and Cura but I just want to confirm.

If you do a home x,y,z (G28).  Are you able to do a (G90 then G0 X0 Y0 Z100 F5000) to move the printhead to 0,0,100? Or any absolute or relative manual move using the console?

If you can manually move the printhead with G-Codes from the console (command line) then I don't think the printer is your problem.

If you can't move it or it moves to the incorrect position... then it's definitely the printer.

So... Can you move the print head manually?

Yup. I can move the print head to the absolute position you gave. 

  • Like 1
Link to comment
Share on other sites

  • 0
1 hour ago, nannyogg82 said:

It couldn’t be the firmware on the Octopus board could it?

I would say "no", the klipper firmware on the MCU (Octopus board or whatever) is really "simple". All the intelligence and calculations are done by the klipper software running on the PI. Basically the firmware on the MCU is just a thin interface layer that allows the software on the PI to interact with the MCU hardware (read and set stuff). There's nothing stored on the MCU board itself (in terms of config) this is very different to something like Marlin where it does store config and the "intelligence" on the MCU board.

  • Like 1
Link to comment
Share on other sites

  • 0

@Penatr8tor ROFL I'd said earlier the opposite (it's possilby the way the  printer is "interpreting" the GCODE).

@nannyogg82 has posted the Voron test cube Gcode that he was trying (and failing) to print. I managed to print that on one of my printers fine, and having had a look at the GCODE can't see anything out of the ordinary (well nothing that makes it look like it would career off the print area). So in my view the slicer(s) were working fine.

Given that manual moves (via GCODE) work; there's no errors displayed on the console; the generated GCODE file looks sane and prints (elsewhere) the only things I can think of are:

1) Get some kind soul with a known good set up to generate some GCODE and provide that (takes away doubt about slicers).

2) Step through the generate GCODE line by line to see if there's something non-intuitive causing the failure.
 

3) Figure out how to increase logging - that's perhaps desparation as logs are often confusingly unhelpful at the best of times without increase the logging level - but it might reveal some hitherto unnoticed issue.

Link to comment
Share on other sites

  • 0

You know I'm going to sound like a horrible film critic (sorry), but it would be interesting to have a fixed view. I can't tell if the gantry us moving up slightly when it was going cronk-cronk-cronk, or if that's an artefact of you physically moving the camera.

Link to comment
Share on other sites

  • 0
11 minutes ago, smirk said:

You know I'm going to sound like a horrible film critic (sorry), but it would be interesting to have a fixed view. I can't tell if the gantry us moving up slightly when it was going cronk-cronk-cronk, or if that's an artefact of you physically moving the camera.

From what I recall it seems like just movement on the x/y axis. As though it’s trying to do the first layer there. 

Link to comment
Share on other sites

  • 0
1 hour ago, nannyogg82 said:

[gcode_macro G32]
gcode:
    SAVE_GCODE_STATE NAME=STATE_G32
    G90
    G28
    QUAD_GANTRY_LEVEL
    G28
    ##  Uncomment for for your size printer:
    #--------------------------------------------------------------------
    ##  Uncomment for 250mm build
    #G0 X125 Y125 Z30 F3600
    
    ##  Uncomment for 300 build
    #G0 X150 Y150 Z30 F3600
    
    ##  Uncomment for 350mm build
    G0 X175 Y175 Z30 F3600
    #--------------------------------------------------------------------
    RESTORE_GCODE_STATE NAME=STATE_G32

A small possibility, if your gcode has any G91 (relative positioning) set, then when it completes the quad_leveling macro then the RESTORE_STATE will turn that back on. You could add another G90 after the RESTORE_STATE just to make sure the printer isn't trying to make relative moves.

Link to comment
Share on other sites

  • 0

So to recap. The first time I built the printer, I followed the guide on here:

that first time it did start printing in the middle of the bed but wouldn’t adhere. So I repeated the step with the Z height adjustment in the video. 
 

while I was doing that I thought I would install Klipper screen for my Pi 7”. I followed the guide on this video by Modbot

I tried using Kiauh as suggested but it kept saying access denied. So I tried the manual method and after that I got some update error message about Klipperscreen. I wish I’d made a note of it. I somehow managed to get it updated and it’s ever since then this has been happening. 

Link to comment
Share on other sites

  • 0

Still cannot see how klipper screen could be the source of the woes (noting I have not used it myself) as it's just a GUI that speaks to moonraker. I've got a touch screen "somewhere" if I can find it I'll give it a go and try it out

Link to comment
Share on other sites

  • 0
11 minutes ago, smirk said:

Still cannot see how klipper screen could be the source of the woes (noting I have not used it myself) as it's just a GUI that speaks to moonraker. I've got a touch screen "somewhere" if I can find it I'll give it a go and try it out

I have klipperscreen running on mine... There are definitely differences between the klipperscreen UI and desktop, ala in a browser, UI. Things like preheat for ABS, PLA, etc.

So I'm thinking it could it be possible that klippersceen is the culprit. I'm going to peek inside my Pi4 to see if there may be something in one of the KS configs.

  • Like 1
Link to comment
Share on other sites

  • 0
24 minutes ago, smirk said:

Sadly there isn't on in the generated GCODE file.

If you're feeling "brave" try printing this file, it's just a simple 4 patches. I took your heat settings from your previous file (250 & 100)

nannyogg82.gcode 29.14 kB · 1 download

Bugger me! It worked! I had to really raise my z height though as it was dragging right across the plate. Think I might have knackered it lol. So has my starting z height been set too low, causing the print head to crash there? Or is the pin too short on the z endstop? I followed the guide in the video with heat soaking and then using the drag on a piece of paper plus the 0.1 decrease in z height. If this is the issue how do I go about resolving it?

Link to comment
Share on other sites

  • 0
1 minute ago, Penatr8tor said:

I have klipperscreen running on mine

Guess the proof-in-the-pudidng would be deinstalling KlipperScreen - how do you remove it then?

Actually, for all the talk about Klipper Screen - @nannyogg82 did you reinstall it after your reflashed the PI/MainsailOS?

Link to comment
Share on other sites

  • 0
2 minutes ago, nannyogg82 said:

Bugger me! It worked!

Thanks for the offer but I'll pass 🤣 Sorry about the print bed. It's a possibiliy it is getting caught on something. I'll need to compare the GCODE and see what it is setting the z-offset stuff to betwen yours and mine.

That was generated out of Cura (just using their stock V2.4r2 printer definition). It just uses the PRINT_START and PRINT_END macros in the startup/finish gcode routines

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...