Skip to content

Bugfix 1.1.x#1

Merged
silentninja1 merged 386 commits intosilentninja1:bugfix-1.1.xfrom
MarlinFirmware:bugfix-1.1.x
Jul 21, 2018
Merged

Bugfix 1.1.x#1
silentninja1 merged 386 commits intosilentninja1:bugfix-1.1.xfrom
MarlinFirmware:bugfix-1.1.x

Conversation

@silentninja1
Copy link
Owner

Requirements

  • Filling out this template is required. Pull Requests without a clear description may be closed at the maintainers' discretion.

Description

Benefits

Related Issues

thinkyhead and others added 30 commits May 8, 2018 11:09
Co-Authored-By: Giuliano <gmagician@users.noreply.github.com>
Co-Authored-By: Simon Swenson <simon-swenson-8351@users.noreply.github.com>
* Allow both AD595 and AD8495 in concert
* General temperature code tweaks
Co-Authored-By: ejtagle <ejtagle@hotmail.com>
Use macros that explicitly avoid double-evaluation and can be used for any datatype, replacing `min`, `max`, `abs`, `fabs`, `labs`, and `FABS`.

Co-Authored-By: ejtagle <ejtagle@hotmail.com>
For parity with #10728

Co-Authored-By: ejtagle <ejtagle@hotmail.com>
thinkyhead and others added 29 commits July 11, 2018 20:31
For some probes like micro switches the full Z clearance raise between
probing attempts is not required while bigger Z clearance between probe
points is still needed to avoid clamps. The shorter Z raise within
multiprobing same point significantly increase probing speed and the whole
auto level process.
[1.1.x] Unify "I" parameter for M906,M912 etc.
[1.1.x] Shorter Z raise between multiple probes
This will fix kill message on dual printer with 0 alignment offset
The maximum movement is 180mm for Velleman K8400.
An offset of `Y_MIN_POS` violates an assertion in `SanityCheck.h`.

Code tested on Vellemann K8400 with Dual Extruder.
…16 or more LED's

Change Max7219_idle_task() routines to use single line if X-Axis has 16 or more LED's

This gets bugfix_1.1.x at parity with #11285 when it gets merged.
Prevent crash, on filament change, when printer is not homed
It takes 20 seconds to display the mesh values at startup...   If we are going to display this information at startup, we should find a more terse way to do it.   Perhaps displaying an entire row of the mesh at a time makes sense?
Based on #11295

Co-Authored-By: Giuliano <gmagician@users.noreply.github.com>
Co-Authored-By: J.C. Nelson <xc0000005@users.noreply.github.com>
[1.1.x] Better Malyan LCD Feedrate/Temp handling
[1.1.x] Add support for power loss detect pin
@silentninja1 silentninja1 merged commit a1d22e4 into silentninja1:bugfix-1.1.x Jul 21, 2018
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

Successfully merging this pull request may close these issues.