Line 4: Line 4:
=Configuring Melzi Jumpers=
=Configuring Melzi Jumpers=
[[File:MOST_Melzi_jumpers_highlight.jpg‎|thumb|right|Melzi controller board with jumpers highlighted.]]There are two jumpers on the Melzi controller board as shown in the image to the right. The jumper in the middle of the board determines from where the controller will get power, either the USB cable or board power (supplied to power terminals on the Melzi board). Either may be appropriate:
[[File:MOST_Melzi_jumpers_highlight.jpg‎|thumb|right|Melzi controller board with jumpers highlighted.]]There are two jumpers on the Melzi controller board as shown in the image to the right. The jumper in the middle of the board determines from where the controller will get power, either the USB cable or board power (supplied to power terminals on the Melzi board). Either may be appropriate:
*When set to board power, the controller will only be powered when power is applied to the Melzi's power terminals.
*When set to board power, the controller will only be powered when power is applied to the Melzi's power terminals.  This is slightly more stable, so if you experience connection loss, use this setting.
*When set to USB power, the controller will be powered whenever the USB cable is plugged into a powered port, like on a computer.
*When set to USB power, the controller will be powered whenever the USB cable is plugged into a powered port, like on a computer.
The jumper on the bottom of the board determines if the controller auto-resets when a connection made to a computer via the USB cable. The jumper should be over both pins when uploading firmware or an error will result.
The jumper on the bottom of the board determines if the controller auto-resets when a connection made to a computer via the USB cable. The jumper should be over both pins when uploading firmware or an error will result.
{{clear}}
{{clear}}
=Melzi Thermistor Fixed Resistor Value=
=Melzi Thermistor Fixed Resistor Value=
[[File:MOST_Melzi_resistor_highlight.jpg‎|thumb|right|Melzi controller board with locations of fixed resistors highlighted.]]In order to configure firmware so that it controls hot end temperature, both the resistance of the thermistor and the resistance of the fixed resistor on the Melzi board must be known. Note the numbers on the resistors highlighted in the image at right and compare to the magnified images of the resistors:
[[File:MOST_Melzi_resistor_highlight.jpg‎|thumb|right|Melzi controller board with locations of fixed resistors highlighted.]]In order to configure firmware so that it controls hot end temperature, both the resistance of the thermistor and the resistance of the fixed resistor on the Melzi board must be known. Note the numbers on the resistors highlighted in the image at right and compare to the magnified images of the resistors:

Revision as of 16:41, 15 July 2014

Configuring Melzi Jumpers

Melzi controller board with jumpers highlighted.

There are two jumpers on the Melzi controller board as shown in the image to the right. The jumper in the middle of the board determines from where the controller will get power, either the USB cable or board power (supplied to power terminals on the Melzi board). Either may be appropriate:

  • When set to board power, the controller will only be powered when power is applied to the Melzi's power terminals. This is slightly more stable, so if you experience connection loss, use this setting.
  • When set to USB power, the controller will be powered whenever the USB cable is plugged into a powered port, like on a computer.

The jumper on the bottom of the board determines if the controller auto-resets when a connection made to a computer via the USB cable. The jumper should be over both pins when uploading firmware or an error will result.

Melzi Thermistor Fixed Resistor Value

Melzi controller board with locations of fixed resistors highlighted.

In order to configure firmware so that it controls hot end temperature, both the resistance of the thermistor and the resistance of the fixed resistor on the Melzi board must be known. Note the numbers on the resistors highlighted in the image at right and compare to the magnified images of the resistors:


4.7k-ohm resistor.

If the number is 4700 (4.7 k-ohm), set EXT0_TEMPSENSOR_TYPE to 1.

10k-ohm resistor.

If the number is 1002 (10 k-ohm), set EXT0_TEMPSENSOR_TYPE to 97, uncomment USE_GENERIC_THERMISTORTABLE_1 and ensure that GENERIC_THERM1_R0 is 100000 and GENERIC_THERM1_R2 is 10000.

Firmware

  1. Download the firmware from github under the Repetier folder.
  2. Connect the Melzi controller to a host computer with a USB A to mini B cable.
  3. Open the Arduino IDE.
  4. Arduino IDE select correct board.
    Ensure that the proper hardware files for the Melzi controller have been installed by selecting Tools>Board and locate "Mighty 1284p 16 MHz using Optiboot". If not found in the list, return to overview and follow the instructions for installing the hardware files.
  5. Ensure that the Arduino IDE has selected the correct communication port by selecting Tools>Serial Port. If there are multiple ports available, perform an internet search for "serial ports" for the operating system installed (e.g. "windows serial ports") and locate the port assigned to an FTDI USB-serial device. In Windows - go to the control panel and click on the unspecified device, and then the hardware tab and read what port it is.
  6. Select File>Open and navigate to the location where the MOST printer firmware was saved and select Repetier.ino.
  7. Open the configuration.h tab.
    Note that the IDE separates the different files that make up Repetier firmware into different tabs along the top of the edit pane. Locate the Configuration.h tab and click on it.
  8. The bulk of the definitions are logically named and documentation is thorough. Likewise, most of the settings will not need changing, but a few will. It is well worth the time to read through configuration.h and learn what some of the settings do - you will want to tweak your printer and this is the place where tweaking is done.
  9. Locate the line containing #define DELTA_DIAGONAL_ROD and change the number to that recorded during assembly of the tie rods. Magnetic jointed tie rods have a length of 250mm unless otherwise noted.
  10. Locate the line containing #define PRINTER_RADIUS and change the number to 175. This number may need adjustment if the linking boards were not properly spaced during assembly.
  11. Upload the firmware to the Melzi controller (right arrow on toolbar or File>Upload). If the upload was successful, the printer should be ready for commissioning. Calibration is the last step that should be performed.
If you have trouble uploading double check your board choice and port, if correct and you still get this:
Binary sketch size: 56,256 bytes (of a 130,048 byte maximum)
avrdude: stk500_getsync(): not in sync: resp=0x00
Then move the jumper to touch both pins of the autoreset at the bottom of the board and retry uploading.


Notes on Repetier Firmware for the Delta

It's recommended that new printer builders use the firmware maintained by MTU-MOST at github. After having some experience, everyone is encouraged to download the in-the-wild Repetier firmware https://github.com/repetier/Repetier-Firmware. Note that there are two versions, a release (master) version and a development version. Since these exist in the public domain and almost anyone can change them, what is downloaded will not be configured for your printer - you MUST configure the firmware to work with your printer.

All of OS 3-D printer firmwares were originally written for Cartesian printers and were subsequently modified for use with the increasingly popular delta printers. With some annoying exceptions, most all of the configuration settings for Repetier are located in Configuration.h. As of the current version (development v0.91) the following settings are required (assuming the printer is built per the BOM):

#define NUM_EXTRUDER 1

#define MOTHERBOARD 63

#define DRIVE_SYSTEM 3

#define BELT_PITCH 5

#define PULLEY_TEETH 12

#define STEPS_PER_ROTATION 200

#define MICRO_STEPS 16

#define EXT0_INVERSE false

#define EXT0_HEAT_MANAGER 0

#define ENDSTOP_PULLUP_X_MIN false
#define ENDSTOP_PULLUP_Y_MIN false
#define ENDSTOP_PULLUP_Z_MIN false
#define ENDSTOP_PULLUP_X_MAX true
#define ENDSTOP_PULLUP_Y_MAX true
#define ENDSTOP_PULLUP_Z_MAX true

#define ENDSTOP_X_MAX_INVERTING false
#define ENDSTOP_Y_MAX_INVERTING false
#define ENDSTOP_Z_MAX_INVERTING false

#define MIN_HARDWARE_ENDSTOP_X false
#define MIN_HARDWARE_ENDSTOP_Y false
#define MIN_HARDWARE_ENDSTOP_Z false
#define MAX_HARDWARE_ENDSTOP_X true
#define MAX_HARDWARE_ENDSTOP_Y true
#define MAX_HARDWARE_ENDSTOP_Z true

#define INVERT_X_DIR false
#define INVERT_Y_DIR false
#define INVERT_Z_DIR false

#define X_HOME_DIR 1
#define Y_HOME_DIR 1
#define Z_HOME_DIR 1

Virtually anything else can be tweaked to the user's liking. If you notice nothing changes upon uploading a new configuration:

Setting EEPROM_MODE to anything other than 0 causes the firmware to load settings found in EEPROM - it will ignore changes to Configuration.h unless the value of EEPROM_MODE is changed.

Cookies help us deliver our services. By using our services, you agree to our use of cookies.