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

    [Firmware 3.2beta3] Can't resume after a filament-error0.g

    Scheduled Pinned Locked Moved
    Beta Firmware
    firmware 3.2beta3
    5
    24
    854
    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.
    • jay_s_ukundefined
      jay_s_uk @Krohm Koala
      last edited by

      @chrishamm

      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 0
      • chrishammundefined
        chrishamm administrators
        last edited by

        @Krohm-Koala Provided you're using a Duet 3 MB6HC, please try to upgrade to this firmware build: : https://pkg.duet3d.com/Duet3Firmware_MB6HC.bin

        @jay_s_uk Does the same problem persist with this firmware build? https://pkg.duet3d.com/Duet3Firmware_Mini5plus_v02.uf2

        I haven't had any issues with pause/resume/cancel with the latest firmware build yet.

        Duet software engineer

        Krohm Koalaundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
        • Krohm Koalaundefined
          Krohm Koala @chrishamm
          last edited by

          @chrishamm sorry, forgot it, i'm on a duet 2 wifi

          chrishammundefined 1 Reply Last reply Reply Quote 0
          • chrishammundefined
            chrishamm administrators @Krohm Koala
            last edited by

            @Krohm-Koala In that case please share the output of M122.

            Duet software engineer

            Krohm Koalaundefined 2 Replies Last reply Reply Quote 0
            • Krohm Koalaundefined
              Krohm Koala @chrishamm
              last edited by

              @chrishamm here it is

              10/11/2020 à 19:27:25	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta3 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J9DG-3SJ6Q-KBWBG
Used output buffers: 3 of 24 (20 max)
=== RTOS ===
Static ram: 23996
Dynamic ram: 100880 of which 24 recycled
Never used RAM 5148, free system stack 200 words
Tasks: NETWORK(ready,166) HEAT(blocked,308) MAIN(running,466) IDLE(ready,19)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 70:25:50 ago, cause: software
Last software reset at 2020-11-07 21:01, reason: User, GCodes spinning, available RAM 4904, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0x00
MCU temperature: min 25.6, current 26.3, max 35.1
Supply voltage: min 0.4, current 0.5, max 24.5, under voltage events: 1, over voltage events: 0, power good: no
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2020-11-10 19:27:12
Cache data hit count 4294967295
Slowest loop: 7.07ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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
LCD 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: 24.61ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.24beta2-05b1
WiFi MAC address 84:f3:eb:42:b3:87
WiFi Vcc 3.34, reset reason Power up
WiFi flash size 4194304, free heap 25096
WiFi IP address 192.168.1.33
WiFi signal strength -63dBm, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
              1 Reply Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @chrishamm
                last edited by

                @chrishamm Thats fixed the issue for me thanks.
                Now pausing and resuming correctly

                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 0
                • Krohm Koalaundefined
                  Krohm Koala @chrishamm
                  last edited by

                  @chrishamm Have you got time to check the result ? or do you need something else ?

                  chrishammundefined 1 Reply Last reply Reply Quote 0
                  • chrishammundefined
                    chrishamm administrators @Krohm Koala
                    last edited by

                    @Krohm-Koala It should be fixed with RRF 3.2.0-b3.2, available from the unstable package feed. Your diagnostics output showed that you were still using 3.2.0-b3.

                    Let me know if the same problem is still present in that version.

                    Duet software engineer

                    Krohm Koalaundefined 3 Replies Last reply Reply Quote 0
                    • Krohm Koalaundefined
                      Krohm Koala @chrishamm
                      last edited by

                      @chrishamm i'll try as soon as my print finish and come back to you 🙂 thanks 🙂

                      1 Reply Last reply Reply Quote 0
                      • Krohm Koalaundefined
                        Krohm Koala @chrishamm
                        last edited by

                        @chrishamm So i've upgrade to beta 3.2, and still the same, here is the M122 after the error-gcode is done, the file haven't change since :

                        M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta3.2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J9DG-3SJ6Q-KBWBG
Used output buffers: 3 of 24 (22 max)
=== RTOS ===
Static ram: 24108
Dynamic ram: 101512 of which 60 recycled
Never used RAM 4368, free system stack 114 words
Tasks: NETWORK(ready,136) HEAT(blocked,308) MAIN(running,435) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:09:08 ago, cause: software
Last software reset at 2020-11-14 06:57, reason: User, GCodes spinning, available RAM 5148, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0x00
MCU temperature: min 33.0, current 34.8, max 35.2
Supply voltage: min 0.3, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 2000, standstill, SG min/max 0/530
Driver 1: position 1400, standstill, SG min/max 0/443
Driver 2: position 2217, standstill, SG min/max 0/0
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2020-11-24 21:50:46
Cache data hit count 866645660
Slowest loop: 107.87ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.8ms, write time 40.4ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 143, MaxWait: 111806ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 546, completed moves 546, StepErrors 0, LaErrors 0, Underruns [0, 0, 4], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.7
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0 0 25, running macro
Code queue is empty.
=== Network ===
Slowest loop: 85.57ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.24beta2-05b1
WiFi MAC address 84:f3:eb:42:b3:87
WiFi Vcc 3.34, reset reason Power up
WiFi flash size 4194304, free heap 26600
WiFi IP address 192.168.1.33
WiFi signal strength -69dBm, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
                        1 Reply Last reply Reply Quote 0
                        • Krohm Koalaundefined
                          Krohm Koala @chrishamm
                          last edited by

                          Hi @chrishamm i've updated to beta 4 and the problem is different, at the end of the macro, the printing resume automatically without going to previous Z position, XY are good but the interface locks in "pause" state so the print is running and i can't pause or cancel. Here is the M122 that i've done just after it resumed:

                          M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta4 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J9DG-3SJ6Q-KBWBG
Used output buffers: 3 of 24 (23 max)
=== RTOS ===
Static ram: 24108
Dynamic ram: 101308 of which 236 recycled
Never used RAM 4396, free system stack 100 words
Tasks: NETWORK(ready,158) HEAT(blocked,308) MAIN(running,390) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 57:54:31 ago, cause: software
Last software reset at 2020-11-26 21:20, reason: User, GCodes spinning, available RAM 4780, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0x08
MCU temperature: min 25.3, current 34.6, max 37.9
Supply voltage: min 0.4, current 24.2, max 24.7, under voltage events: 7, over voltage events: 0, power good: yes
Driver 0: position 26467, ok, SG min/max 0/1023
Driver 1: position 5481, ok, SG min/max 0/522
Driver 2: position 319, ok, SG min/max 0/96
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2020-11-29 07:14:55
Cache data hit count 4294967295
Slowest loop: 167.67ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 5.8ms, write time 48.1ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 165, MinFreeDm: 103, MaxWait: 78729874ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 814, completed moves 792, StepErrors 0, LaErrors 0, Underruns [0, 0, 25], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.8
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X132.337 Y34.381 E33.01870" 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
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0 0 25, running macro
Code queue is not empty:
Queued 'M106 P3 S1.0����������������������������������������������������' for move 795
Queued 'M106 P3 S1.0����������������������������������������������������' for move 804
2 of 16 codes have been queued.
=== Network ===
Slowest loop: 164.71ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.24beta2-05b1
WiFi MAC address 84:f3:eb:42:b3:87
WiFi Vcc 3.34, reset reason Power up
WiFi flash size 4194304, free heap 26280
WiFi IP address 192.168.1.33
WiFi signal strength -70dBm, mode none, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
                          1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators
                            last edited by

                            @Krohm-Koala, does normal pause and resume work correctly?

                            Please post your resume.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

                            Krohm Koalaundefined 1 Reply Last reply Reply Quote 0
                            • Krohm Koalaundefined
                              Krohm Koala
                              last edited by Krohm Koala

                              Hi @dc42, normal pause and resume work perfectly, i don't know why but filament errors resume automatically without calling the resume (it stays at Z pause height).
                              I've just tested in the last pre-release beta 4.1, exactly the same thing.

                              Here is the resume.g

                              ; resume.g
; called before a print from SD card is resumed
;
; generated by RepRapFirmware Configuration Tool v2 on Tue Dec 25 2018 07:35:06 GMT+0100 (heure normale d’Europe centrale)
G1 R1 X0 Y0 Z5 F6000 ; go to 5mm above position of the last print move
G1 R1 X0 Y0          ; go back to the last print move
M83                  ; relative extruder moves
;G1 E10 F3600         ; extrude 10mm of filament
                              1 Reply Last reply Reply Quote 0
                              • Krohm Koalaundefined
                                Krohm Koala @dc42
                                last edited by

                                Hi @dc42 I've just updated to the 3.2RC1, still act as before, is there something i can do to have more info about what's going on at this moment ? If it can help, could be good 🙂 I don't know if i'm the only one to have this issue.

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

                                  Can you confirm if this is still a problem in 3.2 RC2?

                                  Z-Bot CoreXY Build | Thingiverse Profile

                                  Krohm Koalaundefined 1 Reply Last reply Reply Quote 0
                                  • Krohm Koalaundefined
                                    Krohm Koala @Phaedrux
                                    last edited by

                                    @Phaedrux I've just tested, yes, still a problem in 3.2 RC2.

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

                                      @Krohm-Koala said in [Firmware 3.2beta3] Can't resume after a filament-error0.g:

                                      @Phaedrux I've just tested, yes, still a problem in 3.2 RC2.

                                      Can you confirm that you are running regular RRF on your Duet in standalone mode, not the SBC version?

                                      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

                                      Krohm Koalaundefined 1 Reply Last reply Reply Quote 0
                                      • Krohm Koalaundefined
                                        Krohm Koala @dc42
                                        last edited by

                                        @dc42 Yes I'm running a duet2 wifi with regular rrf standalone (never really fond how sbc works on duet 2 🤣🤣)

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

                                          Are you turning any axis motors off while the print is paused? Resume.g won't be called if any axes are flagged as not homed.

                                          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

                                          Krohm Koalaundefined 1 Reply Last reply Reply Quote 0
                                          • Krohm Koalaundefined
                                            Krohm Koala @dc42
                                            last edited by

                                            @dc42 No i don't turn any axis off, i just move the extruder + some meta code (exactly what i've put in my first post), it's weird that it's resuming directly after the purge is ending (i have a dialog to validate normally before i do anything else but it skip that) and it don't call resume.g

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