[aprssig] HF APRS igates on fldigi

Wed May 13 10:03:04 EDT 2020

Yes, because it would be insanely difficult to type a binary AX.25 header by hand. The packets aren't in ASCII TNC2 command-mode format, so no receiving station will understand them with the first 16+ bytes of the frame not compliant with the AX.25 protocol specification.

Andrew, KA2DDOauthor of YAAC

-------- Original message --------
From: Joe Della Barba <joe at dellabarba.com> 
Date: 5/13/20  07:34  (GMT-05:00) 
To: Joe Bennett <aprs at ka3nam.com> 
Cc: TAPR APRS Mailing List <aprssig at lists.tapr.org> 
Subject: Re: [aprssig] HF APRS igates on fldigi 

    That is what I sent. Apparently sending by hand does not work. 

    Joe N3HGB

    On 5/12/2020 11:46 PM, Joe Bennett
      wrote:

      Here is what I got. I never gated it. I'm guessing that its
        because it was not a KISS frame???? I'm not sure what FLDigi
        needs to see to forward it over the KISS interface. I'll have to
        work on setting up some sort of test bed so I can test it end to
        end.

      N3HGB-8>APU25N:=3859.15N/07617.12WlSVCoquina

      tR tbsy n_pO e

      -- Joe 

      KA3NAM

      May 12, 2020, 7:55 PM by joe at dellabarba.com:

        That looks like me - the callsign is getting mangled. I might
          be able to try again in about 30 minutes.

        73

        N3HGB

        On 5/12/2020 6:57 PM, Joe Bennett wrote:

          I received this on 60 meters. No callsign, but the
            lat/lon look to be for N3HGB:

          PU25N:=3859.15N/07617.12W 

          lTestFlDigi1700t;gi @r

          j tn>APU2gC15N/07617.12WlTestFlDigi

          t

          Before RSID: <<2020-05-12T22:50Z MFSK-16 @
            5403500+1693>>

          isainnew¿ obp
            t»8>APU25N:=3859.15N/07617.12WlTestFlDig4it=

          -- Joe 

          KA3NAM

          May 12, 2020, 10:11 AM by joe at dellabarba.com:

            I think that was me.I am going to try again today if I
              can. I was centered on 1700 Hz. I could see the data going
              out, it sends the RSID, a gap, and then the text. Maybe I
              need more power, I was sending at about 20 watts. :)

            73 Joe N3HGB

            On 5/11/2020 3:03 PM, Stephen H. Smith wrote:

              On 5/11/2020 10:45 AM, Joe Della Barba wrote:

                I was sending on 60 and 30 meters earlier this
                  morning as N3HGB-8. Nothing showed up on APRS.FI darn
                  the luck!

                Joe N3HGB

                _______________________________________________

                aprssig mailing list

                aprssig at lists.tapr.org

                http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org

              Around 09:01 EDT (1301 UTC), I copied these RSID
                transmissions without any following traffic.  Do these
                look like the times you tried?

                Before RSID: <<2020-05-11T13:01Z MFSK-16 @
                5403500+1700>>

                Before RSID: <<2020-05-11T13:08Z MFSK-16 @
                5403500+1700>>

                Before RSID: <<2020-05-11T13:08Z MFSK-16 @
                5403500+1700>>

                Before RSID: <<2020-05-11T13:09Z MFSK-16 @
                5403500+1700>>

                Before RSID: <<2020-05-11T13:13Z MFSK-16 @
                5403500+1700

              What kind of transceiver were you using?

              What exact "dial frequency were you on?

              Were you on USB?  (Most ham transceivers try to
                default to LSB below 10 MHz, and must be overridden to
                USB.)

              Was the center frequency of the cursor in the FLdigi
                waterfall exactly on 1700 Hz?

              Did you see your transmitted string appear in the
                upper (buff-colored) window of FLdigi?

              Were you trying to send from a KISS-linked APRS
                application, or did you just hand-enter a string
                directly into FLdigi?

              The RSID mode ID sent before the actual transmission
                is very reliable and will often be decoded even when the
                actual transmission on MFSK16, PSK63, etc fails to
                decode.  This could happen if the radio frequency of the
                radio, or the audio tones in FLdigi are off.

              ___________________________________________________________

              Stephen H. Smith    wa8lmf (at) aol.com

              Skype:        WA8LMF

              EchoLink:  Node #  14400  [Think bottom of the
                2-meter band]

              Home Page:          http://wa8lmf.net

              -----   NEW!    60-Meter APRS!   HF NVIS APRS Igate
                Now Operating ------

                 <http://wa8lmf.ddns.net:14447/>

              Live Off-The-Air APRS Activity Maps

                 <http://wa8lmf.net/map>

              Long-Range APRS on 30 Meters HF

                 <http://wa8lmf.net/aprs/HF_APRS_Notes.htm>

              You MUST be within 20-30 Hz of the correct frequency
                for a successful decode to happen. This includes the
                total of any error in both the RF frequency and the
                audio frequency in FLdigi.

            _______________________________________________

            aprssig mailing list

            aprssig at lists.tapr.org

            http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20200513/a6ed2095/attachment-0001.html>