Blackbox 32 Openbuilds control R7 Vectric aspire for gcode I home the machine and set xyz to zero. I probe with the open builds probe. When I run the gcode it raises the z and executes the program but the z is way too high. This same code was working when I used it a month ago. I am working with a 3/4 piece of mdf. T1 G17 G20 G90 G0Z0.8000 G0X0.0000Y0.0000 S16000M3 G0X3.9330Y10.0384Z0.2000 G1Z0.0000F15.0 G1X3.7850Y10.0007Z-0.0134 G1X3.7513Y9.9920Z-0.0164 G1X3.7176Y9.9829Z-0.0195 G1X3.6840Y9.9736Z-0.0225 G1X3.6505Y9.9640Z-0.0256 G1X3.6171Y9.9541Z-0.0286
obviously the probe did not set Z zero at the surface of the material. which exact probe option did you use? if you click 'gotoZero' does it go to the correct 0,0,0 position on the material?
goto work zero sends it to the correct position on the material. running the code causes it to lift the z axis and start cutting air.
As @David the swarfer said plus, if you are setting XYZ zero immediately after homing that is not necessary. Homing sets your machine coordinates system and probing will set the workplace coordinate system zero. Alex.
Probing correct then Can you hear Z suffering, stalling, grinding or anything during Z moves? Anything loose or binding? Z-Axes acceleration/max rate tuned for reliability? Newly set up machine - or old setup with new issues?
Any recent changes, like installing a new controller, new version of a CAM application, anything at all? Grbl Settings backup for review? (CONTROL > Grbl settings tab > Backup Settings button on main toolbar)
No hardware or software changes. Working zero is going to the front, left with the z touching the top of the work piece.
Yes indeed Craig. If it's set to "zero" off the bed but probed off the material surface, then you will get the exact problem that the OP describes. He hasn't actually stated that he's checked that setting in Vectric so who knows.
