Cannot Edit Post w/o "Invalid post processsor." error.

[Parker.Musselman]

Every time I edit a post in Visual Studio Code they can no longer be used in Fusion without getting the error above. 

I've tried uploading to Cloud and local via the post library. I've tried dragging files to "C:\Users\******\AppData\Roaming\Autodesk\Fusion 360 CAM\Posts" and they don't show up in the post library. 

I haven't seen this issue while searching. 

[dwilliamsFM6K4]

What post and what editing are you trying to do?

I've had posts that I've incorrectly edited not show up in the post library despite being properly placed because of code issues, for that reason I ALWAYS make a copy prior to editing, and leave the old file in place as a 'check'

Are you certain the post changes you are trying to make are allowed?

[seth.madore]

What sort of edits are you doing to the post, and have you confirmed that inside of Visual Studio, the code is good?

[Parker.Musselman]

Thanks for the quick reply and the help.

Edit: I should add that the issue was that the code was not good.

I am trying to edit the provided DMS Router Fagor 8065 post. The way it is programmed outputs G53 coordinate movements in the "function onOpen()" block - giving the following:

G53
G0 G53 Z0
X0 Y0
G53 B0. C0.

Our machine uses MSC coordinates instead of G53. The intended output would be formatted like:

#MCS Z-4.(MCS = MACHINE COORDINATE SYSTEM IN STANDARD UNITS - DOESNT TOGGLE PROGRAM TO STANDARD)
#MCS B0.
#MCS C0.
#MCS Z0.

I found this post but it seems to be outdated. The DMS post code that Bob Schults edited differs from the current DMS post code. 

The pertinent code in the current DMS is here:

// startup blocks
  writeBlock("#MCS OFF"); // Use part system
  writeBlock("#CS OFF"); // Part coordinate system
  if (getProperty("fifthAxis")) {
    writeBlock("#RTCP OFF"); // Cancel TCP transformation
    writeBlock("#HSC OFF"); // Disable contouring error
    writeBlock("#KIN ID[0]"); // Kinematics style
  }
  writeBlock(gUnitModal.format(unit == IN ? 70 : 71), gCycleModal.format(80), gAbsIncModal.format(90));
  writeBlock(gPlaneModal.format(17), gFormat.format(40));
  writeBlock(gFormat.format(53));

  if (getProperty("useVTable")) {
    swapVTable(true, false);
  }
}

function onComment(message) {
  writeComment(message);
}

/** Force output of X, Y, and Z. */
function forceXYZ() {
  xOutput.reset();
  yOutput.reset();
  zOutput.reset();
}

/** Force output of A, B, and C. */
function forceABC() {
  aOutput.reset();
  bOutput.reset();
  cOutput.reset();
}

/** Force output of X, Y, Z, A, B, C, and F on next output. */
function forceAny() {
  forceXYZ();
  forceABC();
  feedOutput.reset();
}

[Parker.Musselman · Accepted solution]

For posterity, I was able to fix this with some code that Bob Schultz sent as follows: 

You should be able to use the instructions from the original Forum thread, by replacing the output of the G53 blocks to use #MCS instead.  There are only 2 of these for the DMS Fagor 8065 post, one in onSection ...

// writeBlock(gFormat.format(53), aOutput.format(0), bOutput.format(0), cOutput.format(abc.z));
writeBlock("#MCS", aOutput.format(0), bOutput.format(0), cOutput.format(abc.z));

... and one in writeRetract ...

// writeBlock(gMotionModal.format(0), gWCSModal.format(53), words); // retract

writeBlock(gMotionModal.format(0), "#MCS", words); // retract