We added pretty rigorous guard rails to prevent the machine from doing anything if something is off. They worked really well to massively reduce the number of folks breaking belts, but now we’re seeing people get stuck in the frustrating situation where the machine won’t let them do anything because something is just slightly off.
Should we be making it easier to get up and running even if the anchor locations aren’t great? Maybe with a warning popup saying that something is off, but you can still use the machine?
I think you could lower guards a bit, we need to identify why some these failures are happening. @Smiley was working until recently. My experience running different yaml settings for initial anchor points indicates something is wrong in the initial waypoints calculation.
That is a good point, we do want to identify what is going on.
I think that the new math should be much less impacted by what the initial settings in the .yaml file are at the beginning which might help with some of these.
I think that some of them are a combination of other small factors adding up like frame flex or the spoil board thickness being set incorrectly.