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

    Getting confused with the BLtouch installation

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    2
    756
    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.
    • Nylkosundefined
      Nylkos
      last edited by

      I know that I am not the first to post on the subject and that there are threads in large amount to be found on multiple issues but trying so many different things on multiple files can be confusing… not knowing if I made a mistake I actually reconfig my entire printer twice ...
      I have read these
      https://duet3d.com/wiki/Connecting_a_Z_probe
      https://www.duet3d.com/forum/thread.php?id=459&p=2

      ATM, when I do home all, everything is good For X and Y axis. Once I get to the Z I get this message: Z probe already triggered at start of probing move.

      so far what I did:
      Config.g file:

      ; Configuration file for Duet 0.8.5 (firmware version 1.17)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool on Fri Sep 01 2017 23:00:38 GMT-0400 (Eastern Standard Time)

      ; 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

      M667 S1 ; Select CoreXY mode
      M208 X0 Y0 Z0 S1 ; Set axis minima
      M208 X300 Y300 Z300 S0 ; Set axis maxima

      ; Endstops
      M574 Z0 S0 ; Define active low and unused microswitches
      M574 X2 Y2 S0 ; Define active high microswitches
      M558 P5 X0 Y0 Z1 H5 F100 T2000
      G31 X30 Y18 Z3 P25
      M557 X15:285 Y15:285 S20 ; Define mesh grid

      ; Drives
      M569 P0 S1 ; Drive 0 goes forwards
      M569 P1 S1 ; Drive 1 goes forwards
      M569 P2 S1 ; Drive 2 goes forwards
      M569 P3 S1 ; Drive 3 goes forwards
      M92 X160 Y160 Z800 E100 ; Set steps per mm
      M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
      M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
      M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2)
      M906 X800 Y800 Z800 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Heaters
      M143 S300 ; Set maximum heater temperature to 300C
      M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
      M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1

      ; Tools
      M563 P0 D0 H1 ; 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

      ; Network
      M550 PMy printer ; Set machine name
      M540 PBE:EF:DE:AD:FE:ED ; Set MAC address
      M552 P192.168.2.50 S1 ; Enable network and set IP address
      M553 P255.255.255.0 ; Set netmask
      M554 P192.168.2.254 ; Set gateway
      M586 P0 S1 ; Enable HTTP
      M586 P1 S0 ; Disable FTP
      M586 P2 S0 ; Disable Telnet

      ; Fans
      M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
      M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

      ; Custom settings
      M307 H1 A506.7 C200.3 D6.0 B0 ; Save hotend PID
      M307 H3 A-1 C-1 D-1 ; reserve pin 21 for M42 or servo use

      T0

      bed.g file:

      ; bed.g
      ; called to perform automatic bed compensation via G32
      ;
      ; generated by RepRapFirmware Configuration Tool on Fri Sep 01 2017 23:00:38 GMT-0400 (Eastern Standard Time)

      ; Clear any bed transform
      M561

      ; Home all axes
      ;G28
      M98 Pdeployprobe.g

      ; Probe the bed at 5 points
      G30 P0 X15 Y15 H0 Z-99999
      G30 P1 X15 Y285 H0 Z-99999
      G30 P2 X285 Y285 H0 Z-99999
      G30 P3 X285 Y15 H0 Z-99999
      G30 P4 X150 Y150 H0 Z-99999 S
      M98 Pretractprobe.g

      homez.g file:

      ; homez.g
      ; called to home the Z axis
      ;
      ; generated by RepRapFirmware Configuration Tool on Fri Sep 01 2017 23:00:38 GMT-0400 (Eastern Standard Time)

      ; Lift Z relatively to current position
      G91
      G1 Z5 F6000

      ; Back to absolute positioning
      G90
      M98 Pdeployprobe.g
      ; Go to first bed probe point and home the Z axis
      G1 X13.2 Y12 F6000
      G30

      ; Uncomment the following lines to lift Z after probing
      ;G91
      ;G1 Z5 F100
      ;G90

      deployprobe.g file:

      M280 P3 S10 I1

      retractprobe.g file:

      M280 P3 S90 I1

      Thanks you for your assistance.

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

        I don't know the Bltouch, but it's a good idea to test a new Z probe. Deploy it and check that the value displayed in the Z probe box in DWC is close to zero. Then trigger it and check that the value rises to around 1000.

        In your deployprobe.g file, you might need to add a G4 delay command after the M280 command, to give the probe time to deploy.

        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