Date   

Re: Sleeping device breaks beaconing

ronnies07@...
 

Kenwood TM-V71A + Tiny Trak 4 in KISS mode
Using a Bolutek BLK-MD-BC04-B_DEMO Bluetooth to serial board I grabbed off eBay for the TNC connection.
The HP iPaq rx5915 Travel Companion does not posses a cellular radio, I operate RF only in the car
Received packets do appear on the scroller.
The APRSIS OK pane reports that NEMA is OK and TinyTrak4 is OK. ConMgr and APRS-IS is not shown as I have the 'Internet access' option disabled. Other then DIST it will cycle through other variables that have absurd numbers, a 20 mile trip will have DIST, PROJ, HEAD, etc in the high thousands with not a single beacon transmitted.
I operate KJ4HBF-9.

I think it has something to do with the 'min beacon time' setting breaking, as once the machine is in this state pushing 'transmit' gives me a 'beacon too fast' warning, but I can FORCE a beacon which is properly transmitted. Unfortunately this doesn't fix it; the timer counts down to 00:00 and stays there, the DIST; PROJ; and other variables just keep counting, and pushing Transmit a second time produces another 'beacon too fast' warning regardless of how much time has passed.


---In aprsisce@..., <kj4erj@...> wrote:

What radio and TNC?  What connection to the TNC?  Do you have mobile Internet and an APRS-IS connection?  Are there any packets scrolling by?  What all does the APRSIS OK pane say (other than DIST 8400%)?

And finally, what callsign-SSID are we talking about?

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

On 11/1/2013 9:23 PM, ronnies07@... wrote:
So with APRSISCE6P on my little HP Ipaq here I can set it to automatically sleep on external power loss figured this would be useful to automatically shut the device down when the car is off.

Problem is that this breaks beaconing, Waking the device with APRSISCE6P running appears to work normally, GPS finds a fix, TNC connects, Mapping works, Tracks position, etc. Except it won't beacon for any reason, The timer will count down and stay on 00:00, Dist, Proj, and other just keep counting (DIST 8400%) and pushing the 'Transmit' button produces a warning that I am beaconing too fast, and if I really want to FORCE it.


Re: Sleeping device breaks beaconing

Lynn Deffenbaugh
 

What radio and TNC?  What connection to the TNC?  Do you have mobile Internet and an APRS-IS connection?  Are there any packets scrolling by?  What all does the APRSIS OK pane say (other than DIST 8400%)?

And finally, what callsign-SSID are we talking about?

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

On 11/1/2013 9:23 PM, ronnies07@... wrote:
So with APRSISCE6P on my little HP Ipaq here I can set it to automatically sleep on external power loss figured this would be useful to automatically shut the device down when the car is off.

Problem is that this breaks beaconing, Waking the device with APRSISCE6P running appears to work normally, GPS finds a fix, TNC connects, Mapping works, Tracks position, etc. Except it won't beacon for any reason, The timer will count down and stay on 00:00, Dist, Proj, and other just keep counting (DIST 8400%) and pushing the 'Transmit' button produces a warning that I am beaconing too fast, and if I really want to FORCE it.


Sleeping device breaks beaconing

ronnies07@...
 

So with APRSISCE6P on my little HP Ipaq here I can set it to automatically sleep on external power loss figured this would be useful to automatically shut the device down when the car is off.

Problem is that this breaks beaconing, Waking the device with APRSISCE6P running appears to work normally, GPS finds a fix, TNC connects, Mapping works, Tracks position, etc. Except it won't beacon for any reason, The timer will count down and stay on 00:00, Dist, Proj, and other just keep counting (DIST 8400%) and pushing the 'Transmit' button produces a warning that I am beaconing too fast, and if I really want to FORCE it.


Re: DF1CHB is Air Mobile

sbd sbd
 

Yes he has been doing that for awhile. I was told by Helge a German ex airline pilot that it’s a 737 it’s a charter company. It could be he has swapped to a 747 now though. Tracked him earlier today on 30M

 

Steve Daniels

Amateur Radio Callsign G6UIM

Torbay Freecycle  Owner

http://uk.groups.yahoo.com/group/torbay_freecycle

APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com

 


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of g0jxn.jim@...
Sent: 01 November 2013 06:50
To: aprsisce@...
Subject: [aprsisce] DF1CHB is Air Mobile

 

 

Hi Guys

 

On the 1st October Cyril, DF1CHB, is flying between Dusseldof and the Canaries in his 747 and will be Air Mobile with beacons on 10m, 17m, 20m & 30m. He cannot engage in message exchanges because of his work load and space limitations in the cockpit.

 

Go to the News section of www.net104.org.uk for details and reports and for QRG information go to the Frequencies section. There is also a live 20m map.

 

There are also reports and maps relating to his earlier flights to Kosovo in the News section.

 

73

 

Jim, G0JXN/MB7UXN


DF1CHB is Air Mobile

G0JXN Jim
 

Hi Guys

 

On the 1st October Cyril, DF1CHB, is flying between Dusseldof and the Canaries in his 747 and will be Air Mobile with beacons on 10m, 17m, 20m & 30m. He cannot engage in message exchanges because of his work load and space limitations in the cockpit.

 

Go to the News section of www.net104.org.uk for details and reports and for QRG information go to the Frequencies section. There is also a live 20m map.

 

There are also reports and maps relating to his earlier flights to Kosovo in the News section.

 

73

 

Jim, G0JXN/MB7UXN


Re: WIKI Issues

ronnies07@...
 

That's fine, Cloudfront is a distributed hosting service run by amazon that provides distributed hosting. This way a server outage doesn't make the site inaccessible. Many sites are using this, looks like WikiDot has jumped onto the bandwagon as well.



---In aprsisce@..., <aprsisce@...> wrote:

Ok thanks for that. Not for me so I need a reinstall it seems

For info I am getting redirected to a site d3g0gp88917kc0.cloudfront.net

Seems all my anti virus and malware has failed. I am currently blocked from some site due to it

Lookis like a complete reinstall to get rid of it

 

Steve Daniels

Amateur Radio Callsign G6UIM

 


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of M1ARF
Sent: 30 October 2013 23:47
To: aprsisce@...
Subject: Re: [aprsisce] WIKI Issues

 

 

Works ok for me.

Derek M1ARF

 


From: Steve Daniels <steve@...>
To: aprsisce@...
Sent: Wednesday, 30 October 2013, 23:34
Subject: [aprsisce] WIKI Issues

 

 

I am experiencing issues getting on the WIKI am getting redirected to a cloudfront.net Amazon site. Although thats not working so I just have the browser sat wating.

Not sure if I have a virus, the WIKI has a virus, or if it’s due to a failed server trying to give me an advert.

This is happening on other sites as well but not all. And it’s the same address that I am being redirected to

Can someone with the ability to check without possibly getting infected check things out on the WIKI.

 

Steve Daniels

Amateur Radio Callsign G6UIM

 

 

 

 


Re: Lat and long reading

Lynn Deffenbaugh
 

 Nope, I don't even have a formatter that would show that yet.  It's always been APRS-standard format of ddmm.mm dddmm.mm but sometimes, depending on !DAO! extensions, it may show more fractional minute digits.

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

On 10/30/2013 9:31 PM, greg andersen wrote:

I believe it used to show Lat and Long,  degree, minute, seconds.

 

From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Adam Mahnke
Sent: Tuesday, October 29, 2013 2:45 AM
To: aprsisce@...
Subject: RE: [aprsisce] Lat and long reading

 

 

What are you expecting to see?

Looks normal to me.

DDmm.mm

Adam
 KC2ANT

--- Original Message ---

From: "greg andersen" <gwandersen@...>
Sent: October 29, 2013 1:22 AM
To: aprsisce@...
Subject: [aprsisce] Lat and long reading

 

Lynn,

 

Lynn,

 

I’m stumped.   My lat and long readings aren’t showing correctly. Here’s what shows when I click on an icon.

 

Tks,

 

greg

 

 

 

Chandler VHF I-Gate

Mobiles WIDE1-1,WIDE2-1  KB7KFC@...

 

Sym: IGate (deprec) (I&)

App: UIview 32 bit (25N)

Cap: IGATE,MSG_CNT=7,LOC_CNT=54

PHG: 25w 80ft 9dBi Omni (22mi)

3/32 Paths (2Kb)

Hearing(30m): KB0BWG-1 W7MOT-3

Packet(13s):N7UV-9 E 21.7 KB0BWG-1 SW 22.1 KB7KFC-1 Total:43.8mi

I+G: 8+11

FromCtr: 20.8mi SW

FromME: 21.3mi SW (236º)

GridSquare: DM43bf

3314.01N 11151.96W

Time: 00-28 05:16:00z

2013-10-29 05:20:24 (21s)

TCPIP*

IGATE[11] TCP RemRF

 

From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Monday, October 28, 2013 5:42 PM
To: aprsisce@...
Subject: Re: [aprsisce] Returning help

 

 

See the Wiki at http://aprsisce.wikidot.com/  Especially:

http://aprsisce.wikidot.com/initial-startup

and

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

and maybe even

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

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

On 10/28/2013 8:12 PM, kb3cxq@... wrote:

I have returned to APRS-IS.  Unfortunately, I do not remember how to set it all up.  I got it partially working, but I cannot make it transmit nor do I remember what my passcode was.

 

Is there a getting started file I can refer to?  Where can I get my passcode again?

 

Thanks,

Shaun / KB3CXQ

 


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3615/6786 - Release Date: 10/27/13


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3615/6786 - Release Date: 10/27/13



Re: Lat and long reading

greg andersen <gwandersen@...>
 

I believe it used to show Lat and Long,  degree, minute, seconds.

 

From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Adam Mahnke
Sent: Tuesday, October 29, 2013 2:45 AM
To: aprsisce@...
Subject: RE: [aprsisce] Lat and long reading

 

 

What are you expecting to see?

Looks normal to me.

DDmm.mm

Adam
 KC2ANT

--- Original Message ---

From: "greg andersen" <gwandersen@...>
Sent: October 29, 2013 1:22 AM
To: aprsisce@...
Subject: [aprsisce] Lat and long reading

 

Lynn,

 

Lynn,

 

I’m stumped.   My lat and long readings aren’t showing correctly. Here’s what shows when I click on an icon.

 

Tks,

 

greg

 

 

 

Chandler VHF I-Gate

Mobiles WIDE1-1,WIDE2-1  KB7KFC@...

 

Sym: IGate (deprec) (I&)

App: UIview 32 bit (25N)

Cap: IGATE,MSG_CNT=7,LOC_CNT=54

PHG: 25w 80ft 9dBi Omni (22mi)

3/32 Paths (2Kb)

Hearing(30m): KB0BWG-1 W7MOT-3

Packet(13s):N7UV-9 E 21.7 KB0BWG-1 SW 22.1 KB7KFC-1 Total:43.8mi

I+G: 8+11

FromCtr: 20.8mi SW

FromME: 21.3mi SW (236º)

GridSquare: DM43bf

3314.01N 11151.96W

Time: 00-28 05:16:00z

2013-10-29 05:20:24 (21s)

TCPIP*

IGATE[11] TCP RemRF

 

From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: Monday, October 28, 2013 5:42 PM
To: aprsisce@...
Subject: Re: [aprsisce] Returning help

 

 

See the Wiki at http://aprsisce.wikidot.com/  Especially:

http://aprsisce.wikidot.com/initial-startup

and

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

and maybe even

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

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

On 10/28/2013 8:12 PM, kb3cxq@... wrote:

I have returned to APRS-IS.  Unfortunately, I do not remember how to set it all up.  I got it partially working, but I cannot make it transmit nor do I remember what my passcode was.

 

Is there a getting started file I can refer to?  Where can I get my passcode again?

 

Thanks,

Shaun / KB3CXQ

 


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3615/6786 - Release Date: 10/27/13


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3615/6786 - Release Date: 10/27/13


Re: WIKI Issues

Greg Depew
 

Steve, I can get to the wiki no problem, but both links you gave for cloudfront will not load. Hope that helps?

Greg KB3KBR Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Steve Daniels <steve@daniels270.eclipse.co.uk>
Date: Thu, 31 Oct 2013 00:30:35
To: <aprsisce@yahoogroups.com>
Subject: RE: [aprsisce] WIKI Issues

 





Ok thanks for that. Not for me so I need a reinstall it seems
For info I am getting redirected to a site d3g0gp88917kc0.cloudfront.net
Seems all my anti virus and malware has failed. I am currently blocked from some site due to it
Lookis like a complete reinstall to get rid of it
 

Steve Daniels
Amateur Radio Callsign G6UIM
 


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

From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of M1ARF
Sent: 30 October 2013 23:47
To: aprsisce@yahoogroups.com
Subject: Re: [aprsisce] WIKI Issues
 
 




Works ok for me.

Derek M1ARF

 




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

From: Steve Daniels <steve@daniels270.eclipse.co.uk>
To: aprsisce@yahoogroups.com
Sent: Wednesday, 30 October 2013, 23:34
Subject: [aprsisce] WIKI Issues

 


 


I am experiencing issues getting on the WIKI am getting redirected to a cloudfront.net Amazon site. Although thats not working so I just have the browser sat wating.

Not sure if I have a virus, the WIKI has a virus, or if it's due to a failed server trying to give me an advert.

This is happening on other sites as well but not all. And it's the same address that I am being redirected to

Can someone with the ability to check without possibly getting infected check things out on the WIKI.

 

Steve Daniels

Amateur Radio Callsign G6UIM


Re: WIKI Issues

sbd sbd
 

Ok thanks for that. Not for me so I need a reinstall it seems

For info I am getting redirected to a site d3g0gp88917kc0.cloudfront.net

Seems all my anti virus and malware has failed. I am currently blocked from some site due to it

Lookis like a complete reinstall to get rid of it

 

Steve Daniels

Amateur Radio Callsign G6UIM

 


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of M1ARF
Sent: 30 October 2013 23:47
To: aprsisce@...
Subject: Re: [aprsisce] WIKI Issues

 

 

Works ok for me.

Derek M1ARF

 


From: Steve Daniels
To: aprsisce@...
Sent: Wednesday, 30 October 2013, 23:34
Subject: [aprsisce] WIKI Issues

 

 

I am experiencing issues getting on the WIKI am getting redirected to a cloudfront.net Amazon site. Although thats not working so I just have the browser sat wating.

Not sure if I have a virus, the WIKI has a virus, or if it’s due to a failed server trying to give me an advert.

This is happening on other sites as well but not all. And it’s the same address that I am being redirected to

Can someone with the ability to check without possibly getting infected check things out on the WIKI.

 

Steve Daniels

Amateur Radio Callsign G6UIM

 

 

 

 


Re: WIKI Issues

M1ARF <m1arf@...>
 

Works ok for me.

Derek M1ARF


From: Steve Daniels
To: aprsisce@...
Sent: Wednesday, 30 October 2013, 23:34
Subject: [aprsisce] WIKI Issues



I am experiencing issues getting on the WIKI am getting redirected to a cloudfront.net Amazon site. Although thats not working so I just have the browser sat wating.
Not sure if I have a virus, the WIKI has a virus, or if it’s due to a failed server trying to give me an advert.
This is happening on other sites as well but not all. And it’s the same address that I am being redirected to
Can someone with the ability to check without possibly getting infected check things out on the WIKI.
 
Steve Daniels
Amateur Radio Callsign G6UIM
 
 





WIKI Issues

sbd sbd
 

I am experiencing issues getting on the WIKI am getting redirected to a cloudfront.net Amazon site. Although thats not working so I just have the browser sat wating.

Not sure if I have a virus, the WIKI has a virus, or if it’s due to a failed server trying to give me an advert.

This is happening on other sites as well but not all. And it’s the same address that I am being redirected to

Can someone with the ability to check without possibly getting infected check things out on the WIKI.

 

Steve Daniels

Amateur Radio Callsign G6UIM

 

 


Re: KPC-3 with aprsisce problem locking into kiss mode

Dave VA3NSC
 

What I did wrong was I didn't delete the ports before I tried Simply Kiss Mode,once I deleted them and re did it in simply kiss mode it works and I can shut the tnc or program off and on and it still works! And it doesn't unlock from kiss...now to set up the digipeater and it can go to the tower site...thanks again everyone!

 



---In aprsisce@..., <va3nsc@...> wrote:

Now it finally works in SimpleKiss mode...thanks Rob! And thanks to everyone for there input and help. Dave



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

If you are using OPEN and CLOSE commands, you are defeating the purpose.
Your initial post said you want it to remain in KISS mode across resets.
As Fred said -
   If you want it to remain in KISS between "reboots", use Simple(KISS) - BLANK Open and Close
   If you want to "put the TNC in KISS mode on start of APRS, then you need the commands in the OPEN and CLOSE.
 
KEEP in KISS:
1. open APRSISce/32 and delete port (must be DISABLED)
2. Create new "Simple(KISS) port for KPC3
3. Disable NEW KPC3 port (probably won't connect anyway)
4. Open terminal program and connect to KPC3
5. ISSUE commands to place TNC in KISS mode
     cmd: INT KISS<enter>
     cmd: reset<enter>
6.  Check received data for KISS format CO {HEX CODE} CO
7. Close terminal program
8. Go back to APRSISce/32 and enable port
 
 
 
Robert Giuliano
KB8RCO


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

From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
To: aprsisce@...
Sent: Wednesday, October 30, 2013 12:52 PM
Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode

 
See http://aprsisce.wikidot.com/tnc-kpc-3 and pick up an entire known-to-have-worked set of <Open/CloseCmd>s from there.

Once you have those in place, check Enables / Logging / File Enabled and Enables / Logging / Port(<YourPortName>) and then disable, wait, and re-enable the port then wait for some packets to come in.  The Port(<YourPortName>) should contain some diagnostics that should show the interaction with the TNC.

These commands will put the TNC into and out of KISS mode whenever the port is enabled/disabled or APRSISCE/32 is executed/closed.  The only thing that locking the TNC into KISS mode does is to ensure that if the TNC drops power or otherwise resets while APRSISCE/32 is running, the port will continue working.  With switching it into and out of KISS mode, a TNC reset will drop it out of KISS and APRSISCE/32 will quit getting packets until the port or program is bounced.

This is no worse than using the internal TNC in a Kenwood radio in KISS mode because those radios don&apos;t even provide a way to lock into KISS.  If the TNC or radio resets, you need to disable/enable the port in APRSISCE/32 to get it back into KISS mode for operations.

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

On 10/30/2013 12:35 PM, va3nsc@... wrote:
Thats what I thought Larry thanks for the input...this has me baffled
Dave
 


---In aprsisce@..., mailto:k6kusman@... wrote:

I think the command to put it into kiss mode is "kiss on" then there is another command to make it stay in kiss mode. I just can&apos;t for the life of me remember what it is. But there is a command that set&apos;s it to keep the kiss mode on even after reboot. It&apos;s some command that set&apos;s it to a perm prameter that will survive power off or reboot.
Larry Ellsworth
          K6KUS
    Irlp Node 7413
Echolink Node 524805
  Allstar Link 27775

--------------------------------------------
On Wed, 10/30/13, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:

Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode
To: aprsisce@...
Date: Wednesday, October 30, 2013, 9:27 AM
















 












Great catch
Patrick!  You are correct
that one of the two following <CloseCmd>s will
knock a KPC-3
out of KISS mode:



<CloseCmd>^192^255^192~!!0</CloseCmd>

<CloseCmd>^C^C^C~!!0</CloseCmd>


Dave, If you have these in your APRSIS32.XML file, and
you want
your KPC-3 to stay in KISS mode when APRSISCE/32
isn&apos;t running,
then you need to remove them or replace them with the
following
No-Op.



<CloseCmd>~!!0</CloseCmd>



The other <CloseCmd>s listed below are
Kenwood-specific
commands that probably shouldn&apos;t be firing at
anyone&apos;s KPC-3
device!



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



On 10/30/2013 10:51 AM, Patrick Wood wrote:






Doesn&apos;t
that close command take it out
of KISS?  If you want to leave it in kiss,
put it into kiss
mode then use a simple kiss port.



p




On Oct 30, 2013 10:43 AM, <va3nsc@...>
wrote:







Thats how its set Adam,I have some other
tnc&apos;s here I will
try another and see if it does the same thing
with
them...thanks for responding. Dave

 




---In aprsisce@...,
mailto:kc2ant@... wrote:




Someone else (Jeremy
can&apos;t remember the
call sign) used this for the port config
with a
9612.



<!--RFPort[0]-->

<RFPort
Name="KAM">

<Protocol>KISS</Protocol>

<Device>COM4:9600,N,8,1</Device>

<RfBaud>1200</RfBaud>

<OpenCmd>^M~</OpenCmd>

<OpenCmd>^M~</OpenCmd>

<OpenCmd>XFLOW
ON!!0</OpenCmd>

<OpenCmd>FULLDUP
OFF!!0</OpenCmd>

<OpenCmd>INT
KISS!!0</OpenCmd>

<OpenCmd>RESET!!0</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>1</Enabled>

<XmitEnabled>1</XmitEnabled>

<ProvidesNMEA>0</ProvidesNMEA>

<RFtoISEnabled>1</RFtoISEnabled>

<IStoRFEnabled>1</IStoRFEnabled>

<MyCallNot3rd>0</MyCallNot3rd>

<BeaconingEnabled>1</BeaconingEnabled>

<BeaconPath></BeaconPath>

<BulletinObjectEnabled>0</BulletinObjectEnabled>

<DXEnabled>0</DXEnabled>

<DXPath></DXPath>

<MessagesEnabled>1</MessagesEnabled>

<MessagePath></MessagePath>

<TelemetryEnabled>0</TelemetryEnabled>

<TelemetryPath></TelemetryPath>

<!--DigiXform-->

</RFPort>

<!--RFPort[0]-->



I know that I
managed to lock my 9612 into KISS
but I don&apos;t
remember how I did
it.



Adam
KC2ANT



PS Yes I know
the KPC3+ is a different model,
but I&apos;ve found
a lot of the commands to be the
same/similar
for programming.




To: aprsisce@...

From: kj4erj@...

Date: Wed, 30 Oct 2013 10:00:59
-0400

Subject: Re: [aprsisce] KPC-3 with
aprsisce
problem locking into kiss mode



 




Put a new battery in your
KPC-3.  It
sounds like it is resetting
to factory
defaults every time you
power it down.



Try setting some other
setting (like
MYCALL), turn it off, wait a
bit, turn
it on and see if you MYCALL
has also
disappeared.



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



On
10/30/2013 9:26
AM, va3nsc@...
wrote:



Heres the prob
folks, I have
a KPC-3 I am trying to set
up to work
with aprsisce. For some
reason it wont
stay locked into kiss mode.
I have used
pacterm to put it into kiss
mode as
follows..cmd intface it
comes up as
newuser so I cmd intface
kiss then
enter,it shows in kiss mode
so I cmd
reset.  Fire up
aprsisce and the tnc
works fine,but if I turn the
tnc off and
back on again,refire the
program it will
not connect. I check pacterm
again and
intface is in terminal
mode..any ideas
on how to keep it locked
into kiss mode?
Dave




Re: KPC-3 with aprsisce problem locking into kiss mode

Dave VA3NSC
 

Now it finally works in SimpleKiss mode...thanks Rob! And thanks to everyone for there input and help. Dave



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

If you are using OPEN and CLOSE commands, you are defeating the purpose.
Your initial post said you want it to remain in KISS mode across resets.
As Fred said -
   If you want it to remain in KISS between "reboots", use Simple(KISS) - BLANK Open and Close
   If you want to "put the TNC in KISS mode on start of APRS, then you need the commands in the OPEN and CLOSE.
 
KEEP in KISS:
1. open APRSISce/32 and delete port (must be DISABLED)
2. Create new "Simple(KISS) port for KPC3
3. Disable NEW KPC3 port (probably won't connect anyway)
4. Open terminal program and connect to KPC3
5. ISSUE commands to place TNC in KISS mode
     cmd: INT KISS<enter>
     cmd: reset<enter>
6.  Check received data for KISS format CO {HEX CODE} CO
7. Close terminal program
8. Go back to APRSISce/32 and enable port
 
 
 
Robert Giuliano
KB8RCO


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

From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
To: aprsisce@...
Sent: Wednesday, October 30, 2013 12:52 PM
Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode

 
See http://aprsisce.wikidot.com/tnc-kpc-3 and pick up an entire known-to-have-worked set of <Open/CloseCmd>s from there.

Once you have those in place, check Enables / Logging / File Enabled and Enables / Logging / Port(<YourPortName>) and then disable, wait, and re-enable the port then wait for some packets to come in.  The Port(<YourPortName>) should contain some diagnostics that should show the interaction with the TNC.

These commands will put the TNC into and out of KISS mode whenever the port is enabled/disabled or APRSISCE/32 is executed/closed.  The only thing that locking the TNC into KISS mode does is to ensure that if the TNC drops power or otherwise resets while APRSISCE/32 is running, the port will continue working.  With switching it into and out of KISS mode, a TNC reset will drop it out of KISS and APRSISCE/32 will quit getting packets until the port or program is bounced.

This is no worse than using the internal TNC in a Kenwood radio in KISS mode because those radios don&apos;t even provide a way to lock into KISS.  If the TNC or radio resets, you need to disable/enable the port in APRSISCE/32 to get it back into KISS mode for operations.

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

On 10/30/2013 12:35 PM, va3nsc@... wrote:
Thats what I thought Larry thanks for the input...this has me baffled
Dave
 


---In aprsisce@..., mailto:k6kusman@... wrote:

I think the command to put it into kiss mode is "kiss on" then there is another command to make it stay in kiss mode. I just can&apos;t for the life of me remember what it is. But there is a command that set&apos;s it to keep the kiss mode on even after reboot. It&apos;s some command that set&apos;s it to a perm prameter that will survive power off or reboot.
Larry Ellsworth
          K6KUS
    Irlp Node 7413
Echolink Node 524805
  Allstar Link 27775

--------------------------------------------
On Wed, 10/30/13, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:

Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode
To: aprsisce@...
Date: Wednesday, October 30, 2013, 9:27 AM
















 












Great catch
Patrick!  You are correct
that one of the two following <CloseCmd>s will
knock a KPC-3
out of KISS mode:



<CloseCmd>^192^255^192~!!0</CloseCmd>

<CloseCmd>^C^C^C~!!0</CloseCmd>


Dave, If you have these in your APRSIS32.XML file, and
you want
your KPC-3 to stay in KISS mode when APRSISCE/32
isn&apos;t running,
then you need to remove them or replace them with the
following
No-Op.



<CloseCmd>~!!0</CloseCmd>



The other <CloseCmd>s listed below are
Kenwood-specific
commands that probably shouldn&apos;t be firing at
anyone&apos;s KPC-3
device!



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



On 10/30/2013 10:51 AM, Patrick Wood wrote:






Doesn&apos;t
that close command take it out
of KISS?  If you want to leave it in kiss,
put it into kiss
mode then use a simple kiss port.



p




On Oct 30, 2013 10:43 AM, <va3nsc@...>
wrote:







Thats how its set Adam,I have some other
tnc&apos;s here I will
try another and see if it does the same thing
with
them...thanks for responding. Dave

 




---In aprsisce@...,
mailto:kc2ant@... wrote:




Someone else (Jeremy
can&apos;t remember the
call sign) used this for the port config
with a
9612.



<!--RFPort[0]-->

<RFPort
Name="KAM">

<Protocol>KISS</Protocol>

<Device>COM4:9600,N,8,1</Device>

<RfBaud>1200</RfBaud>

<OpenCmd>^M~</OpenCmd>

<OpenCmd>^M~</OpenCmd>

<OpenCmd>XFLOW
ON!!0</OpenCmd>

<OpenCmd>FULLDUP
OFF!!0</OpenCmd>

<OpenCmd>INT
KISS!!0</OpenCmd>

<OpenCmd>RESET!!0</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>1</Enabled>

<XmitEnabled>1</XmitEnabled>

<ProvidesNMEA>0</ProvidesNMEA>

<RFtoISEnabled>1</RFtoISEnabled>

<IStoRFEnabled>1</IStoRFEnabled>

<MyCallNot3rd>0</MyCallNot3rd>

<BeaconingEnabled>1</BeaconingEnabled>

<BeaconPath></BeaconPath>

<BulletinObjectEnabled>0</BulletinObjectEnabled>

<DXEnabled>0</DXEnabled>

<DXPath></DXPath>

<MessagesEnabled>1</MessagesEnabled>

<MessagePath></MessagePath>

<TelemetryEnabled>0</TelemetryEnabled>

<TelemetryPath></TelemetryPath>

<!--DigiXform-->

</RFPort>

<!--RFPort[0]-->



I know that I
managed to lock my 9612 into KISS
but I don&apos;t
remember how I did
it.



Adam
KC2ANT



PS Yes I know
the KPC3+ is a different model,
but I&apos;ve found
a lot of the commands to be the
same/similar
for programming.




To: aprsisce@...

From: kj4erj@...

Date: Wed, 30 Oct 2013 10:00:59
-0400

Subject: Re: [aprsisce] KPC-3 with
aprsisce
problem locking into kiss mode



 




Put a new battery in your
KPC-3.  It
sounds like it is resetting
to factory
defaults every time you
power it down.



Try setting some other
setting (like
MYCALL), turn it off, wait a
bit, turn
it on and see if you MYCALL
has also
disappeared.



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



On
10/30/2013 9:26
AM, va3nsc@...
wrote:



Heres the prob
folks, I have
a KPC-3 I am trying to set
up to work
with aprsisce. For some
reason it wont
stay locked into kiss mode.
I have used
pacterm to put it into kiss
mode as
follows..cmd intface it
comes up as
newuser so I cmd intface
kiss then
enter,it shows in kiss mode
so I cmd
reset.  Fire up
aprsisce and the tnc
works fine,but if I turn the
tnc off and
back on again,refire the
program it will
not connect. I check pacterm
again and
intface is in terminal
mode..any ideas
on how to keep it locked
into kiss mode?
Dave




Re: KPC-3 with aprsisce problem locking into kiss mode

Lynn Deffenbaugh
 

You are correct about the Quiet Time behavior, but in some areas of low APRS activity, it's pretty hard to determine a good value.  I use 300 seconds here, but I rarely go a single minute without receiving something on the port.

I had considered attempting to detect a non-KISS mode, but I'm not convinced I could do it reliably.  There's not supposed to be any data outside the s, but I hesitate to cycle the port disable/enable and associated s just because something didn't smell right.

That said, I do have plans to implement a KPC-3+ reset timer feature that will do exactly that (cycle the port) every N hours to recover from the packet delay issue described at

http://blog.aprs.fi/2011/03/kantronics-kpc3-considered-harmful.html

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

On 10/30/2013 2:34 PM, Steve Daniels wrote:

I thought if you set a quiet time other than 0 that APRSIS32 would cycle the port if nothing was received So if a TNC dropped out of KISS after a time it would get sent the open commands again.

If not would it be hard to detect non KISS mode on a KISS port and resend the open commands?

 

Steve Daniels

Amateur Radio Callsign G6UIM

Torbay Freecycle  Owner

http://uk.groups.yahoo.com/group/torbay_freecycle

APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com

 


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: 30 October 2013 16:52
To: aprsisce@...
Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode

 

 

See http://aprsisce.wikidot.com/tnc-kpc-3 and pick up an entire known-to-have-worked set of s from there.

Once you have those in place, check Enables / Logging / File Enabled and Enables / Logging / Port() and then disable, wait, and re-enable the port then wait for some packets to come in.  The Port() should contain some diagnostics that should show the interaction with the TNC.

These commands will put the TNC into and out of KISS mode whenever the port is enabled/disabled or APRSISCE/32 is executed/closed.  The only thing that locking the TNC into KISS mode does is to ensure that if the TNC drops power or otherwise resets while APRSISCE/32 is running, the port will continue working.  With switching it into and out of KISS mode, a TNC reset will drop it out of KISS and APRSISCE/32 will quit getting packets until the port or program is bounced.

This is no worse than using the internal TNC in a Kenwood radio in KISS mode because those radios don't even provide a way to lock into KISS.  If the TNC or radio resets, you need to disable/enable the port in APRSISCE/32 to get it back into KISS mode for operations.

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

On 10/30/2013 12:35 PM, va3nsc@... wrote:

Thats what I thought Larry thanks for the input...this has me baffled
Dave

 



---In aprsisce@..., wrote:

I think the command to put it into kiss mode is "kiss on" then there is another command to make it stay in kiss mode. I just can't for the life of me remember what it is. But there is a command that set's it to keep the kiss mode on even after reboot. It's some command that set's it to a perm prameter that will survive power off or reboot.
Larry Ellsworth
          K6KUS
    Irlp Node 7413
Echolink Node 524805
  Allstar Link 27775

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

On Wed, 10/30/13, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:

Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode
To: aprsisce@...
Date: Wednesday, October 30, 2013, 9:27 AM
















 












Great catch
Patrick!  You are correct
that one of the two following s will
knock a KPC-3
out of KISS mode:



^192^255^192~!!0

^C^C^C~!!0


Dave, If you have these in your APRSIS32.XML file, and
you want
your KPC-3 to stay in KISS mode when APRSISCE/32
isn't running,
then you need to remove them or replace them with the
following
No-Op.



~!!0



The other s listed below are
Kenwood-specific
commands that probably shouldn't be firing at
anyone's KPC-3
device!



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



On 10/30/2013 10:51 AM, Patrick Wood wrote:






Doesn't
that close command take it out
of KISS?  If you want to leave it in kiss,
put it into kiss
mode then use a simple kiss port.



p




On Oct 30, 2013 10:43 AM, <va3nsc@...>
wrote:







Thats how its set Adam,I have some other
tnc's here I will
try another and see if it does the same thing
with
them...thanks for responding. Dave

 




---In aprsisce@...,
wrote:




Someone else (Jeremy
can't remember the
call sign) used this for the port config
with a
9612.





Name="KAM">

KISS

COM4:9600,N,8,1

1200

^M~

^M~

XFLOW
ON!!0

FULLDUP
OFF!!0

INT
KISS!!0

RESET!!0

^192^255^192~!!0

^C^C^C~!!0

TC
1!TS 1

TN
2,0!TN
2,0

0

1

1

0

1

1

0

1



0

0



1



0











I know that I
managed to lock my 9612 into KISS
but I don't
remember how I did
it.



Adam
KC2ANT



PS Yes I know
the KPC3+ is a different model,
but I've found
a lot of the commands to be the
same/similar
for programming.




To: aprsisce@...

From: kj4erj@...

Date: Wed, 30 Oct 2013 10:00:59
-0400

Subject: Re: [aprsisce] KPC-3 with
aprsisce
problem locking into kiss mode



 




Put a new battery in your
KPC-3.  It
sounds like it is resetting
to factory
defaults every time you
power it down.



Try setting some other
setting (like
MYCALL), turn it off, wait a
bit, turn
it on and see if you MYCALL
has also
disappeared.



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



On
10/30/2013 9:26
AM, va3nsc@...
wrote:



Heres the prob
folks, I have
a KPC-3 I am trying to set
up to work
with aprsisce. For some
reason it wont
stay locked into kiss mode.
I have used
pacterm to put it into kiss
mode as
follows..cmd intface it
comes up as
newuser so I cmd intface
kiss then
enter,it shows in kiss mode
so I cmd
reset.  Fire up
aprsisce and the tnc
works fine,but if I turn the
tnc off and
back on again,refire the
program it will
not connect. I check pacterm
again and
intface is in terminal
mode..any ideas
on how to keep it locked
into kiss mode?
Dave

 



Re: Message acks

n5dtx
 

Very interesting Lynn, all kinds of great experiments come to mind with your post.  I am currently running my 30m HF instance with two separate antennas that feed two instances of UZ7HO Soundmodem into APRSIS32.   The original antenna looks north/south, and in July I added the second antenna that looks east/west.

You Florida and California guys were rarely ever read here before I added the second antenna, but I had plenty of Canada and Central America/Mexico.  With the addition of the second antenna, I now read the east/west coasts regularly and I have even received several hits from France, Germany, Spain, and a few folks sailing in the Atlantic.

I have some inherent latencies somewhere in my setup that I have not been able to overcome.  I read RF direct approximately 10 to 20 times more HF stations than I ever gate to APRSIS. I don't really see it as a problem as those stations get gated elsewhere, but I tend to be the gate of last resort if they are not heard anywhere else.  As of this writing, APRS.FI is showing that I have gated KJ4ERJ-2 five times this month, but you are in my rf direct log well over 100 times since you brought your 30m station back online.

I have always configured my APRSIS32 paths to stay on permanently to visualize the traffic and it has been a real kick to see the additional east/west traffic since adding the second antenna July.


Graham

N5DTX



---In aprsisce@..., <aprsisce@...> wrote:

On 10/29/2013 5:53 PM, Denis wrote:
I just sent you a message on HF and your station sent about 8 ACKS back 
in one transmission.

Yes, and thanks for bringing that to my attention.  My KJ4ERJ-2 instance is an interesting test platform for 30m HF APRS.  Here's the deal...

The APRS spec says that clients should send an ack for each copy of a message that is received.  There is no specification for duplicates, and in fact, when you think about it, just because a client has already acked a given message doesn't mean that the sender received the ack, so if the message is received again, even though it is already known, it's likely a retry and therefore a new ack should be sent to satisfy the originator.

The spec (somewhere) further recommends that a double-ack be fired on message reception on RF.   This "improves" the chances that the ack is received by the sending station.

APRSISCE/32 is coded to do all of the above.  Acks are triggered for every reception of a message, regardless if it was received and acked before, and a second ck is fired on RF ports (RF-Only on the second one).

Enter KJ4ERJ-2, my 30m HF APRS test instance.  I have it configured with the following ports.

DireWolf - via TCP/IP and an AGW-type port
DireWolf KISS - via TCP/IP and a KISS-type port
UZ7HO's SoundModem which is running both channels offset +/- 25hz (1675 and 1725 configured)

Both DireWolf and UZ7HO are talking to the same "SoundCard" which is actually a SignaLink USB connected to a single iCom 706 tuned to 10.147.60 USB.

So for every packet received, KJ4ERJ-2 receives up to FOUR copies of it, provided that it was decoded by both DireWolf and both channels of UZ7HO.  Some packets are slightly off frequency and are only decoded by one channel of UZ7HO, so I only get three copies of those packets.  And others, for various reasons that I'm still observing, are only decoded by DireWolf or only by UZ7HO, one or both ports.

But back to the point of this posting...  Couple receiving four copies of an incoming message with the double-ack and put it all in a near instantaneous time frame and you have 8 acks being transmitted in a single burst.  These are all sent via the first (25hz low) channel of UZ7HO since I have both DireWolf ports Receive-Only because I don't have any COMM ports to hand it for PTT and I haven't seen how to configure DireWolf for VOX which is what the SignaLink USB looks like.  UZ7HO handles transmitting through the SignaLink with aplomb.

So, to "fix" this non-bug (since it is WAD - Working As Designed and only occurs on multiple ports on a single frequency) redundancy requires the following:

1) Send acks only on the port from which a message was received along with APRS-IS (if messaging is enabled).  This requires that APRSISCE/32 internally track the reception port.  Acks are currently issued after all incoming has merged into a single packet flow and they no longer "know" which port they came from, only if it was RF or -IS.  Also, APRSISCE/32 doesn't currently have the internal ability to target outbound packets (like acks) to a specific RF port.  It can do -IS vs RF, but not target a specific RF port.  This is all due to my naivity when implementing RF ports, I never imagined multiple ports into a single APRSISCE/32 instance and still recommend against it for most installations, hence this poll http://tinyurl.com/l82p273 (see below).

2) Support individual configuration and enable flags for multi-port devices like stereo SignalLinks.  Without this, acks are not able to go out the "second" port of a SignaLink.

I've got this all in mind, but am currently trying to stabilize APRSISCE/32 development loose ends so that I can release a new stable, general release.  Once that gets out the door, I can rip into the internals to try to do some of this stuff.

But I was truly amazed last night at how smoothly the QSO flowed with HF/RF only!  (See http://aprs.fi/?c=message&call=KJ4ERJ-2 from 10/29 17:49 through 23:18)  Thanks for that opportunity., outside of when my radio locked in transmit for more seconds that I was expecting due to the ack burst(s)!  You should have seen my mouse ripping around the screen trying to figure out what locked up.  My finger was actually on the 706's power switch when PTT finally released on its own.  I just got the radio back from repair (blown finals, SWR-sensing diodes, and the stupid pad corrosion causing it to not power up (http://www.n1eq.com/tech/page_03.html)), so I really didn't want to do something stupid within the first week of operation!

Most RF installations (hopefully) aren't running multiple ports to a single radio, so they won't suffer from the packet multiplication effect on message reception.  Now that I'm aware of the "feature", I'll try to remember to disable the DireWolf ports to reduce the duplications when in a QSO.  I normally keep them all enabled to compare the decode capabilities of the various soundcard soft TNCs.

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

PS.  On 2m RF-only, you'll see similar behavior if your station receives an incoming message and shortly thereafter a digipeated copy of the message.  Double-acks will be sent for each reception, but 1200 baud is so much faster than 300 baud that the behavior has not been noticed, or at least, not reported.

PPS.  The Poll mentioned above (http://tinyurl.com/l82p273) was:

How many concurrently active RF ports do you use per APRSISCE/32 instance?
ldeffenb
 
55 Votes
 
August 3, 2012
 
Never end
Zero. I use APRSISCE/32 on the APRS-IS only.
11% (6)
One. I only have one radio/TNC/interface.
55% (30)
One. I run separate instances for each radio/TNC/interface/frequency.
24% (13)
Two or more, and I'm anxious for cross-port repeating too!
11% (6)
RF? APRS does RF? I thought it was Internet based.
0% (0)
Other - Details sent to the group.
0% (0


Re: KPC-3 with aprsisce problem locking into kiss mode

Rob Giuliano
 

That would depend on a LOT of factors.
Just because "some data is coming in with out the KISS format, may not mean the port needs resetting.
   One such event might be if you have GPS data coming over the same port and the format of that data.
Something else all together would be a "slow APRS day".
   Although resets due to "true inactivity" probably won't hurt much.
Robert Giuliano
KB8RCO


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

From: Steve Daniels
To: aprsisce@...
Sent: Wednesday, October 30, 2013 2:34 PM
Subject: RE: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode

 
I thought if you set a quiet time other than 0 that APRSIS32 would cycle the port if nothing was received So if a TNC dropped out of KISS after a time it would get sent the open commands again.
If not would it be hard to detect non KISS mode on a KISS port and resend the open commands?
 
Steve Daniels
Amateur Radio Callsign G6UIM
Torbay Freecycle  Owner
APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com/
 
From: aprsisce@... [mailto: aprsisce@... ] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: 30 October 2013 16:52
To: aprsisce@...
Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode
 
 
See http://aprsisce.wikidot.com/tnc-kpc-3 and pick up an entire known-to-have-worked set of s from there.

Once you have those in place, check Enables / Logging / File Enabled and Enables / Logging / Port() and then disable, wait, and re-enable the port then wait for some packets to come in.  The Port(<YourPortName>) should contain some diagnostics that should show the interaction with the TNC.

These commands will put the TNC into and out of KISS mode whenever the port is enabled/disabled or APRSISCE/32 is executed/closed.  The only thing that locking the TNC into KISS mode does is to ensure that if the TNC drops power or otherwise resets while APRSISCE/32 is running, the port will continue working.  With switching it into and out of KISS mode, a TNC reset will drop it out of KISS and APRSISCE/32 will quit getting packets until the port or program is bounced.

This is no worse than using the internal TNC in a Kenwood radio in KISS mode because those radios don&apos;t even provide a way to lock into KISS.  If the TNC or radio resets, you need to disable/enable the port in APRSISCE/32 to get it back into KISS mode for operations.

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

On 10/30/2013 12:35 PM, va3nsc@... wrote:
Thats what I thought Larry thanks for the input...this has me baffled
Dave
 
I think the command to put it into kiss mode is "kiss on" then there is another command to make it stay in kiss mode. I just can&apos;t for the life of me remember what it is. But there is a command that set&apos;s it to keep the kiss mode on even after reboot. It&apos;s some command that set&apos;s it to a perm prameter that will survive power off or reboot.
Larry Ellsworth
          K6KUS
    Irlp Node 7413
Echolink Node 524805
  Allstar Link 27775

--------------------------------------------
On Wed, 10/30/13, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:

Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode
To: aprsisce@...
Date: Wednesday, October 30, 2013, 9:27 AM
















 












Great catch
Patrick!  You are correct
that one of the two following s will
knock a KPC-3
out of KISS mode:



^192^255^192~!!0

^C^C^C~!!0


Dave, If you have these in your APRSIS32.XML file, and
you want
your KPC-3 to stay in KISS mode when APRSISCE/32
isn&apos;t running,
then you need to remove them or replace them with the
following
No-Op.



~!!0



The other s listed below are
Kenwood-specific
commands that probably shouldn&apos;t be firing at
anyone&apos;s KPC-3
device!



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



On 10/30/2013 10:51 AM, Patrick Wood wrote:






Doesn&apos;t
that close command take it out
of KISS?  If you want to leave it in kiss,
put it into kiss
mode then use a simple kiss port.



p




On Oct 30, 2013 10:43 AM, <va3nsc@...>
wrote:







Thats how its set Adam,I have some other
tnc&apos;s here I will
try another and see if it does the same thing
with
them...thanks for responding. Dave

 




---In aprsisce@...,
mailto:kc2ant@... wrote:




Someone else (Jeremy
can&apos;t remember the
call sign) used this for the port config
with a
9612.





Name="KAM">

KISS

COM4:9600,N,8,1

1200

^M~

^M~

XFLOW
ON!!0

FULLDUP
OFF!!0

INT
KISS!!0





^C^C^C~!!0

TC
1!TS 1

TN
2,0!TN
2,0</CloseCmd>

0

1
1
0
1

1

0

1





0



1



0











I know that I
managed to lock my 9612 into KISS
but I don&apos;t
remember how I did
it.



Adam
KC2ANT



PS Yes I know
the KPC3+ is a different model,
but I&apos;ve found
a lot of the commands to be the
same/similar
for programming.




To: aprsisce@...

From: kj4erj@...

Date: Wed, 30 Oct 2013 10:00:59
-0400

Subject: Re: [aprsisce] KPC-3 with
aprsisce
problem locking into kiss mode



 




Put a new battery in your
KPC-3.  It
sounds like it is resetting
to factory
defaults every time you
power it down.



Try setting some other
setting (like
MYCALL), turn it off, wait a
bit, turn
it on and see if you MYCALL
has also
disappeared.



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



On
10/30/2013 9:26
AM, va3nsc@...
wrote:



Heres the prob
folks, I have
a KPC-3 I am trying to set
up to work
with aprsisce. For some
reason it wont
stay locked into kiss mode.
I have used
pacterm to put it into kiss
mode as
follows..cmd intface it
comes up as
newuser so I cmd intface
kiss then
enter,it shows in kiss mode
so I cmd
reset.  Fire up
aprsisce and the tnc
works fine,but if I turn the
tnc off and
back on again,refire the
program it will
not connect. I check pacterm
again and
intface is in terminal
mode..any ideas
on how to keep it locked
into kiss mode?
Dave
 



Re: KPC-3 with aprsisce problem locking into kiss mode

sbd sbd
 

I thought if you set a quiet time other than 0 that APRSIS32 would cycle the port if nothing was received So if a TNC dropped out of KISS after a time it would get sent the open commands again.

If not would it be hard to detect non KISS mode on a KISS port and resend the open commands?

 

Steve Daniels

Amateur Radio Callsign G6UIM

Torbay Freecycle  Owner

http://uk.groups.yahoo.com/group/torbay_freecycle

APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com

 


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: 30 October 2013 16:52
To: aprsisce@...
Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode

 

 

See http://aprsisce.wikidot.com/tnc-kpc-3 and pick up an entire known-to-have-worked set of s from there.

Once you have those in place, check Enables / Logging / File Enabled and Enables / Logging / Port() and then disable, wait, and re-enable the port then wait for some packets to come in.  The Port() should contain some diagnostics that should show the interaction with the TNC.

These commands will put the TNC into and out of KISS mode whenever the port is enabled/disabled or APRSISCE/32 is executed/closed.  The only thing that locking the TNC into KISS mode does is to ensure that if the TNC drops power or otherwise resets while APRSISCE/32 is running, the port will continue working.  With switching it into and out of KISS mode, a TNC reset will drop it out of KISS and APRSISCE/32 will quit getting packets until the port or program is bounced.

This is no worse than using the internal TNC in a Kenwood radio in KISS mode because those radios don't even provide a way to lock into KISS.  If the TNC or radio resets, you need to disable/enable the port in APRSISCE/32 to get it back into KISS mode for operations.

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

On 10/30/2013 12:35 PM, va3nsc@... wrote:

Thats what I thought Larry thanks for the input...this has me baffled
Dave

 



---In aprsisce@..., wrote:

I think the command to put it into kiss mode is "kiss on" then there is another command to make it stay in kiss mode. I just can't for the life of me remember what it is. But there is a command that set's it to keep the kiss mode on even after reboot. It's some command that set's it to a perm prameter that will survive power off or reboot.
Larry Ellsworth
          K6KUS
    Irlp Node 7413
Echolink Node 524805
  Allstar Link 27775

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

On Wed, 10/30/13, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:

Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode
To: aprsisce@...
Date: Wednesday, October 30, 2013, 9:27 AM
















 












Great catch
Patrick!  You are correct
that one of the two following s will
knock a KPC-3
out of KISS mode:



^192^255^192~!!0

^C^C^C~!!0


Dave, If you have these in your APRSIS32.XML file, and
you want
your KPC-3 to stay in KISS mode when APRSISCE/32
isn't running,
then you need to remove them or replace them with the
following
No-Op.



~!!0



The other s listed below are
Kenwood-specific
commands that probably shouldn't be firing at
anyone's KPC-3
device!



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



On 10/30/2013 10:51 AM, Patrick Wood wrote:






Doesn't
that close command take it out
of KISS?  If you want to leave it in kiss,
put it into kiss
mode then use a simple kiss port.



p




On Oct 30, 2013 10:43 AM, <va3nsc@...>
wrote:







Thats how its set Adam,I have some other
tnc's here I will
try another and see if it does the same thing
with
them...thanks for responding. Dave

 




---In aprsisce@...,
wrote:




Someone else (Jeremy
can't remember the
call sign) used this for the port config
with a
9612.





Name="KAM">

KISS

<Device>COM4:9600,N,8,1

1200

^M~

^M~

XFLOW
ON!!0

FULLDUP
OFF!!0

<OpenCmd>INT
KISS!!0

RESET!!0

^192^255^192~!!0
^C^C^C~!!0

TC
1!TS 1

TN
2,0!TN
2,0

0

1

1

0

1



0
1



0</BulletinObjectEnabled>

0



1</MessagesEnabled>



0











I know that I
managed to lock my 9612 into KISS
but I don't
remember how I did
it.



Adam
KC2ANT



PS Yes I know
the KPC3+ is a different model,
but I've found
a lot of the commands to be the
same/similar
for programming.




To: aprsisce@...

From: kj4erj@...

Date: Wed, 30 Oct 2013 10:00:59
-0400

Subject: Re: [aprsisce] KPC-3 with
aprsisce
problem locking into kiss mode



 




Put a new battery in your
KPC-3.  It
sounds like it is resetting
to factory
defaults every time you
power it down.



Try setting some other
setting (like
MYCALL), turn it off, wait a
bit, turn
it on and see if you MYCALL
has also
disappeared.



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



On
10/30/2013 9:26
AM, va3nsc@...
wrote:



Heres the prob
folks, I have
a KPC-3 I am trying to set
up to work
with aprsisce. For some
reason it wont
stay locked into kiss mode.
I have used
pacterm to put it into kiss
mode as
follows..cmd intface it
comes up as
newuser so I cmd intface
kiss then
enter,it shows in kiss mode
so I cmd
reset.  Fire up
aprsisce and the tnc
works fine,but if I turn the
tnc off and
back on again,refire the
program it will
not connect. I check pacterm
again and
intface is in terminal
mode..any ideas
on how to keep it locked
into kiss mode?
Dave

 


Re: KPC-3 with aprsisce problem locking into kiss mode

Lynn Deffenbaugh
 

I would add a few steps between 6 and 7:

With the terminal emulator still open and connected:

6.2.  Turn off the KPC-3
6.3  Wait a bit
6.4  Turn on the KPC-3
6.5  Wait until you see some KISS-type packets coming in.

If you end up in Cmd: mode after 6.4, then you've definitely got TNC issues and APRSISCE/32's s are completely uninvolved since you only had the terminal emulator talking to the TNC for the entire sequence.

As was alluded to, KISS packets into a terminal emulator will be a burst of non-readable characters followed by a humanly readable payload (unless the packet was a Mic-E).  If you see fully readable packets, then the TNC isn't in KISS mode.  If you don't see anything, then the TNC isn't receiving or decoding anything.  You should see bursts of non-readables interspersed with readable APRS packet payloads.

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

On 10/30/2013 1:05 PM, Rob Giuliano wrote:
If you are using OPEN and CLOSE commands, you are defeating the purpose.
Your initial post said you want it to remain in KISS mode across resets.
As Fred said -
   If you want it to remain in KISS between "reboots", use Simple(KISS) - BLANK Open and Close
   If you want to "put the TNC in KISS mode on start of APRS, then you need the commands in the OPEN and CLOSE.
 
KEEP in KISS:
1. open APRSISce/32 and delete port (must be DISABLED)
2. Create new "Simple(KISS) port for KPC3
3. Disable NEW KPC3 port (probably won't connect anyway)
4. Open terminal program and connect to KPC3
5. ISSUE commands to place TNC in KISS mode
     cmd: INT KISS
     cmd: reset
6.  Check received data for KISS format CO {HEX CODE} CO
7. Close terminal program
8. Go back to APRSISce/32 and enable port
 
 
 
Robert Giuliano
KB8RCO


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

From: Lynn W Deffenbaugh (Mr)
To: aprsisce@...
Sent: Wednesday, October 30, 2013 12:52 PM
Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode

 
See http://aprsisce.wikidot.com/tnc-kpc-3 and pick up an entire known-to-have-worked set of s from there.

Once you have those in place, check Enables / Logging / File Enabled and Enables / Logging / Port() and then disable, wait, and re-enable the port then wait for some packets to come in.  The Port() should contain some diagnostics that should show the interaction with the TNC.

These commands will put the TNC into and out of KISS mode whenever the port is enabled/disabled or APRSISCE/32 is executed/closed.  The only thing that locking the TNC into KISS mode does is to ensure that if the TNC drops power or otherwise resets while APRSISCE/32 is running, the port will continue working.  With switching it into and out of KISS mode, a TNC reset will drop it out of KISS and APRSISCE/32 will quit getting packets until the port or program is bounced.

This is no worse than using the internal TNC in a Kenwood radio in KISS mode because those radios don&apos;t even provide a way to lock into KISS.  If the TNC or radio resets, you need to disable/enable the port in APRSISCE/32 to get it back into KISS mode for operations.

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

On 10/30/2013 12:35 PM, va3nsc@... wrote:
Thats what I thought Larry thanks for the input...this has me baffled
Dave
 


---In aprsisce@..., mailto:k6kusman@... wrote:

I think the command to put it into kiss mode is "kiss on" then there is another command to make it stay in kiss mode. I just can&apos;t for the life of me remember what it is. But there is a command that set&apos;s it to keep the kiss mode on even after reboot. It&apos;s some command that set&apos;s it to a perm prameter that will survive power off or reboot.
Larry Ellsworth
          K6KUS
    Irlp Node 7413
Echolink Node 524805
  Allstar Link 27775

--------------------------------------------
On Wed, 10/30/13, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:

Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode
To: aprsisce@...
Date: Wednesday, October 30, 2013, 9:27 AM
















 












Great catch
Patrick!  You are correct
that one of the two following s will
knock a KPC-3
out of KISS mode:



^192^255^192~!!0

^C^C^C~!!0


Dave, If you have these in your APRSIS32.XML file, and
you want
your KPC-3 to stay in KISS mode when APRSISCE/32
isn&apos;t running,
then you need to remove them or replace them with the
following
No-Op.



~!!0



The other s listed below are
Kenwood-specific
commands that probably shouldn&apos;t be firing at
anyone&apos;s KPC-3
device!



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



On 10/30/2013 10:51 AM, Patrick Wood wrote:






Doesn&apos;t
that close command take it out
of KISS?  If you want to leave it in kiss,
put it into kiss
mode then use a simple kiss port.



p




On Oct 30, 2013 10:43 AM, <va3nsc@...>
wrote:







Thats how its set Adam,I have some other
tnc&apos;s here I will
try another and see if it does the same thing
with
them...thanks for responding. Dave

 




---In aprsisce@...,
mailto:kc2ant@... wrote:




Someone else (Jeremy
can&apos;t remember the
call sign) used this for the port config
with a
9612.





Name="KAM">

KISS

COM4:9600,N,8,1

1200

^M~

^M~

XFLOW
ON!!0

FULLDUP
OFF!!0

INT
KISS!!0

RESET!!0

^192^255^192~!!0

^C^C^C~!!0

TC
1!TS 1

TN
2,0!TN
2,0

0

1

1

0

1

1

0

1



0

0



1



0











I know that I
managed to lock my 9612 into KISS
but I don&apos;t
remember how I did
it.



Adam
KC2ANT



PS Yes I know
the KPC3+ is a different model,
but I&apos;ve found
a lot of the commands to be the
same/similar
for programming.




To: aprsisce@...

From: kj4erj@...

Date: Wed, 30 Oct 2013 10:00:59
-0400

Subject: Re: [aprsisce] KPC-3 with
aprsisce
problem locking into kiss mode



 




Put a new battery in your
KPC-3.  It
sounds like it is resetting
to factory
defaults every time you
power it down.



Try setting some other
setting (like
MYCALL), turn it off, wait a
bit, turn
it on and see if you MYCALL
has also
disappeared.



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



On
10/30/2013 9:26
AM, va3nsc@...
wrote:



Heres the prob
folks, I have
a KPC-3 I am trying to set
up to work
with aprsisce. For some
reason it wont
stay locked into kiss mode.
I have used
pacterm to put it into kiss
mode as
follows..cmd intface it
comes up as
newuser so I cmd intface
kiss then
enter,it shows in kiss mode
so I cmd
reset.  Fire up
aprsisce and the tnc
works fine,but if I turn the
tnc off and
back on again,refire the
program it will
not connect. I check pacterm
again and
intface is in terminal
mode..any ideas
on how to keep it locked
into kiss mode?
Dave





Re: KPC-3 with aprsisce problem locking into kiss mode

Rob Giuliano
 

If you are using OPEN and CLOSE commands, you are defeating the purpose.
Your initial post said you want it to remain in KISS mode across resets.
As Fred said -
   If you want it to remain in KISS between "reboots", use Simple(KISS) - BLANK Open and Close
   If you want to "put the TNC in KISS mode on start of APRS, then you need the commands in the OPEN and CLOSE.
 
KEEP in KISS:
1. open APRSISce/32 and delete port (must be DISABLED)
2. Create new "Simple(KISS) port for KPC3
3. Disable NEW KPC3 port (probably won't connect anyway)
4. Open terminal program and connect to KPC3
5. ISSUE commands to place TNC in KISS mode
     cmd: INT KISS
     cmd: reset
6.  Check received data for KISS format CO {HEX CODE} CO
7. Close terminal program
8. Go back to APRSISce/32 and enable port
 
 
 
Robert Giuliano
KB8RCO


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

From: Lynn W Deffenbaugh (Mr)
To: aprsisce@...
Sent: Wednesday, October 30, 2013 12:52 PM
Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode

 
See http://aprsisce.wikidot.com/tnc-kpc-3 and pick up an entire known-to-have-worked set of
Once you have those in place, check Enables / Logging / File Enabled and Enables / Logging / Port(<YourPortName>) and then disable, wait, and re-enable the port then wait for some packets to come in.  The Port() should contain some diagnostics that should show the interaction with the TNC.

These commands will put the TNC into and out of KISS mode whenever the port is enabled/disabled or APRSISCE/32 is executed/closed.  The only thing that locking the TNC into KISS mode does is to ensure that if the TNC drops power or otherwise resets while APRSISCE/32 is running, the port will continue working.  With switching it into and out of KISS mode, a TNC reset will drop it out of KISS and APRSISCE/32 will quit getting packets until the port or program is bounced.

This is no worse than using the internal TNC in a Kenwood radio in KISS mode because those radios don&apos;t even provide a way to lock into KISS.  If the TNC or radio resets, you need to disable/enable the port in APRSISCE/32 to get it back into KISS mode for operations.

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

On 10/30/2013 12:35 PM, va3nsc@... wrote:
Thats what I thought Larry thanks for the input...this has me baffled
Dave
 


---In aprsisce@..., mailto:k6kusman@... wrote:

I think the command to put it into kiss mode is "kiss on" then there is another command to make it stay in kiss mode. I just can&apos;t for the life of me remember what it is. But there is a command that set&apos;s it to keep the kiss mode on even after reboot. It&apos;s some command that set&apos;s it to a perm prameter that will survive power off or reboot.
Larry Ellsworth
          K6KUS
    Irlp Node 7413
Echolink Node 524805
  Allstar Link 27775

--------------------------------------------
On Wed, 10/30/13, Lynn W Deffenbaugh (Mr) <kj4erj@...> wrote:

Subject: Re: [aprsisce] RE: KPC-3 with aprsisce problem locking into kiss mode
To: aprsisce@...
Date: Wednesday, October 30, 2013, 9:27 AM
















 












Great catch
Patrick!  You are correct
that one of the two following s will
knock a KPC-3
out of KISS mode:



^192^255^192~!!0

^C^C^C~!!0


Dave, If you have these in your APRSIS32.XML file, and
you want
your KPC-3 to stay in KISS mode when APRSISCE/32
isn&apos;t running,
then you need to remove them or replace them with the
following
No-Op.



~!!0



The other s listed below are
Kenwood-specific
commands that probably shouldn&apos;t be firing at
anyone&apos;s KPC-3
device!



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



On 10/30/2013 10:51 AM, Patrick Wood wrote:






Doesn&apos;t
that close command take it out
of KISS?  If you want to leave it in kiss,
put it into kiss
mode then use a simple kiss port.



p




On Oct 30, 2013 10:43 AM, <va3nsc@...>
wrote:







Thats how its set Adam,I have some other
tnc&apos;s here I will
try another and see if it does the same thing
with
them...thanks for responding. Dave

 




---In aprsisce@...,
mailto:kc2ant@... wrote:




Someone else (Jeremy
can&apos;t remember the
call sign) used this for the port config
with a
9612.





Name="KAM">

KISS

COM4:9600,N,8,1

1200

^M~

^M~

XFLOW
ON!!0

FULLDUP
OFF!!0

INT
KISS!!0

RESET!!0

^192^255^192~!!0

^C^C^C~!!0

TC
1!TS 1

TN
2,0!TN
2,0

0

1

1

0

1

1

0

1


0

0



1



0











I know that I
managed to lock my 9612 into KISS
but I don&apos;t
remember how I did
it.



Adam
KC2ANT



PS Yes I know
the KPC3+ is a different model,
but I&apos;ve found
a lot of the commands to be the
same/similar
for programming.




To: aprsisce@...

From: kj4erj@...

Date: Wed, 30 Oct 2013 10:00:59
-0400

Subject: Re: [aprsisce] KPC-3 with
aprsisce
problem locking into kiss mode



 




Put a new battery in your
KPC-3.  It
sounds like it is resetting
to factory
defaults every time you
power it down.



Try setting some other
setting (like
MYCALL), turn it off, wait a
bit, turn
it on and see if you MYCALL
has also
disappeared.



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



On
10/30/2013 9:26
AM, va3nsc@...
wrote:



Heres the prob
folks, I have
a KPC-3 I am trying to set
up to work
with aprsisce. For some
reason it wont
stay locked into kiss mode.
I have used
pacterm to put it into kiss
mode as
follows..cmd intface it
comes up as
newuser so I cmd intface
kiss then
enter,it shows in kiss mode
so I cmd
reset.  Fire up
aprsisce and the tnc
works fine,but if I turn the
tnc off and
back on again,refire the
program it will
not connect. I check pacterm
again and
intface is in terminal
mode..any ideas
on how to keep it locked
into kiss mode?
Dave



11221 - 11240 of 35496