Re: following error problems

[Ray Henry <rehenry-at-up.net>]

Jason

For you folk that use that funny number system, we really should figure 
out a way to make Ferror and Min-Ferror responsive to the units used.  

For backplot to show green, the interpreter is supposed to be using a g0. 
You may also get some funny colors on some of the older releases if you 
use % to open and close a file.  Red and blue colors are supposed to 
represent g2 and g3.  There is nothing in there that responds to m3, m4, 
or m5, but it would be possible to do that with a bit of recoding.  If 
so, there are a few other commands that will turn off the spindle.

These line colors are not an exact thing.  As a matter of fact, they will 
get screwed up if you are doing contouring with very small arcs.  We 
parse the active line at the start of each plot computation and look for 
a change in movement type and change color to match.  

I'll post a couple of possible fixes to you off line if you send a 
message to my email and tell me what gui you are using and how you start 
the backplot.

Ray

On Thursday 16 January 2003 01:31 am, you wrote:
> thanks Ray
>  turns out that it was the FERROR  and MIN_FERROR that were the source
> of the problems.
>
> One more question: how do I setup backplot so that the colours change
> acording to spindel motor on/off /reverse state as I mill PCB's and its
> hard to see green aginst yellow ?
>
>
> thanks
> Jason Cox
>
> On Thu, 2003-01-16 at 06:33, Ray Henry wrote:
> > Hi Jason
> >
> > Sorry to take so long to get back to you.  I've been wrestling with a
> > Mazak spindle motor and drive.
> >
> > This is a rather common complaint with freqmod.  It can be caused by
> > one of several things.
> >
> > One is a metric definition for the units variable.  To fix this you
> > need to multiply the following error values by 25.4.
> >
> > Another is the default acceleration of 20.  Set this back to 5 or
> > less and then set max_velocity in [TRAJ] a bit higher than you set it
> > for the same variable name in any axis definition.  What happens is
> > that during acceleration some steps get put into following error and
> > don't get a chance to be fed back into the running axis.
> >
> > A third problem can be the P parameter.  I'd start with this around
> > 300 and then shift up or down depending on how a real motor sounds. 
> > If you don't have a motor connected you can set it as high as you
> > like.
> >
> > Hope this helps.
> >
> > Ray
> >
> > On Wednesday 15 January 2003 02:25 am, you wrote:
> > > hi all,
> > > 	finaly got all the hardware up for my axis's. all 3 are stepper
> > > motors and and operate correctly.
> > > The system is a 1.2GHz Duron with MDK9.0 (2.4.19-16mdk) with RTAI
> > > 24.1.10 ( I've got a patch if you need ?).
> > > The Problem is that it will run fine in a positve direction but
> > > running back to Y0 causes a following error. Is it just more
> > > tuneing ?
> > >
> > > also has anyone got a patch to direct the IO_BASE_ADDRESS to a
> > > device so that I could experiment with USB2.0 ?
> > >
> > > Thanks
> > > Jason Cox