Wait, so WIFI can be turned off on the rover? will that help eliminate any noise?
Yes, you don’t need your home WiFi on the core at all if everything is functioning properly. HaLow for primary, turn on cellular for backup just in case. As for noise, can you elaborate on what issue you are having?
There is a problem with your data center. RTK status is 1 and HaLow is false. Have you tried unplugging the DC power and core battery for 5 mins and then plugging in the DC followed by the core?
The most common firmware complaints:
- Yarbo made changes after the season that doesn’t help last season
- Yarbo made changes during the season when it was working fine
After is worse, can’t test till next year, and then if it sucks you are stuck with it all season, then the next fix comes after the season is done, put on repeat, nothing gets done timely.
If they did small changes and more frequently things would improve faster.
Smaller changes more frequently is the way in my opinion.
Yes, constant iterative bug fixes and less frequent major releases. Bug fixes need to be decoupled from the major releases. I think they need a public beta test program too for things that roll out of closed beta testing to roll into next. Something as simple as Apple does it, toggle on the public beta if you want it and toggle it off if you don’t. Rolling updates wouldn’t be needed then IMHO. After 2 weeks of public beta without big issues, ship it to all. Those who have automatic updates enabled (this should be a toggle) it will auto install at the time and day specified by the end user. No unpredictable updates time/day. Otherwise it will inform the user there is an update available when they open the app and they can choose whether or not to install it. If they say no, they should be able to go back into the app and check for updates and install at any time. Not have to wait for the next update or contact support. The app needs to be fully backwards compatible through a couple of firmware versions.
I’ve been a beta tester for Apple’s software for some time and can agree that it’s a good system. For me, I don’t mind the bugs in exchange for early access to new features, but others I know just want something simple that works every time, and have no interest in beta testing.
Agree, Agree, Agree, we can’t continue to wait an entire to season to get minor issues fixed. In many cases they’re items that were broken in a previous release. I can think several of from last year that still aren’t fixed - not new features, but bugs that have simply not been addressed.
Remembering how many times this was mentioned last year, I ran out of fingers.
Agree with all of the above.
Yarbo needs two dev paths. One for major new feature releases, and another for quick bug fixes.
The current process of taking an entire season to release an update is harmful in that the update doesn’t appear until the season is almost over, and as a result, no one can test and provide feedback for the updates until the next year when the season begins again. If the update wasn’t ideal, it will then take another YEAR before another fix can be received by the end users. Dev cycle is simply too long.
Agree with all of that. I would also recommend doing a roll back option for all updates.
Everyone who agrees, please click the link above and vote on that feature request.
Can’t keep doing the same thing and expect different results.
I did all that - it’s working again!
Thank you Bryan.
Awesome, glad to hear it!
I don’t see, in the new app, where the new pathway offset can be managed. Does this need the new firmware to show up?
Welcome to the community. Yes. I think so.