I am having an issue with auto level when it comes to actual milling.
I run the test probe and auto levels fine. I then send the auto leveled Gcode to the workspace and it says “no units found in Gcode,” so I tell it to use mm. Then when I run the Gcode, the spindle speeds up and the vbit immediately proceeds to plunge down through both the FR-4 and waste board.
I have run this Gcode before without the autoleveling so I know the original code is not the problem.
I thought perhaps it might be related to zeroing out before auto leveling? I have been zeroing all three axes first, then returning to zero after auto level is complete.
Yes, zeroing out is the right approach. The auto-level also does it’s own zeroing out when it does the first point. That becomes it’s reference for all subsequent points.
Seeing a Z of -34 is wrong. That would shove 34 mm into the workpiece. Are you using work coordinate systems or something like that such that it would throw off the Z values? You can see on line 24 it goes to Z 0 correctly.
What I really need is a screenshot of chilipeppr to see the 3d rendering of the auto-level. I bet that too is showing -34 roughly as the range of the points.
N24 G1 F80.00Z0.0000 (al new z)
N25 G0 Z1.9990 (al z mod 1.999)
M3 S10000
N27 G0 X2.4438 Y3.4351 Z-34.2447 (al new z)
Yeah, that’s crazy wrong. Each location should be in the 0.0xx range. When you watch it do it’s thing, when does the number jump so high? Are you using an electronic touch plate? Or a pressure switch?
I can watch for the jump in numbers the next time I run the test. I’m new to auto-leveling and honestly was just excited to see it working.
I’m using the same board that I am trying to mill. I initially milled one without auto-leveling and was hoping to make another using that feature to create a nicer looking board, as the first one came out a bit crude looking.
