Skip to content

Unexpected extra extrusion after returning from park position (M600) #249

@Ranney1

Description

@Ranney1

Description

When using the latest firmware I run into a problem with the filament runout sensor. When triggered:

  1. Print is neatly interrupted
  2. Nozzle moves to park position
  3. Filament is discharged neatly.
  4. Screen beeps (according to M600 config) and goes to print pause screen (screen: 39_E_printresume)
  5. Screens 34 and 35 are not triggered.
  6. The moment the 'resume' button is pressed (screen 39_E_printresume) the filament is loaded.
  7. Printer returns to start position (and starts extruding during this move).
  8. At the 'resume position', extruding takes place for about 1.5 sec, after which the print is resumed.

Point 7 and certainly point 8 make the print fail.

The above is with the latest github version of Screen and Marlin.

  1. Is reproducible with every print
  2. Reproducible with SD print AND Octoprint
  3. Reproducible with filament runout (which I mainly care about) and M600 command.
  4. Have tried everything with the Config_Adv M600 config, but can't get any better.

Steps to Reproduce

If this is a Bug Report, please describe the steps needed to reproduce the issue

See above.

Expected behavior:

  1. Filament runout triggers screens 34 and 35
  2. M600 and filament runout can be used without problem from point 7 and point 8 (* see above)

Actual behavior:

See above.

Logging:

[Enter M111 S247 in a serial monitor (Pronterface or Octoprint). Reproduce the issue, then copy the relevant logs here.
For Octoprint you can either user serial.log or copy/paste the output from the terminal. More information: https://marlinfw.org/docs/gcode/M111.html ]

i will try to get logging out of octoprint. Currently i see only the 'busy' info in the terminal.

Additional Information

  1. CR-6 SE
  2. BTT Mainboard
  3. Stock screen
  4. Neopixels installed
  5. Latest (current) github FW)
  6. Problem is also with my own config. See files enclosed

My own config and config adv file in zip file (but latest community FW have same behavour)
Video of problem in zip file
Gcode example file (please wait for 1 or 2 layers and trigger filament runout. Every file gave me the same issue. This is an example file.

Maybe that i do something stupid, but after trying for days looking for help now.. Thanks!

Github.zip

[Which exact firmware version did you flash? Provide a link to the download you have used.]
Current github release

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions