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

Extruder feed rate is unusable slow through LCD touch screen #4

Closed
NickDevoctomy opened this issue Sep 26, 2020 · 10 comments
Closed

Extruder feed rate is unusable slow through LCD touch screen #4

NickDevoctomy opened this issue Sep 26, 2020 · 10 comments

Comments

@NickDevoctomy
Copy link

Description

Extruder feeding through LCD touch screen is extremely slow

Steps to Reproduce

Attempt to feed 60mm using menu, it takes a whole minute

  1. Navigate to feed menu on touch screen
  2. Enter 60mm
  3. Press feed

Personally I would expect it to feed at a reasonable rate, preferable the same speed as Octoprint, which operates at 300 mm/m

It operates at 60 mm/m making the feature unusable for loading / unloading filament

Additional Information

I also noticed that in the source code there are some poorly named enums,

PROC_COM

HeaterMoveEnterKey = 17,
HeaterMoveStartKey = 18,

These have nothing to do with the heater, but rather the Axis, so should ideally be

AxisMoveEnterKey = 17,
AxisMoveStartKey = 18,

Line 63 in touch_lcd.cpp appears to hold the feed rates for the axis movement feature. And the last value for the extruder is set to 60, my recommendation would be (5*60) to match Octoprint.

Obviously I understand that this could be entirely subjective so my apologies if you don't care about this. I just thought I'd mention it whilst I'm poking about in the source.

@Sebazzz Sebazzz reopened this Sep 26, 2020
@Sebazzz
Copy link
Collaborator

Sebazzz commented Sep 26, 2020

Is this something you experience in stock firmware as well?

@NickDevoctomy
Copy link
Author

Yes, it was like that on the printer, out-of-the box if that's what you mean, along with many other issues / bugs.

@Sebazzz
Copy link
Collaborator

Sebazzz commented Sep 26, 2020

Alright. I can't promise I can do anything anytime soon though, I have still yet to receive my unit and play with the touch screen how this particular part works/behaves 😄

@NickDevoctomy
Copy link
Author

Sure thing, no worries, as I mentioned above this could be seen as quite subjective as I'm not sure how many other people rely on the same features that I do. I've put it into my own fork of your repo so am giving it a good test. Understood if you don't want to put it in.

Hopefully you receive it soon! Mine was sent on 1st of August and I got it last week (UK). The tracking info was sitting in Germany for most of that.

@64Spaces
Copy link

64Spaces commented Oct 6, 2020

Yes, the filament feed rate, in or out, is painfully slow. Since the extruder is not visible, I have to feel the filament to be sure it’s moving.

@Sebazzz
Copy link
Collaborator

Sebazzz commented Oct 25, 2020

I also noticed that in the source code there are some poorly named enums,

PROC_COM

HeaterMoveEnterKey = 17,
HeaterMoveStartKey = 18,

Heh... yeah this is the legacy Creality left us. This is because the virtual pointers are used across the screens. What might be an "enter" key on one screen is a button to abort the print on another. The real distinction between the codes is based on the button value. This also makes the code very hard to refactor.

Check this for more information: https://github.com/CR6Community/CR-6-touchscreen#how-buttons-are-handled-with-code

@Sebazzz Sebazzz added this to the Community Release 4 alpha milestone Oct 29, 2020
@Sebazzz
Copy link
Collaborator

Sebazzz commented Nov 1, 2020

@nickacker I think you said this is the feed rate, didn't you?

@Sebazzz
Copy link
Collaborator

Sebazzz commented Nov 5, 2020

Extui uses 6mm/s resulting in 360mm/m.

@Sebazzz Sebazzz closed this as completed Nov 5, 2020
@64Spaces
Copy link

64Spaces commented Nov 5, 2020 via email

@Sebazzz
Copy link
Collaborator

Sebazzz commented Nov 5, 2020

Yes and no, you can change FILAMENT_CHANGE_FAST_LOAD_FEEDRATE and compile it yourself. Also, if you have a better suggestion for the feedrate, please do give it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants