- Posts: 22
- Thank you received: 0
Weird rotary axis movement
1 year 3 months ago #331204
by Methier
Weird rotary axis movement was created by Methier
Hello, we have a machine with a rotary axis, in some corners the cutter does not reach the corner completely and makes a rapid movement on the rotary axis. I tried to reduce the error with G64 but lowering the P value makes it worse.
Machine is running analog servos, old yellow cap fanuc.
The error is consistent int the same place.
Attached a pic.
Thanks
Machine is running analog servos, old yellow cap fanuc.
The error is consistent int the same place.
Attached a pic.
Thanks
Please Log in to join the conversation.
- Todd Zuercher
- Offline
- Platinum Member
-
Less
More
- Posts: 4739
- Thank you received: 2
1 year 3 months ago #331512
by Todd Zuercher
Replied by Todd Zuercher on topic Weird rotary axis movement
Could you post the G-code that is giving the error? Not necessarily the the entire G-code program. Especially if the program is large. Just a snippet that includes at least a few lines before the error, and a few lines after, so we might be able to test and reproduce the error. It's a little hard to see and understand what is going on just from your image.
Please Log in to join the conversation.
1 year 3 months ago #331612
by Hakan
Replied by Hakan on topic Weird rotary axis movement
If I remember right, linuxcnc doesn't do synchronized motion on rotary axis.
Maybe wrong term but feeds,speeds and acceleration is determined by x,y,z only and the rotary axis will do the best it can. When it can't keep up this in the figure happens.
One usually uses the inverse time feed specification G93, and calculate the time needed for the movement in the CAM post-processor.
There are converters on "the web" that can translate G code to G93.
Maybe wrong term but feeds,speeds and acceleration is determined by x,y,z only and the rotary axis will do the best it can. When it can't keep up this in the figure happens.
One usually uses the inverse time feed specification G93, and calculate the time needed for the movement in the CAM post-processor.
There are converters on "the web" that can translate G code to G93.
Please Log in to join the conversation.
- Todd Zuercher
- Offline
- Platinum Member
-
Less
More
- Posts: 4739
- Thank you received: 2
1 year 3 months ago #331702
by Todd Zuercher
Replied by Todd Zuercher on topic Weird rotary axis movement
It isn't that Linuxcnc doesn't do sychronized motion with rotoary axis. Rotary axis are sychronized just fine with linear. The problem is the incompatability of linear feed rate units with rotary feed rate units. The result is often (especially with inches) unexpectedly slow movements when a rotary move is mixed with a linear one. The problem is actually a G-code limitation, rather than a Linuxcnc one. For example you are milling along at F20 inches/min then you throw in a 40 degree move with the rotary. The rotary move is going to take 2 minutes to comple because of the F20, if the same line also includes a 1 inch move, the linear move will be limited to 0.5ipm so that it takes the same 2 minutes to complete. This is where the invers time mode comes to the rescue. it has no unit of measure involved just time. So if you want your 40deg 1inch combined move to move so that the linear component still moves at 20ipm you would specify F code on the line as 1/t or in this case 1/0.05min. or F20.0
Please Log in to join the conversation.
1 year 3 months ago #331705
by Hakan
Replied by Hakan on topic Weird rotary axis movement
Yeah I didn't remember that right. Then I wonder if that's the problem here.
Please Log in to join the conversation.
1 year 3 months ago #331713
by andypugh
Replied by andypugh on topic Weird rotary axis movement
Is there any possibility that this is configured as a WRAPPED_ROTARY?
linuxcnc.org/docs/html/config/ini-config...:ini:sec:axis-letter
wiki.linuxcnc.org/cgi-bin/wiki.pl?WrappedRotaryAxes
linuxcnc.org/docs/html/config/ini-config...:ini:sec:axis-letter
wiki.linuxcnc.org/cgi-bin/wiki.pl?WrappedRotaryAxes
Please Log in to join the conversation.
Time to create page: 0.085 seconds
