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

RE: [aprsisce] APRIS32 Transmit stops Kenwood D710 from decoding packets.

Expand Messages
  • Adam Mahnke
    Tony, Lets start over again. Please reference http://aprsisce.wikidot.com/port:kenwood-tm-d710 as I go through my understanding of how APRSISCE32 interacts
    Message 1 of 4 , Dec 19, 2012
    Tony,

    Lets start over again.  Please reference http://aprsisce.wikidot.com/port:kenwood-tm-d710 as I go through my understanding of how APRSISCE32 interacts with a D710.

    for PHYSICAL ports on the D710 there are two, for communication with APRSISCE/32 you would be connected to the one on the back of the display panel(COM Port), which you said you have done. The one on the radio body is for memory programming (PC Port).


    In APRSISCE32 Configure->ports->New

    KWD710(APRS) automatically puts the D710 into it's Native APRS mode, and allows APRSISCE32 to receive and decode packets from the D710 and display them, as well as gate them to the IS stream if that is set up.

    KWD710(Pkt) Automatically puts the D710 into Packet mode, which puts APRSISCE32 in full control of the radio's TNC, as it would any other Radio/TNC combination.


    I was curious as to what mode the D710 TNC was in when you first launched the APRSISCE32 program, AND which of the above KWD710 choices you'd chosen when setting up the new port. Please refer to attached "New Port Screen.jpg"

    You'll see a caution on the above referenced wiki page that says it can be confusing using APRSISCE32 to control a D710 in APRS mode, and while I may be mistaken, I think that is the case with your set up, of course I may be wrong. (it does happen quite often, but that's how I learn)

    If you chose the KWD710(APRS) option, the D710 handles all APRS functions, APRSISCE32 is a very handy display tool, but it should not be used for controlling beacons through the radio (by hitting transmit) It can confuse the D710 TNC and cause issues.

    If you chose the KWD710(Pkt) then the D710 display will not decode and display any received packets, and ALL APRS function will be handled by APRSISCE32.

    The other possibility that I have in mind is that the com speed setting not being the same between APRSISCE32 and the D710, so the radio is receiving something, but then it can't read the rest of it so it has no idea what to do.
    Please refer to the attached "Port Configuration.jpg" and menu #528 under AUX and make sure that they are the same.


    There may be more going on here, but without knowing what your end goal of what your set up desires are, it's hard to help you get there. (for me anyway)


    Hopefully this makes more sense then my last attempt at a reply.

    Adam
    KC2ANT





    To: aprsisce@yahoogroups.com
    From: tony@...
    Date: Wed, 19 Dec 2012 11:23:15 -0700
    Subject: RE: [aprsisce] APRIS32 Transmit stops Kenwood D710 from decoding packets.

     
    At 05:08 AM 2012-12-19, Adam Mahnke wrote:


    Which of the 2 D710 ports are you using?

    The APRS one allows the D710 to stay in it's native APRS mode and still send packets to aprsisce/32 for display.

    The packet mode turns the D710 into a radio with TNC and the D710 won't decode anything.

    Which two parts are you talking about?    The physical ports one of which is in the radio body and used to program the memory channels and the other which is in the head and is the TNC?    If so I'm hooked up to the TNC port in the head. 

    Or do you mean there are two COM ports in Windws?   Which there aren't.

    Or do you mean something else?

    Can you share your radio settings at start,

    So you want me to go through every menu item on the D710 and write them down?

    your port configuration choices for aprsisce32, to include the kwdD710 port style you've chosen.

    9600 bps and 8N1 if that's what you mean.

    And then what is displayed on the radio face after transmit with aprsisce32

    Which if the 100 or so icons are you specifically interested in?

    Tony

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

    From: Tony VE6MVP
    Sent: 19 Dec 2012 07:43:37 GMT
    To: aprsisce@yahoogroups.com
    Subject: [aprsisce] APRIS32 Transmit stops Kenwood D710 from decoding packets.

     

    Folks

    When I click on Transmit in APRSIS32 I see the following in the port log.    Then the Kenwood  D710 TNC stops decoding packets on the D710 display until I do a power off/on cycle on the D710 radio.  Whereupon the D710 starts decoding packets and sending them to APRSIS32.

    Port(KwdD710):2012-12-19T07:21:39.590 Kenwood[85]:INSFRE>APOT30,ELKPNT,VERMLN,WIDE2*:!5322.58NS11131.71W#PHG3530\W2,AB7,Innisfree VA6BF
    Port(KwdD710):2012-12-19T07:21:41.836 Kenwood[79]:INSFRE>APOT30,LLOYD*,WIDE2-1:!5322.58NS11131.71W#PHG3530\W2,AB7,Innisfree VA6BF
    >>>>   I hit the transmit menu item.
    Port(KwdD710):2012-12-19T07:22:36.436 Command[4]:TC 0
    Port(KwdD710):2012-12-19T07:22:36.436 Output[5]:TC 0<0D>
    Port(KwdD710):2012-12-19T07:22:36.499 Command[3]:^M~
    Port(KwdD710):2012-12-19T07:22:36.499 Output[1]:<0D>
    Port(KwdD710):2012-12-19T07:22:37.513 Missed Expected Response(cmd:) From Command(^M~!cmd:!1)
    Port(KwdD710):2012-12-19T07:23:56.651 Kenwood[14]:KWXIMON  was 0
    >>>>> Several packets were received but not displayed on the D710 or received by APRSIS32
    >>>>> power cycle D710
    Port(KwdD710):2012-12-19T07:24:06.402 Kenwood[98]:VE6RHS>APWW10,CHPMAN,INSFRE,WIDE2*:/002400h5331.82N/11326.74W_031/000g000t-00r000p002P000h66b00000
    Port(KwdD710):2012-12-19T07:24:12.096 Kenwood[94]:BICHE>APOT21,ELKPNT,WIDE2*:!5446.95NS11213.12W#CNT00000 PHG4530/W2,  ABn,  Lac La Biche VE6SRV

    I have hit the Transmit button a number of times in the past few months and the local digis have happily sent back my beacon.    But not now.  This also happens when I go to send an APRS message which I've done lots of although not in the past few weeks.   Restarting APRSIS 32 does not help and there is a very similar if not identical message at the bottom of the port log.

    Any ideas what I might be doing wrong?

    Tony

  • Tony VE6MVP
    ... Right. And if you go back to the log I posed in my original email you will see some APRS packets which were received by APRSIS32. Which would not have
    Message 2 of 4 , Dec 19, 2012
    • 0 Attachment
      At 04:16 PM 2012-12-19, Adam Mahnke wrote:

      for PHYSICAL ports on the D710 there are two, for communication with APRSISCE/32 you would be connected to the one on the back of the display panel(COM Port), which you said you have done. The one on the radio body is for memory programming (PC Port).

      Right.  And if you go back to the log I posed in my original email you will see some APRS packets which were received by APRSIS32.  Which would not have been the case if the D710 port in use was the one on the body.    I have been running APRSIS just fine for several months.   This behavior is new and might've been caused by me changing some setting somewhere and not recalling exactly what it might've been.

      In APRSISCE32 Configure->ports->New

      KWD710(APRS) automatically puts the D710 into it's Native APRS mode, and allows APRSISCE32 to receive and decode packets from the D710 and display them, as well as gate them to the IS stream if that is set up.

      I just went to the port in APRSIS and it is indeed KWD710(APRS)   as well as 9600 8N1.

      I was curious as to what mode the D710 TNC was in when you first launched the APRSISCE32 program,

      I have no idea how you would tell what mode the TNC is using which of the 50 or 100 icons or so.  The only relevant one I know states APRS12.

      You'll see a caution on the above referenced wiki page that says it can be confusing using APRSISCE32 to control a D710 in APRS mode, and while I may be mistaken, I think that is the case with your set up, of course I may be wrong. (it does happen quite often, but that's how I learn)

      I didn't realize that web page existed.  I hooked up my D710 and it has been working just fine for a number of months.

      If you chose the KWD710(APRS) option, the D710 handles all APRS functions, APRSISCE32 is a very handy display tool, but it should not be used for controlling beacons through the radio (by hitting transmit) It can confuse the D710 TNC and cause issues.

      But you also need APRIS32 to be able to acknowledge messages.  Which it has been doing just fine for months so I would think I need that capability.

      Now one difference is that I do have Beacon checked whereas that page does not.   I'm pretty sure I've had Beacon checked for a long time but who knows.  I'll turn that off and see if it makes a difference.

      The other possibility that I have in mind is that the com speed setting not being the same between APRSISCE32 and the D710, so the radio is receiving something, but then it can't read the rest of it so it has no idea what to do.
      Please refer to the attached "Port Configuration.jpg" and menu #528 under AUX and make sure that they are the same.

      They were both set to 9600 bps.

      Tony
    • Adam Mahnke
      From: tony@ve6mvp.com Date: Thu, 20 Dec 2012 13:28:46 -0700 Subject: RE: [aprsisce] APRIS32 Transmit stops Kenwood D710 from decoding packets. But you also
      Message 3 of 4 , Dec 20, 2012
      • 0 Attachment
        From: tony@...
        Date: Thu, 20 Dec 2012 13:28:46 -0700
        Subject: RE: [aprsisce] APRIS32 Transmit stops Kenwood D710 from decoding packets.


        But you also need APRIS32 to be able to acknowledge messages.  Which it has been doing just fine for months so I would think I need that capability.

        KC2ANT>Honestly, I think it's a fluke that it's worked that way for as long as it has. It's not designed to work that way. 


        Yes, beaconing has been turned off for the last day.  The D710 has been happily receiving  packets, displaying them on the screen and APRSIS32 has been happily igating them.   However the RF beaconing from within APRSIS32 does not work as it has for several months.  

                KC2ANT> again, it's my understanding that it's not designed to work that way, and shouldn't be working as you described it. The messaging part will work, but the beaconing via RF is reported to cause issues and shouldn't work. 


        My goal is to get APRSIS32 working like it did several days ago and has been working for the past number of months.
        1) igating
        2) beaconing
        3) transmitting messages via RF

        I think that's the part you're not quite getting.  That is the D710 and APRIS32 have been successfully igating, beaconing and transmitting messages for the past number of months.  Suddenly, for no apparent reason, APRSIS32 is no longer beaconing and allowing me to transmit messages.   Which is why I posted the port log entries in my first posting so hopefully someone would recognize the problem.

        KC2ANT> I get it, I'm just saying it shouldn't have worked like that for as long as it did. Did you change the SSID of APRSISCE/32 recently? I'll freely admit I'm not the best at log message decoding, but APRSISCE/32 is telling the radio to do something, and the radio is not responding the way APRSISCE/32 is expecting it to. The messaging part is something I didn't see before, if it was mentioned. 


        Any transmission from within APRSIS32, be it a beacon, the Tramsmit menu item or sending a message causes the D710 to stop decoding packets.     Then I have to power cycle the D710 for it to start decoding packets.

        KC2ANT>Have you made any changes to the radio recently?

        Adam
        KC2ANT

      • Adam Mahnke
        I m not sure where in the port log the transmitting would be. and I didn t capture the transmit log while I was doing it. I ll be back out in about an hour to
        Message 4 of 4 , Dec 20, 2012
        • 0 Attachment
          I'm not sure where in the port log the transmitting would be. and I didn't capture the transmit log while I was doing it. I'll be back out in about an hour to pick up harmonics from sports, maybe I can capture it then.

          Adam
          KC2ANT


          To: aprsisce@yahoogroups.com
          From: tony@...
          Date: Thu, 20 Dec 2012 17:05:50 -0700
          Subject: RE: [aprsisce] APRIS32 Transmit stops Kenwood D710 from decoding packets.

           
          At 04:47 PM 2012-12-20, Adam Mahnke wrote:


          Port(D710 APRS):2012-12-20T23:31:50.482 Command[4]:TC 0
          Port(D710 APRS):2012-12-20T23:31:50.482 Output[5]:TC 0<0D>
          WinMain:2012-12-20T23:31:50.521 Waiting at line 2843
          Port(D710 APRS):2012-12-20T23:31:50.583 Command[2]:^M
          Port(D710 APRS):2012-12-20T23:31:50.583 Output[2]:<0D 0D>
          Port(D710 APRS):2012-12-20T23:31:50.609 CmdResp[8]:cmd:cmd:
          Port(D710 APRS):2012-12-20T23:31:50.609 Command[5]:LTM 0
          Port(D710 APRS):2012-12-20T23:31:50.609 Output[6]:LTM 0<0D>
          WinMain:2012-12-20T23:31:50.621 Waiting at line 2843

          And here is my log when I attempted to send an RF message.  So my TNC is not behaving as expected by Lynn.

          Port(KwdD710):2012-12-20T23:52:24.454 Kenwood[91]:ELKPNT>APOT21,LLOYD,WIDE2*:!5359.72NS11049.27W#CNT00000 PHG4530/W2,  ABn,  Elk Point VE6SRV
          Port(KwdD710):2012-12-20T23:52:34.402 Command[4]:TC 0
          Port(KwdD710):2012-12-20T23:52:34.402 Output[5]:TC 0<0D>
          Port(KwdD710):2012-12-20T23:52:34.465 Command[3]:^M~
          Port(KwdD710):2012-12-20T23:52:34.465 Output[1]:<0D>
          Port(KwdD710):2012-12-20T23:52:35.479 Missed Expected Response(cmd:) From Command(^M~!cmd:!1)

          Hmm, now this interesting.  I restarted APRSIS32 and it started processing the incoming packets.  In the past it just locked up.

          Now where in your log does it actually do the transmitting?  Or is that down a ways past the part you pasted?

          At this point I'm going to do a factory reset, or whatever it's called and reload my memory settings that I had from a month or two ago.  But that won't happen for an hour or two and maybe not today.

          Tony

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