Re: [Emc-developers] Hardware testing for improved spindle tracking jitter (issue 164)

On 29 September 2016 at 02:35, Robert Ellenberg wrote: > That would certainly be convenient. What if we took it one step further and > automatically limit the maximum spindle speed for each G33 segment? > > If like me, they have a gea

Re: [Emc-developers] Hardware testing for improved spindle tracking jitter (issue 164)

That would certainly be convenient. What if we took it one step further and automatically limit the maximum spindle speed for each G33 segment? It would be ugly, but we may be able to stuff a spindle speed command into the queue before adding the line segment. Combined with a message to the user th

Re: [Emc-developers] Hardware testing for improved spindle tracking jitter (issue 164)

On 29 September 2016 at 01:51, Robert Ellenberg wrote: > > Ideally, I'd like to have the interpreter catch the error, so that we get > as much advance warning as possible. Doing so is a bit tricky, because the > error condition happens fairly deep within canon. This means either > throwing an ex

Re: [Emc-developers] Hardware testing for improved spindle tracking jitter (issue 164)

On Wed, Sep 28, 2016 at 8:41 PM andy pugh wrote: > On 29 September 2016 at 01:36, andy pugh wrote: > > > > > I approve of this warning, definitely. > > Given that (as far as I can guess) nobody ever prefers to make a bad > > thread than no thread, could the warning abort all motion? > > > > (Sup

Re: [Emc-developers] Hardware testing for improved spindle tracking jitter (issue 164)

On 29 September 2016 at 01:36, andy pugh wrote: > > I approve of this warning, definitely. > Given that (as far as I can guess) nobody ever prefers to make a bad > thread than no thread, could the warning abort all motion? > (Supplementary thought). It's a following error. We abort those hard.

Re: [Emc-developers] Hardware testing for improved spindle tracking jitter (issue 164)

On 29 September 2016 at 01:30, Robert Ellenberg wrote: > This branch also adds a canon-level warning if the user tries to start a > G33 move that isn't capable of reaching the required feed. Unfortunately, > the warning only appears when the motion starts, but it's better than > nothing. > I app

Re: [Emc-developers] Hardware testing for improved spindle tracking jitter (issue 164)

Update: I've combined my fix for Issue 68 with the jitter improvement in this branch (also pushed to the official repo for the buildbot): https://github.com/robEllenberg/linuxcnc-mirror/tree/feature/nominal-vel-during-sync This branch also adds a c