Hi, I’m new here from Spain.
I 've received one Reach module last week. I’ve started to config my module, but I’m having some problems.
About wifi configuration ok…It’s easy (more or less). Then I enter on my “ReachView App”, select “config” tab, and there I can Start, Stop and change the config.
In my case I set the module as ROVER.
The next step is to choose the “positioning mode”… When I load the deafult single reach configuration, all it’s OK, I start receiving signal and I could see the status signal bars on the ‘Status’ top tab and also I could see how lat,long,height table is filled with an approximated location.
If I want get more accuracy on my location, I will have to set one NTRIP client. Then I select “Input source for base correction” --> ntripcli, and I fill with my data (IP, port, mountpoint, user, passwd). I save mi config and apply it, but on my satus tab no data is coming, not even a single status signal… no bars, “0” on my lat, lon height…
Anyone could help me what step I’m doing wrong? Help will be so much appreciated.
Then I got some little differences like start/stop in one button or also less fields in configuration tab. At this moment, I could get single status, but I was having the same answer when I set the NTRIP base corrections… Nothing.
Yesterday I tried it again and I updated the device using the ‘Update’ button on Logs tab. I could see how a blue led was remaining for few seconds and then I refresh the ReachView App and finally version v.0.0.2 appeared on this tab (Logs).
Then all things went better… For single reach configuration easy again and very fast. I tried again to set my NTRIP configuration and …finally I got FLOAT!!!
I was there waiting for a while…maybe for 15 minutes, but I couldn’t got FIX solution. Are there some advices to get FIX?
(screeshot from yesterday)
Today I will try it again, making some config changes…
Would it be possible to know how many satellites (total number) I’m tracking each moment? (obviously more sats than I could see on reachview bar status)
I want to use the correction provided by University of Padua http://184.108.40.206/Web/index.php because I have access to ntrip service (i’m able to do this with my old lea6t and rtklib on my laptop)
but … I tried to configure my device but I’n not able to receive the info from base station
At the first, I would like to know if you have updated your Reach device or if you are trying to set it like your device arrived. In my case when we update the Reach device properly, I started to get corrections from the GNSS network which I was trying to connect. Before that, zero data. First I reflashed the Firmware (http://docs.emlid.com/reach/firmware-reflashing/) and after I pushed the ‘update’ button inside the Reach AppView.
I am only using one device, I mean, I’m not usign one as base and other one as rover. I configure it as you can see on the next picture
inside the config tab you could use the output params, for example could create a file with NMEA output solution, or data raw, etc… Then you could see all NMEA received messages. By the way, when you are running your reach appview, if you are really getting corrections from your base station, I think you always will have to see some grey bars together green/yellow/red bars. Something like this
When you are connecting to Reach Wi-Fi with your laptop it does not have internet access, this is why you are not getting data from NTRIP. You need to connect your Reach to Wi-Fi network with internet access.
This is my situation
I have Ipad connected to internet then I open wifi connection I select the reach device so I’m able to open the reach app I set the ntrip connection
is it correct ?
In rtklib I can check if the ntrip works opening the ntrip mount point … and if I see the list I’m sure to receive the ntrip correction (in fact with mi old lea6t I can receive the correction in my area)
in your last config screenshot I could see you had put “MAX3” as a Mountpoint to connect. That is a ‘Network solution’ but is not a single antenna… we didnt try if this kind of mountpoint works on reach yet or if only work with real antennas, when we will try it, we will post it here… Maybe today we will test some kinematic track with reach device and export it to kml file and we could see how accuracy with the map has the recorded track.