# Time to ramp to cutting speed **URL:** \ **Category:** Onefinity Spindle Kit by Redline CNC\ **Created:** [March 26, 2025, 1:36am UTC](https://forum.onefinitycnc.com/t/time-to-ramp-to-cutting-speed/31942 "2025-03-26T01:36:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![NikkiShins](https://avatars.discourse-cdn.com/v4/letter/n/ecc23a/32.png) [@NikkiShins](https://forum.onefinitycnc.com/u/NikkiShins)\ **Post date:** [March 26, 2025, 1:36am UTC](https://forum.onefinitycnc.com/t/time-to-ramp-to-cutting-speed/31942/1 "2025-03-26T01:36:34Z")
I have noticed that when starting a program and leaving the spindle controls on automatic, not enough time is given for the spindle to get up to speed before cutting begins. Essentially, you hit run, the spindle begins to ramp up, and while its still ramping up the machine plunges into the work piece. Is there a way to prevent this? I have thought about setting a macro to ramp up to a generic 16k. Then I would run the program and the speed it set to would take over. But this would almost defeat the purpose of having spindle control baked in. I would have to hit the macro, reselect the program (because macros deselect the selected program), then run it. I have also thought about editing the “on program start” G-Code in the settings to do the same thing. It would run two lines of g-code, one to start the spindle at 16k, one to wait 5 seconds, THEN the rest of the program would run. However this would start the spindle up whenever I use my “travel to X location” macros. My current “fix” is to jog the spindle as far from the entry point as I can before running it, that way by the time it travels back where it needs to be, it’s gotten close enough to speed to not break the bit. All I can think of now would be to edit the Post library in Fusion to add those two lines. But that’s above my know-how. Any other ideas? I’m running a BB model with Fusion. ---
**Author:** ![avacado](https://avatars.discourse-cdn.com/v4/letter/a/e47774/32.png) [@avacado](https://forum.onefinitycnc.com/u/avacado)\ **Post date:** [March 26, 2025, 2:00am UTC](https://forum.onefinitycnc.com/t/time-to-ramp-to-cutting-speed/31942/2 "2025-03-26T02:00:38Z")
Read this thread: > [@Delay between the start of the spindle and the start of work](https://forum.onefinitycnc.com/t/delay-between-the-start-of-the-spindle-and-the-start-of-work/19977): > > Hello everybody. I finished installing my new spindle today and I tested it. Everything is OK I realize that the work starts at the same time as the spindle. I would like the work to start only when the spindle has reached its working speed. Is it possible? Now I press play to start, pause for the spindle to go up to its working speed and play again to start the job. I know that you can modify certain startup parameters on a recurrent basis. I thought there was probably a solution here. … ---
**Author:** ![xenith](https://avatars.discourse-cdn.com/v4/letter/x/a3d4f5/32.png) [@xenith](https://forum.onefinitycnc.com/u/xenith)\ **Post date:** [March 26, 2025, 2:01am UTC](https://forum.onefinitycnc.com/t/time-to-ramp-to-cutting-speed/31942/3 "2025-03-26T02:01:54Z")
I’m pretty sure that the community maintained fusion360 postprocessors [here](https://github.com/blaghislain/onefinity-post-processors) have a spindle pause option to address that issue. You should see the option during the post process step in fusion once you have the right postprocessor selected. ---
**Author:** ![poppyscott](https://avatars.discourse-cdn.com/v4/letter/p/a587f6/32.png) [@poppyscott](https://forum.onefinitycnc.com/u/poppyscott)\ **Post date:** [March 26, 2025, 2:20am UTC](https://forum.onefinitycnc.com/t/time-to-ramp-to-cutting-speed/31942/4 "2025-03-26T02:20:57Z")
You can tell Masso how many saconds to wait for the Spindle to come up to speed. ---
**Author:** ![NikkiShins](https://avatars.discourse-cdn.com/v4/letter/n/ecc23a/32.png) [@NikkiShins](https://forum.onefinitycnc.com/u/NikkiShins)\ **Post date:** [March 26, 2025, 7:50am UTC](https://forum.onefinitycnc.com/t/time-to-ramp-to-cutting-speed/31942/5 "2025-03-26T07:50:04Z")
Avacado, that thread seems to go over the same fix I found as well; editing the “On Program Start” g-code. Definitely a doable solution if I didn’t use macros. But rad, xenith! That looks like exactly what I need, I didn’t know this existed