- Shifted coordinate system so X0 Y0 matches standard nozzle (T1502)
- Adjusted Y=0 coordinates mitigates hard crash due to Cura 2 bug (T1498)
- Added workaround for Marlin not raising nozzle prior to G29 (T1503)
- "Change filament" now allows extruder selection on dual extruder heads (T1438)
- Fix for broken M600 resume_print; head motion during M600; backport from upstream (T1221)
- Homing to bottom is accomplished by reducing current on Z motor and using stallguard
to detect when the Z axis bottoms out.
- This is a lot faster than homing to Z_MAX (yah!)
G28 was disabling bed leveling on entry, but not re-enabling it
on exit. This bug in upstream was probably not caught as G28
is most often followed by G29.
However, Cura now rehomes X/Y after pausing a print, so it is
necessary that G28 keep bed leveling information.
- Added workaround for allowing sensorless homing without
stealthchop
- Tuned sensitivity of sensorless homing to reduce chatter.
- G28 now backs away from endstops to help reduce chatter on subsequent homing.
- Now supports EinsyRambo 0.3
- M119 now shows average stallguard values for previous planner motion.
- M914 now disables stealthchop to allow SGT to be hand-tuned.
- Now using SERIAL_ECHO rather than SERIAL_PROTOCOL.
- M914 now allows negative values without overflow.
Made changed requested by Logan fori testing jigs in production.
- Fixed "auto0.g" autostart which was not working.
- Made it so M226 works on protected pins:
- There are no longer protected pins
- However, will only work on pins that are already inputs (like endstops)
* Add Max7219 LED Matrix Debug Support
The Max7219 8x8 LED Matrix's are very helpful for debugging new code.
And for that matter, just trying to maximize printer settings without
causing stuttering.
The displays are very inexpensive (under $2.00 with shipping) and
provide a lot of help when trying to debug complicated code.
* Try to keep Makefile up to date.
When M405 is used it changes 'volumetric_multiplier[FILAMENT_SENSOR_EXTRUDER_NUM]' value. When M406 disables M405 it leaves the value unchanged.
This PR applies 'calculate_volumetric_multipliers' in M406 instead of resetting it to 1.0 because M200 may not be compatible with M405 hence I'm sure to restore anyway with correct value.
Marcio Teixeira