ive been working with this lead 1515 for a while, and even though im definitely not an expert, ive been able to produce what i needed with remarkably few mishaps using sketchup with the sketchucam plugin, and ive been able to fix most issues ive encountered because they were file related, not the actual machine. however somebody else messed with the machine and now its doing all sorts of gobbledegook and im not experienced enough to know how to fix it, or even whats causing it. the person who messed with it knows enough (much more than me) to **** it up, but not enough to correct his mistake. he also lacks the wisdom to just let things be that arent broken, and will likely mess with the machine again. i need the knowledge to fix these, and i dont even know where to start. lv_0_20241113181805 demonstrating the most importand issue, some kind of binding, despite the x axis being perfectly functional during a jog. no other cut file from the same source has this issue, and the y axis also did this on the same cut file in the same spot (tried it twice), so i re-exported it, resulting in the issue seen. no other cut files have had this problem. 20241113_175146 shows the jog timing out or something while i was holding the button down. not an important issue, but while this issue persists, jackass will continue to mess with the machine. 20241113_175007 shows the homing function coming short and throwing an error code. i dont know where to fix it, but having a name is at least nice. again, not the worst issue, but jackassery persists. the image is the result of one side of the y axis binding during a job. on the second try, the machine bound in the exact same spot, leading me to believe it could be a file issue, but nothing i tried on the generating end has netted better results.
no binding, did you read the error message? it said 'error 3 reset while in motion', binding will not cause that, but wiring/power supply/EMI issues will. Unless what I am seeing is the result of you resetting after it stopped, in which case what was the error message in the console BEFORE you reset it? It sounds like it is decelerating to a normal stop rather than binding which would cause many more interesting grinding noises, together with skewing the Y which I did not see. It says it cannot find the end points in the distance it thinks it should try. It gets that distance from the 'max travel' settings in GRBL. (you should read thwe entire GRBL wiki, knowledge is power!) I suggest making a backup of the settings and posting them here, while at the same time checking that the max travel settings ($130-$132) match the size of the machine. If the mechanics bind in the same spot every time, it is probably mechanical..... if it stops only one side, it CANNOT be the Gcode since the code is not in control of the 2 sides of the Y independantly, they are linked internally by a physcial piece of wire. Clean the wheels/rails/leadscrews, binding is most often just dirt (which the router generates in mass quantities). A bit of dry teflon on the clean leadscrews won't hurt. If everything is clean and adjusted correctly, and one side of Y still stops in the same place, then look at wiring. Since the machine has been operating for some time, one of the motor wires may have fatigued off and be disconnecting when it moves in that area. If that is not it, then slow down the max rate and acceleration for Y and see if that fixes it (would be handy to know if the motion when it stops is a rapid or a cut). In this case this points to still having binding in that area, either dirt or bent leadscrew or damaged rail that is causing a sudden increase in resistance at that spot. Overall i'd guess that your fiddling man has tried to make it go faster and upped the maxrates and accelerations to where the mechanics cannot cope. This is where a backup of the settings from when it was working perfectly would come in handy, and would also solve any future fiddling. Just restore and carry on. You can attach one of your Gcode files so we can check it too if you like.
