Regenerate and Post with multi-threading enabled

[samuelhanson]

I am trying to regenerate and post a number of operations from a C# NET-Hook.

 

I iterate through each operation, regenerate if necessary, then start the post processor.

 

If multi-threading is enabled sometimes the regeneration is not completed before the post processor is initiated. When that happens it doesn't post properly. Turn multi-threading off and everything works perfect but slower.

 

How can I make the post processor wait until operations are finished regenerating?

string pathNC = Mastercam.IO.SettingsManager.UserDirectory+@"Router\NC\new";

Mastercam.Database.Operation[] selectedOps = Mastercam.Support.SearchManager.GetOperations(false);

foreach (var op in selectedOps)
{
   op.NCIName = Mastercam.IO.SettingsManager.UserDirectory + @"Router\NCI\cake.nci";
   op.Commit(false);
   if (op.Dirty)
   {
      op.Regenerate();
   }
}

// System.Threading.Thread.Sleep(10000); //Wait... but apparently that locks up the regeneration too.

foreach (var op in selectedOps)
{
   op.Retrieve();
   if (op.Dirty)
   {
      System.Windows.Forms.MessageBox.Show("Error - dirty operation");
      return;
   }
}

Mastercam.Operations.OperationsManager.PostOperations(selectedOps, pathNC, true, false); 

Mastercam X9 Router, C# NET-Hook

[Roger Martin from CNC Software]

In X9, in a NET-Hook you cannot really know when all of the operations have completed (or not) .

 

In Mastercam 2017 there will be a new Notify method jut for this purpose ->

 

public override MCamReturn MultiThreadOpStateNotify(int opId, MCamMultiThreadOpState state)

{

    string status = "Unknown";

    switch (state)

    {

        case Mastercam.App.Types.MCamMultiThreadOpState.Success:

            status = "Success";

            break;

        case Mastercam.App.Types.MCamMultiThreadOpState.Stopped:

            status = "Stopped";

            break;

        case Mastercam.App.Types.MCamMultiThreadOpState.Failed:

            status = "Failed";

            break;

    }

 

    MessageBox.Show(

        string.Format("opID: {0}\nState: {1}", opId, status), 

        "MultiThread Manager",

        MessageBoxButtons.OK, 

        MessageBoxIcon.Information);

 

    return Mastercam.App.Types.MCamReturn.NoErrors;

}

 

You'd make note of the opIDs that you submitted to be regenerated and then using the MultiThreadOpStateNotify method you can determine their status.

[samuelhanson]

The man with all the answers once again. Thanks!

[Matthew Hajicek - Singularity]

Be aware that some operations (multi-axis drill comes to mind) require their geometry to be visible during regeneration.  If the geometry is not visible it will throw an error, but then show the operation as having been regenerated rather than dirty as it should.

[jlw™]

Be aware that some operations (multi-axis drill comes to mind) require their geometry to be visible during regeneration. If the geometry is not visible it will throw an error, but then show the operation as having been regenerated rather than dirty as it should.

Yeah, that's bucked me in the futt a few times. I've got two where I make one view sheet with every level on before regen when I have multiaxis drill ops.

[samuelhanson]

Be aware that some operations (multi-axis drill comes to mind) require their geometry to be visible during regeneration.  If the geometry is not visible it will throw an error, but then show the operation as having been regenerated rather than dirty as it should.

Good to know, thanks

[samuelhanson]

Related,

The NC file is opening for editing even when I specify not to. Any ideas what might cause this?

public static bool regenAndPost(string fileName, bool onlySelected){
  //Regenerate toolpaths
  //...
  
  //Post
  Mastercam.Operations.OperationsManager.PostAllOperations(System.IO.Path.GetDirectoryName(fileName),false);
  return true;
} 

[Roger Martin from CNC Software]

In the Post Processor (PST) that is being used...

Is bug1$ defined? And if so, is it set to a value other then '0'?

[samuelhanson]

bug1$ is not defined in the PST.

However, I did try it with a different post and the editor was not launched.

 

Is there anything else in the post language that could cause the editor to launch?

 

Edit: Looks like bug1$ might be in the PSB... I'll verify and report back.

[samuelhanson]

bug1$ was the answer. Had our post developer switch it to 0 in the PSB and everything is good.

[Roger Martin from CNC Software]

Only bug1$ and putting the bug1$ setting in the PSB doesn't sound like a good idea to me.

[samuelhanson]

External company developed post... is what it is now.