dave wrote:
> Tuning linuxcnc come up time and again. As far as I can tell it is still
> an art. I keep hoping someone with the requisite brights will write a
> usable diagnostic that gives us a bode plot and then tell us what to do
> with it. I certainly can't do it. Zu hilfe! Zu hilfe! Zu hilfe!
On Sunday 09 December 2012 21:53:04 andy pugh did opine:
> On 10 December 2012 01:26, Gene Heskett wrote:
> >> Not in your case, as encoder velocity is the controlled quantity, not
> >> the derivative thereof.
> >>
> >> encoder.velocity is only an appropriate feedback-deriv term in a
> >> positi
On Sunday 09 December 2012 21:36:51 Jon Elson did opine:
> Gene Heskett wrote:
> > Should I be able to induce a rail to rail oscillation with Pgain?
>
> You probably can, but in an actual machine, it would be a VERY bad thing
> to do! Fine for a simulation exercise, but it is likely to cause
> d
On 10 December 2012 01:26, Gene Heskett wrote:
>> Not in your case, as encoder velocity is the controlled quantity, not
>> the derivative thereof.
>>
>> encoder.velocity is only an appropriate feedback-deriv term in a
>> position loop.
>
> But this is not a position loop per sei, its a velocity l
On Sun, 2012-12-09 at 19:43 -0600, Jon Elson wrote:
> Gene Heskett wrote:
> > Should I be able to induce a rail to rail oscillation with Pgain?
> >
> You probably can, but in an actual machine, it would be a VERY bad thing
> to do! Fine for a simulation exercise, but it is likely to cause damag
Gene Heskett wrote:
> Should I be able to induce a rail to rail oscillation with Pgain?
>
You probably can, but in an actual machine, it would be a VERY bad thing
to do! Fine for a simulation exercise, but it is likely to cause damage,
perhaps permanent damage to mechanical parts.
Jon
--
On Sun, 2012-12-09 at 20:26 -0500, Gene Heskett wrote:
> On Sunday 09 December 2012 20:19:59 andy pugh did opine:
>
> > On 10 December 2012 00:40, Gene Heskett wrote:
> > > I can't make Pgain cause more than about a 10% of that range cyclic
> > > wibble, not near enough to hear it with the spindl
On Sunday 09 December 2012 20:19:59 andy pugh did opine:
> On 10 December 2012 00:40, Gene Heskett wrote:
> > I can't make Pgain cause more than about a 10% of that range cyclic
> > wibble, not near enough to hear it with the spindle at say 6 rps
> > commanded. At least at Pgains up to 150 or so
On 10 December 2012 00:40, Gene Heskett wrote:
> I can't make Pgain cause more than about a 10% of that range cyclic wibble,
> not near enough to hear it with the spindle at say 6 rps commanded. At
> least at Pgains up to 150 or so, with FF0 = 100, FF1 = 20 and FF2 = 10.
What makes you think th
Greetings;
I haven't tried this method yet, primarily because when it says its
supposed to oscillate, I would assume it is meaning a runaway, and will be
limited by the rail to rail range of the control at pid.N.out.
I can't make Pgain cause more than about a 10% of that range cyclic wibble,
n
I seem to remember promising someone I'd do this but I can't find the
incriminating message now.
I've added a Wiki page WhatLatencyTestDoes and linked to if from the
LatencyTest page.
On this page I tried to outline what the current latency-test does, how
it does it, and how it is invoked.
If
On Sunday 09 December 2012 17:57:05 Thomas J Powderly did opine:
> On 12/09/2012 08:16 AM, Gene Heskett wrote:
> > On Sunday 09 December 2012 09:06:49 Anders Wallin did opine:
> >>> Do we have a utility that can plot all the paths& connects the
> >>> drawn path with its signal name alongside the
On 12/09/2012 08:16 AM, Gene Heskett wrote:
> On Sunday 09 December 2012 09:06:49 Anders Wallin did opine:
>
>
>>> Do we have a utility that can plot all the paths& connects the drawn
>>> path with its signal name alongside the path line from logic block to
>>> logic block or I/O pin? A 'logi
On 9 December 2012 11:20, Javier Ros wrote:
> I'm not sure if a Kalman filter woud benefit your setup, but properly
> adjusted surely it can.
The typical approach to this sort of problem in my day-job is a look-up table.
They can approximate any function, and none.
For example, one PID controll
On 12/9/2012 9:16 AM, Gene Heskett wrote:
> It seems to me that
> dead ends & crossed connections would be a lot easier to see in that
> format.
Dead ends are easy to detect in software (it's what my friends in the
process and piping industry calls "free-ends analysis"). A simple
script (does e
On Sunday 09 December 2012 09:26:15 Kent A. Reed did opine:
> On 12/9/2012 7:20 AM, Anders Wallin wrote:
> >> Do we have a utility that can plot all the paths & connects the drawn
> >> path with its signal name alongside the path line from logic block
> >> to logic block or I/O pin? A 'logic' blo
On Sunday 09 December 2012 09:06:49 Anders Wallin did opine:
> > Do we have a utility that can plot all the paths & connects the drawn
> > path with its signal name alongside the path line from logic block to
> > logic block or I/O pin? A 'logic' block being like the pid module
> > for instance,
On 12/9/2012 7:20 AM, Anders Wallin wrote:
>> Do we have a utility that can plot all the paths & connects the drawn path
>> with its signal name alongside the path line from logic block to logic
>> block or I/O pin? A 'logic' block being like the pid module for instance,
>> or encoder, pwngen etc.
> Do we have a utility that can plot all the paths & connects the drawn path
> with its signal name alongside the path line from logic block to logic
> block or I/O pin? A 'logic' block being like the pid module for instance,
> or encoder, pwngen etc. I looked at halitosis, but that isn't the out
Gene,
I'm not sure if a Kalman filter woud benefit your setup, but properly
adjusted surely it can. If you are interested on such a setup I can try to
work out a model that gives you a Kalman filtered output. And from it
developing a comp module should be trivial.
It can be interesting for my own
20 matches
Mail list logo
