I'm reasonably decent at CAD having used Fusion360 to design and 3D print for some time now. However I'm a newbie (and I mean COMPLETE newbie) to CAM, gcode and post processors.
I've built a 1500x1500mm downdraft plasma CNC table. It's working rather well. I've managed to get myself as far as the most basic of understanding manufacturing in Fusion. Using the PP from the forum here I can get a flat pattern, generate a tool path and post it to an NC file and get parts cut with reasonable success.
I haven't figured out hole spotting though. I know folks may say use something like Sheetcam and I'm sure it's a good solution but I'm trying to stay in Fusion (for now at least).
I tested QtPlasmaC's built in spotting function by writing a really simple gcode file to spot at the torch's current zeroed position and it works. The built in spotting is quite nice actually. Leaves a perfect little dimple (I'm testing with 1/8" aluminum sheet). 500ms pulse@20A
Code:
G20 ; Set units to inches
G90 ; Absolute distance mode
N60 F#<_hal[plasmac.cut-feed-rate]> ; Copied from other working NC files
G0 X0 Y0 ; Torch is already jogged to test location
M3 $2 S1 ; Fire spotting tool (triggers the millisecond timer)
G91 ; Switch to relative (why?)
G1 X0.000001 ; Microscopic move to satisfy LinuxCNC motion controller (why?)
M30 ; End program
Before I try to reverse engineer the Fusion360 post processor to figure this out I'm wondering if there's any cool tricks in Fusion to get the PP to write the M3 $2 S1 command at a specific point.
Or as a reasonable work around get it to write something out that's easy to search and replace with M3 $2 S1. If that makes sense.
I did see something about adding in a drilling operation but when I tried it I discovered the free version of Fusion won't allow that.
Also not sure why the G91/G1microscopic move is necessary. Pretty sure the tolerance settings will result in it being ignored but without it I get an error loading the file that it'll move outside my machine boundary. I don't think that's the case but QtPlasmaC still throws the error.
Anyway I hope this isn't a bunch of utterly annoying newbie questions.

I sincerely appreciate any help with this part of the learning curve.
Cheers,
-Dave