Reach - Bluetooth related and app talk

TB_RTK · March 28, 2016, 8:01am

This post is a follow up from from this post - http://www.emlid.com/reachview-update-bluetooth/
Since ReachView version v0.2.2, its possible to connect phone/tablets via bluetooth.
I`m new to all this so i like to share experience with application that works, could work and so on.

Tested on my phone, a Samsung s5 with android version 5.0

Status:

Mobile topographer pro (Working)

Bluetooth GPS Provider (working)

https://play.google.com/store/apps/details?id=de.mobilej.btgps

Lefebure NTRIP (Working) - https://play.google.com/store/apps/details?id=com.lefebure.ntripclient

RTKGPS+ (Not recommende.)
I have found another app, called rtk gps - https://play.google.com/store/apps/details?id=gpsplus.rtkgps

igor.vereninov · March 28, 2016, 8:35am

Lefebure NTRIP also supports mock location over Bluetooth, but we have not tested it yet. RTKGPS+ will not work with solution input, you can stream raw data to it and use it to calculate position, but I would not recommend that. The app has not been updated for a while.

TB_RTK · March 28, 2016, 8:46am

Hi,
yes, all i could get with rtk+ was connection error (111).

igor.vereninov · March 28, 2016, 8:47am

Does Lefebure NTRIP work for you?

TB_RTK · March 28, 2016, 9:08am

Yes, eventually.

Made connection with the following setting, bottom picture.
Had to use “secure via reflection”

igor.vereninov · March 28, 2016, 9:09am

Nice! Mock locations functional as well?

TB_RTK · March 28, 2016, 9:10am

both on and of yes.

igor.vereninov · March 28, 2016, 9:14am

Cool, thanks! Lefebure can also receive corrections from NTRIP, but we do not support input of correction trough bluetooth yet.

TB_RTK · March 28, 2016, 9:55am

Bluetooth GPS Provider also work - https://play.google.com/store/apps/details?id=de.mobilej.btgps

egor.fedorov · March 28, 2016, 10:39am

Nice review!

TB_RTK · March 28, 2016, 12:37pm

Nice

Pi_RTK · March 29, 2016, 7:02pm

If you are interested I’m actually using a Raspberry Pi to do RTK corrections via Lefebure NTRIP via bluetooth… It works quite well!

Is RTKlib on Reach configurable via bluetooth?

mikhail.avkhimenia · March 30, 2016, 9:08am

@Pi_RTK At the moment Reach uses Bluetooth only for an output of the solution.

TB_RTK · March 30, 2016, 2:49pm

Survey for fence - #8 by Pi_RTK
Quote from another post

ducatienergia_ebike · July 8, 2016, 1:25pm

Hi everyone.
I’m using Mobile Topographer Pro, but when I start surveying I see positions that differ a lot from what appears in ReachViewApp. Why does this occur?

TB_RTK · July 8, 2016, 1:40pm

Are you also using ntrip?

ducatienergia_ebike · July 8, 2016, 1:52pm

You mean Lefebure NTRIP Client? Yes, I configured it as suggested in Reach guide. I also tried Bluetooth GPS Provider.
Both gave me results that differed from ReachViewApp.

igor.vereninov · July 8, 2016, 4:13pm

Please update your ReachView, this bug has been fixed (there was a lat/lon mixup in the status).

ducatienergia_ebike · July 11, 2016, 7:35am

Hi Igor,
thanks for your reply.
The screenshots I posted were taken with ReachView version v0.4.4.
I updated to v0.4.5, but nothing changed.
What astonishes me the most is the big difference in altitude.
When I reach a fix solution, there’s no difference in lat and lon between ReachViewApp and Mobile Topographer, but altitude in Mobile Topographer is still wrong.
Any other possible explication?

igor.vereninov · July 11, 2016, 8:46am

Hi,

The lat/lon mixup should have been fixed in 0.4.4, please try clearing the cache of your browser. At least it would be good to see that there is no lat/lon issue.

Height is most likely different because NMEA reports height above geoid.