Inventor CAM Ultimate 10.0.0.21308 - Generates code which crashed my machine.

[SafetyLok]

Hi,

Last week we were making parts without issues.

We did an Inventor 2023 update last week, and now this weekend with the same part, when we re-generate our tool paths Inventor CAM makes a mistake deep down in the g-code and puts the spindle through the part and into the table.  This is really bad, like very bad.

I've found an online g-code simulator to illustrate my point.

From our revision control, this is the result of the g-code generation of last Wednesday:

And now as of the latest inventor update, with code generated today, this is the result:

We made a small tweek to the part, but regardless, nothing should cause g-code like this!.

Is there any way we can get some help with this????.

I can send the .ipt file to an Autodesk person, but can't post it here due to NDA.

Thanks.

EDIT:

Actually it looks like a bug.

What we changed was the "Stay Down Level" on the linking tab of an adaptive tool path. We made this change was our machine spending too much time plunging into air.

When we select a 90% stay-down level, we get valid g-code.

When we select "MOST", we get INVALID g-code as posted above.

[user87246]

yikes!

[CGBenner]

Tagging @jeff.pek   🙂

[SafetyLok · Accepted solution]

For those interested we had a Hiedenhain ISO post processor we found on a forum post.

It has the following revision data:

  Heidenhain ISO post processor configuration.
  $Revision: 41960 008441bba96f8a0a2230dac71d544bca3ae8b70e $
  $Date: 2018-05-01 11:19:56 $
  FORKID {43354140-D681-47d0-B056-9A0A277F620D}

Deep down in the processor we have a condition from when we change from circular moves to linear moves. The problem started appearing as we had just completed a 3D adaptive path and then used the same tool to clean up a boundary.

The previous OnCircular() used in the 3D adaptive sets G91 but in some cases when doing the next OnLinear() G90 is not output as G code.

We updated our OnLinear() G01 without radius comp code to read:

// LG, added G90 as operation from previous circular did not reset the G91!!
writeBlock(gAbsIncModal.format(90), gFormat.format(1), x, y, z, f);

This change fixed the problem.