Acceleration Settings

[sstantz]

Put it in an "Expert Mode" if you have to, with a warning that changing the settings could result in undesirable results and printer damage.

But, I want Acceleration settings. Changing eeprom or reflashing firmware is not practical for tuning these settings, especially when a particular part can benefit from a custom accel, nor does it allow the control of slicing-software-defined parameters

[jimc]

generally you just put it in your start script. add this line

M201 X1000 Y1000

default for marlin is usually 3000 for x and y. i turn mine down to 1000. with this in the start script it will be loaded when you run your print and will be saved with that process. now you can have specific settings for each profile or print.

[sstantz]

I'm well aware of the G-Code command. Unfortunately, that does not produce the desired effect at all.

In Slic3r, they have a whole section for accelerations under the speed settings in expert mode.
It allows you to have different acceleration settings for perimeters, infill, bridges, first layer, etc.

I realize I wasn't clear in my first post about the limitations I'm concerned about.

[3D Seed BARCELONA]

I agree... we use Repetier when we do big parts ( 700mm cubic) because I can't get the acceleration to work in Simplify 3d... PLEASE... in the next release?

[slipstick]

Have these been added? My Printrbot Simple Metal was jerking around quite a bit until I reduced the print speed.

[CompoundCarl]

Acceleration is set in the firmware. It's already supported. Either edit the config file for your firmware or use the GCode commands to change and save the settings to the EEPROM. Some users also just add a single GCode command to their starting script to change the acceleration settings, which also works, but I prefer to just permanently save these changes to the firmware.

[Caall99]

Acceleration plugin should be a capability of S3D. Cura has it, and its a no brainer this day in age when printers are still using anemic 8 bit microcontrollers. There shouldn't have to be a firmware acceleration planner... instead the slicer should be able to compute accelerated moves and output them in the gcode for the printer controller to simply parse through....

I +1 this....

[dorsai3d]

Acceleration plugin should be a capability of S3D. Cura has it, and its a no brainer this day in age when printers are still using anemic 8 bit microcontrollers. There shouldn't have to be a firmware acceleration planner... instead the slicer should be able to compute accelerated moves and output them in the gcode for the printer controller to simply parse through....

That's really not how gcode or acceleration commands work. Like, at all...


But you can get the acceleration changed for different features if you really want. Just use the firmware commands in conjunction with the REPLACE postprocessing commands. Something like this, but with the accel values you want:

{REPLACE "; raft" "M201 X1000 Y1000\n; raft"}
{REPLACE "; skirt" "M201 X1000 Y1000\n; skirt"}
{REPLACE "; infill" "M201 X1000 Y1000\n; infill"}
{REPLACE "; support" "M201 X1000 Y1000\n; support"}
{REPLACE "; gap fill" "M201 X1000 Y1000\n; gap fill"}
{REPLACE "; solid layer" "M201 X1000 Y1000\n; solid layer"}
{REPLACE "; inner perimeter" "M201 X1000 Y1000\n; inner perimeter"}
{REPLACE "; outer perimeter" "M201 X1000 Y1000\n; outer perimeter"}

[Caall99]

I wouldn't know how to do this in Sailfish firmware... Accelerated "planning" should be done by the slicer, not the printer hardware.

[dorsai3d]

Because sailfish doesn't really let you modify the acceleration on the fly, from what I can tell. Sailfish firmware handles acceleration in its motion planner as well, but the acceleration values are set in EEPROM and not really meant to be changed on the fly. See: http://www.sailfishfirmware.com/doc/par ... x18-560011

Acceleration is always handled by the motion planner on a machine. There's no good representation of accelerated motion in gcode or x3g files. Slicers are for creating paths, not executing them. Acceleration and motion planning is pretty much explicitly the job of the firmware.