LORD-MicroStrain/ntrip_client

Issues

• RTCM message not received

  #53 opened 3 months ago by ciniminis1
  0

• Feature request: publish the current connection state

  #52 opened 4 months ago by gennartan
  0

• Node dies if connection to caster fails

  #44 opened a year ago by tiesus
  1

• NTRIP Client Checksums do not match RTCM msgs from PointPerfect Ublox Service

  #49 opened 7 months ago by akrv
  0

• Invalid NMEA sentence, sentence should have a "*" character to separate the checksum, but we could not find it

  #47 opened 7 months ago by kosmonauta144
  1

• Troubles in setting the right parameters

  #43 opened a year ago by pieterblok
  0

• New ROS 2 release

  #42 opened a year ago by mrkbac
  0

• Issue of the Ntrip client

  #35 opened 2 years ago by yulan0215
  4

• UTF-8 codec can't decode byte

  #41 opened a year ago by martfrau
  0

• Checksum error when connecting to RTCM 3.3 caster

  #40 opened a year ago by dvismans
  0

• Reconnecting because we received 0 bytes from the socket even though it said there was data available 5 times

  #29 opened a year ago by Hadain
  20

• nmea message handling bug

  #36 opened 2 years ago by edvart-ros
  1

• ntrip_client.launch does not pass rtcm_msg_pkg through as an arg

  #31 opened 2 years ago by arpaterson
  1

• Max length is 82, but sentence was 83 bytes

  #12 opened 2 years ago by tomy983
  3

• ntrip_client should support ZED-F9P for applications other than mav-ros - i.e. support KumarRobotics driver

  #10 opened 2 years ago by PaulBouchier
  4

• `ntrip_client` does not attempt to reconnect to ntrip server if initially unsucceessful

  #11 opened 2 years ago by vinnnyr
  1

• the parsed RTCM packets are empty

  #14 opened 2 years ago by JeffYoung17
  0

• ROS2 Timer does not support shutdown and join

  #4 opened 3 years ago by PhilippPolterauer
  2