G30 / G31 issue with 2.03RC1
-
Hello,
I just tested 2.03RC1 for my CNC router and run into the following issue using a simple switch for z-probing.
- I calibrate my probe using G30 S-3 and then save the calibration using M500 P31
- I probe z-level using G30 (so far everything good as expected)
- I move to probe away to maximum Z-level using G53 G0 Z140. This results in a crash at the z-max level.
- After the crash the z-value displayed is Z113.65 which happens to be the maximum value possible with the old calibration.
I'm not sure what is the reason for this behavior.
Regards,
Marc -
Where did you get 2.03RC1? They is no such release as far I know
-
Did you mean 2.03beta1? 2.03RC1 isn't out yet, unless you built it yourself from the source files on github.
-
Yes, I built it myself from GitHub. Saw the tag and was not aware that it is not officially out yet.
-
@mwinterm said in G30 / G31 issue with 2.03RC1:
Hello,
I just tested 2.03RC1 for my CNC router and run into the following issue using a simple switch for z-probing.
- I calibrate my probe using G30 S-3 and then save the calibration using M500 P31
- I probe z-level using G30 (so far everything good as expected)
- I move to probe away to maximum Z-level using G53 G0 Z140. This results in a crash at the z-max level.
- After the crash the z-value displayed is Z113.65 which happens to be the maximum value possible with the old calibration.
What is your Z max value set to in M208? Is it 113.65?
-
No, the Z max value set with M208 is 140. So I basically want to send the head all up.
I run all this in G54 which before running G30 was in a state that 113.65 in G54 would have corresponded to 140 in G53 (machine coordinates). -
I'm still not clear exactly what problem you are describing. Please can you describe the complete sequence, including any G10 commands that you are using to set the workplace coordinate offset, and when it goes wrong tell us what you expected to happen and what actually happens.
-
- I switch on the machine
- Home all Axis
- G10 L2 P1 -> Origin of workplace 1: X100.00 Y100.00 Z38.50 U0.00 V0.00 (from config-override.g)
- G10 P1 -> Tool 1 offsets: X0.00 Y 0.00 Z12.15 U0.00 V0.00 active/standby temperature(s): 0.0/0.0 (from config-override.g)
- G0 X0 Y0 move to the probing point
- I probe z-level using G30
- I issue G0 Z0 to check if the tool moves to the probed level -> everything good (note the new probed level is different from the initial one)
- I issue again G10 L2 P1 -> Origin of workplace 1: X100.00 Y100.00 Z38.50 U0.00 V0.00. This result does not make sense to me. I would expect the Z-coordinate to be different according to the new probed level.
7 . I move to probe away to maximum Z-level using G53 G0 Z140 -> crash into the mechanical top level endstop - After the crash the z-value displayed is Z113.65 which happens to be the maximum value possible with the initial calibration (113.65 = 140 -38.5+12.15)
-
@mwinterm said in G30 / G31 issue with 2.03RC1:
- I switch on the machine
- Home all Axis
- G10 L2 P1 -> Origin of workplace 1: X100.00 Y100.00 Z38.50 U0.00 V0.00 (from config-override.g)
- G10 P1 -> Tool 1 offsets: X0.00 Y 0.00 Z12.15 U0.00 V0.00 active/standby temperature(s): 0.0/0.0 (from config-override.g)
- G0 X0 Y0 move to the probing point
- I probe z-level using G30
- I issue G0 Z0 to check if the tool moves to the probed level -> everything good (note the new probed level is different from the initial one)
- I issue again G10 L2 P1 -> Origin of workplace 1: X100.00 Y100.00 Z38.50 U0.00 V0.00. This result does not make sense to me. I would expect the Z-coordinate to be different according to the new probed level.
7 . I move to probe away to maximum Z-level using G53 G0 Z140 -> crash into the mechanical top level endstop - After the crash the z-value displayed is Z113.65 which happens to be the maximum value possible with the initial calibration (113.65 = 140 -38.5+12.15)
Please can you try firmware 2.02RC3 and see if this issue is resolved. There have been fixes to handling workplace coordinate offsets between RC2 and RC3.