topic Re: Post Process Custom Drill Cycle? in Fusion Manufacture Forum

Post Process Custom Drill Cycle?

alexwbakker — Tue, 04 Jun 2019 21:54:01 GMT

I have a CNC controlled knee mill, running Mach 3, that has the CNC control of the knee z axis, rather than the spindle. As a result, it does great cnc milling, but doesn't mess with my ability to use the machine as a manual drill press/hand tap, etc.

What I'd like to do though is create a custom PP for this machine that can "take over" a drill cycle, and just locate the hole while I manual drill with the quill. Given that my feed rates on the knee are not very high, I think this will be much more convenient than trying to get drilling to work with the knee, and also will allow me to tap, since my spindle is controlled manually, not with Mach 4.

So, is there a way to essentially take the drill cycle and replace it with a Gcode output that moves to the center of the first hole, waits for cycle start, and then moves to the next hole? Then i could start the G code, machine moves the table, I drill the hole, hit cycle start, machine moves the hole, etc. I could repeat for tapping or pre-drilling, etc.

Thanks for any help you can offer!

Re: Post Process Custom Drill Cycle?

HughesTooling — Tue, 04 Jun 2019 23:04:30 GMT

I've done that on my Anilam machine. I use a dwell 0.0 to make the machine pause and wait for the start button, is there something similar in Mach4? Are you going to always manually drill, or do you want the post to do manual and automatic? Could just have 2 posts though.

Mark

Re: Post Process Custom Drill Cycle?

alexwbakker — Wed, 05 Jun 2019 00:21:53 GMT

That would work - I'd probably never use the standard drill cycle. (My max feed rate on the knee is about 6 IPM, so I avoid anything that might involve rapid retracts). Any pointers on how to modify the PP so that I can strip out the all the Z axis moves and insert the dwell codes?

Thanks!

Re: Post Process Custom Drill Cycle?

HughesTooling — Wed, 05 Jun 2019 22:38:22 GMT

Are you using a PC or mac? Easier if you're using a PC as there's an option on the post dialog to open the post processor. Just select open config and the post should open in your editor, save to a place on your hard drive not back to the generic folder.

Then look for something like this.

Change the 81 to 00 for a rapid move and below after the comma add "G04 0.0" including the quotes or thinking about it "M0" might be a better idea.

Mark.

Test the post carefully and I'd better add this

The accompanying advice and or non-standard post processor is provided as-is and without warranty of any kind, and usage is at the user’s own risk.

Do not put custom posts in the generic posts folder. Use the personal folder. or another location.

Fusion 360 CAM Personal Posts Folder Locations

_______________________________________________________________________________

Microsoft Windows:
%appdata%\Autodesk\Fusion 360 CAM\Posts

Mac / Apple / OSX:
/Users/<user id>/Autodesk/Fusion 360 CAM/Posts

Re: Post Process Custom Drill Cycle?

alexwbakker — Thu, 06 Jun 2019 01:59:38 GMT

Well, I gave that a try, here's what the block looks like now inside the Mach3 PP, modified per your suggestions.

function onCyclePoint(x, y, z) {
  if (!isSameDirection(getRotation().forward, new Vector(0, 0, 1))) {
    expandCyclePoint(x, y, z);
    return;
  }
  if (isFirstCyclePoint()) {
    repositionToCycleClearance(cycle, x, y, z);
    
    // return to initial Z which is clearance plane and set absolute mode

    var F = cycle.feedrate;
    var P = !cycle.dwell ? 0 : cycle.dwell; // in seconds

    switch (cycleType) {
    case "drilling":
      writeBlock(
        gRetractModal.format(98), gCycleModal.format(00),
        getCommonCycle(x, y, "M0"),
        feedOutput.format(F)
      );
      break;

but, I just get ".failed" appended to my post processors. unfortunately, the PP file says "view the log file" but does not indicate which one, and fusion writes a *lot* of log files. It does not appear to be in any of the normal fusion diagnostics log...huh.

I've attached the latest .failed file just so you can see. It does write an initializing block, but doesn't get any further.

Thank you for the help, Mark!

Re: Post Process Custom Drill Cycle?

johnswetz1982 — Thu, 06 Jun 2019 02:57:17 GMT

I think you were supposed to do this,
switch (cycleType) {
    case "drilling":
      writeBlock(
        gRetractModal.format(98), gCycleModal.format(0),
        getCommonCycle(x, y, "M0"),feedOutput.format(F), "M00"
      );
      break;
Adding the "M0" where you had it was probably what was giving you your error.

Re: Post Process Custom Drill Cycle?

alexwbakker — Mon, 10 Jun 2019 23:00:51 GMT

So, I made your suggested changes, and I can now get the code to post, but, the code is odd. It will move to the first hole and issue and M00, but, then it just lists all the other coordinates in one giant string of rapids. Do I need to do something to the later blocks to issue the M00 between each hole? I think we’re close here.

Re: Post Process Custom Drill Cycle?

johnswetz1982 — Tue, 11 Jun 2019 01:27:14 GMT

That was just a clarification of what Huges was trying to get across. Perhaps @HughesTooling would know?

Re: Post Process Custom Drill Cycle?

daniel_lyall — Tue, 11 Jun 2019 02:19:11 GMT

Try 01 it is Optional program stop

Re: Post Process Custom Drill Cycle?

HughesTooling — Tue, 11 Jun 2019 07:47:46 GMT

Sorry should have looked closer, the drill cycle is setup on the first call then all other calls are passed to the end of the function.

I haven't had time to test this but I think it should work. Added a check for the cycle type and output m01 if drilling. Codes also below for copy paste.

  // 2nd through nth cycle point
  } else {
    if (cycleExpanded) {
      expandCyclePoint(x, y, z);
    } else {
      if (!xyzFormat.areDifferent(x, xOutput.getCurrent()) &&
          !xyzFormat.areDifferent(y, yOutput.getCurrent()) &&
          !xyzFormat.areDifferent(z, zOutput.getCurrent())) {
        switch (gPlaneModal.getCurrent()) {
        case 17: // XY
          xOutput.reset(); // at least one axis is required
          break;
        case 18: // ZX
          zOutput.reset(); // at least one axis is required
          break;
        case 19: // YZ
          yOutput.reset(); // at least one axis is required
          break;
        }
      }
      if (incrementalMode) { // set current position to retract height
        setCyclePosition(cycle.retract);
      }
		if(cycleType == "drilling") {
			writeBlock(xOutput.format(x), yOutput.format(y), "M0");
		}else {
			writeBlock(xOutput.format(x), yOutput.format(y));
		}
      if (incrementalMode) { // set current position to clearance height
        setCyclePosition(cycle.clearance);
      }
    }
  }
}

Mark