Updated Marlin customized for Mendel90

Re: Updated Marlin customized for Mendel90

JaredTS486 — Mon, 02 May 2022 20:15:18 -0400

Can anyone advise on how to get Octoprint to work with this firmware? I keep getting "Communication timeout while idle" errors when trying to connect.

Edit: After updating the firmware I can connect to the printer but issue no commands and no temperatures are visible.

Edit: Nevermind, I am going to use nophead's latest Marlin 2.0.x update.

Re: Updated Marlin customized for Mendel90

wueste87 — Sun, 23 Feb 2020 13:24:32 -0500

Hi,

first sorry for my bad english.

I want to update my Mendel90 Dibond (Nophead Kit) to use auto bed leveling and a Display.

I downloaded this firmware here: https://github.com/neildarlow/Marlin/tree/Marlin_v1_Mendel90/Marlin
I set the settings in the configuration.h file and add the Sanguino to the Arduino IDE.
If I try to compile the Code I become the Error Message:

exit status 1
'E_STEPS_PER_MM' was not declared in this scope

This is because I taked the settings one to one from Nophead´s configuration.h.

With which value can I replace it?

#define DEFAULT_AXIS_STEPS_PER_UNIT   {80,80,200*16/1,E_STEPS_PER_MM}

Can you check if I made any other mistakes during the takeover from the Nophead´s Settings, please.
The printer is unchanged so far.

#ifndef CONFIGURATION_H
#define CONFIGURATION_H

// This configurtion file contains the basic settings.
// Advanced settings can be found in Configuration_adv.h
// BASIC SETTINGS: select your board type, temperature sensor type, axis scaling, and endstop configuration

//User specified version info of this build to display in [Pronterface, etc] terminal window during startup.
//Implementation of an idea by Prof Braino to inform user that any changes made
//to this build by the user have been successfully uploaded into firmware.
#define STRING_VERSION_CONFIG_H __DATE__ " " __TIME__ // build date and time
#define STRING_CONFIG_H_AUTHOR "(none, default config)" //Who made the changes.

// SERIAL_PORT selects which serial port should be used for communication with the host.
// This allows the connection of wireless adapters (for instance) to non-default port pins.
// Serial port 0 is still used by the Arduino bootloader regardless of this setting.
#define SERIAL_PORT 0

// This determines the communication speed of the printer
#define BAUDRATE 250000
//#define BAUDRATE 115200

//// The following define selects which electronics board you have. Please choose the one that matches your setup
// 10 = Gen7 custom (Alfons3 Version) "https://github.com/Alfons3/Generation_7_Electronics"
// 11 = Gen7 v1.1, v1.2 = 11
// 12 = Gen7 v1.3
// 13 = Gen7 v1.4
// 3  = MEGA/RAMPS up to 1.2 = 3
// 33 = RAMPS 1.3 / 1.4 (Power outputs: Extruder, Bed, Fan)
// 34 = RAMPS 1.3 / 1.4 (Power outputs: Extruder0, Extruder1, Bed)
// 4  = Duemilanove w/ ATMega328P pin assignment
// 5  = Gen6
// 51 = Gen6 deluxe
// 6  = Sanguinololu < 1.2
// 62 = Sanguinololu 1.2 and above
// 63 = Melzi
// 64 = STB V1.1
// 7  = Ultimaker
// 71 = Ultimaker (Older electronics. Pre 1.5.4. This is rare)
// 8  = Teensylu
// 80 = Rumba
// 81 = Printrboard (AT90USB1286)
// 82 = Brainwave (AT90USB646)
// 9  = Gen3+
// 70 = Megatronics
// 701= Megatronics v2.0
// 702= Minitronics v1.0
// 90 = Alpha OMCA board
// 91 = Final OMCA board
// 301 = Rambo

#ifndef MOTHERBOARD
#define MOTHERBOARD 63
#endif

// This defines the number of extruders
#define EXTRUDERS 1

//// The following define selects which power supply you have. Please choose the one that matches your setup
// 1 = ATX
// 2 = X-Box 360 203Watts (the blue wire connected to PS_ON and the red wire to VCC)

#define POWER_SUPPLY 1

//===========================================================================
//=============================Thermal Settings  ============================
//===========================================================================
//
//--NORMAL IS 4.7kohm PULLUP!-- 1kohm pullup can be used on hotend sensor, using correct resistor and table
//
//// Temperature sensor settings:
// -2 is thermocouple with MAX6675 (only for sensor 0)
// -1 is thermocouple with AD595
// 0 is not used
// 1 is 100k thermistor - best choice for EPCOS 100k (4.7k pullup)
// 2 is 200k thermistor - ATC Semitec 204GT-2 (4.7k pullup)
// 3 is mendel-parts thermistor (4.7k pullup)
// 4 is 10k thermistor !! do not use it for a hotend. It gives bad resolution at high temp. !!
// 5 is 100K thermistor - ATC Semitec 104GT-2 (Used in ParCan) (4.7k pullup)
// 6 is 100k EPCOS - Not as accurate as table 1 (created using a fluke thermocouple) (4.7k pullup)
// 7 is 100k Honeywell thermistor 135-104LAG-J01 (4.7k pullup)
// 8 is 100k 0603 SMD Vishay NTCS0603E3104FXT (4.7k pullup)
// 9 is 100k GE Sensing AL03006-58.2K-97-G1 (4.7k pullup)
// 10 is 100k RS thermistor 198-961 (4.7k pullup)
//
//    1k ohm pullup tables - This is not normal, you would have to have changed out your 4.7k for 1k
//                          (but gives greater accuracy and more stable PID)
// 51 is 100k thermistor - EPCOS (1k pullup)
// 52 is 200k thermistor - ATC Semitec 204GT-2 (1k pullup)
// 55 is 100k thermistor - ATC Semitec 104GT-2 (Used in ParCan) (1k pullup)

#define TEMP_SENSOR_0 1
#define TEMP_SENSOR_1 0
#define TEMP_SENSOR_2 0
#define TEMP_SENSOR_BED 1

// Actual temperature must be close to target for this long before M109 returns success
#define TEMP_RESIDENCY_TIME 60  // (seconds)
#define TEMP_HYSTERESIS 5       // (degC) range of +/- temperatures considered "close" to the target one
#define TEMP_WINDOW     1       // (degC) Window around target to start the recidency timer x degC early.

// The minimal temperature defines the temperature below which the heater will not be enabled It is used
// to check that the wiring to the thermistor is not broken.
// Otherwise this would lead to the heater being powered on all the time.
#define HEATER_0_MINTEMP 5
#define HEATER_1_MINTEMP 5
#define HEATER_2_MINTEMP 5
#define BED_MINTEMP 5

// When temperature exceeds max temp, your heater will be switched off.
// This feature exists to protect your hotend from overheating accidentally, but *NOT* from thermistor short/failure!
// You should use MINTEMP for thermistor short/failure protection.
#define HEATER_0_MAXTEMP 275
#define HEATER_1_MAXTEMP 275
#define HEATER_2_MAXTEMP 275
#define BED_MAXTEMP 150

// If your bed has low resistance e.g. .6 ohm and throws the fuse you can duty cycle it to reduce the
// average current. The value should be an integer and the heat bed will be turned on for 1 interval of
// HEATER_BED_DUTY_CYCLE_DIVIDER intervals.
//#define HEATER_BED_DUTY_CYCLE_DIVIDER 4

// PID settings:
// Comment the following line to disable PID and enable bang-bang.
#define PIDTEMP
#define BANG_MAX 256 // limits current to nozzle while in bang-bang mode; 256=full current
#define PID_MAX 256 // limits current to nozzle while PID is active (see PID_FUNCTIONAL_RANGE below); 256=full current
#ifdef PIDTEMP
  //#define PID_DEBUG // Sends debug data to the serial port.
  //#define PID_OPENLOOP 1 // Puts PID in open loop. M104/M140 sets the output power from 0 to PID_MAX
  #define PID_FUNCTIONAL_RANGE 10 // If the temperature difference between the target temperature and the actual temperature
                                  // is more then PID_FUNCTIONAL_RANGE then the PID will be shut off and the heater will be set to min/max.
  #define PID_INTEGRAL_DRIVE_MAX 255  //limit for the integral term
  #define K1 0.95 //smoothing factor withing the PID
  #define PID_dT ((16.0 * 8.0)/(F_CPU / 64.0 / 256.0)) //sampling period of the temperature routine

// If you are using a preconfigured hotend then you can use one of the value sets by uncommenting it
// Ultimaker
    #define  DEFAULT_Kp 25.05
    #define  DEFAULT_Ki 2.30
    #define  DEFAULT_Kd 68.15

// Makergear
//    #define  DEFAULT_Kp 7.0
//    #define  DEFAULT_Ki 0.1
//    #define  DEFAULT_Kd 12

// Mendel Parts V9 on 12V
//    #define  DEFAULT_Kp 63.0
//    #define  DEFAULT_Ki 2.25
//    #define  DEFAULT_Kd 440
#endif // PIDTEMP

// Bed Temperature Control
// Select PID or bang-bang with PIDTEMPBED.  If bang-bang, BED_LIMIT_SWITCHING will enable hysteresis
//
// uncomment this to enable PID on the bed.   It uses the same frequency PWM as the extruder.
// If your PID_dT above is the default, and correct for your hardware/configuration, that means 7.689Hz,
// which is fine for driving a square wave into a resistive load and does not significantly impact you FET heating.
// This also works fine on a Fotek SSR-10DA Solid State Relay into a 250W heater.
// If your configuration is significantly different than this and you don't understand the issues involved, you proabaly
// shouldn't use bed PID until someone else verifies your hardware works.
// If this is enabled, find your own PID constants below.
//#define PIDTEMPBED
//
//#define BED_LIMIT_SWITCHING

// This sets the max power delived to the bed, and replaces the HEATER_BED_DUTY_CYCLE_DIVIDER option.
// all forms of bed control obey this (PID, bang-bang, bang-bang with hysteresis)
// setting this to anything other than 256 enables a form of PWM to the bed just like HEATER_BED_DUTY_CYCLE_DIVIDER did,
// so you shouldn't use it unless you are OK with PWM on your bed.  (see the comment on enabling PIDTEMPBED)
#define MAX_BED_POWER 256 // limits duty cycle to bed; 256=full current

#ifdef PIDTEMPBED
//120v 250W silicone heater into 4mm borosilicate (MendelMax 1.5+)
//from FOPDT model - kp=.39 Tp=405 Tdead=66, Tc set to 79.2, argressive factor of .15 (vs .1, 1, 10)
    #define  DEFAULT_bedKp 10.00
    #define  DEFAULT_bedKi .023
    #define  DEFAULT_bedKd 305.4

//120v 250W silicone heater into 4mm borosilicate (MendelMax 1.5+)
//from pidautotune
//    #define  DEFAULT_bedKp 97.1
//    #define  DEFAULT_bedKi 1.41
//    #define  DEFAULT_bedKd 1675.16

// FIND YOUR OWN: "M303 E-1 C8 S90" to run autotune on the bed at 90 degreesC for 8 cycles.
#endif // PIDTEMPBED



//this prevents dangerous Extruder moves, i.e. if the temperature is under the limit
//can be software-disabled for whatever purposes by
#define PREVENT_DANGEROUS_EXTRUDE
//if PREVENT_DANGEROUS_EXTRUDE is on, you can still disable (uncomment) very long bits of extrusion separately.
#define PREVENT_LENGTHY_EXTRUDE

#define EXTRUDE_MINTEMP 170
#define EXTRUDE_MAXLENGTH (X_MAX_LENGTH+Y_MAX_LENGTH) //prevent extrusion of very large distances.

//===========================================================================
//=============================Mechanical Settings===========================
//===========================================================================

// Uncomment the following line to enable CoreXY kinematics
// #define COREXY

// corse Endstop Settings
#define ENDSTOPPULLUPS // Comment this out (using // at the start of the line) to disable the endstop pullup resistors

#ifndef ENDSTOPPULLUPS
  // fine Enstop settings: Individual Pullups. will be ignord if ENDSTOPPULLUPS is defined
  #define ENDSTOPPULLUP_XMAX
  #define ENDSTOPPULLUP_YMAX
  #define ENDSTOPPULLUP_ZMAX
  #define ENDSTOPPULLUP_XMIN
  #define ENDSTOPPULLUP_YMIN
  //#define ENDSTOPPULLUP_ZMIN
#endif

#ifdef ENDSTOPPULLUPS
  #define ENDSTOPPULLUP_XMAX
  #define ENDSTOPPULLUP_YMAX
  #define ENDSTOPPULLUP_ZMAX
  #define ENDSTOPPULLUP_XMIN
  #define ENDSTOPPULLUP_YMIN
  #define ENDSTOPPULLUP_ZMIN
#endif

// The pullups are needed if you directly connect a mechanical endswitch between the signal and ground pins.
const bool X_ENDSTOPS_INVERTING = false; // set to true to invert the logic of the endstops.
const bool Y_ENDSTOPS_INVERTING = false; // set to true to invert the logic of the endstops.
const bool Z_ENDSTOPS_INVERTING = false; // set to true to invert the logic of the endstops.
//#define DISABLE_MAX_ENDSTOPS

// For Inverting Stepper Enable Pins (Active Low) use 0, Non Inverting (Active High) use 1
#define X_ENABLE_ON 0
#define Y_ENABLE_ON 0
#define Z_ENABLE_ON 0
#define E_ENABLE_ON 0 // For all extruders

// Disables axis when it's not being used.
#define DISABLE_X false
#define DISABLE_Y false
#define DISABLE_Z false
#define DISABLE_E false // For all extruders

#define INVERT_X_DIR false    // for Mendel set to false, for Orca set to true
#define INVERT_Y_DIR false    // for Mendel set to true, for Orca set to false
#define INVERT_Z_DIR true     // for Mendel set to false, for Orca set to true
#define INVERT_E0_DIR true   // for direct drive extruder v9 set to true, for geared extruder set to false
#define INVERT_E1_DIR false    // for direct drive extruder v9 set to true, for geared extruder set to false
#define INVERT_E2_DIR false   // for direct drive extruder v9 set to true, for geared extruder set to false

// ENDSTOP SETTINGS:
// Sets direction of endstops when homing; 1=MAX, -1=MIN
#define X_HOME_DIR -1
#define Y_HOME_DIR -1
#define Z_HOME_DIR -1

#define min_software_endstops true //If true, axis won't move to coordinates less than HOME_POS.
#define max_software_endstops true  //If true, axis won't move to coordinates greater than the defined lengths below.
// Travel limits after homing
#define X_MAX_POS 100
#define X_MIN_POS -100
#define Y_MAX_POS 100
#define Y_MIN_POS -100
#define Z_MAX_POS (Z_HOME_POS - 0.1)
#define Z_MIN_POS 0

#define X_MAX_LENGTH (X_MAX_POS - X_MIN_POS)
#define Y_MAX_LENGTH (Y_MAX_POS - Y_MIN_POS)
#define Z_MAX_LENGTH (Z_MAX_POS - Z_MIN_POS)

// The position of the homing switches
//#define MANUAL_HOME_POSITIONS  // If defined, MANUAL_*_HOME_POS below will be used
//#define BED_CENTER_AT_0_0  // If defined, the center of the bed is at (X=0, Y=0)

//Manual homing switch locations:
#define MANUAL_X_HOME_POS (X_MIN_POS - 1)
#define MANUAL_Y_HOME_POS (Y_MIN_POS - 1)
#define MANUAL_Z_HOME_POS (204.11)

//// MOVEMENT SETTINGS
#define NUM_AXIS 4 // The axis order in all axis related arrays is X, Y, Z, E
#define HOMING_FEEDRATE {35*60, 35*60, 4*60, 0}  // set the homing speeds (mm/min)

// default settings

#define DEFAULT_AXIS_STEPS_PER_UNIT   {80,80,200*16/1,E_STEPS_PER_MM}  // default steps per unit for ultimaker
#define DEFAULT_MAX_FEEDRATE          {400, 400, 4, 30}    // (mm/sec)
#define DEFAULT_MAX_ACCELERATION      {2000,2000,150,5000}    // X, Y, Z, E maximum start speed for accelerated moves. E default values are good for skeinforge 40+, for older versions raise them a lot.

#define DEFAULT_ACCELERATION          2000    // X, Y, Z and E max acceleration in mm/s^2 for printing moves
#define DEFAULT_RETRACT_ACCELERATION  5000   // X, Y, Z and E max acceleration in mm/s^2 for r retracts

// Offset of the extruders (uncomment if using more than one and relying on firmware to position when changing).
// The offset has to be X=0, Y=0 for the extruder 0 hotend (default extruder).
// For the other hotends it is their distance from the extruder 0 hotend.
// #define EXTRUDER_OFFSET_X {0.0, 20.00} // (in mm) for each extruder, offset of the hotend on the X axis
// #define EXTRUDER_OFFSET_Y {0.0, 5.00}  // (in mm) for each extruder, offset of the hotend on the Y axis

// The speed change that does not require acceleration (i.e. the software might assume it can be done instanteneously)
#define DEFAULT_XYJERK                10.0    // (mm/sec)
#define DEFAULT_ZJERK                 0.0     // (mm/sec)
#define DEFAULT_EJERK                 10.0    // (mm/sec)

//===========================================================================
//=============================Additional Features===========================
//===========================================================================

// EEPROM
// the microcontroller can store settings in the EEPROM, e.g. max velocity...
// M500 - stores paramters in EEPROM
// M501 - reads parameters from EEPROM (if you need reset them after you changed them temporarily).
// M502 - reverts to the default "factory settings".  You still need to store them in EEPROM afterwards if you want to.
//define this to enable eeprom support
//#define EEPROM_SETTINGS
//to disable EEPROM Serial responses and decrease program space by ~1700 byte: comment this out:
// please keep turned on if you can.
//#define EEPROM_CHITCHAT

// Preheat Constants
#define PLA_PREHEAT_HOTEND_TEMP 180 
#define PLA_PREHEAT_HPB_TEMP 70
#define PLA_PREHEAT_FAN_SPEED 255   // Insert Value between 0 and 255

#define ABS_PREHEAT_HOTEND_TEMP 240
#define ABS_PREHEAT_HPB_TEMP 100
#define ABS_PREHEAT_FAN_SPEED 255   // Insert Value between 0 and 255

//LCD and SD support
//#define ULTRA_LCD  //general lcd support, also 16x2
//#define DOGLCD  // Support for SPI LCD 128x64 (Controller ST7565R graphic Display Family)
//#define SDSUPPORT // Enable SD Card Support in Hardware Console
//#define SDSLOW // Use slower SD transfer mode (not normally needed - uncomment if you're getting volume init error)

//#define ULTIMAKERCONTROLLER //as available from the ultimaker online store.
//#define ULTIPANEL  //the ultipanel as on thingiverse

// The RepRapDiscount Smart Controller (white PCB)
// [reprap.org]
//#define REPRAP_DISCOUNT_SMART_CONTROLLER

// The GADGETS3D G3D LCD/SD Controller (blue PCB)
// [reprap.org]
//#define G3D_PANEL

// The RepRapDiscount FULL GRAPHIC Smart Controller (quadratic white PCB)
// [reprap.org]
//
// ==> REMEMBER TO INSTALL U8glib to your ARDUINO library folder: [code.google.com]
//#define REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER

// The RepRapWorld REPRAPWORLD_KEYPAD v1.1
// [reprapworld.com]
//#define REPRAPWORLD_KEYPAD
//#define REPRAPWORLD_KEYPAD_MOVE_STEP 10.0 // how much should be moved when a key is pressed, eg 10.0 means 10mm per click

//automatic expansion
#if defined (REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER)
 #define DOGLCD
 #define U8GLIB_ST7920
 #define REPRAP_DISCOUNT_SMART_CONTROLLER
#endif

#if defined(ULTIMAKERCONTROLLER) || defined(REPRAP_DISCOUNT_SMART_CONTROLLER) || defined(G3D_PANEL)
 #define ULTIPANEL
 #define NEWPANEL
#endif

#if defined(REPRAPWORLD_KEYPAD)
  #define NEWPANEL
  #define ULTIPANEL
#endif

//I2C PANELS

//#define LCD_I2C_SAINSMART_YWROBOT
#ifdef LCD_I2C_SAINSMART_YWROBOT
  // This uses the LiquidCrystal_I2C library ( [bitbucket.org] )
  // Make sure it is placed in the Arduino libraries directory.
  #define LCD_I2C_TYPE_PCF8575
  #define LCD_I2C_ADDRESS 0x27   // I2C Address of the port expander
  #define NEWPANEL
  #define ULTIPANEL 
#endif

// PANELOLU2 LCD with status LEDs, separate encoder and click inputs
//#define LCD_I2C_PANELOLU2
#ifdef LCD_I2C_PANELOLU2
  // This uses the LiquidTWI2 library v1.2.3 or later ( [github.com] )
  // Make sure the LiquidTWI2 directory is placed in the Arduino or Sketchbook libraries subdirectory.
  // (v1.2.3 no longer requires you to define PANELOLU in the LiquidTWI2.h library header file)
  // Note: The PANELOLU2 encoder click input can either be directly connected to a pin 
  //       (if BTN_ENC defined to != -1) or read through I2C (when BTN_ENC == -1). 
  #define LCD_I2C_TYPE_MCP23017
  #define LCD_I2C_ADDRESS 0x20 // I2C Address of the port expander
  #define LCD_USE_I2C_BUZZER //comment out to disable buzzer on LCD
  #define NEWPANEL
  #define ULTIPANEL 
#endif

// Panucatt VIKI LCD with status LEDs, integrated click & L/R/U/P buttons, separate encoder inputs
//#define LCD_I2C_VIKI
#ifdef LCD_I2C_VIKI
  // This uses the LiquidTWI2 library v1.2.3 or later ( [github.com] )
  // Make sure the LiquidTWI2 directory is placed in the Arduino or Sketchbook libraries subdirectory.
  // Note: The pause/stop/resume LCD button pin should be connected to the Arduino
  //       BTN_ENC pin (or set BTN_ENC to -1 if not used)
  #define LCD_I2C_TYPE_MCP23017 
  #define LCD_I2C_ADDRESS 0x20 // I2C Address of the port expander
  #define LCD_USE_I2C_BUZZER //comment out to disable buzzer on LCD (requires LiquidTWI2 v1.2.3 or later)
  #define NEWPANEL
  #define ULTIPANEL 
#endif

#ifdef ULTIPANEL
//  #define NEWPANEL  //enable this if you have a click-encoder panel
  #define SDSUPPORT
  #define ULTRA_LCD
  #ifdef DOGLCD // Change number of lines to match the DOG graphic display
    #define LCD_WIDTH 20
    #define LCD_HEIGHT 5
  #else
    #define LCD_WIDTH 20
    #define LCD_HEIGHT 4
  #endif
#else //no panel but just lcd
  #ifdef ULTRA_LCD
  #ifdef DOGLCD // Change number of lines to match the 128x64 graphics display
    #define LCD_WIDTH 20
    #define LCD_HEIGHT 5
  #else
    #define LCD_WIDTH 16
    #define LCD_HEIGHT 2
  #endif
  #endif
#endif

// Increase the FAN pwm frequency. Removes the PWM noise but increases heating in the FET/Arduino
//#define FAST_PWM_FAN

// M240  Triggers a camera by emulating a Canon RC-1 Remote
// Data from: [www.doc-diy.net]
// #define PHOTOGRAPH_PIN     23

// SF send wrong arc g-codes when using Arc Point as fillet procedure
//#define SF_ARC_FIX

// Support for the BariCUDA Paste Extruder.
//#define BARICUDA

/*********************************************************************\
*
* R/C SERVO support
*
* Sponsored by TrinityLabs, Reworked by codexmas
*
**********************************************************************/

// Number of servos
//
// If you select a configuration below, this will receive a default value and does not need to be set manually
// set it manually if you have more servos than extruders and wish to manually control some
// leaving it undefined or defining as 0 will disable the servo subsystem
// If unsure, leave commented / disabled
//
// #define NUM_SERVOS 3

#include "Configuration_adv.h"
#include "thermistortables.h"

#endif //__CONFIGURATION_H

Thanks for your help

Re: Updated Marlin customized for Mendel90

neildarlow — Tue, 27 Dec 2016 05:03:21 -0500

Hi,

I believe there was a bug in the PID code which was fixed. The initial overshoot is much reduced particularly if you use the PID autotune on the extruder and bed.

Regards,
Neil Darlow

Re: Updated Marlin customized for Mendel90

amr_dwarf — Sun, 25 Dec 2016 17:29:22 -0500

Now I have tried a few test prints with the new firmware.
It works well. Cannot see any change in print quality. I guess that is more down to the slicer.
What I do see is much more stable temperatures both bed and nozzle. Almost no over shoot at warm up.

Re: Updated Marlin customized for Mendel90

amr_dwarf — Fri, 23 Dec 2016 12:30:51 -0500

Today I finally got around to install the latest Marlin by Neil Darlow.
Some minor quirks to iron out before I got it working.
Now its time to change from the very outdated Slic3r to a more modern slicer software.

A question to those who are more used to use the Paneloulou with their printers. How do I set the Z-height from the control panel? Or do I have to use the Z-offset, and how do I set that?

Re: Updated Marlin customized for Mendel90

cederron — Fri, 25 Nov 2016 11:23:43 -0500

I have Marlin rc7 running in my Mendel90 (converted to RAMPS).
It's actually pretty easy, just 5 minutes messing with a configuration file...

Re: Updated Marlin customized for Mendel90

Conti — Wed, 16 Nov 2016 06:28:40 -0500

Hello!

I own a Mendel 90 dibond.
I want to try this firmware, but i also want to install an auto-bed-levelling-system.
Did someone already do that?

Regards,
Holger

Re: Updated Marlin customized for Mendel90

neildarlow — Mon, 31 Oct 2016 16:21:31 -0400

Hi All,

I have added a new branch to my Github Marlin Repository named Mendel90_RC.

This branch has originated from Marlin-1.1.0-RC7 and I intend to use it to follow future RC versions with tagged stable releases as they occur.

There are a few items that you should be aware of in setting-up for, and using, this branch:

Arduino IDE 1.6.0 or later is required
The Melzi support files structure has changed
The format of Configuration.h and Configuration_adv.h has changed significantly
This firmware is literally a re-configuration of standard Marlin

I am currently building this firmware with Arduino IDE 1.6.4. It might be possible to use a later version but please be aware that the very latest version often contains bugs. Please test thoroughly before raising bug reports.

After selecting the Mendel90_RC branch from the Github Repository web interface you may either clone or download a zipfile of the repository content.

Three folders are of interest:

ArduinoAddons/hardware/melzi
ArduinoAddons/libraries/LiquidTWI2
Marlin

ArduinoAddons/hardware/melzi should be copied into your Arduino/hardware folder.
ArduinoAddons/libraries/LiquidTWI2 should be copied into your Arduino/libraries folder.
Marlin should be copied into your Arduino folder.

The functionality of this firmware is similar to my previous version and only requires editing of Z_HEIGHT_MM and E_STEPS_PER_MM expressions located towards the top of Configuration.h. Panelolu2 support is included as before.

There are a number of new features in this version:

X, Y and Z coordinate display is reverted to 1mm resolution. The axis labels blink to indicate an un-homed condition
Thermal runaway protection is enabled by default
Cooling fan kickstart and minimum fan speed are set so that cooling fan speed control is possible
Z axis Baby-stepping is enabled to permit on-the-fly adjustment of first layer height at 0.01mm resolution
Completely revised Panelolu2 menu structure with access to many operational settings which may be adjusted and stored in EEPROM
Progress bar display of print progress on Panelolu2 LCD display
Lots of experimental features which are defaulted to off due to a need to configure their operation

If you have made additional customisations to Configuration.h or Configuration_adv.h please merge them into my new versions. Do not attempt to use files from an earlier version of Marlin - they are not compatible due to changes in configuration macro names and additions.

In order to make support of different Melzi versions possible the Melzi board choice is presented under the heading Melzi AVR Boards of the Board menu item as Melzi 1.0/2.0 hybrid. This describes nophead's Melzi as shipped with his Dibond kits i.e. an Ardentissimo-style board with ATmega-1284p microcontroller running at 16MHz.

Please enjoy testing this version of Marlin and be aware that, as this is a specific configuration of standard upstream Marlin, any bugs should be reported to the Marlin project.

Regards,
Neil Darlow

Re: Updated Marlin customized for Mendel90

neildarlow — Thu, 19 May 2016 07:16:20 -0400

Hi,

It could possibly be supported in the example configuration files directory. It really depends on what future interest there is for the Mendel90.

I am happy with my Mendel90 using the firmware at its present level. Many of the recent changes to Marlin involve code re-factoring and newer features which the Mendel90 does not support without modification.

The bed levelling code is known to work because I configured it for a friend who has a Prusa i3 with Panelolu2 and he is happy with it (3-point levelling only).

Regards,
Neil Darlow

Re: Updated Marlin customized for Mendel90

marcosscriven — Thu, 19 May 2016 06:10:39 -0400

Quote
neildarlow
Hi,

When Marlin-1.1.0 is released I will produce another branch for the Mendel90.

The problem in doing this is that Arduino-1.0.x will not build the Marlin-1.0.x and later code but Marlin-1.1.0 will require Arduino-1.6.8 or later. This means that I will have to transition to a newer Arduino and support of the old fork will likely cease.

I am still using my Mendel90 but much of my current efforts are going into developing my own dual-extruder printer. Not much to say about it right now except that it will be opensource and designed to be built by enthusiasts. The electronics will be custom and I cannot see them being home-built however.

Regards,
Neil Darlow

May I ask why the Mendel90 version needs to be permanently branched? I'm seriously out of date, but when I last looked the differences seemed to be some hardcoded differences for z home direction and so forth. Could those not be merged upstream as build options?

Re: Updated Marlin customized for Mendel90

neildarlow — Thu, 21 Apr 2016 12:15:01 -0400

Hi,

The Melzi is just one of many boards supported by Marlin. It is just a case of providing the relevant numerical define for what Marlin calls the Motherboard.

Regards,
Neil Darlow

Re: Updated Marlin customized for Mendel90

bastard — Wed, 20 Apr 2016 05:29:56 -0400

Hi Neil,

how do you integrate the Melzi board into Arduino?

Re: Updated Marlin customized for Mendel90

neildarlow — Tue, 19 Apr 2016 09:22:55 -0400

Hi,

When Marlin-1.1.0 is released I will produce another branch for the Mendel90.

The problem in doing this is that Arduino-1.0.x will not build the Marlin-1.0.x and later code but Marlin-1.1.0 will require Arduino-1.6.8 or later. This means that I will have to transition to a newer Arduino and support of the old fork will likely cease.

I am still using my Mendel90 but much of my current efforts are going into developing my own dual-extruder printer. Not much to say about it right now except that it will be opensource and designed to be built by enthusiasts. The electronics will be custom and I cannot see them being home-built however.

Regards,
Neil Darlow

Re: Updated Marlin customized for Mendel90

sguzzel — Sun, 17 Apr 2016 05:22:51 -0400

Hi,

I am currently trying to update to the latest Marlin 1.1 RC branch and use the current Arduino Version. To get there, I merged neildarows code with the current stable release of Marlin (1.0.2-1). Seems to works fine for me. If anyone is willing to test the code just send me a pm.

When Marlin 1.1 and Arduino 1.6.8 is working for me, I will publish the code at github (@neildarow: maybe I can reuse your repo?)

Regards

Re: Updated Marlin customized for Mendel90

nophead — Fri, 29 Jan 2016 18:50:09 -0500

I don't use that code because it is more trouble than it is worth unless you use 40W heater cartridges, in which case you need it because they can burn your house down.

Re: Updated Marlin customized for Mendel90

daichiasuka — Fri, 29 Jan 2016 15:35:38 -0500

That's fair for a PCB bed heater; I just used it as an example. The code change applies to all heaters, however. The default of being unable to recover 4 degrees on a hotend in 40 seconds is too much in my opinion. If I can't recover 4 degrees in a fraction of that time, it may not be a runaway issue, but something is wrong.

Like I said, the right way to really do this would be adding options to configure settings for each heater and have the code realize that current behavior is outside of realistic limits and/or dangerous.

Re: Updated Marlin customized for Mendel90

nophead — Fri, 29 Jan 2016 03:43:59 -0500

Runaway protection is pointless for a PCB bed heater and will just cause problems. The temperature is self limiting because the resistance of copper increases with temperature. It will max out at about 135C when driven with 12V, so nothing bad happens.

Re: Updated Marlin customized for Mendel90

daichiasuka — Thu, 28 Jan 2016 22:11:34 -0500

I like the idea behind the Thermal Run Away code to add a bit of safety, but I was having issues with it. Namely, I warm the bed part of the way before I move the hot end into position to finish the warm up process. Doing so would trigger the a Thermal Run Away since the difference in temperature was greater than the threshold and the bed cannot close the gap fast enough. I could have tweaked the settings, but that would just handicap the protection itself. Instead, I submitted a pull request to your github code which allows the temperature to be changed after the initial warming phase. If at any point the intended temperature changes, the Thermal Run Away process will fall back to the warming phase until the targeted temperature is reached. This allows for intentional changes during the printing process, but will still trigger the protection in the event of a sensor issue.

I should note that this does introduce the possibility of a Thermal Run Away if a problem occurs during an intended temperature change. This condition is already possible at the beginning of a print, but it could not easily occur during the print. (Technically, it could be done by turning the heater off to reset the Thermal Run Away Protection and turning it back on at a higher temperature.) The correct solution to this is not in the existing Thermal Run Away code but to add limits and expected outcomes to the code responsible for monitoring temperature changes during an intentional temperature change. [e.g. if (current_temp < previous_temp and current_temp < target_temp) or (time_passed_for_change > reasonable_time_for_temp_difference): something is wrong.]

[github.com]

Re: Updated Marlin customized for Mendel90

amr_dwarf — Thu, 28 Jan 2016 14:36:52 -0500

*Problem solved*
** The fault was stupid me using a coma as a decimal point....**

Hello,

I have this version of Marlin in my Mendel90 and use it with a Paneloulu2 without problems since a year or so.

But now I was to change the home position and get errors. I followed the instructions in the first post in this thread, but it does not work.

Help..

[attachment 71051 error.png]

Marlin.h:69: error: echomagic causes a section type conflict
Marlin.h:68: error: errormagic causes a section type conflict
Marlin_main.cpp:4394: error: __c causes a section type conflict
Marlin_main.cpp:4393: error: __c causes a section type conflict
Marlin_main.cpp:4381: error: __c causes a section type conflict
Marlin_main.cpp:4380: error: __c causes a section type conflict
Marlin_main.cpp:3894: error: __c causes a section type conflict
Marlin_main.cpp:3882: error: __c causes a section type conflict
Marlin_main.cpp:3872: error: __c causes a section type conflict
Marlin_main.cpp:3870: error: __c causes a section type conflict
Marlin_main.cpp:3598: error: __c causes a section type conflict
Marlin_main.cpp:3507: error: __c causes a section type conflict
Marlin_main.cpp:3499: error: __c causes a section type conflict
Marlin_main.cpp:3497: error: __c causes a section type conflict
Marlin_main.cpp:3496: error: __c causes a section type conflict
Marlin_main.cpp:3490: error: __c causes a section type conflict
Marlin_main.cpp:2789: error: __c causes a section type conflict
Marlin_main.cpp:2777: error: __c causes a section type conflict
Marlin_main.cpp:2769: error: __c causes a section type conflict
Marlin_main.cpp:2735: error: __c causes a section type conflict
Marlin_main.cpp:2733: error: __c causes a section type conflict
Marlin_main.cpp:2731: error: __c causes a section type conflict
Marlin_main.cpp:2728: error: __c causes a section type conflict
Marlin_main.cpp:2726: error: __c causes a section type conflict
Marlin_main.cpp:2724: error: __c causes a section type conflict
Marlin_main.cpp:2722: error: __c causes a section type conflict
Marlin_main.cpp:2713: error: __c causes a section type conflict
Marlin_main.cpp:2643: error: __c causes a section type conflict
Marlin_main.cpp:2554: error: __c causes a section type conflict
Marlin_main.cpp:2545: error: __c causes a section type conflict
Marlin_main.cpp:2543: error: __c causes a section type conflict
Marlin_main.cpp:2541: error: __c causes a section type conflict
Marlin_main.cpp:2523: error: __c causes a section type conflict
Marlin_main.cpp:2516: error: __c causes a section type conflict
Marlin_main.cpp:2487: error: __c causes a section type conflict
Marlin_main.cpp:2484: error: __c causes a section type conflict
Marlin_main.cpp:2482: error: __c causes a section type conflict
Marlin_main.cpp:2433: error: __c causes a section type conflict
Marlin_main.cpp:2400: error: __c causes a section type conflict
Marlin_main.cpp:2392: error: __c causes a section type conflict
Marlin_main.cpp:2384: error: __c causes a section type conflict
Marlin_main.cpp:2382: error: __c causes a section type conflict
Marlin_main.cpp:2380: error: __c causes a section type conflict
Marlin_main.cpp:2376: error: __c causes a section type conflict
Marlin_main.cpp:2374: error: __c causes a section type conflict
Marlin_main.cpp:2371: error: __c causes a section type conflict
Marlin_main.cpp:2369: error: __c causes a section type conflict
Marlin_main.cpp:2039: error: __c causes a section type conflict
Marlin_main.cpp:1927: error: __c causes a section type conflict
Marlin_main.cpp:1925: error: __c causes a section type conflict
Marlin_main.cpp:1914: error: __c causes a section type conflict
Marlin_main.cpp:1909: error: __c causes a section type conflict
Marlin_main.cpp:1907: error: __c causes a section type conflict
Marlin_main.cpp:1883: error: __c causes a section type conflict
Marlin_main.cpp:1379: error: __c causes a section type conflict
Marlin_main.cpp:856: error: home_dir_P causes a section type conflict
Marlin_main.cpp:851: error: base_min_pos_P causes a section type conflict
Marlin_main.cpp:855: error: home_retract_mm_P causes a section type conflict
Marlin_main.cpp:785: error: __c causes a section type conflict
Marlin_main.cpp:778: error: __c causes a section type conflict
Marlin_main.cpp:732: error: __c causes a section type conflict
Marlin_main.cpp:731: error: __c causes a section type conflict
Marlin_main.cpp:728: error: __c causes a section type conflict
Marlin_main.cpp:710: error: __c causes a section type conflict
Marlin_main.cpp:695: error: __c causes a section type conflict
Marlin_main.cpp:684: error: __c causes a section type conflict
Marlin_main.cpp:667: error: __c causes a section type conflict
Marlin_main.cpp:665: error: __c causes a section type conflict
Marlin_main.cpp:624: error: __c causes a section type conflict
Marlin_main.cpp:618: error: __c causes a section type conflict
Marlin_main.cpp:609: error: __c causes a section type conflict
Marlin_main.cpp:562: error: __c causes a section type conflict
Marlin_main.cpp:560: error: __c causes a section type conflict
Marlin_main.cpp:556: error: __c causes a section type conflict
Marlin_main.cpp:555: error: __c causes a section type conflict
Marlin_main.cpp:554: error: __c causes a section type conflict
Marlin_main.cpp:553: error: __c causes a section type conflict
Marlin_main.cpp:552: error: __c causes a section type conflict
Marlin_main.cpp:551: error: __c causes a section type conflict
Marlin_main.cpp:547: error: __c causes a section type conflict
Marlin_main.cpp:546: error: __c causes a section type conflict
Marlin_main.cpp:543: error: __c causes a section type conflict
Marlin_main.cpp:542: error: __c causes a section type conflict
Marlin_main.cpp:541: error: __c causes a section type conflict
Marlin_main.cpp:540: error: __c causes a section type conflict
Marlin_main.cpp:539: error: __c causes a section type conflict
Marlin_main.cpp:534: error: __c causes a section type conflict
Marlin_main.cpp:448: error: __c causes a section type conflict
Marlin_main.cpp:446: error: __c causes a section type conflict
Marlin_main.cpp:433: error: __c causes a section type conflict
Marlin_main.cpp:431: error: __c causes a section type conflict

Re: Updated Marlin customized for Mendel90

arndtw — Sun, 24 Jan 2016 06:35:42 -0500

Thank you again;
Now thinks are getting clearer :)

I found the definitions of port number in fastio.h

I will experiment a bit, when my sensor arrived.

Wolfgang

Re: Updated Marlin customized for Mendel90

miharix — Sat, 23 Jan 2016 14:22:44 -0500

If I remember correctly, I was looking at the schematic reading the existing code and g-code and test my predictions by simply changing an existing end stop pin, and then checking the endstops status ( M119 ).

I'll think the EXT-A2 is A.pin 29 EXT-A3 is 28, and EXT-A4 is 27
Because the M42 P29 S255 is the gcode command that activates my bed fan (pin under Z_MIN_PIN)

Changing X0 Y0 probably isn't necessary, but I didn't experiment to long after
I found that after G29 I simply couldn't move to negative coordinates, but positive did go till bed dimensions.
For me it didn't make much difference, because the new bed material and thickness did require new gcodes.
Also most prints I do generate gcode before printing (stl/stl-s->Slic3r(position->select material...->send to printer)->RsPi+octoprint load & print )

Re: Updated Marlin customized for Mendel90

arndtw — Sat, 23 Jan 2016 11:48:44 -0500

Thank you for the detailed description.

I have still some questions to that.

I see that you connected the Z-Probe to JP16 Pin 2 (i.e. EXT A1)

In pins.h you added

#define Z_MIN_PIN 30
#define Z_STOP_PIN 20
#define Z_MAX_PIN 20

Where are those numbers (20,30) from. Is there a table like EXT-A1 on a melzi is pin Arduino Pin 30 ?

Is it really neccessary to change X0 and Y0 Postion. I have 100 gcode files that are obselete if i change that.

Wolfgang

My mod on Updated Marlin customized for Mendel90

miharix — Fri, 22 Jan 2016 15:50:36 -0500

If I didn't forget something, those are my steps:

0. Bed is from 214mm x 202mm x 3mm aluminum (from www.plocevine.si) - same dimensions and mounting as original glass from nophead

1. Sensor is "LJ12A3-4-Z/BX Inductive Proximity Sensor Switch NPN DC6-36V" from ebay seller "gameszone.no1"
[attachment 70538 Senzor_bed.jpg]

2. The small PCB on the head is little customized.
[attachment 70536 Senzor_wire.jpg]
2.1 Drilled a 3. hole and inserted single pin from pin header
2.2 Used resistors: 2x serial 100ohm(=200ohm) 1x 330ohm
2.3 Used hot glue for securing and isolating
*On the picture you can see that I cut a trace but that was only my mistake.
!! test using a voltmeter before connecting the pin to the board !!
[attachment 70539 PCB_back_mod.jpg][attachment 70540 PCB_back_done.jpg]
[attachment 70537 Z_level_pin.jpg]

3. I had some problems installing some Arduino dependency for board on Ubuntu, so I used Win10 32x & Arduino 1.0.1 (from nophead SD card)

4. Reset the board(little button on the board) before uploading - This stupid thing took me few days :S, because I turned printer on, and at upload I got some generic error.

In the code I needed to:
- define the sensor pin
- changed it so that it still homes UP
- the Z0 is on the board (don't forget to change your sensor distance from nozzle)
- the X0 Y0 is in one of the corners (when in center the calibration goes nuts )
- LCD is disabled because it used to much ROM

/*
*that little red board on the photo connected to the board using yellow cable is a "IRF520 MOS FET Driver" for bed collying fan.
*because of the aluminum my bed temperature is 10°C lower than using glass, For ABS I use UHU stick, and for PLA nothing.
*It works great, only the print speed had to be dropped or it did skip steps on XY
*My extruder is E3Dv6
*Sensor holder: [www.thingiverse.com]
*/

My starting G-code using Slic3r:

M106 ; extruder fan on, to stop oozing from last print
G28 ; home all axes
G1 X110 Y140 F9000 ; move X Y fast on the center
G1 Z50 ; move Z closer to the bed, to reduce waiting time
M106 S0 ; extruder fan off
M42 P29 S0; bed fan off


M190 S[first_layer_bed_temperature] ; bed on[first_layer_bed_temperature] degree and wait till it it reaches

G29 ;perform bed calibration

M104 S[first_layer_temperature] ; set extruder on [first_layer_temperature]

G1 Z5 ; - those lines below still aren't optimal
G1 X30 Y0
G1 Z0 ; nozzle on the bed, to prevent oozing
M109 S[first_layer_temperature] ; wait extruder to reach [first_layer_temperature]

G1 Z0.3 ; Up a little bit
G92 E0 ;set Extruder coordinate 0
G1 X100 E5 F100 ; move 100mm and extrude 5mm at speed 100 
G1 Z2 ; tare off

Hope it helps a little bit.

Greetings,
Miha

Re: Updated Marlin customized for Mendel90

miharix — Wed, 20 Jan 2016 14:02:05 -0500

Damn, I forgot to post.
I got my Z-probe working & also kept homing up not down on my nophead mendel 90.
I'll post the minimal changed source and HW details tomorrow about the same time. (It's on a laptop, currently in office)

Re: Updated Marlin customized for Mendel90

arndtw — Wed, 20 Jan 2016 12:54:56 -0500

Quote
neildarlow
It is not obvious but the auto bed levelling feature uses the port assigned to Z_MIN_PIN in pins.h.

For a standard Mendel90, which homes upwards, this will not be already defined. You will need to assign the required pin.

Hi, read the whole day for finding the right pin to connect my z-probe with your firmware. I have a nophead mendel 90 with the melzi board. I connected a bed fan to the board like shown here

[blog.seidel-philipp.de]

As you stated before i have to define z_pin_min in pins.h. So i looked into Configuration.h. Melzi is board 63. In your pins.h melzi definitions are from line 1207 to 1210.
So i looked into the pinout from JP16 in the melzi cuircuit from here [reprap.org].
Which is the correct number to use for the z-probe. I dont understand the connection from the pin number on the cuircuit to the pin number i have to define.

So for example. If i want to connect the Z-probe to JP16- Pin 2 (FXT A1), what is the corresponding line to add to pins.h

Thx
Wolfgang

Re: Updated Marlin customized for Mendel90

neildarlow — Wed, 16 Dec 2015 17:10:57 -0500

My guess is that you set the pin under the wrong motherboard stanza. You need to follow the motherboard definition from Configuration.h into pins.h and locate which one to change.

Re: Updated Marlin customized for Mendel90

miharix — Wed, 16 Dec 2015 15:56:39 -0500

Still no luck. :(

I did this:
[pins.h]
Under line 1208: #ifdef MELZI
commented out line 1210: //#define FAN_PIN 4
added line: #define Z_MIN_PIN 4
I do use fan, but I did this just to make for simpler first testing.

[Configuration.h]
uncommented line 399: #define ENABLE_AUTO_BED_LEVELING

But when I run compile I get:
#error "You must have a Z_MIN endstop in order to enable Auto bed Leveling feature!!! Z_MIN_PIN must point to a valid hardware pin."

It's like somewhere down the code it's resetting the Z_MIN_PIN (the DISABLE_MIN_ENDPOINTS are commented out), but for now I didn't found it where.

Re: Updated Marlin customized for Mendel90

neildarlow — Mon, 14 Dec 2015 05:47:02 -0500

It is not obvious but the auto bed levelling feature uses the port assigned to Z_MIN_PIN in pins.h.

For a standard Mendel90, which homes upwards, this will not be already defined. You will need to assign the required pin.

Re: Updated Marlin customized for Mendel90

miharix — Sun, 13 Dec 2015 16:51:18 -0500

But where in the code, do I define the probe port?

Re: Updated Marlin customized for Mendel90

neildarlow — Sun, 13 Dec 2015 15:30:17 -0500

If you get the Melzi circuit schematic from the reprap.org wiki you can determine which pin to use.

The port associated with P27 has a LED attached to it so that one is not available. If you have the chassis fan fitted you may have used the port associated with P28 for that.

There are two more ports available if you are not using a Panelolu2 or other I2C-interfaced LCD panel. You will need to determine which to use for yourself.