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

New Failure to Record APRS Message on Map

Expand Messages
  • derek.elias@btinternet.com
    Spent a frustrating evening with APRS. I have a Kenwood TH D7 and am sending beacon data with a Yaesu FT1DR. I can happily send an APRS message to the Kenwood
    Message 1 of 11 , Feb 11, 2014
    • 0 Attachment
      Spent a frustrating evening with APRS. I have a Kenwood TH D7 and am sending beacon data with a Yaesu FT1DR. I can happily send an APRS message to the Kenwood and when the Kenwood is connected to the pc I see the Yaesu position recorded correctly.

      However when we send APRS from the balloon transmitter using a Radiometrix on 144.39mhz the APRS is recorded on the Kenwood correctly but when the Kenwood is connected to the pc (an Acer laptop running Vista)and using APRSIS it will not record the balloon position although it will record the Yaesu position.

      In simple terms the balloon can send APRS to the Kenwood directly but when the Kenwood is connected to the pc it wont respond on APRSIS altough the program is working ok because it will accept Yaesu messages.

      Can there be something missing from our balloon APRS that can be received directly but not passed on to APRSIS.

      In another direction I thought it might be the laptop so I switched to a Samsung running 8.1. Although I've had it working fine recently as earlier reported it just won't work now at all even with APRS from the Yaesu. I recorded a log which might be of interest. In fact I reloaded APRSIS afresh configured it shut it down switched on the Kenwood then fired up APRSIS but no luck. Any comments would be appreciated.

      WinMain:2014-02-12T00:54:17.873 Starting Port(Kenwood)
      Port(Kenwood):2014-02-12T00:54:17.873 CpReader Running on COM8:9600,N,8,1 (6 OpenCmds, 4 CloseCmds)
      Port(Kenwood):2014-02-12T00:54:17.874 Opening COM8:9600,N,8,1
      Port(Kenwood):2014-02-12T00:54:17.874 Opening COM8 with 4 Args
      Port(Kenwood):2014-02-12T00:54:17.911 Opened COM8:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 6 OpenCmds
      Port(Kenwood):2014-02-12T00:54:18.912 Missed Expected Response(cmd:) From Command(^M~)
      Port(Kenwood):2014-02-12T00:54:20.913 Missed Expected Response(cmd:) From Command(^M~)
      Port(Kenwood):2014-02-12T00:54:21.914 Missed Expected Response(cmd:) From Command(XFLOW OFF)
      Port(Kenwood):2014-02-12T00:54:22.915 Missed Expected Response(cmd:) From Command(FULLDUP OFF)
      Port(Kenwood):2014-02-12T00:54:23.915 Missed Expected Response(cmd:) From Command(KISS ON)
    • James Ewen
      Off the top, APRS messages will never be recorded on a map. An APRS message has no location information, and thus doesn t belong on a map. It is strictly a
      Message 2 of 11 , Feb 11, 2014
      • 0 Attachment
        Off the top, APRS messages will never be recorded on a map. An APRS
        message has no location information, and thus doesn't belong on a map.
        It is strictly a string of text meant for human eyes.

        APRS position reports on the other hand will end up on a map given the
        right circumstances.


        On Tue, Feb 11, 2014 at 5:56 PM, derek.elias@...
        <derek.elias@...> wrote:

        > Spent a frustrating evening with APRS. I have a Kenwood TH D7 and am
        > sending beacon data with a Yaesu FT1DR. I can happily send an APRS
        > message to the Kenwood and when the Kenwood is connected to the pc
        > I see the Yaesu position recorded correctly.

        Okay, clarify if the Kenwood is connected to the PC and the PC is
        running APRSISCE/32 when you say you see the Yaesu position correctly.

        If you can send an APRS packet from the Yaesu and have APRSISCE/32
        show you the appropriate message in the messaging dialog box, or
        position report on the map (depending upon what type of APRS packet
        you are sending as you are changing terms in mid sentence), then there
        is nothing to change on the Kenwood/APRSISCE/32 side of things. Keep
        it set up as such and look for other issues causing you strife. Don't
        bother reloading software or swapping computers, or moving to a new
        country... if you are decoding packet off air from one device with
        another, but unable to decode from a third device, it is best to look
        at the third device.


        > However when we send APRS from the balloon transmitter using a
        > Radiometrix on 144.39mhz the APRS is recorded on the Kenwood
        > correctly but when the Kenwood is connected to the pc (an Acer
        > laptop running Vista)and using APRSIS it will not record the balloon
        > position although it will record the Yaesu position.

        So, again at the risk of sounding like a broken record... can you post
        the log of the packets captured during this event? If you can't
        provide evidence of what is going on, we can't help determine what's
        going on.

        > Can there be something missing from our balloon APRS that can
        > be received directly but not passed on to APRSIS.

        Yes, it is quite possible, but you are not allowing us to help you
        determine if that is the case.


        > WinMain:2014-02-12T00:54:17.873 Starting Port(Kenwood)
        > Port(Kenwood):2014-02-12T00:54:17.873 CpReader Running on COM8:9600,N,8,1 (6 OpenCmds, 4 CloseCmds)
        > Port(Kenwood):2014-02-12T00:54:17.874 Opening COM8:9600,N,8,1
        > Port(Kenwood):2014-02-12T00:54:17.874 Opening COM8 with 4 Args
        > Port(Kenwood):2014-02-12T00:54:17.911 Opened COM8:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 6 OpenCmds
        > Port(Kenwood):2014-02-12T00:54:18.912 Missed Expected Response(cmd:) From Command(^M~)
        > Port(Kenwood):2014-02-12T00:54:20.913 Missed Expected Response(cmd:) From Command(^M~)
        > Port(Kenwood):2014-02-12T00:54:21.914 Missed Expected Response(cmd:) From Command(XFLOW OFF)
        > Port(Kenwood):2014-02-12T00:54:22.915 Missed Expected Response(cmd:) From Command(FULLDUP OFF)
        > Port(Kenwood):2014-02-12T00:54:23.915 Missed Expected Response(cmd:) From Command(KISS ON)

        So that's the program trying to open the port to the Kenwood, and
        getting no response.

        I assume at some point you got the unit working in KISS mode... if
        not, you wouldn't see the Yaesu positions as you describe above.

        Okay, now how about a log of the packets received?

        Show us the log with Yaesu packets successfully received, and then the
        ones from the Radiometrix unit, and finally followed up with a Yaesu
        packet again.

        If this all happens in the above sequence, we'll know that the port
        was working properly before and after your faulty packets.

        If the Radiometrix unit is working properly, we should see packets
        between the Yaesu packets, which may have something as simple as a
        formatting error. If we see nothing, there may be level issues or
        other issues happening. Physical level issues shouldn't be the case as
        you say the Kenwood copies the packets on it's own.

        So, show us the packet log, or continue beating your head against the
        wall. It sounds like you're really frustrated, and if you provide us
        with the means to help you, we might be able to save you a few dents
        in the wall.

        --
        James
        VE6SRV
      • Lynn W Deffenbaugh (Mr)
        ... Kenwood APRS radios don t stay in KISS mode. You must make sure the radio s internal TNC is in PACKET mode BEFORE starting APRSISCE/32 or enabling the
        Message 3 of 11 , Feb 11, 2014
        • 0 Attachment
          On 2/11/2014 7:56 PM, derek.elias@... wrote:
          > WinMain:2014-02-12T00:54:17.873 Starting Port(Kenwood)
          > Port(Kenwood):2014-02-12T00:54:17.873 CpReader Running on COM8:9600,N,8,1 (6 OpenCmds, 4 CloseCmds)
          > Port(Kenwood):2014-02-12T00:54:17.874 Opening COM8:9600,N,8,1
          > Port(Kenwood):2014-02-12T00:54:17.874 Opening COM8 with 4 Args
          > Port(Kenwood):2014-02-12T00:54:17.911 Opened COM8:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 6 OpenCmds
          > Port(Kenwood):2014-02-12T00:54:18.912 Missed Expected Response(cmd:) From Command(^M~)
          > Port(Kenwood):2014-02-12T00:54:20.913 Missed Expected Response(cmd:) From Command(^M~)
          > Port(Kenwood):2014-02-12T00:54:21.914 Missed Expected Response(cmd:) From Command(XFLOW OFF)
          > Port(Kenwood):2014-02-12T00:54:22.915 Missed Expected Response(cmd:) From Command(FULLDUP OFF)
          > Port(Kenwood):2014-02-12T00:54:23.915 Missed Expected Response(cmd:) From Command(KISS ON)
          >

          Kenwood APRS radios don't stay in KISS mode. You must make sure the
          radio's internal TNC is in PACKET mode BEFORE starting APRSISCE/32 or
          enabling the port. I'm assuming you have configured the port as a type
          of KISS which is the basic support for the internal Kenwood radio TNCs.

          The proper sequence to get a Kenwood APRS radio to work with a KISS port
          on APRSISCE is:

          1) Close APRSISCE/32 or disable the port

          2) Put the radio's TNC into PACKET mode

          3) Start APRSISCE/32 or enable the port

          If the radio loses power, you have to close APRSISCE/32 or disable the
          port and do the whole procedure again.

          Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
        • derek.elias@btinternet.com
          James Thanks for that. I ll get the packets to you as soon as I can. I need to get over to my son s place to this as he has all the kit there. Actually I was
          Message 4 of 11 , Feb 12, 2014
          • 0 Attachment
            James
            Thanks for that. I'll get the packets to you as soon as I can. I need to get over to
            my son's place to this as he has all the kit there. Actually I was only ever sending 
            position reports either from the Yaesu or the the balloon transmitter. 

            I did have a phone discussion with my son this afternoon about sending you the log report from
            the successful Yaesu beacon and the unsuccessful balloon beacon. He maintained that as the
            balloon beacon had not been recorded on APRSIS there we be nothing of value in the log. But 
            from what you say there will be so I'll go ahead and do it asap although for logistical reasons it 
            may take a day or so to get set up again.

            We certainly didn't change anything between the Yaesu and the balloon transmissions. Basically 
            we did a Yaesu to check all was well then immediately without touching anything sent a balloon position
            message which always failed. Although as I said when the Kenood was unhooked from the pc it happily
            recorded balloon reports.

            So thanks again and I'll be in touch soon.
            regards and 73 Derek
          • derek.elias@btinternet.com
            Lynn Thanks for your swift reply. I had been working on it last night till 1am when I sent the message. But this morning I traced the problem to a broken wire.
            Message 5 of 11 , Feb 12, 2014
            • 0 Attachment
              Lynn
              Thanks for your swift reply. I had been working on it last night till 1am when I sent the message.
              But this morning I traced the problem to a broken wire. Fixing that the Samsung laptop now happily 
              records position reports from may Yaesu.
              regards and 73
              Derek  
            • James Ewen
              ... By capturing the log and providing a copy, we can determine whether there s anything captured between the Yaesu transmissions. If there s nothing there but
              Message 6 of 11 , Feb 12, 2014
              • 0 Attachment
                On Wed, Feb 12, 2014 at 12:58 PM, <derek.elias@...> wrote:

                > I did have a phone discussion with my son this afternoon about sending you the log report from
                > the successful Yaesu beacon and the unsuccessful balloon beacon. He maintained that as the
                > balloon beacon had not been recorded on APRSIS there we be nothing of value in the log. But
                > from what you say there will be so I'll go ahead and do it asap although for logistical reasons it
                > may take a day or so to get set up again.

                By capturing the log and providing a copy, we can determine whether
                there's anything captured between the Yaesu transmissions.

                If there's nothing there but the Yaesu transmissions before and after,
                then you have a problem with the transmissions from the Radiometrix
                unit. You would need to look at deviation, power output, and all other
                things associated with putting out a proper signal.

                If there were packets recorded between the Yaesu transmissions, then
                we could look to see if the APRS packets were malformed in some
                manner.

                If you couldn't even get Yaesu packets recorded, then there are
                probably issues with getting the port and Kenwood configured.

                You don't provide a consistent chronological listing of testing
                conditions and results, so the process devised was designed to try and
                create a known test condition, and provide a set of result from which
                a possible set of suggested corrective actions could be produced.

                Things like broken wires in the cabling might be able to be pinpointed.

                Correcting issues like you are having requires detailed and careful
                analysis of the problem, input conditions, and output results. Hopping
                around from one point to another can lead to missing a specific
                failure point, and lead to much frustration and head banging.

                I do enough of that at work with people who won't follow a
                troubleshooting process... I get paid by the hour there, so if it
                takes 3 weeks to find a broken wire, someone is paying me for my time.

                Even at that, I'd like to correct customer problems faster than that.
                I fixed a customer problem after 10 minutes on site the other day,
                where two coworkers each blew a day for the previous two days trying
                to correct the problem. Knowing what to look for, and knowing how to
                find the issue saves much aggravation for everyone.


                --
                James
                VE6SRV
              • derek.elias@btinternet.com
                James Well I collected the logs. However the log from the Yaesu FT1DR to the Kenwood (connected to the pc) is fine. However we are concerned that the log from
                Message 7 of 11 , Feb 15, 2014
                • 0 Attachment
                  James
                  Well I collected the logs. However the log from the Yaesu FT1DR to the Kenwood (connected to the pc) is fine. However we are concerned that the log from the transmission from our balloon transmitter to the Kenwood won't be much use as nothing was registered as far as we know in APRSIS. These are the logs:

                  From the Yaesu which gave a position on APRSIS

                  WinMain:2014-02-13T21:04:05.684 Restore Saved Enable

                  WinMain:2014-02-13T21:04:13.152 Starting Port(Kat)

                  Port(Kat):2014-02-13T21:04:13.152 CpReader Running on COM5:9600,N,8,1 (6 OpenCmds, 4 CloseCmds)

                  Port(Kat):2014-02-13T21:04:13.152 Opening COM5:9600,N,8,1

                  Port(Kat):2014-02-13T21:04:13.152 Opening COM5 with 4 Args

                  Port(Kat):2014-02-13T21:04:13.183 COM5:Packet Length 64 Version 2

                  Port(Kat):2014-02-13T21:04:13.183 COM5:ServiceMask 0x1 Reserved1 0x0

                  Port(Kat):2014-02-13T21:04:13.183 COM5:MaxQueue Tx 0 Rx 0 Baud 268435456

                  Port(Kat):2014-02-13T21:04:13.183 COM5:Provider SubType 1 Capabilities 0xFF

                  Port(Kat):2014-02-13T21:04:13.183 COM5:Settable Params 127 Baud 0x1007FFFF Data 0xF StopParity 0x1F07

                  Port(Kat):2014-02-13T21:04:13.183 COM5:Current Queue Tx 0 Rx 4096

                  Port(Kat):2014-02-13T21:04:13.183 COM5:Provider Specifics 0x0 0x0

                  Port(Kat):2014-02-13T21:04:13.188 CpOpen:Port COM5 9600,N,8,1 !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense RTS_ENABLE

                  Port(Kat):2014-02-13T21:04:13.188 Opened COM5:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 6 OpenCmds

                  Port(Kat):2014-02-13T21:04:13.188 Command[3]:^M~

                  Port(Kat):2014-02-13T21:04:13.188 Output[1]:<0D>

                  Port(Kat):2014-02-13T21:04:13.210 CmdResp[6]:<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:04:13.210 Command[3]:^M~

                  Port(Kat):2014-02-13T21:04:13.210 Output[1]:<0D>

                  Port(Kat):2014-02-13T21:04:13.230 CmdResp[6]:<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:04:13.230 Command[9]:XFLOW OFF

                  Port(Kat):2014-02-13T21:04:13.230 Output[10]:XFLOW OFF<0D>

                  Port(Kat):2014-02-13T21:04:13.278 CmdResp[32]:XFLOW OFF<0D 0A>XFLOW    was ON<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:04:13.278 Command[11]:FULLDUP OFF

                  Port(Kat):2014-02-13T21:04:13.278 Output[12]:FULLDUP OFF<0D>

                  Port(Kat):2014-02-13T21:04:13.317 CmdResp[22]:FULLDUP OFF<0D 0A>?EH<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:04:13.317 Command[7]:KISS ON

                  Port(Kat):2014-02-13T21:04:13.317 Output[8]:KISS ON<0D>

                  Port(Kat):2014-02-13T21:04:13.364 CmdResp[31]:KISS ON<0D 0A>KISS     was OFF<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:04:13.364 Command[7]:RESTART

                  Port(Kat):2014-02-13T21:04:13.364 Output[8]:RESTART<0D>

                  Port(Kat):2014-02-13T21:04:13.708 KISS:Missing Leading C0[9]:RESTART<0D 0A>

                  Port(Kat):2014-02-13T21:04:48.213 KISS:M6CYT-10>UQRUPP,WIDE1-1,WIDE2-1:`v0l [/`_$  (36)


                  From Our Balloon Transmitter (We may have let the log run on too long)

                  WinMain:2014-02-13T21:06:32.316 Restore Saved Enable

                  WinMain:2014-02-13T21:06:40.483 Starting Port(Kat)

                  Port(Kat):2014-02-13T21:06:40.484 CpReader Running on COM5:9600,N,8,1 (6 OpenCmds, 4 CloseCmds)

                  Port(Kat):2014-02-13T21:06:40.484 Opening COM5:9600,N,8,1

                  Port(Kat):2014-02-13T21:06:40.484 Opening COM5 with 4 Args

                  Port(Kat):2014-02-13T21:06:40.516 COM5:Packet Length 64 Version 2

                  Port(Kat):2014-02-13T21:06:40.516 COM5:ServiceMask 0x1 Reserved1 0x0

                  Port(Kat):2014-02-13T21:06:40.516 COM5:MaxQueue Tx 0 Rx 0 Baud 268435456

                  Port(Kat):2014-02-13T21:06:40.516 COM5:Provider SubType 1 Capabilities 0xFF

                  Port(Kat):2014-02-13T21:06:40.516 COM5:Settable Params 127 Baud 0x1007FFFF Data 0xF StopParity 0x1F07

                  Port(Kat):2014-02-13T21:06:40.516 COM5:Current Queue Tx 0 Rx 4096

                  Port(Kat):2014-02-13T21:06:40.516 COM5:Provider Specifics 0x0 0x0

                  Port(Kat):2014-02-13T21:06:40.523 CpOpen:Port COM5 9600,N,8,1 !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense RTS_ENABLE

                  Port(Kat):2014-02-13T21:06:40.523 Opened COM5:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 6 OpenCmds

                  Port(Kat):2014-02-13T21:06:40.523 Command[3]:^M~

                  Port(Kat):2014-02-13T21:06:40.523 Output[1]:<0D>

                  Port(Kat):2014-02-13T21:06:40.544 CmdResp[6]:<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:06:40.544 Command[3]:^M~

                  Port(Kat):2014-02-13T21:06:40.544 Output[1]:<0D>

                  Port(Kat):2014-02-13T21:06:40.567 CmdResp[6]:<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:06:40.567 Command[9]:XFLOW OFF

                  Port(Kat):2014-02-13T21:06:40.567 Output[10]:XFLOW OFF<0D>

                  Port(Kat):2014-02-13T21:06:40.616 CmdResp[32]:XFLOW OFF<0D 0A>XFLOW    was ON<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:06:40.616 Command[11]:FULLDUP OFF

                  Port(Kat):2014-02-13T21:06:40.616 Output[12]:FULLDUP OFF<0D>

                  Port(Kat):2014-02-13T21:06:40.653 CmdResp[22]:FULLDUP OFF<0D 0A>?EH<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:06:40.653 Command[7]:KISS ON

                  Port(Kat):2014-02-13T21:06:40.653 Output[8]:KISS ON<0D>

                  Port(Kat):2014-02-13T21:06:40.701 CmdResp[31]:KISS ON<0D 0A>KISS     was OFF<0D 0A>cmd:

                  Port(Kat):2014-02-13T21:06:40.701 Command[7]:RESTART

                  Port(Kat):2014-02-13T21:06:40.701 Output[8]:RESTART<0D>

                  Port(Kat):2014-02-13T21:06:41.045 KISS:Missing Leading C0[9]:RESTART<0D 0A>


                  So there is no message from the balloon. We also sent the balloon message through the Kenwood

                  to a terminal emulator. Here is the record from the balloon transmission which failed to make APRSIS respond.


                  21:17:12$ fm M6CYT-10 to UQRUP-0 via WIDE1-1,WIDE2-1 UI PID=F0

                  `v0l [/`_$


                  Obviously there is some difference eg the UI PID=F0 which we don't understand.


                  We had been thinking that we were not dealing with the audio frequencies for the 1's and 0's properly. We originally set the 1's at 1200hz and the 0's on 2400 hz. Someone commented to us that the frequencies should not be harmonics so we changed the 2400hz to 2200hz. We also played about with the emphasis between the frequencies but still no joy. Of course there is a wide range of possibilities for changing the emphasis and we were really just shooting in the dark as we weren't getting any useful info via APRSIS that we understood. 


                  So there it stands at the moment. We have been using a programmable chip in our transmitter which has allowed us to be flexible. We are now wondering if we shouldn't just get an Arduino, stick the GPS shield on it and download the software. But this goes against the grain a bit of producing your own product.


                  Any ideas would be gratefully received. I'll send this to Lynn too who has made some helpful comments.

                  best regards and 73

                  Derek









                • Lynn W Deffenbaugh (Mr)
                  May I suggest that you take APRSISCE/32 out of the equation since you re developing your own AX.25 transmitter? Stick to a simple terminal emulator connected
                  Message 8 of 11 , Feb 15, 2014
                  • 0 Attachment
                    May I suggest that you take APRSISCE/32 out of the equation since you're developing your own AX.25 transmitter?  Stick to a simple terminal emulator connected to a trusted TNC in text mode and compare EXACTLY the packets that you receive, both those from other stations as well as those from your experimental transmitter.

                    Feel free to post such packets here and I'll see if I can assist in figuring out what's worng (or right) with them.

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


                    On 2/15/2014 2:12 PM, derek.elias@... wrote:
                    James
                    Well I collected the logs. However the log from the Yaesu FT1DR to the Kenwood (connected to the pc) is fine. However we are concerned that the log from the transmission from our balloon transmitter to the Kenwood won't be much use as nothing was registered as far as we know in APRSIS. These are the logs:

                    From the Yaesu which gave a position on APRSIS

                    WinMain:2014-02-13T21:04:05.684 Restore Saved Enable

                    WinMain:2014-02-13T21:04:13.152 Starting Port(Kat)

                    Port(Kat):2014-02-13T21:04:13.152 CpReader Running on COM5:9600,N,8,1 (6 OpenCmds, 4 CloseCmds)

                    Port(Kat):2014-02-13T21:04:13.152 Opening COM5:9600,N,8,1

                    Port(Kat):2014-02-13T21:04:13.152 Opening COM5 with 4 Args

                    Port(Kat):2014-02-13T21:04:13.183 COM5:Packet Length 64 Version 2

                    Port(Kat):2014-02-13T21:04:13.183 COM5:ServiceMask 0x1 Reserved1 0x0

                    Port(Kat):2014-02-13T21:04:13.183 COM5:MaxQueue Tx 0 Rx 0 Baud 268435456

                    Port(Kat):2014-02-13T21:04:13.183 COM5:Provider SubType 1 Capabilities 0xFF

                    Port(Kat):2014-02-13T21:04:13.183 COM5:Settable Params 127 Baud 0x1007FFFF Data 0xF StopParity 0x1F07

                    Port(Kat):2014-02-13T21:04:13.183 COM5:Current Queue Tx 0 Rx 4096

                    Port(Kat):2014-02-13T21:04:13.183 COM5:Provider Specifics 0x0 0x0

                    Port(Kat):2014-02-13T21:04:13.188 CpOpen:Port COM5 9600,N,8,1 !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense RTS_ENABLE

                    Port(Kat):2014-02-13T21:04:13.188 Opened COM5:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 6 OpenCmds

                    Port(Kat):2014-02-13T21:04:13.188 Command[3]:^M~

                    Port(Kat):2014-02-13T21:04:13.188 Output[1]:<0D>

                    Port(Kat):2014-02-13T21:04:13.210 CmdResp[6]:<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:04:13.210 Command[3]:^M~

                    Port(Kat):2014-02-13T21:04:13.210 Output[1]:<0D>

                    Port(Kat):2014-02-13T21:04:13.230 CmdResp[6]:<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:04:13.230 Command[9]:XFLOW OFF

                    Port(Kat):2014-02-13T21:04:13.230 Output[10]:XFLOW OFF<0D>

                    Port(Kat):2014-02-13T21:04:13.278 CmdResp[32]:XFLOW OFF<0D 0A>XFLOW    was ON<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:04:13.278 Command[11]:FULLDUP OFF

                    Port(Kat):2014-02-13T21:04:13.278 Output[12]:FULLDUP OFF<0D>

                    Port(Kat):2014-02-13T21:04:13.317 CmdResp[22]:FULLDUP OFF<0D 0A>?EH<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:04:13.317 Command[7]:KISS ON

                    Port(Kat):2014-02-13T21:04:13.317 Output[8]:KISS ON<0D>

                    Port(Kat):2014-02-13T21:04:13.364 CmdResp[31]:KISS ON<0D 0A>KISS     was OFF<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:04:13.364 Command[7]:RESTART

                    Port(Kat):2014-02-13T21:04:13.364 Output[8]:RESTART<0D>

                    Port(Kat):2014-02-13T21:04:13.708 KISS:Missing Leading C0[9]:RESTART<0D 0A>

                    Port(Kat):2014-02-13T21:04:48.213 KISS:M6CYT-10>UQRUPP,WIDE1-1,WIDE2-1:`v0l [/`_$  (36)


                    From Our Balloon Transmitter (We may have let the log run on too long)

                    WinMain:2014-02-13T21:06:32.316 Restore Saved Enable

                    WinMain:2014-02-13T21:06:40.483 Starting Port(Kat)

                    Port(Kat):2014-02-13T21:06:40.484 CpReader Running on COM5:9600,N,8,1 (6 OpenCmds, 4 CloseCmds)

                    Port(Kat):2014-02-13T21:06:40.484 Opening COM5:9600,N,8,1

                    Port(Kat):2014-02-13T21:06:40.484 Opening COM5 with 4 Args

                    Port(Kat):2014-02-13T21:06:40.516 COM5:Packet Length 64 Version 2

                    Port(Kat):2014-02-13T21:06:40.516 COM5:ServiceMask 0x1 Reserved1 0x0

                    Port(Kat):2014-02-13T21:06:40.516 COM5:MaxQueue Tx 0 Rx 0 Baud 268435456

                    Port(Kat):2014-02-13T21:06:40.516 COM5:Provider SubType 1 Capabilities 0xFF

                    Port(Kat):2014-02-13T21:06:40.516 COM5:Settable Params 127 Baud 0x1007FFFF Data 0xF StopParity 0x1F07

                    Port(Kat):2014-02-13T21:06:40.516 COM5:Current Queue Tx 0 Rx 4096

                    Port(Kat):2014-02-13T21:06:40.516 COM5:Provider Specifics 0x0 0x0

                    Port(Kat):2014-02-13T21:06:40.523 CpOpen:Port COM5 9600,N,8,1 !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense RTS_ENABLE

                    Port(Kat):2014-02-13T21:06:40.523 Opened COM5:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 6 OpenCmds

                    Port(Kat):2014-02-13T21:06:40.523 Command[3]:^M~

                    Port(Kat):2014-02-13T21:06:40.523 Output[1]:<0D>

                    Port(Kat):2014-02-13T21:06:40.544 CmdResp[6]:<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:06:40.544 Command[3]:^M~

                    Port(Kat):2014-02-13T21:06:40.544 Output[1]:<0D>

                    Port(Kat):2014-02-13T21:06:40.567 CmdResp[6]:<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:06:40.567 Command[9]:XFLOW OFF

                    Port(Kat):2014-02-13T21:06:40.567 Output[10]:XFLOW OFF<0D>

                    Port(Kat):2014-02-13T21:06:40.616 CmdResp[32]:XFLOW OFF<0D 0A>XFLOW    was ON<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:06:40.616 Command[11]:FULLDUP OFF

                    Port(Kat):2014-02-13T21:06:40.616 Output[12]:FULLDUP OFF<0D>

                    Port(Kat):2014-02-13T21:06:40.653 CmdResp[22]:FULLDUP OFF<0D 0A>?EH<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:06:40.653 Command[7]:KISS ON

                    Port(Kat):2014-02-13T21:06:40.653 Output[8]:KISS ON<0D>

                    Port(Kat):2014-02-13T21:06:40.701 CmdResp[31]:KISS ON<0D 0A>KISS     was OFF<0D 0A>cmd:

                    Port(Kat):2014-02-13T21:06:40.701 Command[7]:RESTART

                    Port(Kat):2014-02-13T21:06:40.701 Output[8]:RESTART<0D>

                    Port(Kat):2014-02-13T21:06:41.045 KISS:Missing Leading C0[9]:RESTART<0D 0A>


                    So there is no message from the balloon. We also sent the balloon message through the Kenwood

                    to a terminal emulator. Here is the record from the balloon transmission which failed to make APRSIS respond.


                    21:17:12$ fm M6CYT-10 to UQRUP-0 via WIDE1-1,WIDE2-1 UI PID=F0

                    `v0l [/`_$


                    Obviously there is some difference eg the UI PID=F0 which we don't understand.


                    We had been thinking that we were not dealing with the audio frequencies for the 1's and 0's properly. We originally set the 1's at 1200hz and the 0's on 2400 hz. Someone commented to us that the frequencies should not be harmonics so we changed the 2400hz to 2200hz. We also played about with the emphasis between the frequencies but still no joy. Of course there is a wide range of possibilities for changing the emphasis and we were really just shooting in the dark as we weren't getting any useful info via APRSIS that we understood. 


                    So there it stands at the moment. We have been using a programmable chip in our transmitter which has allowed us to be flexible. We are now wondering if we shouldn't just get an Arduino, stick the GPS shield on it and download the software. But this goes against the grain a bit of producing your own product.


                    Any ideas would be gratefully received. I'll send this to Lynn too who has made some helpful comments.

                    best regards and 73

                    Derek










                  • Lynn W Deffenbaugh (Mr)
                    And based on the logs below, it appears that you re running both the FT1DR and your balloon transmitter as M6CYT-10. If you make them different, it would be
                    Message 9 of 11 , Feb 15, 2014
                    • 0 Attachment
                      And based on the logs below, it appears that you're running both the FT1DR and your balloon transmitter as M6CYT-10.  If you make them different, it would be easier to tell the packets apart.

                      And PID F0 is the APRS PID over AX.25, so rest easy on that one!  If you received a packet from the FT1DR while in the terminal emulator, you would hopefully see the same thing.

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

                      On 2/15/2014 2:12 PM, derek.elias@... wrote:
                      From the Yaesu which gave a position on APRSIS
                      Port(Kat):2014-02-13T21:04:48.213 KISS:M6CYT-10>UQRUPP,WIDE1-1,WIDE2-1:`v0l [/`_$  (36)


                      From Our Balloon Transmitter (We may have let the log run on too long)


                      So there is no message from the balloon. We also sent the balloon message through the Kenwood

                      to a terminal emulator. Here is the record from the balloon transmission which failed to make APRSIS respond.


                      21:17:12$ fm M6CYT-10 to UQRUP-0 via WIDE1-1,WIDE2-1 UI PID=F0

                      `v0l [/`_$



                    • derek.elias@btinternet.com
                      Lynn Thanks for your comment. regards Derek
                      Message 10 of 11 , Feb 16, 2014
                      • 0 Attachment
                        Lynn
                        Thanks for your comment.
                        regards
                        Derek
                      • derek.elias@btinternet.com
                        Dear Lynn Thanks. As I mentioned to James, time is rushing on and we have to get everything ready for GPSL in June. We may just go the more trusted Arduino
                        Message 11 of 11 , Feb 16, 2014
                        • 0 Attachment
                          Dear Lynn
                          Thanks. As I mentioned to James, time is rushing on and we 
                          have to get everything ready for GPSL in June. We may just
                          go the more trusted Arduino route, tag on a GPS shield and 
                          use their firmware which presumably works. Building our own from
                          scratch is using time we don't have to spare.

                          Thanks again for your help.
                          regards
                          Derek
                        Your message has been successfully submitted and would be delivered to recipients shortly.