Loading ...
Sorry, an error occurred while loading the content.

RE: [tracker2] Re: Garmin "Database error" problem

Expand Messages
  • Scott Miller
    The duplicate waypoint thing is a Garmin issue. Someone complained to them about that for one device (in NMEA mode at least) and they fixed it, so you could
    Message 1 of 8 , Dec 15, 2006
    • 0 Attachment
      The duplicate waypoint thing is a Garmin issue.  Someone complained to them about that for one device (in NMEA mode at least) and they fixed it, so you could try asking them about it.  Unfortuntely I have no control over that, and no way to see if a waypoint already exists.
       
      As for the second part of that, do you want to avoid seeing yourself on the map?  I find it useful to know that I'm hitting a digi, but I could suppress it.
       
      Autodetecting Garmin mode would require switching to 9600 baud and sending a packet to get device info - the GPS receiver won't send anything on its own.  So far I've avoided anything that requires active probing because of the possibility of screwing up some attached device.  Maybe I could add an option to check for Garmin and La Crosse...
       
      Scott


      From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of va3ytr
      Sent: Monday, December 11, 2006 3:19 PM
      To: tracker2@yahoogroups.com
      Subject: [tracker2] Re: Garmin "Database error" problem

      1. Mycall duplicating on gps display
      As suggested, I tried Garmin mode today. The database error did not
      come up but everytime my position was digi'd, a new waypoint was
      created.

      Mycall is va3ytr-9 .... waypoints were created as:
      va3ytr-9
      va3ytr-9 1
      va3ytr-9 2
      va3ytr-9 3
      va3ytr-9 4 etc...

      What am I missing? Could this be a config problem?

      Is there a way to disable the display of my position packets echoed
      from the digipeater?

      2. ABaud. If I exit Garmin mode, why does the baud rate remain at
      9600 if abaud is set to 4800? Do I need to reset the unit to go back
      to 4800?

      3. Would it be possible for the OT2 to autodetect Garmin binary mode
      and switch amode to Garmin on its own?

      My config:

      Argent Data Systems Tracker2 Firmware Build
      54076
      Copyright (C) 2006 Argent Data
      Systems

      cmd:
      cmd:display
      1WIREWX OFF
      ABAUD 4800
      ALIAS 1:RELAY 2:WIDE 3:TEMP
      ALTITUDE OFF
      AMODE AUTO
      AUTHLIST
      AUTOBAUD ON
      AUTOSAVE OFF
      BBAUD 4800
      BMODE FLOW
      CDINVERT OFF
      CLIMB OFF
      CNTRESET OFF
      COMMENT testing OpenTracker2
      prototype
      COMPRESS OFF
      COUNTER OFF
      CUSTSYM ON
      DIGI ON
      DIGIID 1:ON 2:ON 3:ON 4:ON 5:ON 6:ON 7:ON
      8:ON
      DUPETIME 30
      FAHRENHT OFF
      GPSDATA OFF
      HBAUD 1200
      HEADERLN OFF
      HOPLIMIT 1:0 2:1 3:5 4:0 5:0 6:0 7:0
      8:0
      INTERVAL 20
      LVINHIBIT 0
      MAXRANGE 0
      MONITOR ON
      MYCALL VA3YTR-9
      NICE 0
      OUTPUT1 OFF
      POSITION GPS
      POWER ON
      PREEMPT 1:OFF 2:OFF 3:OFF 4:OFF 5:OFF 6:OFF 7:OFF
      8:OFF
      PTTINPUT OFF
      PATH WIDE1-1,WIDE2- 2
      QUIET 16
      REARM 250
      RETRIES 6
      RETRYTIME 7
      REQALL OFF
      RING OFF
      SHAREDPTT OFF
      SLOT 0
      SMARTBCON 7 83 900 28 5
      SWDCD ON
      STATUS 6
      SYMBOL /j
      TELEMETRY OFF
      TEMP OFF
      TEMPADJ 0
      TIMEHMS ON
      TIMESLOT OFF
      TIMESTAMP ON
      TXDELAY 30
      TXLEVEL 102
      TXNOFIX OFF
      TXONCHG OFF
      USEALIAS 1:OFF 2:ON 3:OFF 4:OFF 5:OFF 6:OFF 7:OFF 8:OFF
      VELOCITY ON
      VOLTAGE OFF
      WAYPOINTS ON
      WPTLEN 9

      --- In tracker2@yahoogroup s.com, "va3ytr" <marcarchambault@ ...> wrote:
      >
      > Scott,
      >
      > The following packets caused the Garmin database error on my Garmin
      > GPSMAP 60CX. I'm in NMEA mode, using the latest garmin and OT2
      firmware.
      >
      > Xastir log file data:
      >
      > # 1165622819 Fri Dec 08 19:06:59 EST 2006
      > VE3KHV-9>APT311, WIDE1*,WIDE2- 2:!4418.51N/ 07748.04W> 283/000/
      A=000528/
      > Port-a-Track va3krv@...
      > # 1165622820 Fri Dec 08 19:07:00 EST 2006
      > VE3KHV-9>APT311, WIDE1,VE3MHZ* ,WIDE2-1: !4418.51N/ 07748.04W> 283/000/
      A=000528/
      > Port-a-Track va3krv@...
      > # 1165622998 Fri Dec 08 19:09:58 EST 2006
      > VE3KHV-9>APT311, WIDE1*,WIDE2- 2:!4418.51N/ 07748.04W> 283/000/
      A=000501/
      > Port-a-Track va3krv@...
      > # 1165622999 Fri Dec 08 19:09:59 EST 2006
      > VE3KHV-9>APT311, WIDE1,VE3MHZ* ,WIDE2-1: !4418.51N/ 07748.04W> 283/000/
      A=000501/
      > Port-a-Track va3krv@...
      >
      > # 1165623284 Fri Dec 08 19:14:44 EST 2006
      > VE3UEL>APN382, VE3MHZ*,WIDE2- 1:!4425.60NS0763 8.33W#PHG3120/ W2 ONn
      > Kingston/Frontenac Area Digi
      > # 1165623285 Fri Dec 08 19:14:45 EST 2006
      > VE3UEL>APN382, VE3KHV*:! 4425.60NS07638. 33W#PHG3120/ W2 ONn
      > Kingston/Frontenac Area Digi
      >
      > For example, 2 waypoints were created with the following name:
      > VE3KHZ-9VE3KHV.
      >
      > I'll do some more monitoring and post my results.
      >
      >
      >
      >
      > --- In tracker2@yahoogroup s.com, <scott@> wrote:
      > >
      > > Can you send me the original packet that generated this waypoint?
      > Sounds
      > > like it might be invalid. In any case, I need to make sure the T2
      > either
      > > formats it right or drops it if it can't figure it out - you don't
      > want it
      > > beeping at you all the time.
      > >
      > > I ran a T2-135 board all day yesterday, tracking the balloon I
      > launched in
      > > the Mojave desert. Worked great, though the altitude display
      > stopped being
      > > correct on my GPSmap 60CS above around 65,000 feet. I need to see
      > if that's
      > > a problem in how the T2 is generating the waypoint, or if it's a
      > display bug
      > > in the 60CS. It did show up right at around 98,000 feet,
      though. Can't
      > > really blame Garmin if they never tested waypoint elevations more
      > than twice
      > > as high as Everest.
      > >
      > > Scott
      > >
      > >
      > > _____
      > >
      > > From: tracker2@yahoogroup s.com [mailto:tracker2@yahoogroup s.com]
      On
      > Behalf
      > > Of larsendr2002
      > > Sent: Sunday, November 12, 2006 5:47 PM
      > > To: tracker2@yahoogroup s.com
      > > Subject: [tracker2] Garmin "Database error" problem
      > >
      > >
      > >
      > > Scott-
      > >
      > > Received one of the new batch of Proto C boards and it went
      together
      > > fine. Every thing works as expected except for the "Database
      error"
      > > problem on NMEA $GPWPL string. I happened to get on waypoint
      through
      > > and by reading the NMEA protocal and comparing the strings
      produced. I
      > > believe this is the problem.
      > >
      > > $GPWPL,3856. 8[00],N,09244. 7[00],W,A0GFC3* 55
      > >
      > > Was produced by my Tracker2 Build 53939
      > >
      > > When I hand edit the string and send it to my Garmin 276c as below
      > > the waypoint is accepted. I also confirmed it on a Garmin Etrex
      Vista
      > >
      > > $GPWPL,3856. 800,N,09244. 700,W,A0GFC3* 55
      > >
      > > This is the packet produces by the Tracker2 that went through
      fine.
      > >
      > > $GPWPL,3901. 30,N,09412. 11,W,A0PXP7* 41
      > > $PMGNWPL,3901. 30,N,09412. 11,W,813, F,A0PXP7, ,am*32
      > >
      > > It seems that if the original packet has greater that 3 decimal
      > > resolution a correct packet is formed, if less the [00] is added
      and
      > > Garmin rejects the NMEA string
      > >
      > > I have also noted that with monitor on and waypoint on in the text
      > > terminal, many valid position packets do not produce a waypoint
      > > string. I will watch them for more information.
      > >
      > > Any way the square brackets seem to be a problem in Garmin GPS in
      the
      > > NMEA mode. Hope this helps
      > >
      > > Dave Larsen
      > > KV0S
      > >
      >

    • va3ytr
      ... to them ... it, so you ... Ok, can you tell me which waypoint command you use so that I can be very specific with the request? Thanks, Marc
      Message 2 of 8 , Dec 18, 2006
      • 0 Attachment
        --- In tracker2@yahoogroups.com, "Scott Miller" <scott@...> wrote:
        >
        > The duplicate waypoint thing is a Garmin issue. Someone complained
        to them
        > about that for one device (in NMEA mode at least) and they fixed
        it, so you
        > could try asking them about it.

        Ok, can you tell me which waypoint command you use so that I can be
        very specific with the request?


        Thanks, Marc
      • Scott Miller
        It depends on the unit. For a GPSmap 60CS, it should be D109, but that might depend on the software version. A utility like DNRGarmin will tell you what
        Message 3 of 8 , Dec 18, 2006
        • 0 Attachment
          It depends on the unit.  For a GPSmap 60CS, it should be D109, but that might depend on the software version.  A utility like DNRGarmin will tell you what packet type it uses.
           
          In NMEA mode it's $GPWPL, but you're only having the problem in Garmin mode, right?
           
          Scott


          From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of va3ytr
          Sent: Monday, December 18, 2006 7:17 AM
          To: tracker2@yahoogroups.com
          Subject: [tracker2] Re: Garmin "Database error" problem

          --- In tracker2@yahoogroup s.com, "Scott Miller" <scott@...> wrote:
          >
          > The duplicate waypoint thing is a Garmin issue. Someone complained
          to them
          > about that for one device (in NMEA mode at least) and they fixed
          it, so you
          > could try asking them about it.

          Ok, can you tell me which waypoint command you use so that I can be
          very specific with the request?

          Thanks, Marc

        Your message has been successfully submitted and would be delivered to recipients shortly.