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

    Error during print

    Scheduled Pinned Locked Moved
    My Duet controlled machine
    4
    7
    191
    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.
    • Joepundefined
      Joep
      last edited by

      When starting a print every thing works fine, after some time the print stops without any error message, i'm using firmware 2.05 and this is my config.g content.
      ; executed by the firmware on start-up

      ; General preferences
      M669 K1 ; CoreXY mode
      G90 ; Send absolute coordinates...
      M83 ; ...but relative extruder moves

      M555 P0 ; Set firmware compatibility to look like native output

      ; Network
      M550 P JW Duet ; Set machine name
      M552 S1 ; Enable network
      M586 P0 S1 ; Enable HTTP
      M586 P1 S0 ; Disable FTP
      M586 P2 S0 ; Disable Telnet

      ; Drives
      M569 P0 S0 ; Drive 0 goes backwards
      M569 P1 S0 ; Drive 1 goes backwards
      M569 P2 S0 ; Drive 2 goes backwards
      M569 P3 S1 ; Drive 3 goes forwards
      M350 X256 Y256 Z256 E16 I1 ; Configure microstepping with interpolation
      M92 X2576 Y2576 Z20508 E391 ; Set steps per mm
      M566 X4500 Y4500 Z120 E522 ; Set maximum instantaneous speed changes (mm/min)
      M203 X9000 Y9000 Z210 E3600 ; Set maximum speeds (mm/min)
      M201 X2400 Y2400 Z36 E250 ; Set accelerations (mm/s^2)
      M906 X1000 Y1000 Z900 E800 I40 ; Set motor currents (mA) and motor idle factor in per cent
      M84 S20 ; Set idle timeout

      ; Pressure advance
      ;M572 D0 S0.03 ; enabled Pressure advance

      ; Axis Limits
      M208 X-1 Y-1 Z-1 S1 ; Set axis minima
      M208 X315 Y310 Z315 S0 ; Set axis maxima

      ; Endstops
      M574 X1 Y1 S1 ; Set active high endstops

      ; Mi Touch
      M558 P8 F500 H10 I0 T4000
      G31 P500 X0 Y0 Z-1 ; Set Z probe trigger value, neg. cor. bij neg bedhoogte
      M557 X15:290 Y15:280 S90 ; Define mesh grid

      ; Filament sensor
      M591 D0 P1 C3 S1 ; Set Filament sensor extruder 0, connected to nput 3 (E0)

      M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
      M143 H0 S125 ; Set temperature limit for heater 0 to 115C
      M305 P1 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 1
      M307 H1 A286.0 C120.0 D3.3 S1.00 V24.2 B0 ; Set PID for hotend values
      M307 H0 A99.1 C453.2 D2.2 B0 ; Set PID for heated bed values
      M143 H1 S280 ; Set temperature limit for heater 1 to 280C
      ;M303 H1 S280 P1.0 ; autotuning heater 1

      ; Fans
      M106 P0 S0 I0 H-1 ; Set fan 0 value, PWM signal Thermostatic control is turned off
      M106 P1 S1.0 I0 H-1 ; Set fan 1 value, PWM signal Thermostatic control is turned off
      M106 P2 S0 I0 H-1 ; Set fan 2 value, PWM signal Thermostatic control is turned off

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

      ; serial port
      M575 P1 B57600 S1

      ; Automatic power saving
      M911 S21 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

      ; Custom settings are configured
      M912 P0 S-21.7 ;CPU temp sensor correction
      M564 H0 ; Let the Jog buttons work blv: added to allow jog buttons
      ;M375 ;Load height-map.csv
      T0
      G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
      M929 P"\logging\DuetJW.txt" S1 ; start logging to file eventlog.txt
      in my logging file i don't see any points at the moment of stopping.
      This is some text out my eventlog.txt:
      2020-01-13 10:43:27 Started printing file 0:/gcodes/Hemera_FanMountPS.gcode
      2020-01-13 10:45:42 Cancelled printing file 0:/gcodes/Hemera_FanMountPS.gcode, print time was 0h 2m
      2020-01-13 10:45:42 Event logging stopped
      power up + 00:00:01 Event logging started

      Who know the anwser?

      Thanks Joep

      DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by

        Please post the output of M122 after this happens

        1 Reply Last reply Reply Quote 0
        • Joepundefined
          Joep
          last edited by

          Hi Veti,
          the machine is completely blocked after the stop and i can only give a M122 P100 result after a restart. Would that give the error code we need?
          Joep

          1 Reply Last reply Reply Quote 0
          • DIY-O-Sphereundefined
            DIY-O-Sphere @Joep
            last edited by DIY-O-Sphere

            @Joep said in Error during print:

            M350 X256 Y256 Z256 E16 I1 ; Configure microstepping with interpolation
            M92 X2576 Y2576 Z20508 E391 ; Set steps per mm

            https://forum.duet3d.com/topic/13156/duet-stops-mid-print/24?_=1578917458937

            (UTC+1)

            Joepundefined 1 Reply Last reply Reply Quote 0
            • Joepundefined
              Joep @DIY-O-Sphere
              last edited by

              @DIY-O-Sphere
              Thank you this gives a good continue of the print!
              Can you explain why the settings can't be put on 256 steps?
              Thanks Joep

              Phaedruxundefined DIY-O-Sphereundefined 2 Replies Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator @Joep
                last edited by

                @Joep said in Error during print:

                Can you explain why the settings can't be put on 256 steps?

                It's too much for the step pulse generator to handle reliably. Too much stress on the CPU. It's better to set x16 microsteps and let the drivers do the work of sending the x256 pulses to the motors via interpolation.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • DIY-O-Sphereundefined
                  DIY-O-Sphere @Joep
                  last edited by

                  @Joep
                  You can search the forum for “Hiccups” witch is technically the reason for the issue.
                  https://forum.duet3d.com/topic/8688/stepper-movement-hiccups-and-microstepping
                  In the report of M122 the count is displayed.

                  (UTC+1)

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