Facet & SW Maps no longer working with NTrip

@Simpsriu, I turned off all unnecessary NMEA messages. The idea is to have plenty of available bandwidth over Bluetooth to make sure the GGA is sent to the caster every 10 seconds. Most NTRIP Casters that I’ve used will disconnect if they don’t receive a GGA every 30 seconds or less.

I obviously don’t know if this is your issue, but you might want to try it ?

My Torch Settings

Menu: Message NMEA
1) Message GPDTM: 0
2) Message GPGBS: 0
3) Message GPGGA: 1 (could be higher if you wish)
4) Message GPGLL: 0
5) Message GPGNS: 0
6) Message GPGRS: 0
7) Message GPGSA: 0
8) Message GPGST: 4  ( <5 keeps most Apps happy reporting the RTK residuals)
9) Message GPGSV: 10 ( this one is a bandwidth HOG ! )
10) Message GPRMC: 1
11) Message GPROT: 0
12) Message GPTHS: 0
13) Message GPVTG: 0
14) Message GPZDA: 0
x) Exit

My Facet Settings:


Menu: Message NMEA_
1) Message UBX_NMEA_DTM: 0
2) Message UBX_NMEA_GBS: 0
3) Message UBX_NMEA_GGA: 1
4) Message UBX_NMEA_GLL: 0
5) Message UBX_NMEA_GNS: 0
6) Message UBX_NMEA_GRS: 0
7) Message UBX_NMEA_GSA: 0
8) Message UBX_NMEA_GST: 4
9) Message UBX_NMEA_GSV: 10
10) Message UBX_NMEA_RLM: 0
11) Message UBX_NMEA_RMC: 1
13) Message UBX_NMEA_VLW: 0
14) Message UBX_NMEA_VTG: 0
15) Message UBX_NMEA_ZDA: 0

I got the NTRIP to work, But now when I send the file to my GIS guy, Thru .CSV file, it shows 1.5m difference fom collection point.