Control of motor direction
Opened this issue · 5 comments
Description
Changing the motor direction from the user interface would be simplest, yet powerfull feature. To be precise: I've switched to dual drive extruder, so I have to change the E motor direction. It's no use.
Feature Workflow
Additional fetures on UI level would do the job...
- [First Action]
- [Second Action]
- [and so on...]
Additional Information
- Provide pictures or links that demonstrate a similar feature or concept.
It’s not really the “simplest“ feature.
Okay, there’s a common hack to set negative number of steps per unit which should work for the extruder when using units/mm (never tried it). Not for other axis though as it does not cover homing, min/max, etc.
Talking about the M92
command that is also used for extruder calibration M92 E-...
plus M500 for persistence.
It’s a thing you typically will use exactly once per printer (or once per EEPROM reset), so axis direction in Marlin is a build-time config for good reasons. I guess build your own firmware once or use M92 via console is an acceptable effort for such one-time action and an additional menu not worth the effort.
So far, it's no use (negative values are unacceptable)...
Is it really only the direction you need to change, no other parameter (federate, retracts, etc.)?
You can either enable #define KNUTWURST_BMG
which inverts the direction and sets some parameters for BMC (clone) extruders or modify only this section so specify INVERT_E0_DIR
Marlin-2-0-x-Anycubic-i3-MEGA-S/Marlin/Configuration.h
Lines 2029 to 2033 in c41a853
No idea about your hardware, but my point still holds: an inversion toggle is neither simple (if negative values don’t work here, it’s actually quite a huge task) nor useful for more than one or two people modifying their hardware. So you’re better off learning how to build the firmware (Wiki) and make the changes as required yourself, once in the code.
I'm not asking anymore for extra features, just have mentioned, that interesting hack does not work.
I'm skilled enought, to build/compile/recompile AVR software (skilled enough to reimplement AVR in Programable Logic Device, to be honest), but I don't like to modify someone's code without asking the author about possibilities that at specific point of time are unknown and worth of question - and that's what i did.
Thanks a lot, I know what to do.