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

    3.4 rc1 1XD Probe problem after update

    Scheduled Pinned Locked Moved Unsolved
    Beta Firmware
    4
    13
    643
    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.
    • tom33undefined
      tom33
      last edited by Phaedrux

      Hi,

      Since I hace update from 3.4 beta 4 to 3.4 rc1 I have a problem with the probing (G30, G30 S-2,....)

      When I start a probe and the endstop his triggered I have a problem with my Z axis, thats create a an error in my encoder

      I use duet1XD and external motor with encoder.

      I don't understand because G30 works fine with 3.4beta4 but with 3.4beta7 and 3.4rc1 thats create a problem to my driver something have changed ?

      ; Configuration file for Duet 3 (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Mar 31 2021 11:16:46 GMT+0200 (heure d’été d’Europe centrale)
      ;M98 P"/sys/condition2.g"
      ; General preferences
      G90                                                ; send absolute coordinates...
      M83                                                ; ...but relative extruder moves
      M550 P""  
      M451
      M929 S3
      
      ; Drives
      M569 P0 S0                                             ; Drive 0 T0 Extrudeur Gauche
      M569 P1 S1                                             ; Drive 1 T1 Extrudeur Droit
      M569 P2 S1                                             ; Drive 3 T0 Extrudeur Bobine Gauche
      M569 P3 S1                                             ; Drive 3 T0 Extrudeur Bobine Droit
      M569 P4 S1                                             ; Drive 4 T1 Montée descente
      
      G4 S1
      
      ; set drive mapping
      M584 E1:2
      M584 A3 B4 C0
      M584 P7
      
      M350 E16:16 I1                                         	; configure microstepping without interpolation
      M350 A16 B16 C16 I1                        	; configure microstepping with interpolation
      M92 A415 B415 C300 E582:582             	; set steps per mm
      M566 X500 Y500 Z25 W25 A500 B500 C50 E500:500              ; set maximum instantaneous speed changes (mm/min)
      M203 X12000 Y12000 Z1800 W1800 A3600 B3600 C10000 E1200:1200 	; set maximum speeds (mm/min)
      M201 X350 Y350 Z50 W50 A500 B500 C500 E500:500            ; set accelerations (mm/s^2)
      M906 A1200 B1200 C750 E400:400 I30   	; set motor currents (mA) and motor idle factor in per cent
      M84 S0                                                	; Set idle timeout
      M913 C100                                               ; Courant moteur Axe C 50%
      
      ; Axis Limit
      M208 X0:1040 Y0:515 Z0:534.3 W0:534.3 A-10000:10000 B-10000:10000 C-10:10
      M671 X0:1040 Y250:250
      
      ; Endstops
      M574 A0
      M574 B0
      M574 C2 S1 P"!10.io0.in" 
      
      ; Z-Probe
      M558 P5 C"!io4.in" H10 F300 T6000                       ; set Z probe type to switch and the dive height + speeds "!io8.in"
      G31 P500 X0 Y0 Z-2.725	                                  ; set Z probe trigger value, offset and trigger height
      M557 X15:985 Y15:485 S150                                ;define mesh grid
      
      ; Bed heater 
      M308 S0 P"temp0" Y"thermistor" A"Plateau chauffant" T100000 B4138 C0       ; configure sensor 0 as thermistor on pin temp0
      M950 H0 C"out5" T0                                      ; create bed heater output on out0 and map it to sensor 0
      M307 H0 B0 R0.334 C356.2 D1.33 S1.00 V24.0                                        ; disable bang-bang mode for the bed heater and set PWM limit
      M140 H0                                                 ; map heated bed to heater 0
      M143 H0 S120
      M570 H0 P60 T10 S120; set temperature limit for heater 0 to 120C
      
      ; Tool 0 heater
      M308 S1 P"temp1" Y"thermistor" A"E0" T98640 B4632.86 C9.4861662E-08 H0 L0	; Set thermistor
      ;M307 H1 B0 R1.862 C397.7:397.7 D19.89 S1.00 V24.0
      M307 H1 B0 R1.857 C385.6:374.5 D14.06 S1.00 V24.0
      M950 H1 C"out1" T1					                    ; Extruder 0 heater
      M143 H1 S300 					                        ; Set temperature limit for heater 1 to 300C
      M570 H1 P60 T35 S120
      
      ;Tool 1 heater
      M308 S2 P"temp2" Y"thermistor" A"E1" T98640 B4632.86 C9.4861662E-08 H0 L0      ; configure sensor 2 as thermistor on pin temp2
      M307 H2 B0 R1.782 C345.7:345.7 D18.75 S1.00 V24.0
      M950 H2 C"out2" T2                                      ; create nozzle heater output on out2 and map it to sensor 2
      M143 H2 S300   
      M570 H2 P60 T35 S120
      
      ;Heat chamber
      M308 S3 P"temp3" Y"thermistor" A"Chambre" T100000 B4138 C7.06e-8           ; configure sensor 3 as thermistor on pin temp3
      M950 H3 C"out0" T3                                 ; create chamber heater output on out3 and map it to sensor 3
      M307 H3 B0 S1.00                                        ; disable bang-bang mode for the chamber heater and set PWM limit
      M141 H3                                                 ; map chamber to heater 3
      M143 H3 S100                                            ; set temperature limit for heater 3 to 100C
      M950 P6 C"out3"
      
      ; Tools
      M563 P0 S"E0" D0 H1 F0					                ; Define Extruder 0 drive 0 Heater 1 Fan 0
      G10 P0 X-10.085 Y-5.075 Z0 C0						                ; Set offset
      G10 P0 R0 S0 							                ; Reset initial tool 0 active and standby temperatures to 0C
      
      M563 P1 S"E1" D1 H2 F1                                  ; Define Extruder 1 drive 1 Heater 2 Fan 1
      G10 P1 X10.085 Y5.075 Z0 C0                                     ; set tool 1 axis offsets Essais Z offset pour déplacement axe C
      G10 P1 R0 S0                                            ; set initial tool 1 active and standby temperatures to 0C
      
      ;Filament Monitor
      ;M591 P3 C"io5.in" S1 D0                                 ; filament monitor connected to E0_stop
      ;M591 P3 C"io6.in" S1 D0                                 ; filament monitor connected to E0_stop
      
      ; Fans
      M950 F0 C"10.out1"                                       ; create fan 1 on pin out5 and set its frequency
      ;M950 F1 C"out8"                                         ; create fan 2 on pin out6 and set its frequency
      
      ;Servo
      ;950 S4 C"io4.out"   ; Servo Montée / Descente
      M950 S5 C"io5.out"   ; Servo B0
      M950 S7 C"io7.out"   ; Servo B1
      
      ;Input
      ;M950 J0 C"io0.in"      ; Arret d'urgence
      ;M950 J20 C"35.io0.in"
      ;M581 T0 P0 S1 R0        ; T0 --> M112 Arret d'urgence
      ;M581 T0 P20 S1 R0
      
      ;M950 J1 C"io1.in"       ; Pause / Play trigger 2.g
      ;M581 T2 P1 S0 R0        ; T6 --> M25 Pause / Play
      
      ;M950 J2 C"io2.in"       ; Pause / Stop trigger 3.g
      ;M581 T3 P2 S0 R0 	    ; Stop
      
      ;M950 J3 C"25.io2.in"    ; Door
      ;M581 T4 P3 S0 R0        ; Door
      
      ;M950 J10 C"!10.io0.in"     ; Detection Outils Impression 3D
      ;M581 T10 P10 S0 R0        ; Trigger10.g 
      
      ;M950 J11 C"!20.io0.in"     ; Detection Outils CNC
      ;M581 T11 P11 S0 R0        ; Trigger11.g
      
      ;Output
      ;M950 P0 C"20.out0" ; Verrouillage porte
      M950 P1 C"10.out0" ;
      
      M150 X0    ; set LED type to NeoPixel and set SPI frequency to 3MHz
      M501
      ; Custom settings are not defined
      ;M375 P"/sys/_Printer/heightmap.csv"
      M376 H25						; bed compensation taper
      
      ;global CumulativeTime = 0
      ;M98 P"0:/macros/myUpTime.g" ; this could be in start.g if doing print time
                                                     ; load saved parameters from non-volatile memory
      M911 S22.0 R22.5 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ;set voltage thresholds and actions to run on power loss
      M501
      
      x_pedro_xundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined Phaedrux marked this topic as a question
      • Phaedruxundefined Phaedrux moved this topic from Duet Hardware and wiring
      • x_pedro_xundefined
        x_pedro_x @tom33
        last edited by

        @tom33 I second this finding, today while testing 3.4 rc1 I couldn't get reliable reading while probing.
        My setup is as follows:

        ; Drives
        M569 P0.0 S0 D3 H50 V50                            ; physical drive 0.0 goes backwards
        M569 P0.1 S0 D3 H50 V50                            ; physical drive 0.1 goes backwards
        M569 P0.2 S0 D3 H50 V50                            ; physical drive 0.2 goes backwards
        M569 P0.3 S1 D3 H50 V50                            ; physical drive 0.3 goes forwards
        M569 P0.4 S1 D3 H50 V50                            ; physical drive 0.4 goes forwards
        M569 P0.5 S0 D3 H50 V50                            ; physical drive 0.5 goes backwards
        M584 X0.3 Y0.4 Z0.2:0.1:0.0 E0.5                 ; set drive mapping
        M350 X16 Y16 Z16 E16 I1                              ; configure microstepping with interpolation
        M92 X80.00 Y80.00 Z1600.00 E835                         ; set steps per mm
        M566 X400.00 Y400.00 Z6.00 E120.00 P1              ; set maximum instantaneous speed changes (mm/min)
        M203 X20800.00 Y20800.00 Z1000.00 E3600.00         ; set maximum speeds (mm/min)
        M201 X6000.00 Y6000.00 Z3000.00 E3600.00             ; set accelerations (mm/s^2)
        M906 X2000 Y2000 Z1200 E800 I20                              ; set motor currents (mA) and motor idle factor in per cent
        M84 S30                                            ; Set idle timeout
        
        

        and my bed.g:

        M561 ; clear any bed transform
        
        G30 P0 X5 Y5 Z-99999      ; probe near a leadscrew
        G30 P1 X5 Y20 Z-99999     ; probe near a leadscrew
        G30 P2 X20 Y5 Z-99999     ; probe near a leadscrew
        G30 P3 X230 Y470 Z-99999  ; probe near a leadscrew
        G30 P4 X250 Y470 Z-99999  ; probe near a leadscrew
        G30 P5 X250 Y450 Z-99999  ; probe near a leadscrew
        G30 P6 X270 Y450 Z-99999  ; probe near a leadscrew
        G30 P7 X470 Y20 Z-99999   ; probe near a leadscrew
        G30 P8 X470 Y5 Z-99999    ; probe near a leadscrew
        G30 P9 X450 Y5 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
        
        M280 P0 S160              ; clear and reset BL touch
        G29 S1                    ; probe the bed and enable compensation
        
        

        More what i found is that the motor attribution doesn't seem to work properly
        while using M584 Z0:0 (and other possible combinations z0:1 or z0:2)
        Sometimes I had two motors rotating and some others I had just one, I suspected I had something wrong with the wires but reverting to 3.3 made the printer fully operational without any physical change on the printer.

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

          @x_pedro_x @tom33 the significant difference between 3.4rc1 (also 3.4beta7) and earlier releases is that in 3.4rc1, when a motor controlled by a CAN-connected board is stopped because and endstop or Z probe is triggered, the slight overshoot that occurs is corrected after a short delay by reversing the motor movement and sending whatever steps are needed. If you are using closed-loop drivers, perhaps they don't handle this situation very well? If so then reducing the speed of the homing or probing move may help.

          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

          x_pedro_xundefined tom33undefined 2 Replies Last reply Reply Quote 0
          • x_pedro_xundefined
            x_pedro_x @dc42
            last edited by

            @dc42 Thanks for the quick reply, on my eagerness to post I forgot valuable information:

            • I'm using a Duet 3 6HC with an SBC
            • Open loop steppers

            In reality it does look like what you explained every now and then the stepper would make a sound like I had mixed the coils (usually after the 2nd probe location, but also on the 3rd) .

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

              @x_pedro_x please post your complete config.g file so that I can reproduce your setup.

              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

              x_pedro_xundefined 1 Reply Last reply Reply Quote 0
              • x_pedro_xundefined
                x_pedro_x @dc42
                last edited by x_pedro_x

                @dc42 Hi,

                You may find all the files here

                Thanks for the help,
                Pedro Oliveira

                1 Reply Last reply Reply Quote 0
                • tom33undefined
                  tom33 @dc42
                  last edited by

                  @dc42 I don't have the problem for the homing just for the probing. And Reduce the acceleration or speed doesn't work for me

                  dc42undefined 1 Reply Last reply Reply Quote 0
                  • dc42undefined dc42 referenced this topic
                  • dc42undefined
                    dc42 administrators @tom33
                    last edited by

                    @tom33 @x_pedro_x this has now been fixed. Please try the new expansion board firmware at https://www.dropbox.com/sh/2dt7sbqpx6l74np/AADn4-lpcil1iqnWKkiVri3Ia?dl=0.

                    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

                    x_pedro_xundefined tom33undefined 3 Replies Last reply Reply Quote 0
                    • x_pedro_xundefined
                      x_pedro_x @dc42
                      last edited by

                      @dc42 I will have to wait a bit, unfortunately i destroyed my sbc (forgot that the camera link is not hot-plugable) and am waiting for a new one 😕
                      As soon as i receive it I'll try the FW.

                      Marcossfundefined 1 Reply Last reply Reply Quote 0
                      • Marcossfundefined
                        Marcossf @x_pedro_x
                        last edited by

                        @x_pedro_x @dc42 I think we have the same problem than you, as David said in our post entry. We will test it tomorrow to see if the 3.4RC1+2 solve the issue.

                        David, do we use all RC1+2 dropbox updated files, or only the one for the 1XD board?

                        Marcossfundefined 1 Reply Last reply Reply Quote 0
                        • Marcossfundefined
                          Marcossf @Marcossf
                          last edited by

                          @x_pedro_x Hi Pedro, we've tested with the David's 1LC 3.4rc1+2 files and it's working fine.

                          1 Reply Last reply Reply Quote 0
                          • tom33undefined
                            tom33 @dc42
                            last edited by

                            @dc42 I try this today !

                            1 Reply Last reply Reply Quote 0
                            • x_pedro_xundefined
                              x_pedro_x @dc42
                              last edited by

                              @dc42 Hi, I tested your files and the homing could be done properly.
                              Just to confirm I reverted to the public rc1 and the problem happens again, using rc1+2 behaves as expected.
                              Thanks for the help.

                              1 Reply Last reply Reply Quote 0
                              • Marcossfundefined Marcossf referenced this topic
                              • Marcossfundefined Marcossf referenced this topic
                              • Marcossfundefined Marcossf referenced this topic
                              • HighFrequndefined HighFreq referenced this topic
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA