bdring
bdring
The easiest way to implement this might be to add a single new boolean item: **ramp_on:** with a default of false. If this is true it uses **spinup_ms** for the...
Could the steps be done in a fixed time? Then it could be calculated. Is there a downside to doing short delays?
You already know the total time and the range, therefore you can determine the acceleration. By fixed time, I mean the value changes every 50ms (TBD). You use the other...
If you request a ramp, it uses the **spinup_ms** for the full range ramp duration. It determines an amount per interval that the speed increases in the **init()**. We could...
I don't know that we need to optimize it. If we find a reason, we could do it. It is better than Joe StepStick trying to optimize it.
I have a working branch. The ramp is linear. I think that is what people expect and what VFDs do. People just pick a ramp length that yields the results...
Wow. On my 2.2kW VFD spindle, I have no break, but ramp down in about 6 seconds. If there is a power failure the spindle takes about 30 seconds to...
Can you useoutputs? user ouputs? http://wiki.fluidnc.com/en/config/user_outputs You could implement the pull and hold with gcode delays G4...
This gcode has a pull and hold ```gcode M67 E0 Q100.00 ; pull level 100% G4 P0.1 ; wait 0.1 sec M67 E0 Q50.00 ; hold level 50% ```