Plasmac Post Processors

This thread is for user donated post processors for CAM software that has no native post processer for QtPlasmaC/PlasmaC.
I will make this sticky and unlocked and just keep current versions here.
If there are posted comments or corrections I will delete them after they have been actioned.

Current PP's:

• Fusion360 - QtPlasmaC
• Fusion360 - PlasmaC (AXIS & GMOCCAPY)
• ProNest 2019
• SOLIDWORKS (CAMWorks)
• Inkscape
• PeddiNest

There are no third party PP's here for SheetCam, use the PlasmaC PP included with SheetCam for both QtPlasmaC and Plasmac.

PP creators need to be aware of the following:

• LinuxCNC does not allows analog/digital input or output while cutter compensation (G41) is active.
• QtPlasmaC disables G92 offsets.

All work product by the author is provided ​“AS IS”. The Author makes no other warranties, express or implied, and hereby disclaims all implied warranties, including any warranty of merchantability and warranty of fitness for a particular purpose.

Fusion360 post processor for use with PlasmaC. There is also a manual and a test file included.
Please use cautiously at your own risk. It is working for me, but there could still be errors.
Please post any problems or questions over in the existing topic: Fusion360 Post Processor Topic

You will need to remove the .txt extension from the post processor file and the Fusion360 test file.

pronest 2019 post for plasmac
rename to CFF

Also i wanted to share my PP for Solidworks (Camworks). it is basically a copy of phils Sheetcam PP.

Its not fully tested, so always check trough the gcode, for my spotting, marking etc it works. No scribing and it is setup for a metric machiene .

the attached Plasma001.ctl is the compiled PP file. Under your machiene setup in camworks point to this file. The file location should also contain the attached info files with Plasma001_L.rtf,Plasma001_S.rtf, Plasma001.pinf and Plasma001.lng

it might be necessary to compile the PP on your machiene yourself. U need to download the UPG (universal post generator) from the camworks site. You open the source file Plasma001.gpsd in the EC Editor (The UPG wont recognize the file, u cant open it with the UPG). Under the section Library files u change the path to the Plasma001.lib file to the location you have it on your computer, the same for the Master Library file from camworks Mill.Lib.

You save the Plasma001.gpsd file and now in the UPG Program you go to File--> compile source and select the freshly edited Plasma001.gpsd. After sucessful compilation, select it again in your solidworks machiene setup and regenerate the toolpaths.

that should do the trick

After running into some trouble with the Fusion 360 post processor, I spent some time working on it to solve the issues I was experiencing.  Refer to my post here forum.linuxcnc.org/plasmac/38199-fusion-...-for-plamac?start=40

I have fixed up the F360 post processor and tested a new version.  It works well with F360 and qtPlasmac.  I have also updated the F360 test files to fully test the changes and small hole functions.  The original author may want to do a compare and review the changes

Unfortunately after editing this post I lost the original content out of it some how that had the change list of what I changed and why.  I don't remember all the little details.  

Fixes were mostly around the small hole features that were not correctly working.  Also G41 offset compensation used the wrong signal name.

I have also included a Plasmac materials library and matching F360 tool library for Hypertherm Powermax 45.

No changes have been made that alter functionality from the original documentation.

The attached  Custom G-code Filter  should render the G-code suitable for QtPlasmaC.

Copy custom_filter.py to the configuration directory for the plasma table.

Some examples of typical PeddiNest G-code files are attached.

You do need to be aware that all the motion in these files is incremental.

Hi  Phill
Question just to be sure I understand correctly:
in the custom_pre_parse(data)  funtion "data" is a single row or a array of rows.
then if it is a single row (as i think) the return data is the statement that will substitute the actual row?

Edit..
The code you sent me is working now I added pre and post amble.
thanks 

 

grijalvap wrote:

in the custom_pre_parse(data)  funtion "data" is a single row or a array of rows.

then if it is a single row (as i think) the return data is the statement that will substitute the actual row?

Correct:

• data is a single line of G-code from the loading file.
• the return may be None to delete the line, a single line of G-code, or multiple lines of G-code separated by a newline.

The code you sent me is working now I added pre and post amble.

Great, glad it works. You may need to ensure that it does not affect code written by another PP.

hi i got a problem with your post . i got no M3 commaand for starting the plasma do you have a clue what i am doing wrong