G28 and G28.1 help needed (Carbide Motion, S3)

[OttoPilot]

I'm trying to use G28 and G28.1 manually into the GCode that HSMExpress is creating. Trying to use G28 to bring the machine forward to overhang the workspace to allow for easier tool changes.

I can get the two commands working in MDI without issue, but have not had any luck adding them into my HSMExpress outputs.

Any G28 command I enter appear to be ignored when running the file.

Has anyone had a similar issue, or have an example of a correct implementation outside of MDI?

[heathenx]

What if instead of g28 you use g0 x0 y0 z0?

[OttoPilot]

That should just rapid back to my zero location (which in most situations is the corner of my workpiece).

I need a way that I can set a zero on my workpiece, and have a secondary location to return to for tool changes.

The g28 command works in universal gcode sender...but I don't have any way to pause/resume a cut in UGS (or at least I haven't found one). So it returns to the proper coordinates, and then zips right back to the work piece with the same tool.

Carbide motion allows for the pause/resume commands to work, but doesn't give me any way to move to a tool change location.

I'm sure there's some way of doing what I need in both programs...I just haven't been able to figure it out.

[heathenx]

What about a G30/G30.1 for your sendary location? Works the same as G28/G28.1.

[OttoPilot]

Negative. Appears to ignore them all while streaming.

[edwardrford]

You could setup another Work Coordinate System. Where G54 (the default WCS) is the toolchange location, and G55 is your job 0,0,0. You can call a specific WCS from within g-code just by passing it's value on a single line: G54, G55, etc.

@twforeman has a good writeup on the wiki.

[heathenx]

You could setup another Work Coordinate System. Where G54 (the default WCS) is the toolchange location, and G55 is your job 0,0,0. You can call a specific WCS from within g-code just by passing it's value on a single line: G54, G55, etc.

@twforeman has a good writeup on the wiki.

I just recently learned how to do this myself (setting work offsets) and enlisted the help of GRBL-Panel since I found it easier to set. I now know how to use offsets in Carbide Motion but it's a bit more manual and I didn't quite understand what I was doing at first. As a matter of fact, I thought there was a bug in Carbide Motion because my machine was moving to odd places. User error, most likely. Anyway, unlike OttoPilot, I prefer to run single jobs per tool rather than running a bigger file with all my tool changes inside. I feel like I can keep track of what is going on when I break things up.

[OttoPilot]

Thanks guys after a quick skim this appears to be what I'm looking for, looks like I have some reading to do.