What is going on with Pathpilot for 15L? So many new issues

I build my programs mostly in conversational but some edits I will do in note pad. My programs are between 6 and 12 steps with tool changes in between.

  1. When I edit a completed program in conversational, Pathpilot always adds an M1 stop between steps. This is after I had previously deleted them AND didn’t even edit those particular steps. Is there a way to disable that? It is hugely annoying.
  2. On a similar note I notice that when I edit a step or two Pathpilot will add a ; to the G30 and Tool change command on a few random steps so that it is sure to be on the wrong tool and crash the machine. Has anyone had this happen? This is recent as of V12.12.X
  3. When programming a profile, once you set external or internal it doesn’t let you switch and will try to automatically change a previous step to the last setting you had (ext/int). I’m running both profiles on the same part and it tries to make them match. This has also crashed a few tools. I can’t get the button back (in conversation mode) to select ext or int on the profile page.
  4. This goes along with #3. When I edit the program with both profiles it will switch the one step that I’m not editing to the same settings as the one that I am. I see no options to unselect the auto switching.

Most of these are getting to the point where I’m not going to edit in Pathpilot because it will screw up the entire program by adding all kinds of things I didn’t tell it to add. A 5 min edit turns into another 20 minutes of clean up (or crashed machines and broken tools )because of Pathpilot.

  1. Has anyone noticed that when you key in a tool change on the screen Pathpilot will go to a solid green cycle start condition where you have to hit the stop button just to jog the tool? This is also new for V12.12.X and is very annoying.

I always do a “save as” and make a new version of my program and it is consistently doing this. Has anyone else experienced these issues?

@Eric_Flavin I would highly recommend putting this into a Service Ticket, if you haven’t already, so these issues can be looked into more in depth. Jira Service Management