New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature for Multizone configuration #36
Comments
Noted for future enhancement |
May you could use NodeRed for this: Start Landroid -> Wait 3 Seconds (or how long it takes to leave homebase) -> Pause Landroid -> Landroid Home -> Wait N Seconds (how long does it take if the Landroid is following the wire until the point you want to start mowing?) -> Pause Landroid -> Start Landroid (should begin mowing from this point) |
Remember - too many concurrent commands within 10 minutes will get you banned! |
@vistalba nice idea! However, if your robot sometimes gets stuck on its path and needs to free itself, it gets biased. As far as I know, the multizone feature uses actual wheel odometry (which is quite good) to measure distance instead of time. I'll try it anyway :) thanks! |
Added support for miltizone configuration ( issue #36 )
Hi! It would be really nice to have the possibility to update the multizone scheduling (the probabilities which can be set). Since there is no possibility to command the robot directly to a specific zone, my plan is to adjust the probability distribution of the zones to 100% for a specific zone before I start the robot.
I would have loved to implement it myself and do a pull request, but I was unable to figure out where the actual update request is done in decompiled smali code.
The text was updated successfully, but these errors were encountered: