This is a very early version, but it allows you to use many standard Fusion tool paths, such as 3D parallel pass tool paths using the Avid laser. Essentially the laser is turned on, at the appropriate power based on the spindle speed during cutting operations, and you can utilize the smooth lead in/lead out/transition that Fusion provides between lines.
Should work for contour (simple vector) and pocket (filling) paths. Probably works for most paths. Note: this will follow Z axis geometry, so if your milling tool path would move in the Z axis, so will this later tool path.
For example, here is a 3D parallel tool path using sketch geometry to choose parallel path geometry
Zooming in very far, you can see the cutting (blue) geometry during which the laser would be burning, along side the non-cutting (lead-in, lead-out) paths. This may be difficult to see, but the smooth geometry (green, light blue in the following pic) allows for smooth machine movements from one scan line to another.
What have you changed over the stock post? Right now in the stock post you can use the special fusion laser mode, and if you want you can currently use regular milling tool paths as laser tool paths.
You just need to be on tool 99 and have that tools RPM set to the laser power you want.
The stock post processor wasn’t always including M3 in the tool path section, so the spindle (laser) was never turned on:
(STOCK)
(MACHINE)
( VENDOR AVID EX ROTARY)
( MODEL CHETEX)
(T99 D=0.007 CR=0. - ZMIN=0.234 - FLAT END MILL)
G90 G94 G40 G49 G17
G20
(-ATTENTION- PROPERTY SAFE RETRACTS IS SET TO CLEARANCE HEIGHT.)
(ENSURE THE CLEARANCE HEIGHT WILL CLEAR THE PART AND OR FIXTURES.)
(RAISE THE Z-AXIS TO A SAFE HEIGHT BEFORE STARTING THE PROGRAM.)
(PARALLEL1)
T99 M6
G17 G90 G94
G0 A0.
G0 X1.5092 Y0.2002
Z0.834
G0 Z0.314
G1 Z0.2347 F50.
....
Note: my machine has a different name/model but is actually unmodified from the avid machine profile.
Even if it did include that, for example S21 M3the laser would be on at 21% for the entire tool path, including rapids, lead ins, lead outs, dwells, …
My post will ensure, when the laser tool is being used, that a S0 M3is issued in the section header (fusion tool path start) after the T99 M6.
Only during the cutting (CUTTING and FINISH_CUTTING) movements the laser is turned on at the spindle RPM and is turned off for non-cutting operations (lead-in, lead-out, rapids, etc.). This is done by introducing the onMovement function:
function onMovement(movement) {
if (!bmpLaserMilling) return;
switch (movement) {
case MOVEMENT_CUTTING:
case 14: /* finishing cut */
if (bmpLaserState == 0) {
writeBlock(sOutput.format(currentSection.getTool().spindleRPM));
bmpLaserState = 1;
gMotionModal.reset();
}
break;
default:
if (bmpLaserState == 1) {
bmpLaserState = 0;
writeBlock(sOutput.format(0));
gMotionModal.reset();
}
}
}
Yeah, it’s weird. Looking at the code, IIRC (I’m away from my main computer), the logic should emit an M3 after tool change, or if it is the first section (tool path) always, or similar logic.
I assume you are referring to setting the operation type to cutting in the manufacturing setup? In that case, all that is exposed is a 2D profile tool path. Maybe I’m missing something??
My use case for laser on the Avid CNC is 99% engraving/marking – almost zero cutting. I have a dedicated laser system based on homegrown centroid for more typical laser only use cases. That is generally driven by lightburn, though that can be a mess (I mentioned the g-code and rounding issues that plagues lightburn in some other thread). Also, for my use cases, the engraving is almost always after typical milling (routing) operations.
Attached is the Fusion project for the Avid keychain, if you are curious.
Ok, so this special post makes a little more sense… Question: Why not just use VCarve/Aspire with the laser module? It makes these type of engravings a total piece of cake.
Switching CAM software can be a pain, but Vectric really does make laser engraving easy.
We did a similar thing for Mach… basically we let users convert router g code into laser g code right in Mach. That works well, but you do lose out on some of the toolpath optimization you get in something that’s more dedicated to lasering… Like for example being able to raster across a whole bunch of items at once, etc. That feature alone saves a lot of time when lasering.
I do wish Fusion would add some more support for toolpaths like that. Perhaps an “Add-in” could be created to do that…
