ReachView 2 beta Bug Reports

@RickJ Did you find the menu icon on the top of the app?

Hi Igor,

Yes, I have if you mean the 4 lines.

Version 2.0.9

And if you click on the menu you will see links to the screens with all the functions you are looking for. If you do not see them, please post screenshots.

Don’t get communications link info and seem to loose configs.
Is there somewhere to set ports?
I was not selecting RTCM messages because the selection boxes where offscreen on my pocket phone.

When I flashed the base unit, Windows said it could not format the Edison F file after completing reflash. Can this be a hardware problem?

9 posts were split to a new topic: Converting UBX files to RINEX using RTKCONV

Could not connect to a strange name wifi (name included a *) with a very long password including letter other than 0-9 and a-x.

Tried Reflashing unit this morning. Intel Phone Flash Lite showed successful flash with no errors.

No change in ReachView. No Correction information. All data configurations show only internal receiver connection.

Only setting for mode is Kinetic, No Stable or Single Mode. Only solution is Single.

I would revert to previous image, but last Version while showing Fixes with good resolution gave meter+ errors in ENU on both Reach and postprocessing.

Any ideas?

OK. Some progress…

I abandoned the smartphone WebBrowser and went to Firefox on my Ubuntu 14.04 Trusty OS 32Bit,

And guess what !! The initial view shows the missing Connections SetUp screen. I tried Chrome on my smartPhone, but could not access the Reach units. Same problem with My Windows7 WebBrowser. Any suggestion?

Next step is to see if if there is FirefoxWebBrowser for Android & Test it.

Hello again. Well, Both Reach units appear to work good for Beta release. Now, I’ll look more at suggestions for my planned uses.

I have no idea why the some of the WebBrowsers don’t work with this Beta Version. Obviously, there is some incompatability somewhere.

I am now using Firefox Browser with Android. Entering “192.168.XX.XXX” in Website search where XX.XXX or XX.XX is your rover and base addresses.

By the way, the GNSS Predictor appears to be working. Nice Feature!!

Cannot connect to open WiFi. “Create” button is not clickable. Only tried from Android phone.

Thank you all for the useful feedback!

Confirmed issues:
RCH-352: Create button not clickable for open networks (@savvy0816)
RCH-344: SSID should allow printable ASCII characters instead of only 0-9, a-Z (@savvy0816)
RCH-353: Wi-Fi Password should allow any characters (@tobias-dahms )
RCH-354: Browser caching issues (@TB_RTK )

@TB_RTK

-GNSS predictor does not update coordinate in real-time, but it is not needed as it is for an area.
-Reach naming allows big letters, but no special characters. This is reasonable because it is used for device local name, access point name and is buried deep in the OS. We do not want issues potentially caused by special characters.

@Andreas_Ortner

I am not sure if I follow. How reproducible not saving of settings is? Is it only for the base settings?

@RickJ

Please do not use default browser on Android, it does not support many modern features. We do all of our testing on Chrome and Firefox. These should work well.

@Charlie_Robinson

This is very strange. Did you try to connect to 192.168.42.1 address? Rebooting the module did not help?

@savvy0816

Which version of RTKCONV did you use?

1 Like

Confirmed. Good catch! RCH-356 issue.

@igor.vereninov : That address worked - I was trying the addresses in the quickstart guide, with :5000 appended. Cheers :slight_smile:

Hi,
i have a minor bug: when connecitng to a WIFI, the interface won’t allow anything bat a-z, 0-9 in the WAP2 password, while WPA2 PSK can (and do) contain special characters and punctuation

Hi Johannes,

Thanks! This one has been reported:[quote=“ivereninov, post:31, topic:4311”]
RCH-344: SSID should allow printable ASCII characters instead of only 0-9, a-Z (@savvy0816)
RCH-353: Wi-Fi Password should allow any characters (@tobias-dahms )
[/quote]

2 Likes

yes, sorry, i searched here but didn’t see it

Cannot specify position output frequency (Hz).
Cannot specify individual NMEA strings in position output: GGA vs GSA, etc.

I did try to do it again. I think the error was my own. I used reachlocal to connect to reach and i had 2 windows open.
maybe in did use the false reach.

solution: i did rename reach into reachbase und reachrover.

another question: where i can find the .conf files on reach using ssh.?