Re: BDI 2.12 & A axis

[Paul <paul.corner-at-tesco.net>]

Hi Tim

In response to your first question - I have some notes on this issue, but 
can't for the ** remember where they are...
 As I understand the problem, if an interpolated move is commanded using A 
and EMC thinks the cutter tip is on or near the centerline of A, an extreme 
rotational velocity is often calculated. There is some comments buried in the 
sources somewhere on this subject - I'll have to dig it out sometime.
The fix is to use a very low feed rate when the cutter tip is close to the 
centerline of the rotary axis. i.e. If you normally use F75, drop to F5 and 
see if the following error disappears.

On the second question - Switch to Auto, select World, and then switch back 
to Manual. This "quirk" is due to changes needed for hexapod support that 
have yet to be made in steppermod.

BTW One bug I've noticed with four or more axis - Switching between 
Metric-Imperial the conversion is applied to the rotary axis as wel as the 
linear !

Regards, Paul.


On Monday 04 Mar 2002 6:57 pm, Tim Goldstein wrote:
> I just loaded up BDI 2.12 to again try and get 4 axis running reliably. It
> is on a test PII 233 system. I edited the .ini file to add the additional
> axis and with Freqmod.o tkemc comes up properly with the A axis as desired.
> If I jog the axis or do g1 moves on the A axis all seems fine. As soon as I
> try to run a program in auto mode I get a follow error on axis 3 (A axis).
> I have tried reducing the feed rate, lowering the acceleration, increasing
> the P value and I still get the error in auto mode. Any ideas?
>
> Second question, If I switch to steppermod.o tkemc comes up with 4 axes
> displayed, but they are labeled in joint not world and I can not get them
> to switch. I would really rather use steppermod.o on my 4 axis setup as I
> am running Gecko G320 step and direction servos and steppermod.o seems to
> work much better in that application.
>
> Tim
> [Denver, CO]