SOLVED 3.2 SBC cancel print not working w/ missing/blank cancel.g



  • M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
    Board ID: 08DJM-956L2-G43S8-6JTDG-3SJ6P-KB0UG
    Used output buffers: 1 of 40 (10 max)
    === RTOS ===
    Static ram: 149788
    Dynamic ram: 63788 of which 64 recycled
    Never used RAM 145192, free system stack 124 words
    Tasks: Linux(ready,71) HEAT(blocked,296) CanReceiv(blocked,927) CanSender(blocked,346) CanClock(blocked,352) TMC(blocked,19) MAIN(running,717) IDLE(ready,19)
    Owned mutexes: HTTP(MAIN)
    === Platform ===
    Last reset 02:30:34 ago, cause: software
    Last software reset at 2021-01-13 09:03, reason: User, none spinning, available RAM 145192, slot 1
    Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    Aux1 errors 0,0,0
    MCU temperature: min 34.4, current 35.1, max 42.7
    Supply voltage: min 24.3, current 24.7, max 25.3, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
    Driver 0: position 0, standstill, reads 17103, writes 43 timeouts 0, SG min/max 0/0
    Driver 1: position 0, standstill, reads 17103, writes 43 timeouts 0, SG min/max 0/0
    Driver 2: position 85642, standstill, reads 17091, writes 55 timeouts 0, SG min/max 0/0
    Driver 3: position 0, standstill, reads 17091, writes 55 timeouts 0, SG min/max 0/0
    Driver 4: position 0, standstill, reads 17092, writes 55 timeouts 0, SG min/max 0/0
    Driver 5: position 0, standstill, reads 17103, writes 44 timeouts 0, SG min/max 0/1023
    Date/time: 2021-01-13 11:34:33
    Slowest loop: 180.92ms; fastest: 0.04ms
    === Storage ===
    Free file entries: 10
    SD card 0 not detected, interface speed: 37.5MBytes/sec
    SD card longest read time 0.0ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 125, maxWait 1171149ms, bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 19083, completed moves 19083, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 11], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP* is doing "M122" 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
    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.
    === CAN ===
    Messages queued 36177, send timeouts 81349, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
    === SBC interface ===
    State: 4, failed transfers: 0
    Last transfer: 2ms ago
    RX/TX seq numbers: 44017/44017
    SPI underruns 0, overruns 0
    Number of disconnects: 2, IAP RAM available 0x2c8a8
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.2.0
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 38.93
    Maximum length of RX/TX data transfers: 2672/1504
    


  • @Heartleander81 said in Problem after cancel print:

    I doun't have a Cancel.g to time.

    What does that mean?

    Is the code you posted in cancel.g?

    In the code posted you are setting the temps to zero. When you try to print again do you restore the correct settings?

    Frederick



  • The last config is my end GCode afte the print.



  • In the code posted you are setting the temps to zero. When you try to print again do you restore the correct settings?

    Frederick

    I doun't know. I start the gcode. The bed heats up, the nozzle heats up, then make the printer his homing. Then extrude any filament. After this doun't come filament out the nozzel.



  • 20210113_145053.jpg

    There is a picture oft the DWC .
    Print is at layer 71 and filament only used 0.4mm, but must ~100mm used at this layer hight.

    I hope you understand what i mean. My english is not the best 😊



  • Hi,

    This is a long shot but create an empty cancel.g file and see if that makes a difference.

    Frederick



  • @fcwilt Will test it after work. But just think that I have an error somewhere in a file. After successfully printing the file, the problem was that the next print did not work either. It only worked again after restarting the Pi. That's only since I updated from 3.1.1 to 3.2.0


  • Moderator

    @Heartleander81 said in Problem after cancel print:

    If I have to cancel a print and start this or another, the extruder no longer feeds filament.
    Only when I reboot the Raspberry Pi 4 does the pressure go back to normal.

    Can you try describing again what exactly this means? I'm having a hard time understanding the problem.

    Does the printer try to resume the print but the extruder motor doesn't turn?

    Does it just sit there?

    Is the heater at temp at that point?



  • @Phaedrux
    I start a print.
    For example, a component comes loose.
    Then press pause and release the pressure.
    Change something on the slice or try to reprint.
    Then nothing is extruded during printing.
    When I restart the Pi, it prints normally.
    But today I was able to determine that this problem also occurred even after a successful print. That's only since the update from 3.1.1 to 3.2.0

    After Bed and Nozzle is on temp make my Printer Homing.


  • Moderator

    @Heartleander81 said in Problem after cancel print:

    and release the pressure.

    What does that mean?



  • Sorry. Fu.. Translator. I doun't have check before copy and past.PRESS pause and then cancel i the print

    I have a Video on youtube

    https://youtu.be/FWr_m28CsAc


  • Moderator

    Did you try creating the missing cancel.g?



  • This post is deleted!


  • Is the same with empty cancel.g


  • Moderator

    Do you have a T0 command in your slicer start gcode?
    Is your tool still selected after canceling?
    Can you try putting some commands in your cancel.g?

    Example:

    ; cancel.g
    ;
    ; Run when the print is paused, and then canceled.
    ;
    
    G10 P0 R0 S0		; Set hotend temp to 0
    M140 S0			; Set bed temp to 0
    M106 S255 		; Fan at 100 to cool nozzle and bed
    M220 S100		; Set speed factor back to 100% in case it was changed
    M221 S100		; Set extrusion factor back to 100% in case it was changed
    M290 R0 S0              ; clear babystepping
    G28 XY			; home XY
    M84			; turn off steppers
    G4 S60			; wait 1 minute for nozzle to cool
    M107			; turn off the fan
    


  • Now is working with this config.

    Can you tell me why?



  • @Heartleander81 said in Problem after cancel print:

    Now is working with this config.

    Can you tell me why?

    What config? Did you mean to post one?

    Frederick



  • @fcwilt i mean the config post from phaedrux


  • Moderator

    You mean you added those commands to cancel.g?

    I'm thinking there is an issue with missing or blank cancel.g files and the firmware isn't doing the expected default behaviour.

    Thanks for confirming that adding a cancel.g with commands allows it to work. I'll flag this for further investigation.



  • @Phaedrux I doun't now why, but on second test, the same bevore. I test at saturday more cycles. I think the problem is at my side.
    I give you Feedback at saturday night ore sunday morning.



  • @Phaedrux
    Thanks for your help. But i doun't find out what is. I have downgraded to 3.1.1

    When the next 3.2.x stabel comes out i test it.



  • I found the mistake. It was the slicer. I accidentally swapped relative and absolute extrusion. As a result, the skirt was still printed and nothing came out of the nozzle during the actual printing


  • Moderator

    Thanks for the update.


Log in to reply