Skip to content
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

Closed
jukindle opened this issue May 19, 2020 · 4 comments
Closed

Feature for Multizone configuration #36

jukindle opened this issue May 19, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@jukindle
Copy link
Contributor

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.

@MTrab MTrab added the enhancement New feature or request label May 25, 2020
@MTrab
Copy link
Owner

MTrab commented May 25, 2020

Noted for future enhancement

@vistalba
Copy link

@jukindle

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)

@MTrab
Copy link
Owner

MTrab commented May 26, 2020

Remember - too many concurrent commands within 10 minutes will get you banned!

@jukindle
Copy link
Contributor Author

jukindle commented Jun 3, 2020

@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!

MTrab added a commit that referenced this issue Jul 29, 2020
Added support for miltizone configuration ( issue #36 )
@MTrab MTrab closed this as completed Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants