Marlin 2,0 bugfix when linear advance 1.5 is compiled printng is very slow
Attached are the configurations
Configuration_adv.zip
Marlin 2,0 bugfix using TMC2209
Expected behavior: [Printer operates with new marlin 2.0 bugfix linear advance 1.5]
Actual behavior: [Printer does not operate correctly very slow print speed steppes heat up too hot to touch]
It's not clear to me, what "very slow" means in this context. Can you quantify this? Also, looking at your configs, there's a couple of potential problems:
If these config changes do not fix it, please let us know at which release it was still running fine for you (with the exact same config).
Sorry to jump in, but why is scurve acceleration incompatible with LA? I've been using these both settings for a long time now, just asking thou.
LA don't account for SCurve correction, so result is quite unpredictable.
LA don't account for SCurve correction, so result is quite unpredictable.
maybe needs sanitycheck ?
maybe needs sanitycheck ?
It has.
i have/had both enabled, never saw a warning - or do i misunderstand sanity check?
Check is not in stable version yet, only bugfix-2.0.x
ok, but i do bugfix-2.0.x update once a week. no sanity check warnings in VSCode.
ok, but i do bugfix-2.0.x update once a week. no sanity check warnings in VSCode.
This is what you should see if you try to compile it with both LA & S-C enabled and EXPERIMENTAL_SCURVE is disabled:
#error "LIN_ADVANCE and S_CURVE_ACCELERATION may not play well together! Enable EXPERIMENTAL_SCURVE to continue."
@qwewer0 yes, disabling EXPERIMENTAL_SCURVE shows the warning. thanks for enlightening me.
XDA-Bam thank you deactivated S-Curve Acceleration changed default extruder jerk to 15
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
It's not clear to me, what "very slow" means in this context. Can you quantify this? Also, looking at your configs, there's a couple of potential problems:
If these config changes do not fix it, please let us know at which release it was still running fine for you (with the exact same config).