Other than the crown, this is my first real Estlcam attempt… That line down the middle showed up at the end and is not supposed to be there. It’s not in the design and not in the gcode preview, so what gives?
That sucks. When someone posts the answer, I want to know too. It looks like ESTLCAM created a seam in the pattern. That’s a division of the pattern but ain’t got a clue why it did that.
That sucks. When someone posts the answer, I want to know too. It looks like ESTLCAM created a seam in the pattern. That’s a division of the pattern but ain’t got a clue why it did that. It looks like it continued your cut line from the above straight through into the center. You probably need to open the pattern back up and cut and delete that line. The code thinks it’s all part of the same cut.
Can you attach or link your gcode and what your end of job setting are in estlcam please.
I could be wrong, but I don’t think it’s a deliberate move in the gcode or it would show up in the preview. Not sure exactly when it happened, but I’m running it again to see if it’s a fluke and videoing to pinpoint the time if not. gcode attached. I didn’t do anything special for end of job that I’m aware of.
Aztec-Calender-Ring1.gcode (1.77 MB)
Clearly, just posting problems here is sometimes enough to solve the problem.
Any chance this crept in during the tool change?
It was the will of the machine gods. Lol. Best to run a styrofoam blank first, then your wood. Cheaper and easier. Glad it’s fixed.
I know, right?
I don’t think it was the tool change as it ran with no issues for quite some time after that, but who knows. This second time around I split it into two separate programs because the logistics of the tool change just made it easier that way.
I don’t have a lot of confidence running the entire calendar at this point as that is waaaaay bigger than this little portion I’m practicing with. It’s taking forever just to select all the curves in Estlcam. There has to be a better way without spending $400 on VCarve. I can’t believe Fusion 360 isn’t capable of this task.
I had something similar happen to me a while back with using estlcam, but after looking for problems on my MPCNC, it seemed to have slipped in the Z-axis. The part that held the Z-nut was my problem. That was when I was using the older design. I have not had that problem since upgrading to newer design & M8 threaded rod.
The gcode has many instances where the Z is given a movement and only “F” for speed, The “F” should always have an actual speed attached (F480 for instance for 480mm/min) and I’m not really sure what’s going to happen when it’s not included, it might be taken as a zero, might be taken as infinite and might be taken as the first byte of the next command… Double check all your ESTLCAM settings to find out where it’s not being set.