- Dec 16, 2013
-
-
daid authored
-
daid authored
-
daid authored
-
Erik van der Zalm authored
- Dec 11, 2013
-
-
ErikZalm authored
Z and Y dual stepper drivers error
-
RicardoGA authored
if you try to enable Z_DUAL_STEPPER_DRIVERS the error "You cannot have dual drivers for both Y and Z" shows even if you don't have defined Y_DUAL_STEPPER_DRIVERS and don't let you compile the firmware to solve this problem i change this line: #ifdef Z_DUAL_STEPPER_DRIVERS && Y_DUAL_STEPPER_DRIVERS to: #if defined (Z_DUAL_STEPPER_DRIVERS) && defined (Y_DUAL_STEPPER_DRIVERS) now the error only show if you define both Z_DUAL_STEPPER_DRIVERS and Y_DUAL_STEPPER_DRIVERS
-
- Dec 07, 2013
-
-
ErikZalm authored
Added support for Cheaptronic v1 electronic
-
Michal Dyntar authored
-
- Nov 28, 2013
-
-
Alex Borro authored
In some cases the Bed Heater FET heats up more then stepper drivers, so this change add the bed monitoring to the controller fan. As soon as the bed heater is turned on, the controller fan will run as well.
-
Alex Borro authored
Recommended for those who are using the Z Probe for Z Homing (as Z-Endstop) This feature has two changes: 1) Allow user to choose where the Z Probe will touch the bed when homing all axis together (G28) by setting below defines: Z_SAFE_HOMING_X_POINT Z_SAFE_HOMING_Y_POINT 2) Prevents the user to perform Z Axis Homing when the Z Probe is outsite bed.
-
- Nov 27, 2013
-
-
Alex Borro authored
In previous version, even with PWM = 127, the system turns the FET off and then on in the next cycle. This bevavior may increase the FET heat dissipation. It was fixed keeping the FET always On when PWM=127.
-
- Nov 17, 2013
-
-
Erik van der Zalm authored
-
Erik van der Zalm authored
This allows a hot end with two heaters and a FET for each heater. This is useful if the FET is not capable of heating two heaters.
-
- Nov 10, 2013
-
-
Erik van der Zalm authored
-
ErikZalm authored
Implement M226 - GCode Initiated Pause
-
ErikZalm authored
M80 - ATX Power On related modification
-
ErikZalm authored
Added support for BT on AT90USB devices, corrected LCD bug, added new board and LCD
-
ErikZalm authored
Fix servo control for Melzi v2.0
-
ErikZalm authored
Add UUID support to M115 responses.
-
ErikZalm authored
Add (correct) missing pin definitions for Y2
-
- Nov 09, 2013
-
-
Richard Miles authored
Implemented M226 as described here: http://reprap.org/wiki/G-code#M226:_Gcode_Initiated_Pause Waits for pin to be become either HIGH, LOW or the inverse of what it was before. Allows printing to pause until user interaction
-
- Nov 04, 2013
-
-
Charles R authored
start another print with suicide feature after a print without suicide...
-
- Nov 03, 2013
-
-
fmalpartida authored
Added AT90USB device BT connectivity support using second UART.
-
- Nov 01, 2013
-
-
Kaz Walker authored
-
- Oct 31, 2013
-
-
Daniel Benamy authored
I tested this and it works.
-
- Oct 30, 2013
-
-
fmalpartida authored
If only an LCD is defined and no menu or keyboard defined, there is a compilation error. Added conditional compilation.
-
Justus Perlwitz authored
-
ErikZalm authored
Made instructions more clear.
-
Daniel Benamy authored
Not sure what happened to my last commit so this includes that one + reordering the steps.
-
fmalpartida authored
Included support for BT dongle on AT90USB boards. Added LCD Shift Register LCD control Included support for RepRap Clone Wars project board (SAV MKI).
-
- Oct 29, 2013
- Oct 25, 2013
-
-
Bernhard Kubicek authored
Make G11 not horribly broken
-
whosawhatsis authored
-
- Oct 22, 2013
-
-
alexborro authored
-
bkubicek authored
since it can occure in comments.
-
-
bkubicek authored
If a print is stopped, it would be nice in the future to write a file with the printer state, the filename of the print, and the position within the print. this file could be read, to continue a previously stopped print. not finished yet.
-
bkubicek authored
by overloading M32 it is now possible to execute gcode files from other gcode files, with a fixed recursion level. This can be used e.g. for having a real start.g and end.g somewhere on the sd card, which are then called from the normal print file. Another usecase would be to have macro-files for nozzle-change and layerchange. I have not tested the speedwise performance. The testing was done with pronterface. syntax: normal call from sd card will open the new file and continue executing there. M32 !/path/filename# this however will call the new file and return to the caller file. M32 P !/path/filename# with the optional "S<position>" the file starting position can be set. this is for continuing prints from a previous location.
-