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

    Voron Corexy weired x/y movement

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    6
    16
    733
    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.
    • TimTomundefined
      TimTom
      last edited by

      Dear Duet Community,

      for weeks I've been struggeling with a weired erratic behavior with my Voron build.

      It's a core xy build and the x/y axis sometimes work and sometimes do some unexpected moves, see video (seeing is better than describing it).

      https://www.youtube.com/watch?v=aFjJciD4qlc

      what actually happens is, that sometimes moves are fine and suddenly the moves are not x/y but x+y with an unhealthy sound.

      What I tried so far:

      • switched Board
      • tried different drivers/connectors
      • recrimped all connectors (multiple times)
      • changed motor cables
      • tried different software configurations
      • checked configuration from https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_coreXY all fine.
      • increased and decreased belt tension

      My current config.g (reduced to a minimum until movement works)

      ; General preferences
      G90                                            	    ; send absolute coordinates...
      M83                                                 ; ...but relative extruder moves
      M550 P"Voron"                                   	; set printer name
      M669 K1                                            	; select CoreXY mode
      
      ; Network
      M552 S1                                   	; enable network and acquire dynamic address via DHCP
      M586 P0 S1                                          ; enable HTTP
      M586 P1 S1                                         	; enable FTP
      M586 P2 T1 S0                                      	; disable Telnet
      
      ; Drives for XY
      M569 P0 S1                                       	; A motor 
      M569 P1 S2                                       	; B motor
      
      ; Drives for Z
      M569 P2 S1                                       	; Front left 
      M569 P3 S0                                       	; Back left
      M569 P4 S1                                       	; Back right
      M569 P5 S0                                       	; Front right
      
      ; Drive for extruder 
      M569 P6 S0                                       	; physical drive 1.0 goes forwards
      
      ; Drive mappings (assign previously 
      M584 X0 Y1 Z2:3:4:5 E6               	; set drive mapping
      
      ; General drive config like speeds, accel, jerk, etc
      M350 E64:64:64:64 I0                                                ; configure microstepping without interpolation
      M350 X16 Y16 Z16 I1                                                 ; configure microstepping with interpolation
      M92 X160.00 Y160.00 Z400.00:400.00:400.00:400.00 E420.00              ; set steps per mm
      M566 X900.00 Y900.00 Z900.00:900.00:900.00:900.00 E120              ; set maximum instantaneous speed changes (mm/min)
      M203 X60000.00 Y60000.00 Z60000.00:6000.00:6000.00:6000.00 E120.00  ; set maximum speeds (mm/min)
      M201 X6000.00 Y6000.00 Z4000.00:4000.00:4000.00:4000.00 E250.00     ; set accelerations (mm/s^2)
      M906 X1200 Y1200 Z1200:1200:1200:1200 E400 I100                      ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                    
      
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1                                   	; set axis minima
      ;M208 X301 Y305 Z265 S0                             	; set axis maxima original - not sure which build plate used?
      M208 X350 Y350 Z350 S0                             	; set axis maxima
      
      ; Endstops
      M574 X2 S1 P"io1.in"                               ; X Hall effect endstop
      M574 Y2 S1 P"io2.in"                               ; Y Hall effect endstop
      M574 Z1 S2                                                          ; configure Z-probe endstop for low end on Z
      
      ; Z-Probe
      M558 P8 C"io3.in" H5 F120 T60000                                 ; set Z probe type to unmodulated and the dive height + speeds
      G31 P500 X0 Y0 Z2.5                                                 ; set Z probe trigger value, offset and trigger height
      M557 X15:215 Y15:195 S20                                            ; define mesh grid
      
      
      ; Enable 12864 display
      M918 P2 E4 F2000000
      
      

      My last guess would be that one of the motors is defective. Any hint would be highle apreciated.

      PCRundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
      • PCRundefined
        PCR @TimTom
        last edited by

        @timtom why that 64 microstepping? Try 16 with I1

        TimTomundefined 1 Reply Last reply Reply Quote 0
        • TimTomundefined
          TimTom @PCR
          last edited by

          @pcr
          Thanks for the input,
          x / y motor are already in 16 I1
          64 is currently configured for Extruder (will take about that one later once x/y/z work correctly)

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

            @timtom all your entries for Z after M584 should only have one value

            M92 X160.00 Y160.00 Z400.00:400.00:400.00:400.00 E420.00  
            

            is incorrect and should be

            M92 X160.00 Y160.00 Z400.00 E420.00  
            
            M350 E64:64:64:64 I0
            

            is also incorrect as you only have one extruder. it should be

            M350 E64 I0
            

            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

            TimTomundefined 1 Reply Last reply Reply Quote 1
            • TimTomundefined
              TimTom @jay_s_uk
              last edited by

              @jay_s_uk
              Thanks Jay, updated that, tried many many different configurations, just adapted your changes, I'm currently not worried about correct stepping.
              The erratic behavior is still there.

              For the record here the updated config.g file:

              ; General drive config like speeds, accel, jerk, etc
              M350 E16 I0                                                ; configure microstepping without interpolation
              M350 X16 Y16 Z16 I1                                                 ; configure microstepping with interpolation
              M92 X160.00 Y160.00 Z400.00 E420.00              ; set steps per mm
              M566 X900.00 Y900.00 Z900.00:900.00:900.00:900.00 E120              ; set maximum instantaneous speed changes (mm/min)
              M203 X60000.00 Y60000.00 Z60000.00:6000.00:6000.00:6000.00 E120.00  ; set maximum speeds (mm/min)
              M201 X6000.00 Y6000.00 Z4000.00:4000.00:4000.00:4000.00 E250.00     ; set accelerations (mm/s^2)
              M906 X1200 Y1200 Z1200:1200:1200:1200 E400 I100                      ; set motor currents (mA) and motor idle factor in per cent
              M84 S30                    
              
              jay_s_ukundefined 1 Reply Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @TimTom
                last edited by

                @timtom your other lines need changing, so M566, M203, M201 and M906

                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

                TimTomundefined 1 Reply Last reply Reply Quote 0
                • TimTomundefined
                  TimTom @jay_s_uk
                  last edited by

                  @jay_s_uk

                  Thanks for the quick reply, unfortunately still no success

                  for the record:

                  ; General drive config like speeds, accel, jerk, etc
                  M350 E16 I0                                                ; configure microstepping without interpolation
                  M350 X16 Y16 Z16 I1                                                 ; configure microstepping with interpolation
                  M92 X160.00 Y160.00 Z400.00 E420.00              ; set steps per mm
                  M566 X900.00 Y900.00 Z900.00 E120              ; set maximum instantaneous speed changes (mm/min)
                  M203 X60000.00 Y60000.00 Z60000.00 E120.00  ; set maximum speeds (mm/min)
                  M201 X6000.00 Y6000.00 Z4000.00 E250.00     ; set accelerations (mm/s^2)
                  M906 X1200 Y1200 Z1200 E400 I100                      ; set motor currents (mA) and motor idle factor in per cent
                  M84 S30                    
                  
                  jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                  • jay_s_ukundefined
                    jay_s_uk @TimTom
                    last edited by

                    @timtom definitely sounds quite mechanical in nature.
                    what firmware are you running?

                    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

                    TimTomundefined 1 Reply Last reply Reply Quote 0
                    • TimTomundefined
                      TimTom @jay_s_uk
                      last edited by

                      @jay_s_uk

                      That's my fear, that x or y motor has a defect. . .

                      Currently I use RepRapFirmware for Duet 3 Mini 5+ 3.4.0beta6 (2021-11-06)
                      But previously I also had the latest stable --> same issue.

                      zaptaundefined 1 Reply Last reply Reply Quote 0
                      • A Former User?
                        A Former User
                        last edited by A Former User

                        This post is deleted!
                        TimTomundefined 1 Reply Last reply Reply Quote 2
                        • TimTomundefined
                          TimTom @A Former User
                          last edited by

                          @arnold_r_clark
                          Thanks for the hint, will check this evening to be sure.

                          On the other hand I somehow doubt that to be the reason:

                          1. There are also clean movement (sometimes x and y works just fine, to just instantantly switching to the erratic behavior).
                          2. While recrimping I made sure that "colors" match. These are genuine LDO/Voron motors bought from a European distributer, so the risk should be comparably low.
                          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                          • jay_s_ukundefined
                            jay_s_uk @TimTom
                            last edited by

                            @timtom just to give you a bit of reassurance its not firmware, I run 2 corexy's on 3.4b6 and one of them is a Voron V0 using LDO motors

                            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 0
                            • zaptaundefined
                              zapta @TimTom
                              last edited by

                              @timtom said in Voron Corexy weired x/y movement:

                              That's my fear, that x or y motor has a defect. . .

                              Have you tried testing the motors independently? E.g. releasing the belt tension and issuing manually G1 command with H2 parameter.

                              If the motors are ok, make sure your gantry is de-racked (nero3dp has an instruction video) , the belts seat properly and that there are no mechanical friction or binding.

                              A stepper motor analyzer would help https://forum.duet3d.com/post/262112

                              1 Reply Last reply Reply Quote 1
                              • Phaedruxundefined
                                Phaedrux Moderator @TimTom
                                last edited by

                                @timtom said in Voron Corexy weired x/y movement:

                                checked configuration from https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_coreXY all fine.

                                Can you make a video showing you going through the motion testing section of this guide to show correct movement?

                                From your video it really seems like a motor direction is incorrect and is fighting the other motor.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                TimTomundefined 1 Reply Last reply Reply Quote 0
                                • TimTomundefined
                                  TimTom @Phaedrux
                                  last edited by

                                  OK shame on me!
                                  While I wanted to replace the x/y motors I detected that the belt was misguided and rubbing on plastic!

                                  So please excuse my "wrongly" reported issue.

                                  Bear with me, I had so many external issues during the build (badly soldered hall effect platines, badly soldered extruder pcb's, broken duet board, wrongly configured wiring loom).
                                  Everything took me several hours to identify (I ordered all parts in Europe, with the hope to avoid Chinese quality issues - wrong assumption).

                                  After days of troubleshooting I stopped to challenge my own work, sorry for that.

                                  zaptaundefined 1 Reply Last reply Reply Quote 2
                                  • zaptaundefined
                                    zapta @TimTom
                                    last edited by

                                    @timtom, that's normal. We all struggle with similar problems.

                                    😉

                                    1 Reply Last reply Reply Quote 0
                                    • 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