search

Ultimaker / Ultimaker2Marlin

GNU General Public License v3.0
189 stars 231 forks source link

readme

Marlin 3D Printer Firmware

Flattr this git repo

Quick Information

This RepRap firmware is a mashup between Sprinter, grbl and many original parts.

Derived from Sprinter and Grbl by Erik van der Zalm. Sprinter's lead developers are Kliment and Caru. Grbls lead developer is Simen Svale Skogsrud. Sonney Jeon (Chamnit) improved some parts of grbl. A fork by bkubicek for the Ultimaker was merged, and further development was aided by him. Some features have been added by: Lampmaker, Bradley Feldman, and others...

Features:

The default baudrate is 250000. This baudrate has less jitter and hence errors than the usual 115200 baud, but is less supported by drivers and host-environments.

Differences and additions to the already good Sprinter firmware:

Look-ahead:

Marlin has look-ahead. While sprinter has to break and re-accelerate at each corner, lookahead will only decelerate and accelerate to a velocity, so that the change in vectorial velocity magnitude is less than the xy_jerk_velocity. This is only possible, if some future moves are already processed, hence the name. It leads to less over-deposition at corners, especially at flat angles.

Arc support:

Arc support: Old versions of Slic3r (before v2.0) can find curves that, although broken into segments, were meant to describe an arc. Marlin is able to print those arcs. The advantage is the firmware can choose the resolution, and can perform the arc with nearly constant velocity, resulting in a nice finish. Also, less serial communication is needed.

Temperature Oversampling:

To reduce noise and make the PID-differential term more useful, 16 ADC conversion results are averaged.

AutoTemp:

If your gcode contains a wide spread of extruder velocities, or you realtime change the building speed, the temperature should be changed accordingly. Usually, higher speed requires higher temperature. This can now be performed by the AutoTemp function By calling M109 S T F you enter the autotemp mode.

You can leave it by calling M109 without any F. If active, the maximal extruder stepper rate of all buffered moves will be calculated, and named "maxerate" [steps/sec]. The wanted temperature then will be set to t=tempmin+factor*maxerate, while being limited between tempmin and tempmax. If the target temperature is set manually or by gcode to a value less then tempmin, it will be kept without change. Ideally, your gcode can be completely free of temperature controls, apart from a M109 S T F in the start.gcode, and a M109 S0 in the end.gcode.

EEPROM:

If you know your PID values, the acceleration and max-velocities of your unique machine, you can set them, and finally store them in the EEPROM. After each reboot, it will magically load them from EEPROM, independent what your Configuration.h says.

LCD Menu:

If your hardware supports it, you can build yourself a LCD-CardReader+Click+encoder combination. It will enable you to realtime tune temperatures, accelerations, velocities, flow rates, select and print files from the SD card, preheat, disable the steppers, and do other fancy stuff. One working hardware is documented here: http://www.thingiverse.com/thing:12663 Also, with just a 20x4 or 16x2 display, useful data is shown.

SD card folders:

If you have an SD card reader attached to your controller, also folders work now. Listing the files in pronterface will show "/path/subpath/file.g". You can write to file in a subfolder by specifying a similar text using small letters in the path. Also, backup copies of various operating systems are hidden, as well as files not ending with ".g".

SD card folders:

If you place a file auto[0-9].g into the root of the sd card, it will be automatically executed if you boot the printer. The same file will be executed by selecting "Autostart" from the menu. First 0 will be performed, than 1 and so on. That way, you can heat up or even print automatically without user interaction.

Endstop trigger reporting:

If an endstop is hit while moving towards the endstop, the location at which the firmware thinks that the endstop was triggered is outputed on the serial port. This is useful, because the user gets a warning message. However, also tools like QTMarlin can use this for finding acceptable combinations of velocity+acceleration.

Coding paradigm:

Not relevant from a user side, but Marlin was split into thematic junks, and has tried to partially enforced private variables. This is intended to make it clearer, what interacts which what, and leads to a higher level of modularization. We think that this is a useful prestep for porting this firmware to e.g. an ARM platform in the future. A lot of RAM (with enabled LCD ~2200 bytes) was saved by storing char []="some message" in Program memory. In the serial communication, a #define based level of abstraction was enforced, so that it is clear that some transfer is information (usually beginning with "echo:"), an error "error:", or just normal protocol, necessary for backwards compatibility.

Interrupt based temperature measurements:

An interrupt is used to manage ADC conversions, and enforce checking for critical temperatures. This leads to less blocking in the heater management routine.

Implemented G Codes:

RepRap M Codes

Custom M Codes

Configuring and compilation:

Install the Classic Arduino software IDE/toolset v1.0.5 https://www.arduino.cc/en/Main/OldSoftwareReleases#1.0.x

Copy the Marlin firmware https://github.com/Ultimaker/Ultimaker2Marlin (Use the download button)

The firmware can be built from either the Arduino IDE or from the command line with a make file.

To build with the Arduino IDE: Start the arduino IDE. Select Tools -> Board -> Arduino Mega 2560 (or your microcontroller) Select the correct serial port in Tools ->Serial Port Open Marlin.pde

One time change: The UM2 made changes to the I2C driver. You will have to remove this driver function from the Arduino IDE by removing the entire TWI_vect interrupt routine (located in arduino/libraries/Wire/utility/twi.c, starting at line 364). Note: when you compile the sources using the makefile you can skip this step.

Click the Verify/Compile button

Click the Upload button If all goes well the firmware is uploading

That's it. Enjoy Silky Smooth Printing.