People told me this and I didn't believe them until I really got in the weeds of killing cycle time on long runs: These things are so fucking fast that you can spend hours or days hand tweaking a program with no air time, no retracts, High Accuracy codes all over the place, be all proud of yourself, run the program and save 3 seconds of cycle time. You can be sloppy with Brother programs and not be hurt bad at all, time wise.
Aside from the obvious palaces everyone turns to to find time - lead in/out reduction, minimize retractions, none of this business where the drill starts half an inch above making contact with the material - the two places to find time in a Speedio are:
1- Using G100
properly. The number of times I see a tool retract, stop, coolant turns off, spindle turns off, then it accelerates back up to change. Conversely, tools that stop on approach to set offsets, turn on coolant, etc etc. G100 handles everything and to work properly, you need to let it. As soon as the tool comes out of contact with the material? G100 to the next tool - don't even retract to the operation clearance plane, just go. No fiddle fucking with G40 or coolant off codes. Let G100 do what G100 does. Also, call all the stuff you would do on approach in G100 - coolant, G43, work offset.
So many people are giving up at least a second on their total tool-change cycle by not using G100 properly.
2- High Accuracy modes. I recently got schooled by an old project that I worked on that the customer had put on the back shelf due to COVID. They came back to it and had their excellent inside guy program it, but they still wanted a bit more time. Compared notes, got the latest code (with no HA applied), added my usual M298 bits where I would normally put them and... My code was like 30 seconds slower on a ~2 min cycle. WTF?
Turns out, they were just using the M298 Roughing for *everything*, save critical profiles which used Finish. All my fussy accuracy setting and thoughts about what was necessary? Totally out the window, I never even thought about trying the whole thing in Rough and seeing what would happen. Lesson learned - on jobs where you are really dialing in, throw away your standard High Accuracy defaults and work backwards. Default to keeping everything wide open, then selectively apply the minimum HA code required to bring the part into the desired results.