4TH AXIS CODE TOO LONG...

[Anonymous]

Hello,

Im looking of an answer to reduce the amount of code that gets posted for 4th axis milling. Currently using the Generic HAAS A-axis post.

Current Fusion code:

N95 G94 Z2.1938 F10.
N100 G93 A44. F1821.539
N105 A44.602 F1821.552
N110 A45.204 F1821.542
N115 A45.806 F1821.55
N120 A46.409 F1821.548
N125 A47.011 F1821.541
N130 A47.613 F1821.546
N135 A48.215 F1821.544
N140 A48.817 F1821.55
N145 A49.42 F1821.548
N150 A50.022 F1821.544

I want this to be one A axis move not 2mb worth...

ex. A0.0

A90.0

[LibertyMachine]

Do you mind sharing your file? Perhaps there is something set improper

File > Export > Save to local folder. Return to thread and attach the .f3d file in your reply

[Anonymous]

Here you go Seth

[LibertyMachine]

What you're seeing is a function of "Inverse Time" which is how the post generates the code. I understand what you are looking for, but I'm honestly uncertain if the post is capable of being modified to produce what you want

punting to @GeorgeRoberts if he's still online 😉

[GeorgeRoberts]

Hi both!

The tolerance is causing all of these values. I have raised it as an issue and will take a look into how we can minimize the amount of movements outputted

Many thanks

[Anonymous]

George,

Please let me know if this gets fixed, for now i have to revert to using Gibbscam.