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

    tool position freeze (3.2.2)

    Scheduled Pinned Locked Moved
    Duet Web Control
    3
    19
    741
    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.
    • Pseud3mysundefined
      Pseud3mys @dc42
      last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • Pseud3mysundefined
        Pseud3mys @dc42
        last edited by Pseud3mys

        @dc42 I updated the boards to 3.3beta2 but is still freeze (I have the web interface 3.2.2).
        Is there an other way to create a pin for a Z probe (it is a simple button) ?

        Phaedruxundefined 1 Reply Last reply Reply Quote 0
        • Pseud3mysundefined
          Pseud3mys @dc42
          last edited by

          @dc42 rerefind what go wrong, it is the K parameter
          this work fine:

          M558 P8 C"^!125.io0.in" F300 T3000
          

          and this start the freeze thing:

          M558 K1 P8 C"^!125.io0.in" F300 T3000
          

          In fact this paramerter is not in the M558 doc:
          https://duet3d.dozuki.com/Wiki/Gcode#Section_M558_Set_Z_probe_type

          but in this section it is given as an exemple:
          https://duet3d.dozuki.com/Wiki/Gcode#Section_M585_Probe_Tool

          New code:

          M558 K1 P5 C"!e0stop" ; create probe #1 for use with M585, active low

          ...

          M585 X100 F600 P1 S0 ; probe X until probe #1 is triggered

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

            @pseud3mys, please share your complete config.g file.

            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

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

              @pseud3mys said in tool position freeze (3.2.2):

              I updated the boards to 3.3beta2 but is still freeze (I have the web interface 3.2.2).

              YOu may also need DWC to match.

              https://github.com/Duet3D/RepRapFirmware/releases/download/3.3beta2/DuetWebControl-SD-3.3b2.zip

              Z-Bot CoreXY Build | Thingiverse Profile

              Pseud3mysundefined 2 Replies Last reply Reply Quote 0
              • Pseud3mysundefined
                Pseud3mys @dc42
                last edited by Pseud3mys

                @dc42 , this is my config file for 3.3beta2 with a little change for 3.3beta2

                ; executed by the firmware on start-up
                
                
                ; General preferences
                G90                                                          ; send absolute coordinates...
                M83                                                          ; ...but relative extruder moves
                M550 P"MultiTool Cartesian"                                  ; set printer name
                
                ;emergency stop !
                M950 J0 C"^io0.in"
                M581 P0 T0 S1 R0
                
                ; Network
                M552 P0.0.0.0 S1                                             ; enable network and acquire dynamic address via DHCP
                M586 P0 S1                                                   ; enable HTTP
                M586 P1 S0                                                   ; disable FTP
                M586 P2 S0                                                   ; disable Telnet
                
                
                ; Drives
                G4 S1   ;wait for expansion boards to start
                
                ; Extruders
                M569 P121.0 S1 D3 V2000	; ToolBoard drive 121.0 goes forwards
                M569 P122.0 S1 D3 V2000	; ToolBoard drive 122.0 goes forwards
                M584 E121.0:122.0       ; set extruders drivers
                M350 E64:64 I0          ; configure microstepping without interpolation for extruder
                ; speed
                M92 E415.00:415.00		; set steps per mm
                M203 E1200.00:1200.00	; set maximum speeds (mm/min)
                M201 E250.00:250.00		; set accelerations (mm/s^2)
                M566 E120.00:120.00		; set maximum instantaneous speed changes (mm/min)
                M906 E800:800			; set motor currents (mA)
                
                
                
                G10 L2 P1 X0.00 Y0.00 Z0.00 ;reset the 1st coordinate system to coorspond to the machine one
                ;XYZ axis
                M569 P41.0 S1 R0 T2.6:2.6:0:5	; X
                M569 P40.0 S0 R0 T2.6:2.6:0:5	; Y
                M569 P42.0 S0 R0 T2.6:2.6:0:5	; Z
                M584 Y40.0 X41.0 Z42.0			; set Y, X and Z drivers
                ;speed
                M92 X125.00 Y125.00 Z125.00 		; step per mm
                M203 X19200.00 Y19200.00 Z15000.00 	; maximum speeds (mm/min)
                M566 X900.00 Y900.00 Z900.00 		; maximum instantaneous speed changes (mm/min)
                M201 X1500.00 Y1200.00 Z800.00 		; accelerations (mm/s^2). théorical max: 6400
                
                M84 S0	; Disable motor idle current reduction
                
                
                ; Axis Limits
                M208 X0 Y0 Z0 S1                                             ; set axis minima
                M208 X1000 Y950 Z500 S0                                     ; set axis maxima
                
                
                ;alarms
                ;X axis fail
                M950 J10 C"41.io2.in" ; create a GPIO pin number 2 on 1XD board at CAN address 41 for alarm reset
                M581 P10 S0 T10 ; invoke trigger 10 when an active-to-inactive edge is detected on input 10
                
                ;Yaxis fail
                M950 J11 C"40.io2.in" ; create a GPIO pin number 2 on 1XD board at CAN address 40 for alarm reset
                M581 P11 S0 T11 ; invoke trigger 11 when an active-to-inactive edge is detected on input 11
                
                ;Z axis fail
                M950 J12 C"42.io2.in" ; create a GPIO pin number 2 on 1XD board at CAN address 42 for alarm reset
                M581 P12 S1 T12 ; invoke trigger 12 when an inactive-to-active edge is detected on input 12
                
                
                ; Endstops
                M574 X2 S1 P"41.io1.in"
                M574 Y1 S1 P"40.io1.in"
                M574 Z2 S1 P"42.io1.in"
                
                
                ; Z-Probe
                ; Spindle board Z probe
                ; ! All work fine without this line:
                ; M558 P8 K2 C"^!125.io0.in" F300 T3000
                
                
                ; Heaters
                M308 S0 P"temp0" Y"thermistor" T100000 B4138		; configure sensor 0 as thermistor on pin temp0
                M950 H0 C"out0" T0                                  ; create bed heater output on out0 and map it to sensor 0
                M307 H0 B0 S1.00                                    ; disable bang-bang mode for the bed heater and set PWM limit
                M140 H0                                             ; map heated bed to heater 0
                M143 H0 S120                                        ; set temperature limit for heater 0 to 120C
                
                ; configure sensor 1 as thermistor on pin 121.temp0
                M308 S1 P"121.temp0" Y"thermistor" T500000 B3600 C1.196220e-7 H-12
                M950 H1 C"121.out0" T1		; create nozzle heater output on 121.out0 and map it to sensor 1
                M307 H1 B0 S0.35            ; disable bang-bang mode for heater  and set PWM limit
                M143 H1 P1 S285 A0 			; raise a heater fault if it exceeds 285C
                
                ; configure sensor 2 as thermistor on pin 122.temp0
                M308 S2 P"122.temp0" Y"thermistor" T500000 B3600 C1.196220e-7 H-15 L-12
                M950 H2 C"122.out0" T2      ; create nozzle heater output on 122.out0 and map it to sensor 2
                M307 H2 B0 S0.35            ; disable bang-bang mode for heater  and set PWM limit
                M143 H1 P1 S285 A0 			; raise a heater fault if it exceeds 285C
                
                ; Fans de hotend
                M950 F0 C"121.out2" Q500                                     ; create fan 0 on pin 121.out2 and set its frequency
                M106 P0 S0 H1 T45 L255										 ; set fan 0 value. Thermostatic control is turned on (ON/OFF, no PWM)
                M950 F1 C"122.out2" Q500                                     ; create fan 1 on pin 122.out2 and set its frequency
                M106 P1 S0 H2 T45 L255                                      ; set fan 1 value. Thermostatic control is turned on (ON/OFF, no PWM)
                
                ; Fans de filaments
                
                
                
                ; Tools
                M563 P0 S"Extrudeur 0" D0 H1 F0                              ; define tool 0
                G10 P0 X0 Y0 Z0                                              ; set tool 0 axis offsets
                G10 P0 R0 S0                                                 ; set initial tool 0 active and standby temperatures to 0C
                M563 P1 S"Extrudeur 1" D1 H2 F1                              ; define tool 1
                G10 P1 X0 Y0 Z0                                              ; set tool 1 axis offsets
                G10 P1 R0 S0                                                 ; set initial tool 1 active and standby temperatures to 0C
                
                ; !! for version 3.3
                M950 R0 C"!out9" L12000 ; Create spindle index 0, with PWM pin on heater 3 and 12000 RPM achieved at full PWM
                M563 P2 S"Spindle" R0 ; Create tool 1 with spindle 0 and call it "Spindle"
                
                ; !! version 3.x
                ; M563 P2 S"Spindle" F-1                                       ; define tool 2
                ; M453 C"!out9" Q100 T2 R12000
                G10 P2 X0 Y0 Z0                                              ; set tool 2 axis offsets
                M5
                ; relay spdindle activation
                M950 P8 C"out4"	; create output
                M42 P8 S0	; desactivate it
                
                ;M563 P3 S"Laser" F-1                                        ; define tool 3
                ;G10 P3 X0 Y0 Z0                                             ; set tool 3 axis offsets
                
                
                ; Triggers
                ; extrudeur 0 and 1 toolboard
                M950 J2 C"!121.button0"
                M581 P2 T2 S0
                M950 J3 C"!121.button1"
                M581 P3 T3 S0
                M950 J4 C"!122.button0"
                M581 P4 T4 S0
                M950 J5 C"!122.button1"
                M581 P5 T5 S0
                
                ; spindle board:
                M950 J6 C"!125.button0"
                M581 P6 T6 S0
                M950 J7 C"!125.button1"
                M581 P7 T7 S0
                
                
                ; Miscellaneous
                M501                                                         ; load saved parameters from non-volatile memory
                M929 P"logs/log.txt" S1 ; start log
                
                
                1 Reply Last reply Reply Quote 0
                • Pseud3mysundefined
                  Pseud3mys @Phaedrux
                  last edited by

                  @phaedrux okay thank you, I will make the complete update.

                  1 Reply Last reply Reply Quote 0
                  • Pseud3mysundefined
                    Pseud3mys @Phaedrux
                    last edited by Pseud3mys

                    @phaedrux the bug stay the same in 3.2.2 or in 3.3beta2 (with the right DWC version). It is the all "status" box how freeze (the status "idle" don't go to "busy", speed and coordinates don't change) just the sensors part is not impacted.

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

                      @pseud3mys, I'm running your config.g file with tool boards at addresses 121 and 125. I sent G92 X0 Y0 Z0 to pretend-home the printer. I un-commented the M558 K2 line.

                      When I command movement in X and/or Y and/or Z, the status goes busy for a short while and the coordinates in the display change as expected.

                      I am running in standalone mode using the main board firmware, tool board firmware and DWC at https://www.dropbox.com/sh/dupd9u1xppr1om5/AADYg4guuj2n8LJokVqtK-C7a?dl=0. Please try those files.

                      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

                      Pseud3mysundefined 1 Reply Last reply Reply Quote 0
                      • Pseud3mysundefined
                        Pseud3mys
                        last edited by

                        @dc42 I change the firmawre and DWC with your files and I try with my setup (3 extarnals drivers boards (CAN 40, 41, 42) and one toolboard with CAN 125) in standalone but only the busy status goes fine, the coordinate and speed still freeze after I send exactly this command (the same that in the config.g file).

                        M558 P8 K2 C"^!125.io0.in" F300 T3000
                        
                        dc42undefined 1 Reply Last reply Reply Quote 0
                        • Pseud3mysundefined
                          Pseud3mys @dc42
                          last edited by Pseud3mys

                          @dc42 To overcome this issues I use the 3.3beta2 metacommand:

                          ; in my config.g file:
                          M950 J8 C"^!125.io0.in"
                          
                          
                          ; in a macros:
                          G91
                          while sensors.gpIn[8].value == 0 ; this loop run fine
                          	G1 Z-0.01 F500
                          G0 Z20 F300
                          M400
                          while sensors.gpIn[8].value == 0
                          	G1 Z-0.01 F100
                          G90
                          

                          And I have one question:

                          • and after, can this replace a Z probe ? did the loop will stop at the exact moment the button is closed (with this 0.01 resolution) ?

                          Thank you for your time and help !

                          Pseud3mysundefined 1 Reply Last reply Reply Quote 0
                          • Pseud3mysundefined
                            Pseud3mys @Pseud3mys
                            last edited by Pseud3mys

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • dc42undefined
                              dc42 administrators @Pseud3mys
                              last edited by dc42

                              @pseud3mys said in tool position freeze (3.2.2):

                              @dc42 I change the firmawre and DWC with your files and I try with my setup (3 extarnals drivers boards (CAN 40, 41, 42) and one toolboard with CAN 125) in standalone but only the busy status goes fine, the coordinate and speed still freeze after I send exactly this command (the same that in the config.g file).

                              M558 P8 K2 C"^!125.io0.in" F300 T3000
                              

                              I managed to reproduce this by sending the command again. The Object Model browser reports the positions correctly, so this appears to be a bug in DWC. One for @chrishamm. https://github.com/Duet3D/DuetWebControl/issues/357

                              I found a workaround: create Z probe 0 as well.

                              dc42 created this issue in Duet3D/DuetWebControl

                              closed Tool position coordinates freeze if you have Z probe #2 but not #0 #357

                              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

                              Pseud3mysundefined 1 Reply Last reply Reply Quote 0
                              • Pseud3mysundefined
                                Pseud3mys @dc42
                                last edited by

                                @dc42 ok thank you !

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