You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using probe type 2 and a x and y offset vs nozzle I can observe correct behavior of "G30 P1" which offsets the head before probing making the probe hit where nozzle was.
After then probing multiple points with "G30 P0" (with G0 commands between) the finishing "G30 P2" does not restore head position.
If script is rerun, the first probe ends up probing with no offsetting as it has already had the offset applied, but upon returning up from probe hit, it will move diagonally up offsetting the point again.
Rest of points continue as normal. This leads to a coordinate creep until system crashes in wall.
The text was updated successfully, but these errors were encountered:
I made a mistake and ran old code. Updated to latest dev2 as of today and it behaves better.
Still not correct though.
Now it homes x and y even though machine was homed before move to probe target.
Use a core-xyz macine with x and y offset on probe set in eeprom.
Home machine
Move to target x,y,z with G0.
Issue G30 P3 or just G30 to do a single probe
Machine rehomes x and y, then does a jig to offset the probe vs nozzle and then probes at the home location.
After this, a re-issue of G0 to a target and a G30 P1 activates offset and probes correctly. And a G30 P2 deactivates offset after another probe.
Using probe type 2 and a x and y offset vs nozzle I can observe correct behavior of "G30 P1" which offsets the head before probing making the probe hit where nozzle was.
After then probing multiple points with "G30 P0" (with G0 commands between) the finishing "G30 P2" does not restore head position.
If script is rerun, the first probe ends up probing with no offsetting as it has already had the offset applied, but upon returning up from probe hit, it will move diagonally up offsetting the point again.
Rest of points continue as normal. This leads to a coordinate creep until system crashes in wall.
The text was updated successfully, but these errors were encountered: