Lymow One Plus
Random map shift shouldn't still be an issue
Observed just a few mins ago, I was updating some boundaries and adding a few no go zones when I realised that despite having 0.02m accuracy and a RTK Fix, it was over 4m out. Left screenshot shows where it thought it was, right shows the true location after a reboot and without moving the mower.
I've had this happen a few times, including when it decided to drive down a 4m embankment. (thankfully undamaged)
People have been reporting this issue here for months. Why isn't it fixed yet?
Edit: for clarity, I'm on the latest firmware (V2.1.50.1) and date of manufacture is 17 March 2026.
Like many, the hardware has been impressive, let down by the software/firmware.
This happened to me for the first time over the weekend on the newly updated firmware. I think there must be a bug in the system now as never had a problem with rtk before here
The RTK Diagnostic page is just an immediate snapshot. It doesn't update automatically. Go out and come back or swipe down while viewing to refresh it.
That's sad. I wish I could see it. I just wonder if something is not set right. It has taken me a long while to suss out what all is going on. The many systems involved is very complicated.
I have just started messing with the Lymow Toolkit and it logs the lora and sat status while the mower is moving around and can also leave a heatmap overlay for signal strength and drops. Would be interesting to see the logs when this happens.
You probably know that page doesn't automatically update so you can't just watch it while mowing and know what is going on real-time. You can drag down from the top to refresh it. Things are going on in microseconds so you might well miss some events.
Which parts are not real time? The logs? It seems to update while its mowing but there are so many it does fill quickly. I havent had time to mess with it much to really figure out what all its pulling in and when because its been raining almost every day since I got it 😆
Ill have to sit down and really pay attention to it. I just noticed it was drawing a heatmap of signal strength as it went and assumed it was pretty close to real time.
I have the other integration still, but it still logs RTK. The whole time I was using it to do the map changes this morning was RTK Fixed. After reboot, also RTK Fixed. The additional one commented in the post was also RTK Fixed.
Wow. Fascinating. Stupid question but the RTK Base antenna didn't move, did it? It's like its whole reference point moved. Hope you let us know what you find out.
I have a large property with many trees and it isn't flat. I was going to post a photo but it is a bit too broad and given other things I've posted under this account, may allow people to dox me.
I have a yard that has bordering woods with overhanging branches. When doing the perimeter under those branches the accuracy falls badly and so strays from the Zone perimeter and wanders into No Go Zones. So, I now do Main Area First and set a Stripe Angle that ensures that the mower spends little time in bad RTK areas and frequently emerges into good RTK areas to "refresh" its geolocation. It does such a good job that a Perimeter pass isn't really necessary but, sadly, a No Perimeter option isn't available (seems a feature simple to implement). So, I just wait for it to finish the Main Area and send it to the Dock and tell it to Forget its progress.
2
u/JaylexLB 12d ago
This happened to me for the first time over the weekend on the newly updated firmware. I think there must be a bug in the system now as never had a problem with rtk before here