Re: [tracker2] Database error GPS
- What would really help is the waypoint output of the tracker. I'll see
if I can duplicate it based on the packets you provided.
Most often the problem is that the station name has a character (like a
decimal point) that the GPS doesn't like. That'll show up on the D700
too - but the T2 makes an attempt to filter it. Unfortunately there's
not a lot of consistency in what's allowed and what's not. The
filtering that exists now (mostly optimized for the Garmin mode) is
based on experimentation with about half a dozen different models, but
there are variations even between different firmware versions.
Magellans, on the other hand, are incredibly forgiving and don't really
require any filtering.
Tyson S. wrote:
> So it is not just the Tracker 2 that is doing it, it is something with
> the APRS system if D700's are doing it also?
> ----- Original Message ----
> From: James Ewen <ve6srv@...>
> To: email@example.com
> Sent: Friday, December 21, 2007 7:44:03 PM
> Subject: Re: [tracker2] Database error GPS
> On Dec 21, 2007 5:08 PM, Scott Miller <scott@opentrac. org
> <mailto:scott%40opentrac.org>> wrote:
> > That usually means there's some character coming through that the GPS
> > receiver doesn't like. Is it in Garmin mode or NMEA?
> I have tried to connect my database errors with a status packet being
> sent out by one of the local OT units. I have not seen the database
> error occur that can be conclusively attributed to a status packet
> from this unit.
> However, I was able to track down the source of at least some of my
> database errors.
> Let's backtrack a bit... I'm running a D700 into a Garmin GPS II+.
> I recently changed the local network to send repeater objects, and at
> around that time, database errors started showing up.
> EDMNTN>BEACON: ;444.80+SB* 111111z5332. 70N/11329. 65WrR50k VE6SBR
> PIGEON>BEACON: ;146.88-SS* 111111z5255. 83N/11351. 13WrR60k VE6SS
> Both of these repeater objects cause the Garmin to report a database
> error. I was led astray because these waypoints still appear in the
> database if you look at the waypoint list.
> I had a couple minutes this morning while sitting in the parking lot
> where both of these objects were observed to cause the database error.
> There may be other packets that cause database errors to be reported,
> but I can confirm that these two packets are creating database errors
> for me. Check your latest packets for repeater object packets when you
> notice a database error pop up.
> Never miss a thing. Make Yahoo your homepage.