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

Re: [aprsisce] DX reports (Dev: 2012/08/01 23:47)

Expand Messages
  • Lynn W Deffenbaugh (Mr)
    ... If you check Configure / Status / Status Report s DX box, then the UI-View style DX information in the status report packet will be transmitted. If you
    Message 1 of 3 , Aug 2, 2012
      On 8/2/2012 12:29 AM, James Ewen wrote:
      > On Wed, Aug 1, 2012 at 9:49 PM, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:
      >
      >> Support DX packet option on RF port configuration. If enabled, then
      >> when a direct packet is received further than Configure / DX / Min
      >> Trigger, a DX cluster packet will be transmitted with a path of RFONLY.
      >> These packets are NOT supported on APRS-IS ports, but the RF path can be
      >> modified as <DXPath> in the XML configuration file. (James VE6SRV)
      > Does this mean you don't send the older modified UI-View style any
      > longer? Can you enable the old style versus the DX Cluster style?
      >
      > I have enabled the DX reporting, and will have to wait to see what pops up...

      If you check Configure / Status / Status Report's DX box, then the
      UI-View style DX information in the status report packet will be
      transmitted. If you check Configure / Ports / <YourRFPort>'s DX box,
      then the DX cluster format packet will be sent on that RF port.

      Configure / DX / Min Trigger governs the immediate generation of either
      type of packet when a new DX is directly received. Configure / DX / Min
      Dist governs the remembering of DXs (likely less than Min Trigger) so
      that the next Status Report (if enabled) or ?DX query can use that
      information.

      Currently, DX information is cleared at the top of each hour and
      accumulation starts again. I'm working on a different (hopefully
      better) way of doing that to allow a user-specified DX interval with
      fallback DX distances when the furthest (see I can be educated) one
      expires. Of course, a fallback will not trigger an immediate
      transmission because it didn't just happen. Only a newly received max
      DX will transmit immediately.

      When the new fallback list is implemented, it will also be
      port-specific, and will likely display, in its full
      time/distance-descending glory, in the port visibility windows you get
      if you control-double-click the APRS-IS OK pane.

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

      PS. Wow, one would think I live on the east coast of somewhere? Or at
      least that there's not much APRS activity anywhere but West of me (note
      the dgs)? From the DXcluster trace log of my KJ4ERJ-1 IGate (which also
      illustrates the 1 hour reset described above):

      WinMain:2012-08-02T03:44:26.240 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS KG4YZY-11 279 dg frm KJ4ERJ-1 126mi
      WinMain:2012-08-02T04:00:01.747 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-15 271 dg frm KJ4ERJ-1 57mi
      WinMain:2012-08-02T04:08:27.890 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-14 286 dg frm KJ4ERJ-1 63mi
      WinMain:2012-08-02T04:34:43.866 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-11 257 dg frm KJ4ERJ-1 77mi
      WinMain:2012-08-02T05:00:01.476 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-15 271 dg frm KJ4ERJ-1 57mi
      WinMain:2012-08-02T05:08:29.685 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-14 286 dg frm KJ4ERJ-1 63mi
      WinMain:2012-08-02T05:14:44.783 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-11 257 dg frm KJ4ERJ-1 77mi
      WinMain:2012-08-02T06:00:01.526 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-15 271 dg frm KJ4ERJ-1 57mi
      WinMain:2012-08-02T06:08:28.791 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-14 286 dg frm KJ4ERJ-1 63mi
      WinMain:2012-08-02T06:14:43.936 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-11 257 dg frm KJ4ERJ-1 77mi
      WinMain:2012-08-02T06:39:26.907 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS KG4YZY-11 279 dg frm KJ4ERJ-1 126mi
      WinMain:2012-08-02T07:00:41.924 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-13 250 dg frm KJ4ERJ-1 43mi
      WinMain:2012-08-02T07:18:04.251 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-10 263 dg frm KJ4ERJ-1 71mi
      WinMain:2012-08-02T07:44:44.107 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-11 257 dg frm KJ4ERJ-1 77mi
      WinMain:2012-08-02T07:52:11.126 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS K4LKL-10 273 dg frm KJ4ERJ-1 79mi
      WinMain:2012-08-02T08:04:44.103 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-11 257 dg frm KJ4ERJ-1 77mi
      WinMain:2012-08-02T08:12:11.144 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS K4LKL-10 273 dg frm KJ4ERJ-1 79mi
      WinMain:2012-08-02T08:59:27.469 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS KG4YZY-11 279 dg frm KJ4ERJ-1 126mi
      WinMain:2012-08-02T09:00:41.782 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-13 250 dg frm KJ4ERJ-1 43mi
      WinMain:2012-08-02T09:10:04.691 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-15 271 dg frm KJ4ERJ-1 57mi
      WinMain:2012-08-02T09:15:07.603 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS KG4YZY-10 279 dg frm KJ4ERJ-1 126mi
      WinMain:2012-08-02T10:00:42.153 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-13 250 dg frm KJ4ERJ-1 43mi
      WinMain:2012-08-02T10:04:49.356 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS WC4PEM-11 257 dg frm KJ4ERJ-1 77mi
      WinMain:2012-08-02T10:12:13.597 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS K4LKL-10 273 dg frm KJ4ERJ-1 79mi
      WinMain:2012-08-02T10:35:18.838 KJ4ERJ-1>APWW10,RFONLY:DX de KJ4ERJ-1>APRS KG4YZY-10 279 dg frm KJ4ERJ-1 126mi
    Your message has been successfully submitted and would be delivered to recipients shortly.