Announcements

Announcement: We’re aware of an issue affecting starting a new topic from category pages and creating new blog posts. New topics can still be started directly from the relevant board. Learn more here.

XCZ machining exceeding X-axis limit

XCZ machining exceeding X-axis limit

MichaelSmith1987
Enthusiast Enthusiast
559 Views
4 Replies
Message 1 of 5

XCZ machining exceeding X-axis limit

MichaelSmith1987
Enthusiast
Enthusiast

My post is outputting XZC co-ordinates correctly, apart from outputting negative X-axis values. I am programming for a mill/turn machine. The xAxisMinimum property is set to 0, but this seems to be ignored for XZC output. How can I keep the X-axis in the positive? 

 

Below is a screenshot of the adaptive milling operation that I am programming. The operation starts in the X positive with respect to the axis orientation, but then it moves into the negative, even when the C axis is rotating. 

Screenshot 2025-04-15 094847.pngScreenshot 2025-04-15 094847.png

Thanks in advance. 

0 Likes
560 Views
4 Replies
Replies (4)
Message 2 of 5

a.laasW8M6T
Mentor
Mentor

Hi

It shouldn't be doing that but...

 

assuming all those cutouts are identical I would set the adaptive toolpath to machine just one of them and then add it to a circular pattern.

This should machine each one then index the C around and to the next.

 

Hard to tell for sure though with out the file and knowing exactly what postprocessor.

Andrew Laas
Senior Machinist, Scott Automation


EESignature

0 Likes
Message 3 of 5

MichaelSmith1987
Enthusiast
Enthusiast

Thanks for your quick response. 

 

For smaller parts it will work to output X and Y axis movements and then index the C axis for the other copies. But for larger parts that cannot be done using the Y axis, it will be necessary to use XZC. 

 

I have made a test file that patterns an XZC operation. The output I get still moves over to X negative, even when I would expect X values for each instance of the pattern to be the same with only the C axis values changing. 

 

I have attached the test file and the post I am using. 

0 Likes
Message 4 of 5

a.laasW8M6T
Mentor
Mentor

Hi

 

Your post is outputting with G12.1, this means the controller should convert the negative values into the correct motion for you.

I'm not sure if you have run the code on the machine yet or were just looking at it and seeing the negative values assuming it won't work.

 

If you want Fusion to do the true XZC for you you need to use a manual action command before the toolpath or change the post processor.

alaasW8M6T_0-1744748161026.pngalaasW8M6T_0-1744748161026.png

 

 

in the post you can change this:

var gotPolarInterpolation = true;

 

to false

var gotPolarInterpolation = false;

 

and it will always output XZC

Andrew Laas
Senior Machinist, Scott Automation


EESignature

Message 5 of 5

MichaelSmith1987
Enthusiast
Enthusiast

Hi there

 

Thanks for your response. 

 

This is a partial solution as it resolves the issue of the X going into the negative but it comes with the issue of XZC programming which does not always give the best surface finish. 

The code has been tested on the machine and while the machine accepts G12.1 and polar co-ordinates, the machine does not convert the negative X values as would be expected. 

Would there be a way to output G12.1 but have it convert the negative X values in the post? 

 

Thanks

0 Likes