Your message dated Sun, 13 Jan 2008 12:14:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line GSA sentences should be included since 2.36-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: gpsd
Version: 2.34.dfsg-6
Severity: normal

When the 'raw' output is translated NMEA data, such as from my Garmin
60CSx via a USB connection, gpsd does not produce any 'GSA' sentences in
the output.

The GSA sentence contains information somewhat similar to the 'q'
command, so this is hopefully not too difficult to achieve.

The GSA sentences are used extensively by gpsdrive to evaluate whether
the unit has a 3D or 2D fix.  I have also filed bug #456149 against
gpsdrive earlier in relation to this problem.

The GSA sentences themselves seem to provide useful information which is
not straightforwardly available in the other NMEA output, so it would be
useful to provide this if it is not too complicated.

In case it's usefule here's some of the NMEA output from gpsd, showing
the lack of GSA sentences:

m
GPSD,M=3
q
GPSD,Q=11 1.20 0.00 0.56 0.56 1.33
q
GPSD,Q=11 1.20 0.00 0.56 0.56 1.33
q
GPSD,Q=11 1.20 0.00 0.56 0.56 1.33
r
GPSD,R=1
$GPGSV,3,1,11,16,08,118,15,08,33,235,24,10,07,228,00,23,27,007,17*79
$GPGSV,3,2,11,19,57,067,22,03,45,116,16,28,11,290,38,11,02,019,32*71
$GPGSV,3,3,11,13,59,335,17,27,58,221,14,25,76,193,20*47
$GPGGA,063755,4106.5418,S,17452.2880,E,1,11,,90.8,M,16.836,M,,*44
$GPRMC,063755,A,4106.5418,S,17452.2880,E,0.5443,340.630,171207,,*38
$GPGSV,3,1,11,16,08,118,15,08,33,235,24,10,07,228,00,23,27,007,17*79
$GPGSV,3,2,11,19,57,067,22,03,45,116,16,28,11,290,38,11,02,019,33*70
$GPGSV,3,3,11,13,59,335,17,27,58,221,14,25,76,193,20*47
$GPGGA,063756,4106.5415,S,17452.2882,E,1,11,,90.5,M,16.836,M,,*45
$GPRMC,063756,A,4106.5415,S,17452.2882,E,1.0691,33.550,171207,,*0F
$GPGSV,3,1,11,16,08,118,15,08,33,235,24,10,07,228,00,23,27,007,18*76
$GPGSV,3,2,11,19,57,067,22,03,45,116,16,28,11,290,38,11,02,019,33*70
$GPGSV,3,3,11,13,59,335,17,27,58,221,14,25,76,193,20*47
$GPGGA,063757,4106.5411,S,17452.2881,E,1,11,,90.8,M,16.836,M,,*4E
$GPRMC,063757,A,4106.5411,S,17452.2881,E,0.7581,20.680,171207,,*01
$GPGSV,3,1,11,16,08,118,14,08,33,235,24,10,07,228,00,23,27,007,18*77
$GPGSV,3,2,11,19,57,067,22,03,45,116,16,28,11,290,38,11,02,019,33*70
$GPGSV,3,3,11,13,59,335,17,27,58,221,14,25,76,193,20*47
$GPGGA,063758,4106.5407,S,17452.2882,E,1,11,,90.9,M,16.836,M,,*44
$GPRMC,063758,A,4106.5407,S,17452.2882,E,0.9719,15.300,171207,,*0C
r
GPSD,R=0


Regards,
Andrew McMillan.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-rc5-hippy (SMP w/2 CPU cores)
Locale: LANG=en_NZ.UTF8, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages gpsd depends on:
ii  debconf [debconf-2.0]        1.5.17      Debian configuration management sy
ii  libc6                        2.7-4       GNU C Library: Shared libraries
ii  libdbus-1-3                  1.1.2-1     simple interprocess messaging syst
ii  libgps16                     2.34.dfsg-6 C library for communicating with G
ii  lsb-base                     3.1-24      Linux Standard Base 3.1 init scrip
ii  netbase                      4.30        Basic TCP/IP networking system
ii  python                       2.4.4-6     An interactive high-level object-o

Versions of packages gpsd recommends:
ii  gpsd-clients                 2.34.dfsg-6 Clients for the GPS daemon

-- debconf information excluded



--- End Message ---
--- Begin Message ---
Version: 2.36-1


Hi Andrew,

gpsd should print GSA messages since 2.36-1. Since 2.36-2, which was
uploaded a few seconds ago, the Garmin USB driver is supposed to work
again, too. Could you please test if both bugs are really fixed and - if
not - reopen them?

Thanks,

Bernd

-- 
Bernd Zeimetz
<[EMAIL PROTECTED]>                         <http://bzed.de/>


--- End Message ---

Reply via email to