After sending a homing command to a particular axis, 2/3 of the time the actuators will behave correctly, but about 1/3 of the time the actuator will hit the switch, stutter for a second, then continue moving in the direction of the switch at search velocity until either the switch is released (because I moved it) or the stop command is given (!%). It does not then change direction and move at latch velocity after the switch is released. If I send a homing command for all three axes, this issue tends to happen with the third (y) axis.
tinyG or G2?
What sort of switches(mechanical, proximity, etc)?
Shielded wiring used to switches?
Shields grounded properly?
Post your parameter set to a cloud file and provide a URL.
I have experienced the same thing with my Y axis. If the gantry is too close to my mechanical limit switches when i try to home it (approximately within 150mm), it hits the limit and tries to keep going until i kill it.
I notice that when I pull my y axis back further than 150 or 200mm and start the G28.2 homing command, it goes for about 20mm and then the motor pair makes a blip sound almost as though it's doing an instantaneous stop start. As long as it does this, it will consistently stop when it hits the limit switch. Odd I know, but I have not tried to figure out there logic there yet.
Odd behavior indeed.
What are you using to communicate with your machine? Chilipeppr/CoolTerm, ?
Posting your parameter set ($$ dump) to a cloud drive and providing a URL will tell us a lot about your machine and short-cut a whole bunch of questions.
This topic is from the original forum (August 2016). Your reply starts a new discussion linked to it.