[joeavaerage]

Hi,
all the required code to handle four axis was already in the Fusion post. It required that your 'turn on' the code in the machine definition which is a part of the post, assign an axis in the form of a vector
about which the rotary axis rotates and specify its range of movement, ie a trunnion or a free running axis. A dozen keystrokes is all it took.
The information that I needed to identify those statements within the post that I needed to edit I got from the Fusion forum.

Since that time I have studied the post a bit more closely largely because of the link to a 300page PDF on Autodesks post processors. Note that the Fusion posts are near identical to HSMworks
and so on. There is a lot to digest. Much of the post looks mystifying because its written in Javascript which I've never had any exposure to. Once you start to get familiar with Javascript, and a good
intro is in the PDF I mentioned, then the post starts to look a lot more comprehensible, including those features that you need to 'turn on' for multi-axis.

https://cam.autodesk.com/posts/posts...ng%20Guide.pdf

Craig

[difalkner]

Hi,
all the required code to handle four axis was already in the Fusion post. It required that your 'turn on' the code in the machine definition which is a part of the post, assign an axis in the form of a vector
about which the rotary axis rotates and specify its range of movement, ie a trunnion or a free running axis. A dozen keystrokes is all it took.
The information that I needed to identify those statements within the post that I needed to edit I got from the Fusion forum.

Since that time I have studied the post a bit more closely largely because of the link to a 300page PDF on Autodesks post processors. Note that the Fusion posts are near identical to HSMworks
and so on. There is a lot to digest. Much of the post looks mystifying because its written in Javascript which I've never had any exposure to. Once you start to get familiar with Javascript, and a good
intro is in the PDF I mentioned, then the post starts to look a lot more comprehensible, including those features that you need to 'turn on' for multi-axis.

https://cam.autodesk.com/posts/posts...ng%20Guide.pdf

Craig

Thanks, Craig! I'll begin studying this soon.

[joeavaerage]

Hi,

You get an error on this "OnOpen" function. And it wont compile the .nc file.
Maby i can find an other post file for an other machine to generate the right gcodes....

But that is exactly the sort of error that you would get if you have a four axis toolpath but do not have a four axis machine definition in your post, and that in turn is often only a matter
of turning that feature on in the post.

Have you had a look inside the post and seen if there are any multi-axis definitions in there? There may well be, many if not most Fusion posts are multi-axis, but 'de-tuned' to three axis
for release.

Why don't you ask on the Fusion forum, the Manufacturing sub-board. Someone will surely know if the post has four or even five axis code.

Craig

[eisendud]

Hi there

We found a other post pros.
In sted of useing the richauto post pros.
You just use the "HAAS - A-axis (pre-NGC)" and edit this file here to change the X Z

If you have the A axsis in X direction on your table....

if (true) {
var aAxis = createAxis({coordinate:0, table:true, axis:[(getProperty("makeAAxisOtherWay") ? -1 : 1) * -1, 0, 0], cyclic:true, preference:0});
machineConfiguration = new MachineConfiguration(aAxis);

And you have your A axsis in Y direction on your table:
if (true) {
var aAxis = createAxis({coordinate:0, table:true, axis:[(getProperty("makeAAxisOtherWay") ? -1 : 1) * 0, -1, 0], cyclic:true, preference:0});
machineConfiguration = new MachineConfiguration(aAxis);

Hope this help the next guy who have richauto controller, we use Rickauto A18

Eis