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

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

Expand Messages
  • Adam Mahnke
    I ll probably do that at w2cxm-1 because thats a dedicated station. For home KC2ANT I ve got several ports set up for different radio/TNC combinations. I like
    Message 1 of 34 , Aug 3, 2012
    • 0 Attachment
      I'll probably do that at w2cxm-1 because thats a dedicated station.

      For home KC2ANT I've got several ports set up for different radio/TNC combinations.

      I like the idea of DXid when enabled.

      Adam
      KC2ANT

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

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

       

      Yes, thanks.

      You might want to consider renaming the RF port from "w2cwm-1" to something like 144390.0 or 144.800.0 or whatever frequency that port is actually listening on.  I'm considering adding  port-specific "DX-ID" field that will be required if you opt to transmit DX on a specific RF port, but that'll not happen until I get some other port-specific work done, and then only if I remember (or am reminded).

      I might even remind myself when I get around to implementing the port/packet-specific paths that have been hinted at for years in the disabled "B Path" and "T Path" buttons on the Configure Port dialog.  Right now, paths are global and singular via Configure / Beacon / Path, but I'm hoping to make them optionally port/packet specific.

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

      On 8/3/2012 10:22 AM, Adam Mahnke wrote:
      So this is what you're looking for to use as wiki fodder?

      Adam
      KC2ANT

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

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

      DX reports only go to the DX list as far as I know.  They're "special" packets and aren't really APRS stations so I doubt that they'd show up there.  I know they only go to the DX screen on my D700.

      And I'm still curious as to whether the D72 even has the support as I could not find it mentioned in the manual.

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

      PS.  Look for an update later today that brings in the whole enchilada of the new rolling DX accumulation window and Min Interval application.

      On 8/3/2012 10:00 AM, Adam Mahnke wrote:
      I have to do more playing with it, but I think the D710 is showing the DX reports on the screen, but not in the station list.

      Anyone else able to confirm that?

      Adam
      KC2ANT

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

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

      The DX cluster format is completely different than anything else in APRS (in fact, it's not even mentioned in aprs101.pdf - see postscripts).  The timestamp is just HHMMz and is positioned in the packet to show up on the radio display as shown in the D700 manual, specifically:

      vs

      and

      vs

      I know the row-split callsign looks strange, but that's an unfortunate side effect of the fact that only 01234569 and ABCDEFGHIJ show up on the D7 (and presumably D72) displays per http://www.aprs.org/TWP.html

      According to the D710 manual, DX reports will probably have the "nnn dg frm xxxxx nnkm" all on one line:

      and

      I eyeballed the D72 manual and searched it for "DX" but came up empty.  Does the D72 even support the reception and display of these packets?  I'll have to dig out a D7 manual sometime and see what it has to say (if anything) as well.

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

      PS.  The "D" datatype (first character at the start of the AX.25 payload) which would be :DX de ... is not even documented in aprs101.pdf, so there's very little to go on as to how these particular packets are formatted for transmission or how various radios parse and display them.  Does anyone know what an FTM-350 does with them?  If anything?

      PPS.  Now that I'm transmitting them, I'm realizing that they'll probably be treated as Status Reports by APRSISCE if received per the following provision from Chapter 19 of aprs101.pdf:

      All Other Packets

      Packets that do not meet any of the formats described in this document are
      assumed to be non-APRS beacons. Programs can decide to handle these, or
      ignore them, but they must be able to process them without ill effects.

      APRS programs may treat such packets as APRS Status Reports. This allows
      APRS to accept any UI packet addressed to the typical beacon address to be
      captured as a status message. Typical TNC ID packets fall into this category.
      Once a proper Status Report (with the APRS Data Type Identifier >) has
      been received from a station it will not be overwritten by other non-APRS
      packets from that station.

      Maybe I need to treat "DX de" packets as "special" in APRSISCE/32?  I'll have to update my KJ4ERJ-2/KJ4ERJ-4 instance to see what it does when it receives DX packets from KJ4ERJ-1.

      On 8/2/2012 9:42 AM, Adam Mahnke wrote:
      If you're using the same timestamp format as the QRU objects then you should be good to go. I've got W2CXM-1 updated and running, but won't see what it does to my radio until I get out of work at 1500. Will let you know (if i remember)
       
      Adam
      KC2ANT
       

      To: aprsisce@yahoogroups.com
      From: kj4erj@...
      Date: Thu, 2 Aug 2012 09:28:26 -0400
      Subject: Re: [aprsisce] DX reformatting (Dev: 2012/08/02 08:57)

      Oh yeah, the DXcluster trace log that forces itself visible every time it updates will quit doing that in the next Dev release.  Sorry 'bout that in the meantime, but at least you can tell when it sends a packet out!

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

      On 8/2/2012 9:06 AM, Lynn W Deffenbaugh (Mr) wrote:
      Reformat the DX report to provide HHMMz visible in the list (timestamps are important), add NNNNmi/km for visibility on D700 (and hopefully D710) details, use Port Name as "frequency" element and position for readability (http://www.aprs.org/TWP.html is wrong about FIELD-ONE's position on screen).

      Here's some (hopefully final) screen shots from my D700:





      Note that I renamed my RF Port as 144390.0 (edit the XML and change the <RFPort Name="xxxxx"> element).  The 79mi won't show up on D7/D72s according to Bob's Tiny Web Pages document, but then, he had the frequency element down one line on the D700 also.

      If anyone gets this going and can get screen caps from a D7, D72, and/or a D710, it would be good Wiki fodder.

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






    • Lynn W Deffenbaugh (Mr)
      ... http://dictionary.reference.com/browse/diatribe I didn t realize diatribe was quite that negative! I ll go with the ... Lynn (D) - KJ4ERJ - Author of
      Message 34 of 34 , Aug 3, 2012
      • 0 Attachment
        On 8/3/2012 3:32 PM, James Ewen wrote:
        On Fri, Aug 3, 2012 at 1:25 PM, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:
        
        
        See also one of the lower paragraphs in my diatribe response to James.
        
        I wouldn't consider that a diatribe response... just sharing ideas and
        implementation reasonings. We're not bitter nor forceful!

        http://dictionary.reference.com/browse/diatribe

        I didn't realize "diatribe" was quite that negative!  I'll go with the origin from:

        Origin:
        1575–85;  < Latin diatriba  < Greek diatribḗ  pastime, study, discourse, derivative of diatríbein  to rub away ( dia- dia-  + tríbein  to rub)

        Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
      Your message has been successfully submitted and would be delivered to recipients shortly.