At the start of a toolpath the other day the machine started at the Zero-point, moved to the plunge point and then immediately plunged too deep and through the material, moved about 1/4" and then came up to the proper height and cut the rest of the tool-path correctly. I've checked the GCODE and this plunge is not in the file. I also ran the tool-path twice more and it did NOT do the same errant plunge as the first run. Has anyone seen the controller do a random maneuver like this? I've attached a picture of the errant holes, at the top of the center hub. The piece is just a template for cutting other holes in the primary project, so it's not ruined but still annoying. The machine has been running flawlessly for about 2 months until this.
The machine needs to be homed before you run Gcode. Either homed with limit switches or use the 'fake the home' method if you have no switches. This is not optional. Home, Fusion360 and G53 Z moves How to 'Fake the home'
How is zeroing different than homing? I have always just zeroed the XYZ to the material using the probe. I'm just curious why it needs to be homed and zeroed. Thanks.
Homing sets a reference point in the MACHINE co-ordinate system - the back, right, up corner is set to the MAXIMUM dimension for each axis and is used as a reference point for all other coordinate systems. Zeroing XYZ sets a reference point (in the same place on your workpiece as you set the origin in your cam software) in a Workplace Coordinate System (WCS) so your controller "knows" where in the machine's workspace you put the workpiece. Alex.
Agreed, I guess I just don't see how not homing would cause the machine to plunge too deep when it wasn't in the GCODE. Also to do it randomly (1 out of 3 runs).
some Gcode moves are relative to home, that is why homing is important, as explained in the 2 links I gave you
Understood. Though from doing some reading it seems all GCODE commands are executed from the ZERO point. Here is the snippet of GCODE where it plunged too deeply, there doesn't seem to be anything that implies one command is from HOME vs ZERO (I'm not trying to be difficult; just trying to understand the process): G0X6.0000Y6.8162 G0Z1.0000 G0Z0.2000 G1Z0.0000F10.0 This is where it plunged too deeply G1X6.0802Y6.8123Z-0.0038
G53 commands operate with reference to home and add to that my apologies, I missed the randomness of it. random movements imply EMI or other communications failure, ie what the PC sent is not what the controller received. EMI docs:blackbox-x32:faq-emi [OpenBuilds Documentation] communications docs:blackbox-x32:faq-usb-connection-failed [OpenBuilds Documentation]
Hi Valin6210 When you had that end-mill plow right through the workpiece, did you press "return to zero" by any chance? (The question is only relevant however if you zeroed off the spoil board.)
PC vs Interface, same thing. In that context above EMI is EMI. Same corruption of electrical signals regardless where they originated. However EMI tends to be more random. Won't always be Z and only at the start of the job. Those symptoms makes it feel more like something in your zeroing procedure or something similar.
Not that I'm aware of. I always zero using the probe plate to the material (left, front, top of the material).
