New milling strategy

Tonight I tried a new milling strategy for the final contour cut of my aluminum plate.
Instead of cutting the entire plate with .2mm depth cuts, I cut first 2mm at .2mm depth cuts, and then switched the depth cuts to .25mm

The cutting feed speed was set to 330mm/minute, but I suspect that GRBL is gating the feed speed.

Third successful aluminum run

I milled the third of four plates that I'll need for upgrading the CNC router to use the larger extrusions. I milled with the Niagara bit, 300 mm/minute feed rate, and .2mm per pass. At some point it lost a few steps doing the final contour cut. It also had to be cut down to 7.25mm, and even then didn't make it all the way through --- even though the aluminum is only 6.25mm thick.

This run was the first aluminum run with the X-Controller.

Upgrading to X-controller, GRBL values dump

$0=10 (step pulse, usec)

$1=25 (step idle delay, msec)

$2=0 (step port invert mask:00000000)

$3=3 (dir port invert mask:00000011)

$4=0 (step enable invert, bool)

$5=0 (limit pins invert, bool)

$6=0 (probe pin invert, bool)

$10=3 (status report mask:00000011)

$11=0.010 (junction deviation, mm)

$12=0.002 (arc tolerance, mm)

$13=0 (report inches, bool)

$20=0 (soft limits, bool)

$21=0 (hard limits, bool)

$22=0 (homing cycle, bool)

$23=0 (homing dir invert mask:00000000)

$24=25.000 (homing feed, mm/min)

$25=500.000 (homing seek, mm/min)

$26=250 (homing debounce, msec)

$27=1.000 (homing pull-off, mm)

$100=40.000 (x, step/mm)

$101=40.000 (y, step/mm)

$102=320.000 (z, step/mm)

$110=2000.000 (x max rate, mm/min)

$111=1000.000 (y max rate, mm/min)

$112=500.000 (z max rate, mm/min)

$120=10.000 (x accel, mm/sec^2)

$121=10.000 (y accel, mm/sec^2)

$122=10.000 (z accel, mm/sec^2)

$130=200.000 (x max travel, mm)

$131=200.000 (y max travel, mm)

$132=200.000 (z max travel, mm)

The jumper for the Z-axis is set to 2x microstepping.

You'd think I'd know by now to dump the values before switching to the X-controller, instead of looking them up after figuring out what my Z movement was wrong.

Nope.