Got my shapeoko pro xxl late last year. Have been using it and the only issues that have come up have been obvious user error.
Until yesterday. Out of nowhere the machine will not keep my set Z axis zero.
This is what occurs:
Initialize the machine w/bitsetter and the bit I intend to use.
Set XYZ zero on my piece of wood.
Load gcode for project and it again does the bitsetter routine.
Start program and it plunges way to deep into wood.
I check the Z axis zero and it is 9mm off. (9mm shows on the zero page of carbide motion when put back where I originally zeroed)
I have duplicated this multiple times with different gcode. Gcode that has been used prior with no issues. The only way to fix it, and this really doesn’t make sense to me, is too reset the bitsetter’s XY location. Then it will work for one job before adding the 9mm in Z axis error again.
Shapeoko pro xxl, Vcarve, Carbide motion, all Amana bits w/tool files
Do you hear an awful noise when the machine tries to retract?
Please take photos of your Z-axis motor wiring, including the connectors for the wiring extension, including at the controller and send them to support@carbide3d.com
Unfortunately it doesn’t appear that the issue is with the workflow. It has happened after initializing with the same tool that the job required. So not only does the tool get measured during the initialization process, but also at the start of the job.
To answer the question about what it sounds like, it sounds fine. No difference from day 1. I’ll get pictures once home from work.
9mm z axis discrepancy when it does happen and resetting the bitsetter XY fixes it for at least one job.
I do not know if it makes any difference, but I ALWAYS set Z after the file is loaded. Not so much the XY since I have always used the same reference point and that never seems to change unless the material is place somewhere different on the waste board.
I’m pretty sure loading the file is just filling a bucket with gcode that is later poured down the pipe to the machine (CM is written by plumbers, evidently )
The contents of the loaded file don’t appear affect anything to do with zeros or bitsetter state.
This happens to me periodically as well and for some reason I also get 9mm difference. However, I have no way to replicate it and it does it absolutely randomly for me. Carbide has replaced my cables on multiple occasions and the issue still randomly occurs. I have ruled out workflow error with bitsetter and did have a separate issue where it used to plunge down into the work piece and ruin it but new cables eliminated that. I have kind of just given up at this point since it never plunges down anymore for me, it is always 9mm above, so more annoying and a waste of time with having to reset zero than anything else.
Well shoot. I guess what I am going to do in the future is initialize the machine with the tool I intend to use, zero on my project, then click tool change (not actually changing tool) to hit the Bitsetter again. Then move to the previous set XYZ zero and see if the Z stops at 6mm above the project. This doesn’t guarantee anything once I run the program but at least another check before I ruin a project and break a bit again.
Yeah, you can do that but honestly I have tried just about every iteration but then once I hit start and it does its sequence with the bit setter it loses zero on z and air cuts. I can’t pin point where in the process after hitting start that happens though
I can share my gcode for the most recent projects I had it happen on when I get home. For additional information I generally use Vcarve Desktop for CAD and Carbide Motion for CAM. I also use your post processor for Vcarve. My stock has varied in thickness but generally is ~ .5" - 1.5" depending when on CNC. I always zero from top of material and unless I plan to cut through I will just measure with a ruler, otherwise I use calipers to get the most accurate measurement for thickness.
I also have the same issue of not keeping z-0 I’m 95% sure it’s a carbide motion issue.
Reasoning is simple. It had been many months since I had updated it and all was fine. After update, this started happening. No other changes were made in between to machine or the g-code file I’m using. I’m also having issues where if I navigate the software a bit into jog and back into run, it occasionally forces me to reinitialize the machine.
It’s just a buggy version. @carbide3D is probably on it.
Had this EXACT same thing happen to me today. 9MM deep right into the project! It was my very firsr time using my new bitsetter, so i thought maybe i just did something out of order.
Started completley over and ran the project again. Worked fine the second time. I didn’t do anything different the second time, from the first.
Check to make sure your router isn’t loose. I pressed the power button on mine the other day and noticed it rotate slightly. Not sure why the screws loosened but might be something for you to check.
)