Post Processor suddenly outputs different codes

[MichaelD87]

Hi,

We are using a post processor for the DMG MORI CLX 450 TC.

We have noticed that our post processor suddenly started outputting different codes than what we are used to.

It seems like it is having problems outputting G18 and G17 where it should. And it sometimes does not output

AROT Y90 when it should.

We belive that this started happening a couple of weeks ago.

We have made sure that no change has taken place in our post processor in the last month that could be the source of this issue.

This means that most of what we post is useless and requires a large amount of manual correction to be usable.

Is anyone else having this issue? Has Fusion heard of anything like this in the last two weeks?

Was wondering if this could be a fusion update issue.

[seth.madore]

Are you using the post from the library or one of your own modified post processors?

Which post processor are you using? I see that the NLX post was updated 15 days ago (which coincides with your timeline). Can you share your post or a link to the one you are using?

[MichaelD87]

We are using a post processor that is customized from a Fusion supplier.

So i'm not sure if i should share it on a public forum.

[seth.madore]

You can drop me an email with the post processor.

That said, if you could share some sample code here showing the "before" and "after", that would be most helpful to any other user who stumbles upon this thread.

Email: seth DOT madore AT autodesk DOT com

[MichaelD87]

Here are the sample files before and after.
The post is not able to post G17,G18 and AROT Y90 at the right locations.

[Vohnsen]

we had that problem and a friend of mine had that problen - we used standart modifyed posts.. i guess someone clicked update..

Why the hell at autodesk thought about that ideea - small button that updates the most important file and can potientially destroy the machines if they are wrong.. 

[MichaelD87]

Our post processor is not linked to Fuison in any way and does not update to Fusions post processor library.
Our problem is that nothing has changed with our post processor but the codes that comes from Fusion to the post processor has. Leading to a change in angle calculations in the NC code.

[seth.madore]

Could you also email me a sample file that you were using to generate the code?

[seth.madore]

And are you seeing this with older Fusion files that would have produced proper output, but now (without regenerating the toolpaths) produce incorrect values?

[MichaelD87]

Have sent you a link to the file.
And yes the problem exists with every program i use the post processor on that had no issues before.
And no changes have been made to the post processor.
I'm not 100% sure but i belive that the 2 NC files you got from me are from the same post processor.
Only change that was added was adding part counter options or something like that.
That did not affect the way the machine moved.

[a.laasW8M6T]

One thing you could try is turning off this option.

I'm not sure if it will have any effect but its worth a shot.