- Apr 04, 2014
-
-
whosawhatsis authored
-
- Feb 25, 2014
-
-
anfroholic authored
-
- Jan 21, 2014
-
-
Dan Lipsitt authored
Having actual section headers instead of just bold text makes those parts of the document individually linkable.
-
- Oct 30, 2013
-
-
Daniel Benamy authored
Not sure what happened to my last commit so this includes that one + reordering the steps.
-
- Oct 22, 2013
-
-
alexborro authored
-
- Oct 08, 2013
-
-
alexborro authored
-
- Sep 29, 2013
-
-
Alex Borro authored
Check the Readme for instruction how to enable and configure the feature
-
- Aug 30, 2013
-
-
Erik van der Zalm authored
-
- Jul 17, 2013
-
-
Robert F-C authored
Dual x-carriage designs offer some substantial improvements for dual extruder printing.
-
- Jul 14, 2013
-
-
Erik van der Zalm authored
Untested
-
Erik van der Zalm authored
M109 S180 waits only when heating. M109 R180 also waits when cooling.
-
- Jun 06, 2013
-
-
Scott Lahteine authored
Diffed and merged, preserving my updates
-
- Jun 02, 2013
-
-
Erik van der Zalm authored
-
Erik van der Zalm authored
-
- May 18, 2013
-
-
Gord Christmas authored
-
- Mar 01, 2013
-
-
Robert F-C authored
This change allows fan outputs to automatically turn on/off when the associated nozzle temperature of an extruder is above/below a threshold temperature. Multiple extruders can be assigned to the same pin in which case the fan will turn on when any selected extruder is above the threshold. It also makes the M42 command compatible with the M106/M107 command. The majority of the logic in this change will be evaluated by the compiler at build time (i.e, low code space requirements).
-
- Dec 10, 2012
-
-
daid303 authored
Move the Arduino related stuff out of the Marlin tree, as they are not directly related to Marlin functionality but addons for the Arduino IDE. Also split up the addons for pre 1.0.0 Arduino and post 1.0.0 Arduino.
-
- Nov 07, 2012
-
-
Robert F-C authored
-
- Oct 09, 2012
-
-
Mark Finn authored
-
- Sep 13, 2012
-
-
Mark Finn authored
-
- Aug 11, 2012
-
-
Ian Jackson authored
Previously the parameters set in M206 would only be used if a G82 command was sent with specific axis home values. This limits its usefulness. Really, we should have a way to adjust the XYZ homing of a machine in the eeprom. So as the first stage of this, make M206 affect every home command. The values set using M206 are now added to the configuration variables [XYZ]_HOME_POS. This is achieved by replacing all uses of [XYZ]_HOME_POS in the code by a new home_pos[] which includes the adjustment. We also have to adjust the uses of [XYZ]_{MIN,MAX}_POS similarly - see below. To allow axis_is_at_home to be written as a function taking an axis index rather than a macro taking an axis letter, we provide constant arrays in program memory containing the values of [XYZ]_{MIN,MAX,HOME}_POS from the compiled-in configuration. This is done with some helper macros to deal with the declaration (XYZ_CONSTS_FROM_CONFIG) and definition of the inline function which does the program memory access. We also introduce the overloaded function read_pgm_any, whose instances are produced with DEFINE_PGM_READ_ANY, which allows the access functions to automatically produce the correct type. The type- and pointer-massaging code in the access function boils down, when compiled, to a simple program memory access. A question arises: if the M206 offset is set, should this adjustment to the home position shift or change the possible range of movement permitted by the software endstops ? The documentation in Configuration.h describes these limits as: // Travel limits after homing Since this is a file containing physical limits, and actual suggested values for these configuration parameters appear to include a certain amount of slop, I've taken the view that these should be regarded as nominal physical distances from the limit switches, and that the permissible travel should be unaffected by M206. So for example with the (rather unrealistic) #define X_HOME_DIR -1 #define X_MIN_POS -20 #define X_HOME_POS 0 #define X_MAX_POS 100 no matter the setting of M206 X, the machine would be permitted to move from 20mm "beyond" the limit switch trigger point in the negative X direction and 100mm away from the limit switch in the positive X direction, for a total travel of 120mm. With M206 X-10 that would be considered to correspond to X coordinates -30 to +90. With M206 X+10 that would be considered to correspond to X coordinates -10 to +110. fixes #200 (in ErikZalm/Marlin). Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
-
- Jul 14, 2012
-
-
Erik van der Zalm authored
-
- Jun 02, 2012
- May 04, 2012
-
-
Bernhard Kubicek authored
-
- Apr 15, 2012
-
-
Erik van der Zalm authored
-
- Mar 18, 2012
-
-
ErikZalm authored
-
- Feb 26, 2012
-
-
Erik van der Zalm authored
-
Erik van der Zalm authored
Included AD595 calibration options. (daid)
-
- Feb 20, 2012
-
-
Christian Thalhammer authored
-
- Feb 17, 2012
-
-
Christian Thalhammer authored
-
- Feb 08, 2012
-
-
Erik van der Zalm authored
-
- Nov 21, 2011
-
-
ErikZalm authored
-
- Nov 20, 2011
-
-
Bernhard Kubicek authored
-
Erik van der Zalm authored
-
Bernhard Kubicek authored
-
Bernhard Kubicek authored
-
Bernhard Kubicek authored
-
Bernhard Kubicek authored
-
Bernhard Kubicek authored
-