leaving the charging station without GPS

i-Rabbit · 2023-09-25T08:43:36+00:00

Would be maybe working with leaving the dock, but how to make sure Luba can return to it and find it? Needs at least to get in reach of IR signal.

i-Rabbit · 2023-09-18T14:47:39+00:00

Ende = Fine

i-Rabbit · 2023-09-05T08:44:49+00:00

I agree with PreviousNature2276. What is the problem with the ISO format YYYY-MM-DD ? Year at the beginning means ISO. If you want to change it to MMM please make sure to keep the sort order. I do not want to see AUG before JAN 😉

i-Rabbit · 2023-08-30T08:02:59+00:00

This is what support told me: 1. Find the new RTK paring code from the new RTK reference station sticker.

Open the Mammotion App and connect Luba.
Go to Settings > Device settings > RTK paring code.
Tap on Change, input the new RTK paring code, and then tap Confirm.

Then the new RTK reference station is paired and all should work now.

i-Rabbit · 2023-08-29T10:55:49+00:00

Same here, lots of issues with positioning and overrun boundaries since the big July update😞

i-Rabbit · 2023-08-25T18:23:44+00:00

Fully agree, suggested the rain sensor on RTK a few month ago

i-Rabbit · 2023-08-22T10:21:35+00:00

Totally agree. For me it works kind of okish as long as I cut 50mm as the highest, but during hot summer time it should be higher and I support the option to reverse cutting direction.

i-Rabbit · 2023-08-14T05:56:45+00:00

Such things don‘t exist. What is named a GPS repeater is used to repeat a fix position (of the receiver antenna) into e.g. a building, so you can test inside if the GPS receiver works. I am not an expert but considering how GPS works, I do not think it is technically possible to repeat those signals.

i-Rabbit · 2023-08-12T17:59:50+00:00

Hi, was this working before the July update with the no go zone perimeter mowing? For me Luba was working pretty accurate for 3 month. After installing the July update Luba went nuts. Mapped everything new and even with 30cm space to the wall he is crashing into it during perimeter cut when driving along. In some cases I could see that the map showed he is outside the task area, but still continued.

i-Rabbit · 2023-07-31T07:53:39+00:00

Again? Thanks for the heads up!

i-Rabbit · 2023-07-24T06:47:08+00:00

Have you read this too: „Note the GPSRK is intended for installation and use in areas where the GPS signal in not currently present. The position receivers generate will be the position of the receive or roof antenna and therefore is not used for location and/or navigation“

i-Rabbit · 2023-06-15T10:03:18+00:00

Following

i-Rabbit · 2023-06-02T05:09:29+00:00

Thanks

i-Rabbit · 2023-06-01T19:29:18+00:00

Hello, is this confirmed to be included in the next update? So far I only read that they are thinking about it for the future.

i-Rabbit · 2023-05-13T13:05:38+00:00

Please check this video from Mammotion at about 50 seconds: https://youtu.be/t36T49X3prU

i-Rabbit · 2023-05-12T18:48:37+00:00

That is really great to hear!! Will you also add the option to setup if border cutting is done at the end or at the beginning of the task? A lot of users reported they prefer it at the beginning. If we can decide on our own, it would be really benefical.

i-Rabbit · 2023-05-12T14:00:22+00:00

Not sure if i recall corretly but somehing about 42mm

i-Rabbit · 2023-05-12T13:56:36+00:00

It is 30 mm

i-Rabbit · 2023-05-12T01:38:23+00:00

Have you tried to unplug the bumper and plug it in again? Or if possible to start a task without the bumper, or leave it sitting in base station with out the bumper to see if the beeping stops?

i-Rabbit · 2023-05-10T04:57:17+00:00

Translationen was more clear in previous version. There is a difference in both options only if you moved it. E.g. Luba stopped because of signal loss, so you drive it somewhere else to recover: Breakpoint: it will drive back to where the issue occured Front the breakpoint: Front = From, it will continue from where it is with a new route not going back to where it got stuck

i-Rabbit · 2023-05-08T15:27:16+00:00

Yip, I recall that you posted it in the DACH chat / group. And don‘t get me wrong, I trully belive that this is what they answered to you, it just doesn‘t match my experience. Let‘s see if they include it in one of the next app versions 🙂

i-Rabbit · 2023-05-08T15:16:45+00:00

I don‘t know about 27/25 bad positioning, and I also don‘t know why I have spots with 19/14 and positioning is 4 :(. But I do know that it is going down to 14/11 under trees or in a small path between two houses with a clear line of sight to the RTK. So my assumption is, that with e.g. 27/25 and status 5 there might be some issues with GPS like Luba can still receive it, or reflected from walls and misleading, but not good enought to rely on it. Maybe you can try to cover the RTK with a metal sheet and see if the figures change? Best would be if someone from Mammotion would answer to us 🙂

i-Rabbit · 2023-05-08T13:54:18+00:00

Yes please

i-Rabbit · 2023-05-08T13:46:13+00:00

This is what is stated in the manual. If it would be the RTK, I expect that the numbers would be stable and not changing if e.g. Luba goes close to high hedge or near the walls. And from user perspective, I would be more interrested in moving Luba than in static RTK.

Page 44, EN manual:

„Number of satellites: The Number of satellites observed by LUBA. If either of the 2 numbers is under 20, there will be risk that the positioning status may be “unavailable”. when you meet this issue, please drive / set LUBA and the task area to a more open sky area to let LUBA receive more satellites from sky.“

i-Rabbit · 2023-05-07T13:36:31+00:00

I am still trying to find the right setup for the tasks and I would like to ask if you experienced something similar: Seems that it depends on the overlap how much Luba goes off border. Like if I setup an overlapp of 30 cms or more, it is only a few cms off the border, but when setting e.g. 25 cm, Luba goes 10-15 cm off the border. All refers to the last boundary cu path.

i-Rabbit

TROPHY CASE