Scheduling fails after a stall

If I get a stall on the x axis, usually something stuck on the rails, the scheduler fails to run. The scheduled events show up and when the time comes, they just disappear. I have deleted and recreated the events but that does not help. I have to reboot the system and everything starts working fine. It seems to have started in the last 2-3 months. The system is several years old and has been working fine. It is a genesis XL version 1.5. The software is up to date.

Hi @ldgaley hope you don’t mind the obvious questions :slight_smile:

  • Was the device E-stopped following the X-axis stall ?
  • Did you perform UNLOCK before next scheduled Events were due ?

A snippet of or a picture of the Logs around a Stall occurrence might be informative.

It was e-stopped, I unlocked it, cleaned off the rails, moved it back and forth to make sure it was clear, sent it back to home. The only message was ‘stall detected on x-axis’ and later when I cleared it ‘unlocked’. I watched it when the next event was scheduled and nothing moved and the event just went away. This has happened 3 times in the last 3 months.

Interesting… and all following scheduled events also ‘went away’ ?

yes- the schedule showed all of the future events, and when the time came, they just went away as if they were run.

Ok… I’ll try to reproduce this issue.

Edit:
Could not reproduce.

  • Scheduled Sequence Execution encountering Stall stopped before completion (good !).
  • Allowed next Execution to run (to make sure it ‘went away’, and it DID)
  • Prior to Execution after that I hit E-STOP followed by UNLOCK and waited . . .
  • Next Execution ran normally

Maybe we need additional detail(s) or Logs in your case ?

interesting- I will play around with it and manually stall it to see the results- there is nothing in the logs that show anything. Is there any other diagnostics I can try?

And I can’t recreate the problem manually. I’m beginning to think it might be a power problem. I had the network repeater fail around the same time. I have placed a power monitor on the outlet to see if there are any issues. The farmbot is powered by cables that run underground thru several outlets. The voltage reads ok but I wonder if there are any spikes happening. Thanks for the effort. I will be monitoring it closely and will let you know.

1 Like

Not any I know about . . except building your own FBOS with SSH added in so that you can get to the Elixir “console” … that gives you a little more logging than the WebApp gives and also allows you to “poke around” inside FBOS to debug stuff. :wink:

Edit: In the Settings panel for Error Handling there’s a toggle which enables E-STOP on movement error (Default: OFF) … which makes me wonder what state the whole Bot thinks it is in after an Axis Stall ? I’ll do some more work on this one …

I already have the e-stop on movement error set to yes- retries set to 3- if it happens again, before I unlock it, is there a way to see what state it thinks its in?

Not sure, that’s what I want to find out . .
So, in your “manual” testing, you only had to press UNLOCK to allow additional Event executions ?

yes- I held the gantry by hand, it stalled and e-stopped. I unlocked it, sent it back to home and then I set up an event to run in 5 minutes and it ran. As I’m thinking maybe I should et up an event before I stall it to see if it acts different.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.