Date   

Re: Satellite Telemetry

Lynn Deffenbaugh
 

I still don't understand what "satellite tracking" is?

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

On 8/3/2020 12:33 PM, Thomas Testa via groups.io wrote:
I have satellite tracking activated. The satellite details box is blank. There is no information coming in. I haven’t changed a thing. It was all working fine until 2 days ago. The details box went blank and the date and time box turned red ate the same time.

                   Thank You Tom N2UFM




On Monday, August 3, 2020, 11:53 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

What is the "satellite pop up box"?  I"m not familiar with that one.

And I didn't ask before, but I might as well go ahead and ask what you mean by "satellite telemetry"?  I don't know what that is either.

It doesn't show popups, but sometimes the screen layout at the URL below is helpful.  For instance, 16 is the date/time box.

http://aprsisce.wikidot.com/doc:screen-elements

Also, the date/time box on the lower right background color represents how much CPU APRSIS32 believes it is using vs how busy the system is in general.  This is only an approximation and sometimes gets confused and goes solid red background.  It has nothing to do with GPS nor satellites.

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

On 8/3/2020 11:23 AM, Thomas Testa via groups.io wrote:
Lynn it is N2UFM-2. I am a fixed station with no GPS activated. Everything was working fine until two day ago when I stopped receiving satellite telemetry. The  satellite pop up box opens without any information and the date and time box on the lower right is solid red.

                        Thank You , Tom N2UFM




On Monday, August 3, 2020, 10:37 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

I need more information.  Is this APRSISCE or APRSIS32?  What operating system?  What is your GPS and how do you have it configured in APRSISCE/32?

Actually, I did some queries and answered the APRSIS32 and O/S questions.  Are we talking about N2UFM-2 (your IGate with a Simply(KISS) RF port) or N2UFM (an RF-only Weather station?)?

And definitely what GPS are you using via what connection and how do you have it configured in APRSIS32?

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

On 8/3/2020 9:19 AM, Thomas Testa via groups.io wrote:

Hi Lynn I am not receiving Satellite Telemetry. The box opens stays blank and the time and date box is a steady read. I am running the latest Development Version.
                                Thank You , Tom N2UFM



Re: Satellite Telemetry

Thomas Testa
 

I have satellite tracking activated. The satellite details box is blank. There is no information coming in. I haven’t changed a thing. It was all working fine until 2 days ago. The details box went blank and the date and time box turned red ate the same time.

                   Thank You Tom N2UFM




On Monday, August 3, 2020, 11:53 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

What is the "satellite pop up box"?  I"m not familiar with that one.

And I didn't ask before, but I might as well go ahead and ask what you mean by "satellite telemetry"?  I don't know what that is either.

It doesn't show popups, but sometimes the screen layout at the URL below is helpful.  For instance, 16 is the date/time box.

http://aprsisce.wikidot.com/doc:screen-elements

Also, the date/time box on the lower right background color represents how much CPU APRSIS32 believes it is using vs how busy the system is in general.  This is only an approximation and sometimes gets confused and goes solid red background.  It has nothing to do with GPS nor satellites.

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

On 8/3/2020 11:23 AM, Thomas Testa via groups.io wrote:
Lynn it is N2UFM-2. I am a fixed station with no GPS activated. Everything was working fine until two day ago when I stopped receiving satellite telemetry. The  satellite pop up box opens without any information and the date and time box on the lower right is solid red.

                        Thank You , Tom N2UFM




On Monday, August 3, 2020, 10:37 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

I need more information.  Is this APRSISCE or APRSIS32?  What operating system?  What is your GPS and how do you have it configured in APRSISCE/32?

Actually, I did some queries and answered the APRSIS32 and O/S questions.  Are we talking about N2UFM-2 (your IGate with a Simply(KISS) RF port) or N2UFM (an RF-only Weather station?)?

And definitely what GPS are you using via what connection and how do you have it configured in APRSIS32?

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

On 8/3/2020 9:19 AM, Thomas Testa via groups.io wrote:

Hi Lynn I am not receiving Satellite Telemetry. The box opens stays blank and the time and date box is a steady read. I am running the latest Development Version.
                                Thank You , Tom N2UFM



Re: Satellite Telemetry

Lynn Deffenbaugh
 

What is the "satellite pop up box"?  I"m not familiar with that one.

And I didn't ask before, but I might as well go ahead and ask what you mean by "satellite telemetry"?  I don't know what that is either.

It doesn't show popups, but sometimes the screen layout at the URL below is helpful.  For instance, 16 is the date/time box.

http://aprsisce.wikidot.com/doc:screen-elements

Also, the date/time box on the lower right background color represents how much CPU APRSIS32 believes it is using vs how busy the system is in general.  This is only an approximation and sometimes gets confused and goes solid red background.  It has nothing to do with GPS nor satellites.

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

On 8/3/2020 11:23 AM, Thomas Testa via groups.io wrote:
Lynn it is N2UFM-2. I am a fixed station with no GPS activated. Everything was working fine until two day ago when I stopped receiving satellite telemetry. The  satellite pop up box opens without any information and the date and time box on the lower right is solid red.

                        Thank You , Tom N2UFM




On Monday, August 3, 2020, 10:37 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

I need more information.  Is this APRSISCE or APRSIS32?  What operating system?  What is your GPS and how do you have it configured in APRSISCE/32?

Actually, I did some queries and answered the APRSIS32 and O/S questions.  Are we talking about N2UFM-2 (your IGate with a Simply(KISS) RF port) or N2UFM (an RF-only Weather station?)?

And definitely what GPS are you using via what connection and how do you have it configured in APRSIS32?

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

On 8/3/2020 9:19 AM, Thomas Testa via groups.io wrote:

Hi Lynn I am not receiving Satellite Telemetry. The box opens stays blank and the time and date box is a steady read. I am running the latest Development Version.
                                Thank You , Tom N2UFM



Re: Satellite Telemetry

Thomas Testa
 

Lynn it is N2UFM-2. I am a fixed station with no GPS activated. Everything was working fine until two day ago when I stopped receiving satellite telemetry. The  satellite pop up box opens without any information and the date and time box on the lower right is solid red.

                        Thank You , Tom N2UFM




On Monday, August 3, 2020, 10:37 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

I need more information.  Is this APRSISCE or APRSIS32?  What operating system?  What is your GPS and how do you have it configured in APRSISCE/32?

Actually, I did some queries and answered the APRSIS32 and O/S questions.  Are we talking about N2UFM-2 (your IGate with a Simply(KISS) RF port) or N2UFM (an RF-only Weather station?)?

And definitely what GPS are you using via what connection and how do you have it configured in APRSIS32?

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

On 8/3/2020 9:19 AM, Thomas Testa via groups.io wrote:

Hi Lynn I am not receiving Satellite Telemetry. The box opens stays blank and the time and date box is a steady read. I am running the latest Development Version.
                                Thank You , Tom N2UFM



Re: Satellite Telemetry

Lynn Deffenbaugh
 

I need more information.  Is this APRSISCE or APRSIS32?  What operating system?  What is your GPS and how do you have it configured in APRSISCE/32?

Actually, I did some queries and answered the APRSIS32 and O/S questions.  Are we talking about N2UFM-2 (your IGate with a Simply(KISS) RF port) or N2UFM (an RF-only Weather station?)?

And definitely what GPS are you using via what connection and how do you have it configured in APRSIS32?

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

On 8/3/2020 9:19 AM, Thomas Testa via groups.io wrote:

Hi Lynn I am not receiving Satellite Telemetry. The box opens stays blank and the time and date box is a steady read. I am running the latest Development Version.
                                Thank You , Tom N2UFM


Satellite Telemetry

Thomas Testa
 


Hi Lynn I am not receiving Satellite Telemetry. The box opens stays blank and the time and date box is a steady read. I am running the latest Development Version.
                                Thank You , Tom N2UFM


Re: Igate setup

Lynn Deffenbaugh
 

Welcome to APRS!

The passcode is generated from your callsign and is used to access the APRS-IS network.  Some other APRS software may have additional security levels (UI-View comes to mind), but APRSISCE/32 only needs the APRS-IS passcode.  It is perfectly fine to use the one from APRSdroid, provided that you're using the same base callsign.  The passcode works with any -SSID.

No, you do not need any permission from the APRS-IS servers.  I recommend that you use noam.aprs2.net so that your connection goes to a lightly loaded server in North America.  Stations not in North America might want to use rotate.aprs2.net as their APRS-IS server specification.

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

On 8/3/2020 5:27 AM, Alder Kail wrote:
Hello, I'm new to groups.io and I'm new to this software! I have two questions and hopefully I can get on my way. The spot that I live in is fairly rural and I'm trying to set up an Igate and possibly a digipeater in the future. I already have a passcode for APRS-IS from another program I was using (APRSdroid) so I was confused whether I would be breaking any rules or not if I just slapped that in APRSIS32 and started up an Igate, or if I needed a moderator to verify my information or activate my passcode or something? My second question, do I need to notify anyone that runs the APRS servers that I will be injecting information onto their website? I'm still trying to learn about all these things, but there doesn't seem to be much information readily available on the internet, and after a lot of digging decided to just ask here. Thanks to anyone that can shed some light on this for me! - Ian, KI5IBL


Igate setup

Alder Kail
 

Hello, I'm new to groups.io and I'm new to this software! I have two questions and hopefully I can get on my way. The spot that I live in is fairly rural and I'm trying to set up an Igate and possibly a digipeater in the future. I already have a passcode for APRS-IS from another program I was using (APRSdroid) so I was confused whether I would be breaking any rules or not if I just slapped that in APRSIS32 and started up an Igate, or if I needed a moderator to verify my information or activate my passcode or something? My second question, do I need to notify anyone that runs the APRS servers that I will be injecting information onto their website? I'm still trying to learn about all these things, but there doesn't seem to be much information readily available on the internet, and after a lot of digging decided to just ask here. Thanks to anyone that can shed some light on this for me! - Ian, KI5IBL


Re: qty or freq tune.

T W
 

This works for me! Thank to all!

Cheers
kf6kyd

On 21 Jul 2020, at 15:49, Robert Bruninga <bruninga@...> wrote:

if you see a freq object on the screen or in the list, just seet it and push TUNE button;
To find them all, just go to the station list and press SORT by call.  All of the numeric named frequency objects will be placfed at the top of the list.
Select anyone and press tune.

The problem is that TUNE only works if the voice band is in VFO and not memory channel mode.

Bob

On Tue, Jul 21, 2020 at 4:45 PM Brad Ko6kL via groups.io <jhill_81=yahoo.com@groups.io> wrote:
I would love to see a youtube video of this repeater object showing up on the Kenwood710 and what buttons to press go get a QSY.
I think the new big display yeasu duel bander will do this as well...
again I would like to see some software that receives this repeater object from aprs and uses the CAT to tune my Kenwood 2000 like that....
it would seem you could scan the logging files for the object and output that to the radios cat input.
or maybe someday have it all running on some guys web-sdr for remote users poking about.
It would be nice to know if I'm getting the object syntax right with out having to buy a kenwood710










Re: APRSIS settings for ISS

bobolink
 

Gotchya
http://www.aprs-is.net/WX/MultilineProtocol.aspx
I’ll try to plot that.

tnx,

Bob
wm6h


Re: APRSIS settings for ISS

Lynn Deffenbaugh
 

You sent a message to ISS, therefore the APRS-IS sends back a "courtesy posit" which is the next posit for that "station".  I (KJ4ERJ-15) also am injecting a multi-line object labelled ISS showing the current oribital position of the ISS along with an approximate RF footprint.  That is the packet that you didn't know what was.

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

On 7/21/2020 1:40 PM, bobolink wrote:
This is kind of interesting. While Hessu is fixing the iOS app, I thought I’d try it myself on the Mac so I looked all this up on the internet. You need to get a APRS-IS password nnnn
||||||||||||||||||||||||||||||||||||||||||||||||

telnet -c noam.aprs2.net 14580

user wm6h-4 pass nnnn

|||||||||||||||||||||||||||||||||||||||||||||||||
1>Beacon your position. Change the position from my house to yours. A little man symbol shows up at your house on aprs.fi 

WM6H-4>APFII0,WIDE1-1,WIDE2-1:!4201.25N/09141.37W[/Test Message1
2>The actual request. You might have to wait a few minutes for the beacon to be registered. You will get the “Please Beacon Your Position” message in the mean time. Just make up a sequence number

WM6H-4>APRS::ISS      :{0005

2A>The request acknowledgment 

ISS>APWW11,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :ack0005

 

3>The ISS pass

ISS>APWW11,KJ4ERJ-15,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 6h31m (2335z) SE^20{RQ}

4>The pass acknowledgement

WM6H-4>APRS::ISS      :ackRQ}

 

I don’t know what this is:

KJ4ERJ-15>APZTLE,TCPIP*,qAC,SEVENTH:;ISS      *163224h0607.91S\17432.71ESMsg4Pass }k1jzNqg\wBx+i"N+3B$\%q5zN{!wf+!

I’ll be listening!


Bob
wm6h


Re: qty or freq tune.

Robert Bruninga
 

if you see a freq object on the screen or in the list, just seet it and push TUNE button;
To find them all, just go to the station list and press SORT by call.  All of the numeric named frequency objects will be placfed at the top of the list.
Select anyone and press tune.

The problem is that TUNE only works if the voice band is in VFO and not memory channel mode.

Bob


On Tue, Jul 21, 2020 at 4:45 PM Brad Ko6kL via groups.io <jhill_81=yahoo.com@groups.io> wrote:
I would love to see a youtube video of this repeater object showing up on the Kenwood710 and what buttons to press go get a QSY.
I think the new big display yeasu duel bander will do this as well...
again I would like to see some software that receives this repeater object from aprs and uses the CAT to tune my Kenwood 2000 like that....
it would seem you could scan the logging files for the object and output that to the radios cat input.
or maybe someday have it all running on some guys web-sdr for remote users poking about.
It would be nice to know if I'm getting the object syntax right with out having to buy a kenwood710







Re: qty or freq tune.

Brad Ko6kL
 

I would love to see a youtube video of this repeater object showing up on the Kenwood710 and what buttons to press go get a QSY.
I think the new big display yeasu duel bander will do this as well...
again I would like to see some software that receives this repeater object from aprs and uses the CAT to tune my Kenwood 2000 like that....
it would seem you could scan the logging files for the object and output that to the radios cat input.
or maybe someday have it all running on some guys web-sdr for remote users poking about.
It would be nice to know if I'm getting the object syntax right with out having to buy a kenwood710







Re: APRSIS settings for ISS

bobolink
 

I guess you should close out the session.
On the Mac ctrl+] 
ctrl+z to exit Telnet 


Re: APRSIS settings for ISS

bobolink
 

This is kind of interesting. While Hessu is fixing the iOS app, I thought I’d try it myself on the Mac so I looked all this up on the internet. You need to get a APRS-IS password nnnn
||||||||||||||||||||||||||||||||||||||||||||||||

telnet -c noam.aprs2.net 14580

user wm6h-4 pass nnnn

|||||||||||||||||||||||||||||||||||||||||||||||||
1>Beacon your position. Change the position from my house to yours. A little man symbol shows up at your house on aprs.fi 

WM6H-4>APFII0,WIDE1-1,WIDE2-1:!4201.25N/09141.37W[/Test Message1
2>The actual request. You might have to wait a few minutes for the beacon to be registered. You will get the “Please Beacon Your Position” message in the mean time. Just make up a sequence number

WM6H-4>APRS::ISS      :{0005

2A>The request acknowledgment 

ISS>APWW11,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :ack0005

 

3>The ISS pass

ISS>APWW11,KJ4ERJ-15,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 6h31m (2335z) SE^20{RQ}

4>The pass acknowledgement

WM6H-4>APRS::ISS      :ackRQ}

 

I don’t know what this is:

KJ4ERJ-15>APZTLE,TCPIP*,qAC,SEVENTH:;ISS      *163224h0607.91S\17432.71ESMsg4Pass }k1jzNqg\wBx+i"N+3B$\%q5zN{!wf+!

I’ll be listening!


Bob
wm6h


Re: qty or freq tune.

Rob Giuliano
 

There is a perspective that needs to be taken into account.
It is possible for the D710 to receive a packet with QSY information and tune to the provided frequency with the proper tone, etc. on its display that you can select and the radio will change frequency. This is handled by the radio itself.

APRSIS (assumed to mean APRSIS32 and not the internet backbone) cannot tell an attached D710 to change frequency and tone (CAT functions for a computer to make the radio act) so that the user can make a voice contact. 

APRSIS32 "CAN" send the properly formated object to tell someone that is driving by (or in any way) using a QSY enabled device (like the D710 radio) that "you" are listening and available on a voice frequency.  This is why it is listed in the Configure Object section of the WIKI.  It does not change the radio attached to the computer running APRSIS32, but requests someone else's radio to change frequency to what you sent and you are listening for voice communication.

So if you wanted to take advantage, you probably need another radio, or at least a radio capable of running packet on one side and voice on the other at the same time.  Then create an object that has the frequency and tone information of the radio you are listening to, send the object periodically while you are listening to that voice frequency listed, and wait for someone to "click" your object.

I hope this helps explain it. 

Robert Giuliano
KB8RCO



On Monday, July 20, 2020, 6:04:49 PM EDT, T W via groups.io <kf6kyd@...> wrote:


In the past I have asked if its possible to tune a D710 to the frequency listed in the frequency monitor. I was told it is a cat function which is something APRSIS does not do. In reading the Wiki it looks like it does work that way. The function in called QSY, and its description is discussed on the configure objects page. Would it be possible to get some clarification on this?

Cheers
kf6kyd


qty or freq tune.

T W
 

In the past I have asked if its possible to tune a D710 to the frequency listed in the frequency monitor. I was told it is a cat function which is something APRSIS does not do. In reading the Wiki it looks like it does work that way. The function in called QSY, and its description is discussed on the configure objects page. Would it be possible to get some clarification on this?

Cheers
kf6kyd


Re: APRSIS settings for ISS

Gervais Fillion <ve2ckn2@...>
 

hello
i would like to see your filter guys,
how do you write the line,is it possible?


i would compare with mine here if i am ok,

thanks
gervais ve2ckn



De : APRSISCE@groups.io <APRSISCE@groups.io> de la part de Lynn Deffenbaugh <kj4erj@...>
Envoyé : 15 juillet 2020 17:39
À : APRSISCE@groups.io <APRSISCE@groups.io>
Objet : Re: [APRSISCE] APRSIS settings for ISS
 

Hessu - You may want to read this and also http://www.aprs.org/aprs11/replyacks.txt

4) When you receive a message line XXX.., send the normal existing
   "ackXXX..". This algoirithm is unchanged.  Even if XXX.. is MM}AA
   then the ack is just the exact copy as before "ackMM}AA"

It appears that your app is not properly acknowledging the responses from the SatSrv.  It uses "Reply-Ack" formatting, but your application is stripping off the final character of the ack string.  Consider the following raw packets captured from aprs.fi.

2020-07-15 08:39:28 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ISS{B3421
2020-07-15 08:39:29 CDT: ISS>APWW10,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :ackB3421
2020-07-15 08:39:29 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:39:38 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNK
2020-07-15 08:39:40 CDT: WM6H-4>APFII0,W0GQ-1,WIDE1*,WIDE2-1,qAR,KW0O-12:@133938h4201.25N/09141.36W-195/000APRS message enabled!w+R!
2020-07-15 08:40:03 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:40:36 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:41:39 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:42:52 CDT: WM6H-4>APFII0,W0GQ-1,WIDE1*,WIDE2-1,qAR,KW0O-12:@134248h4201.25N/09141.37W-298/000APRS message enabled!w21!
2020-07-15 08:43:16 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}

2020-07-15 08:43:16 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:43:25 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNL
2020-07-15 08:43:48 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:44:21 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:45:25 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:47:01 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}

2020-07-15 08:47:01 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:47:33 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:48:06 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:49:10 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:50:46 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:52:20 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNM

2020-07-15 08:52:21 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}
2020-07-15 08:52:25 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNN
2020-07-15 08:52:54 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}
2020-07-15 08:53:18 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNN
2020-07-15 08:53:26 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}

The ack string from your app should have been "ackNK}", but it only sent "ackNK".  Since this wasn't the expected ack, SatSrv continued retrying the message, but your app only seems to have acked it once, or the APRS-IS dupe-suppressed the others.  But then it gets interesting...

Apparently, since the ackNK didn't match any outstanding messages, APRSIS32 (the host for SatSrv) passed it on to SatSrv.  Since SatSrv doesn't care what the body of the message is (except for known stations, see below), it thought the mis-matched ack was a new request, so it queued up another response to be sent when the retries from the first one were exhausted.  When that was sent with {NM}, your app ack'd with ackNM which also didn't match so it queued up another response.  And so the cycle continued.

Please do be cautious of what the message content is that you send to SatSrv.  If the message body is a known APRS station ID, you will get the next pass prediction for the last known location of THAT station and not your own.  So sending "ISS" as the body of the request is not only redundant, but could have looked at the last location of the ISS object and given a pass prediction from there.  It turns out it didn't do that, or the information would have been in the body of the response like (note the @ KQ1L-4):

AOS 2h03m (2339z) SE^4 @ KQ1L-4 (*2-17:36:00)
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.  I think I'll make SatSrv ignore any orphan ack's rather than treating them as a new request and document the fact that the message body should not start with "ack" or you will not get a response.

On 7/15/2020 3:55 PM, bobolink wrote:
Send an APRS message by any method (Internet is probably best) to the satellite name, and you'll get a reply message with information showing the next pass.  So, just send a message to "ISS".  The message text can be anything (it's not used).  Be sure to beacon where you are first.
That worked but is there a way to stop the messages? This may be a problem in the iOS message app I’m using:


Re: APRSIS settings for ISS

Lynn Deffenbaugh
 

Hessu - You may want to read this and also http://www.aprs.org/aprs11/replyacks.txt

4) When you receive a message line XXX.., send the normal existing
   "ackXXX..". This algoirithm is unchanged.  Even if XXX.. is MM}AA
   then the ack is just the exact copy as before "ackMM}AA"

It appears that your app is not properly acknowledging the responses from the SatSrv.  It uses "Reply-Ack" formatting, but your application is stripping off the final character of the ack string.  Consider the following raw packets captured from aprs.fi.

2020-07-15 08:39:28 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ISS{B3421
2020-07-15 08:39:29 CDT: ISS>APWW10,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :ackB3421
2020-07-15 08:39:29 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:39:38 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNK
2020-07-15 08:39:40 CDT: WM6H-4>APFII0,W0GQ-1,WIDE1*,WIDE2-1,qAR,KW0O-12:@133938h4201.25N/09141.36W-195/000APRS message enabled!w+R!
2020-07-15 08:40:03 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:40:36 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:41:39 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:42:52 CDT: WM6H-4>APFII0,W0GQ-1,WIDE1*,WIDE2-1,qAR,KW0O-12:@134248h4201.25N/09141.37W-298/000APRS message enabled!w21!
2020-07-15 08:43:16 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}

2020-07-15 08:43:16 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:43:25 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNL
2020-07-15 08:43:48 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:44:21 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:45:25 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:47:01 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}

2020-07-15 08:47:01 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:47:33 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:48:06 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:49:10 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:50:46 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:52:20 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNM

2020-07-15 08:52:21 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}
2020-07-15 08:52:25 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNN
2020-07-15 08:52:54 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}
2020-07-15 08:53:18 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ackNN
2020-07-15 08:53:26 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}

The ack string from your app should have been "ackNK}", but it only sent "ackNK".  Since this wasn't the expected ack, SatSrv continued retrying the message, but your app only seems to have acked it once, or the APRS-IS dupe-suppressed the others.  But then it gets interesting...

Apparently, since the ackNK didn't match any outstanding messages, APRSIS32 (the host for SatSrv) passed it on to SatSrv.  Since SatSrv doesn't care what the body of the message is (except for known stations, see below), it thought the mis-matched ack was a new request, so it queued up another response to be sent when the retries from the first one were exhausted.  When that was sent with {NM}, your app ack'd with ackNM which also didn't match so it queued up another response.  And so the cycle continued.

Please do be cautious of what the message content is that you send to SatSrv.  If the message body is a known APRS station ID, you will get the next pass prediction for the last known location of THAT station and not your own.  So sending "ISS" as the body of the request is not only redundant, but could have looked at the last location of the ISS object and given a pass prediction from there.  It turns out it didn't do that, or the information would have been in the body of the response like (note the @ KQ1L-4):

AOS 2h03m (2339z) SE^4 @ KQ1L-4 (*2-17:36:00)
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.  I think I'll make SatSrv ignore any orphan ack's rather than treating them as a new request and document the fact that the message body should not start with "ack" or you will not get a response.

On 7/15/2020 3:55 PM, bobolink wrote:
Send an APRS message by any method (Internet is probably best) to the satellite name, and you'll get a reply message with information showing the next pass.  So, just send a message to "ISS".  The message text can be anything (it's not used).  Be sure to beacon where you are first.
That worked but is there a way to stop the messages? This may be a problem in the iOS message app I’m using:


Re: APRSIS settings for ISS

Lynn Deffenbaugh
 

The key assumption in the Reply-Acks spec is the first line of the Summary:

Original APRS ACK:  {#####  <== There were no restrictions on #####

And in the original spec, why qualify "5 alphanumeric characters" with "no spaces" when a space isn't alpha-numeric anyway?

The simple fix is to use up to all 5 characters after the { regardless of what they are as that is the assumption in Reply-Ack.

I was always bothered by the fact that it is a "message number" that isn't numeric!

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

On 7/15/2020 6:13 PM, Heikki Hannikainen wrote:

Hi,

My app currently does not implement the replyacks protocol (other than ignoring it). I couldn't quite parse out the document on how it should actually work and didn't have time to reverse engineer it yet.

As per APRS101.PDF "The message identifier consists of the character { followed by a message number (up to 5 alphanumeric characters, no spaces) to identify the message." and so the app currently only returns the message ID (alphanumeric!) in the ack, and not the trailing } sent by SatSrv.

And yep, orphan or duplicate/delayed acks may well happen at times.


On Wed, 15 Jul 2020, Lynn W Deffenbaugh (Mr) wrote:

Hessu - You may want to read this and also http://www.aprs.org/aprs11/replyacks.txt

4) When you receive a message line XXX.., send the normal existing
    "ackXXX..". This algoirithm is unchanged.  Even if XXX.. is MM}AA
    then the ack is just the exact copy as before "ackMM}AA"

It appears that your app is not properly acknowledging the responses from the SatSrv.  It uses "Reply-Ack" formatting, but your application is stripping off the final character of the ack string.  Consider the following raw packets captured from aprs.fi.

2020-07-15 08:39:28 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS      :ISS{B3421
2020-07-15 08:39:29 CDT: ISS>APWW10,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :ackB3421
2020-07-15 08:39:29 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:39:38 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS :ackNK
2020-07-15 08:39:40 CDT: WM6H-4>APFII0,W0GQ-1,WIDE1*,WIDE2-1,qAR,KW0O-12:@133938h4201.25N/09141.36W-195/000APRS message enabled!w+R!
2020-07-15 08:40:03 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:40:36 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:41:39 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}
2020-07-15 08:42:52 CDT: WM6H-4>APFII0,W0GQ-1,WIDE1*,WIDE2-1,qAR,KW0O-12:@134248h4201.25N/09141.37W-298/000APRS message enabled!w21!
2020-07-15 08:43:16 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h32m (16 0111z) SE^6{NK}

2020-07-15 08:43:16 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:43:25 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS :ackNL
2020-07-15 08:43:48 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:44:21 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:45:25 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}
2020-07-15 08:47:01 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h31m (16 0111z) SE^6{NL}

2020-07-15 08:47:01 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:47:33 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:48:06 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:49:10 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:50:46 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h28m (16 0111z) SE^6{NM}
2020-07-15 08:52:20 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS :ackNM

2020-07-15 08:52:21 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}
2020-07-15 08:52:25 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS :ackNN
2020-07-15 08:52:54 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}
2020-07-15 08:53:18 CDT: WM6H-4>APFII0,qAC,APRSFI::ISS :ackNN
2020-07-15 08:53:26 CDT: ISS>APWW10,KJ4ERJ-15*,TCPIP*,qAS,KJ4ERJ-15::WM6H-4   :AOS 11h19m (16 0111z) SE^6{NN}

The ack string from your app should have been "ackNK}", but it only sent "ackNK".  Since this wasn't the expected ack, SatSrv continued retrying the message, but your app only seems to have acked it once, or the APRS-IS dupe-suppressed the others.  But then it gets interesting...

Apparently, since the ackNK didn't match any outstanding messages, APRSIS32 (the host for SatSrv) passed it on to SatSrv. Since SatSrv doesn't care what the body of the message is (except for known stations, see below), it thought the mis-matched ack was a new request, so it queued up another response to be sent when the retries from the first one were exhausted.  When that was sent with {NM}, your app ack'd with ackNM which also didn't match so it queued up another response.  And so the cycle continued.

Please do be cautious of what the message content is that you send to SatSrv.  If the message body is a known APRS station ID, you will get the next pass prediction for the last known location of THAT station and not your own.  So sending "ISS" as the body of the request is not only redundant, but could have looked at the last location of the ISS object and given a pass prediction from there.  It turns out it didn't do that, or the information would have been in the body of the response like (note the @ KQ1L-4):

AOS 2h03m (2339z) SE^4 @ KQ1L-4 (*2-17:36:00)

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

PS.  I think I'll make SatSrv ignore any orphan ack's rather than treating them as a new request and document the fact that the message body should not start with "ack" or you will not get a response.

On 7/15/2020 3:55 PM, bobolink wrote:

    Send an APRS message by any method (Internet is probably best) to
    the satellite name, and you'll get a reply message with
    information showing the next pass.  So, just send a message to
    "ISS".  The message text can be anything (it's not used).  Be sure
    to beacon where you are first.

That worked but is there a way to stop the messages? This may be a problem in the iOS message app I’m using:



  - Hessu