it is too fast to use F200 with G2?

May it caused by a time sequence problem, a few CNC senior Engineer analysizied that it caused by Y axis command period long 20ms than than x axis command period.

curran209 wrote:

the result of the calculation v^2/R is 2m/s^2, the max acceleration in my INI is 600, 
 

So, your max acceleration in the INI is 600 mm/s2 and you need 2000 mm/s2. So your machine can not make that radius at that speed. (The machine units are mm) 

I set x and y max acceleration to 2500mm/s2 in ini, but it more bad.[img]D:\Users\Administrator\Desktop\xhiqi\问题[/img] The above circle is drawed by 600mm/s2, and the below circle is drawed by 2500mm/s2. 

when i set max acceleration to more smaller, it's to gooder. a =1mm/s2, the effect was almost not too far, but the speed only can to be 120mm/min，it's too slow.

image  a =1, image g code file.  

Physics dictates the acceleration required to draw a circle of given size and speed.

Your mechanical design dictates the maximum possible acceleration.

If your machine can not actually accelerate at the required rate then it can't draw the circle.

You need to make your machine lighter and more powerful.

This is entirely a problem with your mechanical design and there is nothing that LinuxCNC can do about it.

It could also be a drive tuning issue.

Inability to reach 600mm/s^2 acceleration
with a linear motor is quite suspect.

curran209: Can you attach your hal and ini files?

Another CNC control software can use this machine draw circle with setting F6000 and r =5mm.
Does these hal and ini file image enough to analysis it?

Where does the joint feedback data come from?
That is, what drives joint.n.motor-pos-fb

or is this open loop

Is there some reason you cannot post the entire hal and ini files?

please review it.