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

    BLTouch not really working

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    26
    834
    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.
    • jay_s_ukundefined
      jay_s_uk @modl
      last edited by

      @modl that indicates that you either have a wiring issue or you have something in your homing files thats causing issues.
      can you post homex.g and homey.g?

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      modlundefined 1 Reply Last reply Reply Quote 0
      • modlundefined
        modl @jay_s_uk
        last edited by

        @jay_s_uk So M401 and 402 actually work after homing x alone.

        ; homex.g
        ; called to home the X axis
        ;
        ; generated by RepRapFirmware Configuration Tool v3.3.15 on Mon Jan 09 2023 14:50:13 GMT+0100 (Central European Standard Time)
        G91               ; relative positioning
        G1 H2 Z5 F6000    ; lift Z relative to current position
        G1 H1 X-360 F1800 ; move quickly to X axis endstop and stop there (first pass)
        G1 H2 X5 F6000    ; go back a few mm
        G1 H1 X-360 F360  ; move slowly to X axis endstop once more (second pass)
        G1 H2 Z-5 F6000   ; lower Z again
        G90               ; absolute positioning
        
        ; homey.g
        ; called to home the Y axis
        ;
        ; generated by RepRapFirmware Configuration Tool v3.3.15 on Mon Jan 09 2023 14:50:13 GMT+0100 (Central European Standard Time)
        G91                ; relative positioning
        G1 H2 Z5 F6000     ; lift Z relative to current position
        G1 H1 Y-1000 F1800 ; move quickly to Y axis endstop and stop there (first pass)
        G1 H2 Y5 F6000     ; go back a few mm
        G1 H1 Y-1000 F360  ; move slowly to Y axis endstop once more (second pass)
        G1 H2 Z-5 F6000    ; lower Z again
        G90                ; absolute positioning
        
        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @modl
          last edited by

          @modl so theres nothing in there that should stop M401 and M402 from working.
          next is to look at your wiring and make sure nothing is being pulled etc

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          modlundefined 1 Reply Last reply Reply Quote 1
          • modlundefined
            modl
            last edited by

            Ok M401 and M402 don't work after homing y alone, could there be a short somewhere with y endstops or motors ? Or could an overload cause this?

            1 Reply Last reply Reply Quote 0
            • modlundefined
              modl @jay_s_uk
              last edited by

              @jay_s_uk Physically everything looks fine. And if i'm resetting the system, M401 and M402 will work at the exact same position

              jay_s_ukundefined 1 Reply Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @modl
                last edited by

                @modl can you home Y and then send M558 and post the output?

                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                modlundefined 2 Replies Last reply Reply Quote 0
                • modlundefined
                  modl @jay_s_uk
                  last edited by

                  @jay_s_uk
                  At startup

                  M558
                  Z Probe 0: type 9, input pin io4.in, output pin nil, dive height 5.0mm, probe speeds 120,120mm/min, travel speed 6000mm/min, recovery time 0.20 sec, heaters normal, max taps 1, max diff 0.03
                  

                  After homing Y

                  M558
                  Z Probe 0: type 9, input pin io4.in, output pin nil, dive height 5.0mm, probe speeds 120,120mm/min, travel speed 6000mm/min, recovery time 0.20 sec, heaters normal, max taps 1, max diff 0.03
                  
                  1 Reply Last reply Reply Quote 0
                  • modlundefined
                    modl @jay_s_uk
                    last edited by

                    @jay_s_uk I found the culprit !! I actually had an extruder wired the wrong way when i first powered the machine, I rewired it as soon as i found out but it's been getting really hot even if idle since then. I unplugged it from the board and the probing now works. How to know if the stepper is cooked ?

                    Thank you very much for all your replies and your guidance

                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                    • modlundefined
                      modl
                      last edited by

                      Hope i didn't cook the driver...

                      1 Reply Last reply Reply Quote 0
                      • jay_s_ukundefined
                        jay_s_uk @modl
                        last edited by

                        @modl glad you found the culprit! if it gets very hot even when not in use thats not a very good sign at all. is RRF generating any warnings?

                        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                        modlundefined 1 Reply Last reply Reply Quote 0
                        • modlundefined
                          modl @jay_s_uk
                          last edited by

                          @jay_s_uk No RRF doesn't ring. I tested the coils resistance though one is .4 ohms the other is 4.8. I guess this one's cooked. Any way to know how the driver is doing except plugging in an other axis an changing config.g?

                          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                          • jay_s_ukundefined
                            jay_s_uk @modl
                            last edited by

                            @modl thats probably the easiest way to test the driver. Thats the way i usually test drivers

                            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                            modlundefined 1 Reply Last reply Reply Quote 0
                            • modlundefined
                              modl @jay_s_uk
                              last edited by

                              @jay_s_uk OK I'll try that. Again thank you very much!

                              1 Reply Last reply Reply Quote 0
                              • modlundefined
                                modl
                                last edited by

                                It was actually pretty fast, and the driver is doing fine

                                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                • jay_s_ukundefined
                                  jay_s_uk @modl
                                  last edited by

                                  @modl fantastic!

                                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                  1 Reply Last reply Reply Quote 2
                                  • Phaedruxundefined Phaedrux marked this topic as a question
                                  • Phaedruxundefined Phaedrux has marked this topic as solved
                                  • First post
                                    Last post
                                  Unless otherwise noted, all forum content is licensed under CC-BY-SA