I upgraded to firmware 3.13.1 today and I am currently running app version 3.18.2. I also received and installed a new set of the high RTK antennas today.
With spring coming up, it seemed like a good time to try the new positioning service. I figured I might benefit from NetRTK because of the tree cover on my property. I selected that option, but it did not seem to do anything. Is anyone having any luck with NetRTK yet? Also, does Yarbo have a video up explaining the new firmware features and positioning options?
After trying NetRTK, I attempted to switch back to the Data Center, but the app keeps erroring out. I then performed a device reset and added the robot back into the app, but functionally, everything is still acting the same.
The main issue I am seeing is with manual control. At first, everything seemed normal. I went into the app, undocked the robot, and tried to manually move it via Bluetooth. It moved about 5 to 6 feet and then stopped unexpectedly.
I released the controls and tried directing travel again through the app, but the same thing happened. It feels like there is an extreme Bluetooth delay or control lag. The robot only moves about 5 to 6 feet before stopping again.
I also tested with the physical remote and got the same result. However, Follow Mode appears to be working normally.
Current setup:
Firmware: 3.13.1
App version: 3.18.2
New high RTK antennas installed today
Tried switching to NetRTK
Unable to switch back to Data Center due to app errors
Device reset completed and robot was added back into the app
Manual Bluetooth control: severe lag/stops after 5 to 6 feet
Physical remote: same result
Follow Mode: working normally
Is anyone else having issues like this with the new firmware? Any suggestions on what to check, reset, or reconfigure would be appreciated.
I often see this bluetooth lag. I’ve been begging Yarbo to add a toggle to avoid issues like this. Try disabling bluetooth on your phone temporarily when using Yarbo and the lag will go away. As for the NetRTK not switching back, I’m betting it may have been related to the bluetooth lag as well. It has a tendency to switch back and forth frequently causing the app to lose network connection when it switches.
On a side note. One thing that often helps is the standard reset process. This solves a lot of issues. Unplug power to the DC and the battery cable on the core for 5 mins. Plug the DC back in, then the core and power it up. This seems to solve a lot of weird little issues.
At the moment, we don’t have a dedicated video explaining NetRTK yet, but I’ll definitely pass your feedback along to our team.
After switching back to the Data Center, could you let us know if everything is working normally now?
As for the manual control issue, you might want to refer to Bryan’s suggestion and try temporarily turning off Bluetooth on your phone to see if it helps improve the situation.
Please feel free to keep us updated—we’re here to help.
I’ll give that a go and I figured most of my issues I’ve seen so far are likely due to the Bluetooth issue. It was just weird that I never had this Bluetooth issue until I upgraded to the new software version.
That is a little strange for sure. It’s been there for a while. But it seems device dependent (phone). Not everyone has the issue with lag standing next to it, but it does happen.
I have seen the lag with android phones and tablets. I have not seen it with my iphone, but the odd issue yesterday with no gps on bluetooth will stop me from using bluetooth unless I have to.
Story time… Last night big storms coming, yarbo can’t get to dock as it has to go past concrete steps on its path down my concrete sidewalk, (ultrasonic sensors in pro mower) so I go in to settings to turn off sensors, but by now storm is over us and my Starlink does not work. So yarbo goes off line. A few hours before this I took yarbo’s permission away from using bluetooth, so I had to change that back and turn on bluetooth and manually drive yarbo to the dock. It was a few minutes of panic to get yarbo put away.
But another reason why vision and ultrasonic sensors don’t work together on yarbo. It should be able to see concrete steps and go past them. Instead it sent me a notification of issue, and just sat there going back and forth a few inches at a time.
That was like a super annoying comedy of errors. I’m sure it wasn’t fun.
So maybe the Bluetooth problems are an Android thing?? I’d also wonder if maybe some people have a loose Bluetooth antenna inside their Yarbo or something.
Your Starlink went out during the storm? I’ve never experienced that before personally. While I don’t use Starlink at our main house, I do have it at another property and anecdotally I’ve never noticed it failing during inclement weather.
Oh yeah, starlink drops out if it is raining hard, and sometimes just before it even rains, like last night. I have the original round dish that is supposed to be better than the new ones as it has more antenna in it. I know 3 others that have the same drop out in rain. Maybe it is a Wisconsin thing?
I do not miss those satellite weather drop outs. Had DirecTV for many years and it would do the same. Then there could be a tornado out there and it would work fine. Was always right before rain and during a very hard downfall like you said.
Yeah I remember the old satellite days, you want to watch the weather, but nope, no tv (before internet days).
I just switched to T-Mobile from Verizon (no home internet available here) and they offer home internet for a price cheaper than Starlink, I am tempted, did a speed test last night when starlink was down and got 300mbps, so not bad.
I live miles from any fiber hook ups, so only dsl is available here with speeds of 12mbps. So limited on choices.
Yeah I understand that. My in-laws have the same struggle and Starlink was a game changer for them. They are now stream only. I’ve been stream only for TV for a decade at least.
I have the OG Starlink and never had issues with it when a storm was on us. No it acts in standby fall over mode for our fiber service.
As for the Bluetooth issues, I use iPhone. I did what was mentioned in the first response and my system is working great now. No Bluetooth lag, netRTK working, new maps created. Today was a win, win. Thanks everyone! My signal is solid even with all the trees!
UPDATE: got the new lawn mower attachment. Quick update: I was finally able to switch back from NetRTK to Data Center mode to compare the signal.
After switching back to Data Center, it appears I am getting more satellites than I was getting with NetRTK. The GPS/RTK behavior still does not seem fully normal yet, but Data Center appears to be giving me a better signal than NetRTK at the moment.
So my current suspicion is that either:
NetRTK is not fully active or stable yet on my unit/location,
there is a firmware/app issue with switching between NetRTK and Data Center, or
the robot is seeing satellites, but not getting a reliable correction/fix while using NetRTK.
For anyone else on the new firmware, are you seeing better results with Data Center than NetRTK? Has anyone successfully gotten NetRTK working reliably yet, especially around tree cover?
That seems strange. I’ve been using NetRTK for almost a year in testing (off and on). Because my DC’s are ground mounted at the back corner of my house and not ideal conditions, I would periodically get GPS pauses. Nothing major, just sometimes when the rover was near obstructions. PPVS most of the time would get it through it. After switching to NetRTK those incidents almost completely went away. I find it to be very reliable and stable and haven’t really noticed any difference in the detected satellites. But, I do notice at a certain time of day I see upwards of 32 satellites and oddly that is when I seem to have the most issues. When I drop back down into the mid 20’s, I have a very stable GPS experience (on the DC).
Also should note that NetRTK is not a savior for tree cover. If your DC is obstructed, then it will 100% help in those situations. The rover AND the reference station (either DC or NetRTK Base) need to see the same satellites for correction data to be valid.
I’ve been using NetRTK since they released it, and to be honest I completely forgot about it, which is the ultimate praise I can give. For me anyway, it just works. Same with my Mammotion bots. They’re using the equivalent service and it has also been rock solid.
I suspect the netRTK coverage and accuracy must vary depending on where you live.
