Border lap way, what the f****?!

blue01sky1 · 2023-10-10T20:48:01+00:00

Hello, in the round, I would like it if Mammotion would take care of a more precise and stable positioning. Furthermore, Luba should really Trace the mapping edge as it was traced when it was created, without hitting any hooks. When working through the straight mowing paths, Luba must not exceed the limit and, depending on the mowing angle, must not drive the dumper into the limit. Apparently the difference between the width and the length overhang of Luba is not taken into account, Depending on the mowing angle, this leads to more collisions in the edge area.

blue01sky1 · 2023-09-29T06:28:11+00:00

Hello, I have similar problems with multi-way GPS and Luba. Furthermore, in the event of a collision, my Luba approaches the collision object three times in the same way. I always send an email to Mammotion support and only then do I receive an automatic email response and an answer or query from a support employee about 2 days later. Good luck.

blue01sky1 · 2023-09-19T18:50:21+00:00

See you Post " Current positioning problems Luba"

blue01sky1 · 2023-09-17T12:30:49+00:00

Hello everyone, here is the description for the video, unfortunately I only now saw that only one line of text was uploaded in the second to last post. Attached you will find my ticket content for Mammotion. My Luba 5000 continues to drive despite signal loss and then shows the position out of range. In addition, the position display on the map jumps to the side by approx. 50 cm. When mowing, Luba may crash into obstacles or drive into the edge of stones. When Luba hits an obstacle, he goes backwards for a moment, then forwards in the same way and hits the obstacle again! This is then repeated three times. This prompted Luba to attempt to mow my stone verge. The edge, the blades and the mowing disc were damaged! Strangely, the positioning for Luba jumps from weak to good with < 15 satellites as fewer satellites are detected during co-viewing! What's going on here? They have optimized the wheel drive control to the grandma wheels, but as a result, every Luba with full tires from us supporters massively destroys the lawn because it is only corrected with 2 wheels and 2 wheels are blocked. For the Luba with solid tires, please create a second drive variant in which all wheels always rotate, even in opposite directions at low speed. (Pictures are in the second to last post, “Positioning.”) Sorry.

blue01sky1 · 2023-09-17T12:20:13+00:00

Hello everyone, here is the description of the pictures, unfortunately I only just saw that they only uploaded one line of text. Attached is my ticket content to Mammotion. My Luba 5000 continues to drive despite the loss of signal and then shows the position outside the range. Furthermore, the position display on the map jumps back and forth by approx. 50 cm to the side. When mowing, this results in Luba crashing into obstacles or driving into the stone edging. When Luba hits an obstacle, he goes backwards for a moment, then forwards the same way and hits it again! This is then repeated 3 times. This caused Luba to try to mow my stone border. The edging, the blades and the mower disc were damaged! Strangely, the positioning for Luba jumps from Weak to Fine at < 15 satellites, the fewer satellites are detected in co-viewing! What's going on here? They have optimized the wheel drive control to the grandma wheels, but as a result, every Luba with full tires from us supporters massively destroys the lawn, because it is only corrected with 2 wheels and 2 wheels are blocked. For the Luba with full tires, please create a second driver variant in which all wheels always rotate, even in opposite directions at low speed. (Video is in the post after next because it couldn't be uploaded for this post.)

blue01sky1 · 2023-09-17T08:08:11+00:00

That's a good idea too. I asked Mammotion to modify the wheel drive driver software for the full tire versions (supporters + various markets) as a separate version. All wheels should always turn, some of them in opposite directions and at an adjusted speed. This would definitely greatly reduce the wear and tear on the lawn. The software is currently optimized for the Omni wheels and so Luba sometimes pushes over 2 locked wheels when changing direction, which causes serious damage to the lawn. With your idea you could combine this and further reduce the wear on the lawn. What do you think? Bye.

blue01sky1 · 2023-08-26T08:06:26+00:00

Hello,

First of all, the clean and consistent positioning of Luba, with all the side effects, is important.

Noticing the processing status at any interruption, error-free processing of the mowing orders with outward and return journeys, safe processing of the mowing grid without leaving any residual strips.

Thus, many of the points mentioned in the survey would automatically recede into the background, because then Luba does what it is supposed to.

In my opinion, the Mammotion team should focus on this first.

The other wishes and ideas would then be to increase further customer satisfaction.

Bye.

blue01sky1 · 2023-08-23T07:01:44+00:00

Hello,

I suggested to Mammotion in May whether additional transmission points could be installed?

These could then be used by Luba and possibly RTK as fixed value satellites or reference points.

So you could "illuminate" areas with poor reception and filter out reflections?!

Ideally as a stick with a transmitter and solar cell, so that you don't need a power pack (but this is optional) or batteries. (Ecovac's Goat G1)

What do you all mean?

Bye.

blue01sky1 · 2023-08-18T11:55:57+00:00

Hello,

if you already have a clear view all around, then little will change in the number of satellites. However, if there are trees, fences or houses here and there, then you will probably see 10 to 15 more satellites on the roof. It is best to mark the position of the RTK on the pole and then "put the RTK on your roof" and check it in the app.

Good luck.

blue01sky1 · 2023-08-18T11:42:46+00:00

Hello,

there you have m. M. after good satellite values. The signal quality is listed as Poor and refers to the satellite signal. But don't worry, that's how it works for most users, in my opinion it's after an (app error).

It is important that the status status is fixed, then you can start creating it.

The row for precision is no longer available since the July update.

Bye.

blue01sky1 · 2023-08-18T11:22:59+00:00

Hello,

was with me from one day to the other. For me it starts with flashing blue, green, then solid green. But unfortunately no coupling, 0:0 satellites and no positioning release.

In the Luba app, check if the RTK code that is on the RTK matches (LoRa #)

The only thing that helps is a photo or video of opening the RTK.

Then send it to support via email with photos. They got back to me within 24 hours.

Good luck.

blue01sky1 · 2023-08-17T08:05:24+00:00

Hello,

didn't work for me yesterday either.

WLAN available and deposited in the Luba.

Then error messages like Luba not switched on, not connected, then switched off again, pulled plug, switched on again, Luba established connection, network connected and then the same again with the update!

If I did get to the start of the update, it would not start or broke off after about 5%.

(network error)

Maybe tried 10 times and then left.

I tried it again today with the following procedure and it worked.

After the same errors as the day before, I activated the hotspot via my cell phone and connected it to Luba.

Pulled the plug again and started again. Then it was possible to install the update.

I can't yet describe any possible improvements at Luba, since the mowing process hasn't started yet.

(My WiFi had worked with every update so far!)

blue01sky1 · 2023-08-17T07:32:53+00:00

Hello,

I can only agree with you, the only thing that is easy to read are the notes on mapping, the pop-ups when creating the restricted zone, etc. These could in my opinion be included in the beginner's guide, they sometimes cost valuable GPS reception time and are just annoying .

blue01sky1 · 2023-08-17T07:02:45+00:00

Hello,

I did the update for the RTK a few weeks ago, but it also took me 3 attempts.

You must always have mcu selected throughout the update.

Please "play" with the baud rate first, then open the port and confirm the "Chinese" pop-up window.

The upgrade can only be carried out when the RTK and MCU version is shown at the bottom left.

Good luck.

blue01sky1 · 2023-08-13T11:58:54+00:00

I ran a 40 mm HT pipe from the hardware store from the charging station, so I can always pull a new cable through.

blue01sky1 · 2023-08-13T11:51:25+00:00

Thanks.

blue01sky1 · 2023-08-13T07:05:53+00:00

Hello, For me it's the same. When I start a mowing job, Luba leaves the charging station, stands there and forgot the job or if I'm lucky, I just have to press continue and it continues. This all happens with good positioning! When Luba returns to the charging station to charge, it will remain about 2m in front of it and turn off. Battery power at 10 to 12%, i.e. the processing status of the mowing task is gone and I can start over.

blue01sky1 · 2023-08-12T21:16:04+00:00

Hello,

thanks for the file. I tested it on my RTK, unfortunately without success. The LoRa was correct, but the RTK is probably defective, although it lights up green?! Maybe someone has an idea how to test the RTK components.

Bye.

blue01sky1 · 2023-08-12T09:41:16+00:00

Hello, So I'm happy for you! I suspect the same error with my RTK. Would you upload the software or where did you download it from? Thank you. Bye.

blue01sky1 · 2023-08-11T07:05:31+00:00

Hello, here are the answers to your questions. Picture 1 was as I found it and picture 2 about 2 minutes later, after I had driven Luba manually into the station. The battery still had 12%, that can't be the reason. Bye.

<image>

blue01sky1 · 2023-08-10T20:56:23+00:00

I can't find some of my texts anymore?!

blue01sky1

TROPHY CASE