I have a sequence that turns the water on and off.
Then I have a sequence that moves to various spots and then calls the watering one.
The first watering sequence fails, but it works for the other 3 in the overall sequence.
I just noticed that I did have a “take picture” step in the water current spot sequence - maybe that caused the issue.
A post was split to a new topic:
Absolute movement command failed
@kimptoc did you have a look here, seems like a problem I already encountered:
I strongly disagree because I feared that problem and it was affirmed:
This is one more nice example why you really need to program in order to not let the user use the system in a way which
it wasn´t programmed for… -.-
08:25PM - 10 Jun 17 UTC
10:35PM - 10 Jun 17 UTC
I think I noticed that if you are logged in with more than one device, the system gets confused.
This article guides you through troubleshooting movement issues. You’ll start troubleshooting with simple actions. If these don’t work for you, you’ll continue down this guide and perform increasingly invasive actions to troubleshoot your problem. So test your setup after completing each step to verify if your problem is solved.
Make sure your FarmBot receives your commands
FarmBot communicates with the front-end at
https://my.farmbot.io. If your bot has connected, this website should confirm t…
For some reason my vacuum switch off command did not come through in 2 or 3 of 24 times I tried this in a sequence.
Seems to need a little bit more debugging…
@Klimbim - but I think its a different issue. The movements are working ok, its just the pin off/on for the watering that seems to fail.
Seems to consistently be the first watering in the sequence, will try a dummy watering at the start to bypass it
I’ve taken out the “take photo” step and seems to be more reliable.