Skip to main content
J
JO_116557037-Bedrock
7-Bedrock
August 20, 2025
Solved

4 axis post is not indexing to correct angle (Creo 8)

  • August 20, 2025
  • 1 reply
  • 1741 views

Hello All,

 

We have a Haas VF-2 with a Haas HRT210 rotary. I'm machining a block on 4 sides (AO, A90, A180, A270). Working off centerline of the rotary. The problem is that the posed gcode creates A0 and A180 in the correct orientation but A90 and A270 are flipped. In the attached picture specifically (WCS.jpg) depicts how I have the coordinates set up A0 being the top of the part (the face with the cbores).  A270 being the flat face in picture WCS_A270.jpg. Has anyone ran into this problem? Can this be fixed in the post processor application within creo?

 

Thanks,

Jostan

Best answer by JO_11655703

That part is correct. I found the solution. I flipped the the coordinates A270 and A90 to negative values. Then I needed to change the scaling factor from of the A-axis from 1 to a -1. 

1 reply

K
KenFarley21-Topaz II
21-Topaz II
August 20, 2025

The only 4th axis programming I've done is full motion milling, rather than indexing.

One thing I had to experiment with that might be related to your troubles is the "Rotary Axis Type" specification in the Option File Generator. Found at:

 

Applications->NC Post Processor->Type,Specs,& Axes->4-Axis Rotary Table

 

There are a lot of different options there. Maybe the one you currently have set is wrong? I know this particular setting is very dependant on what type of controller/rotary table you have. Took me a bit of experimentation to get it right for our particular setup, since the rotary table was an after-market addon.

J
JO_116557037-BedrockAuthorAnswer
7-Bedrock
August 20, 2025

That part is correct. I found the solution. I flipped the the coordinates A270 and A90 to negative values. Then I needed to change the scaling factor from of the A-axis from 1 to a -1. 

B
BF_142591014-Participant
4-Participant
October 23, 2025

You may run into situations where multiplying the A axis by -1 will be a problem, if you decide in the future to use Haas' Local Coordinate System rotation capabilities.  I recommend correcting the direction of the rotary in your post-processor to avoid a future bug.  Haas is typically backwards from what is mathematically correct, and also has a habit of misnaming rotary axes.  It's also possible that there are parameters in the Haas controller to change the settings (which could be the easiest solution!)

Terms & ConditionsCookie settingsAccessibility statement