NTRIP Connection stuck on "Waiting for corrections". Not sure why

mmiller · October 27, 2021, 8:29pm

Hello, Emlid Community!

I’m having trouble getting our RS2 unit (running Firmware 28.1) to receive corrections from an NTRIP connection. I can connect to the address, provide my login credentials, and select a mount point, but the app just displays “Waiting for corrections.”

This is the first time that I’ve tried connecting to an NTRIP server on these devices so perhaps I’ve missed a setting somewhere.

I’ve tried connecting through a mobile hotspot and through our office’s WiFi. I seem to have a connection because I can select a mount point, but I’m not receiving the correction stream.

Does anyone have any ideas where I might be off course?

I noticed that the mount points seem really far away but yet I have the “Send receiver’s position to the provider” activated.

I contacted the service provider and they show no record of this unit connecting to their system.

I’m very confused. Thank you for any suggestions.

I’ve added the system report below:

Simple system report

app version: 27.1-r0
current_network:
  ip: 192.168.1.151
  security: wpa-psk
  ssid: ZyXEL04
enabled: true
mode: client
base_mode:
  base_coordinates:
    accumulation: 120
    mode: single-and-hold
  output:
    io_type: 'off'
    settings:
      cloud:
        mount_point: ''
      lora:
        air_rate: 18.23
        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.1
    message_1008:
      enabled: false
      frequency: 0.1
    message_1012:
      enabled: false
      frequency: 1
    message_1033:
      enabled: false
      frequency: 0.1
    message_1074:
      enabled: true
      frequency: 1
    message_1084:
      enabled: true
      frequency: 1
    message_1094:
      enabled: true
      frequency: 1
    message_1124:
      enabled: true
      frequency: 1
    message_1230:
      enabled: false
      frequency: 0.1
bluetooth:
  enabled: true
  pairing:
    discoverable: true
    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: 18.23
        frequency: 902000
        output_power: 20
        send_position_to_base: false
      ntripcli:
        address: 168.44.251.90
        mount_point: South_RTCM_NAD83
        password: '***'
        port: 8888
        send_position_to_base: true
        username: 57amater01
      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
  rv3_banner_shown: false
  usage_analysis_accepted: true
logging:
  logs:
    base:
      autostart: false
      format: RTCM3
      started: true
    correction:
      autostart: false
      format: RTCM3
      started: true
    raw:
      autostart: false
      format: UBX
      rinex_options:
        logging_interval: 1
        marker_name: null
        pole_height: null
        satellite_systems:
          beidou: false
          galileo: false
          glonass: false
          gps: true
          qzss: false
          sbas: false
        time_adjustments_enabled: null
      started: true
    solution:
      autostart: false
      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: 'off'
    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: false
      galileo: true
      glonass: true
      gps: true
      qzss: true
    update_rate: 1
  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

jp-drain-sol · October 27, 2021, 11:36pm

Are all the mount points RTCM3? Try the one named MultiStation_RTCM3 and see what it does. If it connects, that is the issue. If not, double-check username/password.

If you want to test it, there is a way to use Lefebure NTRIP app to test your connection. Under Receiver Connection select None (NTRIP Testing Mode). It verifies that you are connecting with the caster with the proper UN/PW. You also have to setup NTRIP settings (caster/port etc.)

wizprod · October 28, 2021, 6:23am

Maybe the provider has a geofencing feature enabled, but yeah, the distance seems weird?
I think the solution is to be found with the provider, not with your GNSS unit.

mmiller · October 28, 2021, 4:52pm

Hello!
Thank you for the suggestions.

To my knowledge, all of the mount points are RTCM3, however, I also tried connecting to the Multi-Station_RTCM3 and have the same issue.

Thank you for the suggestion on the LeFebure app. I’d never heard of it. I loaded it onto my computer and ran it. I manually entered my position and tried to connect with my login credentials. It isn’t receiving data that way either.

I was on the phone with the NTRIP provider a good bit yesterday and they were able to connect just fine on their end using our login credentials.

So strange… I’ll keep at it.

Thank you!

jp-drain-sol · October 28, 2021, 5:49pm

I haven’t tried it with the PC version, just the Android version. I would assume it works the same.

From the screenshot, you have not selected your mountpoint. NTRIP Stream should show MultiStation_RTCM3 or whatever mountpoint you set it up for.

mmiller · October 28, 2021, 7:38pm

Yep. It indeed should show the mount points.

In my case, it never gives me the list to choose from. It just connects and doesn’t receive anything.

I’ve been communicating with the provider. Hopefully we’ll figure something out.

Thank you for checking back and following up on this… It’s a strange one, indeed.

elena.riazanova · October 29, 2021, 4:46pm

Hi Mason,

I see that you have already checked NTRIP credentials information. That’s good because we recently encountered a similar issue where the wrong name and password were the cause of such difficulties.

Let’s get to the point. It seems indeed a little strange. You and Christian noticed right that the baseline is quite long. Which NTRIP network do you use, and how far away is its station actually from you? Also, it’d be helpful to know which messages they send.

I also want to suggest you connect to another NTRIP network. For example, you can use the free RTK2GO network. This would help us to see if the receiver can connect to an NTRIP network in general.

jp-drain-sol · October 29, 2021, 6:55pm

Also, in the Lefebure NTRIP app, I think you can manually enter the mount point instead of selecting the download source table.

You will not be able to download the table as you are getting no response from the server at 11:36:31. That tells me something is wrong in your IP address or port setting. You get it multiple times there after. If it were correct, it would say connected, then if your username/password is correct it would download the table then you select the mount point and it would start transmitting data.

mmiller · November 2, 2021, 8:34pm

I’m sorry that this took a bit to get back to you.

It looks like all of this fuss boils down to my office network not working with the NTRIP network (for whatever reason… I don’t know).

I used a wifi hotspot and was able to connect with the same credentials within a few seconds.

I’m relieved that I was able to suss out the problem, but a little red-faced by how simple it actually was.

mmiller · November 2, 2021, 8:36pm

Thank you, everyone, for all of the thought and suggestions!

michaelL · November 3, 2021, 12:53am

They probably have the port disabled or it is just off by default in the firewall settings. Maybe they would be willing to open it up. Ours runs off of 2101 or 2102 and those are definitely not open by default.

jp-drain-sol · November 3, 2021, 10:03am

If it is your own home network, the port settings are normally in your router. Go in and enable them

michaelL · November 3, 2021, 10:50am

Even most modern modems and routers have firewall functionality but he said office network so I’m assuming they have a separate appliance.

jp-drain-sol · November 3, 2021, 11:18am

Ah, didn’t catch that. That comes down to talking with your IT department then having them add that port to their firewall.

Sorry, replied from my phone and it dropped the end of my statement

svetlana.nikolenko · November 3, 2021, 3:42pm

Hi Mason,

If you find out what’s wrong with the network settings, please share it! This is something new, and I’d like to know what it is.

mmiller · November 5, 2021, 7:15pm

Thank you, everyone…

I must admit that this definitely falls pretty low on my priority list since we aren’t likely to need to connect to the NTRIP network from our office very often (at all, really) any time soon. We’d only need to do that from the field. I will check with our IT folks, though. Maybe it’s a really quick fix.

Thank you very much, everyone!

mmiller · November 5, 2021, 7:15pm

I will do that. Thank you!

system · February 13, 2022, 7:15pm

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.