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

Nuvi 350 position "Glitch" on startup.

Expand Messages
  • Garrett Sloan
    Posted from somewhere just north of Antarctica if I m to believe APRS.FI, apparently I m now a amphibious water craft... I ve been trying to troubleshoot why I
    Message 1 of 2 , Jun 2, 2009
    • 0 Attachment
      Posted from somewhere just north of Antarctica if I'm to believe APRS.FI, apparently I'm now a amphibious water craft...

      I've been trying to troubleshoot why I haven't been showing up on APRS.FI for a couple of days, all my packets are there, but I'm flagged with a location changing too fast.
      After looking at the raw data and talking with Hessu, I found the reason:

      1. 2009-06-01 21:48:33 UTC: VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:!/3IBf1l_[. st12.0V 444.800MHz T103 Nuvi350 OFF - Parked [Location changes too fast (>500 km/h)]
      2. 2009-06-01 21:59:58 UTC: VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:!\lk{vNM{vk st13.8V 444.800MHz T103 Nuvi350 ON - Driving
      3. 2009-06-01 22:00:15 UTC: VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:!\lk{vNM{vk st13.7V 444.800MHz T103 Nuvi350 ON - Driving
      4. 2009-06-01 22:01:05 UTC: VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:/220118h\3I@Z1lrQk:NG13.8V 444.800MHz T103 Nuvi350 ON - Driving [Location changes too fast (>500 km/h)]
      5. 2009-06-01 22:01:20 UTC: VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:/220132h5330.84N\11323.64Wk092/002!W!13.7V 444.800MHz T103 Nuvi350 ON - Driving [Location changes too fast (>500 km/h)]
      6. 2009-06-01 22:01:27 UTC: VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:/220140h5330.85N\11323.62Wk020/016!W!13.8V 444.800MHz T103 Nuvi350 ON - Driving [Location changes too fast (>500 km/h)]

      Both profiles dont have "dont require GPS fix" selected, and both have save GPS position.
      Packet 1 is from profile 2 with a saved GPS position, proper.
      Packet 2 is when it switches to Profile 1, the nuvi is attempting to get a gps fix, but its reporting me at 60.0.0S by 0.0.0W...
      Packet 3 is the same bad location, still waiting on GPS fix
      Packet 4 is just after it gets a fix (I was changing to uncompressed to see where I was being reported)
      and packets 5 & 6 are also good.

      I'm now stuck every time the GPS powers up it reports me back in the middle of the south ocean and all my packets after that are "changes too fast." I've talked with Hessu about the algorythm and there might be a solution there in the long run as its a little glitch, but seeing as how I'm the one making the bad packets...

      Is the Nuvi reporting a valid fix and a invalid location to the OT2 and thats why its getting sent?
      Or, is the OT2 loosing its GPS save and reverting to some default until it gets a fix? (shouldn't having "don't require a GPS fix" unchecked stop this?)
      I've also verified that under profile switching the tx on changing profiles is not selected.
      (Yes I know my beacon rate is "very" high on my "on" profile, I was trying to see what's going on. thanks James ;)

      Any help Scott?

      Garrett
      VE6RKY
    • Scott Miller
      I know I encountered a problem with the GTRANS (which borrowed a lot of T2 code) where it d think it had a valid fix from the nuvi when it didn t. I ll check
      Message 2 of 2 , Jun 2, 2009
      • 0 Attachment
        I know I encountered a problem with the GTRANS (which borrowed a lot of
        T2 code) where it'd think it had a valid fix from the nuvi when it
        didn't. I'll check that out tomorrow.. I can't remember if it was a bug
        in my code, or something weird coming from the nuvi. Normally the nuvi
        will just report its last known location, so it's not generally noticeable.

        Scott

        Garrett Sloan wrote:
        >
        >
        >
        > Posted from somewhere just north of Antarctica if I'm to believe
        > APRS.FI, apparently I'm now a amphibious water craft...
        >
        > I've been trying to troubleshoot why I haven't been showing up on
        > APRS.FI for a couple of days, all my packets are there, but I'm flagged
        > with a location changing too fast.
        > After looking at the raw data and talking with Hessu, I found the reason:
        >
        > 1. 2009-06-01 21:48:33 UTC:
        > VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:!/3IBf1l_[. st12.0V
        > 444.800MHz T103 Nuvi350 OFF - Parked [Location changes too fast (>500 km/h)]
        > 2. 2009-06-01 21:59:58 UTC:
        > VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:!\lk{vNM{vk st13.8V
        > 444.800MHz T103 Nuvi350 ON - Driving
        > 3. 2009-06-01 22:00:15 UTC:
        > VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:!\lk{vNM{vk st13.7V
        > 444.800MHz T103 Nuvi350 ON - Driving
        > 4. 2009-06-01 22:01:05 UTC:
        > VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:/220118h\3I@Z1lrQk:NG13.8V
        > 444.800MHz T103 Nuvi350 ON - Driving [Location changes too fast (>500 km/h)]
        > 5. 2009-06-01 22:01:20 UTC:
        > VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:/220132h5330.84N\11323.64Wk092/002!W!13.7V
        > 444.800MHz T103 Nuvi350 ON - Driving [Location changes too fast (>500 km/h)]
        > 6. 2009-06-01 22:01:27 UTC:
        > VE6RKY-9>APOT21,WIDE1-1,WIDE2-1,qAR,VA6KRM-10:/220140h5330.85N\11323.62Wk020/016!W!13.8V
        > 444.800MHz T103 Nuvi350 ON - Driving [Location changes too fast (>500 km/h)]
        >
        > Both profiles dont have "dont require GPS fix" selected, and both have
        > save GPS position.
        > Packet 1 is from profile 2 with a saved GPS position, proper.
        > Packet 2 is when it switches to Profile 1, the nuvi is attempting to get
        > a gps fix, but its reporting me at 60.0.0S by 0.0.0W...
        > Packet 3 is the same bad location, still waiting on GPS fix
        > Packet 4 is just after it gets a fix (I was changing to uncompressed to
        > see where I was being reported)
        > and packets 5 & 6 are also good.
        >
        > I'm now stuck every time the GPS powers up it reports me back in the
        > middle of the south ocean and all my packets after that are "changes too
        > fast." I've talked with Hessu about the algorythm and there might be a
        > solution there in the long run as its a little glitch, but seeing as how
        > I'm the one making the bad packets...
        >
        > Is the Nuvi reporting a valid fix and a invalid location to the OT2 and
        > thats why its getting sent?
        > Or, is the OT2 loosing its GPS save and reverting to some default until
        > it gets a fix? (shouldn't having "don't require a GPS fix" unchecked
        > stop this?)
        > I've also verified that under profile switching the tx on changing
        > profiles is not selected.
        > (Yes I know my beacon rate is "very" high on my "on" profile, I was
        > trying to see what's going on. thanks James ;)
        >
        > Any help Scott?
        >
        > Garrett
        > VE6RKY
        >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.