[gnea/grbl Issue#730] Increase Spindle Dwell Time

未分类 bolang 6个月前 (10-14) 57次浏览

Issue #730 | 状态: 进行中 | 作者: adammhaile | 创建时间: 2019-09-20


Without actually inserting a dwell command into the gcode is there any way to in firmware increase the amount of time it waits after an M3 Sxxxx command?
I’m using firmware modified to control a servo with M3/M5 commands and it mostly works but it barely hits the paper when it starts moving again.


评论 (9)

#1 – neilferreri 于 2019-09-20

What modified firmware? Doesn’t the S value set the rotation angle of the servo?


#2 – adammhaile 于 2019-09-20

I cobbled it together from a couple. Cprezzi and some others.
You are right but I want there to be more time between hitting the paper
and starting toove again. It’s missing bits of lines

On Thu, Sep 19, 2019, 20:28 neilferreri wrote:

> What modified firmware? Doesn’t the S value set the rotation angle of the
> servo?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/gnea/grbl/issues/730?emailsource=notifications&emailtoken=AAHJV2T4GCOIRM56XAEX3V3QKQKLXA5CNFSM4IYRGVZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7FGCJQ#issuecomment-533356838>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAHJV2UGZ6NSDRGMHF4NSE3QKQKLXANCNFSM4IYRGVZA>
> .
>


#3 – neilferreri 于 2019-09-20

How are you generating the gcode? I’d think that’s where the G4 would come from. Grbl just interprets it.


#4 – adammhaile 于 2019-09-20

I’m using LightBurn which is meant for lasers and it doesn’t include G4 or
have any way to include it.
Really what I’m trying to do here is figure out how to set this up without
having to do any special gcode. Maybe it’s not possible….

On Thu, Sep 19, 2019 at 8:37 PM neilferreri
wrote:

> How are you generating the gcode? I’d think that’s where the G4 would come
> from. Grbl just interprets it.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/gnea/grbl/issues/730?emailsource=notifications&emailtoken=AAHJV2TXEEZ57OGYR5ADWGDQKQLLJA5CNFSM4IYRGVZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7FGNRY#issuecomment-533358279>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAHJV2UNO3VI6LTEMDIKUBTQKQLLJANCNFSM4IYRGVZA>
> .
>


#5 – phil-barrett 于 2019-09-22

No prost processor with Lightburn? You could use a stream editor like SED to insert your G4s after the S commands. It’s an extra step but at least you don’t have to manually edit the g-code file. Honestly modding grbl for this isn’t a very good idea.


#6 – adammhaile 于 2019-09-22

It’s on the long term desired feature list for LightBurn but would be a
long way off. And as noted earlier, I’m mainly just curious in finding if
it’s possible to “solve” the problem in firmware.
I’ve looked through the code but can’t really figure out how it determines
the spindle start up delay.

On Sun, Sep 22, 2019 at 12:53 PM phil-barrett
wrote:

> No prost processor with Lightburn? You could use a stream editor like SED
> to insert your G4s after the S commands. It’s an extra step but at least
> you don’t have to physically edit the g-code file.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/gnea/grbl/issues/730?emailsource=notifications&emailtoken=AAHJV2VPLZPBQQPF5YDCXR3QK6PHNA5CNFSM4IYRGVZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7JKHCQ#issuecomment-533898122>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAHJV2XDBWWWG7YFLE2FTA3QK6PHNANCNFSM4IYRGVZA>
> .
>


#7 – mike-pittelko 于 2019-10-06

It’s certainly possible to solve in firmware, and is in the SuperGerbil version of grbl 1.1 as a $ setting for spindle spin up delay. I think the default is already 1+ seconds, so sort of depends on what you’re doing. If I remember, lightburn supports “overscan” which can be used to help this too.


#8 – adammhaile 于 2019-10-07

Do you know where in regular grbl I could add this?

On Sun, Oct 6, 2019 at 7:33 PM mike-pittelko
wrote:

> It’s certainly possible to solve in firmware, and is in the SuperGerbil
> version of grbl 1.1 as a $ setting for spindle spin up delay. I think the
> default is already 1+ seconds, so sort of depends on what you’re doing. If
> I remember, lightburn supports “overscan” which can be used to help this
> too.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/gnea/grbl/issues/730?emailsource=notifications&emailtoken=AAHJV2VOMRA63EXIGI5T55TQNJYVNA5CNFSM4IYRGVZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOW5MA#issuecomment-538799792>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAHJV2VFBDY2JCTJIY32J7LQNJYVNANCNFSM4IYRGVZA>
> .
>


#9 – mike-pittelko 于 2019-10-07

not offhand, but I’d suggest looking at this to see what they did: https://github.com/paulusjacobus/SuperGerbil


原始Issue: https://github.com/gnea/grbl/issues/730

喜欢 (0)