On Saturday 20 September 2014 10:57:12 Andy Pugh did opine
And Gene did reply:
> > On 19 Sep 2014, at 22:22, Gene Heskett wrote:
> >
> >
> > s5000 = 1407
> > s1300 = 1366
> > s1200 = 1267
> > s1100 = 1164
> > and it follows a reasonable straight line down to
> > s100 = 112
> > s50 = 60
> >
On 09/20/2014 05:12 AM, Mark Wendt wrote:
... snip
>> Can't help diagnose gedit, can only say that in nigh on a quarter
>> century's use of vi/vim, I've never lost (or doubled up on) a byte
>> through unreliability. There is though, some extra use of undo while
>> getting used to it, as with most u
> On 19 Sep 2014, at 22:22, Gene Heskett wrote:
>
>
> s5000 = 1407
> s1300 = 1366
> s1200 = 1267
> s1100 = 1164
> and it follows a reasonable straight line down to
> s100 = 112
> s50 = 60
> s30 = 40
Are you sure that the pod is working? You should get the number you ask for.
I am a
On Saturday 20 September 2014 00:50:35 Jon Elson did opine
And Gene did reply:
> On 09/19/2014 10:58 PM, Gene Heskett wrote:
> > It has been run, for a day & a half, dead clean but not exactly
> > recently. If geany ever does it, yup on the memtest86 session,
> > instantly. So far, geany has not h
On Fri, Sep 19, 2014 at 11:14 PM, Erik Christiansen wrote:
> On 19.09.14 17:22, Gene Heskett wrote:
> > Has anyone else had a similar problem with gedit? Its a PIMA when it
> > happens, to have to do all that edit, restart lcnc to get the next
> error's
> > line number so you can re-edit and fix
yea iv'e just seen gedit mucking with the files , i wondered where it was
coming from
iv'e started using KATE instead ,, it's also usefull for xml editing too
On 19 September 2014 22:22, Gene Heskett wrote:
> Hi have made a wee bit of progress with the spindle controls on the lathe,
> but lower
On 09/19/2014 10:58 PM, Gene Heskett wrote:
>
> It has been run, for a day & a half, dead clean but not exactly recently.
> If geany ever does it, yup on the memtest86 session, instantly. So far,
> geany has not had any such hiccups.
>
>
I use emacs, which I believe is what is actually running
be
On Friday 19 September 2014 23:14:12 Erik Christiansen did opine
And Gene did reply:
> On 19.09.14 17:22, Gene Heskett wrote:
> > Has anyone else had a similar problem with gedit? Its a PIMA when it
> > happens, to have to do all that edit, restart lcnc to get the next
> > error's line number so y
On Friday 19 September 2014 22:37:16 Jon Elson did opine
And Gene did reply:
> On 09/19/2014 04:22 PM, Gene Heskett wrote:
> > Hi have made a wee bit of progress with the spindle controls on the
> > lathe, but lower speed performance is still sorely lacking.
> >
> > Current pid.s settings
> > Pgai
On 19.09.14 17:22, Gene Heskett wrote:
> Has anyone else had a similar problem with gedit? Its a PIMA when it
> happens, to have to do all that edit, restart lcnc to get the next error's
> line number so you can re-edit and fix it till it will actually run again.
> It can be 20+ minutes to fix
On 09/19/2014 04:22 PM, Gene Heskett wrote:
> Hi have made a wee bit of progress with the spindle controls on the lathe,
> but lower speed performance is still sorely lacking.
>
> Current pid.s settings
> Pgain 125
> Igain .05
> FF0 100
> FF120
>
> maxoutput is set 1% below the pwmgen scale t
Hi have made a wee bit of progress with the spindle controls on the lathe,
but lower speed performance is still sorely lacking.
Current pid.s settings
Pgain 125
Igain .05
FF0 100
FF120
maxoutput is set 1% below the pwmgen scale to keep it from hitting 100%
duty cycle. Since this is a par
12 matches
Mail list logo
