Is there any way to have g-code generated ONLY for simulation, and another g-code for actual cn file?

[bernard5BABD]

This may look like a strange question, so I will try to explain as best as I can.
On a Roeders machine, probing is done with Roeders commands, where a "target" is defined, rather than with usual G-Code coordinate instructions. It does work well, the only problem is that probing is never simulated, it goes directly to the first milling toolpath.

It would be much nicer if everything could be simulated, probing included. Would this be possible, or I am asking too much?

[serge.quiblier · Accepted solution]

Hi  

there is no way to achieve such functionality.

By default, the post linked with the .machine file for simulating will mainly be used in order to grab the orientation selected by the post, in order to simulate in Fusion using the same posture.

As the machine may have dissymmetric limits, a preferred tilt direction and so on, we need to be able to grab the orientation selected in the post to transfer back in Fusion.

Because by default in Fusion everything is reachable. (any tool axis if potentially possible)

The canned cycles can't be simulated from the post.

For the classical drilling the system will mimic the behavior of the machine.

But for the probing, as Fusion is not generating the probing moves, just the prepositioning, we can't use them in the post.

And if we were able to recreate them in the post, we don't have the ability to pass them back to Fusion for simulating.

Regards.

______________________________________________________________

If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!

[bernard5BABD]

Thank you for a clear explanation. I thought it would be the case, I asked to be sure I was not missing something. BTW, I finished today, with the last test on one of the Roeders probing function. Everything is working. Just hope the client will not find some hidden bug. Thanks for your help.