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

Resolved Print hangs

Scheduled Pinned Locked Moved
Duet Hardware and wiring
2
21
3.0k
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.
  • undefined
    X4TEC
    last edited by 7 Dec 2016, 16:26

    So PSU ruled out, exactly the same results with a Stabilised 12v bench supply, with and without USB

    1 Reply Last reply Reply Quote 0
    • undefined
      X4TEC
      last edited by 7 Dec 2016, 16:28

      @dc42:

      It's odd that you are getting a software reset. Please post your config.g file just in case I can spot anything.

      Note: I added in the heat calibration at the end as I did get some messages about taking to long.

      ; Configuration file for Duet WiFi
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool on Wed Nov 23 2016 20:59:26 GMT+0000 (GMT Standard Time)

      ; General preferences
      M111 S0 ; Debugging off
      G21 ; Work in millimetres
      G90 ; Send absolute coordinates…
      M83 ; ...but relative extruder moves
      M555 P2 ; Set firmware compatibility to look like Marlin
      M208 X0 Y0 Z0 S1 ; Set axis minima
      M208 X195 Y170 Z180 S0 ; Set axis maxima

      ; Endstops
      M574 X1 Y1 Z1 S0 ; Define active low and unused microswitches
      M558 P1 X0 Y0 Z1 H10 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
      G31 P500 X0 Y12 Z1.0 ; Set Z probe trigger value, offset and trigger height

      ; Drives
      M569 P0 S1 ; Drive 0 goes forwards
      M569 P1 S0 ; Drive 1 goes backwards
      M569 P2 S1 ; Drive 2 goes forwards
      M569 P3 S0 ; Drive 3 goes backwards
      M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation
      M92 X78.7402 Y78.7402 Z2133.3333 E106.707 ; Set steps per mm
      M566 X600 Y600 Z0 E180 ; Set maximum instantaneous speed changes (mm/min)
      M203 X30000 Y30000 Z300 E2700 ; Set maximum speeds (mm/min)
      M201 X3000 Y3000 Z100 E3000 ; Set accelerations (mm/s^2)
      M906 X687 Y687 Z687 E687 I30 ; Set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Heaters
      M143 S275 ; Set maximum heater temperature to 275C
      M305 P0 T100000 B4092 C0 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 0
      M305 P1 T100000 B4092 C0 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 1

      ; Tools
      M563 P0 D0 H1 ; Define tool 0
      G10 P0 X0 Y0 ; Set tool 0 axis offsets
      G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

      ; Network
      M550 PMy3dPrinter ; Set machine name
      M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP

      ; Fans
      M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
      M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
      M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

      ; Custom settings are not configured
      ; set my PID values
      M307 H1 A319.6 C149.5 D11.9 B0
      M307 H0 A138.4 C425.4 D11 B0

      1 Reply Last reply Reply Quote 0
      • undefined
        X4TEC
        last edited by 8 Dec 2016, 17:10

        Finally getting prints, looking like I had the config wrong. Id tried to take the figures used in marlin and translate them to RepRapFirmware. Strange there were no errors as such. Still not got reliable prints yet. But it's not crashing

        1 Reply Last reply Reply Quote 0
        • undefined
          dc42 administrators
          last edited by 8 Dec 2016, 17:33

          I am glad you solved it. The only odd thing I can see in your config.g file is the zero jerk speed for the Z axis in the M566 command. I've never tried using a value of zero, so I am wondering whether rounding errors could make the lookahead mechanism keep recalculating to try to meet it. What value are you using now?

          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

          1 Reply Last reply Reply Quote 0
          • undefined
            X4TEC
            last edited by 8 Dec 2016, 23:36

            Spoke to early, froze again halfway through a 50mm test tower

            1 Reply Last reply Reply Quote 0
            • undefined
              X4TEC
              last edited by 9 Dec 2016, 07:09

              @dc42:

              I am glad you solved it. The only odd thing I can see in your config.g file is the zero jerk speed for the Z axis in the M566 command. I've never tried using a value of zero, so I am wondering whether rounding errors could make the lookahead mechanism keep recalculating to try to meet it. What value are you using now?

              I'll upload a little later, but starting to think my config errors maybe just disguising a hardware issue. Just not sure how I can be certain. It's only the controller I've changed.

              1 Reply Last reply Reply Quote 0
              • undefined
                dc42 administrators
                last edited by 9 Dec 2016, 09:42

                @X4TEC:

                @dc42:

                I am glad you solved it. The only odd thing I can see in your config.g file is the zero jerk speed for the Z axis in the M566 command. I've never tried using a value of zero, so I am wondering whether rounding errors could make the lookahead mechanism keep recalculating to try to meet it. What value are you using now?

                I'll upload a little later, but starting to think my config errors maybe just disguising a hardware issue. Just not sure how I can be certain. It's only the controller I've changed.

                I am inclined to agree. I'm also wondering whether it is time for us to swap your Duet WiFi. However, I would like you to do one more thing. I will shortly release firmware 1.17dev8 and this includes a report of the last software reset code in the M122 report, which previously wasn't working on the Duet WiFi. So please update your firmware to 1.17dev8 later today, do a print, and assuming it fails again, run M122, check that the "Last reset" cause is again software and the reset time corresponds to when the print stopped, and extract the "Last software reset code…" line.

                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

                1 Reply Last reply Reply Quote 0
                • undefined
                  X4TEC
                  last edited by 9 Dec 2016, 13:11

                  @dc42:

                  @X4TEC:

                  @dc42:

                  I am glad you solved it. The only odd thing I can see in your config.g file is the zero jerk speed for the Z axis in the M566 command. I've never tried using a value of zero, so I am wondering whether rounding errors could make the lookahead mechanism keep recalculating to try to meet it. What value are you using now?

                  I'll upload a little later, but starting to think my config errors maybe just disguising a hardware issue. Just not sure how I can be certain. It's only the controller I've changed.

                  I am inclined to agree. I'm also wondering whether it is time for us to swap your Duet WiFi. However, I would like you to do one more thing. I will shortly release firmware 1.17dev8 and this includes a report of the last software reset code in the M122 report, which previously wasn't working on the Duet WiFi. So please update your firmware to 1.17dev8 later today, do a print, and assuming it fails again, run M122, check that the "Last reset" cause is again software and the reset time corresponds to when the print stopped, and extract the "Last software reset code…" line.

                  Will do thanks

                  Heres the current config

                  ; Configuration file for Duet WiFi
                  ; executed by the firmware on start-up
                  ;
                  ; generated by RepRapFirmware Configuration Tool on Wed Nov 23 2016 20:59:26 GMT+0000 (GMT Standard Time)

                  ; General preferences
                  M111 S0 ; Debugging off
                  G21 ; Work in millimetres
                  G90 ; Send absolute coordinates…
                  M83 ; ...but relative extruder moves
                  M555 P2 ; Set firmware compatibility to look like Marlin
                  M208 X0 Y0 Z0 S1 ; Set axis minima
                  M208 X190 Y170 Z180 S0 ; Set axis maxima

                  ; Endstops
                  M574 X1 Y1 Z1 S0 ; Define active low and unused microswitches
                  M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
                  G31 P500 X0 Y12 Z1.7 ; Set Z probe trigger value, offset and trigger height

                  ; Drives
                  M569 P0 S1 ; Drive 0 goes forwards
                  M569 P1 S0 ; Drive 1 goes backwards
                  M569 P2 S1 ; Drive 2 goes forwards
                  M569 P3 S0 ; Drive 3 goes backwards
                  M350 X16 Y16 Z16 E16 I1 ; Configure microstepping without interpolation ab i0-1
                  M92 X78.7402 Y78.7402 Z2133.3333 E106.707 ; Set steps per mm
                  M566 X600 Y600 Z30 E20 ; Set maximum instantaneous speed changes (mm/min) ab 8/12 ( Z0 - Z30; E180 - E20)
                  M203 X15000 Y15000 Z300 E3600 ; Set maximum speeds (mm/min) ab 8/12 (x30000 - 15000 y30000-15000, E2700-3600
                  M201 X800 Y800 Z15 E1000 ; Set accelerations (mm/s^2) ab 8/12 ( x 3000-800 y 3000-800, z100-15 E3000 - 1000)
                  M906 X800 Y800 Z800 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent AB 08/12 changed current all form 678 - 800
                  M84 S30 ; Set idle timeout

                  ; Heaters
                  M143 S275 ; Set maximum heater temperature to 275C
                  M305 P0 T100000 B4092 C0 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 0
                  M305 P1 T100000 B4092 C0 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 1 AB 08/12 B4096-4388
                  ;M301 H0 P10 I0.10 D100 T0.50 S1.0
                  ;M301 H1 P10 I0.10 D100 T0.50 S1.0
                  M570 S120; Increase to allow extra heating time if needed AB 08/12

                  ; Tools
                  M563 P0 D0 H1 ; Define tool 0
                  G10 P0 S0 R0 X0 Y0 ; Set tool 0 axis offsets Set initial tool 0 active and standby temperatures to 0C

                  ; Network
                  M550 PMy3dPrinter ; Set machine name
                  M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP

                  ; Fans
                  M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
                  M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
                  M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

                  ; Custom settings are not configured
                  ; set my PID values
                  ;M307 H1 A319.6 C149.5 D11.9 B0 ; Disabled AB 08/12
                  ;M307 H0 A138.4 C425.4 D11 B0 ; Disabled AB 08/12
                  T0 ; Select first tool

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators
                    last edited by 9 Dec 2016, 14:17

                    I have just released the 1.17dev8 build.

                    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

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      X4TEC
                      last edited by 9 Dec 2016, 16:52

                      @dc42:

                      I have just released the 1.17dev8 build.

                      Just updated and run a test job. I may have been a little zealous in declaring the last failure. I'm used to the job finishing and parking the print head to one side, where as it doesn't look like the firmware does that for you. So when I came back to my tower, the head was sat at the top, as if it had crashed.. I'm still not getting very good print out put maybe down to configuration rather than faults.

                      BTW, really appreciate your help.

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        dc42 administrators
                        last edited by 9 Dec 2016, 17:59

                        To park the head when the print finished, add appropriate moving and/or homing commands at the end of your slicer end gcode, just before the M0 at the end. Alternatively, just put M0 in your slicer end gcode and define the shutdown sequence in /sys/stop.g.

                        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

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          X4TEC
                          last edited by 10 Dec 2016, 10:50

                          @dc42:

                          To park the head when the print finished, add appropriate moving and/or homing commands at the end of your slicer end gcode, just before the M0 at the end. Alternatively, just put M0 in your slicer end gcode and define the shutdown sequence in /sys/stop.g.

                          Many thanks, I believe my original resetting issues have been resolved. I'm still trying to get a print out of the machine, as my use of the manufacturers Marlin settings, plus a possible extruder issue has caused me some problems. Once i get over this hurdle in the next few days, I will play with my setting to help find the original cause. It does sound like its probably that zero jerk speed for the Z axis in the M566 command.

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