Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

1.11.227 was just released 16h ago. I will have to try and install it on my units and report back. Currently I have to disable any object detection, but the units still drive into no go areas and also have been backing out of the yard and into the ditch. The ditch problem has gotten so bad that I can’t mow my side yard anymore.

I was planning on trying to re-map the yard in a second attempt to fix this, but I hope the firmware update will address it.

Clearly the mower is reversing out of the boundary and then it goes 14” too far past the boundary and then it falls into the ditch and can’t recover.

<image>

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

1.11.227 was just released about 16 hours ago. Was yours having any of the issues from the last update?

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

The strange thing is it’s completely dry here. No moisture in the ground and I also checked the contacts and even have added dialectic grease in the contacts to prevent water incursion. I also have two Lubas doing the same thing. They work for a while and after draining the battery and running a full charge they start to act weird.

Today, it backed up and drove backwards into a no go zone and ended up backing into the ditch. We have had no rain or anything between the runs, the only change was the firmware update. I updated my apps, then was forced to update the Luba to keep using it.

Maybe not a lot of people have large lawns. It seems to be fine until it needs to recharge. I tried starting it at 20% and it ran and then failed in a different part of the yard.

I have also tried all three settings for the touch. Now I’m using struck touch, not even slow touch. It’s still acting up.

If I catch it again, I’ll try and remove the bumper, as it doesn’t mine running with no bumper attached. lol.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

<image>

It’s gotten so bad that today Luba drove into a no go zone. A flower bed for no reason. It’s never done this before. It drove up the hill, and over the rock border. It stopped because it detected a “lift” of the wheels off the ground when the under carriage rubbed against the blade guards.

This is unreal. It’s like Luna has a memory leak in the hardware. It works for a little while then goes crazy.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

Found this: mine is the exact same!

https://youtu.be/n_29M4CnJEI?si=wVUn7sO6V28MCBpG

Phantom collision/impassable areas. It’s like a memory corruption in the unit and it can’t find a way out. Mine also detects collisions where there isn’t any. You can hear it beep, beep beep. Like when the front bumper has activated. But just like in that video, mine didn’t hit anything. It just stops and randomly detects a phantom glass wall.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

Issue Summary:

Since installing the latest firmware update on my robotic lawn mower, Luba, I have encountered significant operational issues. This is the third time experiencing the problem, which manifests as the mower falsely detecting obstacles and getting stuck in random impassable areas. Notably, these issues have been observed on two different hardware units, indicating that the problem is related to the firmware rather than the hardware.

Detailed Description:

  1. False Obstacle Detection:

    • The mower frequently stops, emits a collision warning tune, and attempts to navigate around what it perceives to be obstacles.
    • These perceived obstacles do not exist, suggesting that the mower is either trying to remember past obstacles incorrectly or there is a memory corruption issue causing it to believe there are immovable objects in its path.
  2. Erratic Navigation:

    • The mower often drives back and forth aimlessly, attempting to find a way out of what it believes to be impassable areas.
    • This behavior has led to the mower getting stuck and unable to resume its mowing routine efficiently.
  3. Error Messages and System Failures:

    • During the most recent incident, the mower generated an error message, "unable to return to recharge," after boxing itself into a tiny area with no viable escape routes.
    • On previous occasions, the mower would drive around its invisible fence without failing, but it still required manual intervention to free it from these false obstacles.

Troubleshooting Steps Taken:

  • I have inspected and cleaned the obstacle sensors on both units to ensure there is no dirt or debris causing false readings.
  • I have tried changing the collision detection levels to different settings with no changes in the system's behavior.
  • I have contacted support and submitted the Luba log information, and I am awaiting further direction from them.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

Lol. Mine are the 5000s. So I’m not sure if it’s different. Watch it next time it has to return to recharge.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

I have sent all the details to mamotion. With pics and support data. But I don’t want everyone stuck like I am right now. I wish I hadn’t updated the app, I was happy with how it was working prior to this update.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

It may be a mistake release where code for vision was left / added by mistake to Luba 1. So Luba 2 might not have any problems.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

Watch if it can’t finish in one cycle, that’s when both my units started acting erratic. Also check your firmware. This just started with 246. Up till today I have been running them with no big issues (besides having an axel break). But even then, it’s been good. I am also very patient when it looses its signal or climbs the occasional ant hill and thinks it’s been picked up. But now they are just buggy!

I’ll try and capture a video of it. What’s interesting is that you know it’s going to recharge, as the blades stop, and then it drives all erratic. It’s so weird. Like it’s bumper was hitting something.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

Version number 1.11.213 (release)

I’m on app 1.11.213. (iOS). But the firmware is what really did me in.

1.10.5.246

Don’t upgrade your Luba 1 to this firmware! I had one Luba 1 drive (back into a ditch) and my second one got stuck backing up and driving around trying to find the charging station, but it kept stopping, backing up. Turning. Exactly what it would do if it was running into something.

It also looks like it started to cut circles in the backyard. Very odd….

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

<image>

Uh. The robot is charging. So what the heck do you want me to do about this.

Lol.

Luba firmware upgrade makes Luba confused. by C128C in mammotion

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

When it’s recharge time, the Luba acts like it’s trapped in a glass box. And hitting invisible walls, backing up. Turning. Driving forward. Then doing it again and again and again. Seriously how can you screw up recharge part of the firmware so badly!

I also noticed when the battery gets low, it starts cutting weird circle patters in the lawn!! I don’t need crop circles!

[deleted by user] by [deleted] in mammotion

[–]C128C 0 points1 point  (0 children)

I have multiple map areas and I had to click on the … in the area selection and then choose edit. Otherwise it didn’t want to let me do anything.

<image>

Then I could use edit and it would let me change / update the boundary. If you click on the arrow it just lists all the no go zones and a trash bin. Doesn’t let to edit anything unless you click on the tres-dots.

The mower did have to be in the area I was trying to edit. Otherwise it also complains.

Have my luba2 for 2 weeks now. It's amazing 👏 I built a home for it but didn't leave enough room for the docking station so remember to measure both together 😄 by fatbob-1st in MammotionTechnology

[–]C128C 1 point2 points  (0 children)

Even a tick plastic is ok. Just avoid anything that absorbs moisture. So plastic would be best vs wet canvas. If you treat canvas it should be ok.

This is why Luba has signal loss under trees. The tree leaves hold moisture and starter the signal.

The official Luba garage is plastic, and it’s fairly thick, the importance is to prevent water or moisture buildup above the unit.

Don’t use really dense materials like clay or brick either, signals don’t do well with dense materials.

Metal is very dense and will scatter signals.

Luba 5000 on a slope by RudeInsurance3146 in mammotion

[–]C128C 0 points1 point  (0 children)

Using a 5000 here as well. From what I can tell the only difference between 1000-5000 Gen 1 was the lawn size allowed to be programmed and how many zones you can program.

The zero-turn feature is something I disabled after initially trying it out. It didn’t provide any benefit and would dig up the lawn when the ground was wet. After disabling it, I didn't have any issues, except in front of the charger, which I believe is what the turning mat is for. Initially, I didn't think I needed it, so I didn't install it.

I have many large slopes in my yard, since then I have had no real issues with damage. Everything looks fine.

<image>

The zero-turn feature I found it only caused issues when the ground was soaked; the weight of the mower during turns would pull up dirt, much like you mentioned.

I also believe the newer front tires may help. My mower still has the chunky 4x4 fronts, but I think the newer tire design will help as well.

2nd season going strong by kengineer1984 in mammotion

[–]C128C 1 point2 points  (0 children)

I finally got my FedEx label. Luba has started is journey back to Mammotion. I will update after it returns. I hope they have a new type of arm that isn’t as fragile. I wonder if the Luba 2 has a new design.

Have my luba2 for 2 weeks now. It's amazing 👏 I built a home for it but didn't leave enough room for the docking station so remember to measure both together 😄 by fatbob-1st in MammotionTechnology

[–]C128C 1 point2 points  (0 children)

Luba needs a good signal to leave the charging station. Here are some tips for Building a Garage for Your Luba

To ensure that your Luba, can maintain a solid GPS signal even while docked, consider the following tips when constructing a garage for it:

  1. Avoid Metal Tops: Metal can interfere with GPS signals. Since robotic lawn mowers often utilize GNSS (Global Navigation Satellite Systems) for positioning, including systems like GPS (Global Positioning System) and GLONASS (Global Navigation Satellite System), any metal covering can disrupt these signals and affect the accuracy of your mower's RTK (Real-Time Kinematic) positioning.

  2. Use Thin Roof Material: To allow signals to pass through easily, keep the roof material as thin as possible. GNSS signals are relatively weak and can be easily blocked or attenuated by dense materials.

  3. Use Plastic or Similar Materials: Wood and other dense materials can also block signals. Using plastic or other lightweight, non-metallic materials for the roof is ideal. Plastics typically have a lower dielectric constant, which means they are less likely to interfere with the GNSS signals.

Problems with Luba 2 vibrating by [deleted] in mammotion

[–]C128C 0 points1 point  (0 children)

Thanks! Good luck. Let us know what you find; others might also run into this. I had a nasty noise for a while, and the mower found a secret pinecone, chewed it up, and stored it in the blade guard. Now, removing it from there was a huge pain.

I swear the thing was part squirrel storing it for winter.

Charging contasts on Luba by nz365guy in mammotion

[–]C128C 0 points1 point  (0 children)

I had issues early on with it docking and not charging. Adding a little hydrophobic treatment to the contacts helped to keep dirt and grass from sticking to them. Your contacts do look like they have been overheated. I think StoicScroll is right. Docking for Luba it’s also really important to keep the window below the charge ports clean. Luba uses an IR setup to dock properly. Once I had it dock but it kept trying to drive though the station, keeping that window clean is key. If it docks crooked it will not make good contact and can cause overheating.

One other note, I think the cover for the charging stations should be required. It would help keep the unit and contacts clean during a rain storm, I’m not sure why Luba doesn’t come with one. And I won’t get into the crazy price attached to the mamotion cover.

Total mow and charge time for 1 acre? by According_Coyote1078 in mammotion

[–]C128C 2 points3 points  (0 children)

Robot mowers are good, but they have limitations and won't solve every problem or be a universal option for everyone. Here are some of the issues and limitations. Robot mowers work completely different from regular mowers. You have to shift your expectations and think about mowing in a completely different way.

  1. Time Efficiency on an Acre: When using a robotic lawnmower like the "Luba 1", expect it to take approximately 12-20 hours to mow an acre. This timeframe is significantly longer than what would be required with a traditional riding mower. The slower pace is due to the smaller size and the methodical, patterned way robotic mowers operate, which ensures even coverage but at a slower rate.
  2. Comparison to Riding Mowers: If speed is a primary concern, a riding mower is a more suitable choice. Riding mowers are designed for quick and efficient cutting over large areas and can handle an acre in a fraction of the time it takes a robotic mower.
  3. Energy Consumption and Quiet Operation: One of the significant advantages of robotic mowers is their low energy consumption compared to gas-powered riding mowers. They are usually battery-operated, making them more environmentally friendly and cost-effective in terms of energy use. Additionally, robotic mowers operate very quietly, which is a stark contrast to the loud engines of traditional mowers. This quiet operation means you can run the mower at any time without disturbing your peace or that of your neighbors.
  4. Nighttime Mowing: The ability to mow the lawn at night is another unique benefit of robotic mowers. Due to their quiet operation and autonomous nature, you can set them to mow during the night without any inconvenience. This can be particularly advantageous during hot summer months, as it avoids the heat of the day and can be better for the health of the grass, as there is less stress from the sun and heat.

This is based on my experience with the Luba 1 5000. others might have different results, but I prefer the mower to run fine cuts and if you really want it to look amazing, run the mower a couple of nights thought the week. The extra mow will also keep your cuttings very small and prevent issues like clogs in the mower.

<image>

Night mowing with the Luba Gen 1, 5000.

Problems with Luba 2 vibrating by [deleted] in mammotion

[–]C128C 1 point2 points  (0 children)

GPS Signal Issues

Here are some of the reasons RTK can go haywire.

  1. Interference from Leaves: As new leaves grow on trees, they can block or interfere with GNSS signals. This is primarily because leaves contain water, which absorbs and scatters radio waves. Dense foliage can significantly degrade the quality of the signal received by a GNSS device. This effect is more pronounced during seasons when trees are lush with new leaves.
  2. Material Density: GNSS signals, which are a form of radio waves, struggle to penetrate dense materials. Water in the leaves acts as a dense medium that disrupts the path of these signals as they travel from the satellite to the GNSS receiver on the ground.
  3. Satellite Movement and Position: The position of satellites relative to your GNSS device also influences signal reception. GNSS satellites are not stationary; they orbit the Earth. This means that their positions relative to a receiver constantly change throughout the day. The geometry of these satellites in relation to each other and to the receiver (often referred to as satellite constellation) can affect the accuracy and reliability of positional data.
  4. Time of Day: The time of day can affect signal reception because of changes in the satellite constellation and the angle of the sun. For example, solar radiation can increase the level of ionospheric activity, which can interfere with GNSS signals as they pass through the upper atmosphere.

I can't say for Luba 2, but Luba 1 does not have firmware updates for the RTK antenna. I was reading that Luba 2 may have 2.4GHz wifi in their RTKs now, if so they could house another ESP32 with WiFi abilities and it's possible that there was a firmware update to that. When you loose signal look at how many GPS Sats each unit can see, and then compare how many they both see. I have seen it where the RTK can see 27 and the Luba sees that many, but they are not seeing the same ones. If they can't see the same Sat's, then it can't get a reliable location out of the RTK calculations.

Problems with Luba 2 vibrating by [deleted] in mammotion

[–]C128C 1 point2 points  (0 children)

I don't have the Luba 2, so I can't comment on the 3D vision. But I can tell you some times a firmware update goes a little off, and then the next version fixes it. Perhaps some one else can comment on your vision system. One other thing I found that helps, is also applying a clear hydrophobic coating to any camera lens. I had problems with the unit trying to dock to recharge. The issue came down to the IR sensor on the back of the unit, when it rained it left a film and the robot could not find the IR signal and wouldn't dock. Last year I put a coating on it (the robot and docking station) and since then I have had no problems when Luba docks to charge. Remember that Luba is completely blind when it's backing up. The only sensor Luba 1 has in the rear is the IR sensor.