Redeem settings

From iagent
Jump to: navigation, search

Initial Configuration

Calibrating Redeem for your 3D printer's hardware.

There are three levels of configuration files:

default.cfg || defines all of the parameters. this should not be modified. printer.cfg || references a standard set of configuration for specific types of printers local.cfg || any additional changes needed for your local setup

Any settings defined in local.cfg overrides the values in printer.cfg and default.cfg.

Any settings defined in printer.cfg take precedence over default.cfg.

Currently, Redeem ships with printer configuration files for:

  • Kossel K250000
  • Kossel Mini
  • Makerbot Cupcake
  • Max Core XY
  • Mendel Max
  • Prusa i3
  • Prusa i3 quad
  • Rostock Max v2
  • Thing
  • Thing Delta
  • Ultimaker Original

To select the printer configuration, go to the Configuration section of Octoprint and click on the Reedem section.

Octoprint redeem plugin.png

Of the printers listed, clicking the star activates it as the printer configuration. Upon first install, the local.cfg file is blank but from this same screen you can upload you're own file.


If you have a printer not listed, you can create your own printer.cfg and contribute it to the project.

Configuration Settings

  • All units are in SI-units internally in Redeem, but g-codes often expose mm etc.
  • default.cfg is the bible, all configs must be defined in there.
  • All configurations in default.cfg can be overridden
  • default.cfg and printer.cfg can be changed with updates. local.cfg can not.
  • Here is the config hierarchy: local.cfg > printer.cfg > default.cfg

For Redeem, the preferred way to handle configuration is through the web interface. The web interface is available through kamikaze.local assuming you have your BeagleBone on the local network and you are using Umikaze 2.1.1.

The config files for redeem are present in the folder /etc/redeem/. There are three files for setting the configuration. default.cfg is the catch-all at the bottom. It will contain all the possible options and should not be touched. Second is printer.cfg which is a symlink and specific to a printer. Look in the folder to find one that matches your printer. If you cannot find one, make it! *Otherwise leave the existing one as is.* Finally is local.cfg which contains quirks or other individual settings. The local.cfg will not be overwritten by new software updates and can contain stuff like microstepping, stepper current, offsets as well as any bed compensation matrices etc.

Now normally all settings can come from your specific printer.cfg config file, but if no one has made that file, you need to set this stuff up yourself. Most of the stuff in the config files is in SI units. This is perhaps different than what other firmwares do, where the focus is on optimization rather than ease of use. Note that it is important to keep the section headers in the same case as the examples or default.cfg as they are case sensitive.


If you edit a config file incorrectly, redeem will fail to load and you will be unable to connect in octoprint. You must use headers, as shown in the examples, and consistent spacing/formatting. Also the first time you load octoprint you will not have any config files listed in settings/redeem, you are supposed to load a blank local.cfg file. You shouldn't need to do this again unless you reflash the image. However, if you find that your config files suddenly when missing, simply close your browser tab and reopen octoprint and they should return.


If you are not writing your own new printer.cfg, keep all your printer settings in local.cfg to avoid getting any setting over-written by a redeem update.


The system section has only Replicape board revision and log level. For debugging purposes, set the log level to 10, but keep it at 20 for normal operations, since logging is very CPU intensive and can cause delays during prints at high speed. On later versions of Redeem, the board revision is read from the EEPROM on the Replicape.

 1 [System]
 3 # CRITICAL=50, # ERROR=40, # WARNING=30,  INFO=20,  DEBUG=10, NOTSET=0
 4 loglevel =  20
 6 # If set to True, also log to file.
 7 log_to_file = True
 9 # Default file to log to, this can be viewed from octoprint
10 logfile = /home/octo/.octoprint/logs/plugin_redeem.log
12 # Plugin to load for redeem, comma separated (i.e. HPX2Max,plugin2,plugin3)
13 plugins =
15 # Machine type is used by M115
16 # to identify the machine connected.
17 machine_type = Unknown


The geometry section contains stuff about the physical layout of your printer. What the print volume is, what the offset from the end stops is, whether it's a Normal XY style printer, a Delta printer, an H-belt type printer or a CoreXY type printer.

It also contains the bed compensation matrix. The bed compensation matrix is used for compensating any rotation the bed has in relation to the nozzle. This is typically not something you write yourself, but instead it is found by probing the bed at different locations by use of the G-code G29. The G29 command is a macro command, so it only runs other G-codes and you can override it yourself in the local.cfg file or in the printer.cfg file if you are a printer manufacturer.


Homing works differently on cartesian and delta printers. Please refer to :doc:`/support/howto/homing`.

 1     [Geometry]
 2     # 0 - Cartesian
 3     # 1 - H-belt
 4     # 2 - Core XY
 5     # 3 - Delta
 6     axis_config = 0
 8     # The total length each axis can travel
 9     #   This affects the homing endstop searching length.
10     #   travel_* can be left undefined.
11     #   It will be determined by soft_end_stop_min/max_*
12     # travel_x = 0.2
13     # ...
15     # Define the origin in relation to the endstops
16     #   offset_* can be left undefined.
17     #   It will be determined by home_speed and soft_end_stop_min/max_*
18     # offset_x = 0.0
19     # ...
21     # The identity matrix is the default
22     bed_compensation_matrix =
23             1.0, 0.0, 0.0,
24             0.0, 1.0, 0.0,
25             0.0, 0.0, 1.0


Several variables are needed for defining the geometry of the delta setup.


  • Effector is the thing that is in the centre and moves (the one with the hot end)
  • The distance from the centre of the effector to where the rods are mounted is the effector offset.
  • Carriage is those that move up and down along the columns.


I've not figured out what the carriage offset does. You should think this was the offset from the carriages to the rods, but I've not gotten that top work. Seems broken. Instead, add the carriage offset to the effector offset.

For more information on correcting delta calibration, see the :doc:`/support/printers/delta`.

 1     [Delta]
 3     # DEPRECATED IN 2.1.1
 4     # Distance head extends below the effector.
 5     Hez = 0.0
 7     # Length of the rod
 8     L   = 0.135
10     # Radius of the columns (distance from column to the center of the build plate)
11     r   = 0.144
13     # Effector offset (distance between the joints to the rods to the center of the effector)
14     Ae  = 0.026
15     Be  = 0.026
16     Ce  = 0.026
18     # Carriage offset (the distance from the column to the carriage's center of the rods' joints)
19     A_radial = 0.0
20     B_radial = 0.0
21     C_radial = 0.0
23     # DEPRECATED IN 2.1.1
24     # Compensation for positional error of the columns
25     # (For details, read:
26     # Positive values move the tower to the right, in the +X direction, tangent to it's radius
27     A_tangential = 0.0
28     B_tangential = 0.0
29     C_tangential = 0.0
31     # NEW IN 2.1.1
32     A_angular = 0.0
33     B_angular = 0.0
34     C_angular = 0.0

Here is a visual depiction of what the length and radius looks like:

L and R.png

Here is what the Hez looks like:



This section has the stuff you need for the the steppers:

  • the number of steps pr mm for each axis
  • the stepper max current
  • the microstepping
  • the option to invert a stepper (so you don't have to rotate the stepper connector),
  • the decay mode of the current chopping on the motor drives (see the :ref:`ConfigStepperDecay` for more information.

For acceleration and max speed, see Planner

1 # Stepper e is ext 1, h is ext 2
2 [Steppers]


1 microstepping_x = 3
2 ...
Value Gives
0 Full step
1 Half step
2 Half step, interpolated to 256
3 Quarter step
4 16th step
5 Quarter step, interpolated to 256 microsteps
6 16th step, interpolated to 256 microsteps
7 Quarter step, StealthChop, interpolated to 256 microsteps
8 16th step, StealthChop, interpolated to 256 microsteps
1 #Current
2 current_x = 0.5
3 ...


Never run the Replicape with the steppers running above 1.0A without cooling. Never exceed 1.2A of regular use either - the TMC2100 drivers aren't rated higher. If you need more current to drive two motors off the same stepper, use slave mode with a second driver (usually H). While it means splitting off your wiring of the stepper motors you had going to a single driver, but it also means you avoid overheating your drivers.

steps per mm

Defined how many stepper full steps needed to move 1mm. Do not factor in microstepping settings. For example: If the axis will travel 10mm in one revolution and angle per step in 1.8deg (200step/rev), steps_pr_mm is 20.

2 steps_pr_mm_x = 4.0
3 ...

Backlash (deprecated)

2 backlash_x = 0.0
3 ...

Enable / Disable

1 # Which steppers are enabled
2 in_use_x = True
3 ...


1 # Set to -1 if axis is inverted
2 direction_x =  1
3 ...


The decay mode affects the way the stepper motor controllers decays the current. Basically slow decay will give more of a hissing sound while standing still and fast decay will cause the steppers to be silent when stationary, but loud when stepping. The microstepping_ settings is :math:`2^x`, so microstepping_x = 2 means 2^2 = 4. 3 then is 2^3 = 8 or one-eighth.

On Replicape Rev B, there are 8 levels of decay. Please consult the data sheet for TMC2100

on the different options.

There are three settings that are controlled on the TMC2100 by the decay mode or rather “chopper configuration”: CFG0, CFG4 and CFG5 in the TMC2100 data sheet.

CFG0 DIS - 140 Tclk (recommended) EN - 236 Tclk (medium) Sets chopper off time (Duration of slow decay phase)
CFG4 DIS: (recommended): low hysteresis with ≈4% offull scale current. EN: high setting with ≈6% of full scale current at sense resistor. Sets chopper hysteresis (Tuning of zero crossing precision)
CFG5 DIS - 16 (best performance for StealthChop) EN - 24 (recommended, most universal choice) Sets chopper blank time ( Duration of blanking of switching spike )

Value CFG0 CFG4 CFG5
0 0 0 0
1 0 0 1
2 0 1 1
3 0 1 1
4 1 0 0
5 1 0 1
6 1 1 0
1 # Set to True if slow decay mode is needed
2 slow_decay_x = 0
3 ...


1     # A stepper controller can operate in slave mode,
2     # meaning that it will mirror the position of the
3     # specified stepper. Typically, H will mirror Y or Z,
4     # in the case of the former, write this: slave_y = H.
5     slave_x =
6     slave_y =
7     slave_z =
8     ...


If you want to enable slave mode for a stepper driver, meaning it will mirror the movements of another stepper motor exactly, you need to use slave_y = H if you want the H-stepper motor to mirror the moves produced by the Y-stepper motor. Remember to also set the steps_pr_mm to the same value on the the motors mirroring each other, and also the direction. Most likely you will want the current to be the same as well.

  1. Enable the slave stepper driver (in_use_h = True)
  2. The syntax for selecting which axis is the master and which the slave is:

I want to slave H to Z (H follows everything Z does) then you use slave_z = H.

  1. If you have any endstops acting on the master axis, then you should

do the same thing for the slave axis, otherwise it will just keep on turning. For example, on a delta with Z1 connected to a bed probe and Z2 connected to the tower limit switch: end_stop_Z1_stops = x_neg, y_neg, z_neg, h_neg and end_stop_Z2_stops = z_pos,h_pos.

1 # Stepper timout
2 use_timeout = True
3 timeout_seconds = 500


The acceleration profiles are trapezoidal, i.e. constant acceleration. One will probably see and hear a difference between Replicape/Redeem and the simpler 8 bit boards since all path segments are cut down to 0.1 mm on delta printers regardless of speed and there is also a better granularity on the stepper ticks, so you will never have quantized steps either. Further more, all calculations are done with floating point numbers, giving a better precision on calculations compared to 8 bit microcontrollers.

This section is concerned with how the path planner caches and paces the path segments before pushing them to the PRU for processing.

 1     [Planner]
 3     # size of the path planning cache
 4     move_cache_size = 1024
 6     # time to wait for buffer to fill, (ms)
 7     print_move_buffer_wait = 250
 9     # if total buffered time gets below (min_buffered_move_time) then wait for (print_move_buffer_wait) before moving again, (ms)
10     min_buffered_move_time = 100
12     # total buffered move time should not exceed this much (ms)
13     max_buffered_move_time = 1000
15     # DEPRECATED IN 2.1.1
16     # max segment length
17     max_length = 0.001


This sets the accelleration pr stepper in m/s². For XYZ, the slowest step rate of the axis in conjunction with the accelleration rate will govern the maximum accelleration in any direction.

1     acceleration_x = 0.5
2     ...


1     max_jerk_x = 0.01
2     ...

Max speed

This sets the maximum speed of each stepper. The maximum speed in any direction will limit the total speed for the move.

1     # Max speed for the steppers in m/s
2     max_speed_x = 0.2
3     ...

Minimum buffered move time

If total buffered time gets below (min_buffered_move_time) then wait for (print_move_buffer_wait) before moving again, (ms)

1     min_buffered_move_time = 100

E axis active

When true, movements on the E axis (eg, G1, G92) will apply to the active tool (similar to other firmwares). When false, such movements will only apply to the E axis.

1     e_axis_active = True

Cold ends

Replicape has three thermistor inputs and a Dallas one-wire input. Typically, the thermistor inputs are for high temperatures such as hot ends and heated beds, and the Dallas one-wire input is used for monitoring the cold end of a hot end, if you know what I mean... This section is used to connect a fan to one of the temperature probes, so for instance the fan on your extruder will start as soon as the temperature goes above 60 degrees. If you have a Dallas one-wire temperature probe connected on the board, it will show up as a file-like device in Linux under /sys/bus/w1/devices/. Find out the full path and place that in your local.cfg. All Dallas one-wire devices have a unique code, so yours will be different than what you see here.

 1     [Cold-ends]
 2     # To use the DS18B20 temp sensors, connect them like this.
 3     # Enable by setting to True
 4     connect-ds18b20-0-fan-0 = False
 5     connect-ds18b20-1-fan-0 = False
 6     connect-ds18b20-0-fan-1 = False
 8     # This list is for connecting thermistors to fans,
 9     # so they are controlled automatically when reaching 60 degrees.
10     connect-therm-E-fan-0 = False
11     ...
12     connect-therm-H-fan-1 = False
13     ...
14     # For your part cooling fan, you'll want to set this to True for the correct Fan-input so your slicer can control it.
15     # If your part-cooling fan is connected to the Fan0 input, use this:
16     add-fan-0-to-M106 = True
17     ...
19     # If you want coolers to
20     # have a different 'keep' temp, list it here.
21     cooler_0_target_temp = 60
23     # If you want the fan-thermistor connections to have a
24     # different temperature:
25     # therm-e-fan-0-target_temp = 70
27     # if you have a Titan Aero (or any other all-metal) hotend, you'll want the fan on the hotend to turn on 
28     # automatically above 50C. To make the fan connected to the Fan1 input turn on when the hotend reaches 60C 
29     # (provided that the hotend is connected to "thermistor extruder 1", also referred to as E).
30     connect-therm-E-fan-1 = True
31     therm-e-fan-1-target_temp = 50


The heater section controls the PID settings and which temperature lookup chart to use for the thermistor. If you do not find your thermistor in the chart, you can find the Steinhart-Hart coefficients from the NTC Calculator online tool.

Some of the most common thermistor coefficients have already been implemented though, so you might find it here:


An example configuration for `E`. The most important thing to change should be the sensor name matching the thermistor. The Kp, Ti and Td values will be set by the M303 auto-tune and the rest of the values are for advanced tuning or special cases.

 1     [Heaters]
 2     sensor_E = B57560G104F
 3     pid_Kp_E = 0.1
 4     pid_Ti_E = 100.0
 5     pid_Td_E = 0.3
 6     ok_range_E = 4.0
 7     max_rise_temp_E = 10.0
 8     max_fall_temp_E = 10.0
 9     min_temp_E = 20.0
10     max_temp_E = 250.0
11     path_adc_E = /sys/bus/iio/devices/iio:device0/in_voltage4_raw
12     mosfet_E = 5
13     onoff_E = False
14     prefix_E = T0
15     max_power_E = 1.0
17     ...


Name Comment
B57540G0104F000 EPCOS100K with b= 4066K
B57560G1104F EPCOS100K with b = 4092K
B57560G104F EPCOS100K with b = 4092K (Hexagon)
B57561G0103F000 EPCOS10K
NTCS0603E3104FXT Vishay100K
SEMITEC-104GT-2 Semitec (E3D V6)
DYZE DYZE hightemp thermistor
HT100K3950's 3950-100K thermistor (part number HT100K3950-1)

PT100 type thermistors

Name Comment
PT100-GENERIC-PLATINUM Ultimaker heated bed etc.

Linear v/deg Scale Thermocouple Boards 20:17, 19 October 2018 (CEST)20:17, 19 October 2018 (CEST)20:17, 19 October 2018 (CEST)20:17, 19 October 2018 (CEST)20:17, 19 October 2018 (CEST)20:17, 19 October 2018 (CEST)20:17, 19 October 2018 (CEST)Elias (talk)

Name Comment
0.005 Volts pr degree

PID autotune

With version 1.2.6 and beyond, the PID autotune algorithm is fairly stable. To run an auto-tune, use the M-code M303. You should see the hot-end or heated bed temperature oscillate for a few cycles before completing. To set temperature, number of oscillations, which hot end to calibrate etc, try running “M303?” or see the description of the :ref:`M303`.


Use this section to specify whether or not you have end stops on the different axes and how the end stop inputs on the board interacts with the steppers. The lookup mask is useful for the latter. In the default setup, the connector marked X1 is connected to the stepper on the X-axis. For CoreXY and H-bot this is different in that two steppers are denied movement in one direction, but allowed movement in the other direction given that one of the end stops has been hit.

Also of interest is the use of two different inputs for a single axis and direction. Imagine using one input to control the lower end of the Z-axis and a different input to probe the bed with G20/G30.

If you are not seeing any movement even though no end stop has been hit, try inverting the end stop.

See also this blog post and video for a more thorough explanation.

Soft end stops can be used to prevent the print head from moving beyond a specified point. For delta printers this is useful since they cannot have end stops preventing movement outside the build area.

 1     [Endstops]
 2     # Which axis should be homed.
 3     has_x = True
 4     ...
 5     # Number of cycles to wait between checking
 6     # end stops. CPU frequency is 200 MHz
 7     end_stop_delay_cycles = 1000
 9     # Invert =
10     #   True means endstop is connected as Normally Open (NO) or not connected
11     #   False means endstop is connected as Normally Closed (NC)
12     invert_X1 = False
13     ...
14     # If one endstop is hit, which steppers and directions are masked.
15     #   The list is comma separated and has format
16     #     x_cw = stepper x clockwise (independent of direction_x)
17     #     x_ccw = stepper x counter clockwise (independent of direction_x)
18     #     x_neg = stepper x negative direction (affected by direction_x)
19     #     x_pos = stepper x positive direction (affected by direction_x)
20     #   Steppers e and h (and a, b, c for reach) can also be masked.
21     #
22     #   For a list of steppers to stop, use this format: x_cw, y_ccw
23     #   For Simple XYZ bot, the usual practice would be
24     #     end_stop_X1_stops = x_neg, end_stop_X2_stops = x_pos, ...
25     #   For CoreXY and similar, two steppers should be stopped if an end stop is hit.
26     #     similarly for a delta probe should stop x, y and z.
27     end_stop_X1_stops =
28     ...
29     soft_end_stop_min_x = -0.5
30     ...
31     soft_end_stop_max_x = 0.5
32     ...


Currently Redeem does not yet support tool offsets for dual or multi-extrusion. These offsets must be configured in the slicer, instead of in the firmware, for now.


Servos are controlled by two on-chip PWMs and share connector with Endstop X2 and Y2.

- Servo 0 is on pin P9\_14 - Servo 1 is on pin P9\_16

Use :ref:`m280` to set the servo position. Note that multiple servos can be present, the init script will continue to initialize servos as long as there are higher indexes, so keep the indexes increasing for multiple servos.

 1     [Servos]
 2     # For Rev B, servo is either P9_14 or P9_16.
 3     # Not enabled for now, just kept here for reference.
 4     # Angle init is the angle the servo is set to when redeem starts.
 5     # pulse min and max is the pulse with for min and max position, as always in SI unit Seconds.
 6     # So 0.001 is 1 ms.
 7     # Angle min and max is what angles those pulses correspond to.
 8     servo_0_enable = False
 9     servo_0_channel = P9_14
10     servo_0_angle_init = 90
11     servo_0_angle_min = -90
12     servo_0_angle_max = 90
13     servo_0_pulse_min = 0.001
14     servo_0_pulse_max = 0.002


Before attempting the configuration of a Z probe make sure your printer is moving in the right direction and that your hard endstops and your soft endstops are configured correctly please refer to the endstop section.

| The standard configs for Z-probe should work for most. The real

 difficulty lies in making the macro for the whole probing procedure.
 The offsets are the distance from the probe point to the nozzle. Here
 are the standard values:
1     [Probe]
2     length = 0.01
3     speed = 0.05
4     accel = 0.1
5     offset_x = 0.0
6     offset_y = 0.0

For more information, check out the :doc:`/support/howto/zprobes` page.

Rotary Encoders


work in progress.

1     [Rotary-encoders]
2     enable-e = False
3     event-e = /dev/input/event1
4     cpr-e = -360
5     diameter-e = 0.003

Filament Sensors


work in progress. See the blog post `Filament Sensor <>`_.

1     [Filament-sensors]
2     # If the error is > 1 cm, sound the alarm
3     alarm-level-e = 0.01


The watchdog is a time-out alarm that will kick in if the /dev/watchdog file is not written at least once pr. minute. This is a safety issue that will cause the BeagleBone to issue a hard reset if the Redeem daemon were to enter a faulty state and not be able to regulate the heater elements. For the watchdog to start, it requires the watchdog to be resettable, with the proper kernel command line ``omap\_wdt.nowayout=0``.

This should be left on at all time as a safety precauchion, but can be disabled for development purposes. This is not the same as the stepper watchdog which only disables the steppers.

1     [Watchdog]
2     enable_watchdog = True


The macro-section contains macros. Duh. Right now, only G29, G31 and G32 has macro definitions and it's basically a set of other G-codes. To make a new macro, you need to also define the actual g-code file for it. That is beyond this wiki, but look at G29 in the repository.


Each line in macros section needs to be spaced the same or you may not be able to connect in octoprint. Most Inductive sensors don't need probe type defined to work. To simply turn an inductive sensor on and off change the example macro with the g31/g32 macro's i have listed here. The g32 may need adjusting to match your z1 endstop settings. Undock turns probe on, Dock turns it off. Check your Macro and setup carefully, in the g29 example, at the end of each probe point it docks your probe then homes z before the start of the next point, which in some printers can crash your probe into the bed possibly causing damage.

If you find that your probe routine is probing the air, your z axis is most likely moving in the wrong direction for the probing to work. It seems redeem only probes in one direction and this can't be changed in the probing settings. So, You will need to swap your z direction, in the [steppers] section using direction\_z = -1 or direction\_z = +1, then confirm your z stops/homing, ect work make corrections as required. You will also most likely need to change under [Geometry] travel\_z direction. This should trick the probe into moving in the correct direction.

    • G31**
   M574 Z2  ; Probe up (Dock sled)
    • G32**
   M574 Z2 z_ccw, h_ccw  ; Probe down (Undock sled)
 1     [Macros]
 2     G29 =
 3         M561                ; Reset the bed level matrix
 4         M558 P0             ; Set probe type to Servo with switch
 5         M557 P0 X10 Y20     ; Set probe point 0
 6         M557 P1 X10 Y180    ; Set probe point 1
 7         M557 P2 X180 Y100   ; Set probe point 2
 8         G28 X0 Y0           ; Home X Y
10         G28 Z0              ; Home Z
11         G0 Z12              ; Move Z up to allow space for probe
12         G32                 ; Undock probe
13         G92 Z0              ; Reset Z height to 0
14         G30 P0 S            ; Probe point 0
15         G0 Z0               ; Move the Z up
16         G31                 ; Dock probe
18         G28 Z0              ; Home Z
19         G0 Z12              ; Move Z up to allow space for probe
20         G32                 ; Undock probe
21         G92 Z0              ; Reset Z height to 0
22         G30 P1 S            ; Probe point 1
23         G0 Z0               ; Move the Z up
24         G31                 ; Dock probe
26         G28 Z0              ; Home Z
27         G0 Z12              ; Move Z up to allow space for probe
28         G32                 ; Undock probe
29         G92 Z0              ; Reset Z height to 0
30         G30 P2 S            ; Probe point 2
31         G0 Z0               ; Move the Z up
32         G31                 ; Dock probe
34         G28 X0 Y0           ; Home X Y
36         M561 U; (RFS) Update the matrix based on probe data
37         M561 S; Show the current matrix
38         M500; (RFS) Save data
41     G31 =
42         M280 P0 S320 F3000  ; Probe up (Dock sled)
44     G32 =
45         M280 P0 S-60 F3000  ; Probe down (Undock sled)



Dual extrusion with the HPX2Max extruder.

1     [HPX2MaxPlugin]
2     # The channel on which the servo is connected. The numbering correspond to the Fan number
3     servo_channel = P9_14
5     # Extruder 0 angle to set the servo when extruder 0 is selected, in degree
6     extruder_0_angle = 20
8     # Extruder 1 angle to set the servo when extruder 1 is selected, in degree
9     extruder_1_angle = 175


A more general dual extrusion using a servo for switching between hot ends.

 1     [DualServoPlugin]
 2     # The pin name of where the servo is located
 3     servo_channel = P9_14
 4     # minimum pulse length
 5     pulse_min = 0.01
 6     pulse_max = 0.02
 7     angle_min = 0
 8     angle_max = 180
 9     extruder_0_angle = 87.5
10     extruder_1_angle = 92.5


1 #todo


1 #todo


There is a configuration page where you can choose what ``printer.cfg`` links to and edit ``local.cfg``.