January 10, 2019 at 8:24 pm #83186
I’ve been hoping to have more time to experiment and troubleshoot and figure this out on my own, but I haven’t had that time, so I’m throwing this out here.
When I was making my daughter’s hot glue gun stand, I used the MPCNC to engrave a horse image on the front. For this, the 0/0 location was at the center bottom of the image. This was so I could zero the MPCNC at the center of the front edge of the board. This worked out just fine.
I also pocketed a square for a ceramic tile to catch the glue ooze. For this, I set zero point in the center of the square. I laid out the square on the board, zeroed the CNC at the center point of the square. But this cut did not work so well.
Every cut with a negative X or Y coordinate made a fast move from 0/0 to that coordinate, then back. The positive X/Y coordinate movements were just as they should have been. And the further out from center it got, the more aggressive the negative coordinate movement got. It didn’t take long for me to shut it off. I just happened to be recording it as it was my first non-test project.
To successfully make this pocket, I had to remake the gcode file with the zero point at the lower left so all coordinates were positive. Why would one operation have handled negative coordinates just fine, but the other one spaz out? I can’t think of any changes I made in Estlcam between operations, but maybe I’m forgetting something I did?January 10, 2019 at 9:19 pm #83190
That is something different all together. Are your LCD wires bundled with other wires? I have never seen that but looks like some sort of line noise or something.January 11, 2019 at 9:42 am #83279
Zip the gcode and attach it here. Maybe something in that will tell us what’s wrong. If it’s as Ryan suggests the gcode will be fine.January 11, 2019 at 10:27 am #83303
No, the LCD wires aren’t bundled with anything else. I do think it was something with the file. I haven’t had any kind of issue like this since, but I haven’t tried setting 0 anywhere but the lower left so all coordinates would be positive. Unfortunately, when I re-created the file I saved it as the same file name so can’t go back and examine that gcode file.
I thought each negative movement was going to X0/Y0 like spokes on a wheel, but watching it closer now it’s only doing that in quadrant 3 (X-/Y-). In quadrant 1 (X+/Y+) it behaves normally. In quadrant 2 (X-/Y+) it is making horizontal movements perpendicular to the Y axis. In quadrant 4 (X+/Y-) it is making vertical movements perpendicular to the X axis. So it’s like it only has a problem with whichever coordinate is negative and has to go back to 0 location for that particular axis after each movement. Movement in quadrant 3 was particularly problematic since both axis were negative.
You must be logged in to reply to this topic.