Timeline for GRBL with low feed rate not working
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4, 2021 at 23:51 | comment | added | Nick Wallace | @dotswe - Thanks. I didn't adjust the acceleration to see what difference it would make. I did notice that a G-code that has more points in the circle would support a lower speed. I have also done trials with more laps and faster - and it can work. It is slower overall though - and at the speed I'm trying it's already very slow. More laps on acrylic doesn't seem to give a cleaner cut either - it does make a difference on wood. | |
| May 3, 2021 at 1:09 | comment | added | dotswe | Two thoughts; I have noticed problems with Marlin2 and really low acceleration. There are probably limitations. Going more laps at higher speed might help creating nicer cuts, because the surrounding material is not heated as much. | |
| May 2, 2021 at 11:40 | comment | added | Nick Wallace | I guessed a minimum feed rate because it is a very low rate and if the intention is to move smoothly between two positions at a slow rate there are only so many steps between them. If the speed is too slow, the steps will become jumps. Also, if it was the firmware, then why did it work with the same firmware and different stepper drivers (that support finer microstepping)? | |
| Apr 30, 2021 at 22:49 | comment | added | R.. GitHub STOP HELPING ICE | This doesn't sound plausible. There is no such thing as a minimum step rate for a driver. The whole point of steppers is being able to arbitrarily position them. It's likely the firmware just has a minimum feedrate set, wrongly. | |
| Apr 30, 2021 at 14:31 | history | answered | Nick Wallace | CC BY-SA 4.0 |