My last video: ruclips.net/video/c6Qt7u4TxvM/видео.html Luba playlist: ruclips.net/p/PLw2G9IcmMhHqw_qPhsyIrPPtJ5WYIYqRX If you find my videos helpful, I would appreciate a vote before the end of May. No signup or personal info, just two taps: cont.st/uZnrsv_nThtij?g=1
OMG, you explained what I've been seeing -- by accident. When I first got my Luba and set up the RTK and dock placement, the first area that I mapped was a distance away from the dock. So I had to make a channel to it of course, and I chose the channel to coincide with a concrete curved pathway so it wouldn't leave ruts on the grass. I tested that it could go from the charger to my new area, following the channel/pathway, and had it cut that area. But then, in a hurry to continue mapping my entire yard, I next manually mapped the area adjacent to the charger, which was of course "over top" of the sidewalk channel that I'd created earlier. You can't SEE that channel underneath the area anymore. Sure enough, the Luba will accurately follow that hidden channel along the pathway when it moves to cut the first area that I'd mapped, but when it's finished and returning to charge, it takes a direct route across the grass to the charger (and wearing ruts). Now that you've taken the time to explain things (thank you!), I'll go out and delete that area closest to the charger, send the Luba to cut the first area (along the pathway), make sure I send it back to charge again, test it both ways again, and then finally re-map the area closest to the charger again. Whew! There really ought to be a way to map a channel ON TOP of an existing area, but your hack seems like it should work (albeit with additional work on my part). Thanks again.
Wonderful to know I'm not crazy! Thanks for sharing! Let me know if your plan works. it's possible you will need to delete the channel and redo it and retest it to make it work. But I have no idea, we're sort of in "glitch" land, but I know that once it starts working, it's never stopped working. But yeah, if you could come back and say if you had to delete the channel or not that might helps others int eh same boat. I agree, they really need to let you make a channel on top of the other one and show it that way on the map!
@@RobotMowerTricks Alas, my testing of this was unsuccessful. But I have a weird topology. Your trick may hopefully work for others. I deleted the area close to the charger. The channel (following my concrete pathway) showed up again. And curiously, I can't find any way to DELETE a channel! Only by defining a NEW channel between the SAME areas. (And another wish I have on my list is to ALLOW multiple channels between areas, so we'd really need a DELETE CHANNEL capability. But I diverge.) I ran the Luba out to mow the connected area, aborted the mowing, and told her to recharge. She followed the channel/pathway perfectly both ways. I created two more channels for two more areas, along the SAME pathway back to the charger, and again sent Luba to mow and return on each of these. She behaved perfectly. But once I recreated the area closest to the charger, which is "over top of" these channels, the behavior changed. And Luba is now somewhat confused upon exiting the dock, now that I have three channels converging there. She eventually figures out the right way to go, but unfortunately doesn't follow the pathway to any of the three areas. Now the curious thing is that she DOES follow the very first channel that I created back to the charger. But not for the others. I'm thinking that I'm totally bamboozling the software by having three channels "on top" of one another, and then an area on top of all three. Anyway, it was a fun exercise, but didn't work for ME. Your mileage may vary.
@@HangarQueen so you'll need to delete the channels anyway to stop the odd driving. (you do that by tapping map, edit, finding the area and tapping the down arrow and you'll see channels and no go zones in that area. You can delete them individually.) I suspect that if you delete all the channels and retest it'll work.
@@RobotMowerTricks Dang, I never noticed that sneaky "down arrow" under the areas in map editing ... which as you say allows channel and no-go deletions. Thanks for the pointer. (And now I need to update my "Issues and Wishes" document, as it's currently suggesting that this capability is needed.) I'll see if I can find some time to get out there to delete and re-test later today. Thanks again.
Thanks for the suggestion! I will be trying this out in the coming weeks. You're right - sucks that I will have to delete the zone adjacent to the charger, but it's a price I'm willing to pay in exchange for reducing the ruts in front of the charger.
I’m mowing the full 2.5 acres. My house is at the center and my task areas are like the slices of a pie or pizza. Not ideal, but I’m working at optimizing things for most efficient mowing. The app is buggy as hell. Sometimes I have to force it to refresh by closing the app and reopening. I forget what changes I made the other day that weren’t reflected when I was setting up a task. For those changes to be acknowledged I had to power down my phone and restart phone and the app. Is anyone using their iPhone and iPad interchangeably to control their Luba? I picked up my iPad the other day and the app was only recognizing 2 of my 12 task areas and I didn’t take the time to fiddle with it. So I set down the iPad and went back to the iPhone.
I don't have any IOS devices, but I've used my old phone and it worked fine. All the maps are stored on Luba, so if it isn't loading the map right, it's an issue with it fetching the map from your mower. Maybe an IOS glitch, maybe a network glitch, maybe Luba just needs to be turned off, pull the key, sit for 5 minutes, turn it back on, let it sit for 5 minutes again. The app is buggy, I do have to close it out of memory fairly often, but the mower itself has finally been solid since the last update. I have not had to do a remote rescue since then. Upload a lot of logs for every problem you have, and they might just be fixed in the next update.
It makes sense, it goes into the first zone and follows the perimeter to the channel and crosses to the second zone then follows the perimeter again to the area it mows
I understand it will only delete the no mow zone I want to delete - then I can create a new no mow zone around my ditch culvert pipe which as of now is to close at 6 inches and Luba 2 will slide backwards into the culvert. Thank you for your help - I love the machine but the word delete scares me - Thanks again !!!
You're welcome, I hope it works for you! If you could help me out with a vote, I'd really appreciate it. No personal info, just tap vote then tap it again after it says "success". I'm trying to get enough votes so mammotion can't ignore honest reviewers. cont.st/uZnrsv_nThtij?g=1
The drop down arrow. I can't leave pics in comments, but that's always the key people are missing. Go to edit, find the area that has the no-go zone, and tap the down arrow to see the channels and no-go zones in that area.
@@ipodman1910 I'm in the beta group, and so far they only have random cutting angle as a feature, and it has issues. I'm not sure how many people want their yard cut at a random angle. Random driving paths would be much better.
You cannot map channels until you map areas. I thought about making a beginners guide to mapping, but I felt like this is for advanced users who already have maps and understand the weird things Luba is doing. The beginner's guide is that you need to pick how many areas you divide your lawn into, then map the furthest area first, draw a channel, and let Luba use it both ways. Repeat in the order furthest-nearest, getting closer to the charger each time.
@@RobotMowerTricks Thanks for this. My Luba is due to arrive tomorrow and I will keep track of how I set things up. One of my channels will overlap with another but the end points are different so I don't foresee a problem on that front. I'm terribly excited about not having to mow the lawn regularly - fingers cross it all works well!
@@charleswheatcroft Enjoy! Overlapping channels should not be an issue, I've seen screenshots of that. It might be best to map zones as large as possible (but also 1 foot away from rocks/walls and let luba put down straight lines for you to use as a guide when you remap once you see what you'd like to change. Also you can us FPV to watch luba drive perimeter laps to see if it's going to hit something. You can pause it, take note of the percent complete, then end the task, edit map, and start another task using the "start percent" option to jump ahead to where the problem/edit is.
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
My last video: ruclips.net/video/c6Qt7u4TxvM/видео.html
Luba playlist: ruclips.net/p/PLw2G9IcmMhHqw_qPhsyIrPPtJ5WYIYqRX
If you find my videos helpful, I would appreciate a vote before the end of May. No signup or personal info, just two taps: cont.st/uZnrsv_nThtij?g=1
OMG, you explained what I've been seeing -- by accident. When I first got my Luba and set up the RTK and dock placement, the first area that I mapped was a distance away from the dock. So I had to make a channel to it of course, and I chose the channel to coincide with a concrete curved pathway so it wouldn't leave ruts on the grass. I tested that it could go from the charger to my new area, following the channel/pathway, and had it cut that area. But then, in a hurry to continue mapping my entire yard, I next manually mapped the area adjacent to the charger, which was of course "over top" of the sidewalk channel that I'd created earlier. You can't SEE that channel underneath the area anymore.
Sure enough, the Luba will accurately follow that hidden channel along the pathway when it moves to cut the first area that I'd mapped, but when it's finished and returning to charge, it takes a direct route across the grass to the charger (and wearing ruts).
Now that you've taken the time to explain things (thank you!), I'll go out and delete that area closest to the charger, send the Luba to cut the first area (along the pathway), make sure I send it back to charge again, test it both ways again, and then finally re-map the area closest to the charger again. Whew!
There really ought to be a way to map a channel ON TOP of an existing area, but your hack seems like it should work (albeit with additional work on my part). Thanks again.
Wonderful to know I'm not crazy! Thanks for sharing! Let me know if your plan works. it's possible you will need to delete the channel and redo it and retest it to make it work. But I have no idea, we're sort of in "glitch" land, but I know that once it starts working, it's never stopped working.
But yeah, if you could come back and say if you had to delete the channel or not that might helps others int eh same boat.
I agree, they really need to let you make a channel on top of the other one and show it that way on the map!
@@RobotMowerTricks Alas, my testing of this was unsuccessful. But I have a weird topology. Your trick may hopefully work for others. I deleted the area close to the charger. The channel (following my concrete pathway) showed up again. And curiously, I can't find any way to DELETE a channel! Only by defining a NEW channel between the SAME areas. (And another wish I have on my list is to ALLOW multiple channels between areas, so we'd really need a DELETE CHANNEL capability. But I diverge.) I ran the Luba out to mow the connected area, aborted the mowing, and told her to recharge. She followed the channel/pathway perfectly both ways. I created two more channels for two more areas, along the SAME pathway back to the charger, and again sent Luba to mow and return on each of these. She behaved perfectly. But once I recreated the area closest to the charger, which is "over top of" these channels, the behavior changed. And Luba is now somewhat confused upon exiting the dock, now that I have three channels converging there. She eventually figures out the right way to go, but unfortunately doesn't follow the pathway to any of the three areas. Now the curious thing is that she DOES follow the very first channel that I created back to the charger. But not for the others. I'm thinking that I'm totally bamboozling the software by having three channels "on top" of one another, and then an area on top of all three. Anyway, it was a fun exercise, but didn't work for ME. Your mileage may vary.
@@HangarQueen so you'll need to delete the channels anyway to stop the odd driving. (you do that by tapping map, edit, finding the area and tapping the down arrow and you'll see channels and no go zones in that area. You can delete them individually.)
I suspect that if you delete all the channels and retest it'll work.
@@RobotMowerTricks Dang, I never noticed that sneaky "down arrow" under the areas in map editing ... which as you say allows channel and no-go deletions. Thanks for the pointer. (And now I need to update my "Issues and Wishes" document, as it's currently suggesting that this capability is needed.)
I'll see if I can find some time to get out there to delete and re-test later today. Thanks again.
You're welcome! Let me know!
Thanks for the suggestion! I will be trying this out in the coming weeks. You're right - sucks that I will have to delete the zone adjacent to the charger, but it's a price I'm willing to pay in exchange for reducing the ruts in front of the charger.
I'm glad you found this useful enough to be wiling to try it!
...You never know how people will respond when you put stuff on the internet...
I’m mowing the full 2.5 acres.
My house is at the center and my task areas are like the slices of a pie or pizza.
Not ideal, but I’m working at optimizing things for most efficient mowing.
The app is buggy as hell. Sometimes I have to force it to refresh by closing the app and reopening.
I forget what changes I made the other day that weren’t reflected when I was setting up a task.
For those changes to be acknowledged I had to power down my phone and restart phone and the app.
Is anyone using their iPhone and iPad interchangeably to control their Luba?
I picked up my iPad the other day and the app was only recognizing 2 of my 12 task areas and I didn’t take the time to fiddle with it. So I set down the iPad and went back to the iPhone.
I don't have any IOS devices, but I've used my old phone and it worked fine. All the maps are stored on Luba, so if it isn't loading the map right, it's an issue with it fetching the map from your mower. Maybe an IOS glitch, maybe a network glitch, maybe Luba just needs to be turned off, pull the key, sit for 5 minutes, turn it back on, let it sit for 5 minutes again. The app is buggy, I do have to close it out of memory fairly often, but the mower itself has finally been solid since the last update. I have not had to do a remote rescue since then. Upload a lot of logs for every problem you have, and they might just be fixed in the next update.
It makes sense, it goes into the first zone and follows the perimeter to the channel and crosses to the second zone then follows the perimeter again to the area it mows
With all of the updates since this video was published, is this still the best way of minimizing ruts? Do you still have to delete all the maps?
I understand it will only delete the no mow zone I want to delete - then I can create a new no mow zone around my ditch culvert pipe which as of now is to close at 6 inches and Luba 2 will slide backwards into the culvert. Thank you for your help - I love the machine but the word delete scares me - Thanks again !!!
You're welcome, I hope it works for you!
If you could help me out with a vote, I'd really appreciate it. No personal info, just tap vote then tap it again after it says "success". I'm trying to get enough votes so mammotion can't ignore honest reviewers. cont.st/uZnrsv_nThtij?g=1
How do you delete a previous no mow zone and create a new one in the same area
The drop down arrow. I can't leave pics in comments, but that's always the key people are missing.
Go to edit, find the area that has the no-go zone, and tap the down arrow to see the channels and no-go zones in that area.
@@RobotMowerTricksgreat advice! An upgrade just came - let’s hope they introduce a randomised path to task area from charger. It’s the biggest issue.
@@ipodman1910 I'm in the beta group, and so far they only have random cutting angle as a feature, and it has issues. I'm not sure how many people want their yard cut at a random angle. Random driving paths would be much better.
@@RobotMowerTricks exactly!
So the moral of the story is map your channels first and let luba use it both ways before you map your task areas
You cannot map channels until you map areas. I thought about making a beginners guide to mapping, but I felt like this is for advanced users who already have maps and understand the weird things Luba is doing.
The beginner's guide is that you need to pick how many areas you divide your lawn into, then map the furthest area first, draw a channel, and let Luba use it both ways. Repeat in the order furthest-nearest, getting closer to the charger each time.
@@RobotMowerTricks Thanks for this.
My Luba is due to arrive tomorrow and I will keep track of how I set things up. One of my channels will overlap with another but the end points are different so I don't foresee a problem on that front.
I'm terribly excited about not having to mow the lawn regularly - fingers cross it all works well!
@@charleswheatcroft Enjoy! Overlapping channels should not be an issue, I've seen screenshots of that.
It might be best to map zones as large as possible (but also 1 foot away from rocks/walls and let luba put down straight lines for you to use as a guide when you remap once you see what you'd like to change. Also you can us FPV to watch luba drive perimeter laps to see if it's going to hit something. You can pause it, take note of the percent complete, then end the task, edit map, and start another task using the "start percent" option to jump ahead to where the problem/edit is.
very helpful!
Glad it was helpful!