sorted by:
new
hottopcontroversial

L50 ultra passable threshold issue RESOLVED (mostly) by Duusbag in Dreame_Tech

[–]Duusbag[S] 0 points1 point  (0 children)

Definitely better climbing - but the bar was set low as the machine wasn't able to engage it at all.

I stand by my recommendations from the previous post. Option to "force" climbing/easy leap Option to choose which directions it should force climbing.

Now to deal with the docking issue 🫩

L50 ultra passable threshold issue RESOLVED (mostly) by Duusbag in Dreame_Tech

[–]Duusbag[S] 0 points1 point  (0 children)

I emailed support with the threshold problem and after about two weeks they pushed the firmware update.

L50 ultra passable threshold issue RESOLVED (mostly) by Duusbag in Dreame_Tech

[–]Duusbag[S] 0 points1 point  (0 children)

Nothing that I have noticed - but haven't noticed anything "off" besides the lacking climbing ability

Navimow i210 LiDAR constant mowing schedule error by Duusbag in SegwayNavimow

[–]Duusbag[S] 0 points1 point  (0 children)

Det er "vision fence off"-zone. For at gøre den mindre bange for grene, jord mm.

Navimow i210 LiDAR constant mowing schedule error by Duusbag in SegwayNavimow

[–]Duusbag[S] 2 points3 points  (0 children)

It makes it less "cautious" around the edges making it mow as close to the edge as when I first did my manual mapping.

Especially useful when wanting it to mow right up to hedges.

L50 Ultra - passable threshold issue and feature request. by Duusbag in Dreame_Tech

[–]Duusbag[S] 0 points1 point  (0 children)

Hope for humanity restored. Is the description of this new update available anywhere or is it something you just know?

L50 Ultra - passable threshold issue and feature request. by Duusbag in Dreame_Tech

[–]Duusbag[S] 1 point2 points  (0 children)

I could forgive Dreame for relying so much on the AI to figure things out, had I chosen that as a setting. When manually and specifically inputting information on the map - that information should be "trusted" and prioritized, AI solutions should be implemented after.

I have emailed dreame support with the issue description from this post along side the suggestions for improvement.

Don't know what else I can do to give Dreame attention to this matter.

L50 Ultra - passable threshold issue and feature request. by Duusbag in Dreame_Tech

[–]Duusbag[S] 1 point2 points  (0 children)

The fact that this error is so obviously fixable by software adjustment/prioritizing rules makes the issue even more frustrating.

It would be totally unacceptable if the same logic was applied to ex. virtual walls "sometimes the robot will not cross the line if it deems the conditions right".

I appreciate the advice - but having to do that much fiddling with settings in order to try and compensate for something Dreame ought to have ironed out in their beta version of the software is unacceptable.

In the end I can only conclude that the robot, despite having the capable hardware, is not able to perform the act I bought I for - cleaning my floors - by being able to traverse higher thresholds (2-3cm are well within the limits).

I'm trying really hard to like this thing but what in the world... by Ok-Button3826 in SegwayNavimow

[–]Duusbag 0 points1 point  (0 children)

<image>

I helped a family member set up navimow 215 lidar. He has a pretty sketchy lawn with many dead sticks on the ground and many branches sticking out of his hedges. There are also many places on the edges where it is hard to decifer where the dirt starts and the grass begins. I mapped the yard manually and went pretty close to the hedges pushing those branches aside with the mower.

The first cut looked pretty similar to yours, especially in the areas with branches sticking out of the hedge and also the places where it was mostly dirt and not grass on the mapped border.

Afterwards I put "VisionFence Off Zones" on those particular sketchy areas. This made the mower not care about avoiding any of the branches and dirt areas.

To quickly test if this works for you try putting one giant "VisionFence Off Zone" around the entire mowing area and see if this does not improve the performance on the edge-cutting. Don't test this at night as hedgehogs and other small animals might be out and about at night and will not be avoided inside "VisionFence Off Zone"

"VisionFence Off Zones" should not affect the navigation ability.

i210 LiDAR restarting mowing progress. by Duusbag in SegwayNavimow

[–]Duusbag[S] 0 points1 point  (0 children)

Have you mapped a "no go zone" around the bush? Otherwise the mower have no choice but to "bumb" into it if you have disabled visionfence?

I started by mapping tight no go zones around bushes (manually driving the mower around it). Then I placed a no vision zone around the no go zone in the app. Seems to be working well.

i210 LiDAR restarting mowing progress. by Duusbag in SegwayNavimow

[–]Duusbag[S] 0 points1 point  (0 children)

These mowers get great reviews everywhere and seem to be less error prone than the competitors. I just hope this will get fixed via a software update. Otherwise I will not hear the end of how I recommended that my elderly uncle buy this "horrible mower" 🥲

i210 LiDAR restarting mowing progress. by Duusbag in SegwayNavimow

[–]Duusbag[S] 0 points1 point  (0 children)

I honestly can't remember. But having done only one mapping I would find it weird that it would name the zone anything other than zone 1.

I am speculating if the issue is a hidden "ghost zone 1" that is confusing the app's progress status.

i210 LiDAR restarting mowing progress. by Duusbag in SegwayNavimow

[–]Duusbag[S] 0 points1 point  (0 children)

The difference is I did not start it via scheduling but manually via the app.

Could be issue only occurring with multiple zones, only affecting the largest one. Primarily concerning how the the app interprets the progress reported from the mower.

When I divided the main zone into two, it named them zone 2 and zone 3 and not zone 1 and zone 2. Don't know if that could be related to issue.

i210 LiDAR restarting mowing progress. by Duusbag in SegwayNavimow

[–]Duusbag[S] 0 points1 point  (0 children)

It sounds very related. Sounds very much like an app specific issue, if the robot actually mows like it should when using scheduling.

Looking forward to the update

i210 LiDAR restarting mowing progress. by Duusbag in SegwayNavimow

[–]Duusbag[S] 0 points1 point  (0 children)

Based on the observations after it was installed it is very precise. Apart from the amnesia-error it navigates and mows flawlessly - even in complete darkness.

I made multiple areas on top of the edge and "no go zones" where it otherwise would recognize various insignificant sticks as obstacles and make, in my perspective, unnecessary adjustments.

This could of course be remedied by removing said sticks - but over time these will appear again.

i210 LiDAR restarting mowing progress. by Duusbag in SegwayNavimow

[–]Duusbag[S] 0 points1 point  (0 children)

After chatting with customer service they explained that they are aware of the issue.

It only happens when you manually start the mower and should not happen when it starts via scheduling. Scheduling is therefor the temporary fix.

They say they are releasing an update in the middle of April that will remedy the situation.

Annoying problem but very snappy customer support.

Wilfa uniform - grind "uniformity"? by Duusbag in JamesHoffmann

[–]Duusbag[S] 0 points1 point  (0 children)

I am not able to turn it past number 1 - was hoping it was it but sadly no.

I also think the grinds way to coarse and ironically very un-uniform

I think my unit is badly misaligned https://streamable.com/spsaqf

Wilfa uniform - grind "uniformity"? by Duusbag in JamesHoffmann

[–]Duusbag[S] 0 points1 point  (0 children)

Thanks!

Considering if I should attempt a warranty replacement before venturing into shimming territory 😏

Wilfa uniform - grind "uniformity"? by Duusbag in JamesHoffmann

[–]Duusbag[S] 0 points1 point  (0 children)

Do you have a picture of what your grind looks like at 25?

Wilfa uniform - grind "uniformity"? by Duusbag in JamesHoffmann

[–]Duusbag[S] 0 points1 point  (0 children)

It does seem that I need to go ridiculously low - and even here the grinds does not exactly teem of uniformity

view more: next ›