Open geomoes opened 6 years ago
Dear Geomoes, First usually when sat are not filled with colors, it is because you do not have the current ephemeris. Try to use precise and download ESA ephemeris from the tool menu while running. Second before using RTK with base and rover, try only with Rover and PPP static algorithm.
Next could you provide the crash log?
Dear eltorio, i've tried the configuration above. The satellites stay outlined even with 'ESU Precise ephemeris from ESA' checked (Before I used Broadcast-Ephemerids). The app keeps running without crashing.
ESU Precise… is not enough While running you need to inject the ephemeris with the small menu on the top right , next tools and download and inject … ephemeris. If you already download them and no new exist they are automatically injected, but you can still do it manually
For the crash you are speaking 1st, I think when you get the ephemeris downloaded OK (via broadcast). You get a FLOAT lock, and it crash could you retrieve the android crash log?
OK, in the menu I only see the option to load and use the IGS ultra-rapid ephemeris (500 kB). I downloaded them and now a few satellites are colored (my M8T is configured to use GPS, GLONASS and GALILEO). Still looking where to find the android device log. The app now crashes when more than 5 satellites are colored (I suppose these are the satellites with a good signal, that can be used by thhe app?).
Obviously I don't have the same crash! Colorored sat means OK for use (good elevation/ good snr / ephemeris OK) ESU ephemeris does not include predicted ephemeris for other constellations than GPS (I think) so probably you have some Galileo and Glonass SV without ephemeris.
I don't know if that helps, but here is the last .trace file related to the crash reported above.
1 0.010: setsock: setsockopt error 3 sock=79 err=95
1 2.273: setsock: setsockopt error 3 sock=85 err=95
It's strange, but I use the same configuration with MapGis - NTRIP-client, which is also based mainly on Rtklib (version 2.4.3 b29) without any issues.
Hi, finally I got it to work properly. The problem was, that I had to choose rtkgps+ as mock location service provider in developer option before run rtkgps+.
Same issue here. App crashes when mock location reporting fails. It happens on the first solution, no matter if it is float, static, whatever.
Hi, I actually started with the u-blox NEO M8T chip from Drotek. I use the M8T as rover and get precise positioning using Rtklib with officially provided RTCM (2.0) data as base. My device uses a Bluetooth modul (HC-05) to connect wireless to a PC or tablet. On a PC (Win 10) I've installed the customized version of Rtklib (demo5 version from www.rtkexplorer.com), which is a adapted version of the 2.4.3 b29. This works fine with the M8T and I get a FIX and precision down to 2cm.
On my Android tablets I use the same configuration (with identical start/stop commands) with RTKGps+ (vers. 1.0 alpha 26). After pairing with the M8T, the app shows the satellites from the rover. As long as there is no FLOAT, the satellite columns are displayed only outlined, but not filled with colours. When the app changes to FLOAT, the satellite columns are colored, but the app crashes after a few seconds.
I'm using the app on a HUAWEI M3, Android 7.0 the chip is a u-blox NEO M8T I'm sending the following start / stop (provided by rtkexplorer.com):
In the RtkGps folder on my tablet I have a rtkgps_...trace file with the following errors: