Best Practice G-Code

I use Vectric VCarve Desktop which limits G-code files to 25"x25" workspace and then Tiles the output. The majority of my work on my Woodworker fits within the 25"x25" space. Typically if I have a larger file, I can either modify the g-code file, create the file on Free Cad or move the work piece.
Lately I’ve been moving the bit to a new point by using the manual g-code section on the touchscreen interface and then setting that as the new zero point. The tiled file then runs well. With the new macro capability that will be out soon, I’m thinking about setting up some macros to make that easier.
My question is if I should actually be using commands like G54 Fixture Offset or possibly G52 System Shift as a better way to accomplish the same thing?
Really don’t see me spending $350 for the VCarve Pro version since this is a hobby, not a money maker.

IMO, macros are for more persistent use cases. In other words, by the time you setup a macro for a particular, unique, job, you could have just uploaded the GCode file and run it like any other program. Then delete it.

I would suggest just keep using the “Tiling Toolpaths” feature in Vcave, or utilizing FreeCAD as you mentioned doing before.

Or, I haven’t tried this, but you could try designing your own registration holes, and using mutliple “Sheets” in Vcarve. Then copy your vectors to these multiple Sheets, aligning them manually?


Aiph5u explains it well here.
For moving relative to the last tile position just use G92 not G53.


G92 might be an option but I’m trying out the new macro commands and setting up some standard tiles.
This one makes sure I’m starting off referencing the default Coordinate system (G54) then moves to the position I want as the new tile. It then sets that position as the origin of coordinate system 2 then evokes Coordinate system 2 (G55). Then it’s easy to move back and forth in the Coordinate systems as needed.
I wish there was a way to enter data into the file
G0 X16 Y0 Z0
G10 L20 P2 X0 Y0 Z0

Hello Jeff
Trying to understand what you are planning to do:
Are you trying to have G54 be the origin of one tile, G55 the origin of the next tile a set distance away from G54, etc?
Then do you plan to make each tile a different origin in the code and run them so they all seamlessly fit together?
If so I may have something to help you, but I don’t want to muddy the waters if I am misunderstanding.

1 Like

Yes, Chris. I’m creating a coordinate system for each tile. Vcarve writes each toolpath of each tile to a separate file and they are all referenced to X0 Y0 assuming that you have moved the piece or offset the XY… After I load the gcode file, I can just send a single G code (G54 through G57 - I only need 4 maximum) to call that coordinate system, then press play on the file.
I had a complicated test job today that was 2 tiles and 4 files per tile. It worked well until I forgot to send the G55 code before one file and hit a hold down (luckily a plastic one)
I found that each file that you load resets to G54 so the coordinate system command is required before running each file that isn’t #1.
There is a way to combine tool paths so I could have done it in 2 files per tile. I’ll test that this weekend to make sure the coordinate system doesn’t reset between Tool paths within the file.