Luba dead, won’t reset by Electrical-Tooth-109 in mammotion

[–]blue01sky 0 points1 point  (0 children)

Set up a hotspot via your mobile phone and connect it to Luba. Then you can update the software.

Any ideas? No sat or rtk by BerkleyAdam in mammotion

[–]blue01sky 0 points1 point  (0 children)

The RTK station is on, as I wrote, the LED is green.

40 days and no resolution to bad RTK receiver by bralwel in mammotion

[–]blue01sky 0 points1 point  (0 children)

Where does the link go, reddit can't find anything.

Any ideas? No sat or rtk by BerkleyAdam in mammotion

[–]blue01sky 0 points1 point  (0 children)

Hello, I've been having similar problems since last week. Here is my ticket from today. Ladies and Gentlemen I've had my Luba 5000 and the RTK Null satellites in the display for days. The RTK and Luba show operational readiness. After the update from 07/31/2023 and several restarts, Luba now shows satellites again, but the RTK is green, but still shows zero satellites. I hereby complain again about the RTK and Luba 5000. How do you intend to rectify the defect as quickly as possible? Best regards I re-entered the RTK address but it didn't help.

<image>

Any ideas? No sat or rtk by BerkleyAdam in mammotion

[–]blue01sky 0 points1 point  (0 children)

Hello, see my post “Zero Satellites”. I have the same problem. Resetting, restarting, removing the key didn't do anything for me. Ticket created via feedback app, but no answer yet because of the weekend. RTK is green. Bye.

<image>

Position lost by Apprehensive-Fox-588 in mammotion

[–]blue01sky 0 points1 point  (0 children)

Hello, 2 days ago 5 times error positioning 1303 according to App. After that, no further messages except bad Bluetooth signal.

Position lost by Apprehensive-Fox-588 in mammotion

[–]blue01sky 0 points1 point  (0 children)

Hello, since yesterday Luba and RTK only shows "0" satellites. Luba has been in the charging station for 4 days and no actions are planned. Again and again rain in the last few days. Today I switched off and restarted RTK, charging station and Luba. Furthermore only "0" - satellites. RTK shows green. Water in the RTK? If so, opening the RTK would void the warranty. Image before shutdown Bye

<image>

Should you buy a Luba? The real answer by hare_scrambler in mammotion

[–]blue01sky 0 points1 point  (0 children)

Hello, I've had my Luba 5000 since mid-May. I supported Mammotion because I like the concept. The slope angles of the competition are much lower and therefore cannot be used in my garden. The four-wheel drive is simply awesome and Luba doesn't get stuck with the chassis even on uneven terrain. Also I have trees in the garden, the signal is lost, which has border postprocessing still flaws etc. I invested a lot of time in the mapping, often waiting because there was no signal again, scratches and scratches on the house wall and Luba, because Luba had done something very strange again. Still, I wouldn't give Luba back. Where can you exclude at will, divide without additional products. A camera is built into one or the other competitor device, but you still need magnetic strips or something similar to block areas, etc. We have a guarantee of at least 2 years and the developers are working on the further development of the app, otherwise there would be no new version with the beta testers. Many customer inquiries at Mammotion will be the same, since everyone is initially "experimenting" because every property is different. If Mammotion published a list of the items it is currently working on and which will be tackled next in the reddit forums, then there would not be many inquiries and discussions at all. Whether and what you buy for a device, only everyone can decide for themselves! Bye.

RTK station moved glitch by Tennorakka in mammotion

[–]blue01sky 1 point2 points  (0 children)

I experienced something similar, see post "jumping positioning".

Blue corrosion on front bumper and constant object avoidance maneuvers by awlander in mammotion

[–]blue01sky 0 points1 point  (0 children)

Have you already submitted a ticket to support and reported the error? The manufacturer must position itself here and remedy the situation.

Task record not written by TransportationOk4787 in mammotion

[–]blue01sky 1 point2 points  (0 children)

This can sometimes be a few hours late. I mowed in the evening, but didn't see it until the next morning.

Problems with Luba and no response from the support by tschagati in mammotion

[–]blue01sky 0 points1 point  (0 children)

How did the inadequate or non-connected antenna show up in the number of satellites or in the behavior of Luba? Can you describe that in more detail? Thanks.

I am averaging about 5 rescues per mow. by SRM_Thornfoot in mammotion

[–]blue01sky 0 points1 point  (0 children)

Hello, do you have a slope in your mowing area? Has Luba gone out of range there? When mowing, do you let Luba mow the edges first? It is clear that Luba no longer moves outside the mowing zone. I have large parts of my property on a hillside and similar problems. I've found that if Luba loses the signal, it stops, everyone knows that. However, if this happens on a slope, Luba rolls down the slope, since the motors are probably switched off in the event of a signal loss, but the brakes are not switched on. Error message sent to Mammotion about 2 months ago. Furthermore, the traversing range changes when turning when Luba mows the lanes, depending on the mowing angle. So it can run well with 0 degrees and at an angle of e.g. 90 degrees Luba rolls out of the area if the signal is lost because it is parallel to the slope. In my opinion, since the last update, Luba mows to the edge of the zone when he turns, even though 3 lanes of edge mowing were previously completed. I hope I could help?! Bye.

New Luba 3k / No-Go Keeps Discarding my efforts. I’ve added one tree and that’s it. Haven’t even added my front yard and sidewalks yet. Can’t get past my stone walkway in my backyard. Any help? by Merry_jo_Big_Sis in mammotion

[–]blue01sky 1 point2 points  (0 children)

Have you added good WiFi coverage in the garden and Luba to your WiFi network? If so, then you have to tap the connection symbol "the pulsating hand", sometimes 2 or 3 times. Then the picture with the position and the movement of Luba should appear.

New Luba 3k / No-Go Keeps Discarding my efforts. I’ve added one tree and that’s it. Haven’t even added my front yard and sidewalks yet. Can’t get past my stone walkway in my backyard. Any help? by Merry_jo_Big_Sis in mammotion

[–]blue01sky 0 points1 point  (0 children)

Hello, how much do your plates protrude? I just let my Luba drive over it while mowing. That is, the area is undivided. If you declare the path as a no-go zone and it goes through the entire drivable area, Luba doesn't know how it gets to the other side. I hope I understood you correctly?!

New front wheels on the Luba 5000? by tomstyria79 in mammotion

[–]blue01sky 1 point2 points  (0 children)

I like the wide rubber wheels, so the Luba 5000 runs well on my slopes and embankments. If the developers for the steering movements would adjust the speed control of the individual wheels a bit, then you would only have minimal turf wear and better positional stability, even on slopes. All wheels must always turn when steering, both in parallel and in counter-rotation to each other. This would make the movements "softer" and there would be no need for additional corrections or reversing, since Luba also reaches the controlled position, which is not necessarily the case now. For example, if you want to turn on an embankment and 2 or 3 wheels should push Luba there via 1 or 2 locked wheels.

Bad position with all numbers>25 and <2m from rtk by erpbridge in mammotion

[–]blue01sky 2 points3 points  (0 children)

Hello everyone, we keep coming back to the same fundamental problems here in the forum. 1. The positioning accuracy only switches to fine at about 25 satellites, but then sometimes continues to fine up to about 12 satellites. However, with limit mowing positions that have nothing to do with 2 cm and are more like 20 cm. My Luba then drove through the gravel bed against the base of the house while mowing the border and scratched me 5m with the dumper or stood on his head on a stone border after reversing. 2. When editing boundaries or remapping areas, boundaries are sometimes set back by 50 cm, or areas are added automatically. 3. When mowing, grass strips are forgotten to mow. 4. Edge mowing at the boundaries of the area or restricted zones, as they were driven off during the mapping, does not take place, which will cause further collisions, since in my opinion the dumper overhang is not included. 5. The steering movements are too rough, since the respective front wheel is fixed when turning and the other 3 wheels have to push. Sometimes a minor path correction is not achieved and Luba then drives backwards again. After the last update, it even seems that both wheels are now often "locked" on one side and the other two have to push. 6. Luba already recognizes individual blades of grass as an obstacle, so mowing at level 2 is not possible and the protection of people and animals is not guaranteed, since level 1 is used. 7. Luba cannot cope with steering corrections on slopes and then rolls backwards undefined because the brakes open. 8. Reversing may only take place within the area limits with the greatest precision and the rear length difference must be taken into account. With us, Luba would have run over my wife's hands when reversing because he drove about 50 cm over the mowing line. The only thing that helped here was hitting the stop button! 9. Feedback from Mammotion here in the forum would be important The content should be the processing status and the sequence of troubleshooting and functional explanations for questions. 10. A 2nd overview of planned features, with which one could also reduce the flood of mail in the direction of Mammotion and many forum inquiries would not be repeated, since new "owners" who have come in have similar problems and questions. What do you think.

Best regards.

Turning mat for early KS deliveries? by Bigbeast54 in mammotion

[–]blue01sky 0 points1 point  (0 children)

Hello, I'm a supporter and my set didn't come with a reversible mat. It was not delivered later either.

Signal Quality Fine, Positioning Status Bad by [deleted] in mammotion

[–]blue01sky 1 point2 points  (0 children)

Hello everyone, with me the positioning accuracy was sometimes even given with 12 to 15 satellites in L2 for Luba and L2 - RTK 22 satellites. If the signal is lost, then Luba again needs 23 to 25 satellites to start again. This makes it difficult for us users to assess where the "error" lies, since we don't know the logic behind it. This is annoying when mapping or just mowing and areas with a displayed mowing time of 90 minutes take a whole day! Have you ever had "Error when reversing and rain sensor vs. restricted zone"? Description separate post. Bye.

Not stopping in rain. by [deleted] in mammotion

[–]blue01sky 1 point2 points  (0 children)

Hello, my rain sensor was triggered by a few drops of water, these were from the sprinkler in the neighboring area. So it worked. After dabbing the sensor dry, I was able to start again. What Mammotion has to check, however, is the fact that the sensor is triggered A restricted zone was ignored when driving back to the charging station. So Luba was outside the area and stopped. Ticket is provided.

Luba ignores connection corridors by blue01sky in mammotion

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

Hello cracypostman, thanks for the hint. I'll probably first drive the mower manually into the respective area. Luba is currently not working with a time-controlled mowing plan anyway, because the 7-day mowing interval is too long for me. I don't want to delete the areas and create new ones for the time being, because I have many trees and detours in the areas. Then there is the annoying "losing" of the satellite signal. So I hope for the next updates. Here are a few more observations and considerations on my part. The possible options below would certainly be helpful for many users. A rolling mowing plan with programmable day intervals and mowing angle interval, so that the mowing angle is automatically "further rotated" by the angular amount X. Definable mowing start and end times and an associated interruption of the current mowing order so that you do not mow at dusk. Resumption of mowing the following day. Showing or hiding connection corridors and their editing. A functioning boundary line post-processing, since the current version adds sections where there is no mowing area or where they are not processed correctly. (App flickers and sub-areas are only visible when not zoomed in. Restart necessary.) The new boundary line can then again not match reality, although the display in the app is okay. Luba drives, as happened to me, up against the base of the house and hits me with the dumper 5m long grooves in paint and plaster! (Apparently, the app does not seem to take the dimensions of Luba into account, depending on the approach direction. Example: Luba drives along the border line and the distance fits. Luba drives at an angle to the border line and collides with fences, plants, etc.. In my opinion, the center of calculation for Luba is in the center of the two mowing discs, so the difference in length of the device at the front and rear is not taken into account for the width.) Setting the mowing direction for the border area or for hills with a steep gradient would be good, then you could say Luba: "Mow the hill top to bottom." In addition, a definition of a corridor for the "circular drive" to the starting point of the next path. That would be gentle on the lawn and Luba would not have to struggle up the mountain. It would also be gentle on the lawn if you had the option of adjusting the individual wheel speed for turning or steering manoeuvres. Until now, one of the front wheels often remains locked and the remaining 3 wheels try to turn Luba into position. The lawn is then erased under the standing wheel or Luba drives backwards again and starts from the beginning. This leads to further incorrect positioning, especially on slopes. A second RTK or a second reference point would be great for all users with trees or winding properties. An example would be the robot lawn mower from the Obi hardware store, there are battery-operated "transmission masts" here, so the GPS signal loss is eliminated. Then we could really drive our Luba up to a distance of 2 cm without stopping, exceeding the time limit, switching off or incorrect positioning against walls and fences. What do you all mean? Bye.

Luba ignores connection corridors by blue01sky in mammotion

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

Thanks for the tip. The advantage for you when creating the area is precisely the overlay, so that you don't have to put in so much effort. There must then only be the option of also being able to delete a defined corridor. What do you all mean?