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

    BLTouch does not work anymore if M558 executed twice

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    7
    359
    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.
    • TheNetStrikerundefined
      TheNetStriker
      last edited by

      I would like to configure a BLTouch (Version 3.1) probing that first probes fast and then slow. But the problem is that the probe stops working when I execute the M558 command a second time. After that I have to power down the Duet board completely to get the probe working again. This is the command I'm using:

      M558 P9 H5 F300 T2000

      Does anyone have the same problem and what could cause this problem?

      1 Reply Last reply Reply Quote 0
      • droftartsundefined
        droftarts administrators
        last edited by

        Can you send M115 to the printer, and post the response here? This will show your firmware version, Duet Hardware type and version. Please also post your config.g, so we can see how the probe is setup. Finally, please post the EXACT code (first and second M558 commands, and any preceding relevant gcode) you are sending that causes this issue.

        Ian

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

        1 Reply Last reply Reply Quote 0
        • fcwiltundefined
          fcwilt
          last edited by

          Hi,

          Rather than try to change the Z probe feed rate could you temporarily limit the feed rate to the slower speed by using a M203 command?

          Frederick

          Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

          1 Reply Last reply Reply Quote 0
          • TheNetStrikerundefined
            TheNetStriker
            last edited by

            @droftarts Here is the output of the M115 command:

            FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2019-06-13b2

            And those are the command I'm executing:

            M558 P9 H5 F300 T2000 ; Executed by config.g
            M280 P64 S10 ; Deploy probe => works
            M280 P64 S90 ; Retract probe => works
            M558 P9 H5 F100 T2000 ; Execute command again
            M280 P64 S10 ; Deploy probe does not work anymore

            A reset of the Duet board also fixes the problem until the command is again executed a second time after the system is started up. I've uploaded the whole content of my sdcard to GitHub. There you can see all gcode files that I'm currently using:

            https://github.com/TheNetStriker/Promega/tree/LeadscrewBondtechV6/SD Card Structure/Compound/sys

            @fcwilt You solution seems to work. I will use this as a workaround until a fix for the problem is found.

            1 Reply Last reply Reply Quote 0
            • fcwiltundefined
              fcwilt
              last edited by

              Hi,

              Well at least you have a workaround.

              While I have NOT actually done this with the most recent firmware in the past I have used macros to change Z-probe type as I had interchangeable Z-probes.

              Perhaps changing from P9 to P0 and then back to P9 might work.

              Frederick

              Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

              1 Reply Last reply Reply Quote 0
              • TheNetStrikerundefined
                TheNetStriker
                last edited by

                @fcwilt I've just tried that but that also doesn't work. The probe is just not doing anything after the second command.

                fcwiltundefined 1 Reply Last reply Reply Quote 0
                • fcwiltundefined
                  fcwilt @TheNetStriker
                  last edited by

                  @TheNetStriker said in BLTouch does not work anymore if M558 executed twice:

                  @fcwilt I've just tried that but that also doesn't work. The probe is just not doing anything after the second command.

                  As I suggested perhaps the firmware you are using works differently from what I was using when I was changing Z-probe type but I was able to change from one to another and back again.

                  The difference being I was not trying to change any of the parameters.

                  I would do this myself by I am out of town so Just as a test execute the M558 twice with the same parameters and see if that also causes the Z-probe to stop working.

                  Frederick

                  Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

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