Yesterday, life got in the way and I didn’t get time to fault find the Farmbot. This morning I started yesterday’s fault finding. I performed a reset of the Raspberry Pi using the “restart Farbot” option in the Device page of the web app, then used the “find home” options for Z, Y and X in the Device page of the web app. I then ran the sequences (pick up watering tool, put away watering tool), which completed with no errors.
It looked like there were no hardware errors, so I then sucessfully completed a watering sequence.
I then told the Farmbot to start one sequence, and while it was executing, I told the Farmbot to start another sequence.
This totally threw a spanner in the works, the farmbot behaved erratically, got the various stages of the sequences out of order etc.
I have deduced from this that there must be no mechanism for the Farmbot to queue up sequences.
This was not really unexpected, and during nomal operation wouldn’t happen as long as my schedule allows time for each sequence to complete before another starts.