Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

M701-M702 support #1778

Open
charlespick opened this issue May 6, 2021 · 1 comment
Open

M701-M702 support #1778

charlespick opened this issue May 6, 2021 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@charlespick
Copy link

Is your feature request related to a problem? Please describe.
Currently OctoDash supports 2 ways of loading filament from the filament screen during a print. M600 and normal movement commands. I don't want to use M600 because I don't have a screen connected to Marlin and normal movement commands don't work because they affect the E value in marlin meaning that the second that you resume printing, your filament unloads if you're using absolute positioning gcode.

Describe the solution you'd like
A 3rd option, configurable in the settings menu to use M701 and M702.

Additional context
Note I am not suggesting what was suggested in #1549 but rather just the same functionality as the existing non-M600 filament change behavior but using different commands.

@charlespick charlespick added the enhancement New feature or request label May 6, 2021
@Wob76
Copy link

Wob76 commented Jun 28, 2021

I would like to see this also.

I am running Octodash on the BIQU BX and as such I switch between Octodash and the printer LCD on the same screen, I tend to just stay on Octodash as if you switch when the printer is doing something it can have issues.

I was using the default Octodash inbuilt script for filament changes, but I find more often than not it will Jam on the unload (this doesn't happen during the M600 as it does a small purge\pause and then retract which seems to help shape the tip)

I tried switching to M600, this avoids the jamming, but has a few drawbacks, firstly it requires more X-Y motion as the M600 parks the print head during this process. Secondly it requires user prompts, this currently requires switching the LCD or using action prompts in octoprint, neither are ideal.

Implementing M701 and M702 would help over a M600 as it would reduce the unnecessary X-Y Motion and also allow the process to be completed with minimal action prompts, currently M701 still has a Purge More\Continue action prompt. You can also pass unload and load values to M701/M702 with L or U values, so they could also use the values from the settings if wanted, otherwise they will use the values stored in M603.

So I would suggest the interface can remain the same, but enabling this option would just replace the current E motion steps that are currently scripted with the M701 and M702 instead. I would further suggest that there be an option to enable each individually, in my example M702 (unload) offer advantages (it completes the tip forming steps) but M701 (load) has a drawback of requiring action prompts which octodash doesn't yet support.

@UnchartedBull UnchartedBull added this to the v3.1.0 milestone Jun 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants