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



  • Hi,

    I've just installed the 3.2beta3 and i was doing some tests of the filament-error thing, because it's a thing i really wanted but i encountered the issue that i can't resume my print after a filament runout...

    Here is my code

    M291 R"Erreur de filament" P"Déplacement vers la position de parking."S0 T30
    if move.axes[2].machinePosition < move.axes[2].max-10
        G91
        G1 Z5 F500
    G90
    G1 X{move.axes[0].min+10} Y{move.axes[1].min+10} F6000
    
    M291 R"Erreur de filament" P"Déchargement en cours, veuillez patienter..." S0 T30
    
    G1 E5 F500     ;Extrude 10mm filament at low speed
    G1 E-30 F500
    G1 E-100 F3600	;Retract 100mm filament at high speed
    M400
    
    while sensors.filamentMonitors[0].status == "ok"
        M291 R"Erreur de filament" P"Merci de retirer le filament." S0 T30
        G4 S0.1  ;attendre 0.1s pour éviter de surcharger le processeur
    while true
        if sensors.filamentMonitors[0].status == "noFilament"
            M291 R"Erreur de filament" P"Filament déchargé, merci d''insérer le nouveau filament." S0 T30
            G4 S0.1  ;attendre 0.1s pour éviter de surcharger le processeur
        else
            break
    G4 S0.7  ;attendre 1s pour laisser le temps d'insérer le filament
    
    M291 P"Chargement en cours...." R"Changement du Filament" S0
    M106 S255  ;mise en route du ventilateur pour refroidir la purge
    
    G1 E65 F3600	; extrude 65mm at high speed
    M83     	; mode d'extrusion relative
    G1 E20 F200	; extrude 10mm at low speed
    
    M291 R"Erreur de filament" P"Filament chargé. Vous pouvez relancer l''impression." S2
    


  • I also confirm I cannot resume from a normal pause.
    Duet mini 5+ and SBC

    m122
    === Diagnostics ===
    RepRapFirmware for Duet 3 Mini 5+ prototype v0.2 version 3.2-beta3 running on Duet 3 Mini5plus_v02 WiFi (SBC mode)
    Board ID: 8ULVP-1D6P9-F65J0-401FQ-2A03Z-RJW1V
    Used output buffers: 1 of 40 (10 max)
    === RTOS ===
    Static ram: 86072
    Dynamic ram: 112824 of which 76 recycled
    Never used RAM 62148, free system stack 122 words
    Tasks: Linux(ready,99) HEAT(blocked,301) TMC(blocked,69) MAIN(running,433) IDLE(ready,19) AIN(blocked,267)
    Owned mutexes: HTTP(MAIN)
    === Platform ===
    Last reset 00:35:34 ago, cause: software
    Last software reset at 2020-11-07 19:43, reason: User, none spinning, available RAM 62392, slot 1
    Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0xffffffff Task Linu
    Error status: 0x00
    Supply voltage: min 0.0, current 12.6, max 12.7, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: position 16000, standstill, SG min/max 0/426, read errors 0, write errors 1, ifcnt 103, reads 41215, writes 18, timeouts 107, DMA errors 0, failedOp 0x6f
    Driver 1: position 13000, standstill, SG min/max 0/378, read errors 0, write errors 1, ifcnt 102, reads 41305, writes 18, timeouts 16, DMA errors 0, failedOp 0x6f
    Driver 2: position 2568, standstill, SG min/max 0/234, read errors 0, write errors 1, ifcnt 108, reads 41315, writes 24, timeouts 0, DMA errors 0
    Driver 3: position 0, standstill, SG min/max 0/284, read errors 0, write errors 1, ifcnt 108, reads 41315, writes 24, timeouts 0, DMA errors 0
    Driver 4: position 0, standstill, SG min/max 0/456, read errors 0, write errors 1, ifcnt 102, reads 41324, writes 16, timeouts 0, DMA errors 0
    Driver 5: position 0, assumed not present
    Driver 6: position 0, assumed not present
    Driver 7: position 0, assumed not present
    Date/time: 2020-11-07 20:18:37
    Slowest loop: 350.99ms; fastest: 0.07ms
    === Storage ===
    Free file entries: 10
    SD card 0 not detected, interface speed: 11.2MBytes/sec
    SD card longest read time 0.0ms, write time 0.0ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 163, MaxWait: 1223625ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 63, completed moves 63, StepErrors 0, LaErrors 0, Underruns [0, 0, 27], 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, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.4
    Heater 1 is on, I-accum = 0.3
    === GCodes ===
    Segments left: 0
    Movement lock held by File
    HTTP* is doing "M122" in state(s) 0
    Telnet is idle in state(s) 0
    File is idle in state(s) 0 21, running macro
    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
    SBC is idle in state(s) 0
    Daemon is idle in state(s) 0
    Aux2 is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === SBC interface ===
    State: 0, failed transfers: 1
    Last transfer: 10ms ago
    RX/TX seq numbers: 2060/2062
    SPI underruns 0, overruns 0
    Number of disconnects: 0, IAP RAM available 0x0fdd0
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.2.0-beta3
    File:
    Finishing macro pause.g, started by system
    > Next stack level
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 31.77
    File /opt/dsf/sd/gcodes/K40_mechanical_endstop_mount_v2.gcode is selected, paused
    

    I am also unable to cancel the print as it thinks its printing so its asking me to pause first



  • @jay_s_uk i forgot to mention it but same here, can't cancel too




  • administrators

    @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.



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


  • administrators

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



  • @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
    


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



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


  • administrators

    @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.



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



  • @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
    


  • 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
    

  • administrators

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

    Please post your resume.g file.


Log in to reply