Is there a list of usable machine parameters for the MASSO?

[Aiph5u (Aiph5u (not affiliated with Onefinity))]

Hey Moar,

@MoarVoltz

I’ve seen a few posts referencing parameters such as #5221 and #5241 for the X offset for g54 and g55 respectively. Is there a list of these somewhere?

these are numbered parameters and are a part of g-code standard. It may be that not all numbered parameters are available on every CNC controller. The Buildbotics CNC Controller has its g-code patterned after the LinuxCNC g-code dialect, and the parameters are listed here.

@Aiph5u

• The Onefinity CNC Controller is a software and hardware fork of

• the Buildbotics CNC Controller (Source). The G-code the Buildbotics Controller (and therefore the Onefinity Controller) understands is patterned after the LinuxCNC dialect of the G-code Standard.

  • (see also: Differences between LinuxCNC and RS274/NGC).

• The CAMotics 3D toolpath visualization software has the same author as the Buildbotics CNC Controller. CAMotics supports a subset of LinuxCNC GCode.

• LinuxCNC evolved from the NIST’s Enhanced Machine Controller (EMC) project (See EMC History).

The coordinate systems G54–G59.3 and their numbered parameters are described here and the corresponding G54–G59.3 commands here.

Image: RS274/NGC parameters table.

@MoarVoltz

but I’m specifically wanting to find out if there are parameters that correspond to the machine coordinates

For moving in machine coordinates, there is the G53 command.

@Aiph5u

G53 Move in machine coordinates – no matter what coordinate system is in effect, it won’t change the latter.

IMPORTANT NOTE: Unlike the coordinate system commands G54–G59.3, G53 is not modal, it must be programmed on each line. G0 or G1 does not have to be programmed on the same line if one is currently active.

For G53 coordinates, on LinuxCNC and controllers with g-code patterned after LinuxCNC g-code dialect, there are the parameters #<_abs_x>, #<_abs_y>, #<_abs_z>, #<_abs_a> etc. but they do not work on the Onefinity/Buildbotics controller (don’t know for the MASSO, please report). A workaround on the Onefinity/Buildbotics is to use [#<_x> + #<_offset_x>]