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

    Printer Pausing Near End of Print

    Scheduled Pinned Locked Moved
    General Discussion
    3
    6
    238
    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.
    • Tommygunzundefined
      Tommygunz
      last edited by

      Hello. I recently just converted my Anet A8 motherboard to a duet wifi board. Once I set up the board, I followed my calibration process (PID tunes, extrusion calibration) and printed a test cube. However, near the end of the print (about 98% completion) my just printer stops on top of the print with the heaters off. The printer still says it is printing, its just not doing anything. I though it was the firmware so I upgraded it to RRF3. Same issue. Here is my g-code:

      ; Configuration file for Duet WiFi (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat May 16 2020 14:23:01 GMT-0500 (Central Daylight Time)

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"Tom" ; set printer name
      M575 P1 B57600 S1 ;Set baud rate Duet Board.
      M575 P0 B57600 S1 ;Set baud rate USB

      ; Network
      M551 P"" ; 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 S1 ; physical drive 1 goes forwards
      M569 P2 S0 ; physical drive 2 goes backwards
      M569 P3 S1 ; physical drive 3 goes forwards
      M584 X0 Y1 Z2 E3 ; set drive mapping
      M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
      M92 X100.00 Y100.00 Z400.00 E414.44 ; set steps per mm
      M566 X600.00 Y600.00 Z18.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X6000.00 Y6000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
      M201 X1500.00 Y1500.00 Z100.00 E10000.00 ; set accelerations (mm/s^2)
      M906 X500 Y500 Z500 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X-30 Y-8 Z0 S1 ; set axis minima
      M208 X220 Y220 Z240 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"!xstop" ; configure active-low endstop for low end on X via pin xstop
      M574 Y1 S1 P"!ystop" ; configure active-low endstop for low end on Y via pin ystop
      M574 Z1 S1 P"!zstop" ; configure active-low endstop for low end on Z via pin zstop

      ; Z-Probe
      M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
      M557 X20:200 Y20:200 S40 ; define mesh grid

      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin bedtemp
      M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
      M143 H0 S130 ; set temperature limit for heater 0 to 130C
      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
      M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
      M143 H1 S280 ; set temperature limit for heater 1 to 280C
      M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

      ; Fans
      M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan1" Q100 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S70 H-1 ; set fan 1 value. Thermostatic control is turned off
      M950 F2 C"fan2" Q50 ; create fan 2 on pin fan2 and set its frequency
      M106 P2 S150 H-1 ; set fan 2 value. Thermostatic contol is turned off

      ; Tools
      M563 P0 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

      ; Custom settings are not defined

      ; Miscellaneous
      T0 ; select first tool
      M501

      Here is what the M122 command shows when the problem occurs:

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.0 running on Duet WiFi 1.02 or later
      Board ID: 08DLM-996RU-N8PS0-7JTDG-3SN6S-TVB7Q
      Used output buffers: 3 of 24 (22 max)
      === RTOS ===
      Static ram: 28180
      Dynamic ram: 93540 of which 20 recycled
      Exception stack ram used: 568
      Never used ram: 8764
      Tasks: NETWORK(ready,100) HEAT(blocked,1216) MAIN(running,1880) IDLE(ready,80)
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:13:52 ago, cause: power up
      Last software reset at 2020-05-18 16:55, reason: User, spinning module GCodes, available RAM 8956 bytes (slot 1)
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
      Error status: 0
      MCU temperature: min 26.6, current 27.0, max 27.3
      Supply voltage: min 11.7, current 12.9, max 13.0, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: standstill, SG min/max not available
      Driver 1: standstill, SG min/max not available
      Driver 2: standstill, SG min/max not available
      Driver 3: ok, SG min/max 0/350
      Driver 4: standstill, SG min/max not available
      Date/time: 2020-05-18 19:12:37
      Cache data hit count 1395047326
      Slowest loop: 8.94ms; fastest: 0.12ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 9
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest read time 3.6ms, write time 0.0ms, max retries 0
      === Move ===
      Hiccups: 0(0), FreeDm: 168, MinFreeDm: 150, MaxWait: 0ms
      Bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 3638, completed moves: 3636, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      === Heat ===
      Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      Heater 0 is on, I-accum = 0.5
      Heater 1 is on, I-accum = 0.3
      === GCodes ===
      Segments left: 0
      Movement lock held by File
      HTTP is idle in state(s) 0
      Telnet is idle in state(s) 0
      File is doing "G28 X0 Y0 " in state(s) 0
      USB is idle in state(s) 0
      Aux is idle in state(s) 0
      Trigger is idle in state(s) 0
      Queue is idle in state(s) 0
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 201.13ms; fastest: 0.09ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 1 of 8

      • WiFi -
        Network state is active
        WiFi module is connected to access point
        Failed messages: pending 0, notready 0, noresp 1
        WiFi firmware version 1.23
        WiFi MAC address bc:dd:c2:2d:68:c1
        WiFi Vcc 3.44, reset reason Unknown
        WiFi flash size 4194304, free heap 24008
        WiFi IP address
        WiFi signal strength -62dBm, reconnections 0, sleep mode modem
        Socket states: 0 0 0 0 0 0 0 0
      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        So it stops at exactly the same point in the gcode file?

        Can you post that gcode file please?

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk
          last edited by

          It's an issue with 3.1.0. Please update to 3.1.1

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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

            @Tommygunz said in Printer Pausing Near End of Print:

            I though it was the firmware so I upgraded it to RRF3. Same issue.

            @jay_s_uk though this makes it sound like he was on RRF2 previously when the issue happened.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk
              last edited by

              @Phaedrux sorry, missed that bit.

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              1 Reply Last reply Reply Quote 1
              • Tommygunzundefined
                Tommygunz
                last edited by

                It was the software. Updated it to 3.1.1 and the problem went away!

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