Forum Replies Created
-
You don;t need to wrap Gcode in JSON. The input parser figures that anything that’s not already accounted for must be a Gcode command and runs it as Gcode (Technically, if you are in JSON mode the parser wraps the Gcode for you then runs it as JSON Gcode. That way the responses com back in JSON wrappers). It’s written this way so that UIs don’t need to wrap Gcode from a file – it can just be streamed.
You can query limit switches (or any other parameter) using JSON. For example, {“xsn”:””} returns the X min limit switch setting.
–ALden
There are a number of things you might want to do for “Homing”. depending on what you need.
Going to G0x0y0z0 is fine if your machine is already referenced to zero, but does not actually reference it.
Doing G28.2x0y0z0 will actually reference the machine to zero using the homing switches – assuming you have that all set up
Going G28.3×0 will set the current point as absolute 0 (brrr) for X. G28.3x0y0z0 for all 3 axes, or G0x50 will set the current to 50, etc.
G28.2 and G28.3 are “non-standard” extensions to Gcode to handle these cases. Look at G28 and G28.1 (and G30/G30.1) to see how they are used. They also set and return to specific points.
See https://github.com/synthetos/TinyG/wiki/TinyG-Homing
Alden
