Hello Guest it is March 28, 2024, 08:25:38 PM

Author Topic: G52 problems with unintended movement  (Read 2209 times)

0 Members and 1 Guest are viewing this topic.

G52 problems with unintended movement
« on: June 15, 2013, 04:41:47 PM »
Hello,

I'm just starting to learn G code and I'm testing out G52 but I'm having unintended movement.  Here is an example:

G52 X0 Y0 Z0
G1 X0 Y0
G1 Z5
G52 X-200 Y200
G1 x0 y0
G1 z0
G52 X0 Y0 Z0
G0 Z15

At the last G0 Z15, it moves to X0 Y0 at the same time, making a diagonal movement instead of just going straight up in Z.

Is this normal?

Then, in my initialization:
G52 X0 Y0 Z0
G1 X0 Y0
Wouldn't this be dangerous, if a previously run program had set G52 Z to something different, and if I called G1 X0 Y0, it would move in the Z direction?

So then, if I wanted to use G52, my next line that contains a G0 or G1 should contain at least the values for the directions that I changed in the G52?

And if I wanted to have something like:
G52 X10 Y10
Z15

I should instead change this to?:
Z15
G52 X10 Y10


Does Mach3 remember the last used G52 offsets on program start, next loaded G-gode, or after emergency stop?  So do I need to use G52 X0 Y0 Z0 in the beginning of all my programs?



thanks
« Last Edit: June 15, 2013, 04:46:38 PM by thomash »

Offline RICH

*
  • *
  •  7,427 7,427
    • View Profile
Re: G52 problems with unintended movement
« Reply #1 on: June 15, 2013, 05:15:16 PM »
I am not the sharpest one on Gcode, but, my understanding of a G52 use is to provide a shift to the part zero "within the current work offset"  by some amount. A G54 offset is required prior to use of  G52.

Stay tuned for me to be corrected, :D

RICH