Robotics StackExchange | Archived questions

gpsd_client: How to debug?

Hi,

I'm running ros gpsd client on melodic. I'm conected with an external gpsd via tcp. This gpsd uses an ublox hardware.

What I did:

Result: on /extended_fix message

header:
  seq: 565
  stamp:
    secs: 1614755865
    nsecs: 571623888
  frame_id: "gps"
status:
  header:
    seq: 0
    stamp:
      secs: 1614755865
      nsecs: 571623888
    frame_id: ''
  satellites_used: 0
  satellite_used_prn: []
  satellites_visible: 0
  satellite_visible_prn: []
  satellite_visible_z: []
  satellite_visible_azimuth: []
  satellite_visible_snr: []
  status: -1
  motion_source: 0
  orientation_source: 0
  position_source: 0
latitude: 0.0
longitude: 0.0
altitude: 0.0
track: 0.0
speed: 0.0
climb: 0.0
pitch: 0.0
roll: 0.0
dip: 0.0
time: 0.0
gdop: 0.0
pdop: 0.0
hdop: 0.0
vdop: 0.0
tdop: 0.0
err: 0.0
err_horz: 0.0
err_vert: 0.0
err_track: 0.0
err_speed: 0.0
err_climb: 0.0
err_time: 0.0
err_pitch: 0.0
err_roll: 0.0
err_dip: 0.0
position_covariance: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
position_covariance_type: 0

Additionally, I've checked the gps_client by means of a local gpsd, gpsfake and an artificial NMEA log. Here, I see meaningful ouput on the ros messages.

Do you have any advice how to find the cause of having no fix when connected to the external gpsd?

Thanks.

Asked by holunder on 2021-03-03 03:08:15 UTC

Comments

Answers