I’m not sure how to explain this so I’ll do my best with an example case.
A sequence called mount soil sensor with the steps
Find home
Move to Soil Sensor location (35, 351, -372) but stop at 25mm above tool)
Move to Soil Sensor location at 50% speed
Move X axis +100mm.
It’s basically, if not exactly, an example sequence for getting started. The problem is it targets 35, 351, -348 but stops maybe at -254 (z-axis) in the real world but the app keeps going to 267, 284, 302, etc. After 5 seconds or so, the app changes the coordinates back to -254 where it originally stopped. Then moves to the next step of moving 25mm down at 50% speed as if it were at -348. Another way to put it, it completes the sequence at -254mm instead of -348. Sometimes this happens on the y-axis as well. It’s not consistent enough to say there is an obstruction. It’ll stop at different locations then sometimes no issues or a different axis stalls instead. Since the app catches up eventually, I don’t suspect the encoders are faulty. And it wasn’t happening as often when picking up the watering tool with the same sequence. Any suggestions what could cause it to A) stop on the way to a destination, and B) force the farmbot to try again to get to the destination before proceeding if it didn’t make it?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.