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

OT Re: [aprsisce] DX reformatting (Dev: 2012/08/02 08:57)

Expand Messages
  • Adam Mahnke
    Puzzle caches aren t even part of my pocket queries. HATE those things Adam KC2ANT ... From: Lynn W Deffenbaugh (Mr) Sent: 3 Aug 2012 18:08:24 GMT To:
    Message 1 of 1 , Aug 3, 2012
    • 0 Attachment
      Puzzle caches aren't even part of my pocket queries.

      HATE those things

      Adam
      KC2ANT

      -----Original Message-----

      From: Lynn W Deffenbaugh (Mr)
      Sent: 3 Aug 2012 18:08:24 GMT
      To: aprsisce@yahoogroups.com
      Subject: Re: [aprsisce] DX reformatting (Dev: 2012/08/02 08:57)

       

      On 8/3/2012 1:41 PM, James Ewen wrote:
      > For my purposes, these DX reports should be popping up to let me know
      > about anomalous propagation, whether that is enhanced ground
      > propagation, or a HAB flying off in the distance. These are local RF
      > activities that are out of the norm, that I'd like to get waved in my
      > face.

      Ok, now I believe we've gone well beyond simply reporting on a
      simple-to-determine DX and into some very non-APRS territory. It's hard
      enough to describe some configurations let alone having another
      "exclusion" list just for the purposes of determining if a given
      directly-received station counts as "DX" in someone's mind.

      I think it's time to stop turning this seemingly simple function of
      determining if stations are being heard at a greater than normal
      distance into something that only a hard-core propagation specialist
      with the time and inclination to monitor what is normal versus enhanced
      propagation.

      The distance limits are there, one to qualify and one to be worth an
      instant notification, either via Status Report or DX cluster packet.
      There's a Window for how long an older DX remains "king-of-the-hill",
      and a Min Interval to prevent frequent beacons from a Trigger-qualified
      DX from generating too many packets.

      I'm adding an easier visibility to the internal DX information (right
      click on the Port Status/APRS-IS OK pane and select from a popup) and
      then calling it done, at least for the near term.

      Your "simple" addition of a DX-cluster-formatted packet has already
      generated more worms than I had counted on, but then, the entire DX
      mechanism has gotten better as a result. As I said, I never really
      liked the clock hour window, so I took this opportunity to fix it and
      also added the Interval protection. Done.

      Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

      PS. And I still need to read Bob's notes about "gleaning for
      gridsquares", but they can be frighteningly similar to solving a puzzle
      geocache. (Almost) no matter what your solution, it'll give you a point
      that's somewhere on the planet. Been there, done that, and avoid puzzle
      caches ever since. But at least gridsquares are expected to be
      XXNNxxnnxxnnzzzzzzzz.......

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