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

Re: [aprsisce] Re: KPC3 configuration

Expand Messages
  • Lynn W Deffenbaugh (Mr)
    Read it carefully and completely. It says (just above the example ... Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 ... Read it
    Message 1 of 29 , Aug 30, 2013
    • 0 Attachment
      Read it carefully and completely.  It says (just above the example you're referencing):

      If you don't specify a Response (no !), "cmd:" is expected

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


      On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
      Is there something missing on this page?
       
      In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
       
      Best regards,
      Fred N7FMH



      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
      Sent: Thursday, August 29, 2013 21:31
      To: aprsisce@yahoogroups.com
      Subject: Re: [aprsisce] Re: KPC3 configuration

       

      From the log, it is not going into KISS mode.
      The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
        and it looks like I had a bad "cmd:" after the reset.

      Here is an EXACT copy of my port for my KPC-3:
      <!--RFPort[0]-->
      <RFPort Name="KPC3">
      <Protocol>KISS</Protocol>
      <Device>COM1:9600,N,8,1</Device>
      <RfBaud>1200</RfBaud>
      <OpenCmd>^M~!!0</OpenCmd>
      <OpenCmd>^C~!cmd:!2</OpenCmd>
      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
      <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
      <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
      <OpenCmd>INT KISS!!0</OpenCmd>
      <OpenCmd>RESET!!3</OpenCmd>
      <CloseCmd>^192^255^192~!!0</CloseCmd>
      <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
      <QuietTime>0</QuietTime>
      <Enabled>1</Enabled>
      <XmitEnabled>1</XmitEnabled>
      <ProvidesNMEA>0</ProvidesNMEA>
      <RFtoISEnabled>1</RFtoISEnabled>
      <IStoRFEnabled>1</IStoRFEnabled>
      <MyCallNot3rd>0</MyCallNot3rd>
      <BeaconingEnabled>1</BeaconingEnabled>
      <BeaconPath>WIDE2-1</BeaconPath>
      <BulletinObjectEnabled>1</BulletinObjectEnabled>
      <DXEnabled>1</DXEnabled>
      <DXPath>RFONLY</DXPath>
      <MessagesEnabled>1</MessagesEnabled>
      <MessagePath></MessagePath>
      <TelemetryEnabled>0</TelemetryEnabled>
      <TelemetryPath></TelemetryPath>
      <!--DigiXform-->
      </RFPort><!--RFPort[0]-->


      If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly.
      If you have an issue the first time, try
         >Enables >View Logs >Ports(KPC-3)
         >Enables > Port >KPC-3            to close the port
      then again
         >Enables > Port >KPC-3            to re-open the port

      Then check the log - post if needed
      Robert Giuliano
      KB8RCO


      ---------------------------------------------

      From: ke6gyd <ke6gyd@...>
      To: aprsisce@yahoogroups.com
      Sent: Thursday, August 29, 2013 8:01 PM
      Subject: [aprsisce] Re: KPC3 configuration
       
      Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something?

      <!--RFPort[0]-->
      <RFPort Name="KPC-3">
      <Protocol>KISS</Protocol>
      <Device>COM1:9600,N,8,1</Device>
      <RfBaud>1200</RfBaud>
      <OpenCmd>^M~1!!0</OpenCmd>
      <OpenCmd>^C~!cmd:!2</OpenCmd>
      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
      <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
      <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
      <OpenCmd>INT KISS!cmd:!1</OpenCmd>
      <OpenCmd>RESET!cmd:!3</OpenCmd>
      <CloseCmd>^192^255^192~!!0</CloseCmd>
      <CloseCmd>^C^C^C~!!0</CloseCmd>
      <CloseCmd>TC 1!TS 1</CloseCmd>
      <CloseCmd>TN 2,0!TN 2,0</CloseCmd>
      <QuietTime>0</QuietTime>
      <Enabled>0</Enabled>

      Log shows:
      Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0>

      Looks like it somehow is not in KISS mode?

      Any suggestions would be appreciated.
      Thanks
      Bob
      KE6GYD

      --- In aprsisce@yahoogroups.com, Rob Giuliano <kb8rco@...> wrote:
      >
      > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED.
      > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed.
      >    KEY-> the port is opened when APRSISce/32 requests use of it
      >              Application start-up if configured as OPEN on last close
      >             Also through the menu system:
      >               >Enables >Ports {your KPC3 port name}
      >
      >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup)
      > Mine is setup with:
      > <OpenCmd>^M~!!0</OpenCmd>
      > <OpenCmd>^C~!cmd:!2</OpenCmd>
      > <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
      > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
      > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
      > <OpenCmd>INT KISS!cmd:!1</OpenCmd>
      > <OpenCmd>RESET!cmd:!3</OpenCmd>
      >
      > <CloseCmd>^192^255^192~!!0</CloseCmd>
      > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd>
      >
      > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup.
      >
      > Give these a try and let us know
      >
      > Robert Giuliano
      > KB8RCO
      >
      >
      > ---------------------------------------------
      >
      >
      > ________________________________
      > From: ke6gyd <ke6gyd@...>
      > To: aprsisce@yahoogroups.com
      > Sent: Thursday, August 29, 2013 10:35 AM
      > Subject: [aprsisce] Re: KPC3 configuration
      >
      >  
      >
      > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet.
      >
      > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated.
      >
      > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this?
      >
      > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available.
      >
      > Thanks
      > Bob
      > KE6GYD
      >
      > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
      > >
      > > I TOTALLY disagree!
      > >
      > >
      > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you.
      > >
      > > Which you choose will determine what type of port
      > >    Continuous Mode - Simple KISS
      > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode.
      > >
      > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . .
      > >  
      > >
      > > Robert Giuliano
      > > KB8RCO
      > >
      > >
      > > ---------------------------------------------
      > >
      > > From: Adam Mahnke <kc2ant@>
      > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com>
      > > Sent: Tuesday, August 27, 2013 10:16 PM
      > > Subject: RE: [aprsisce] KPC3 configuration
      > >
      > >  
      > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset.
      > >
      > > http://aprsisce.wikidot.com/tnc-kpc-3
      > >
      > >
      > > Adam
      > > KC2ANT
      > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration 
      > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD
      > >
      >


    • Pat Ryan KC6VVT
      The apparent issue is the sole use of KISS mode for Kantronics model TNC within APRSIS32, and the difficulty it causes switching back to Terminal mode for use
      Message 2 of 29 , Aug 30, 2013
      • 0 Attachment
        The apparent issue is the sole use of KISS mode for Kantronics model TNC within APRSIS32, and the difficulty it causes switching back to Terminal mode for use by (shudder) other programs.

        While using APRSIS32, I have pretty much abandoned use of Kantronics TNC in favor of the built in TNC for Kenwood products, such as the TH-7/TH-72; TM-D700/710; and the TS-2000. These respond to a terminal mode setup with addressable parameters at the program setup, not any KISS mode.

        It seems to be that the terminal mode of APRSIS32 used with these built in Kenwood products could be extended to the Kantronics series TNC with adding a choice for selection of this terminal mode at the program start, and adapting switchable parameters in the HTML edit file in plain text settings sent to the TNC at startup.

        This would allow users to address terminal mode Kantronics TNC parameters in a set up file run at start up to account for the few differences in parameters under the AX25 protocol.

        The problem with Kantronics in using bulk parameter files with TNC commands, is that some TNC commands will reset the TNC! This will cause missed command lines during the TNC SOFT RESET!

        Therefore a scheme for Terminal Mode and a TNC Command Line editor may be also necessary to address the TNC Parameters directly, as may be done within a sub-routine of the APRS DOS program. This TNC fine tuning should be available to the knowledgeable users, with a separate sub-routine in an as yet unavailable Terminal Mde for APRSIS32!

        Refer to my recent comments about dual port TNC, and it becomes apparent that the solution may be available with just an adaptaion of the Kenwood TNC series of built in TNC terminal mode extended to the Kantronics TNC (in addition to KISS mode).

        For Lynn and other programmers, suggest that it might be a good idea in APRSIS32 setup, to RENAME Kenwood Setup as Terminal Mode, then add sub selection for RADIO BUILT IN TNC, includee choices between manufactures such as Yaesu and Kenwood and its related TNC files (e.g. VX-8(?), FTM-350 and KW TH-7,TH72, TM-D700, TM-D710, TS-2000 )

        Add another choice under Terminal modefor STANDALONE TNC (adding MFJ and Kantronics TNC parameter setups (fir KPC-3, KPC3+,9612, 9612+, Kam, Kam+, other AX-25)

        Again, just some thoughts for Lynn's consideration, leaving KISS mode as a separate choice for current users!

        73 de Pat KC6VVT


        --- In aprsisce@yahoogroups.com, "ke6gyd" <ke6gyd@...> wrote:
        >
        >
        > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet.
        >
        > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated.
        >
        > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this?
        >
        > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available.
        >
        > Thanks
        > Bob
        > KE6GYD
        >
        > --- In aprsisce@yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
        > >
        > > I TOTALLY disagree!
        > >
        > >
        > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you.
        > >
        > > Which you choose will determine what type of port
        > >    Continuous Mode - Simple KISS
        > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode.
        > >
        > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . .
        > >  
        > >
        > > Robert Giuliano
        > > KB8RCO
        > >
        > >
        > > ---------------------------------------------
        > >
        > > From: Adam Mahnke <kc2ant@>
        > > To: "aprsisce@yahoogroups.com" <aprsisce@yahoogroups.com>
        > > Sent: Tuesday, August 27, 2013 10:16 PM
        > > Subject: RE: [aprsisce] KPC3 configuration
        > >
        > >  
        > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset.
        > >
        > > http://aprsisce.wikidot.com/tnc-kpc-3
        > >
        > >
        > > Adam
        > > KC2ANT
        > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration 
        > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD
        > >
        >
      • Pat Ryan KC6VVT
        I add that in Bob s KB8RCO desire to make the Kantronics KPC-3 series TNC ready for terminal use by other packet programs, that adding an interface command
        Message 3 of 29 , Aug 30, 2013
        • 0 Attachment
          I add that in Bob's KB8RCO desire to make the Kantronics KPC-3 series TNC ready for terminal use by other packet programs, that adding an interface command line might be better at APRSIS32 exit, at the end of the triple ctrl C reset group.

          > > <CloseCmd>INT TERM

          and add any other TNC setup parameters thereafter, as long as the commands do not cause the TNC to automatically reset - see the Kantronics manual for those annotated commands!

          73 de Pat KC6VVT



          --- In aprsisce@yahoogroups.com, "Lynn W Deffenbaugh (Mr)" <kj4erj@...> wrote:
          >
          > You can also read about the KPC-3+ on the Wiki at:
          >
          > http://aprsisce.wikidot.com/tnc-kpc-3
          >
          > The commands may be different for the non-plus version, but the idea is
          > the same.
          >
          > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
          >
          > On 8/29/2013 12:49 PM, Rob Giuliano wrote:
          > >
          > >
          > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to
          > > the TNC when the port is OPENED or CLOSED.
          > > These commands can be used to tell the KPC-3 to enter KISS MODE when
          > > the port is opened, and to tell the KPC-3 to return to its standard
          > > mode when the port is closed.
          > > KEY-> the port is opened when APRSISce/32 requests use of it
          > > Application start-up if configured as OPEN on last close
          > > Also through the menu system:
          > > >Enables >Ports {your KPC3 port name}
          > > You have to edit the XML file in the directory where you APRSIS32.EXE
          > > file is (or linked to if you have a complex setup)
          > > Mine is setup with:
          > > <OpenCmd>^M~!!0</OpenCmd>
          > > <OpenCmd>^C~!cmd:!2</OpenCmd>
          > > <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
          > > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
          > > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
          > > <OpenCmd>INT KISS!cmd:!1</OpenCmd>
          > > <OpenCmd>RESET!cmd:!3</OpenCmd>
          > > <CloseCmd>^192^255^192~!!0</CloseCmd>
          > > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd>
          > > The open commands seem like a lot of "extras", but I had soime issues
          > > with FLOW and Duplex, so I explicitly set them in the setup.
          > > Give these a try and let us know
          > > Robert Giuliano
          > > KB8RCO
          > >
          > >
          > > ---------------------------------------------
          > >
          > > *From:* ke6gyd <ke6gyd@...>
          > > *To:* aprsisce@yahoogroups.com
          > > *Sent:* Thursday, August 29, 2013 10:35 AM
          > > *Subject:* [aprsisce] Re: KPC3 configuration
          > >
          > > I'm leaning toward on demand and would like the TNC to return to
          > > normal mode since I use the TNC mostly for EComm use of Packet.
          > >
          > > What I don't understand in the text below is how to set that up with
          > > my KPC-3 and 3+. I'm not familiar with the terminology stated.
          > >
          > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings
          > > or is that set in the TNC? Where can I find the menu's to accomplish this?
          > >
          > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS
          > > mode with APRSIS32, but I'd like the ability to use the KPC'3 if I
          > > don't have the TT4 available.
          > >
          > > Thanks
          > > Bob
          > > KE6GYD
          > >
          > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
          > > >
          > > > I TOTALLY disagree!
          > > >
          > > >
          > > > I agree that the best mode is KISS, but whether you CHOOSE to have
          > > it continuously in KISS mode (over resets) or CHOOSE to have
          > > APRSISce/32 put it in KISS mode on start and set it back to normal
          > > (converse) mode after shut down, is COMPLELY up to you.
          > > >
          > > > Which you choose will determine what type of port
          > > > Â Â Continuous Mode - Simple KISS
          > > > Â Â KISS on demand - set OPENCMD and CLOSECMD commands to ensure
          > > the TNC (KPC-3) is in the correct mode.
          > > >
          > > > I use the KPC-3, all the time (KB8RCO). Not the Plus . . .
          > > > Â
          > > >
          > > > Robert Giuliano
          > > > KB8RCO
          > > >
          > > >
          > > > ---------------------------------------------
          > > >
          > > > From: Adam Mahnke <kc2ant@>
          > > > To: "mailto:aprsisce%40yahoogroups.com"
          > > <mailto:aprsisce%40yahoogroups.com>
          > > > Sent: Tuesday, August 27, 2013 10:16 PM
          > > > Subject: RE: [aprsisce] KPC3 configuration
          > > >
          > > > Â
          > > > As I recall, the KPC3 will only work in KISS mode, the trick is
          > > locking it into KISS mode across a power reset.
          > > >
          > > > http://aprsisce.wikidot.com/tnc-kpc-3
          > > >
          > > >
          > > > Adam
          > > > KC2ANT
          > > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31
          > > +0000Subject: [aprsisce] KPC3 configurationÂ
          > > > I've just installed APRSISCE and it's working on the laptop (Vista
          > > 32)and receiving Local APRS sations via the internet. I need to use a
          > > KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have
          > > to be in KISS mode? I also use the KPC3 with Outpost Packet Message
          > > Manager using Terminal Mode, so connections are already made to radio,
          > > TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS
          > > as well as packet but wanting to learn more.ThanksBobKE6GYD
          > > >
          > >
          > >
          > >
          > >
          >
        • Fred Hillhouse
          Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!! This now becomes education for me
          Message 4 of 29 , Aug 30, 2013
          • 0 Attachment
            Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
             
            This now becomes education for me and anyone wishing to follow along.
             
            Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
             
            If I look at this line from below:
            <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
             
            I understand this to say:
            Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
             
            I think it can be rewritten and produce the same results as:
            <OpenCmd>CD SOFT</OpenCmd>
             
            And one more from the XML:
            <OpenCmd>RESET!!3</OpenCmd>
            I understand this to say:
            Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
             
             
            Best regards,
             
            Fred N7FMH
             
             

            From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
            Sent: Friday, August 30, 2013 09:55
            To: aprsisce@yahoogroups.com
            Subject: Re: [aprsisce] Re: KPC3 configuration

             

            Read it carefully and completely.  It says (just above the example you're referencing):

            If you don't specify a Response (no !), "cmd:" is expected

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


            On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
            Is there something missing on this page?
             
            In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
             
            Best regards,
            Fred N7FMH



            From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
            Sent: Thursday, August 29, 2013 21:31
            To: aprsisce@yahoogroups.com
            Subject: Re: [aprsisce] Re: KPC3 configuration

             

            From the log, it is not going into KISS mode.
            The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
              and it looks like I had a bad "cmd:" after the reset.

            Here is an EXACT copy of my port for my KPC-3:
            <!--RFPort[0]-->
            <RFPort Name="KPC3">
            <Protocol>KISS</Protocol>
            <Device>COM1:9600,N,8,1</Device>
            <RfBaud>1200</RfBaud>
            <OpenCmd>^M~!!0</OpenCmd>
            <OpenCmd>^C~!cmd:!2</OpenCmd>
            <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
            <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
            <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
            <OpenCmd>INT KISS!!0</OpenCmd>
            <OpenCmd>RESET!!3</OpenCmd>
            <CloseCmd>^192^255^192~!!0</CloseCmd>
            <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
            <QuietTime>0</QuietTime>
            <Enabled>1</Enabled>
            <XmitEnabled>1</XmitEnabled>
            <ProvidesNMEA>0</ProvidesNMEA>
            <RFtoISEnabled>1</RFtoISEnabled>
            <IStoRFEnabled>1</IStoRFEnabled>
            <MyCallNot3rd>0</MyCallNot3rd>
            <BeaconingEnabled>1</BeaconingEnabled>
            <BeaconPath>WIDE2-1</BeaconPath>
            <BulletinObjectEnabled>1</BulletinObjectEnabled>
            <DXEnabled>1</DXEnabled>
            <DXPath>RFONLY</DXPath>
            <MessagesEnabled>1</MessagesEnabled>
            <MessagePath></MessagePath>
            <TelemetryEnabled>0</TelemetryEnabled>
            <TelemetryPath></TelemetryPath>
            <!--DigiXform-->
            </RFPort><!--RFPort[0]-->


            If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly.
            If you have an issue the first time, try
               >Enables >View Logs >Ports(KPC-3)
               >Enables > Port >KPC-3            to close the port
            then again
               >Enables > Port >KPC-3            to re-open the port

            Then check the log - post if needed
            Robert Giuliano
            KB8RCO


            ---------------------------------------------

            From: ke6gyd <ke6gyd@...>
            To: aprsisce@yahoogroups.com
            Sent: Thursday, August 29, 2013 8:01 PM
            Subject: [aprsisce] Re: KPC3 configuration
             
            Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something?

            <!--RFPort[0]-->
            <RFPort Name="KPC-3">
            <Protocol>KISS</Protocol>
            <Device>COM1:9600,N,8,1</Device>
            <RfBaud>1200</RfBaud>
            <OpenCmd>^M~1!!0</OpenCmd>
            <OpenCmd>^C~!cmd:!2</OpenCmd>
            <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
            <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
            <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
            <OpenCmd>INT KISS!cmd:!1</OpenCmd>
            <OpenCmd>RESET!cmd:!3</OpenCmd>
            <CloseCmd>^192^255^192~!!0</CloseCmd>
            <CloseCmd>^C^C^C~!!0</CloseCmd>
            <CloseCmd>TC 1!TS 1</CloseCmd>
            <CloseCmd>TN 2,0!TN 2,0</CloseCmd>
            <QuietTime>0</QuietTime>
            <Enabled>0</Enabled>

            Log shows:
            Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0>

            Looks like it somehow is not in KISS mode?

            Any suggestions would be appreciated.
            Thanks
            Bob
            KE6GYD

            --- In aprsisce@yahoogroups.com, Rob Giuliano <kb8rco@...> wrote:
            >
            > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED.
            > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed.
            >    KEY-> the port is opened when APRSISce/32 requests use of it
            >              Application start-up if configured as OPEN on last close
            >             Also through the menu system:
            >               >Enables >Ports {your KPC3 port name}
            >
            >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup)
            > Mine is setup with:
            > <OpenCmd>^M~!!0</OpenCmd>
            > <OpenCmd>^C~!cmd:!2</OpenCmd>
            > <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
            > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
            > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
            > <OpenCmd>INT KISS!cmd:!1</OpenCmd>
            > <OpenCmd>RESET!cmd:!3</OpenCmd>
            >
            > <CloseCmd>^192^255^192~!!0</CloseCmd>
            > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd>
            >
            > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup.
            >
            > Give these a try and let us know
            >
            > Robert Giuliano
            > KB8RCO
            >
            >
            > ---------------------------------------------
            >
            >
            > ________________________________
            > From: ke6gyd <ke6gyd@...>
            > To: aprsisce@yahoogroups.com
            > Sent: Thursday, August 29, 2013 10:35 AM
            > Subject: [aprsisce] Re: KPC3 configuration
            >
            >  
            >
            > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet.
            >
            > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated.
            >
            > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this?
            >
            > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available.
            >
            > Thanks
            > Bob
            > KE6GYD
            >
            > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
            > >
            > > I TOTALLY disagree!
            > >
            > >
            > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you.
            > >
            > > Which you choose will determine what type of port
            > >    Continuous Mode - Simple KISS
            > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode.
            > >
            > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . .
            > >  
            > >
            > > Robert Giuliano
            > > KB8RCO
            > >
            > >
            > > ---------------------------------------------
            > >
            > > From: Adam Mahnke <kc2ant@>
            > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com>
            > > Sent: Tuesday, August 27, 2013 10:16 PM
            > > Subject: RE: [aprsisce] KPC3 configuration
            > >
            > >  
            > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset.
            > >
            > > http://aprsisce.wikidot.com/tnc-kpc-3
            > >
            > >
            > > Adam
            > > KC2ANT
            > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration 
            > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD
            > >
            >


          • Pat Ryan KC6VVT
            Fred AGREED, my simple point is, with Kantronic tnc (KPC-3 and other models) the RESET command means it may go to a simple terminal mode with a limited TNC
            Message 5 of 29 , Aug 30, 2013
            • 0 Attachment
              Fred

              AGREED, my simple point is, with Kantronic tnc (KPC-3 and other models) the RESET command means it may go to a simple terminal mode with a limited TNC command set available WHICH MAY NOT BE ENOUGH for other packet programs.

              If having trouble when exiting APRSIS32 when you attempt to use these other packet programs, consider the addition of the
              INTF TERM
              command to make ALL Kantronics TNC commands available to the other packet program!

              73 de Pat KC6VVT


              --- In aprsisce@yahoogroups.com, "Fred Hillhouse" <fmhillhouse@...> wrote:
              >
              > Since the KPC in question is going into KISS, apparently the XML is fine. NO
              > changes should be made to any XML at this time!!
              >
              > This now becomes education for me and anyone wishing to follow along.
              >
              > Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in
              > the XML of interest below. I had never looked at this section in the WIKI
              > since I don't have a TNC set up in this fashion.
              >
              > If I look at this line from below:
              > <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
              >
              > I understand this to say:
              > Send command "CD SOFT", and don't look for "cmd:" but look for what is in
              > the field, which just happens to be "cmd:" for up to one second.
              >
              > I think it can be rewritten and produce the same results as:
              > <OpenCmd>CD SOFT</OpenCmd>
              >
              > And one more from the XML:
              > <OpenCmd>RESET!!3</OpenCmd>
              >
              > I understand this to say:
              > Send command "RESET", don't expect any return, wait for 3 seconds, then
              > continue.
              >
              >
              > Best regards,
              >
              > Fred N7FMH
              >
              >
              >
              > _____
              >
              > From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf
              > Of Lynn W Deffenbaugh (Mr)
              > Sent: Friday, August 30, 2013 09:55
              > To: aprsisce@yahoogroups.com
              > Subject: Re: [aprsisce] Re: KPC3 configuration
              >
              >
              >
              >
              >
              >
              > Read it carefully and completely. It says (just above the example you're
              > referencing):
              >
              >
              >
              > If you don't specify a Response (no !), "cmd:" is expected
              >
              >
              > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
              >
              >
              > On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
              >
              >
              > Is there something missing on this page?
              > http://aprsisce.wikidot.com/doc:openclosecmd
              >
              > In the samples at the bottom, the one for "KISS ON" appears incomplete when
              > compared with the open commands below. Or is "cmd:" always expected so it
              > really doesn't need to be included?
              >
              > Best regards,
              > Fred N7FMH
              >
              >
              >
              >
              >
              > _____
              >
              > From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf
              > Of Rob Giuliano
              > Sent: Thursday, August 29, 2013 21:31
              > To: aprsisce@yahoogroups.com
              > Subject: Re: [aprsisce] Re: KPC3 configuration
              >
              >
              >
              >
              >
              >
              > From the log, it is not going into KISS mode.
              > The only issue I see is an "EXTRA <ONE> on your first <OpenCmd>
              > and it looks like I had a bad "cmd:" after the reset.
              >
              >
              > Here is an EXACT copy of my port for my KPC-3:
              >
              > <!--RFPort[0]-->
              >
              > <RFPort Name="KPC3">
              > <Protocol>KISS</Protocol>
              > <Device>COM1:9600,N,8,1</Device>
              > <RfBaud>1200</RfBaud>
              > <OpenCmd>^M~!!0</OpenCmd>
              > <OpenCmd>^C~!cmd:!2</OpenCmd>
              > <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
              > <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
              > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
              > <OpenCmd>INT KISS!!0</OpenCmd>
              > <OpenCmd>RESET!!3</OpenCmd>
              > <CloseCmd>^192^255^192~!!0</CloseCmd>
              > <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
              > <QuietTime>0</QuietTime>
              > <Enabled>1</Enabled>
              > <XmitEnabled>1</XmitEnabled>
              > <ProvidesNMEA>0</ProvidesNMEA>
              > <RFtoISEnabled>1</RFtoISEnabled>
              > <IStoRFEnabled>1</IStoRFEnabled>
              > <MyCallNot3rd>0</MyCallNot3rd>
              > <BeaconingEnabled>1</BeaconingEnabled>
              > <BeaconPath>WIDE2-1</BeaconPath>
              > <BulletinObjectEnabled>1</BulletinObjectEnabled>
              > <DXEnabled>1</DXEnabled>
              > <DXPath>RFONLY</DXPath>
              > <MessagesEnabled>1</MessagesEnabled>
              > <MessagePath></MessagePath>
              > <TelemetryEnabled>0</TelemetryEnabled>
              > <TelemetryPath></TelemetryPath>
              > <!--DigiXform-->
              > </RFPort><!--RFPort[0]-->
              >
              >
              >
              > If power is lost while connected, it may stay in KISS mode, If you OPEN and
              > CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen
              > the port properly.
              > If you have an issue the first time, try
              > >Enables >View Logs >Ports(KPC-3)
              > >Enables > Port >KPC-3 to close the port
              > then again
              > >Enables > Port >KPC-3 to re-open the port
              >
              > Then check the log - post if needed
              > Robert Giuliano
              > KB8RCO
              >
              >
              > ---------------------------------------------
              >
              > From: ke6gyd <mailto:ke6gyd@...> <ke6gyd@...>
              > To: aprsisce@yahoogroups.com
              > Sent: Thursday, August 29, 2013 8:01 PM
              > Subject: [aprsisce] Re: KPC3 configuration
              >
              >
              > Below are the settings I've done as per your last suggestion. Still can't
              > get KPC3 (NO PLUS) to work except for one time after editing the xml file to
              > your suggestions. Don't know if I changed anything that one time. Maybe I'm
              > missing something?
              >
              > <!--RFPort[0]-->
              > <RFPort Name="KPC-3">
              > <Protocol>KISS</Protocol>
              > <Device>COM1:9600,N,8,1</Device>
              > <RfBaud>1200</RfBaud>
              > <OpenCmd>^M~1!!0</OpenCmd>
              > <OpenCmd>^C~!cmd:!2</OpenCmd>
              > <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
              > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
              > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
              > <OpenCmd>INT KISS!cmd:!1</OpenCmd>
              > <OpenCmd>RESET!cmd:!3</OpenCmd>
              > <CloseCmd>^192^255^192~!!0</CloseCmd>
              > <CloseCmd>^C^C^C~!!0</CloseCmd>
              > <CloseCmd>TC 1!TS 1</CloseCmd>
              > <CloseCmd>TN 2,0!TN 2,0</CloseCmd>
              > <QuietTime>0</QuietTime>
              > <Enabled>0</Enabled>
              >
              > Log shows:
              > Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0
              > 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03
              > F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9
              > SATS08 <C0>
              >
              > Looks like it somehow is not in KISS mode?
              >
              > Any suggestions would be appreciated.
              > Thanks
              > Bob
              > KE6GYD
              >
              > --- In aprsisce@yahoogroups.com <mailto:aprsisce%40yahoogroups.com> , Rob
              > Giuliano <mailto:kb8rco@> <kb8rco@> wrote:
              > >
              > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the
              > TNC when the port is OPENED or CLOSED.
              > > These commands can be used to tell the KPC-3 to enter KISS MODE when the
              > port is opened, and to tell the KPC-3 to return to its standard mode when
              > the port is closed.
              > > Â Â KEY-> the port is opened when APRSISce/32 requests use of it
              > > Â Â Â Â Â Â Â Â Â Â Â Â Application start-up if configured as OPEN on
              > last close
              > > Â Â Â Â Â Â Â Â Â Â Â Also through the menu system:
              > > Â Â Â Â Â Â Â Â Â Â Â Â Â >Enables >Ports {your KPC3 port name}
              > >
              > > Â You have to edit the XML file in the directory where you APRSIS32.EXE
              > file is (or linked to if you have a complex setup)
              > > Mine is setup with:
              > > <OpenCmd>^M~!!0</OpenCmd>
              > > <OpenCmd>^C~!cmd:!2</OpenCmd>
              > > <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
              > > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
              > > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
              > > <OpenCmd>INT KISS!cmd:!1</OpenCmd>
              > > <OpenCmd>RESET!cmd:!3</OpenCmd>
              > >
              > > <CloseCmd>^192^255^192~!!0</CloseCmd>
              > > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd>
              > >
              > > The open commands seem like a lot of "extras", but I had soime issues with
              > FLOW and Duplex, so I explicitly set them in the setup.
              > >
              > > Give these a try and let us know
              > >
              > > Robert Giuliano
              > > KB8RCO
              > >
              > >
              > > ---------------------------------------------
              > >
              > >
              > > ________________________________
              > > From: ke6gyd <mailto:ke6gyd@> <ke6gyd@>
              > > To: aprsisce@yahoogroups.com <mailto:aprsisce%40yahoogroups.com>
              > > Sent: Thursday, August 29, 2013 10:35 AM
              > > Subject: [aprsisce] Re: KPC3 configuration
              > >
              > > Â
              > >
              > > I'm leaning toward on demand and would like the TNC to return to normal
              > mode since I use the TNC mostly for EComm use of Packet.
              > >
              > > What I don't understand in the text below is how to set that up with my
              > KPC-3 and 3+. I'm not familiar with the terminology stated.
              > >
              > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or
              > is that set in the TNC? Where can I find the menu's to accomplish this?
              > >
              > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode
              > with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the
              > TT4 available.
              > >
              > > Thanks
              > > Bob
              > > KE6GYD
              > >
              > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
              > > >
              > > > I TOTALLY disagree!
              > > >
              > > >
              > > > I agree that the best mode is KISS, but whether you CHOOSE to have it
              > continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it
              > in KISS mode on start and set it back to normal (converse) mode after shut
              > down, is COMPLELY up to you.
              > > >
              > > > Which you choose will determine what type of port
              > > >   Continuous Mode - Simple KISS
              > > >   KISS on demand - set OPENCMD and CLOSECMD commands to ensure
              > the TNC (KPC-3) is in the correct mode.
              > > >
              > > > I use the KPC-3, all the time (KB8RCO). Not the Plus . . .
              > > > ÂÂ
              > > >
              > > > Robert Giuliano
              > > > KB8RCO
              > > >
              > > >
              > > > ---------------------------------------------
              > > >
              > > > From: Adam Mahnke <kc2ant@>
              > > > To: "mailto:aprsisce%40yahoogroups.com"
              > <mailto:aprsisce%40yahoogroups.com> <mailto:aprsisce%40yahoogroups.com>
              > <mailto:aprsisce%40yahoogroups.com>
              > > > Sent: Tuesday, August 27, 2013 10:16 PM
              > > > Subject: RE: [aprsisce] KPC3 configuration
              > > >
              > > > ÂÂ
              > > > As I recall, the KPC3 will only work in KISS mode, the trick is locking
              > it into KISS mode across a power reset.
              > > >
              > > > http://aprsisce.wikidot.com/tnc-kpc-3
              > > >
              > > >
              > > > Adam
              > > > KC2ANT
              > > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject:
              > [aprsisce] KPC3 configurationÂÂ
              > > > I've just installed APRSISCE and it's working on the laptop (Vista
              > 32)and receiving Local APRS sations via the internet. I need to use a KPC 3
              > AND 3+ so I can see stations received via RF. Does the KPC3 have to be in
              > KISS mode? I also use the KPC3 with Outpost Packet Message Manager using
              > Terminal Mode, so connections are already made to radio, TNC and computer
              > using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but
              > wanting to learn more.ThanksBobKE6GYD
              > > >
              > >
              >
            • Rob Giuliano
              I can t say I really looked at the packet before. Is this a GPS pass-through?    If it is, this must be the KPC-3+ as my KPC-3 doesn t have the capability of
              Message 6 of 29 , Aug 30, 2013
              • 0 Attachment
                I can't say I really looked at the packet before.
                Is this a GPS pass-through?
                   If it is, this must be the KPC-3+ as my KPC-3 doesn't have the capability of 2 serial inputs (GPS and computer).
                 
                 
                Robert Giuliano
                KB8RCO


                ---------------------------------------------

                From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                To: aprsisce@yahoogroups.com
                Sent: Friday, August 30, 2013 9:51 AM
                Subject: Re: [aprsisce] Re: KPC3 configuration

                Actually, it IS going into KISS mode or you wouldn't be seeing the <C0>
                stuff. That's the KISS packet wrapper. The issue is that APRSISCE/32 is
                expecting a command 0 (low nibble) in the first byte of the KISS packet,
                but your packet has 8E or command 14. I need to look that up, but here's
                the interpretation of the packet from your log (I assume you get one of
                these for every packet received?).

                <C0    - Packet framing character
                8E    - Type indicator - but this seems to be missing in your packet!
                8E A0 A6 98 96>@`    - Destination callsign (GPSLK )
                <AE>l<86 A6 A0>@b    - Source callsign (W6CSP -1)
                <9C>l<8A B0>@@<E3    - Path component (N6EX  -1) used (high bit) & last component (low bit)
                03 F0>            - AX.25 protocol and flags (IIRC)
                $GPGGA,051524,3350.5768,N,11755.8527,W,1,08,1.2,37.2,M,-31.9,M,,*4A    - Packet payload!
                <0D 0A    - Don't know why he's including the <cr><lf>, but it's in the packet! - See below...
                C0>    - Packet framing character
                 

                The byte immediately following the opening <C0> is SUPPOSED to be a
                command byte whose upper bit (8x) indicates a SMACK packet, the next 3
                bits are the port number, and the lower nibble (4 bits) is the command
                which APRSISCE/32 expects to be 0 and is causing the packet to be
                rejected. However, your packet seems to be missing this byte because the
                <8E> that was there appears to be the first character (G) of the
                destination callsign. For the KISS spec, please see
                http://www.ax25.net/kiss.aspxwhich states at the end of section 4:

                > The following types are defined in frames to the host:
                >
                > Type            Function        Comments
                >     
                >    0                Data frame      Rest of frame is data from
                >                                      the HDLC channel.

                The destination, source, and path callsigns are bit-shifted ASCII and
                the -SSIDs are encoded in 4 bits of binary along with some flags (hence
                the 0-15 limit on AX.25 compatible -SSIDs). This is the AX.25 packet
                header being carried in the KISS data frame.

                The packet payload is a raw $GPGGA string that correlates to what
                aprs.fi shows for W6CSP-1
                (http://aprs.fi/?c=raw&call=W6CSP-1&limit=5&view=hex). Interestingly
                though, the <CR><LF> aren't in those raw packets, but then they weren't
                digipeated by N6EX-1 either, but received directly by the BOXSPG IGate
                with the original WIDE2-2 path intact. N6EX-1 seems to have replaced the
                path with his own used callsign and apparently appended a <CR><LF> to
                the packet unless that was done by your TNC.

                Question: if you receive other packets in this trace log, do they all
                end with <0D 0A C0>? This may be another bust (IMHO) in your TNC's KISS
                implementation.

                Bottom line: while this appears to be a KISS packet, it's not a proper
                KISS packet, at least not for what I've read in the KISS specs.

                Does anyone else out there have one of these TNCs connected to
                APRSISCE/32 in KISS mode and what are you seeing in your port's trace
                log if you enable it?

                And Bob, if you Enable this trace log, do you see any packets coming
                through cleanly or are they all complaining about the "Missing 0"?

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

                On 8/30/2013 1:19 AM, ke6gyd wrote:
                > Really appreciate your help.  Still not going into KISS mode:
                >
                > Port(KPC3):2013-08-30T05:15:29.953 KISS:Missing 0, found C0[94]:<C0 8E A0 A6 98 96>@`<AE>l<86 A6 A0>@b<9C>l<8A B0>@@<E3 03 F0>$GPGGA,051524,3350.5768,N,11755.8527,W,1,08,1.2,37.2,M,-31.9,M,,*4A<0D 0A C0>
                >
                > Copied and pasted exactly your settings into the .xml file.
                >
                > If any other advice, let me know.  We'll keep trying.
                > Thanks
                > Bob
                > KE6GYD
                >
                > --- In aprsisce@yahoogroups.com, Rob Giuliano <kb8rco@...> wrote:
                >>  From the log, it is not going into KISS mode.
                >> The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                >>   and it looks like I had a bad "cmd:" after the reset.
                >>
                >>
                >> Here is an EXACT copy of my port for my KPC-3:
                >> <!--RFPort[0]-->
                >>
                >> <RFPort Name="KPC3">
                >> <Protocol>KISS</Protocol>
                >> <Device>COM1:9600,N,8,1</Device>
                >> <RfBaud>1200</RfBaud>
                >> <OpenCmd>^M~!!0</OpenCmd>
                >> <OpenCmd>^C~!cmd:!2</OpenCmd>
                >> <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                >> <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                >> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                >> <OpenCmd>INT KISS!!0</OpenCmd>
                >> <OpenCmd>RESET!!3</OpenCmd>
                >> <CloseCmd>^192^255^192~!!0</CloseCmd>
                >> <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                >> <QuietTime>0</QuietTime>
                >> <Enabled>1</Enabled>
                >> <XmitEnabled>1</XmitEnabled>
                >> <ProvidesNMEA>0</ProvidesNMEA>
                >> <RFtoISEnabled>1</RFtoISEnabled>
                >> <IStoRFEnabled>1</IStoRFEnabled>
                >> <MyCallNot3rd>0</MyCallNot3rd>
                >> <BeaconingEnabled>1</BeaconingEnabled>
                >> <BeaconPath>WIDE2-1</BeaconPath>
                >> <BulletinObjectEnabled>1</BulletinObjectEnabled>
                >> <DXEnabled>1</DXEnabled>
                >> <DXPath>RFONLY</DXPath>
                >> <MessagesEnabled>1</MessagesEnabled>
                >> <MessagePath></MessagePath>
                >> <TelemetryEnabled>0</TelemetryEnabled>
                >> <TelemetryPath></TelemetryPath>
                >> <!--DigiXform-->
                >> </RFPort>
                >> <!--RFPort[0]-->
                >>
                >>
                >> If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly.
                >> If you have an issue the first time, try
                >>    >Enables >View Logs >Ports(KPC-3)
                >>    >Enables > Port >KPC-3            to close the port
                >> then again
                >>    >Enables > Port >KPC-3            to re-open the port
                >>
                >> Then check the log - post if needed
                >> Robert Giuliano
                >> KB8RCO
                >>
                >>
                >> ---------------------------------------------
                >>
                >> From: ke6gyd <ke6gyd@...>
                >> To: aprsisce@yahoogroups.com
                >> Sent: Thursday, August 29, 2013 8:01 PM
                >> Subject: [aprsisce] Re: KPC3 configuration
                >>
                >> Â
                >> Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something?
                >>
                >> <!--RFPort[0]-->
                >> <RFPort Name="KPC-3">
                >> <Protocol>KISS</Protocol>
                >> <Device>COM1:9600,N,8,1</Device>
                >> <RfBaud>1200</RfBaud>
                >> <OpenCmd>^M~1!!0</OpenCmd>
                >> <OpenCmd>^C~!cmd:!2</OpenCmd>
                >> <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                >> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
                >> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                >> <OpenCmd>INT KISS!cmd:!1</OpenCmd>
                >> <OpenCmd>RESET!cmd:!3</OpenCmd>
                >> <CloseCmd>^192^255^192~!!0</CloseCmd>
                >> <CloseCmd>^C^C^C~!!0</CloseCmd>
                >> <CloseCmd>TC 1!TS
                >>  1</CloseCmd>
                >> <CloseCmd>TN 2,0!TN 2,0</CloseCmd>
                >> <QuietTime>0</QuietTime>
                >> <Enabled>0</Enabled>
                >>
                >> Log shows:
                >> Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0>
                >>
                >> Looks like it somehow is not in KISS mode?
                >>
                >> Any suggestions would be appreciated.
                >> Thanks
                >> Bob
                >> KE6GYD
                >>
                >> --- In aprsisce@yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
                >>> APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED.
                >>> These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened,
                >>  and to
                >>  tell the KPC-3 to return to its standard mode when the port is closed.
                >>>    KEY-> the port is opened when APRSISce/32 requests use of it
                >>>              Application start-up if configured as OPEN on last close
                >>>             Also through the menu system:
                >>>               >Enables >Ports {your KPC3 port name}
                >>>
                >>>  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup)
                >>> Mine is setup with:
                >>> <OpenCmd>^M~!!0</OpenCmd>
                >>> <OpenCmd>^C~!cmd:!2</OpenCmd>
                >>> <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                >>> <OpenCmd>XFLOW
                >>  ON!cmd:!1</OpenCmd>
                >>> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                >>> <OpenCmd>INT KISS!cmd:!1</OpenCmd>
                >>> <OpenCmd>RESET!cmd:!3</OpenCmd>
                >>>
                >>> <CloseCmd>^192^255^192~!!0</CloseCmd>
                >>> <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd>
                >>>
                >>> The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup.
                >>>
                >>> Give these a try and let us know
                >>>
                >>> Robert Giuliano
                >>> KB8RCO
                >>>
                >>>
                >>> ---------------------------------------------
                >>>
                >>>
                >>> ________________________________
                >>> From: ke6gyd <ke6gyd@>
                >>> To: aprsisce@yahoogroups.com
                >>> Sent: Thursday, August 29, 2013 10:35 AM
                >>> Subject:
                >>  [aprsisce]
                >>  Re: KPC3 configuration
                >>> ÂÂ
                >>>
                >>> I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet.
                >>>
                >>> What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated.
                >>>
                >>> Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this?
                >>>
                >>> BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available.
                >>>
                >>> Thanks
                >>> Bob
                >>> KE6GYD
                >>>
                >>> --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
                >>>> I TOTALLY disagree!
                >>>>
                >>>>
                >>>> I agree that the best mode is KISS, but
                >>  whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you.
                >>>> Which you choose will determine what type of port
                >>>>    Continuous Mode - Simple KISS
                >>>>    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode.
                >>>>
                >>>> I use the KPC-3, all the time (KB8RCO).  Not the Plus . . .
                >>>> ÂÂÂ
                >>>>
                >>>> Robert Giuliano
                >>>> KB8RCO
                >>>>
                >>>>
                >>>> ---------------------------------------------
                >>>>
                >>>> From: Adam Mahnke <kc2ant@>
                >>>> To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com>
                >>>> Sent: Tuesday,
                >>  August 27, 2013 10:16 PM
                >>>> Subject: RE: [aprsisce] KPC3 configuration
                >>>>
                >>>> ÂÂÂ
                >>>> As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset.
                >>>>
                >>>> http://aprsisce.wikidot.com/tnc-kpc-3
                >>>>
                >>>>
                >>>> Adam
                >>>> KC2ANT
                >>>> To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configurationÂÂÂ
                >>>> I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using
                >>  a
                >>  USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD
                >
                >
                >
                > ------------------------------------
                >
                > Yahoo! Groups Links
                >
                >
                >
                >



                ------------------------------------

                Yahoo! Groups Links

                <*> To visit your group on the web, go to:
                    http://groups.yahoo.com/group/aprsisce/

                <*> Your email settings:
                    Individual Email | Traditional

                <*> To change settings online go to:
                    http://groups.yahoo.com/group/aprsisce/join
                    (Yahoo! ID required)

                <*> To change settings via email:
                    aprsisce-digest@yahoogroups.com
                    aprsisce-fullfeatured@yahoogroups.com

                <*> To unsubscribe from this group, send an email to:
                    aprsisce-unsubscribe@yahoogroups.com

                <*> Your use of Yahoo! Groups is subject to:
                    http://docs.yahoo.com/info/terms/



              • Rob Giuliano
                IMHO, the TNC setup for the other packet programs should take care of their own setup. The exit commands are a HARD RESET, and drop you into a cmd: prompt
                Message 7 of 29 , Aug 30, 2013
                • 0 Attachment
                  IMHO, the TNC setup for the "other packet programs" should take care of their own setup.
                  The exit commands are a HARD RESET, and drop you into a cmd: prompt just as if you turned on the TNC.
                   
                  With OpenCmd and/or CloseCmd, you can vary the time parameter at the end if the unit resets.
                  On my unit, it is typically less than 2 seconds, but sometimes more - I use 3.
                   
                       <OpenCmd>RESET!cmd:!3</OpenCmd>
                   
                      <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd>
                   
                  Robert Giuliano
                  KB8RCO


                  ---------------------------------------------

                  From: Pat Ryan KC6VVT <kc6vvt@...>
                  To: aprsisce@yahoogroups.com
                  Sent: Friday, August 30, 2013 10:33 AM
                  Subject: [aprsisce] Re: KPC3 configuration at exit of APRSIS32 progam
                   
                  I add that in Bob's KB8RCO desire to make the Kantronics KPC-3 series TNC ready for terminal use by other packet programs, that adding an interface command line might be better at APRSIS32 exit, at the end of the triple ctrl C reset group.

                  > > <CloseCmd>INT TERM

                  and add any other TNC setup parameters thereafter, as long as the commands do not cause the TNC to automatically reset - see the Kantronics manual for those annotated commands!

                  73 de Pat KC6VVT

                  --- In mailto:aprsisce%40yahoogroups.com, "Lynn W Deffenbaugh (Mr)" <kj4erj@...> wrote:
                  >
                  > You can also read about the KPC-3+ on the Wiki at:
                  >
                  > http://aprsisce.wikidot.com/tnc-kpc-3
                  >
                  > The commands may be different for the non-plus version, but the idea is
                  > the same.
                  >
                  > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
                  >
                  > On 8/29/2013 12:49 PM, Rob Giuliano wrote:
                  > >
                  > >
                  > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to
                  > > the TNC when the port is OPENED or CLOSED.
                  > > These commands can be used to tell the KPC-3 to enter KISS MODE when
                  > > the port is opened, and to tell the KPC-3 to return to its standard
                  > > mode when the port is closed.
                  > > KEY-> the port is opened when APRSISce/32 requests use of it
                  > > Application start-up if configured as OPEN on last close
                  > > Also through the menu system:
                  > > >Enables >Ports {your KPC3 port name}
                  > > You have to edit the XML file in the directory where you APRSIS32.EXE
                  > > file is (or linked to if you have a complex setup)
                  > > Mine is setup with:
                  > > <OpenCmd>^M~!!0</OpenCmd>
                  > > <OpenCmd>^C~!cmd:!2</OpenCmd>
                  > > <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                  > > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
                  > > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                  > > <OpenCmd>INT KISS!cmd:!1</OpenCmd>
                  > > <OpenCmd>RESET!cmd:!3</OpenCmd>
                  > > <CloseCmd>^192^255^192~!!0</CloseCmd>
                  > > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd>
                  > > The open commands seem like a lot of "extras", but I had soime issues
                  > > with FLOW and Duplex, so I explicitly set them in the setup.
                  > > Give these a try and let us know
                  > > Robert Giuliano
                  > > KB8RCO
                  > >
                  > >
                  > > ---------------------------------------------
                  > >
                  > > *From:* ke6gyd <ke6gyd@...>
                  > > *To:* mailto:aprsisce%40yahoogroups.com
                  > > *Sent:* Thursday, August 29, 2013 10:35 AM
                  > > *Subject:* [aprsisce] Re: KPC3 configuration
                  > >
                  > > I'm leaning toward on demand and would like the TNC to return to
                  > > normal mode since I use the TNC mostly for EComm use of Packet.
                  > >
                  > > What I don't understand in the text below is how to set that up with
                  > > my KPC-3 and 3+. I'm not familiar with the terminology stated.
                  > >
                  > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings
                  > > or is that set in the TNC? Where can I find the menu's to accomplish this?
                  > >
                  > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS
                  > > mode with APRSIS32, but I'd like the ability to use the KPC'3 if I
                  > > don't have the TT4 available.
                  > >
                  > > Thanks
                  > > Bob
                  > > KE6GYD
                  > >
                  > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
                  > > >
                  > > > I TOTALLY disagree!
                  > > >
                  > > >
                  > > > I agree that the best mode is KISS, but whether you CHOOSE to have
                  > > it continuously in KISS mode (over resets) or CHOOSE to have
                  > > APRSISce/32 put it in KISS mode on start and set it back to normal
                  > > (converse) mode after shut down, is COMPLELY up to you.
                  > > >
                  > > > Which you choose will determine what type of port
                  > > > Â Â Continuous Mode - Simple KISS
                  > > > Â Â KISS on demand - set OPENCMD and CLOSECMD commands to ensure
                  > > the TNC (KPC-3) is in the correct mode.
                  > > >
                  > > > I use the KPC-3, all the time (KB8RCO). Not the Plus . . .
                  > > > Â
                  > > >
                  > > > Robert Giuliano
                  > > > KB8RCO
                  > > >
                  > > >
                  > > > ---------------------------------------------
                  > > >
                  > > > From: Adam Mahnke <kc2ant@>
                  > > > To: "mailto:aprsisce%40yahoogroups.com"
                  > > <mailto:aprsisce%40yahoogroups.com>
                  > > > Sent: Tuesday, August 27, 2013 10:16 PM
                  > > > Subject: RE: [aprsisce] KPC3 configuration
                  > > >
                  > > > Â
                  > > > As I recall, the KPC3 will only work in KISS mode, the trick is
                  > > locking it into KISS mode across a power reset.
                  > > >
                  > > > http://aprsisce.wikidot.com/tnc-kpc-3
                  > > >
                  > > >
                  > > > Adam
                  > > > KC2ANT
                  > > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31
                  > > +0000Subject: [aprsisce] KPC3 configurationÂ
                  > > > I've just installed APRSISCE and it's working on the laptop (Vista
                  > > 32)and receiving Local APRS sations via the internet. I need to use a
                  > > KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have
                  > > to be in KISS mode? I also use the KPC3 with Outpost Packet Message
                  > > Manager using Terminal Mode, so connections are already made to radio,
                  > > TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS
                  > > as well as packet but wanting to learn more.ThanksBobKE6GYD
                  > > >
                  > >
                  > >
                  > >
                  > >
                  >

                • Rob Giuliano
                  I believe a command like CD SOFT!cmd:!1   means -    Send command CD SOFT    YES - Look for response from TNC of cmd: for 1 seond
                  Message 8 of 29 , Aug 30, 2013
                  • 0 Attachment
                    I believe a command like
                    <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                     
                    means ->
                       Send command "CD SOFT"
                       YES - Look for response from TNC of "cmd:" for 1 seond
                     
                    What "field" are you talking about?  "...but look for what is in the field ..."
                    The "FIELD" between two "!" is "cmd:" -> that's what to look for.
                     
                    The cmd: is what the KPC-3 sends when in "command mode".
                       If it arrives immediately, APRSIS32 will go to the next step.
                       If it doesn't arrive in "1" second, APRSIS32 will go to the next step.
                     
                    That is how I understand it, and it seems to be how APRSIS32 is interfacing with my KPC-3.
                     
                    I can't get at my KPC-3 right now, but will change it to:
                      
                       <OpenCmd>CD SOFT!Fred!10</OpenCmd>
                    to see if it waits 10 seconds before trying the enxt command. 
                       (You REALLY are FAMOUS if my KPC-3 actually responds to your name - hihi)
                     
                    Robert Giuliano
                    KB8RCO


                    ---------------------------------------------

                    From: Fred Hillhouse <fmhillhouse@...>
                    To: aprsisce@yahoogroups.com
                    Sent: Friday, August 30, 2013 10:35 AM
                    Subject: RE: [aprsisce] Re: KPC3 configuration
                     
                    Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
                     
                    This now becomes education for me and anyone wishing to follow along.
                     
                    Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
                     
                    If I look at this line from below:
                    <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                     
                    I understand this to say:
                    Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
                     
                    I think it can be rewritten and produce the same results as:
                    <OpenCmd>CD SOFT</OpenCmd>
                     
                    And one more from the XML:
                    <OpenCmd>RESET!!3</OpenCmd>
                    I understand this to say:
                    Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
                     
                     
                    Best regards,
                     
                    Fred N7FMH
                     
                     
                    From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
                    Sent: Friday, August 30, 2013 09:55
                    To: aprsisce@yahoogroups.com
                    Subject: Re: [aprsisce] Re: KPC3 configuration
                     
                    Read it carefully and completely.  It says (just above the example you're referencing):
                    If you don't specify a Response (no !), "cmd:" is expected
                    Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
                    Is there something missing on this page?
                     
                    In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
                     
                    Best regards,
                    Fred N7FMH


                    From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                    Sent: Thursday, August 29, 2013 21:31
                    To: aprsisce@yahoogroups.com
                    Subject: Re: [aprsisce] Re: KPC3 configuration
                     
                    From the log, it is not going into KISS mode.
                    The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                      and it looks like I had a bad "cmd:" after the reset.
                    Here is an EXACT copy of my port for my KPC-3:
                    <!--RFPort[0]-->
                    <RFPort Name="KPC3">
                    <Protocol>KISS</Protocol>
                    <Device>COM1:9600,N,8,1</Device>
                    <RfBaud>1200</RfBaud>
                    <OpenCmd>^M~!!0</OpenCmd>
                    <OpenCmd>^C~!cmd:!2</OpenCmd>
                    <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                    <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                    <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                    <OpenCmd>INT KISS!!0</OpenCmd>
                    <OpenCmd>RESET!!3</OpenCmd>
                    <CloseCmd>^192^255^192~!!0</CloseCmd>
                    <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                    <QuietTime>0</QuietTime>
                    <Enabled>1</Enabled>
                    <XmitEnabled>1</XmitEnabled>
                    <ProvidesNMEA>0</ProvidesNMEA>
                    <RFtoISEnabled>1</RFtoISEnabled>
                    <IStoRFEnabled>1</IStoRFEnabled>
                    <MyCallNot3rd>0</MyCallNot3rd>
                    <BeaconingEnabled>1</BeaconingEnabled>
                    <BeaconPath>WIDE2-1</BeaconPath>
                    <BulletinObjectEnabled>1</BulletinObjectEnabled>
                    <DXEnabled>1</DXEnabled>
                    <DXPath>RFONLY</DXPath>
                    <MessagesEnabled>1</MessagesEnabled>
                    <MessagePath></MessagePath>
                    <TelemetryEnabled>0</TelemetryEnabled>
                    <TelemetryPath></TelemetryPath>
                    <!--DigiXform-->
                    </RFPort><!--RFPort[0]-->

                    If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly. If you have an issue the first time, try    >Enables >View Logs >Ports(KPC-3)    >Enables > Port >KPC-3            to close the port then again    >Enables > Port >KPC-3            to re-open the port Then check the log - post if needed Robert Giuliano KB8RCO

                    ---------------------------------------------

                    From: ke6gyd mailto:ke6gyd@...
                    To: aprsisce@yahoogroups.com
                    Sent: Thursday, August 29, 2013 8:01 PM
                    Subject: [aprsisce] Re: KPC3 configuration
                     
                    Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something? <!--RFPort[0]--> <RFPort Name="KPC-3"> <Protocol>KISS</Protocol> <Device>COM1:9600,N,8,1</Device> <RfBaud>1200</RfBaud> <OpenCmd>^M~1!!0</OpenCmd> <OpenCmd>^C~!cmd:!2</OpenCmd> <OpenCmd>CD SOFT!cmd:!1</OpenCmd> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> <OpenCmd>INT KISS!cmd:!1</OpenCmd> <OpenCmd>RESET!cmd:!3</OpenCmd> <CloseCmd>^192^255^192~!!0</CloseCmd> <CloseCmd>^C^C^C~!!0</CloseCmd> <CloseCmd>TC 1!TS 1</CloseCmd> <CloseCmd>TN 2,0!TN 2,0</CloseCmd> <QuietTime>0</QuietTime> <Enabled>0</Enabled> Log shows: Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0> Looks like it somehow is not in KISS mode? Any suggestions would be appreciated. Thanks Bob KE6GYD --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano mailto:kb8rco@... wrote: > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED. > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed. >    KEY-> the port is opened when APRSISce/32 requests use of it >              Application start-up if configured as OPEN on last close >             Also through the menu system: >               >Enables >Ports {your KPC3 port name} > >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup) > Mine is setup with: > <OpenCmd>^M~!!0</OpenCmd> > <OpenCmd>^C~!cmd:!2</OpenCmd> > <OpenCmd>CD SOFT!cmd:!1</OpenCmd> > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> > <OpenCmd>INT KISS!cmd:!1</OpenCmd> > <OpenCmd>RESET!cmd:!3</OpenCmd> > > <CloseCmd>^192^255^192~!!0</CloseCmd> > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd> > > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup. > > Give these a try and let us know > > Robert Giuliano > KB8RCO > > > --------------------------------------------- > > > ________________________________ > From: ke6gyd mailto:ke6gyd@... > To: mailto:aprsisce%40yahoogroups.com > Sent: Thursday, August 29, 2013 10:35 AM > Subject: [aprsisce] Re: KPC3 configuration > >   > > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet. > > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated. > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this? > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available. > > Thanks > Bob > KE6GYD > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote: > > > > I TOTALLY disagree! > > > > > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you. > > > > Which you choose will determine what type of port > >    Continuous Mode - Simple KISS > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode. > > > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . . > >   > > > > Robert Giuliano > > KB8RCO > > > > > > --------------------------------------------- > > > > From: Adam Mahnke <kc2ant@> > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com> > > Sent: Tuesday, August 27, 2013 10:16 PM > > Subject: RE: [aprsisce] KPC3 configuration > > > >   > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset. > > > > http://aprsisce.wikidot.com/tnc-kpc-3 > > > > > > Adam > > KC2ANT > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration  > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD > > >
                  • Lynn W Deffenbaugh (Mr)
                    You are correct in all of your statements. Fred, I believe, was referring to something like: CD SOFT which is the same as your example
                    Message 9 of 29 , Aug 30, 2013
                    • 0 Attachment
                      You are correct in all of your statements.  Fred, I believe, was referring to something like:

                      <OpenCmd>CD SOFT</OpenCmd>

                      which is the same as your example because the default string to wait for is "cmd:" and the default wait time is 1 second.

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

                      On 8/30/2013 12:59 PM, Rob Giuliano wrote:
                      I believe a command like
                      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                       
                      means ->
                         Send command "CD SOFT"
                         YES - Look for response from TNC of "cmd:" for 1 seond
                       
                      What "field" are you talking about?  "...but look for what is in the field ..."
                      The "FIELD" between two "!" is "cmd:" -> that's what to look for.
                       
                      The cmd: is what the KPC-3 sends when in "command mode".
                         If it arrives immediately, APRSIS32 will go to the next step.
                         If it doesn't arrive in "1" second, APRSIS32 will go to the next step.
                       
                      That is how I understand it, and it seems to be how APRSIS32 is interfacing with my KPC-3.
                       
                      I can't get at my KPC-3 right now, but will change it to:
                        
                         <OpenCmd>CD SOFT!Fred!10</OpenCmd>
                      to see if it waits 10 seconds before trying the enxt command. 
                         (You REALLY are FAMOUS if my KPC-3 actually responds to your name - hihi)
                       
                      Robert Giuliano
                      KB8RCO


                      ---------------------------------------------

                      From: Fred Hillhouse <fmhillhouse@...>
                      To: aprsisce@yahoogroups.com
                      Sent: Friday, August 30, 2013 10:35 AM
                      Subject: RE: [aprsisce] Re: KPC3 configuration
                       
                      Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
                       
                      This now becomes education for me and anyone wishing to follow along.
                       
                      Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
                       
                      If I look at this line from below:
                      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                       
                      I understand this to say:
                      Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
                       
                      I think it can be rewritten and produce the same results as:
                      <OpenCmd>CD SOFT</OpenCmd>
                       
                      And one more from the XML:
                      <OpenCmd>RESET!!3</OpenCmd>
                      I understand this to say:
                      Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
                       
                       
                      Best regards,
                       
                      Fred N7FMH
                       
                       
                      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
                      Sent: Friday, August 30, 2013 09:55
                      To: aprsisce@yahoogroups.com
                      Subject: Re: [aprsisce] Re: KPC3 configuration
                       
                      Read it carefully and completely.  It says (just above the example you're referencing):
                      If you don't specify a Response (no !), "cmd:" is expected
                      Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
                      Is there something missing on this page?
                       
                      In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
                       
                      Best regards,
                      Fred N7FMH


                      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                      Sent: Thursday, August 29, 2013 21:31
                      To: aprsisce@yahoogroups.com
                      Subject: Re: [aprsisce] Re: KPC3 configuration
                       
                      From the log, it is not going into KISS mode.
                      The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                        and it looks like I had a bad "cmd:" after the reset.
                      Here is an EXACT copy of my port for my KPC-3:
                      <!--RFPort[0]-->
                      <RFPort Name="KPC3">
                      <Protocol>KISS</Protocol>
                      <Device>COM1:9600,N,8,1</Device>
                      <RfBaud>1200</RfBaud>
                      <OpenCmd>^M~!!0</OpenCmd>
                      <OpenCmd>^C~!cmd:!2</OpenCmd>
                      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                      <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                      <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                      <OpenCmd>INT KISS!!0</OpenCmd>
                      <OpenCmd>RESET!!3</OpenCmd>
                      <CloseCmd>^192^255^192~!!0</CloseCmd>
                      <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                      <QuietTime>0</QuietTime>
                      <Enabled>1</Enabled>
                      <XmitEnabled>1</XmitEnabled>
                      <ProvidesNMEA>0</ProvidesNMEA>
                      <RFtoISEnabled>1</RFtoISEnabled>
                      <IStoRFEnabled>1</IStoRFEnabled>
                      <MyCallNot3rd>0</MyCallNot3rd>
                      <BeaconingEnabled>1</BeaconingEnabled>
                      <BeaconPath>WIDE2-1</BeaconPath>
                      <BulletinObjectEnabled>1</BulletinObjectEnabled>
                      <DXEnabled>1</DXEnabled>
                      <DXPath>RFONLY</DXPath>
                      <MessagesEnabled>1</MessagesEnabled>
                      <MessagePath></MessagePath>
                      <TelemetryEnabled>0</TelemetryEnabled>
                      <TelemetryPath></TelemetryPath>
                      <!--DigiXform-->
                      </RFPort><!--RFPort[0]-->

                      If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly. If you have an issue the first time, try    >Enables >View Logs >Ports(KPC-3)    >Enables > Port >KPC-3            to close the port then again    >Enables > Port >KPC-3            to re-open the port Then check the log - post if needed Robert Giuliano KB8RCO

                      ---------------------------------------------

                      From: ke6gyd mailto:ke6gyd@...
                      To: aprsisce@yahoogroups.com
                      Sent: Thursday, August 29, 2013 8:01 PM
                      Subject: [aprsisce] Re: KPC3 configuration
                       
                      Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something? <!--RFPort[0]--> <RFPort Name="KPC-3"> <Protocol>KISS</Protocol> <Device>COM1:9600,N,8,1</Device> <RfBaud>1200</RfBaud> <OpenCmd>^M~1!!0</OpenCmd> <OpenCmd>^C~!cmd:!2</OpenCmd> <OpenCmd>CD SOFT!cmd:!1</OpenCmd> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> <OpenCmd>INT KISS!cmd:!1</OpenCmd> <OpenCmd>RESET!cmd:!3</OpenCmd> <CloseCmd>^192^255^192~!!0</CloseCmd> <CloseCmd>^C^C^C~!!0</CloseCmd> <CloseCmd>TC 1!TS 1</CloseCmd> <CloseCmd>TN 2,0!TN 2,0</CloseCmd> <QuietTime>0</QuietTime> <Enabled>0</Enabled> Log shows: Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0> Looks like it somehow is not in KISS mode? Any suggestions would be appreciated. Thanks Bob KE6GYD --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano mailto:kb8rco@... wrote: > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED. > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed. >    KEY-> the port is opened when APRSISce/32 requests use of it >              Application start-up if configured as OPEN on last close >             Also through the menu system: >               >Enables >Ports {your KPC3 port name} > >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup) > Mine is setup with: > <OpenCmd>^M~!!0</OpenCmd> > <OpenCmd>^C~!cmd:!2</OpenCmd> > <OpenCmd>CD SOFT!cmd:!1</OpenCmd> > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> > <OpenCmd>INT KISS!cmd:!1</OpenCmd> > <OpenCmd>RESET!cmd:!3</OpenCmd> > > <CloseCmd>^192^255^192~!!0</CloseCmd> > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd> > > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup. > > Give these a try and let us know > > Robert Giuliano >KB8RCO > > > --------------------------------------------- > > > ________________________________ > From: ke6gyd mailto:ke6gyd@... > To: mailto:aprsisce%40yahoogroups.com > Sent: Thursday, August 29, 2013 10:35 AM > Subject: [aprsisce] Re: KPC3 configuration > >   > > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet. > > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated. > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this? > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available. > > Thanks > Bob > KE6GYD > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote: > > > > I TOTALLY disagree! > > > > > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you. > > > > Which you choose will determine what type of port > >    Continuous Mode - Simple KISS > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode. > > > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . . > >   > > > > Robert Giuliano > > KB8RCO > > > > > > --------------------------------------------- > > > > From: Adam Mahnke <kc2ant@> > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com> > > Sent: Tuesday, August 27, 2013 10:16 PM > > Subject: RE: [aprsisce] KPC3 configuration > > > >   > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset. > > > > http://aprsisce.wikidot.com/tnc-kpc-3 > > > > > > Adam > > KC2ANT > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration  > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD > > >

                    • Lynn W Deffenbaugh (Mr)
                      This was NOT a GPS pass-through, it just happened to be a raw GPS sentence formatted as an APRS packet from W6CSP-1. Check his raw packets at
                      Message 10 of 29 , Aug 30, 2013
                      • 0 Attachment
                        This was NOT a GPS pass-through, it just happened to be a raw GPS sentence formatted as an APRS packet from W6CSP-1.  Check his raw packets at http://aprs.fi/?c=raw&call=W6CSP-1&limit=5&view=hex and you'll see that the NMEA is just the APRS payload, not from any GPS connected to the KPC.

                        It's just that the KISS wrapper of that received AX.25 packet is missing the first byte after the <C0> which says that it's a data packet from the TNC to the PC.  And APRSISCE/32 therefore rejects the packet because if the data type isn't there, then what is the remainder of the packet?

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

                        On 8/30/2013 12:36 PM, Rob Giuliano wrote:
                        I can't say I really looked at the packet before.
                        Is this a GPS pass-through?
                           If it is, this must be the KPC-3+ as my KPC-3 doesn't have the capability of 2 serial inputs (GPS and computer).
                         
                         
                        Robert Giuliano
                        KB8RCO


                        ---------------------------------------------

                        From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                        To: aprsisce@yahoogroups.com
                        Sent: Friday, August 30, 2013 9:51 AM
                        Subject: Re: [aprsisce] Re: KPC3 configuration

                        Actually, it IS going into KISS mode or you wouldn't be seeing the <C0>
                        stuff. That's the KISS packet wrapper. The issue is that APRSISCE/32 is
                        expecting a command 0 (low nibble) in the first byte of the KISS packet,
                        but your packet has 8E or command 14. I need to look that up, but here's
                        the interpretation of the packet from your log (I assume you get one of
                        these for every packet received?).

                        <C0    - Packet framing character
                        8E    - Type indicator - but this seems to be missing in your packet!
                        8E A0 A6 98 96>@`    - Destination callsign (GPSLK )
                        <AE>l<86 A6 A0>@b    - Source callsign (W6CSP -1)
                        <9C>l<8A B0>@@<E3    - Path component (N6EX  -1) used (high bit) & last component (low bit)
                        03 F0>            - AX.25 protocol and flags (IIRC)
                        $GPGGA,051524,3350.5768,N,11755.8527,W,1,08,1.2,37.2,M,-31.9,M,,*4A    - Packet payload!
                        <0D 0A    - Don't know why he's including the <cr><lf>, but it's in the packet! - See below...
                        C0>    - Packet framing character
                         

                        The byte immediately following the opening <C0> is SUPPOSED to be a
                        command byte whose upper bit (8x) indicates a SMACK packet, the next 3
                        bits are the port number, and the lower nibble (4 bits) is the command
                        which APRSISCE/32 expects to be 0 and is causing the packet to be
                        rejected. However, your packet seems to be missing this byte because the
                        <8E> that was there appears to be the first character (G) of the
                        destination callsign. For the KISS spec, please see
                        http://www.ax25.net/kiss.aspxwhich states at the end of section 4:

                        > The following types are defined in frames to the host:
                        >
                        > Type            Function        Comments
                        >     
                        >    0                Data frame      Rest of frame is data from
                        >                                      the HDLC channel.

                        The destination, source, and path callsigns are bit-shifted ASCII and
                        the -SSIDs are encoded in 4 bits of binary along with some flags (hence
                        the 0-15 limit on AX.25 compatible -SSIDs). This is the AX.25 packet
                        header being carried in the KISS data frame.

                        The packet payload is a raw $GPGGA string that correlates to what
                        aprs.fi shows for W6CSP-1
                        (http://aprs.fi/?c=raw&call=W6CSP-1&limit=5&view=hex). Interestingly
                        though, the <CR><LF> aren't in those raw packets, but then they weren't
                        digipeated by N6EX-1 either, but received directly by the BOXSPG IGate
                        with the original WIDE2-2 path intact. N6EX-1 seems to have replaced the
                        path with his own used callsign and apparently appended a <CR><LF> to
                        the packet unless that was done by your TNC.

                        Question: if you receive other packets in this trace log, do they all
                        end with <0D 0A C0>? This may be another bust (IMHO) in your TNC's KISS
                        implementation.

                        Bottom line: while this appears to be a KISS packet, it's not a proper
                        KISS packet, at least not for what I've read in the KISS specs.

                        Does anyone else out there have one of these TNCs connected to
                        APRSISCE/32 in KISS mode and what are you seeing in your port's trace
                        log if you enable it?

                        And Bob, if you Enable this trace log, do you see any packets coming
                        through cleanly or are they all complaining about the "Missing 0"?

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

                        On 8/30/2013 1:19 AM, ke6gyd wrote:
                        > Really appreciate your help.  Still not going into KISS mode:
                        >
                        > Port(KPC3):2013-08-30T05:15:29.953 KISS:Missing 0, found C0[94]:<C0 8E A0 A6 98 96>@`<AE>l<86 A6 A0>@b<9C>l<8A B0>@@<E3 03 F0>$GPGGA,051524,3350.5768,N,11755.8527,W,1,08,1.2,37.2,M,-31.9,M,,*4A<0D 0A C0>
                        >
                        > Copied and pasted exactly your settings into the .xml file.
                        >
                        > If any other advice, let me know.  We'll keep trying.
                        > Thanks
                        > Bob
                        > KE6GYD
                        >
                        > --- In aprsisce@yahoogroups.com, Rob Giuliano <kb8rco@...> wrote:
                        >>  From the log, it is not going into KISS mode.
                        >> The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                        >>   and it looks like I had a bad "cmd:" after the reset.
                        >>
                        >>
                        >> Here is an EXACT copy of my port for my KPC-3:
                        >> <!--RFPort[0]-->
                        >>
                        >> <RFPort Name="KPC3">
                        >> <Protocol>KISS</Protocol>
                        >> <Device>COM1:9600,N,8,1</Device>
                        >> <RfBaud>1200</RfBaud>
                        >> <OpenCmd>^M~!!0</OpenCmd>
                        >> <OpenCmd>^C~!cmd:!2</OpenCmd>
                        >> <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                        >> <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                        >> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                        >> <OpenCmd>INT KISS!!0</OpenCmd>
                        >> <OpenCmd>RESET!!3</OpenCmd>
                        >> <CloseCmd>^192^255^192~!!0</CloseCmd>
                        >> <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                        >> <QuietTime>0</QuietTime>
                        >> <Enabled>1</Enabled>
                        >> <XmitEnabled>1</XmitEnabled>
                        >> <ProvidesNMEA>0</ProvidesNMEA>
                        >> <RFtoISEnabled>1</RFtoISEnabled>
                        >> <IStoRFEnabled>1</IStoRFEnabled>
                        >> <MyCallNot3rd>0</MyCallNot3rd>
                        >> <BeaconingEnabled>1</BeaconingEnabled>
                        >> <BeaconPath>WIDE2-1</BeaconPath>
                        >> <BulletinObjectEnabled>1</BulletinObjectEnabled>
                        >> <DXEnabled>1</DXEnabled>
                        >> <DXPath>RFONLY</DXPath>
                        >> <MessagesEnabled>1</MessagesEnabled>
                        >> <MessagePath></MessagePath>
                        >> <TelemetryEnabled>0</TelemetryEnabled>
                        >> <TelemetryPath></TelemetryPath>
                        >> <!--DigiXform-->
                        >> </RFPort>
                        >> <!--RFPort[0]-->
                        >>
                        >>
                        >> If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly.
                        >> If you have an issue the first time, try
                        >>    >Enables >View Logs >Ports(KPC-3)
                        >>    >Enables > Port >KPC-3            to close the port
                        >> then again
                        >>    >Enables > Port >KPC-3            to re-open the port
                        >>
                        >> Then check the log - post if needed
                        >> Robert Giuliano
                        >> KB8RCO
                        >>
                        >>
                        >> ---------------------------------------------
                        >>
                        >> From: ke6gyd <ke6gyd@...>
                        >> To: aprsisce@yahoogroups.com
                        >> Sent: Thursday, August 29, 2013 8:01 PM
                        >> Subject: [aprsisce] Re: KPC3 configuration
                        >>
                        >> Â
                        >> Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something?
                        >>
                        >> <!--RFPort[0]-->
                        >> <RFPort Name="KPC-3">
                        >> <Protocol>KISS</Protocol>
                        >> <Device>COM1:9600,N,8,1</Device>
                        >> <RfBaud>1200</RfBaud>
                        >> <OpenCmd>^M~1!!0</OpenCmd>
                        >> <OpenCmd>^C~!cmd:!2</OpenCmd>
                        >> <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                        >> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd>
                        >> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                        >> <OpenCmd>INT KISS!cmd:!1</OpenCmd>
                        >> <OpenCmd>RESET!cmd:!3</OpenCmd>
                        >> <CloseCmd>^192^255^192~!!0</CloseCmd>
                        >> <CloseCmd>^C^C^C~!!0</CloseCmd>
                        >> <CloseCmd>TC 1!TS
                        >>  1</CloseCmd>
                        >> <CloseCmd>TN 2,0!TN 2,0</CloseCmd>
                        >> <QuietTime>0</QuietTime>
                        >> <Enabled>0</Enabled>
                        >>
                        >> Log shows:
                        >> Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0>
                        >>
                        >> Looks like it somehow is not in KISS mode?
                        >>
                        >> Any suggestions would be appreciated.
                        >> Thanks
                        >> Bob
                        >> KE6GYD
                        >>
                        >> --- In aprsisce@yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
                        >>> APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED.
                        >>> These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened,
                        >>  and to
                        >>  tell the KPC-3 to return to its standard mode when the port is closed.
                        >>>    KEY-> the port is opened when APRSISce/32 requests use of it
                        >>>              Application start-up if configured as OPEN on last close
                        >>>             Also through the menu system:
                        >>>               >Enables >Ports {your KPC3 port name}
                        >>>
                        >>>  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup)
                        >>> Mine is setup with:
                        >>> <OpenCmd>^M~!!0</OpenCmd>
                        >>> <OpenCmd>^C~!cmd:!2</OpenCmd>
                        >>> <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                        >>> <OpenCmd>XFLOW
                        >>  ON!cmd:!1</OpenCmd>
                        >>> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                        >>> <OpenCmd>INT KISS!cmd:!1</OpenCmd>
                        >>> <OpenCmd>RESET!cmd:!3</OpenCmd>
                        >>>
                        >>> <CloseCmd>^192^255^192~!!0</CloseCmd>
                        >>> <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd>
                        >>>
                        >>> The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup.
                        >>>
                        >>> Give these a try and let us know
                        >>>
                        >>> Robert Giuliano
                        >>> KB8RCO
                        >>>
                        >>>
                        >>> ---------------------------------------------
                        >>>
                        >>>
                        >>> ________________________________
                        >>> From: ke6gyd <ke6gyd@>
                        >>> To: aprsisce@yahoogroups.com
                        >>> Sent: Thursday, August 29, 2013 10:35 AM
                        >>> Subject:
                        >>  [aprsisce]
                        >>  Re: KPC3 configuration
                        >>> ÂÂ
                        >>>
                        >>> I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet.
                        >>>
                        >>> What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated.
                        >>>
                        >>> Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this?
                        >>>
                        >>> BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available.
                        >>>
                        >>> Thanks
                        >>> Bob
                        >>> KE6GYD
                        >>>
                        >>> --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote:
                        >>>> I TOTALLY disagree!
                        >>>>
                        >>>>
                        >>>> I agree that the best mode is KISS, but
                        >>  whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you.
                        >>>> Which you choose will determine what type of port
                        >>>>    Continuous Mode - Simple KISS
                        >>>>    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode.
                        >>>>
                        >>>> I use the KPC-3, all the time (KB8RCO).  Not the Plus . . .
                        >>>> ÂÂÂ
                        >>>>
                        >>>> Robert Giuliano
                        >>>> KB8RCO
                        >>>>
                        >>>>
                        >>>> ---------------------------------------------
                        >>>>
                        >>>> From: Adam Mahnke <kc2ant@>
                        >>>> To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com>
                        >>>> Sent: Tuesday,
                        >>  August 27, 2013 10:16 PM
                        >>>> Subject: RE: [aprsisce] KPC3 configuration
                        >>>>
                        >>>> ÂÂÂ
                        >>>> As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset.
                        >>>>
                        >>>> http://aprsisce.wikidot.com/tnc-kpc-3
                        >>>>
                        >>>>
                        >>>> Adam
                        >>>> KC2ANT
                        >>>> To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configurationÂÂÂ
                        >>>> I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using
                        >>  a
                        >>  USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD
                        >
                        >
                        >
                        > ------------------------------------
                        >
                        > Yahoo! Groups Links
                        >
                        >
                        >
                        >



                        ------------------------------------

                        Yahoo! Groups Links

                        <*> To visit your group on the web, go to:
                            http://groups.yahoo.com/group/aprsisce/

                        <*> Your email settings:
                            Individual Email | Traditional

                        <*> To change settings online go to:
                            http://groups.yahoo.com/group/aprsisce/join
                            (Yahoo! ID required)

                        <*> To change settings via email:
                            aprsisce-digest@yahoogroups.com
                            aprsisce-fullfeatured@yahoogroups.com

                        <*> To unsubscribe from this group, send an email to:
                            aprsisce-unsubscribe@yahoogroups.com

                        <*> Your use of Yahoo! Groups is subject to:
                            http://docs.yahoo.com/info/terms/




                      • Fred Hillhouse
                        I think you missed what I was saying. If cmd: is expected, and a 1 second delay is normal without adding anymore information to the string, then, adding more
                        Message 11 of 29 , Aug 30, 2013
                        • 0 Attachment
                          I think you missed what I was saying. If "cmd:" is expected, and a 1 second delay is normal without adding anymore information to the string, then, adding more text to define the same thing it isn't needed.
                           
                          From the WIKI:
                          If you don't specify a Response (no !), "cmd:" is expected.
                          If you don't specify a Delay (only one !), 1 second is assumed.
                           
                          As I understand it, adding "!cmd:!1" is redundant but it does make it plain what is going on.
                           
                          If I was to re-write this example from the WIKI:
                          <OpenCmd>KISS ON</OpenCmd> <!— Transmit "KISS ON<cr>", Wait for "cmd:", for 1 second max — >
                           
                          I could add between "ON" and "<", "!cmd:!1" and achieve the same thing. Again, this is my point.
                          <OpenCmd>KISS ON!cmd:!1</OpenCmd> which equals <OpenCmd>KISS ON</OpenCmd>
                           
                          Looking back at the original TNC OpenCmd entry in the XML:
                          <OpenCmd>CD SOFT!cmd:!1</OpenCmd> which is the same as <OpenCmd>CD SOFT</OpenCmd>
                           
                           
                          When I mentioned field, it was in reference to the space that could be used for a "wait for string".
                           
                          If an open command (OpenCmd) is sent, then the default data for the 2 fields are "cmd:" and "1". Each field needs a "!" in front of it.
                           
                          There is a special case of a non-default delay and still expecting a default response. The response, even though it is default, must be re-stated.
                           
                          These are a few examples:
                           
                          Normal, waits for cmd: for up to 1 second (default):
                          <OpenCmd>KISS ON</OpenCmd>
                           
                          Same as Normal, just entered more explicitly:
                          <OpenCmd>KISS ON!cmd:!1</OpenCmd>
                           
                          Expecting a non-default response and a default delay:
                          <OpenCmd>KISS ON!Robert</OpenCmd>
                           
                          Expecting a non-default response and a non-default delay:
                          <OpenCmd>KISS ON!Robert!2</OpenCmd>
                           
                          Expecting default response (re-stated) and with a non-default delay:
                          <OpenCmd>KISS ON!cmd:!2</OpenCmd>
                           
                          Not expecting a response and with a non-default delay:
                          <OpenCmd>KISS ON!!2</OpenCmd>
                           
                          As I said previously, I am trying to get edumacated and this is how I currently understand it.
                           
                          And, yes I am famous but not REALLY famous. :)
                           
                           
                          Best regards,
                          Fred N7FMH
                           


                          From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                          Sent: Friday, August 30, 2013 12:59
                          To: aprsisce@yahoogroups.com
                          Subject: Re: [aprsisce] Re: KPC3 configuration

                           

                          I believe a command like
                          <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                           
                          means ->
                             Send command "CD SOFT"
                             YES - Look for response from TNC of "cmd:" for 1 seond
                           
                          What "field" are you talking about?  "...but look for what is in the field ..."
                          The "FIELD" between two "!" is "cmd:" -> that's what to look for.
                           
                          The cmd: is what the KPC-3 sends when in "command mode".
                             If it arrives immediately, APRSIS32 will go to the next step.
                             If it doesn't arrive in "1" second, APRSIS32 will go to the next step.
                           
                          That is how I understand it, and it seems to be how APRSIS32 is interfacing with my KPC-3.
                           
                          I can't get at my KPC-3 right now, but will change it to:
                            
                             <OpenCmd>CD SOFT!Fred!10</OpenCmd>
                          to see if it waits 10 seconds before trying the enxt command. 
                             (You REALLY are FAMOUS if my KPC-3 actually responds to your name - hihi)
                           
                          Robert Giuliano
                          KB8RCO


                          ---------------------------------------------

                          From: Fred Hillhouse <fmhillhouse@...>
                          To: aprsisce@yahoogroups.com
                          Sent: Friday, August 30, 2013 10:35 AM
                          Subject: RE: [aprsisce] Re: KPC3 configuration
                           
                          Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
                           
                          This now becomes education for me and anyone wishing to follow along.
                           
                          Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
                           
                          If I look at this line from below:
                          <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                           
                          I understand this to say:
                          Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
                           
                          I think it can be rewritten and produce the same results as:
                          <OpenCmd>CD SOFT</OpenCmd>
                           
                          And one more from the XML:
                          <OpenCmd>RESET!!3</OpenCmd>
                          I understand this to say:
                          Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
                           
                           
                          Best regards,
                           
                          Fred N7FMH
                           
                           
                          From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
                          Sent: Friday, August 30, 2013 09:55
                          To: aprsisce@yahoogroups.com
                          Subject: Re: [aprsisce] Re: KPC3 configuration
                           
                          Read it carefully and completely.  It says (just above the example you're referencing):
                          If you don't specify a Response (no !), "cmd:" is expected
                          Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
                          Is there something missing on this page?
                           
                          In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
                           
                          Best regards,
                          Fred N7FMH


                          From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                          Sent: Thursday, August 29, 2013 21:31
                          To: aprsisce@yahoogroups.com
                          Subject: Re: [aprsisce] Re: KPC3 configuration
                           
                          From the log, it is not going into KISS mode.
                          The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                            and it looks like I had a bad "cmd:" after the reset.
                          Here is an EXACT copy of my port for my KPC-3:
                          <!--RFPort[0]-->
                          <RFPort Name="KPC3">
                          <Protocol>KISS</Protocol>
                          <Device>COM1:9600,N,8,1</Device>
                          <RfBaud>1200</RfBaud>
                          <OpenCmd>^M~!!0</OpenCmd>
                          <OpenCmd>^C~!cmd:!2</OpenCmd>
                          <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                          <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                          <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                          <OpenCmd>INT KISS!!0</OpenCmd>
                          <OpenCmd>RESET!!3</OpenCmd>
                          <CloseCmd>^192^255^192~!!0</CloseCmd>
                          <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                          <QuietTime>0</QuietTime>
                          <Enabled>1</Enabled>
                          <XmitEnabled>1</XmitEnabled>
                          <ProvidesNMEA>0</ProvidesNMEA>
                          <RFtoISEnabled>1</RFtoISEnabled>
                          <IStoRFEnabled>1</IStoRFEnabled>
                          <MyCallNot3rd>0</MyCallNot3rd>
                          <BeaconingEnabled>1</BeaconingEnabled>
                          <BeaconPath>WIDE2-1</BeaconPath>
                          <BulletinObjectEnabled>1</BulletinObjectEnabled>
                          <DXEnabled>1</DXEnabled>
                          <DXPath>RFONLY</DXPath>
                          <MessagesEnabled>1</MessagesEnabled>
                          <MessagePath></MessagePath>
                          <TelemetryEnabled>0</TelemetryEnabled>
                          <TelemetryPath></TelemetryPath>
                          <!--DigiXform-->
                          </RFPort><!--RFPort[0]-->

                          If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly. If you have an issue the first time, try    >Enables >View Logs >Ports(KPC-3)    >Enables > Port >KPC-3            to close the port then again    >Enables > Port >KPC-3            to re-open the port Then check the log - post if needed Robert Giuliano KB8RCO

                          ---------------------------------------------

                          From: ke6gyd mailto:ke6gyd@...
                          To: aprsisce@yahoogroups.com
                          Sent: Thursday, August 29, 2013 8:01 PM
                          Subject: [aprsisce] Re: KPC3 configuration
                           
                          Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something? <!--RFPort[0]--> <RFPort Name="KPC-3"> <Protocol>KISS</Protocol> <Device>COM1:9600,N,8,1</Device> <RfBaud>1200</RfBaud> <OpenCmd>^M~1!!0</OpenCmd> <OpenCmd>^C~!cmd:!2</OpenCmd> <OpenCmd>CD SOFT!cmd:!1</OpenCmd> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> <OpenCmd>INT KISS!cmd:!1</OpenCmd> <OpenCmd>RESET!cmd:!3</OpenCmd> <CloseCmd>^192^255^192~!!0</CloseCmd> <CloseCmd>^C^C^C~!!0</CloseCmd> <CloseCmd>TC 1!TS 1</CloseCmd> <CloseCmd>TN 2,0!TN 2,0</CloseCmd> <QuietTime>0</QuietTime> <Enabled>0</Enabled> Log shows: Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0> Looks like it somehow is not in KISS mode? Any suggestions would be appreciated. Thanks Bob KE6GYD --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano mailto:kb8rco@... wrote: > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED. > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed. >    KEY-> the port is opened when APRSISce/32 requests use of it >              Application start-up if configured as OPEN on last close >             Also through the menu system: >               >Enables >Ports {your KPC3 port name} > >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup) > Mine is setup with: > <OpenCmd>^M~!!0</OpenCmd> > <OpenCmd>^C~!cmd:!2</OpenCmd> > <OpenCmd>CD SOFT!cmd:!1</OpenCmd> > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> > <OpenCmd>INT KISS!cmd:!1</OpenCmd> > <OpenCmd>RESET!cmd:!3</OpenCmd> > > <CloseCmd>^192^255^192~!!0</CloseCmd> > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd> > > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup. > > Give these a try and let us know > > Robert Giuliano > KB8RCO > > > --------------------------------------------- > > > ________________________________ > From: ke6gyd mailto:ke6gyd@... > To: mailto:aprsisce%40yahoogroups.com > Sent: Thursday, August 29, 2013 10:35 AM > Subject: [aprsisce] Re: KPC3 configuration > >   > > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet. > > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated. > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this? > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available. > > Thanks > Bob > KE6GYD > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote: > > > > I TOTALLY disagree! > > > > > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you. > > > > Which you choose will determine what type of port > >    Continuous Mode - Simple KISS > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode. > > > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . . > >   > > > > Robert Giuliano > > KB8RCO > > > > > > --------------------------------------------- > > > > From: Adam Mahnke <kc2ant@> > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com> > > Sent: Tuesday, August 27, 2013 10:16 PM > > Subject: RE: [aprsisce] KPC3 configuration > > > >   > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset. > > > > http://aprsisce.wikidot.com/tnc-kpc-3 > > > > > > Adam > > KC2ANT > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration  > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD > > >

                        • Rob Giuliano
                          Missed the Default = 1 second part. Boy reading along and participating sure helps learn new things! Robert Giuliano KB8RCO ...
                          Message 12 of 29 , Aug 30, 2013
                          • 0 Attachment
                            Missed the "Default = 1 second" part.
                             
                            Boy reading along and participating sure helps learn new things!
                             
                            Robert Giuliano
                            KB8RCO


                            ---------------------------------------------

                            From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                            To: aprsisce@yahoogroups.com
                            Sent: Friday, August 30, 2013 1:48 PM
                            Subject: Re: [aprsisce] Re: KPC3 configuration
                             
                            You are correct in all of your statements.  Fred, I believe, was referring to something like: <OpenCmd>CD SOFT</OpenCmd> which is the same as your example because the default string to wait for is "cmd:" and the default wait time is 1 second. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 12:59 PM, Rob Giuliano wrote:
                            I believe a command like
                            <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                             
                            means ->
                               Send command "CD SOFT"
                               YES - Look for response from TNC of "cmd:" for 1 seond
                             
                            What "field" are you talking about?  "...but look for what is in the field ..."
                            The "FIELD" between two "!" is "cmd:" -> that's what to look for.
                             
                            The cmd: is what the KPC-3 sends when in "command mode".
                               If it arrives immediately, APRSIS32 will go to the next step.
                               If it doesn't arrive in "1" second, APRSIS32 will go to the next step.
                             
                            That is how I understand it, and it seems to be how APRSIS32 is interfacing with my KPC-3.
                             
                            I can't get at my KPC-3 right now, but will change it to:
                              
                               <OpenCmd>CD SOFT!Fred!10</OpenCmd>
                            to see if it waits 10 seconds before trying the enxt command. 
                               (You REALLY are FAMOUS if my KPC-3 actually responds to your name - hihi)
                             
                            Robert Giuliano
                            KB8RCO

                            ---------------------------------------------
                            From: Fred Hillhouse mailto:fmhillhouse@...
                            To: aprsisce@yahoogroups.com
                            Sent: Friday, August 30, 2013 10:35 AM
                            Subject: RE: [aprsisce] Re: KPC3 configuration
                             
                            Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
                             
                            This now becomes education for me and anyone wishing to follow along.
                             
                            Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
                             
                            If I look at this line from below:
                            <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                             
                            I understand this to say:
                            Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
                             
                            I think it can be rewritten and produce the same results as:
                            <OpenCmd>CD SOFT</OpenCmd>
                             
                            And one more from the XML:
                            <OpenCmd>RESET!!3</OpenCmd>
                            I understand this to say:
                            Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
                             
                             
                            Best regards,
                             
                            Fred N7FMH
                             
                             
                            From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
                            Sent: Friday, August 30, 2013 09:55
                            To: aprsisce@yahoogroups.com
                            Subject: Re: [aprsisce] Re: KPC3 configuration
                             
                            Read it carefully and completely.  It says (just above the example you're referencing):
                            If you don't specify a Response (no !), "cmd:" is expected
                            Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
                            Is there something missing on this page?
                             
                            In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
                             
                            Best regards,
                            Fred N7FMH


                            From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                            Sent: Thursday, August 29, 2013 21:31
                            To: aprsisce@yahoogroups.com
                            Subject: Re: [aprsisce] Re: KPC3 configuration
                             
                            From the log, it is not going into KISS mode.
                            The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                              and it looks like I had a bad "cmd:" after the reset.
                            Here is an EXACT copy of my port for my KPC-3:
                            <!--RFPort[0]-->
                            <RFPort Name="KPC3">
                            <Protocol>KISS</Protocol>
                            <Device>COM1:9600,N,8,1</Device>
                            <RfBaud>1200</RfBaud>
                            <OpenCmd>^M~!!0</OpenCmd>
                            <OpenCmd>^C~!cmd:!2</OpenCmd>
                            <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                            <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                            <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                            <OpenCmd>INT KISS!!0</OpenCmd>
                            <OpenCmd>RESET!!3</OpenCmd>
                            <CloseCmd>^192^255^192~!!0</CloseCmd>
                            <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                            <QuietTime>0</QuietTime>
                            <Enabled>1</Enabled>
                            <XmitEnabled>1</XmitEnabled>
                            <ProvidesNMEA>0</ProvidesNMEA>
                            <RFtoISEnabled>1</RFtoISEnabled>
                            <IStoRFEnabled>1</IStoRFEnabled>
                            <MyCallNot3rd>0</MyCallNot3rd>
                            <BeaconingEnabled>1</BeaconingEnabled>
                            <BeaconPath>WIDE2-1</BeaconPath>
                            <BulletinObjectEnabled>1</BulletinObjectEnabled>
                            <DXEnabled>1</DXEnabled>
                            <DXPath>RFONLY</DXPath>
                            <MessagesEnabled>1</MessagesEnabled>
                            <MessagePath></MessagePath>
                            <TelemetryEnabled>0</TelemetryEnabled>
                            <TelemetryPath></TelemetryPath>
                            <!--DigiXform-->
                            </RFPort><!--RFPort[0]-->

                            If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly. If you have an issue the first time, try    >Enables >View Logs >Ports(KPC-3)    >Enables > Port >KPC-3            to close the port then again    >Enables > Port >KPC-3            to re-open the port Then check the log - post if needed Robert Giuliano KB8RCO

                            ---------------------------------------------

                            From: ke6gyd mailto:ke6gyd@...
                            To: aprsisce@yahoogroups.com
                            Sent: Thursday, August 29, 2013 8:01 PM
                            Subject: [aprsisce] Re: KPC3 configuration
                             
                            Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something? <!--RFPort[0]--> <RFPort Name="KPC-3"> <Protocol>KISS</Protocol> <Device>COM1:9600,N,8,1</Device> <RfBaud>1200</RfBaud> <OpenCmd>^M~1!!0</OpenCmd> <OpenCmd>^C~!cmd:!2</OpenCmd> <OpenCmd>CD SOFT!cmd:!1</OpenCmd> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> <OpenCmd>INT KISS!cmd:!1</OpenCmd> <OpenCmd>RESET!cmd:!3</OpenCmd> <CloseCmd>^192^255^192~!!0</CloseCmd> <CloseCmd>^C^C^C~!!0</CloseCmd> <CloseCmd>TC 1!TS 1</CloseCmd> <CloseCmd>TN 2,0!TN 2,0</CloseCmd> <QuietTime>0</QuietTime> <Enabled>0</Enabled> Log shows: Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0> Looks like it somehow is not in KISS mode? Any suggestions would be appreciated. Thanks Bob KE6GYD --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano mailto:kb8rco@... wrote: > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED. > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed. >    KEY-> the port is opened when APRSISce/32 requests use of it >              Application start-up if configured as OPEN on last close >             Also through the menu system: >               >Enables >Ports {your KPC3 port name} > >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup) > Mine is setup with: > <OpenCmd>^M~!!0</OpenCmd> > <OpenCmd>^C~!cmd:!2</OpenCmd> > <OpenCmd>CD SOFT!cmd:!1</OpenCmd> > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> > <OpenCmd>INT KISS!cmd:!1</OpenCmd> > <OpenCmd>RESET!cmd:!3</OpenCmd> > > <CloseCmd>^192^255^192~!!0</CloseCmd> > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd> > > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup. > > Give these a try and let us know > > Robert Giuliano > KB8RCO > > > --------------------------------------------- > > > ________________________________ > From: ke6gyd mailto:ke6gyd@... > To: mailto:aprsisce%40yahoogroups.com > Sent: Thursday, August 29, 2013 10:35 AM > Subject: [aprsisce] Re: KPC3 configuration > >   > > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet. > > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated. > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this? > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available. > > Thanks > Bob > KE6GYD > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote: > > > > I TOTALLY disagree! > > > > > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you. > > > > Which you choose will determine what type of port > >    Continuous Mode - Simple KISS > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode. > > > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . . > >   > > > > Robert Giuliano > > KB8RCO > > > > > > --------------------------------------------- > > > > From: Adam Mahnke <kc2ant@> > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com> > > Sent: Tuesday, August 27, 2013 10:16 PM > > Subject: RE: [aprsisce] KPC3 configuration > > > >   > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset. > > > > http://aprsisce.wikidot.com/tnc-kpc-3 > > > > > > Adam > > KC2ANT > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration  > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD > > >
                          • Rob Giuliano
                            Yep!   Lynn straightened me out as well! Robert Giuliano KB8RCO ... ________________________________ From: Fred Hillhouse To:
                            Message 13 of 29 , Aug 30, 2013
                            • 0 Attachment
                              Yep!
                                Lynn straightened me out as well!
                               
                              Robert Giuliano
                              KB8RCO


                              ---------------------------------------------

                              From: Fred Hillhouse <fmhillhouse@...>
                              To: aprsisce@yahoogroups.com
                              Sent: Friday, August 30, 2013 2:02 PM
                              Subject: RE: [aprsisce] Re: KPC3 configuration
                               
                              I think you missed what I was saying. If "cmd:" is expected, and a 1 second delay is normal without adding anymore information to the string, then, adding more text to define the same thing it isn't needed.
                               
                              From the WIKI:
                              If you don't specify a Response (no !), "cmd:" is expected.
                              If you don't specify a Delay (only one !), 1 second is assumed.
                               
                              As I understand it, adding "!cmd:!1" is redundant but it does make it plain what is going on.
                               
                              If I was to re-write this example from the WIKI:
                              <OpenCmd>KISS ON</OpenCmd> <!— Transmit "KISS ON<cr>", Wait for "cmd:", for 1 second max — >
                               
                              I could add between "ON" and "<", "!cmd:!1" and achieve the same thing. Again, this is my point.
                              <OpenCmd>KISS ON!cmd:!1</OpenCmd> which equals <OpenCmd>KISS ON</OpenCmd>
                               
                              Looking back at the original TNC OpenCmd entry in the XML:
                              <OpenCmd>CD SOFT!cmd:!1</OpenCmd> which is the same as <OpenCmd>CD SOFT</OpenCmd>
                               
                               
                              When I mentioned field, it was in reference to the space that could be used for a "wait for string".
                               
                              If an open command (OpenCmd) is sent, then the default data for the 2 fields are "cmd:" and "1". Each field needs a "!" in front of it.
                               
                              There is a special case of a non-default delay and still expecting a default response. The response, even though it is default, must be re-stated.
                               
                              These are a few examples:
                               
                              Normal, waits for cmd: for up to 1 second (default):
                              <OpenCmd>KISS ON</OpenCmd>
                               
                              Same as Normal, just entered more explicitly:
                              <OpenCmd>KISS ON!cmd:!1</OpenCmd>
                               
                              Expecting a non-default response and a default delay:
                              <OpenCmd>KISS ON!Robert</OpenCmd>
                               
                              Expecting a non-default response and a non-default delay:
                              <OpenCmd>KISS ON!Robert!2</OpenCmd>
                               
                              Expecting default response (re-stated) and with a non-default delay:
                              <OpenCmd>KISS ON!cmd:!2</OpenCmd>
                               
                              Not expecting a response and with a non-default delay:
                              <OpenCmd>KISS ON!!2</OpenCmd>
                               
                              As I said previously, I am trying to get edumacated and this is how I currently understand it.
                               
                              And, yes I am famous but not REALLY famous. :)
                               
                               
                              Best regards,
                              Fred N7FMH
                               
                              From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                              Sent: Friday, August 30, 2013 12:59
                              To: aprsisce@yahoogroups.com
                              Subject: Re: [aprsisce] Re: KPC3 configuration
                               
                              I believe a command like
                              <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                               
                              means ->
                                 Send command "CD SOFT"
                                 YES - Look for response from TNC of "cmd:" for 1 seond
                               
                              What "field" are you talking about?  "...but look for what is in the field ..."
                              The "FIELD" between two "!" is "cmd:" -> that's what to look for.
                               
                              The cmd: is what the KPC-3 sends when in "command mode".
                                 If it arrives immediately, APRSIS32 will go to the next step.
                                 If it doesn't arrive in "1" second, APRSIS32 will go to the next step.
                               
                              That is how I understand it, and it seems to be how APRSIS32 is interfacing with my KPC-3.
                               
                              I can't get at my KPC-3 right now, but will change it to:
                                
                                 <OpenCmd>CD SOFT!Fred!10</OpenCmd>
                              to see if it waits 10 seconds before trying the enxt command. 
                                 (You REALLY are FAMOUS if my KPC-3 actually responds to your name - hihi)
                               
                              Robert Giuliano
                              KB8RCO

                              ---------------------------------------------
                              From: Fred Hillhouse <fmhillhouse@...>
                              To: aprsisce@yahoogroups.com
                              Sent: Friday, August 30, 2013 10:35 AM
                              Subject: RE: [aprsisce] Re: KPC3 configuration
                               
                              Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
                               
                              This now becomes education for me and anyone wishing to follow along.
                               
                              Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
                               
                              If I look at this line from below:
                              <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                               
                              I understand this to say:
                              Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
                               
                              I think it can be rewritten and produce the same results as:
                              <OpenCmd>CD SOFT</OpenCmd>
                               
                              And one more from the XML:
                              <OpenCmd>RESET!!3</OpenCmd>
                              I understand this to say:
                              Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
                               
                               
                              Best regards,
                               
                              Fred N7FMH
                               
                               
                              From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
                              Sent: Friday, August 30, 2013 09:55
                              To: aprsisce@yahoogroups.com
                              Subject: Re: [aprsisce] Re: KPC3 configuration
                               
                              Read it carefully and completely.  It says (just above the example you're referencing):
                              If you don't specify a Response (no !), "cmd:" is expected
                              Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
                              Is there something missing on this page?
                               
                              In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
                               
                              Best regards,
                              Fred N7FMH


                              From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                              Sent: Thursday, August 29, 2013 21:31
                              To: aprsisce@yahoogroups.com
                              Subject: Re: [aprsisce] Re: KPC3 configuration
                               
                              From the log, it is not going into KISS mode.
                              The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                                and it looks like I had a bad "cmd:" after the reset.
                              Here is an EXACT copy of my port for my KPC-3:
                              <!--RFPort[0]-->
                              <RFPort Name="KPC3">
                              <Protocol>KISS</Protocol>
                              <Device>COM1:9600,N,8,1</Device>
                              <RfBaud>1200</RfBaud>
                              <OpenCmd>^M~!!0</OpenCmd>
                              <OpenCmd>^C~!cmd:!2</OpenCmd>
                              <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                              <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                              <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                              <OpenCmd>INT KISS!!0</OpenCmd>
                              <OpenCmd>RESET!!3</OpenCmd>
                              <CloseCmd>^192^255^192~!!0</CloseCmd>
                              <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                              <QuietTime>0</QuietTime>
                              <Enabled>1</Enabled>
                              <XmitEnabled>1</XmitEnabled>
                              <ProvidesNMEA>0</ProvidesNMEA>
                              <RFtoISEnabled>1</RFtoISEnabled>
                              <IStoRFEnabled>1</IStoRFEnabled>
                              <MyCallNot3rd>0</MyCallNot3rd>
                              <BeaconingEnabled>1</BeaconingEnabled>
                              <BeaconPath>WIDE2-1</BeaconPath>
                              <BulletinObjectEnabled>1</BulletinObjectEnabled>
                              <DXEnabled>1</DXEnabled>
                              <DXPath>RFONLY</DXPath>
                              <MessagesEnabled>1</MessagesEnabled>
                              <MessagePath></MessagePath>
                              <TelemetryEnabled>0</TelemetryEnabled>
                              <TelemetryPath></TelemetryPath>
                              <!--DigiXform-->
                              </RFPort><!--RFPort[0]-->

                              If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly. If you have an issue the first time, try    >Enables >View Logs >Ports(KPC-3)    >Enables > Port >KPC-3            to close the port then again    >Enables > Port >KPC-3            to re-open the port Then check the log - post if needed Robert Giuliano KB8RCO

                              ---------------------------------------------

                              From: ke6gyd mailto:ke6gyd@...
                              To: aprsisce@yahoogroups.com
                              Sent: Thursday, August 29, 2013 8:01 PM
                              Subject: [aprsisce] Re: KPC3 configuration
                               
                              Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something? <!--RFPort[0]--> <RFPort Name="KPC-3"> <Protocol>KISS</Protocol> <Device>COM1:9600,N,8,1</Device> <RfBaud>1200</RfBaud> <OpenCmd>^M~1!!0</OpenCmd> <OpenCmd>^C~!cmd:!2</OpenCmd> <OpenCmd>CD SOFT!cmd:!1</OpenCmd> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> <OpenCmd>INT KISS!cmd:!1</OpenCmd> <OpenCmd>RESET!cmd:!3</OpenCmd> <CloseCmd>^192^255^192~!!0</CloseCmd> <CloseCmd>^C^C^C~!!0</CloseCmd> <CloseCmd>TC 1!TS 1</CloseCmd> <CloseCmd>TN 2,0!TN 2,0</CloseCmd> <QuietTime>0</QuietTime> <Enabled>0</Enabled> Log shows: Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0> Looks like it somehow is not in KISS mode? Any suggestions would be appreciated. Thanks Bob KE6GYD --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano mailto:kb8rco@... wrote: > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED. > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed. >    KEY-> the port is opened when APRSISce/32 requests use of it >              Application start-up if configured as OPEN on last close >             Also through the menu system: >               >Enables >Ports {your KPC3 port name} > >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup) > Mine is setup with: > <OpenCmd>^M~!!0</OpenCmd> > <OpenCmd>^C~!cmd:!2</OpenCmd> > <OpenCmd>CD SOFT!cmd:!1</OpenCmd> > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> > <OpenCmd>INT KISS!cmd:!1</OpenCmd> > <OpenCmd>RESET!cmd:!3</OpenCmd> > > <CloseCmd>^192^255^192~!!0</CloseCmd> > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd> > > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup. > > Give these a try and let us know > > Robert Giuliano > KB8RCO > > > --------------------------------------------- > > > ________________________________ > From: ke6gyd mailto:ke6gyd@... > To: mailto:aprsisce%40yahoogroups.com > Sent: Thursday, August 29, 2013 10:35 AM > Subject: [aprsisce] Re: KPC3 configuration > >   > > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet. > > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated. > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this? > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available. > > Thanks > Bob > KE6GYD > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote: > > > > I TOTALLY disagree! > > > > > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you. > > > > Which you choose will determine what type of port > >    Continuous Mode - Simple KISS > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode. > > > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . . > >   > > > > Robert Giuliano > > KB8RCO > > > > > > --------------------------------------------- > > > > From: Adam Mahnke <kc2ant@> > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com> > > Sent: Tuesday, August 27, 2013 10:16 PM > > Subject: RE: [aprsisce] KPC3 configuration > > > >   > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset. > > > > http://aprsisce.wikidot.com/tnc-kpc-3 > > > > > > Adam > > KC2ANT > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration  > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD > > >
                            • ke6gyd
                              Gentlemen, The device I was using is a KPC3 (no plus) with one port. I do have a 3+, but not trying it at this time. Haven t played with it yesterday to
                              Message 14 of 29 , Aug 31, 2013
                              • 0 Attachment
                                Gentlemen,

                                The device I was using is a KPC3 (no plus) with one port.  I do have a 3+, but not trying it at this time.

                                Haven't played with it yesterday to further try troubleshooting, but I will say that I'm a neophyte with this terminology and use of the .xml file, so that may be part of the problem.

                                I'll try to digest your comments and suggestions and give it a shot in the next few days and let you know what happens. 

                                I did notice that there seems to be two ways to state an .xml file command such as
                                <OpenCmd>CD SOFT!cmd:!1</OpenCmd>  (1 meaning seconds of time)
                                vs.

                                <OpenCmd>CD SOFT</OpenCmd>

                                Is there a document that explains this code so I can understand it better.
                                I believe that all the items between the >  < are packet terminal commands.

                                Thanks Again
                                Bob
                                KE6GYD
                                 

                                 







                                --- In aprsisce@yahoogroups.com, <kb8rco@...> wrote:

                                Yep!
                                  Lynn straightened me out as well!
                                 
                                Robert Giuliano
                                KB8RCO


                                ---------------------------------------------

                                From: Fred Hillhouse <fmhillhouse@...>
                                To: aprsisce@yahoogroups.com
                                Sent: Friday, August 30, 2013 2:02 PM
                                Subject: RE: [aprsisce] Re: KPC3 configuration
                                 
                                I think you missed what I was saying. If "cmd:" is expected, and a 1 second delay is normal without adding anymore information to the string, then, adding more text to define the same thing it isn't needed.
                                 
                                From the WIKI:
                                If you don't specify a Response (no !), "cmd:" is expected.
                                If you don't specify a Delay (only one !), 1 second is assumed.
                                 
                                As I understand it, adding "!cmd:!1" is redundant but it does make it plain what is going on.
                                 
                                If I was to re-write this example from the WIKI:
                                <OpenCmd>KISS ON</OpenCmd> <!— Transmit "KISS ON<cr>", Wait for "cmd:", for 1 second max — >
                                 
                                I could add between "ON" and "<", "!cmd:!1" and achieve the same thing. Again, this is my point.
                                <OpenCmd>KISS ON!cmd:!1</OpenCmd> which equals <OpenCmd>KISS ON</OpenCmd>
                                 
                                Looking back at the original TNC OpenCmd entry in the XML:
                                <OpenCmd>CD SOFT!cmd:!1</OpenCmd> which is the same as <OpenCmd>CD SOFT</OpenCmd>
                                 
                                 
                                When I mentioned field, it was in reference to the space that could be used for a "wait for string".
                                 
                                If an open command (OpenCmd) is sent, then the default data for the 2 fields are "cmd:" and "1". Each field needs a "!" in front of it.
                                 
                                There is a special case of a non-default delay and still expecting a default response. The response, even though it is default, must be re-stated.
                                 
                                These are a few examples:
                                 
                                Normal, waits for cmd: for up to 1 second (default):
                                <OpenCmd>KISS ON</OpenCmd>
                                 
                                Same as Normal, just entered more explicitly:
                                <OpenCmd>KISS ON!cmd:!1</OpenCmd>
                                 
                                Expecting a non-default response and a default delay:
                                <OpenCmd>KISS ON!Robert</OpenCmd>
                                 
                                Expecting a non-default response and a non-default delay:
                                <OpenCmd>KISS ON!Robert!2</OpenCmd>
                                 
                                Expecting default response (re-stated) and with a non-default delay:
                                <OpenCmd>KISS ON!cmd:!2</OpenCmd>
                                 
                                Not expecting a response and with a non-default delay:
                                <OpenCmd>KISS ON!!2</OpenCmd>
                                 
                                As I said previously, I am trying to get edumacated and this is how I currently understand it.
                                 
                                And, yes I am famous but not REALLY famous. :)
                                 
                                 
                                Best regards,
                                Fred N7FMH
                                 
                                From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                                Sent: Friday, August 30, 2013 12:59
                                To: aprsisce@yahoogroups.com
                                Subject: Re: [aprsisce] Re: KPC3 configuration
                                 
                                I believe a command like
                                <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                 
                                means ->
                                   Send command "CD SOFT"
                                   YES - Look for response from TNC of "cmd:" for 1 seond
                                 
                                What "field" are you talking about?  "...but look for what is in the field ..."
                                The "FIELD" between two "!" is "cmd:" -> that's what to look for.
                                 
                                The cmd: is what the KPC-3 sends when in "command mode".
                                   If it arrives immediately, APRSIS32 will go to the next step.
                                   If it doesn't arrive in "1" second, APRSIS32 will go to the next step.
                                 
                                That is how I understand it, and it seems to be how APRSIS32 is interfacing with my KPC-3.
                                 
                                I can't get at my KPC-3 right now, but will change it to:
                                  
                                   <OpenCmd>CD SOFT!Fred!10</OpenCmd>
                                to see if it waits 10 seconds before trying the enxt command. 
                                   (You REALLY are FAMOUS if my KPC-3 actually responds to your name - hihi )
                                 
                                Robert Giuliano
                                KB8RCO

                                ---------------------------------------------
                                From: Fred Hillhouse <fmhillhouse@...>
                                To: aprsisce@yahoogroups.com
                                Sent: Friday, August 30, 2013 10:35 AM
                                Subject: RE: [aprsisce] Re: KPC3 configuration
                                 
                                Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
                                 
                                This now becomes education for me and anyone wishing to follow along.
                                 
                                Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
                                 
                                If I look at this line from below:
                                <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                 
                                I understand this to say:
                                Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
                                 
                                I think it can be rewritten and produce the same results as:
                                <OpenCmd>CD SOFT</OpenCmd>
                                 
                                And one more from the XML:
                                <OpenCmd>RESET!!3</OpenCmd>
                                I understand this to say:
                                Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
                                 
                                 
                                Best regards,
                                 
                                Fred N7FMH
                                 
                                 
                                From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
                                Sent: Friday, August 30, 2013 09:55
                                To: aprsisce@yahoogroups.com
                                Subject: Re: [aprsisce] Re: KPC3 configuration
                                 
                                Read it carefully and completely.  It says (just above the example you're referencing):
                                If you don't specify a Response (no !), "cmd:" is expected
                                Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
                                Is there something missing on this page?
                                 
                                In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
                                 
                                Best regards,
                                Fred N7FMH


                                From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                                Sent: Thursday, August 29, 2013 21:31
                                To: aprsisce@yahoogroups.com
                                Subject: Re: [aprsisce] Re: KPC3 configuration
                                 
                                From the log, it is not going into KISS mode.
                                The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                                  and it looks like I had a bad "cmd:" after the reset.
                                Here is an EXACT copy of my port for my KPC-3:
                                <!--RFPort[0]-->
                                <RFPort Name="KPC3">
                                <Protocol>KISS</Protocol>
                                <Device>COM1:9600,N,8,1</Device>
                                <RfBaud>1200</RfBaud>
                                <OpenCmd>^M~!!0</OpenCmd>
                                <OpenCmd>^C~!cmd:!2</OpenCmd>
                                <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                                <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                                <OpenCmd>INT KISS!!0</OpenCmd>
                                <OpenCmd>RESET!!3</OpenCmd>
                                <CloseCmd>^192^255^192~!!0</CloseCmd>
                                <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                                <QuietTime>0</QuietTime>
                                <Enabled>1</Enabled>
                                <XmitEnabled>1</XmitEnabled>
                                <ProvidesNMEA>0</ProvidesNMEA>
                                <RFtoISEnabled>1</RFtoISEnabled>
                                <IStoRFEnabled>1</IStoRFEnabled>
                                <MyCallNot3rd>0</MyCallNot3rd>
                                <BeaconingEnabled>1</BeaconingEnabled>
                                <BeaconPath>WIDE2-1</BeaconPath>
                                <BulletinObjectEnabled>1</BulletinObjectEnabled>
                                <DXEnabled>1</DXEnabled>
                                <DXPath>RFONLY</DXPath>
                                <MessagesEnabled>1</MessagesEnabled>
                                <MessagePath></MessagePath>
                                <TelemetryEnabled>0</TelemetryEnabled>
                                <TelemetryPath></TelemetryPath>
                                <!--DigiXform-->
                                </RFPort> ><!--RFPort[0]-->

                                If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly. If you have an issue the first time, try    >Enables >View Logs >Ports(KPC-3)    >Enables > Port >KPC-3            to close the port then again    >Enables > Port >KPC-3            to re-open the port Then check the log - post if needed Robert Giuliano KB8RCO

                                ---------------------------------------------

                                From: ke6gyd mailto:ke6gyd@...
                                To: aprsisce@yahoogroups.com
                                Sent: Thursday, August 29, 2013 8:01 PM
                                Subject: [aprsisce] Re: KPC3 configuration
                                 
                                Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something? <!--RFPort[0]--> <RFPort Name="KPC-3"> <Protocol>KISS</Protocol> <Device>COM1:9600,N,8,1</Device> <RfBaud>1200</RfBaud> <OpenCmd>^M~1!!0</OpenCmd> <OpenCmd>^C~!cmd:!2</OpenCmd> <OpenCmd>CD SOFT!cmd:!1</OpenCmd> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> <OpenCmd>INT KISS!cmd:!1</OpenCmd> <OpenCmd>RESET!cmd:!3</OpenCmd> <CloseCmd>^192^255^192~!!0</CloseCmd> <CloseCmd>^C^C^C~!!0</CloseCmd> <CloseCmd>TC 1!TS 1</CloseCmd> <CloseCmd>TN 2,0!TN 2,0</CloseCmd> <QuietTime>0</QuietTime> <Enabled>0</Enabled> Log shows: Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0> Looks like it somehow is not in KISS mode? Any suggestions would be appreciated. Thanks Bob KE6GYD --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano mailto:kb8rco@... wrote: > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED. > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed. >    KEY-> the port is opened when APRSISce/32 requests use of it >              Application start-up if configured as OPEN on last close >             Also through the menu system: >               >Enables >Ports {your KPC3 port name} > >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup) > Mine is setup with: > <OpenCmd>^M~!!0</OpenCmd> > <OpenCmd>^C~!cmd:!2</OpenCmd> > <OpenCmd>CD SOFT!cmd:!1</OpenCmd> > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> > <OpenCmd>INT KISS!cmd:!1</OpenCmd> > <OpenCmd>RESET!cmd:!3</OpenCmd> > > <CloseCmd>^192^255^192~!!0</CloseCmd> > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd> > > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup. > > Give these a try and let us know > > Robert Giuliano > KB8RCO > > > --------------------------------------------- > > > ________________________________ > From: ke6gyd mailto:ke6gyd@... > To: mailto:aprsisce%40yahoogroups.com > Sent: Thursday, August 29, 2013 10:35 AM > Subject: [aprsisce] Re: KPC3 configuration > >   > > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet. > > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated. > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this? > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available. > > Thanks > Bob > KE6GYD > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote: > > > > I TOTALLY disagree! > > > > > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you. > > > > Which you choose will determine what type of port > >    Continuous Mode - Simple KISS > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode. > > > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . . > >   > > > > Robert Giuliano > > KB8RCO > > > > > > --------------------------------------------- > > > > From: Adam Mahnke <kc2ant@> > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com> > > Sent: Tuesday, August 27, 2013 10:16 PM > > Subject: RE: [aprsisce] KPC3 configuration > > > >   > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset. > > > > http://aprsisce.wikidot.com/tnc-kpc-3 > > > > > > Adam > > KC2ANT > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration  > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD > > >
                              • ke6gyd
                                We ll keep trying, I ll give it a rest for a while and try to digest all the suggestions. Thanks Bob KE6GYD --- In aprsisce@yahoogroups.com,
                                Message 15 of 29 , Aug 31, 2013
                                • 0 Attachment

                                   We'll keep trying, I'll give it a rest for a while and try to digest all the suggestions.

                                  Thanks

                                  Bob

                                  KE6GYD



                                  --- In aprsisce@yahoogroups.com, <ke6gyd@...> wrote:

                                  Gentlemen,

                                  The device I was using is a KPC3 (no plus) with one port.  I do have a 3+, but not trying it at this time.

                                  Haven't played with it yesterday to further try troubleshooting, but I will say that I'm a neophyte with this terminology and use of the .xml file, so that may be part of the problem.

                                  I'll try to digest your comments and suggestions and give it a shot in the next few days and let you know what happens. 

                                  I did notice that there seems to be two ways to state an .xml file command such as
                                  <OpenCmd>CD SOFT!cmd:!1</OpenCmd>  (1 meaning seconds of time)
                                  vs.

                                  <OpenCmd>CD SOFT</OpenCmd>

                                  Is there a document that explains this code so I can understand it better.
                                  I believe that all the items between the >  < are packet terminal commands.

                                  Thanks Again
                                  Bob
                                  KE6GYD
                                   

                                   







                                  --- In aprsisce@yahoogroups.com, <kb8rco@...> wrote:

                                  Yep!
                                    Lynn straightened me out as well!
                                   
                                  Robert Giuliano
                                  KB8RCO


                                  ---------------------------------------------

                                  From: Fred Hillhouse <fmhillhouse@...>
                                  To: aprsisce@yahoogroups.com
                                  Sent: Friday, August 30, 2013 2:02 PM
                                  Subject: RE: [aprsisce] Re: KPC3 configuration
                                   
                                  I think you missed what I was saying. If "cmd:" is expected, and a 1 second delay is normal without adding anymore information to the string, then, adding more text to define the same thing it isn't needed.
                                   
                                  From the WIKI:
                                  If you don't specify a Response (no !), "cmd:" is expected.
                                  If you don't specify a Delay (only one !), 1 second is assumed.
                                   
                                  As I understand it, adding "!cmd:!1" is redundant but it does make it plain what is going on.
                                   
                                  If I was to re-write this example from the WIKI:
                                  <OpenCmd>KISS ON</OpenCmd> <!— Transmit "KISS ON<cr>", Wait for "cmd:", for 1 second max — >
                                   
                                  I could add between "ON" and "<", "!cmd:!1" and achieve the same thing. Again, this is my point.
                                  <OpenCmd>KISS ON!cmd:!1</OpenCmd> which equals <OpenCmd>KISS ON</OpenCmd>
                                   
                                  Looking back at the original TNC OpenCmd entry in the XML:
                                  <OpenCmd>CD SOFT!cmd:!1</OpenCmd> which is the same as <OpenCmd>CD SOFT</OpenCmd>
                                   
                                   
                                  When I mentioned field, it was in reference to the space that could be used for a "wait for string".
                                   
                                  If an open command (OpenCmd) is sent, then the default data for the 2 fields are "cmd:" and "1". Each field needs a "!" in front of it.
                                   
                                  There is a special case of a non-default delay and still expecting a default response. The response, even though it is default, must be re-stated.
                                   
                                  These are a few examples:
                                   
                                  Normal, waits for cmd: for up to 1 second (default):
                                  <OpenCmd>KISS ON</OpenCmd>
                                   
                                  Same as Normal, just entered more explicitly:
                                  <OpenCmd>KISS ON!cmd:!1</OpenCmd>
                                   
                                  Expecting a non-default response and a default delay:
                                  <OpenCmd>KISS ON!Robert</OpenCmd>
                                   
                                  Expecting a non-default response and a non-default delay:
                                  <OpenCmd>KISS ON!Robert!2</OpenCmd>
                                   
                                  Expecting default response (re-stated) and with a non-default delay:
                                  <OpenCmd>KISS ON!cmd:!2</OpenCmd>
                                   
                                  Not expecting a response and with a non-default delay:
                                  <OpenCmd>KISS ON!!2</OpenCmd>
                                   
                                  As I said previously, I am trying to get edumacated and this is how I currently understand it.
                                   
                                  And, yes I am famous but not REALLY famous. :)
                                   
                                   
                                  Best regards,
                                  Fred N7FMH
                                   
                                  From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                                  Sent: Friday, August 30, 2013 12:59
                                  To: aprsisce@yahoogroups.com
                                  Subject: Re: [aprsisce] Re: KPC3 configuration
                                   
                                  I believe a command like
                                  <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                   
                                  means ->
                                     Send command "CD SOFT"
                                     YES - Look for response from TNC of "cmd:" for 1 seond
                                   
                                  What "field" are you talking about?  "...but look for what is in the field ..."
                                  The "FIELD" between two "!" is "cmd:" -> that's what to look for.
                                   
                                  The cmd: is what the KPC-3 sends when in "command mode".
                                     If it arrives immediately, APRSIS32 will go to the next step.
                                     If it doesn't arrive in "1" second, APRSIS32 will go to the next step.
                                   
                                  That is how I understand it, and it seems to be how APRSIS32 is interfacing with my KPC-3.
                                   
                                  I can't get at my KPC-3 right now, but will change it to:
                                    
                                     <OpenCmd>CD SOFT!Fred!10</OpenCmd>
                                  to see if it waits 10 seconds before trying the enxt command. 
                                     (You REALLY are FAMOUS if my KPC-3 actually responds to your name - hihi )
                                   
                                  Robert Giuliano
                                  KB8RCO

                                  ---------------------------------------------
                                  From: Fred Hillhouse <fmhillhouse@...>
                                  To: aprsisce@yahoogroups.com
                                  Sent: Friday, August 30, 2013 10:35 AM
                                  Subject: RE: [aprsisce] Re: KPC3 configuration
                                   
                                  Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
                                   
                                  This now becomes education for me and anyone wishing to follow along.
                                   
                                  Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
                                   
                                  If I look at this line from below:
                                  <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                   
                                  I understand this to say:
                                  Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
                                   
                                  I think it can be rewritten and produce the same results as:
                                  <OpenCmd>CD SOFT</OpenCmd>
                                   
                                  And one more from the XML:
                                  <OpenCmd>RESET!!3</OpenCmd>
                                  I understand this to say:
                                  Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
                                   
                                   
                                  Best regards,
                                   
                                  Fred N7FMH
                                   
                                   
                                  From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
                                  Sent: Friday, August 30, 2013 09:55
                                  To: aprsisce@yahoogroups.com
                                  Subject: Re: [aprsisce] Re: KPC3 configuration
                                   
                                  Read it carefully and completely.  It says (just above the example you're referencing):
                                  If you don't specify a Response (no !), "cmd:" is expected
                                  Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
                                  Is there something missing on this page?
                                   
                                  In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
                                   
                                  Best regards,
                                  Fred N7FMH


                                  From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                                  Sent: Thursday, August 29, 2013 21:31
                                  To: aprsisce@yahoogroups.com
                                  Subject: Re: [aprsisce] Re: KPC3 configuration
                                   
                                  From the log, it is not going into KISS mode.
                                  The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                                    and it looks like I had a bad "cmd:" after the reset.
                                  Here is an EXACT copy of my port for my KPC-3:
                                  <!--RFPort[0]-->
                                  <RFPort Name="KPC3">
                                  <Protocol>KISS</Protocol>
                                  <Device>COM1:9600,N,8,1</Device>
                                  <RfBaud>1200</RfBaud>
                                  <OpenCmd>^M~!!0</OpenCmd>
                                  <OpenCmd>^C~!cmd:!2</OpenCmd>
                                  <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                  <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                                  <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                                  <OpenCmd>INT KISS!!0</OpenCmd>
                                  <OpenCmd>RESET!!3</OpenCmd>
                                  <CloseCmd>^192^255^192~!!0</CloseCmd>
                                  <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                                  <QuietTime>0</QuietTime>
                                  <Enabled>1</Enabled>
                                  <XmitEnabled>1</XmitEnabled>
                                  <ProvidesNMEA>0</ProvidesNMEA>
                                  <RFtoISEnabled>1</RFtoISEnabled>
                                  <IStoRFEnabled>1</IStoRFEnabled>
                                  <MyCallNot3rd>0</MyCallNot3rd>
                                  <BeaconingEnabled>1</BeaconingEnabled>
                                  <BeaconPath>WIDE2-1</BeaconPath>
                                  <BulletinObjectEnabled>1</BulletinObjectEnabled>
                                  <DXEnabled>1</DXEnabled>
                                  <DXPath>RFONLY</DXPath>
                                  <MessagesEnabled>1</MessagesEnabled>
                                  <MessagePath></MessagePath>
                                  <TelemetryEnabled>0</TelemetryEnabled>
                                  <TelemetryPath></TelemetryPath>
                                  <!--DigiXform-->
                                  </RFPort> ><!--RFPort[0]-->

                                  If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly. If you have an issue the first time, try    >Enables >View Logs >Ports(KPC-3)    >Enables > Port >KPC-3            to close the port then again    >Enables > Port >KPC-3            to re-open the port Then check the log - post if needed Robert Giuliano KB8RCO

                                  ---------------------------------------------

                                  From: ke6gyd mailto:ke6gyd@...
                                  To: aprsisce@yahoogroups.com
                                  Sent: Thursday, August 29, 2013 8:01 PM
                                  Subject: [aprsisce] Re: KPC3 configuration
                                   
                                  Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something? <!--RFPort[0]--> <RFPort Name="KPC-3"> <Protocol>KISS</Protocol> <Device>COM1:9600,N,8,1</Device> <RfBaud>1200</RfBaud> <OpenCmd>^M~1!!0</OpenCmd> <OpenCmd>^C~!cmd:!2</OpenCmd> <OpenCmd>CD SOFT!cmd:!1</OpenCmd> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> <OpenCmd>INT KISS!cmd:!1</OpenCmd> <OpenCmd>RESET!cmd:!3</OpenCmd> <CloseCmd>^192^255^192~!!0</CloseCmd> <CloseCmd>^C^C^C~!!0</CloseCmd> <CloseCmd>TC 1!TS 1</CloseCmd> <CloseCmd>TN 2,0!TN 2,0</CloseCmd> <QuietTime>0</QuietTime> <Enabled>0</Enabled> Log shows: Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0> Looks like it somehow is not in KISS mode? Any suggestions would be appreciated. Thanks Bob KE6GYD --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano mailto:kb8rco@... wrote: > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED. > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed. >    KEY-> the port is opened when APRSISce/32 requests use of it >              Application start-up if configured as OPEN on last close >             Also through the menu system: >               >Enables >Ports {your KPC3 port name} > >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup) > Mine is setup with: > <OpenCmd>^M~!!0</OpenCmd> > <OpenCmd>^C~!cmd:!2</OpenCmd> > <OpenCmd>CD SOFT!cmd:!1</OpenCmd> > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> > <OpenCmd>INT KISS!cmd:!1</OpenCmd> > <OpenCmd>RESET!cmd:!3</OpenCmd> > > <CloseCmd>^192^255^192~!!0</CloseCmd> > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd> > > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup. > > Give these a try and let us know > > Robert Giuliano > KB8RCO > > > --------------------------------------------- > > > ________________________________ > From: ke6gyd mailto:ke6gyd@... > To: mailto:aprsisce%40yahoogroups.com > Sent: Thursday, August 29, 2013 10:35 AM > Subject: [aprsisce] Re: KPC3 configuration > >   > > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet. > > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated. > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this? > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available. > > Thanks > Bob > KE6GYD > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote: > > > > I TOTALLY disagree! > > > > > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you. > > > > Which you choose will determine what type of port > >    Continuous Mode - Simple KISS > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode. > > > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . . > >   > > > > Robert Giuliano > > KB8RCO > > > > > > --------------------------------------------- > > > > From: Adam Mahnke <kc2ant@> > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com> > > Sent: Tuesday, August 27, 2013 10:16 PM > > Subject: RE: [aprsisce] KPC3 configuration > > > >   > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset. > > > > http://aprsisce.wikidot.com/tnc-kpc-3 > > > > > > Adam > > KC2ANT > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration  > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD > > >
                                • Lynn W Deffenbaugh (Mr)
                                  ... They are both the same, but the second one relies on the defaults which are explicitly specified in the first one. ...
                                  Message 16 of 29 , Aug 31, 2013
                                  • 0 Attachment
                                    On 8/31/2013 9:04 AM, ke6gyd@... wrote:

                                    I did notice that there seems to be two ways to state an .xml file command such as
                                    <OpenCmd>CD SOFT!cmd:!1</OpenCmd>  (1 meaning seconds of time)
                                    vs.

                                    <OpenCmd>CD SOFT</OpenCmd>

                                    They are both the same, but the second one relies on the defaults which are explicitly specified in the first one.


                                    Is there a document that explains this code so I can understand it better.

                                    http://aprsisce.wikidot.com/doc:openclosecmd

                                    I believe that all the items between the >  < are packet terminal commands.

                                    Almost.  The value of the XML element (between the > and <) is a term which can have one, two, or three parts delimited by !.  The first piece is the command to send out.  The second piece is the expected response with a default of cmd:.  The third piece is the timeout in seconds with a default of 1.

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

                                  • Rob Giuliano
                                    The APRSISce/32 WIKI:    http://aprsisce.wikidot.com I think patrs were posted before, but more specifics:    http://aprsisce.wikidot.com/doc:openclosecmd
                                    Message 17 of 29 , Aug 31, 2013
                                    • 0 Attachment
                                      The APRSISce/32 WIKI:
                                       
                                      I think patrs were posted before, but more specifics:
                                       
                                      Robert Giuliano
                                      KB8RCO


                                      ---------------------------------------------

                                      From: "ke6gyd@..." <ke6gyd@...>
                                      To: aprsisce@yahoogroups.com
                                      Sent: Saturday, August 31, 2013 9:10 AM
                                      Subject: RE: Re: [aprsisce] Re: KPC3 configuration at exit of APRSIS32 progam
                                       
                                       We'll keep trying, I'll give it a rest for a while and try to digest all the suggestions.
                                      Thanks
                                      Bob
                                      KE6GYD
                                      --- In aprsisce@yahoogroups.com, <ke6gyd@...> wrote:
                                      Gentlemen, The device I was using is a KPC3 (no plus) with one port.  I do have a 3+, but not trying it at this time. Haven't played with it yesterday to further try troubleshooting, but I will say that I'm a neophyte with this terminology and use of the .xml file, so that may be part of the problem. I'll try to digest your comments and suggestions and give it a shot in the next few days and let you know what happens.  I did notice that there seems to be two ways to state an .xml file command such as
                                      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>  (1 meaning seconds of time)
                                      vs.
                                      <OpenCmd>CD SOFT</OpenCmd>

                                      Is there a document that explains this code so I can understand it better.
                                      I believe that all the items between the >  < are packet terminal commands.

                                      Thanks Again
                                      Bob
                                      KE6GYD
                                       
                                       


                                      --- In aprsisce@yahoogroups.com, <kb8rco@...> wrote:

                                      Yep!
                                        Lynn straightened me out as well!
                                       
                                      Robert Giuliano
                                      KB8RCO

                                      ---------------------------------------------
                                      From: Fred Hillhouse <fmhillhouse@...>
                                      To: aprsisce@yahoogroups.com
                                      Sent: Friday, August 30, 2013 2:02 PM
                                      Subject: RE: [aprsisce] Re: KPC3 configuration
                                       
                                      I think you missed what I was saying. If "cmd:" is expected, and a 1 second delay is normal without adding anymore information to the string, then, adding more text to define the same thing it isn't needed.
                                       
                                      From the WIKI:
                                      If you don't specify a Response (no !), "cmd:" is expected.
                                      If you don't specify a Delay (only one !), 1 second is assumed.
                                       
                                      As I understand it, adding "!cmd:!1" is redundant but it does make it plain what is going on.
                                       
                                      If I was to re-write this example from the WIKI:
                                      <OpenCmd>KISS ON</OpenCmd> <!— Transmit "KISS ON<cr>", Wait for "cmd:", for 1 second max — >
                                       
                                      I could add between "ON" and "<", "!cmd:!1" and achieve the same thing. Again, this is my point.
                                      <OpenCmd>KISS ON!cmd:!1</OpenCmd> which equals <OpenCmd>KISS ON</OpenCmd>
                                       
                                      Looking back at the original TNC OpenCmd entry in the XML:
                                      <OpenCmd>CD SOFT!cmd:!1</OpenCmd> which is the same as <OpenCmd>CD SOFT</OpenCmd>
                                       
                                       
                                      When I mentioned field, it was in reference to the space that could be used for a "wait for string".
                                       
                                      If an open command (OpenCmd) is sent, then the default data for the 2 fields are "cmd:" and "1". Each field needs a "!" in front of it.
                                       
                                      There is a special case of a non-default delay and still expecting a default response. The response, even though it is default, must be re-stated.
                                       
                                      These are a few examples:
                                       
                                      Normal, waits for cmd: for up to 1 second (default):
                                      <OpenCmd>KISS ON</OpenCmd>
                                       
                                      Same as Normal, just entered more explicitly:
                                      <OpenCmd>KISS ON!cmd:!1</OpenCmd>
                                       
                                      Expecting a non-default response and a default delay:
                                      <OpenCmd>KISS ON!Robert</OpenCmd>
                                       
                                      Expecting a non-default response and a non-default delay:
                                      <OpenCmd>KISS ON!Robert!2</OpenCmd>
                                       
                                      Expecting default response (re-stated) and with a non-default delay:
                                      <OpenCmd>KISS ON!cmd:!2</OpenCmd>
                                       
                                      Not expecting a response and with a non-default delay:
                                      <OpenCmd>KISS ON!!2</OpenCmd>
                                       
                                      As I said previously, I am trying to get edumacated and this is how I currently understand it.
                                       
                                      And, yes I am famous but not REALLY famous. :)
                                       
                                       
                                      Best regards,
                                      Fred N7FMH
                                       
                                      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                                      Sent: Friday, August 30, 2013 12:59
                                      To: aprsisce@yahoogroups.com
                                      Subject: Re: [aprsisce] Re: KPC3 configuration
                                       
                                      I believe a command like
                                      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                       
                                      means ->
                                         Send command "CD SOFT"
                                         YES - Look for response from TNC of "cmd:" for 1 seond
                                       
                                      What "field" are you talking about?  "...but look for what is in the field ..."
                                      The "FIELD" between two "!" is "cmd:" -> that's what to look for.
                                       
                                      The cmd: is what the KPC-3 sends when in "command mode".
                                         If it arrives immediately, APRSIS32 will go to the next step.
                                         If it doesn't arrive in "1" second, APRSIS32 will go to the next step.
                                       
                                      That is how I understand it, and it seems to be how APRSIS32 is interfacing with my KPC-3.
                                       
                                      I can't get at my KPC-3 right now, but will change it to:
                                        
                                         <OpenCmd>CD SOFT!Fred!10</OpenCmd>
                                      to see if it waits 10 seconds before trying the enxt command. 
                                         (You REALLY are FAMOUS if my KPC-3 actually responds to your name - hihi )
                                       
                                      Robert Giuliano
                                      KB8RCO

                                      ---------------------------------------------
                                      From: Fred Hillhouse <fmhillhouse@...>
                                      To: aprsisce@yahoogroups.com
                                      Sent: Friday, August 30, 2013 10:35 AM
                                      Subject: RE: [aprsisce] Re: KPC3 configuration
                                       
                                      Since the KPC in question is going into KISS, apparently the XML is fine. NO changes should be made to any XML at this time!!
                                       
                                      This now becomes education for me and anyone wishing to follow along.
                                       
                                      Okay Lynn, that is what I thought but then I saw the "OpenCmd" operations in the XML of interest below. I had never looked at this section in the WIKI since I don't have a TNC set up in this fashion.
                                       
                                      If I look at this line from below:
                                      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                       
                                      I understand this to say:
                                      Send command "CD SOFT", and don't look for "cmd:" but look for what is in the field, which just happens to be "cmd:" for up to one second.
                                       
                                      I think it can be rewritten and produce the same results as:
                                      <OpenCmd>CD SOFT</OpenCmd>
                                       
                                      And one more from the XML:
                                      <OpenCmd>RESET!!3</OpenCmd>
                                      I understand this to say:
                                      Send command "RESET", don't expect any return, wait for 3 seconds, then continue.
                                       
                                       
                                      Best regards,
                                       
                                      Fred N7FMH
                                       
                                       
                                      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
                                      Sent: Friday, August 30, 2013 09:55
                                      To: aprsisce@yahoogroups.com
                                      Subject: Re: [aprsisce] Re: KPC3 configuration
                                       
                                      Read it carefully and completely.  It says (just above the example you're referencing):
                                      If you don't specify a Response (no !), "cmd:" is expected
                                      Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/30/2013 9:35 AM, Fred Hillhouse wrote:
                                      Is there something missing on this page?
                                       
                                      In the samples at the bottom, the one for "KISS ON" appears incomplete when compared with the open commands below. Or is "cmd:" always expected so it really doesn't need to be included?
                                       
                                      Best regards,
                                      Fred N7FMH


                                      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Rob Giuliano
                                      Sent: Thursday, August 29, 2013 21:31
                                      To: aprsisce@yahoogroups.com
                                      Subject: Re: [aprsisce] Re: KPC3 configuration
                                       
                                      From the log, it is not going into KISS mode.
                                      The only issue I see is an "EXTRA <ONE>   on your first <OpenCmd>
                                        and it looks like I had a bad "cmd:" after the reset.
                                      Here is an EXACT copy of my port for my KPC-3:
                                      <!--RFPort[0]-->
                                      <RFPort Name="KPC3">
                                      <Protocol>KISS</Protocol>
                                      <Device>COM1:9600,N,8,1</Device>
                                      <RfBaud>1200</RfBaud>
                                      <OpenCmd>^M~!!0</OpenCmd>
                                      <OpenCmd>^C~!cmd:!2</OpenCmd>
                                      <OpenCmd>CD SOFT!cmd:!1</OpenCmd>
                                      <OpenCmd>XFLOW ON!cmd:!0</OpenCmd>
                                      <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd>
                                      <OpenCmd>INT KISS!!0</OpenCmd>
                                      <OpenCmd>RESET!!3</OpenCmd>
                                      <CloseCmd>^192^255^192~!!0</CloseCmd>
                                      <CloseCmd>^C^C^C~!cmd:!3</CloseCmd>
                                      <QuietTime>0</QuietTime>
                                      <Enabled>1</Enabled>
                                      <XmitEnabled>1</XmitEnabled>
                                      <ProvidesNMEA>0</ProvidesNMEA>
                                      <RFtoISEnabled>1</RFtoISEnabled>
                                      <IStoRFEnabled>1</IStoRFEnabled>
                                      <MyCallNot3rd>0</MyCallNot3rd>
                                      <BeaconingEnabled>1</BeaconingEnabled>
                                      <BeaconPath>WIDE2-1</BeaconPath>
                                      <BulletinObjectEnabled>1</BulletinObjectEnabled>
                                      <DXEnabled>1</DXEnabled>
                                      <DXPath>RFONLY</DXPath>
                                      <MessagesEnabled>1</MessagesEnabled>
                                      <MessagePath></MessagePath>
                                      <TelemetryEnabled>0</TelemetryEnabled>
                                      <TelemetryPath></TelemetryPath>
                                      <!--DigiXform-->
                                      </RFPort> ><!--RFPort[0]-->

                                      If power is lost while connected, it may stay in KISS mode, If you OPEN and CLOSE the port (or exit and restart APRSIS32 again, it will close and reopen the port properly. If you have an issue the first time, try    >Enables >View Logs >Ports(KPC-3)    >Enables > Port >KPC-3            to close the port then again    >Enables > Port >KPC-3            to re-open the port Then check the log - post if needed Robert Giuliano KB8RCO

                                      ---------------------------------------------

                                      From: ke6gyd mailto:ke6gyd@...
                                      To: aprsisce@yahoogroups.com
                                      Sent: Thursday, August 29, 2013 8:01 PM
                                      Subject: [aprsisce] Re: KPC3 configuration
                                       
                                      Below are the settings I've done as per your last suggestion. Still can't get KPC3 (NO PLUS) to work except for one time after editing the xml file to your suggestions. Don't know if I changed anything that one time. Maybe I'm missing something? <!--RFPort[0]--> <RFPort Name="KPC-3"> <Protocol>KISS</Protocol> <Device>COM1:9600,N,8,1</Device> <RfBaud>1200</RfBaud> <OpenCmd>^M~1!!0</OpenCmd> <OpenCmd>^C~!cmd:!2</OpenCmd> <OpenCmd>CD SOFT!cmd:!1</OpenCmd> <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> <OpenCmd>INT KISS!cmd:!1</OpenCmd> <OpenCmd>RESET!cmd:!3</OpenCmd> <CloseCmd>^192^255^192~!!0</CloseCmd> <CloseCmd>^C^C^C~!!0</CloseCmd> <CloseCmd>TC 1!TS 1</CloseCmd> <CloseCmd>TN 2,0!TN 2,0</CloseCmd> <QuietTime>0</QuietTime> <Enabled>0</Enabled> Log shows: Port(KPC-3):2013-08-29T23:59:52.125 KISS:Missing 0, found C0[101]:<C0 82 A0 9E A8>db<E0 96 94>l<88 B0 A4 E2 9C>l<8A B0>@@<E9 03 F0>/235948h3344.52N/11800.58W>261/000!W85!/A=000007 12.5V 38C HDOP00.9 SATS08 <C0> Looks like it somehow is not in KISS mode? Any suggestions would be appreciated. Thanks Bob KE6GYD --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano mailto:kb8rco@... wrote: > > APRSIS32 has commands in the XML file that provide "INSTRUCTIONS" to the TNC when the port is OPENED or CLOSED. > These commands can be used to tell the KPC-3 to enter KISS MODE when the port is opened, and to tell the KPC-3 to return to its standard mode when the port is closed. >    KEY-> the port is opened when APRSISce/32 requests use of it >              Application start-up if configured as OPEN on last close >             Also through the menu system: >               >Enables >Ports {your KPC3 port name} > >  You have to edit the XML file in the directory where you APRSIS32.EXE file is (or linked to if you have a complex setup) > Mine is setup with: > <OpenCmd>^M~!!0</OpenCmd> > <OpenCmd>^C~!cmd:!2</OpenCmd> > <OpenCmd>CD SOFT!cmd:!1</OpenCmd> > <OpenCmd>XFLOW ON!cmd:!1</OpenCmd> > <OpenCmd>FULLDUP OFF!cmd:!1</OpenCmd> > <OpenCmd>INT KISS!cmd:!1</OpenCmd> > <OpenCmd>RESET!cmd:!3</OpenCmd> > > <CloseCmd>^192^255^192~!!0</CloseCmd> > <CloseCmd>^C^C^C!~!cmd:!3</CloseCmd> > > The open commands seem like a lot of "extras", but I had soime issues with FLOW and Duplex, so I explicitly set them in the setup. > > Give these a try and let us know > > Robert Giuliano > KB8RCO > > > --------------------------------------------- > > > ________________________________ > From: ke6gyd mailto:ke6gyd@... > To: mailto:aprsisce%40yahoogroups.com > Sent: Thursday, August 29, 2013 10:35 AM > Subject: [aprsisce] Re: KPC3 configuration > >   > > I'm leaning toward on demand and would like the TNC to return to normal mode since I use the TNC mostly for EComm use of Packet. > > What I don't understand in the text below is how to set that up with my KPC-3 and 3+. I'm not familiar with the terminology stated. > > Can APRSIS32 put the TNC in KISS Mode by configuring certain settings or is that set in the TNC? Where can I find the menu's to accomplish this? > > BTW, I also have a TinyTrak4 that I've got working just fine in KISS mode with APRSIS32, but I'd like the ability to use the KPC'3 if I don't have the TT4 available. > > Thanks > Bob > KE6GYD > > --- In mailto:aprsisce%40yahoogroups.com, Rob Giuliano <kb8rco@> wrote: > > > > I TOTALLY disagree! > > > > > > I agree that the best mode is KISS, but whether you CHOOSE to have it continuously in KISS mode (over resets) or CHOOSE to have APRSISce/32 put it in KISS mode on start and set it back to normal (converse) mode after shut down, is COMPLELY up to you. > > > > Which you choose will determine what type of port > >    Continuous Mode - Simple KISS > >    KISS on demand - set OPENCMD and CLOSECMD commands to ensure the TNC (KPC-3) is in the correct mode. > > > > I use the KPC-3, all the time (KB8RCO).  Not the Plus . . . > >   > > > > Robert Giuliano > > KB8RCO > > > > > > --------------------------------------------- > > > > From: Adam Mahnke <kc2ant@> > > To: "mailto:aprsisce%40yahoogroups.com" <mailto:aprsisce%40yahoogroups.com> > > Sent: Tuesday, August 27, 2013 10:16 PM > > Subject: RE: [aprsisce] KPC3 configuration > > > >   > > As I recall, the KPC3 will only work in KISS mode, the trick is locking it into KISS mode across a power reset. > > > > http://aprsisce.wikidot.com/tnc-kpc-3 > > > > > > Adam > > KC2ANT > > To: aprsisce@: ke6gyd@: Wed, 28 Aug 2013 00:10:31 +0000Subject: [aprsisce] KPC3 configuration  > > I've just installed APRSISCE and it's working on the laptop (Vista 32)and receiving Local APRS sations via the internet. I need to use a KPC 3 AND 3+ so I can see stations received via RF. Does the KPC3 have to be in KISS mode? I also use the KPC3 with Outpost Packet Message Manager using Terminal Mode, so connections are already made to radio, TNC and computer using a USB to RS232-adapter. I'm a neophyte at APRS as well as packet but wanting to learn more.ThanksBobKE6GYD > > >
                                    Your message has been successfully submitted and would be delivered to recipients shortly.