C-Axis Indexing odd behavior

[ObsidianLabs]

Using the most recent Fanuc post processor in the library just slightly modified for a B&C rotary table and some code for an auto tool setter. I cannot get any C axis indexing alone to post out correctly. If its B and C then everything works pretty good without any issue. I have a part I need to index 180 on C to interpolate a hole. I can use the tool orientation setting to rotate the part around but the tool path is still trying to go to the original location of the feature before indexing, then it corrects itself and links to the new location as seen in the video attached.

Any insight in this would be greatly appreciated.

[AchimN]

Hi @ObsidianLabs ,
I see that in your post the property "Use G68.2" is disabled, is that correct? Does the machine not have that option?
Second, do you have TCP enabled in your machine definition inside Fusion?

Note that there is no need to modify your post to define the kinematics, this is purely done in Fusion when you define your machine there.
Can you maybe share your Fusion project?

[ObsidianLabs]

Unfortunately I do not have TCPC or tilted work planes configured on the machine

[AchimN]

Its hard to say whats going on without the fusion project tbh. Any chance you can share it?

[ObsidianLabs]

Sure.

https://a360.co/3HAXnUg

[ObsidianLabs]

We can close this. 

Solution is to edit the following in the Fanuc post. Now it will output the correct code for C Axis translations.

Set OptimizeType from Optimize Axis to Optimize Both

workPlaneMethod: 

    optimizeType : OPTIMIZE_BOTH // can be set to OPTIMIZE_NONE, OPTIMIZE_BOTH, OPTIMIZE_TABLES, OPTIMIZE_HEADS, OPTIMIZE_AXIS. 'undefined' uses legacy rotations

[AchimN]

I doubt that this is the solution tbh, it more indicates that you have TCP enabled in your machine definition.
OPTIMIZE_AXIS is the default in all posts and respects exactly that TCP setting, when you change that to anything else, the machine definition TCP setting will be ignored.

Unfortunately i cannot download the project you´ve shared due to permission restrictions?

[ObsidianLabs]

I don't have TCP or TWP enabled on this machine, but I did have that checked in the kinematics. You are correct that unchecking TCP does fix the issue without editing the post.  I originally did not have this machine definition configured and was running based on the post processor I had been using. I built the machine config last night and moved over to the most recent Fanuc post. So TCP disabled gives the correct orientation and values 👍🏼

New Link Here.

https://a360.co/3Jl8AJc

[AchimN]

Excellent, thanks for confirming! 👍