So I stripped all the F values from the GCODE generated by LaserWeb3, set an initial F30000 value & tested to see if it would do this image faster than the previous 2.5 hours. Imported the .gcode file into LaserWeb & ran again. After 45 minutes, it was only about 17% completed, so calculating at the same speed it had been going it was looking like it was going to take 4 hours total.

So, seems that doesn't fix my issue with speed of engraves. Still no idea what is causing the slowness. There is no way it is going at 500mm/s (which is what it should be).

The engrave quality seemed about the same as when I used the LaserWeb3 generated GCODE (containing varying F values).

My smoothie config has:

default_feed_rate 4000 # Default rate ( mm/minute ) for G1/G2/G3 moves
default_seek_rate 4000 # Default rate ( mm/minute ) for G0 moves

acceleration 3000 # Acceleration in mm/second/second.
acceleration_ticks_per_second 1000 # Number of times per second the speed is updated

x_axis_max_speed 60000 # mm/min
y_axis_max_speed 30000 # mm/min

alpha_max_rate 60000.0 # mm/min
beta_max_rate 30000.0 # mm/min



Note: I've sped up a section of the video in the middle otherwise it would be 45 minutes worth.

Also note: You may notice that the head carriage is not as jerky as previous test of this same job, so maybe having a fixed F value is better for the jerk? Or maybe I'm imagining it.

свернуть