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

    No Movement with RRF3.1+

    Scheduled Pinned Locked Moved Unsolved
    Duet Hardware and wiring
    5
    20
    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.
    • Vetiundefined
      Veti
      last edited by

      can you disconnect the duex5 ribbon cable and see if that works?

      1 Reply Last reply Reply Quote 0
      • curlypaulundefined
        curlypaul
        last edited by

        I have to admit i didn't try that 🙄

        But, yes - I now get movement, so can only guess it's got something to do with the Drive5 - removed one on the Duex

        1 Reply Last reply Reply Quote 0
        • curlypaulundefined
          curlypaul
          last edited by

          Whilst I'm now getting movement, It's still not as expected/desired...
          like why does my U carriage move when I home Y ?

          But i'll do a seperate post for that.

          Would still like to know if I can get movement with the duex5 in it's current state on this FW somehow ?

          1 Reply Last reply Reply Quote 0
          • Vetiundefined
            Veti
            last edited by

            @dc42 can you comment on that?

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

              @curlypaul, you've posted your new config,g file, but please can you post the working RRF2.02 config.g file too so that I can work out your machine configuration.

              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

              Vetiundefined curlypaulundefined 2 Replies Last reply Reply Quote 0
              • Vetiundefined
                Veti @dc42
                last edited by Veti

                @dc42 but what would make all motors stop moving in rrf3 if he has a bad driver on the duex5?

                1 Reply Last reply Reply Quote 0
                • curlypaulundefined
                  curlypaul @dc42
                  last edited by

                  @dc42 config.g from 2.02 below..
                  The one thing that you may notice is that I have to use M669 K5 to get correct behavior, Not K8

                  ; Configuration file for Duet WiFi (firmware version 2.02)
                  ; executed by the firmware on start-up
                  ;
                  ; generated by RepRapFirmware Configuration Tool v2.1.3 on Sun Dec 08 2019 16:18:30 GMT+0000 (Greenwich Mean Time)
                  
                  ; General preferences
                  G90                                     ; send absolute coordinates...
                  M83                                     ; ...but relative extruder moves
                  M550 P"IDEX"                    		; set printer name
                  
                  M669 K5                                ; select CoreXY mode
                  
                  ; Network
                  M551 P"curly"                           ; set password
                  M552 S1                                 ; enable network
                  M586 P0 S1                              ; enable HTTP
                  M586 P1 S0                              ; disable FTP
                  M586 P2 S0                              ; disable Telnet
                  
                  ; Drives
                  M569 P0 S1               		                ; physical drive 0 goes forwards
                  M569 P1 S0	             		                ; physical drive 1 goes forwards
                  M569 P2 S0                 	 	          	    ; physical drive 2 goes forwards
                  M569 P3 S1  									; physical drive 3 goes forwards
                  M569 P4 S0  									; physical drive 4 goes forwards	
                  M569 P5 R-1  									; physical drive 5 disabled
                  M569 P6 S1  									; physical drive 3 goes forwards
                  M569 P7 S1	                        			; physical drive 3 goes forwards
                  
                  M584 X0 Y1 Z2 U4 V3 E6:7 P4                   			; set drive mapping
                  
                  M350 X16 Y16 U16 V16 Z16 E16:16 I1		     			        ; Configure microstepping with interpolation
                  M92 X160 Y160 U160 V160 Z1280 E396:396		 			; Set steps per mm
                  M566 X600 Y600 U600 V600 Z50 E3000:3000              	                ; Set maximum instantaneous speed changes (mm/min)
                  M203 X20000 Y20000 U20000 V20000 Z600 E9000:9000      	; Set maximum speeds (mm/min)
                  M201 X1000 Y1000 U1000 V1000 Z600 E3000:3000              	; Set accelerations (mm/s^2)
                  ;M204 P1500 T1800										; Set printing and travel accerations
                  M906 X1400 Y1400 U1400 V1400 Z1800 E1200:1200 I30     	; Set motor currents (mA) and motor idle factor in per cent
                  M84 S60                                 				; Set idle timeout                        
                  	
                  ; Axis Limits
                  M208 X-3 Y-92 U100 Z0 S1                      	        ; set axis min
                  M208 X380 Y320 U425 Z325 S0                 	; set axis max
                  
                  ; Endstops
                  M574 X1 Y1 U2 S1                          		; set endstops controlled by ENDSTOPS
                  M574 Z1 S2                              		        ; set endstops controlled by probe
                  
                  ; Z-Probe
                  M307 H3 A-1 C-1 D-1                    			; disable heater on PWM channel for BLTouch
                  M558 P9 H5 F200 T9000                  			; set Z probe type to bltouch and the dive height + speeds
                  G31 P500 X12.5 Y75. Z0.75             			; set Z probe trigger value, offset and trigger height
                  M557 X15:350 Y10:278 S67              			; define mesh grid
                  
                  ; Heaters
                  M305 P0 T100000 R4700 B4725 C7.060000e-8   
                  M307 H0 A73.2 C151.3 D12.9 S1.00 V24.3 B0     	; set thermistor + ADC parameters for heater 0
                  M143 H0 S90                       	      		                        ; set temperature limit for heater 0 to 120C
                  
                  M305 P1 T100000 R4700 B4725 C7.060000e-8        ; set thermistor + ADC parameters for heater 1
                  M143 H1 S270                           			                  ; set temperature limit for heater 1 to 280C
                  M307 H1 A460.4 C235.5 D4.5 S1.00 V24.3 B0
                  
                  M305 P2 T100000 R4700 B4725 C7.060000e-8     	; set thermistor + ADC parameters for heater 1
                  M143 H2 S270                           			                ; set temperature limit for heater 1 to 280C
                  M307 H2 A600.0 C221.8 D4.6 S1.00 V24.2 B0
                  
                  
                  
                  ; Fans
                  M106 P0 S0 I0 F50 H-1                  			; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
                  M106 P1 S1 I0 F50 H2 T45              	 		; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
                  M106 P7 S1 I0 F50 H1 T45               			; set fan 7 value, PWM signal inversion and frequency. Thermostatic control is turned on
                  M106 P8 S0 I0 F10 H-1                  			; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
                  
                  ; Tools
                  M563 P0 S"X-AXIS" D0 H1 F8                      ; define tool 0
                  G10 P0 X0 Y0 U0 Z0                         		; set tool 0 axis offsets
                  G10 P0 R0 S0                            		; set initial tool 0 active and standby temperatures to 0C
                  
                  M563 P1 S"U-AXIS" D1 H2 X3 F0					; Define tool 1
                  G10 P1 X0.1 Y-0.3 U0 Z0 						; Set tool 1 axis offsets
                  G10 P1 R0 S0 									; Set initial tool 1 active and standby temperatures to 0C
                  
                  M563 P2 S"T2 COPY" D0:1 H1:2 X0:3 F0:1			; Define tool 2 Ditto Printing
                  G10 P2 X75 Y0 U-75 Z 							; Set tool 2 axis Ditto Printing offsets
                  G10 P2 R0 S0 									; Set initial tool 2 active and standby temperatures to 0C
                  M567 P2 E1:1 									; Set mix rtio 100% on both extruders
                  
                  
                  ; Custom settings are not defined
                  
                  M501
                  
                  Phaedruxundefined 1 Reply Last reply Reply Quote 0
                  • fulgundefined
                    fulg
                    last edited by fulg

                    One thing I noticed yesterday (running 3.2beta3) is that setting a negative tool offset for Z seems to permanently disable movement for that axis. You can move the axis in the Dashboard panel, the current position changes, but no actual movement occurs.

                    For example if I do G10 P0 X0 Y0 Z-0.06 then any Z axis movement is disabled and the board behaves as if the drivers were busted. Maybe a similar problem occurs for U.

                    It took me a while to realize this was caused by the negative G10 P0 Z-0.06 bit, I was convinced I had somehow managed to kill all four Z drivers on my Duex.

                    VORON V2 CoreXY + Duet3 Mini5+ Ethernet v1.0 with Mini2+ expansion, VORON V0 CoreXY + Duet2 Maestro

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

                      @curlypaul said in No Movement with RRF3.1+:

                      The one thing that you may notice is that I have to use M669 K5 to get correct behavior, Not K8

                      How did CoreXYU work before? What happened to V?

                      Z-Bot CoreXY Build | Thingiverse Profile

                      curlypaulundefined 1 Reply Last reply Reply Quote 0
                      • curlypaulundefined
                        curlypaul @Phaedrux
                        last edited by curlypaul

                        @Phaedrux it's a bit hard to explain/remember properly without being with the printer, but the main issue is U will move towards the homed X when homing Y.
                        also X,Y,U positions are lost/reset when homing other axis
                        Seemingly random but repeatable moves after and during homing.
                        Certainly with 2.03,2.04 and 2.05, the UV motors won't move at all if a movement in XY is commanded, resulting in what at the time I called 'angry noises'
                        Where as 2.02 set at K5, seems to have the printer work exactly as I'd expect

                        It might be best to video the difference and let that explain

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

                          I wonder if this is a similar issue as here

                          https://forum.duet3d.com/topic/20164/g30-g32-issues-on-duet-wifi-corexyu-with-inductive-probe?_=1606925875835

                          Z-Bot CoreXY Build | Thingiverse Profile

                          curlypaulundefined 1 Reply Last reply Reply Quote 1
                          • curlypaulundefined
                            curlypaul @Phaedrux
                            last edited by

                            @Phaedrux I will give this a try at the weekend
                            Thank you for posting this

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

                              @curlypaul I think I know what is going on. The newer version of the TMC2660 driver includes code to reset the microstep position to zero before it enables the driver. That isn't going to work if the driver has been removed. I will disable that feature for drivers that have been disabled using M569 R-1.

                              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

                              curlypaulundefined 1 Reply Last reply Reply Quote 0
                              • curlypaulundefined
                                curlypaul @dc42
                                last edited by

                                @dc42 - That's awesome - Thank you (and Tony) for looking into this for me 🙂

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