Max feedrate ignored

[pjfossee]

I'm not quite sure what's going on with my printer. I've had quite a few issues with it recently, but sorted all of them out. They were almost all my fault, and I suppose this one probably is too. All my axes move perfectly when I'm moving them in pronterface. However, when I execute g code, my z axis starts buzzing and does not move. It starts buzzing on the bolded move in the Cura start g-code:

M190 S110.000000
M109 S230.000000
;Sliced at: Fri 19-02-2016 19:36:57
;Basic settings: Layer height: 0.2 Walls: 0.8 Fill: 20
;Print time: 2 hours 0 minutes
;Filament used: 7.489m 22.0g
;Filament cost: 0.49
;M190 S110 ;Uncomment to add your own bed temperature line
;M109 S230 ;Uncomment to add your own temperature line
G21 ;metric values
G90 ;absolute positioning
M82 ;set extruder to absolute mode
M107 ;start with the fan off
G28 X0 Y0 ;move X/Y to min endstops
G28 Z0 ;move Z to min endstops
G1 Z15.0 F6000 ;move the platform down 15mm
G92 E0 ;zero the extruded length
G1 F200 E3 ;extrude 3mm of feed stock
G92 E0 ;zero the extruded length again
G1 F6000
;Put printing message on LCD screen
M117 Printing...


That speed is obviously way too much for the z axis to handle, but if I'm not mistaken, the firmware's max-feedrate setting is supposed to override that. In the past, this move has never been an issue. But for some reason now it is. When I enter that piece of code directly into pronterface, the same problem occurs. Why do you think I would be having this issue all of the sudden? Thanks

Also, here is my configuration.h. It is straight from makerfarm.
#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__ " 8-24-14 " __TIME__ // build date and time
#define STRING_CONFIG_H_AUTHOR "(Maker Farm Inc, i3v Prusa)" //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 (Power outputs: Extruder, Bed, Fan)
// 34 = RAMPS 1.3 (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
// 7 = Ultimaker
// 71 = Ultimaker (Older electronics. Pre 1.5.4. This is rare)
// 8 = Teensylu
// 81 = Printrboard (AT90USB1286)
// 82 = Brainwave (AT90USB646)
// 9 = Gen3+
// 70 = Megatronics
// 90 = Alpha OMCA board
// 91 = Final OMCA board
// 301 = Rambo


#ifndef MOTHERBOARD
#define MOTHERBOARD 33
#endif


//// 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 5
#define TEMP_SENSOR_1 0
#define TEMP_SENSOR_2 0
#define TEMP_SENSOR_BED 6


// Actual temperature must be close to target for this long before M109 returns success
#define TEMP_RESIDENCY_TIME 10 // (seconds)
#define TEMP_HYSTERESIS 3 // (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 280
#define HEATER_1_MAXTEMP 235
#define HEATER_2_MAXTEMP 235
#define BED_MAXTEMP 125


// 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 PID_MAX 256 // limits current to nozzle; 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 22.2
#define DEFAULT_Ki 1.08
#define DEFAULT_Kd 114


// 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 ferquency 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 true // 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 false // 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 false //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 300
#define X_MIN_POS 0
#define Y_MAX_POS 300
#define Y_MIN_POS 0
#define Z_MAX_POS 300
#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 0
#define MANUAL_Y_HOME_POS 0
#define MANUAL_Z_HOME_POS 0


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


// default settings


#define DEFAULT_AXIS_STEPS_PER_UNIT {80,80,4000,841} // default steps per unit for ultimaker {78.7402,78.7402,200*8/3,760*1.1}920
#define DEFAULT_MAX_FEEDRATE {250, 250, 2, 22} // (mm/sec)
#define DEFAULT_MAX_ACCELERATION {1000,1000,5,1000} // 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 500 // X, Y, Z and E max acceleration in mm/s^2 for printing moves
#define DEFAULT_RETRACT_ACCELERATION 500 // 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 20.0 // (mm/sec)
#define DEFAULT_ZJERK 0.4 // (mm/sec)
#define DEFAULT_EJERK 5.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


//LCD and SD support
//#define ULTRA_LCD //general lcd support, also 16x2
//#define SDSUPPORT // Enable SD Card Support in Hardware Console


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


// The RepRapDiscount Smart Controller (white PCB)
// http://reprap.org/wiki/RepRapDiscount_Smart_Controller
#define REPRAP_DISCOUNT_SMART_CONTROLLER


// The GADGETS3D G3D LCD/SD Controller (blue PCB)
// http://reprap.org/wiki/RAMPS_1.3/1.4...eld_with_Panel
//#define G3D_PANEL


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


// 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 225
#define ABS_PREHEAT_HPB_TEMP 100
#define ABS_PREHEAT_FAN_SPEED 255 // Insert Value between 0 and 255




#ifdef ULTIPANEL
// #define NEWPANEL //enable this if you have a click-encoder panel
#define SDSUPPORT
#define ULTRA_LCD
#define LCD_WIDTH 20
#define LCD_HEIGHT 4

#else //no panel but just lcd
#ifdef ULTRA_LCD
#define LCD_WIDTH 16
#define LCD_HEIGHT 2
#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: http://www.doc-diy.net/photo/rc-1_hacked/
// #define PHOTOGRAPH_PIN 23


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


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


#endif //__CONFIGURATION_H

I have modified firmware files but I'm using this one to solve this issue.

[Mjolinor]

Well I am not trawling through all that, maybe someone else will feel inclined to but my suggestion is that your acceleration settings are way too high. It is not about maximum rate, it is about how fast it tries to get there so lower your acceleration right down and see how it performs.

[pjfossee]

Ha, didn't realize how long that post was. Thanks, I'll check it out. I think I tried that a few weeks ago (been at this for a while), but I'll try it again.

[pjfossee]

Changed Z-max acceleration from 5 to 2. Didn't change anything. So that's not it?

[Mjolinor]

Change it to 0.1

[printbus]

However, when I execute g code, my z axis starts buzzing and does not move.

One problem that has led to similar issues in the past is changing obscure settings in the slicer that lead to unexpected gcode commands being sent to the printer. You are correct that the printer firmware will apply a limit check to the DEFAULT firmware values, but those limits can be changed by gcode command. For example, the slicer can send an M203 command to change what you have in the firmware for DEFAULT_MAX_FEEDRATE values. Is the z-axis problem occurring on an archived gcode files you KNOW printed fine before, or with newly created gcode files?

Part of the issue in getting starting gcode working properly is to at least be aware of the fact that the printer is picking up where the last printing action left it. Starting a new gcode file does not perform any kind of master reset on the printer that restores everything back to the original settings. Following the above example, if the printer was for whatever reason sent an M203 command as part of a prior gcode file, those revised max feedrate settings are still there when you later try to execute the startup snippet in pronterface. Power cycle or reset the printer and try the startup snippet again. Does that make a difference?

Weird things can happen with EEPROM settings... If you have EEPROM enabled (which your configuration.h file says you do), how long has it been since you've restored EEPROM to factory default settings?

You can always use the LCD to affirm what the printer thinks its current limit-check values are at any point in time. For at least the 2014-era Marlin I'm familiar with, DEFAULT_MAX_FEEDRATE equates to Vmax x, Vmax y, Vmax z, and Vmax e menu entries on the LCD. When you get the buzzing from trying to raise the x-axis carriage upwards, what does the LCD show for Vmax z? Does it still correlate to what you have in firmware for DEFAULT_MAX_FEEDRATE or something different?

I realize you're likely just trying to understand what's going on, but if you know that the printer can't move 6,000 mm per minute in the z-axis (don't we all wish), don't try setting it to that. Leave the setting at F120 or whatever you think your printer can really do.

EDIT: Mjolinor has a valid point on acceleration, but only to an extent. Especially at the 4000 steps per mm required for the 16-microstep and M5 z-axis rods on a MakerFarm printer, there'll still be a limit on how fast the axis can move. Testing unfortunately demonstrates that the MakerFarm z-axis just can't be driven very fast. I know that 5mm/Sec (F300) wasn't achievable on my machine.

ANOTHER EDIT: To clarify, all the DEFAULT settings you find in Marlin are the settings used by the printer, but only if there isn't a superseding value stored in EEPROM, and even then only until the point where the settings are overridden by LCD user entry or by gcode command. The DEFAULT settings aren't as definitive as most people think they are.

[pjfossee]

Thanks Printbus, you were right. Although I never actually saw what my old eeprom was because my lcd is displaying gibberish (yay!), I downloaded repetier-host and edited the eeprom with it and this problem is solved. Now I have to figure out why my lcd is displaying gibebrish. But you don't really need the lcd to do a print right. I have one I need done very soon, and I'm thinking of just going for it without the lcd. Is that a bad idea?

[pjfossee]

Also, despite the past three weeks, I have not been able to solve my original problem. My hotend temp oscillates within an 8 degree range, which I think is a little abnormal. PID Autotune did not solve the issue. I haven't put much time into this issue because in trying to solve it I created a dozen more issue, but now I'm finally back where I started. I originally tried solving this issue with a new thermistor, but that didn't work. I should also mention that this issue arose when I used a cheap chinese heater cartridge. I put my old one that worked before back in and the issue persisted. I've been through 3 RAMPS boards and 2 duino boards, and I do not think they are the issue, but I could be mistaken.

[pjfossee]

Ok, the oscillations are gone. No idea why, but I'm not asking any questions. Still have the lcd issue though.

[printbus]

Glad to hear you got the z-axis problem straightened out. My response was already quite long, so I held off on the Repetier-Host suggestion for a later post if it was necessary. I haven't used RH for over a year, but I remember the eeprom view built into it being pretty slick.

You are correct that the LCD isn't required for printing. I've known MakerFarm owners who even removed it from their printer. There are non-MakerFarm printers that don't have one to begin with. IMO, running without an LCD is especially possible when running RH as host software. Slicer capabilities drove me to Simplify3D instead of RH/Cura; I still miss the printer control capabilities that were provided by RH.

Can the display gibberish be at least temporarily fixed by restarting or resetting the printer? If it is a permanent problem and this is still an LCD with two ribbon cables, I'd try switching the two ribbon cables going to the display. I don't think crossing the cables can lead to gibberish, but a bad connection on a pin of one cable might. Seeing what happens by switching the cables might help reveal whether there's a cable problem or some other issue.