Re: Configure APRSISCE for ISS

sbd sbd

I think he might be trying to use the PMS on the ISS, which frustrates most APRS users. Because it kills off APRS use, due to all the connected packet retries. I have watched more than a few passes tied up with someone trying to get through the menu system let alone actually leave a message. It also frustrates the station attempting a PMS attempt for the same reason, they have to fight APRS users over a big footprint, for reception on the ISS system

I believe UISS automates some of the menu process.

In which case APRSISCE/32 is not suitable software.

However if he wants to message people via the ISS and perhaps igate received packets then my write up on the WIKI works well. (at least nobody yet has come up with a complaint)



Steve Daniels

Amateur Radio Callsign G6UIM

Torbay Freecycle  Owner

APRSISCE/32 Beta tester and WIKI editor


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W Deffenbaugh (Mr)
Sent: 19 November 2013 23:51
To: aprsisce@...
Subject: Re: [aprsisce] Configure APRSISCE for ISS



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

On 11/19/2013 6:19 PM, lenkf5elb wrote:
> I am setting up my first APRSISCE Instance ever and am configuring it to send email packets to the ISS and eventually have an IGate to send the emails to me or others who have sent email thru the ISS.

Based on what I see below, by "send email packets" do you mean that
you're sending an APRS message to the EMAIL address for subsequent
sending via the Internet by that service?

> I am running win XP and have an AEA PK88 TNC in KISS Mode. I am assuming for the IGate I will need another instance of APRSISCE, TNC and radio.

Whether or not you need another instance depends on the full scope of
what you're trying to do. I have a single IGate (KJ4ERJ-1) that I use
interactively when I want to do direct local APRS on the RF network.
Sometimes I switch it over and use it to work the ISS digipeater or just
monitor the ISS frequency in a SatGate operation if I happen to notice a

> I am not all that knowledgeable on APRS and Igates.

There's plenty of folks here that can lend a hand, I'm sure.

> I have been using UISS and AGW to successfully connect to the ISS, but the email is not getting picked up and sent on. For this setup I am not using AGW. The documentation seems to say it is not necessarily needed.

I'm not familiar with UISS, but you've got words in there (like
"connect" and "picked up") that imply that you're trying to work the
packet station on the ISS and not the APRS digipeater. Can you clarify
what you mean by the above statements?

> First let me say that I have never seen as many trace logs as this program has. Nice job Lynn.

Thanks. I really need to go through and eliminate some as they're now
actually obsolete and non-informative to the point of confusion.

> I have tried to follow the documentation to set up the first part. I am getting some error codes and I am not sure what I have set up wrong.
> Here are some traces I captured.
> Trace KF5ELB <-> CQ:
> 10:48:37 New Chat Between KF5ELB and CQ on 2013-11-19
> 10:50:08> :EMAIL :lenleslie@... Hello from Len, 73 KF5ELB (*2-10:50:08)

Ok, this is a strange one. Did you open a chat to "CQ" and then send
the text :EMAIL...? If so, that's not really going to get you any where.

What you probably wanted to do was open a chat to "EMAIL" and put the
text "lenleslie@flash..." and send it. APRSISCE/32 takes care of
building the APRS packet in the proper format for sending an APRS message.

> Trace Messages:
> WinMain:2013-11-19T16:48:37.702 New Chat(KF5ELB<>CQ) hwnd(001D01DC) Error(6)
> WinMain:2013-11-19T16:50:08.312 To(CQ) Msg(:EMAIL :lenleslie@... Hello from Len, 73 KF5ELB) NoAck
> WinMain:2013-11-19T16:50:08.312 Sending Message For(CQ) by New
> Getting error 6
> Is NEW correct?

I think this is one of those trace logs that are confusing. As long as
hwnd() is non-zero, the error is actually left over from some other
operation. And yes, New is correct in the context of this trace.

> Trace MyCall:
> 2013-11-19T22:23:50.750 [Telemetry] KF5ELB>APWW10,B/ARISS :T#329,100,048,002,500,000,10000000
> 2013-11-19T22:39:50.750 [Telemetry] KF5ELB>APWW10,B/ARISS :T#330,100,048,002,500,000,10000000
> 2013-11-19T22:48:42.125 [TransmitAPRS] KF5ELB>APWW10,B/ARISS :@224842h3031.22N/09751.48W-PHG3000APRS-IS for Win32

This trace will just show you every packet that mentions your base
callsign and where it was detected. It's there to see if you've seen
any packets that mention you while possibly not be addressed to you.

> Trace Transmit:
> 2013-11-19T22:23:50.750 Transmit(INT) KF5ELB>APWW10,B/ARISS :T#329,100,048,002,500,000,10000000
> 2013-11-19T22:39:50.750 Transmit(INT) KF5ELB>APWW10,B/ARISS :T#330,100,048,002,500,000,10000000
> 2013-11-19T22:48:42.125 Transmit(INT) KF5ELB>APWW10,B/ARISS :@224842h3031.22N/09751.48W-PHG3000APRS-IS for Win32

The first two telemetry packets as Internal make sense. I'm not sure
why the posit packet is only INT, but it depends on a bunch of other flags.

However, the path term of "B/ARISS" is definitely incorrect. I'd
recommend that you get familiar with the terrestrial APRS network before
jumping into the deep end of the pool with the ISS. Set your Configure
/ Beacon / Path to WIDE2-1 and the radio to 144.390 or whatever your
local APRS frequency is to get used to the program and APRS operations.

> Trace Port PK88:
> Port(pk88):2013-11-19T16:48:53.765 Opening COM1 Got -1 Error 5
> Port(pk88):2013-11-19T16:48:53.765 Status 0 Error 0 At 228 in c:\compass\code\aprs\aprsisce\cprtns.c
> Port(pk88):2013-11-19T16:48:53.765 Error Opening COM1:0,N,8,1 LastError 0
> Port(pk88):2013-11-19T16:48:58.765 Opening COM1:0,N,8,1
> Port(pk88):2013-11-19T16:48:58.765 Opening COM1 with 4 Args
> Port(pk88):2013-11-19T16:48:58.765 Opening COM1 Got -1 Error 5
> Port(pk88):2013-11-19T16:48:58.765 Status 0 Error 0 At 228 in c:\compass\code\aprs\aprsisce\cprtns.c
> Port(pk88):2013-11-19T16:48:58.765 Error Opening COM1:0,N,8,1 LastError 0
> Get error 5 - Is that because it gets an error opening com 1 the first time and then Error 0 means it opened Com 1 successfully?

This is where the true errors start. You have your PK88 port configured
to use COM1, but with a zero baud rate and worse, APRSISCE/32 isn't able
to open that COM port, possibly because you have some other program
using it at the same time. First, go to Configure / Ports / PK88 and
click Device and correct the baud rate. Then open the trace log and
make sure it is Enabled. It'll tell you lots of stuff.

Are you able to talk to the PK88 on COM1 from a terminal emulator? Are
you sure no other program was accessing COM1 when you captured the above

> Trace Port Packets:
> WinMain:2013-11-19T16:48:23.687 Growing PortPackets from 0 to 16 - Increment
> WinMain:2013-11-19T16:48:23.687 Initializing PortPackets[0/1] for RfPort:0 - Increment was 0 for pk88
> WinMain:2013-11-19T16:48:24.140 Initializing PortPackets[1/2] for RfPort:1111 - Increment was 0 for *Internal*
> Are the RFPort 1111 and *Internal* OK?

Yes, this is all fine.

> At the top of the map I have PK88 OK and under it is disabled. Should I have something enabled that is turned off. I have Internet access, OSM Fetch, sound, port for PK88 and logging enabled.

Check out and identify
the screen area that you're seeing "PK88 OK" in . it should be #27. If
it says "Disabled" below that, it means that you've got position
beaconing disabled (check Enables / Beaconing Enabled).

> Any help will be appreciated.

See where this takes you and please delete any sections you don't think
we need to go further with in your reply.

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

Join to automatically receive all group messages.