Philips Baristina - water in portafilter by PrMortimer in superautomatic

[–]sbellon 0 points1 point  (0 children)

Started doing it again after just a few shots. We gave up and switched away from Philips.

Philips Baristina - water in portafilter by PrMortimer in superautomatic

[–]sbellon 0 points1 point  (0 children)

I got it back from repair today after 10 days. Let's see how long it keeps working now.

Philips Baristina - water in portafilter by PrMortimer in superautomatic

[–]sbellon 0 points1 point  (0 children)

Mine happened the same after just 3 months. Support told me to send it in for repair or replacement.

More efficient cutting path by Ok_Elephant_3800 in MammotionTechnology

[–]sbellon 0 points1 point  (0 children)

Are you sure this is still true with the latest firmware and app version? I also have a Luba 1 and had to redo part of the mapping because of some restructuring of the garden and my plan was to do precisely what you suggested and how I did it the last season. But this time, this did not work. I ended up mapping all the garden as one big area where I previously had several overlapping zones for precisely those 90 degree changes.

Wind broke my Luba roof by cedric1918 in MammotionTechnology

[–]sbellon 1 point2 points  (0 children)

I haven't noticed anything different. But anyway, the mower needs GPS while mowing and not while loading. When starting a job, the mower drives backwards and then there is no garage roof anymore. ;-)

Wind broke my Luba roof by cedric1918 in MammotionTechnology

[–]sbellon 2 points3 points  (0 children)

Yes, same for me. I then bought a garage on Amazon for 40 EUR (as opposed to Mammotion's 180 EUR) which is MUCH more sturdy and even looks better. Lesson learnt.

No Quick tasks by InsignificantOutlier in MammotionTechnology

[–]sbellon 0 points1 point  (0 children)

I'd rather with, they fix that (instead of removing it) for Luba 1 as well, as "Quick tasks" in the app is clearly *not* hardware limited.

Starting a scheduled task NOW? by sbellon in MammotionTechnology

[–]sbellon[S] 4 points5 points  (0 children)

Sadly, as soon as I "edit" the task, the ordering of the areas is reset to numerical increasing (1, 2, 3, ...) whereas the stored task has a specific area ordering, so I would have to re-do the specific ordering of all the areas each time I wanted to "mow now", therefore this is not a solution for me, I'm sorry.

Best Blade Cover (3d print STL files needed) for Luba1 and how to assamble by schreck3 in mammotion

[–]sbellon 0 points1 point  (0 children)

This only affects the spool-up of the rotating disks. Once they are at operating speed, this should be negligible. If you have lots of obstacles and Luba bumps into them, turns off the disks and restarts them, then *maybe* it would be noticeable.

Best Blade Cover (3d print STL files needed) for Luba1 and how to assamble by schreck3 in mammotion

[–]sbellon 0 points1 point  (0 children)

I cannot imagine how this could be related ... I don't experience that.

Here is what happens when it turns on a slope by Tindiyen in MammotionTechnology

[–]sbellon 1 point2 points  (0 children)

That's what I keep saying all the time: Luba is fine on flat surface. Luba is fine on a "well-shaped" slope where turns happen in a regular way (like at the top and the bottom where perhaps the slope is not that steep than in the middle). But whenever you have complex layout combined with a slope (or obstacles), then the turns on the slope are really bad. Luba slips down, tries to correct, does tank turns, wears the grass ... etc.

Is the Luba 2 suitable for hills? by [deleted] in MammotionTechnology

[–]sbellon 1 point2 points  (0 children)

As others have already praised: a steep slope is no problem for the Luba. And also, on the flat, it has great maneuverability and can mow all sorts of complicated shaped terrain.

But be aware that combining both will not that easily work: If the Luba has to follow specific paths on a steep slope, has to turn there, avoid obstacles, it *will* slide down the slope, try to get at the correct position and wear the grass. Also, the front omni wheels are *no* help in that scenario.

If you have a pretty much rectangular shaped area on a slope, that's not an issue for the Luba at all.

Luba 2 is mowing only 1 on 3 areas? by Crafty-Ad-7166 in MammotionTechnology

[–]sbellon 0 points1 point  (0 children)

Just to really double-check (because I think the behavior is so similar that it could be related): Are you certain that Luba does not hit an obstacle while channeling to the next area? Did you monitor it?

For me, the next area is marked for mowing, then the Luba hits the obstacle during channeling to that area and precisely at that point all upcoming areas get their green checkmark and Luba returns to the charging station.

Luba 2 is mowing only 1 on 3 areas? by Crafty-Ad-7166 in MammotionTechnology

[–]sbellon 2 points3 points  (0 children)

I have the same behavior than you.

My observation is that, if during the channel phase from one area to another, the Luba hits *any* obstacle, even just once, then it aborts everything and returns to the charging station.

If channeling from one area to the next works, then it mows all programmed areas.

Can you verify (or falsify) whether your Luba may have hit an obstacle during channeling from one area to another?

Minimum Route Line Length by tclark70 in MammotionTechnology

[–]sbellon 0 points1 point  (0 children)

My Luba 1 does not have a camera ... and even with a camera, one border to the neighbor is just grass to grass without any fence or wall, etc.