After I home the gantry. I then run the break in and the y axis runs completely fine, but the x axis just barely passes the halfway. When it begins to go back to the top left corner, the x axis hits the stop at least 15 inches before the y axis. Also when jogging from the corner, on the Fire control app, it shows the x axis on zero. I move it towards the end and stops a bit before the half way line. Once it stops it shows that the x axis is now 47 and when i go back towards the zero the machine hits the corner and it says the x axis is 10.
Check to see if your coupler is slipping. I made marks on the lead screws and couplers to make sure it’s not slipping.
No, not slipping,
It give a Warning The loaded program extends beyond the machine travel limits
Check all your motor plugs on the electronic enclosure, Make sure they and seeded tight.
the retaining screws can sometime hold the connector somewhat out of the socket.
Did you ever solve this issue?
Welcome to the forum!
As you can see, the original poster (OP) did not provide any feedback on whether the problem was solved or not. This doesn’t help anyone. If you’re experiencing the same problem, I suspect the solution suggested by @TinWhisperer was correct as it’s a common problem. If this works for you, let us know. If you still have a problem, start a new thread and you’ll be sure to get help.
2 Likes
It sounds as though the OP was experiencing slipping of the motor coupler on the X axis.
If the X axis binds and the motor coupler slips, Firecontrol still thinks the axis has continued moving, since the motor is still turning. This causes Firecontrol to think the X has traveled further than it actually did.
For example, the X binds and stops at 24", but the motor coupler slips and Firecontrol thinks the X has gone 47". When it goes back the other way, it thinks it needs to go 47" to get back to zero, but it is only 24" from zero. This will cause it to crash.
It’s ironic that the addition of limit switches has caused the very problem it’s supposed to prevent.
I’ve been happily running my table for 3 years without them.
- Note that this can still occur even if the coupler does not slip. Firecontrol only knows that it commanded the stepper to make a certain number of steps, but there is no way for it to know if those steps were completed.
3 Likes
I fixed my issues. It ended up being the dip switch on my x drive. The #2 pin wasn’t flipped from the factory like all the other drives. I flipped it and bam full speed no more problems.
2 Likes
@Devorak101 - Thank you for posting your solution!
1 Like