Machine Simulation with TABLE ROT in heidenhain not working

[rusty.bird]

When I simulate a toolpath that has the table (C axis) rotated but not the head (B axis), the machine simulation doesn't show the rotation on the simulation and shows it cutting C0,B0 but running the code for this will rotate the table on the machine correctly.  If I have the head rotated and the Table , It will show it correctly in the machine simulation and run the code on the machine correctly.

I have a .machine file (table-head machine) with Y and C axis on the table and X,Z,B on the head.  I have the machine working properly when testing out the axis.

The Toolpath is a contour Milling path with a tool orientation with the X axis (X axis on head as indicated above) reversed to rotate the table 180 deg.  I have tried at 90 deg aswell.

[marcus.toepke]

So if you mean the simulation in the machine, that's actually normal I think

[rusty.bird]

So its normal If I have a tool orientation to rotate the table 90 deg or 180deg and make a toolpath but the machine simulation doesnt show this rotation at all?

[a.laasW8M6T]

It is possible the machine configuration isn't quite correct, can you upload your simulation model and machine config here so someone can take a look?

This should work fine

[rusty.bird]

I have just tried this machine model in Fusion 360 library called "Autodesk Generic 5-axis (AC Table-Table)" Table: AC Head: XYZ.  I am getting the same issue with this and is more easier to test.

If you are Facing the Top of a Part and have a Tool orientation on it "Select Z axis/plane & X axis" and click the "Flip X Axis" it should rotate the table 180 deg and face the part am I correct?

[a.laasW8M6T]

Ahh I understand the problem now, um I'm not good enough with posts to fix this

Maybe @bob.schultz will have some ideas?

[rusty.bird]

The post already works and will rotate the table but the machine simulation doesn't match.

[MaxWP2TT]

Can you post some pics? I might be able to help with this. some screenshots of your config and desired result/actual would help.

[bob.schultz · Accepted solution]

Hello @rusty.bird,

Thanks for reporting this, it is an issue with the post processor.  While the Heidenhain post processor outputs the correct PLANE SPATIAL SPA+0 SPB+0 SPC-90 command so that the machine will rotate the C-axis, you will notice that the positioning of the tables just prior to this command is L A+0 C+0, which is incorrect.  You can replace the getWorkPlaneMachineABC function with the following function to correctly position the rotary axes during machine simulation.

function getWorkPlaneMachineABC(workPlane, rotate) {
  var W = workPlane; // map to global frame

  var currentABC = isFirstSection() ? new Vector(0, 0, 0) : getCurrentDirection();
  var abc = machineConfiguration.getABCByPreference(W, currentABC, ABC, PREFER_PREFERENCE, ENABLE_ALL);

  var direction = machineConfiguration.getDirection(abc);
  if (!isSameDirection(direction, W.forward)) {
    error(localize("Orientation not supported."));
  }

  if (rotate) {
    var tcp = false; // keep false for CYCL 19
    if (tcp) {
      setRotation(W); // TCP mode
    } else {
      var O = machineConfiguration.getOrientation(abc);
      var R = machineConfiguration.getRemainingOrientation(abc, W);
      setRotation(R);
    }
  }
  return abc;
}

We will get it updated in the library post.

[rusty.bird]

Thanks @bob.schultz that fixed the problem.  Testing this in fusion 360 works fine but doesn't seam to work in HSMWorks machine simulation.  

[bob.schultz]

This fix is meant to work with Fusion 360.  From a post processor standpoint, I don't think anything can be done to affect how HSMWorks controls the machine simulation in this situation.

[rusty.bird]

ok thanks atleast it works for fusion which is more what I wanted.