Nozzle will not start low enough to print



  • Hi all

    Below is my present config file. After I zero my nozzle and attempt to print, the nozzle will not go low enough to give me a good first layer. It seems to start printing at about 2.2 mm above the bed.
    Please help!
    I am soooo close

    ; Configuration file for Duet WiFi (firmware version 2.03)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu May 07 2020 15:49:06 GMT-0400 (Eastern Daylight Time)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"My Printer" ; set printer name

    ; Network
    M552 S1 ; enable network
    M586 P0 S1 ; enable HTTP
    M586 P1 S0 ; disable FTP
    M586 P2 S0 ; disable Telnet

    ; Drives
    M569 P2 S0 ; physical drive 2 goes backwards
    M569 P1 S0 ; physical drive 1 goes backwards
    M569 P0 S1 ; physical drive 0 goes forwards
    M569 P4 S1 ; physical drive 4 goes forwards
    M569 P3 S1 ; physical drive 3 goes forwards
    M584 X2 Y1 Z0:4 E3 ; set drive mapping
    M350 X16 Y16 Z16:16 E16 I1 ; configure microstepping with interpolation
    M92 X80.00 Y80.00 Z1800.00 E420.00 ; set steps per mm
    M566 X900.00 Y900.00 Z0.2 E120.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z120.00 E1200.00 ; set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
    M906 X1200 Y1400 Z2400 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X0 Y0 Z0 S1 ; set axis minima
    M208 X1160 Y1430 Z1815 S0 ; set axis maxima

    ; Endstops
    M574 X1 S3 ; set endstops controlled by motor stall detection
    M574 Y1 S3 ; set endstops controlled by motor stall detection
    M574 Z0 P"nil" ; set endstops controlled by probe

    ; Z-Probe
    M558 P5 C"!zprobe.in" H6 F120 T500 ; set Z probe type to switch and the dive height + speeds
    G31 P500 X-30 Y-36 Z0.66 ; set Z probe trigger value, offset and trigger height
    M557 X0:1160 Y0:1430 S200 ; define mesh grid

    ; Heaters
    M140 H0 ; enable heated bed; map heated bed to heater 0
    M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
    M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
    M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit

    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    ; M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
    M308 S0 P"bed_temp" Y"thermistor" T100000 B3950
    M308 S1 P"e0_temp" Y"thermistor" T100000 B4138
    ; M950 H0 C"bed_heat" T0
    M950 H1 C"e0_heat" T1
    M143 H1 S280 ; set temperature limit for heater 1 to 280C

    ; Fans
    M950 F0 C"!Fan0"
    M106 P0 S0.5 H1 T45 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on

    ; Tools
    M563 P0 D0 H1 F0 ; define tool 0
    G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
    G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

    ; Custom settings

    ; X axis sensorless endstop config
    M915 X S5 F0 H172 R0

    ; Y axis sensorless endstop config
    M915 Y S8 F0 H172 R0

    M501



  • Hi,

    I always check the result of G30 to be sure the Z probe is working as expected.

    I have a macro that does something like this

    G90      ; absolute mode
    G1 X# Y# ; move to center of bed - use X and Y values that account for the Z probe offsets
    G30      ; probe bed
    G1 Z#    ; move Z to a specific position
    

    At this point I verify that Z is in fact at the correct position. Now in my case my measuring device is a 1mm thickness gauge so the Z move is G1 Z1.

    Frederick



  • Thank you. I will give that a try.


  • Moderator

    What firmware version are you using? M115 to show.

    What is the probe?

    How are you homing? Post your homeall.g

    What do you have in your slicer start gcode?



  • @Phaedrux

    /31/2020, 7:27:23 PM M115
    FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-01-03b3

    NPN inductive Z probe

    ; homeall.g
    ; called to home all axes
    ;
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu May 07 2020 15:49:06 GMT-0400 (Eastern Daylight Time)

    ; homex.g
    ; called to home the X axis
    ;
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu May 07 2020 15:49:06 GMT-0400 (Eastern Daylight Time)
    G91 ; relative positioning
    ; G1 H2 Z20 F120 ; lift Z relative to current position
    M92 X172.00 ; set movement speed to match m915 H param
    M201 X100.00 ; reduce acceleration
    M566 X100.00 ; reduce maximum instantaneous speed changes (mm/min)
    G1 H1 X-1160 F6000 ; move quickly to X axis endstop and stop there (first pass)
    ; G1 H2 Z-5 F6000 ; lower Z again
    G90 ; absolute positioning
    M92 X80.00 ; set steps per mm back to default
    M566 X900.00 ; set maximum instantaneous speed changes back to normal (mm/min)
    M201 X500.00 ; set ac

    ; homey
    G91 ; relative positioning
    ; G1 H2 Z5 F6000 ; lift Z relative to current position
    M92 Y172.00 ; set movement speed to match m915 H param
    M201 Y100.00 ; reduce acceleration
    M566 Y100.00 ; reduce maximum instantaneous speed changes (mm/min)
    G1 H1 Y-1430 F6000 ; move quickly to Y axis endstop and stop there (first pass)
    ;G1 H2 Z-5:-5 F6000 ; lower Z again
    G90 ; absolute positioning
    M92 Y80.00 ; set steps per mm back to default
    M566 Y900.00 ; set maximum instantaneous speed changes back to normal (mm/min)
    M201 Y500.00 ; set accelerations back to normal (mm/s^2)

    G91 ; relative positioning
    G90 ; absolute positioning
    ; G1 X5 Y-10 F6000 ; go to first probe point
    G30 ; home Z by probing the bed

    ; Uncomment the following lines to lift Z after probing
    ;G91 ; relative positioning
    ;G1 Z5 F120 ; lift Z relative to current position
    ;G90 ; absolute positioning

    The last question, I don't have an answer to. I used my Prusa Slicer but I didn't see a setting for a start code. I suspect it my ignorance of the software is at least one of my issues. Thank you for any help you can give. I am new to DIY printers.


  • Moderator

    @damaged_goods said in Nozzle will not start low enough to print:

    FIRMWARE_VERSION: 3.0

    Update your firmware by uploading this zip file as is to the /sys folder.

    https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip


  • Moderator

    @damaged_goods said in Nozzle will not start low enough to print:

    I used my Prusa Slicer but I didn't see a setting for a start code.

    It's in the printers tab.


  • Moderator

    @damaged_goods said in Nozzle will not start low enough to print:

    M92 X172.00 ; set movement speed to match m915 H param
    M201 X100.00 ; reduce acceleration
    M566 X100.00 ; reduce maximum instantaneous speed changes (mm/min)
    G1 H1 X-1160 F6000 ; move quickly to X axis endstop and stop there (first pass)
    ; G1 H2 Z-5 F6000 ; lower Z again
    G90 ; absolute positioning
    M92 X80.00 ; set steps per mm back to default
    M566 X900.00 ; set maximum instantaneous speed changes back to normal (mm/min)
    M201 X500.00 ; set ac

    It's quite bizarre to alter your steps per mm in a homing file. What is the reasoning?

    @damaged_goods said in Nozzle will not start low enough to print:

    ; G1 X5 Y-10 F6000 ; go to first probe point
    G30 ; home Z by probing the bed

    What position on the bed are you actually probing? The probe should be positioned at the center.

    @damaged_goods said in Nozzle will not start low enough to print:

    G31 P500 X-30 Y-36 Z0.66 ; set Z probe trigger value, offset and trigger height

    How have you measured the trigger height?

    If you haven't already, see here: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe



  • @Phaedrux thank you. This should be very helpful.


Log in to reply