Hello Guest it is December 21, 2024, 07:22:55 AM

Author Topic: Is B and C axis G1 feed rate broken?  (Read 3546 times)

0 Members and 2 Guests are viewing this topic.

Offline simpson36

*
  •  1,369 1,369
Is B and C axis G1 feed rate broken?
« on: July 18, 2012, 08:00:00 AM »
Search turned up nothing useful on this.

Problem:  B axis (C has same behavior) G1 feed rate is dog slow no matter how feedrate or Rotation Radius is set.

Example: set A, B, and C identically. rotation radius .001 on each. All are set as rotary axis, not inhibits, etc.

A obeys set feedrate wil G1 move, B and C do not.   

Is there a reason for this behavior?
Re: Is B and C axis G1 feed rate broken?
« Reply #1 on: July 18, 2012, 08:40:21 AM »
R3.43.22
Seems to be fine here.
Can only affect it in Motor Tuning.
Are you sure B & C are tuned same as A ? (most likely are, just checking)

Russ

Offline simpson36

*
  •  1,369 1,369
Re: Is B and C axis G1 feed rate broken?
« Reply #2 on: July 18, 2012, 04:20:39 PM »
Thanks for the response, Russ.

Yes, I seth up A.B abd C identically and double checked every setting that I am aware of as detainled in the first. post.

I did not try 022. I am using 062.  I'll throw 022 on something ans see if the behavior is the same.

Oh and my development computer is Win7 64 bit, but I get the same behavior on the mill which is XP pro 32 bit.

 

Offline simpson36

*
  •  1,369 1,369
Re: Is B and C axis G1 feed rate broken?
« Reply #3 on: July 18, 2012, 04:42:52 PM »
Follow up:

22 does indeed work fine, so 062 is broken.

THANKS!

Offline simpson36

*
  •  1,369 1,369
Re: Is B and C axis G1 feed rate broken?
« Reply #4 on: July 21, 2012, 07:22:46 AM »
Just to follow up, I have a work around.

The application is a macro for hard tapping as seen in my latest video. When the feed rate is broken, the only option is to use G0 which can be a bit scary  :o

My work around was so store the Z axis velocity and accel and then change them to appropriate maximums allowing the use of G0. At the end of the macro the setting are restored to their original values.  Works fine so far.