[adamvs]

I have this up on the Autodesk/CAM forum, but was asked to put it here also. So here it is. This is NOT from Tormach, this is my doing, but I've been using it all along and it's working quite well. It support a bunch of things:
X+ ( turret ), X- ( QCTP ), and gang tooling - and any combination thereof.
Looping, through the use of 'PassThroughs'.
Importing outside gcode, through use of 'Actions'.
Bar Pullers, through using the above, and 'Stock Transfer' ops on Fusion.
Lathing on the Tormach Mills.

Highly advisable to read the instructions - they are brief. You will need to change the extension from '.txt' to '.cps'. This forum wouldn't let up upload a '.cps' file for some reason.

That said, here is the disclaimer:
[usual] Disclaimer: It's a homegrown effort that seems to be working OK on *my* machine, but *may* have mistakes and is not guaranteed in any way. Using this software may cause scrapped parts, tool breakage, machine damage, and otherwise ruin your day! Contains unverified code to support 'Turret mode', I (sniff) don't have a turret yet! Please check the PathPilot tool path window, check gcode, and run air passes, to check validity before cutting parts.

Happy posting!

[MichaelHenry]

Thanks Adam!

[LeeWay]

Thanks a bunch, Adam.
I was getting ready to use it the other day and was stopped because F360 does not yet support NPT threads. The conversational in PP does though.
Maybe that would have been a good chance to find out about Actions.

I still don't quite understand what looping is.

[adamvs]

Thanks a bunch, Adam.
I was getting ready to use it the other day and was stopped because F360 does not yet support NPT threads. The conversational in PP does though.
Maybe that would have been a good chance to find out about Actions.

I still don't quite understand what looping is.

This is great! This feature will get used! I actually got the idea to support loops in the gcode for your setup. You can use the 'PassThrough' feature to setup a loop around a bunch of operations by inserting the linux loop stuff,e.g., o1003 repeat [32] ... o1003 endrepeat

[LeeWay]

Ahh. Okay.
I know more about that than I thought I did.
Early on, I asked Tormach about the possibility of having a cycle counter put into PP. They seemed to think it was doable.
I think I need to mention that again.
At times, it would be a very good thing to know how many cycles it has left to run on a bar.
Should not take up much Real Estate in the GUI on the main screen. Sometimes we have over 50 cycles (loops) per bar.

[LeeWay]

Here it is as an idea still.
http://www.tormach.com/pathpilot_tracking.html#issues

#994

[adamvs]

Ahh. Okay.
I know more about that than I thought I did.

.. yes you do.

Early on, I asked Tormach about the possibility of having a cycle counter put into PP. They seemed to think it was doable.
I think I need to mention that again.
At times, it would be a very good thing to know how many cycles it has left to run on a bar.
Should not take up much Real Estate in the GUI on the main screen. Sometimes we have over 50 cycles (loops) per bar.

This is cool idea, and something that could be easily done in linuxcnc ( and in a post processor ) with a software counter. Just improvising here, but all that's needed is an M command, with some dedicated space in the backplot pane in PP. Tho PP could be hacked. I spent a some hours one day looking at the PathPilot source code for a way to add an M command but couldn't easily find it. My guess is the parser is on the linuxcnc side.

[adamvs]

I've put this post processor up on github, so the latest can be downloaded:
https://github.com/adamvs99/Tormach_SlantPRO