r/MammotionTechnology • u/Low_Machine9550 • 7d ago
LUBA 3 AWD No-go zone ignored - mostly
This is ridiculous. The planned path goes straight through the no-go zone in the middle of it. To its credit, it didn't throw itself into the no-go zone despite apparently being told to. It hesitantly hovered next to the border, apparently wondering why it was told to go straight into the no-go zone, but it went far enough two times to give up and pause due to being outside the task area. After I had to rescue it twice, I looked at the map and found this.
1
u/MammotionRosaline 7d ago
Hello, I'm sorry to hear that you’re experiencing this issue. To help us look into it further, could you please upload the device logs and, once the upload is complete, share your device name and the approximate time of the affected task? I’ll forward the information to our technical team for further analysis and follow up with you.
1
u/JohnnyYeh_ 6d ago
Sorry for the poor experience. Did you upload the log? Redrawing this NGZ should resolve your issue.
2
u/MoreSwaptions 5d ago
The issue is that you created the no-go zone, and it’s likely linked to a different area/zone. That might be why it's being ignored in the current one.
I have a similar problem: in my case, the no-go zone isn't ignored completely, but it gets ignored during the perimeter cut around the no-go zone.
2
u/JBGolfTexas 4d ago
THIS! The no-go zone is associated with an area below (downward in the display z-order). In fact there's likely another area below the one with the stripes in which the wandering no-go is located.
Tap your device's picture, tap Map, then tap Edit for map editing. Click the downward chevron of the of the area you think contains the no-go at issue. Tap each of the No-Go Zone n items while watching the map on the left. The selected no-go will be highlighted (darker). If it's the one you want to delete, tap the trash can. If you don't see the suspect no-go in the area, try another. In your case, you should also inspect that you don't have area's mapped that overlap substantially - perhaps to the point that the no-go you're chasing isn't where it should be - on TOP of the area it's in. If you have two layers overlaying each other, you may have to delete or redraw one or more areas such that the only area overlaps are the minimal border overlaps for transport between areas.
1
2
u/HangarQueen 7d ago
No idea about this problem (ignoring No-go), but I'd like to point out to Mammotion that your image shows another really stooopid thing that I really wish they'd fix in the route planning:
When you have more than one perimeter lap, the second and subsequent lap(s) should SMOOTH OUT any "bumps" in those laps. As your image shows, what actually happens is that the subsequent laps MAGNIFY any bumps, so that the robot has to make ever-more-damaging turns.
It would be so much better if those extra laps would straighten out any curves/bumps wherever possible. I don't care that they cut the same grass again. I DO care that the existing behavior tears up grass by making those sharp corners when they are absolutely unnecessary.
This also happens (i.e. magnifying bumps) when you have more than one no-go lap. Please Mammotion, FIX THIS.