search

MarlinFirmware / Marlin

Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.
https://marlinfw.org
GNU General Public License v3.0
16.29k stars 19.24k forks source link

G0 on Z without specified Feedrate #5503

Closed martindb closed 7 years ago

martindb commented 7 years ago

The mpcnc project uses Marlin as the firmware to run this CNC multitool machine. There are users that generate their g-code with estlcam software, and this g-code use G0 without feedrate specified in the first lines of the programs. We were using Marlin 1.1.0-RC7 without problems.

With RC8, Arduino starts to reset when executing the G0 over Z. If you put a feedrate on those first moves, all is working.

Does Marlin have to limit these movements as specified in default_max_feedrate for each axis, in particular for Z?

thinkyhead commented 7 years ago

The reset may be due to the Z axis failing to move, or trying to move too quickly and eating up all the CPU.

The speed of the Z axis should be constrained by the max feedrate (DEFAULT_MAX_FEEDRATE) and max acceleration (DEFAULT_MAX_ACCELERATION) values for the Z axis, which prevent it from moving or accelerating at excessive rates. But it's possible the acceleration and jerk behave differently enough in RC8 that your settings need to be adjusted.

I suggest you start by cutting the DEFAULT_ZJERK value in half (use M205 Z or the LCD controller). If that doesn't fix the issue, try setting lower max feedrate (M203 Z or the LCD) and max acceleration (M201 Z or the LCD) until the problem goes away.

If you find values that work, save them to EEPROM with M500 and set them as your DEFAULT_MAX_FEEDRATE and DEFAULT_MAX_ACCELERATION values for Z.

HTH

martindb commented 7 years ago

Thanks! I've lowered DEFAULT_MAX_FEEDRATE for Z and no more resets with G0 without explicit feedrate.

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.