Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    homing z failed with bltouch

    Scheduled Pinned Locked Moved
    IR Height Sensor
    2
    2
    1.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jrohundefined
      jroh
      last edited by jroh

      Hi,

      I upgraded firmware and webserver to 1.21 and equipped BLTOUCH at PWM5 of DEUX5 . But before probing homing-z fails with the reason of "z-probe already triggered at start of probing move".

      Could somebody advise me whether my setting is something wrong?

      My machine is self-made cartesian size of 600 x 850 x 700 with DUETWIFI and DUEX5, and Diamond 5color nozzle set and settings are as follows.

      //Homeall.g file
      G28 XY ;Home XY
      M561 ; Clear any bed transform that might be in place

      G30 ; Do a single probe
      ;M375 P"bareplate.csv" ; Load my custom heightmap. Otherwise use
      ;G29 S1 ;
      G90
      G1 Z10 F6000 S2 ; Move Z to 20

      //homez.g file
      G30 ; Do a single probe to home our Z axis
      G90 ; Make sure we are in absolute mode
      G1 Z10 F6000 S2 ; Rapidly move the Z axis to Z=10.

      //config.g file
      ; General preferences
      M111 S0 ; Debugging off
      G21 ; Work in millimetres
      G90 ; Send absolute coordinates...
      M83 ; ...but relative extruder moves
      M555 P1 ; Set firmware compatibility to look like RepRapFirmare
      ; Automatic saving after power loss is not enabled
      M208 X0 Y0 Z0 S1 ; Set axis minima
      M208 X580 Y800 Z700 S0 ; Set axis maxima

      ;disable heater7
      M307 H7 A-1 C-1 D-1 ; disable heater7

      ; Endstops
      M574 X1 Y1 S1 ; Set active high endstops
      M574 Z1 S2 ;
      M558 P9 X0 Y0 Z1 H5 F120 T6000 ; Set Z Probe to type Switch or Digital output where Z probe connector is used. Used for z only.;
      G31 P50 X-32.5 Y0 Z2.5; Set Z probe trigger value, offset and trigger height
      M557 X15:580 Y15:750 S25 ; Define mesh grid

      ; Drives
      M569 P0 S0 ;
      M569 P1 S1 ;
      M569 P2 S1 ;
      M569 P3 S0 ;
      M569 P4 S1 ;
      M569 P5 S1 ;
      M569 P6 S1 ;
      M569 P7 S1 ;
      M569 P8 S1 ;
      M569 P9 S1 ;

      M584 X3:4 Y0 Z1:2 E5:6:7:8:9 ; Apply custom drive mapping
      M350 X16 Y16 Z16 E16:16:16:16:16 I1 ; Configure microstepping with interpolation
      M92 X80 Y80 Z320 E421:421:421:421:421 ; Set steps per mm
      M566 X900 Y900 Z12 E120:120:120:120:120 ; Set maximum instantaneous speed changes (mm/min)
      M203 X6000 Y6000 Z180 E1200:1200:1200:1200:1200 ; Set maximum speeds (mm/min)
      M201 X800 Y800 Z150 E250:250:250:250:250 ; Set accelerations (mm/s^2)
      M906 X1400 Y1400 Z1680 E1000:1000:1000:1000:1000 I70 ; Set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Heaters
      M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
      M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
      M143 H0 S120 ; Set temperature limit for heater 0 to 120C
      M305 P2 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 1
      M143 H2 S280 ; Set temperature limit for heater 1 to 280C

      ; tools
      M563 P0 D0 H2
      G10 P0 X0 Y0 Z0
      G10 P0 R0 S0

      M563 P1 D1 H2
      G10 P1 X0 Y0 Z0
      G10 P1 R0 S0

      M563 P2 D2 H2
      G10 P2 X0 Y0 Z0
      G10 P2 R0 S0

      M563 P3 D3 H2
      G10 P3 X0 Y0 Z0
      G10 P3 R0 S0

      M563 P4 D4 H2
      G10 P4 X0 Y0 Z0
      G10 P4 R0 S0

      ; Fans
      M106 PO S255
      M106 P1 S1

      //////////////////////////////

      Above is my settings. I also set deployprobe.g and retractprobe.g files at sys folder. Should I set bed.g as well which is omitted on my sys folder?

      Would appraciate for advise.

      Thanks.

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        The bed.g file is needed only to do G32 bed probing, not for homing Z.

        Have you tested the Z probe and it configuration as described at https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe ?

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Unless otherwise noted, all forum content is licensed under CC-BY-SA