ReachView 2 beta v2.1.1

[egor.fedorov]

Hi!

I’ll try to address some of the mentioned issues.

@jcampen

Firstly, seems there is no way to update from within ReachView v1.2 to 2.1.* or even 2.09 from what I could see?

The new app and even the new image are rewritten from the ground up. Updating from 1.2 is borderline impossible, even if we thought it would be worth the effort. New image contains countless new features including Linux-level modifications which will help us enable support for accessories, such as USB modems and such.

Updating from 2.0.9 is possible by going to “192.168.1.XX/updater” url. There is also a link inside the settings tab(marked with a gear).

@jcampen

I suggest to please have a link to the newest FW update files as you post them so people updating from v1.2 get the latest fw to flash with and one without the buggy 2.09 ?

That’s a fair point. But during this phase, we also need to test and smooth out the update experience itself and just putting out new firmware with every update would be cheating

@jcampen

When I change the coordinates format from LLH to XYZ it doesn’t hold and always reverts back to LLH after I switch pages.

Good idea. We’ll do something about it.

@jcampen

When I changed over to use another wifi network, it lost most of the settings and I had to redo them all again. Is there anyway to save the settings or back them up?

Settings are saved every time you hit apply. If they are lost, then it means something went wrong. Probably the file got corrupted. It should be connected to an unfortunate powerdown. Are there more details to this?

@jcampen

I set the coordinates accumulation time to 15min but it seems to take much longer. Sometimes up to 30min to 1hr or more to get a Base coordinate fix. This is even when I have constant 6 to 8 sats well over 45

I don’t quite understand. What do you mean by Base fix? Does the procedure itself start?

@jcampen

Sometimes in Rover it shows I have 8-9 sats over 45 but when i go to the Base screen it might only show 4-5 sats over 45. When this happens it sits often in Float mode mostly but can also be in fix mode. (inconsistent?)

By Rover and Base you mean two different Reaches? Check enabled GNSS in the settings. One probably has more systems enabled and therefore shows more satellites.

@jcampen

I like to dedicate one browser wholly for Reach use to avoid cache issue etc. I tried Opera for this. When first loading ReachView in Opera it doesn’t get past the Emlid logo first page screen. Once I load it up in either IE or Firefox, after then it loads ok in Opera. Except the settings might be all different again. This also might happen when switching from IE to Firefox they settings seem different sometimes. I suppose this is again a cache issue?

Most definitely. We are working on this problem.

@jcampen

Suggestion:
Presets for Base and Rover.
Ability to Save settings and save them as presets.

Updated documentation, which no doubt is in the queue. But a quick setup guide for now would have saved me quite a few hours.

We are currently trying to figure out a way to do this without cluttering the interface and experience.

Things still might change considerably, so it’s a little early for the docs.

Thanks for the feedback!