Fusion 360 Post Processor MPCNC v3.0 (Beta 3) is Available

Software / Firmware Fusion360
41

I have setup my lowrider for Zero Probe to be the corner of my table.

I have setup G56 location of my work piece.

When I set WCS to 3 in fusion it never updates the gcode to relocate to G56 after probing.

Has anyone else tried this?

Is the post processor capable of accepting the WCS setting from fusion?

I am at a loss….

42

Has development of this stopped?

I am looking into making a change to include the WCS info but not sure where it needs to go.

I did locate this grbl.cps

grbl.zip (19.9 KB)

44

No development hasn’t stopped but it is not actively happening as I’ve heard of no issues. That said, I’m interested in understanding issues.

If you are going to look at the pp, make sure you use the zip at the top of this thread - I’m not sure what GRBL.zip contains.

To determine if the problem you are describing is a pp issue, do the following. Create the simplest F360 project you can that has the issue then enable the debug comment level. This should show you detailed information to help you understand what the pp is receiving and doing.

45

If you isolate a problem, post the relevant part of the debug output that is wrong and then your expected results.

The pp is basically a formatter, it doesn’t interpret the GCode (other than the enhancements documented). Offsetting by a coordinate position I would assume would be done by F360 prior to the pp being pasted the operation to be output - though I could be wrong.

46

After further review:

What you’re describing points to two related gaps in the PP:

  1. WCS selection: The PP currently does not read F360’s WCS setting and map it to G54/G55/G56 etc. It always operates in the default coordinate system. Support for this would require explicitly reading currentSection.workOffset and emitting the corresponding G5x command.
  2. Probe target register: Even if WCS were respected, the probe routine stores its result into a fixed register (effectively G54/P1). To probe into G56, it would need to use G10 L20 P3 Z0 (or the equivalent for X/Y).
    As a workaround for now: since you’ve already manually set G56 in your controller, you can add G56 as a manual NC command at the top of your F360 setup (via the “Manual NC” operation). This will cause the PP to emit it verbatim at that point in the gcode, and your pre-configured G56 offset will take effect from there.

WCS support is on my radar as a future enhancement. If others are using multiple WCS offsets, please chime in — it’ll help prioritize.

Unfortunately, at this time I can’t commit to a timeline to make these changes but will add it to my list of things to do

1 Like
47

Follow-up for those interested in Work Coordinate’s.

I set 3 locations at Terminal Mode:

Zero Table

G54 (Corner of table)

Move to location

G10 L20 P1 X0 Y0 Z0

Save the config: $CD=Config.yaml

Zero Table

G55 (Tool change location)

Moved to location

G10 L20 P2 X0 Y0 Z0

$CD=Config.yaml

Zero Table

G65 (1st Work Location)

G10 L20 P3 X0 Y0 Z0

$CD=Config.yaml

To use the locations, Set the location you want to use.

Tool Change

G55

Now issue G90 X0 Y0 Z0 (G90-Fast move)

Now if i can figure out how to change the Modes Buttons, it could be a quick way of getting around.