RS2 fails to connect to real-time network via NTRIP (problem began in last 24 hours)

Guleed · August 1, 2021, 1:48am

My RS2 does not connect to the NTRIP network of the California Real Time Network (CRTN). I am only able to retrieve single solutions from satellites in view (not float). I’ve attempted to reconnect the RS2 to the NTRIP stations over the past 10 hours with no success. This is unusual because I have been able to connect the RS2 to CRTN for the last 7 months without fail, including a brief 1-hr-long interval of useage about 24 hours ago. Since the successful connection to CRTN just yesterday, I made no changes to the settings of my phone, RS2, or ReachView 3. At present, the status of the CRTN stations (updated every 5 minutes on their website) shows the stations are working. This seems to suggest that my current inability to connect the RS2 to CRTN stations is probably related to my device or its settings.

In summary, NTRIP corrections using CRTN are not working on my RS2. The failed connection to the CRTN is unusual because of its abrupt onset.

Edit (Aug 1): I actually updated the ReachView 3 app. The problem I have began immediately after the update to Version 6.4.

Any suggestions towards a solution would be greatly appreciated.

Current ReachView version: 2.25.2-dev
ReachView 3 Version 6.4

System report:

Simple system report

app version: 2.25.2-dev
current_network:
  ip: 172.20.10.7
  security: wpa-psk
  ssid: iPhone
enabled: true
mode: client
base_mode:
  base_coordinates:
    accumulation: 120
    mode: single-and-hold
  output:
    io_type: tcpsvr
    settings:
      cloud:
        mount_point: ''
      lora:
        air_rate: 9.1099999999999994
        frequency: 902000
        output_power: 20
      ntripsvr:
        address: ''
        mount_point: ''
        password: '***'
        port: -1
      serial:
        baud_rate: 38400
        device: ttyEXTS0
      tcpcli:
        address: localhost
        port: 9001
      tcpsvr:
        port: 9000
  rtcm3_messages:
    message_1004:
      enabled: false
      frequency: 1
    message_1006:
      enabled: true
      frequency: 0.10000000000000001
    message_1008:
      enabled: false
      frequency: 1
    message_1012:
      enabled: false
      frequency: 1
    message_1033:
      enabled: false
      frequency: 1
    message_1074:
      enabled: true
      frequency: 1
    message_1084:
      enabled: true
      frequency: 1
    message_1094:
      enabled: false
      frequency: 1
    message_1124:
      enabled: false
      frequency: 1
    message_1230:
      enabled: false
      frequency: 0.10000000000000001
bluetooth:
  enabled: false
  pairing:
    discoverable: false
    pin: '***'
correction_input:
  base_corrections:
    io_type: ntripcli
    settings:
      bluetooth:
        send_position_to_base: false
      cloud:
        mount_point: ''
        send_position_to_base: true
      lora:
        air_rate: 2.6000000000000001
        frequency: 902000
        output_power: 20
        send_position_to_base: false
      ntripcli:
        address: 132.239.152.175
        mount_point: P654_RTCM3
        password: '***'
        port: 2103
        send_position_to_base: true
        username: Redacted
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        send_position_to_base: false
      tcpcli:
        address: localhost
        port: 10001
        send_position_to_base: false
      tcpsvr:
        port: 10000
        send_position_to_base: false
device:
  power_on_bottom_connector: false
  privacy_policy_accepted: true
  role: null
  usage_analysis_accepted: false
logging:
  logs:
    base:
      format: RTCM3
      started: true
    correction:
      format: RTCM3
      started: true
    raw:
      format: UBX
      started: true
    solution:
      format: LLH
      started: true
  settings:
    debug: false
    interval: 24
    overwrite: true
network:
  tcp_over_modem: false
position_output:
  output1:
    io_type: bluetooth
    nmea_settings:
      bluetooth:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      serial:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpcli:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpsvr:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
    settings:
      bluetooth:
        format: NMEA
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        format: ERB
      tcpcli:
        address: localhost
        format: ERB
        port: 9000
      tcpsvr:
        format: LLH
        port: 9001
  output2:
    io_type: tcpsvr
    nmea_settings:
      bluetooth:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      serial:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpcli:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpsvr:
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
    settings:
      bluetooth:
        format: NMEA
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        format: ERB
      tcpcli:
        address: localhost
        format: ERB
        port: 9000
      tcpsvr:
        format: LLH
        port: 9001
positioning_settings:
  elevation_mask_angle: 15
  glonass_ar_mode: false
  gnss_settings:
    positioning_systems:
      beidou: true
      galileo: true
      glonass: true
      gps: true
      qzss: true
    update_rate: 5
  gps_ar_mode: fix-and-hold
  max_horizontal_acceleration: 1
  max_vertical_acceleration: 1
  positioning_mode: kinematic
  snr_mask: 35
sound:
  mute: false
  volume: 100

wizprod · August 1, 2021, 4:43pm

I would argue the other way: if you haven’t changed anything, the origin of the probably is likely external to your device.
I would do 2 things:

first contact CRTN and ask them to troubleshoot with you.
then update to the newest released non-beta firmware (26.4)

Guleed · August 1, 2021, 4:52pm

Hi, Christian. That sounds like a good suggestion.

I’ve tried updating the firmware, but I cannot find the version you’ve suggested (26.4). The only firmware update available to me is a beta (27.0.beta.2-dev); however, even when I try to update to the beta, one of the tests fails. That test is Test 8. Is that meaningful?

wizprod · August 1, 2021, 5:08pm

That’s odd.
In that case you write to Emlid Support. Remember to include the serial number or your device, and refer to your thread here on forum as well.

Guleed · August 1, 2021, 5:38pm

I will contact them and see what they suggest.

Note the edit now to my initial post: I’ve realized that I actually updated the ReachView 3 application to Version 6.4 just before the NTRIP problem began.

steve.m · August 2, 2021, 11:14am

If I remember correctly and if they haven’t changed it, since the Dev version is beyond the stable version, @Guleed will have to wait until a stable version (non-beta) of 27.0 comes out. Otherwise you are committed to the Dev version unless you flash the unit.

I do agree with @wizprod on the network issues. There was a Monday morning here in Indiana where my RS2 all of a sudden could not connect to the INCORS network. I checked their status site and it showed that everything was working. After talking to the network administrator, it turns out that they had updated the network over the weekend and even though the stations were working, no one could connect to them.

jp-drain-sol · August 2, 2021, 12:10pm

I think if you turn off the Dev version option, it will make the last stable release availble.

Guleed · August 2, 2021, 10:18pm

As suggested by @jp-drain-sol, I turned off the dev version option, which allowed me to revert the firmware to the last stable release. This, however, did not solve the problem of the inability to connect the RS2 to CRTN base stations.

re: @steve.m I have now also flashed my RS2, which brought the device back to v26.4. But this step (like in the previous attempt) did not solve the problem.

I could not find any obvious contacts for the California Real Time Network. But I did find a link to the UNAVCO IT. They wrote on their twitter feed that they performed network maintenance on July 29. I’ve written to UNAVCO IT, and am awaiting their response to my inquiry on the operational status of their system. Perhaps the problem is similar to what @steve.m experienced with INCORS (I.e., connection to stations were not possible inspite of their working status).

jp-drain-sol · August 2, 2021, 10:56pm

You could download/install Snip, https://www.use-snip.com/, and use your username/password connect to CRTN to see if there is an issue with the server. Not a hard program to learn.

andrew.belov · August 3, 2021, 2:32pm

Hi @Guleed,

Welcome to the community forum!

The updating of your RS2 was the right thing to do.
I suggest you to drop off all NTRIP settings and delete the NTRIP profile in the ReachView 3 app. Sometimes after the update, these settings need reconfiguration.

Keep me posted about the progress.

Guleed · August 3, 2021, 7:18pm

Hi, @andrew.belov. Thanks for the welcome.

I took your suggestion. I deleted all of the the NTRIP profiles that were stored in my ReachView3 (presumably that is sufficient to “drop off all NTRIP settings”). Unfortunately, this did not fix the problem, too.

I’m still waiting on a response concerning this problem from one of UNAVCO’s engineers.

In the mean time, is it possible to test if the problem is isolated to the UNAVCO stations by attempting a connection to a stream from a base station outside of the that network?

vgo195 · August 4, 2021, 5:28pm

Try Lefebure NTRIP client (android app on playstore) and see if it receives data from the CORS.
On the receiver settings set "None (NTRIP Testing Mode)
On NTRIP settings set your caster ip etc
Then Connect to the mountpoint you wish and check if it receives data.

jdouglas · August 4, 2021, 5:40pm

I spoke with Guleed. This issue was on the service provider side. No issue on the RS2 side of things.
They sorted it out and he is up and running.

andrew.belov · August 6, 2021, 12:22pm

Hi @jdouglas,

Thanks for the update! Great that it’s possible to achieve Fix with the CRTN network.

I’ve double-checked this case. We have other users who also have faced difficulties with the CRTN network. The issue occurs only with corrections from it, though.

We’ve previously contacted CRTN support regarding this to no avail. So hopefully, now the issue will be resolved for good. Would it be possible to share the conclusion on what triggered the issue in the first place?

jdouglas · August 6, 2021, 12:56pm

"I’m just writing to you to inform you that I did find a solution with the folks at UNAVCO. They provided me with a username and password to access their streams directly, instead of the way I was previously receiving the data, which was through a third-party system (CRTN/SOPAC). Based on the reasoning they presented to me, the problem was being caused by the third party.

So all is well now."

Guleed

andrew.belov · August 6, 2021, 2:13pm

Joe,

Thanks for keeping us informed!