Fusion 360 post processor file for Plamac

Thanks Steven, i will look into the sheetcam going on your advise. I was hoping to limit the amount of programs and steps needed to complete a task from start to finish. We use Gibbs cam to program our mill and lathes and fusion has been filling the gap with design and sheetmetal. If the Fusion cam worked out for the plasma it was just a bonus!! Thankyou again for your advise on this forum this far i hope you manage to get something to work efficiently for you, before you start the Job with 200 holes!!!!

I got a working solution to the circles being broken into many arcs problem over on the Fusion360 forum from Bob Schultz. I have incorporated that solution into my Fusion360 post processor. I will post this over in the PlasmaC Post Processors topic that Phil recently started.

Steven

Thankyou again Steven very much appreciated that you have shared the post processor. Your solution will make a big difference, having managed to incorporate the small hole processing and center punch mark features and by taking the time to produce a manual.

I appreciate the time and effort put into this pp. I couldn't dream of making an attempt at it. I've tried to use it several times, and I keep getting the same type of error at the machine when I load the gcode file. I've attached a screenshot of the error message as well as attached the gcode file itself.

Pat

Please bear with me as I am not skilled at using Fusion 360 and the CAM features. I am also not skilled in describing the geometry of Cartesian moves.

I needed to make a piece of equipment that required solid modeling to get all the parts right. So I built up a model in Fusion 360 with little effort ( I am an old ProE hand). Then I went to CAM several of the sheet steel parts to cut out with the plasma cutter using PlasmaC for the control. I used the PlasmaC post processor for Fusion 360 posted at the top of the topics. It took a bit of work to get everything setup and going but in the end I was able to get the models posted without any reported errors. Upon loading the Gcode into Plasmac I was greeted with errors on some of the arc moves. While the start and end points of the arcs were correct the posted I and J values were not on the blocks that error-ed out. The first thing I did notice was that the posted precision was rather excessive for imperial units, I reduced the posted precision to 4 places for imperial units with no change in the reported errors on loading. Because these are simple rectilinear parts I was able to manually fix the code to produce the parts.

The errors always occurred with two types of moves. A G2 (clockwise move) with the arc in the 4th quadrant and a G3 ( counter clockwise move) with the arc in the 2nd quadrant. The errors are very repeatable with minor geometry changes producing the same errors. So for now it is back to Inkscape and SheetCam for me.

One other thing, is there a way in Fusion 360 to do nesting? I like to cut a whole sheet of mixed parts at a time. I know how to do it manually by using work piece offsets but that isn't nice and graphically easy to do.

John

In the 'Property' section of the Post Process dialog box in Fusion change the "MergeCircles" value to "NO" this will fix the radius differs issue

I am just playing with the Fusion 360 PlasmaC post processor now. Is the intention that you need to create a tool in F360 that has zero kerf width so that the GCode is created with movements that are "on the line" and then PlasmaC adds offset based on its chosen kerf width??? I have tried with an existing plasma tool in Fusion 360 with a kerf width of 1.3mm and then posting with the PlasmaC PP and the GCode definitely contains the offset. I assume PlasmaC will then add more offset based on its kerf width. Is this correct?

I just tried & Fusion 360 won't let me set a zero kerf plasma tool. What am I missing???