Solved Waves on around holes

Look here for
Vibrations and Ringing:

https://www.simplify3d.com/support/print-quality-troubleshooting/



(P.S. on the Robo it is usually acceleration -- the firmware has those numbers in the stupid zone by default)

 

Same as described in there -- edit the firmware to change the default configuration
Lower it (by a lot). The default was 9000 -- start at most with say 3000.

http://community.robo3d.com/index.p...ate-and-edit-robo-firmware-with-arduino.5227/


If you have an R1+ clear the flash eprom as well after editing/reloading the firmware. In a GCode terminal do the M502 and then an M500.

 

If you do not want to edit the firmware or can't edit it for whatever reason, a less permanent way to do this would be to restrict acceleration values in g-code, either using a terminal window from host software connected to your printer or put it in your startup g-code from your slicer. Acceleration numbers are placed in an M201 g-code. http://reprap.org/wiki/G-code#M201:_Set_max_printing_acceleration

 

Yes.

 

literally anything from 0 -> 9000
you need to experiment and see which ones work best for you.
Earlier in the thread I had suggestions: http://community.robo3d.com/index.php?threads/waves-on-around-holes.19389/#post-116241

 

Personally I believe 3000 is still too much, but try it and see. There will be a physical limit to just how fast it can accelerate. that will be different for every machine. I think I had my R1 set around 1000, for X and Y and 500 for Z, E doesn't really matter as much.

 

Wrong spot, it must be before the semi-colon. If it is after the g-code interpreter treats it as a comment and not an executable command.

 

Still after the semicolon.
Notice how everything else in there has the GCode followed by a semi-colon?

It should end like this:

...
G29;
M201 X1000 Y1000 Z500 E2000;


because ANYTHING you have after a semi-colon on a given line is ignored.