Date   

Re: JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Lynn Deffenbaugh
 

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.

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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:
12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl


Re: Password

Rob Giuliano
 

Passcode for W8KTM is 8846

This passcode will work for any -SSID (http://aprsisce.wikidot.com/doc:ssids) you choose to use.
Because it is actually the APRS-IS network passcode, it should also work with other APRS-IS client software.

73 de
Robert Giuliano
KB8RCO



On Monday, April 27, 2020, 1:48:33 AM EDT, Jason Means <jsmeans76@...> wrote:


Would like a password for APRS IS

Thanks

Jason Means 
W8KTM

--
Jason Means
1506 Byng Dr.
S. Charleston, WV 25303
(304) 561-7939
MSSL, BSOL, LMT
W8KTM 


Re: JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Ryszard Labus
 

What i am doing wrong?

I cant see FT-3D as recognized?

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:
12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl


Password

Jason Means
 

Would like a password for APRS IS

Thanks

Jason Means 
W8KTM

--
Jason Means
1506 Byng Dr.
S. Charleston, WV 25303
(304) 561-7939
MSSL, BSOL, LMT
W8KTM 


JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Lynn Deffenbaugh
 

Yes, you read the subject correctly.  There's a new development version of APRSIS32 on the web!  Just check About and it should be available for download, assuming that you're configured for the Development release (see PS).

So, what's new you ask?  Well, here's what I could determine I've done since the last release.

1) New support for JS8Call and FT8 log-scraping objects.  This is similar to the JT65 scraper that already existed.  Simply create new object of the appropriate type and point it to your ALL.TXT log file for the corresponding program.  Object will be created for any detected station for which a grid square is available. These are objects local to your instance only.

2) Better file detection logic for file-based objects.  This includes the new JS8Call and FT8 objects as well as the previous JT65 and weather station objects.

3) Support for "Hashes".  These are similar to !shriek!s, but are delimited by a single preceding #, as in #JS8 or #EVENT.  More details on this to follow at some later date.

4) Driving GPX overlays now supports multiple segments in a single file.

5) Messages are now gated from the APRS-IS to RF even if the source station has been copied inside a third-party packet.  It seems that some Direwolf gates are taking source messages and gating them to RF as third-party packets which was causing a receiving APRSIS32 IGate to no longer gate messages from that station since it was presumably already on RF.

6) Battery current telemetry is now transmitted in 10s of mA to keep the value in the valid range of 0..255.  Definitions were updated accordingly.

7) If too many stations were known, some popup menu items would select the wrong action.  This has been (hopefully) corrected.  I think the limit was something like > 30,000 known stations.

8) MBTiles database storage for map tiles is there, but not well documented nor exposed to the user at this point.  I've got more work to do here, especially on expiration and refresh so more to come.

9) Tile server URLs are no longer limited to 128 characters. They can now go up to 260 (MAX_PATH in C).

10) KISS (aka AX.25) callsigns are now limited to A..Z and 0..9. Invalid characters are simply removed from the transmitted callsign, so beware!

11) The ToCall was updated from APWW10 to APWW11 (finally!).

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

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

PS.  So, your About box says that you're running the general release from 2012?  Follow the instructions at the following link to re-configure for development releases.

http://aprsisce.wikidot.com/doc:development-version


Re: aprsis32 and fldig kiss interface

Lynn Deffenbaugh
 

It's actually just "winfldigi" or https://groups.io/g/winfldigi


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

On 4/24/2020 5:40 PM, John Rabold wrote:
Miguel, in case it helps, Dave Freese W1HKJ is the software developer of fldigi and the other applications in the NBEMS suite. He and fldigi users support fldigi in the groups.io group named "nbems". He also supports the Windows version of the NBEMS applications in the groups.io group named "Win-FLDIGI".

John / KS6M


Re: aprsis32 and fldig kiss interface

John Rabold
 

Miguel, in case it helps, Dave Freese W1HKJ is the software developer of fldigi and the other applications in the NBEMS suite. He and fldigi users support fldigi in the groups.io group named "nbems". He also supports the Windows version of the NBEMS applications in the groups.io group named "Win-FLDIGI".

John / KS6M


Reply for membership from KB9YDK

Dean A. Nelson
 

Reply for membership from KB9YDK Dean

 

Thank you

73’s

Dean


Virus-free. www.avg.com


Re: aprsis32 and fldig kiss interface

Miguel EB5JEQ
 

OK, Lynn, thanks for your help.  I go to try  your advices, and  I  later will tell you my results.

When you have time, I tell to you my journey to the states. 

73s 


PASSWORD

Gary
 

I have registered and have my map. I would like a password.  My name is Gary Asbury N6GLS. 



Sent from my T-Mobile 4G LTE Device


Re: Using NWS County shapefiles for other packets

Jon KM8V
 

Is there a document or guide on how to gate NWS warnings and watches out over the air?

I'm not sure how to subscribe to or receive warning or alert info from the WXSVR.

Thanks & 73 de KM8V


Re: aprsis32 and fldig kiss interface

Rob Giuliano
 

As I recall from the old KPC-3 manual and such, TNC-2 KISS is the base KISS protocol.
Later there were additions that were called XKISS and I think others extensions.

Robert Giuliano
KB8RCO



On Wednesday, April 22, 2020, 5:25:49 AM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


I don't know fldigi and how it works, but I do know that APRSIS32 doesn't do UDP/IP, but only TCP/IP.  If the labels on the various options ae to be trusted, I suspect you'll want Listen/Bind selected.  If they're checkboxes and not radio buttons, you'll also want TCP/IP checked as well and maybe AX25 Decode, although I'm not sure how that would apply to KISS.

Then, configure APRSIS32 with a Simply(KISS) type port with a TCP/IP connection to 127.0.0.1 and the port should match the I/O number box in your fldigi configuration dialog.

At least, that'd be my rank amateur guess from reading the screen.

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

PS.  I have no idea what a "TNC-2 KISS protocol" is.  Usually it's either KISS with AX.25 formatted packets or non-KISS (or telnet) TCP/IP with TNC-2 formatted (ASCII, humanly readable) packets.  I've never enountered the two packet formats in the same protocol name...

On 4/22/2020 4:52 AM, miguel.bahi@... wrote:
Hi, I want to try aprsis32 in HF 30 meters with psk63 modulation of fldigi. But no success.

I configure fldigi like this 



and I am create one port in APRSIS32 "fldigi"  device ( I try simpleKISS and KISS ), tcpip  , ip 127.0.0.1 port 7342 
But I obtain fldigi port delay. 

this is the msg of the log of this port
Port(fldigi):2020-04-22T08:01:25.448 connect(@127.0.0.1) Failed
Port(fldigi):2020-04-22T08:01:25.448 Delaying Restart for 18907/20000 msec
Port(fldigi):2020-04-22T08:01:44.463 Restarting Reader...
Port(fldigi):2020-04-22T08:01:44.463 TcpReader Running on @127.0.0.1 or 127.0.0.1:7342 (6 OpenCmds, 4 CloseCmds)
Port(fldigi):2020-04-22T08:01:45.549 connect errno 10061
Port(fldigi):2020-04-22T08:01:45.549 connect(@127.0.0.1) Failed
Port(fldigi):2020-04-22T08:01:45.549 Delaying Restart for 38914/40000 msec

Any suggestion?

thanks in advance.

73 Miguel EB5JEQ.


Re: aprsis32 and fldig kiss interface

Lynn Deffenbaugh
 

I found http://www.w1hkj.com/FldigiHelp/config_io_page.html which would seem to imply that there are two possibilities.

1) Simply(KISS) in APRSIS32 nd do NOT check AX25 Decode

2) Text port type in APRSIS32 and DO check AX25 Decode

In either case, you'll definitely want both TCP/IP and Listen/Bind checked and use the I/O number from fldigi as the Port number in APRSIS32's TCP/IP connection.  In the second case, it's not really speaking "KISS", but is actually a humanly-readable TNC-2-formatted telnet-type simple TCP/IP socket connection.  If you're good with networking, you should be able to telnet to the port in option 2 and see all the received packets.

I'm leaning toward the second option because of the following note in the AX25 Decode section.

NOTE:
When actived, only valid ax25 data will be displayed to the receive panel. No un-squelched random characters will be seen.

This would seem to imply that without AX25 decode, fldigi would be running in some sort of "PASSALL" mode whereby ALL decodes are passed through without checking the FCS checksums.  This can result in seriously corrupted packets being passed because the checksum isn't actually available to the receiving program in a KISS packet so they can't be validated by anyone but the demodulator.

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

PS.  Wow, pretty cool AX.25 CRC/FCS description for MatLab of all things!


On 4/22/2020 5:22 AM, Lynn Deffenbaugh wrote:

I don't know fldigi and how it works, but I do know that APRSIS32 doesn't do UDP/IP, but only TCP/IP.  If the labels on the various options ae to be trusted, I suspect you'll want Listen/Bind selected.  If they're checkboxes and not radio buttons, you'll also want TCP/IP checked as well and maybe AX25 Decode, although I'm not sure how that would apply to KISS.

Then, configure APRSIS32 with a Simply(KISS) type port with a TCP/IP connection to 127.0.0.1 and the port should match the I/O number box in your fldigi configuration dialog.

At least, that'd be my rank amateur guess from reading the screen.

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

PS.  I have no idea what a "TNC-2 KISS protocol" is.  Usually it's either KISS with AX.25 formatted packets or non-KISS (or telnet) TCP/IP with TNC-2 formatted (ASCII, humanly readable) packets.  I've never enountered the two packet formats in the same protocol name...

On 4/22/2020 4:52 AM, miguel.bahi@... wrote:
Hi, I want to try aprsis32 in HF 30 meters with psk63 modulation of fldigi. But no success.

I configure fldigi like this 



and I am create one port in APRSIS32 "fldigi"  device ( I try simpleKISS and KISS ), tcpip  , ip 127.0.0.1 port 7342 
But I obtain fldigi port delay. 

this is the msg of the log of this port
Port(fldigi):2020-04-22T08:01:25.448 connect(@127.0.0.1) Failed
Port(fldigi):2020-04-22T08:01:25.448 Delaying Restart for 18907/20000 msec
Port(fldigi):2020-04-22T08:01:44.463 Restarting Reader...
Port(fldigi):2020-04-22T08:01:44.463 TcpReader Running on @127.0.0.1 or 127.0.0.1:7342 (6 OpenCmds, 4 CloseCmds)
Port(fldigi):2020-04-22T08:01:45.549 connect errno 10061
Port(fldigi):2020-04-22T08:01:45.549 connect(@127.0.0.1) Failed
Port(fldigi):2020-04-22T08:01:45.549 Delaying Restart for 38914/40000 msec

Any suggestion?

thanks in advance.

73 Miguel EB5JEQ.


Re: aprsis32 and fldig kiss interface

Lynn Deffenbaugh
 

I don't know fldigi and how it works, but I do know that APRSIS32 doesn't do UDP/IP, but only TCP/IP.  If the labels on the various options ae to be trusted, I suspect you'll want Listen/Bind selected.  If they're checkboxes and not radio buttons, you'll also want TCP/IP checked as well and maybe AX25 Decode, although I'm not sure how that would apply to KISS.

Then, configure APRSIS32 with a Simply(KISS) type port with a TCP/IP connection to 127.0.0.1 and the port should match the I/O number box in your fldigi configuration dialog.

At least, that'd be my rank amateur guess from reading the screen.

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

PS.  I have no idea what a "TNC-2 KISS protocol" is.  Usually it's either KISS with AX.25 formatted packets or non-KISS (or telnet) TCP/IP with TNC-2 formatted (ASCII, humanly readable) packets.  I've never enountered the two packet formats in the same protocol name...

On 4/22/2020 4:52 AM, miguel.bahi@... wrote:
Hi, I want to try aprsis32 in HF 30 meters with psk63 modulation of fldigi. But no success.

I configure fldigi like this 



and I am create one port in APRSIS32 "fldigi"  device ( I try simpleKISS and KISS ), tcpip  , ip 127.0.0.1 port 7342 
But I obtain fldigi port delay. 

this is the msg of the log of this port
Port(fldigi):2020-04-22T08:01:25.448 connect(@127.0.0.1) Failed
Port(fldigi):2020-04-22T08:01:25.448 Delaying Restart for 18907/20000 msec
Port(fldigi):2020-04-22T08:01:44.463 Restarting Reader...
Port(fldigi):2020-04-22T08:01:44.463 TcpReader Running on @127.0.0.1 or 127.0.0.1:7342 (6 OpenCmds, 4 CloseCmds)
Port(fldigi):2020-04-22T08:01:45.549 connect errno 10061
Port(fldigi):2020-04-22T08:01:45.549 connect(@127.0.0.1) Failed
Port(fldigi):2020-04-22T08:01:45.549 Delaying Restart for 38914/40000 msec

Any suggestion?

thanks in advance.

73 Miguel EB5JEQ.


aprsis32 and fldig kiss interface

Miguel EB5JEQ
 

Hi, I want to try aprsis32 in HF 30 meters with psk63 modulation of fldigi. But no success.

I configure fldigi like this 



and I am create one port in APRSIS32 "fldigi"  device ( I try simpleKISS and KISS ), tcpip  , ip 127.0.0.1 port 7342 
But I obtain fldigi port delay. 

this is the msg of the log of this port
Port(fldigi):2020-04-22T08:01:25.448 connect(@127.0.0.1) Failed
Port(fldigi):2020-04-22T08:01:25.448 Delaying Restart for 18907/20000 msec
Port(fldigi):2020-04-22T08:01:44.463 Restarting Reader...
Port(fldigi):2020-04-22T08:01:44.463 TcpReader Running on @127.0.0.1 or 127.0.0.1:7342 (6 OpenCmds, 4 CloseCmds)
Port(fldigi):2020-04-22T08:01:45.549 connect errno 10061
Port(fldigi):2020-04-22T08:01:45.549 connect(@127.0.0.1) Failed
Port(fldigi):2020-04-22T08:01:45.549 Delaying Restart for 38914/40000 msec

Any suggestion?

thanks in advance.

73 Miguel EB5JEQ.


Re: Nickname File Transfer

Lynn Deffenbaugh
 

Interesting thought, but not currently implemented, of course.  And it's not quite as easy as it might sound given that I'm using a pre-packaged lua XML reader/interpreter and that's not part of the native XML spec.

What would end up happening is that the <include>...</include> value would simply come through as an element in the parsed XML which the APRSIS32 XML processor would summarily ignore and drop on the floor on the next save.

I'll give it some thought though...

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

On 4/19/2020 11:19 AM, Rob Giuliano via groups.io wrote:
Lynn,
Is adding an 'include" (<Include>{path and xml file name}</include>) into the main xml as a means of doing simple things like this?
I realize this would make it a pain when saving the XML, a simple expansion and write out as a single file would even work as a short term fix.

Robert Giuliano
KB8RCO



On Saturday, April 18, 2020, 7:11:14 PM EDT, Bob KE6GYD <ke6gyd@...> wrote:


Our group has over 100 nicknames set up on my computer.  Is there a file containing those nicknames that can be transferred to other members computers so they don't have to recreate them all?
73
Bob
KE6GYD  


Re: Nickname File Transfer

Rob Giuliano
 

Lynn,
Is adding an 'include" (<Include>{path and xml file name}</include>) into the main xml as a means of doing simple things like this?
I realize this would make it a pain when saving the XML, a simple expansion and write out as a single file would even work as a short term fix.

Robert Giuliano
KB8RCO



On Saturday, April 18, 2020, 7:11:14 PM EDT, Bob KE6GYD <ke6gyd@...> wrote:


Our group has over 100 nicknames set up on my computer.  Is there a file containing those nicknames that can be transferred to other members computers so they don't have to recreate them all?
73
Bob
KE6GYD  


Re: Igate verification

Lynn Deffenbaugh
 

Glad to know it's all working now!  Ever the simple things trip us up.

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

On 4/19/2020 1:24 AM, Yatharth Verma via groups.io wrote:
Hi,
Indeed, Xmit was disabled on the APRS-IS port. After enabling fresh packets are being Igated. I verified this using the Igate trace log. Moreover, the packet entry made it to aprs.fi as well '2020-04-19 07:17:55 IST: RS0ISS>CQ,qAR,VU3NUF-10:>ARISS - International Space Station'.

Thank you Lynn for the quick help.

Best regards,
Yatharth
VU3NUF



On Thursday, April 16, 2020, 11:53:37 PM GMT+5:30, Lynn Deffenbaugh <kj4erj@...> wrote:


Check your Configure / Ports / APRS-IS.  I suspect you have Xmit disabled on that port which completely disables transmitting anything to the APRS-IS, including IGate packets.  Or at least you had it disabled when that packet was received and that log was generated.

You might find it beneficial to tune your radio to your local APRS frequency until we can ascertain that your IGate is working properly with all the settings.  At least there, you might get more packets received than waiting for a satellite pass.  Especially if you can generate your own APRS packets from another local radio.

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

On 4/16/2020 12:46 PM, Yatharth Verma via groups.io wrote:
Hi,
Thanks for the quick reply! I checked for Igate logs under view logs. There were 2 logs Igate(not) & Igate enabled. The Igate enabled one showed:
WinMain:2020-04-16T14:21:17.539 UZ7HO[AGW] IGating Receive-Only
WinMain:2020-04-16T14:21:17.539 ***** IGate Enabled Receive-Only *****

and the Igate(not) showed this entry:
WinMain:2020-04-16T10:42:53.908 RFtoIS:    !Xmit(APRS-IS)  (RS0ISS>CQ:>ARISS - International Space Station)
I didn't understand what Igate(not) means

Also, I checked the trace log of Packets which I suppose should show all the packets displayed in the scroller and it showed:
2020-04-16T10:42:53.908 RF[UZ7HO][1200] RS0ISS>CQ:>ARISS - International Space Station

So does it mean that the packet was Igated?

Regarding aprs.fi - till the time I received this packet from ISS I was using the callsign VU3NUF but I tweaked the settings a little bit today and added a suffix VU3NUF-10, but it was hours after receiving the packet.

Best regards,
Yatharth
VU3NUF

On Thursday, April 16, 2020, 08:43:00 PM GMT+5:30, Lynn Deffenbaugh <kj4erj@...> wrote:


Look under Enables / View Log for any IGate* logs.  Bring each of those up and enable it.  One of them should tell you whether or not packets are being gated to the APRS-IS.

However, those are not "CQ" packets from the ISS.  That's actually the ToCall or UnProto piece.  The packet is from RS0ISS (the first part before the >) with a destination (ToCall/UnProto) of CQ (the part after the > until either a comma or colon).  It has an empty path (colon immediately follows ToCall with no commas) and is actually a status packet (the > after the colon).  Therefore it has no location (the ISS never actually says where it is), so it will show up on your map at 0,0 or at the Null Island.

But one of the IGate* trace logs should be able to answer your question.

Well, sort of.  Your question was whether the packet is "reaching aprs.fi", but that is not under APRSIS32's direct control.  APRSIS32 is only responsible for delivering gated packets to your immediate upstream (directly connected) APRS-IS server.  Whether your packet actually gets distributed, and how far, through the APRS-IS is dependent on timing and the duplicate suppression rules of the APRS-IS servers.

A quick check at https://aprs.fi/?c=raw&call=RS0ISS&limit=1000&view=normal doesn't show anything from VU3NUF, which I assume (possibly incorrectly) is the callsign under which you are running APRSIS32?

Remember, aprs.fi is simply (albeit quite complex actually) a database capturing and displaying data from the APRS-IS as well as several other sources.  It is NOT the APRS-IS network.

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

On 4/16/2020 10:55 AM, Yatharth Verma via groups.io wrote:
Greetings..from India!

I have just started using APRSIS32 again after a hiatus of 2 years, therefore there is something which I need to seek help for.

First of all, about my installation:

1. Intel i5 CPU with 4 GB RAM
2. Windows 8.1 operating system
3. RTL-SDR radio dongle for RX with UZ&HO sound modem (working correctly)
4. Homebrewed QFH antenna

Now my problem:
I am receiving APRS CQ packets from an ISS pass correctly. I say correctly since it gets displayed on the sound modem screen (text pasted below):

1:Fm RS0ISS To CQ <UI R Pid=F0 Len=36> [16:12:53R] [+++]
>ARISS - International Space Station

This also reaches APRSIS32 in the log of the sound modem port:
Port(UZ7HO):2020-04-16T10:42:53.908 AGW:AX.25[0] RS0ISS>CQ:>ARISS - International Space Station

But I am unable to verify (rather I don't know how to verify), whether this packet is being Igated or not. Please help me find out this. And also whether it is reaching aprs.fi or not?

I shall be grateful for any help.

Best regards,
Yatharth
VU3NUF


Re: Igate verification

Yatharth Verma
 

Hi,
Indeed, Xmit was disabled on the APRS-IS port. After enabling fresh packets are being Igated. I verified this using the Igate trace log. Moreover, the packet entry made it to aprs.fi as well '2020-04-19 07:17:55 IST: RS0ISS>CQ,qAR,VU3NUF-10:>ARISS - International Space Station'.

Thank you Lynn for the quick help.

Best regards,
Yatharth
VU3NUF



On Thursday, April 16, 2020, 11:53:37 PM GMT+5:30, Lynn Deffenbaugh <kj4erj@...> wrote:


Check your Configure / Ports / APRS-IS.  I suspect you have Xmit disabled on that port which completely disables transmitting anything to the APRS-IS, including IGate packets.  Or at least you had it disabled when that packet was received and that log was generated.

You might find it beneficial to tune your radio to your local APRS frequency until we can ascertain that your IGate is working properly with all the settings.  At least there, you might get more packets received than waiting for a satellite pass.  Especially if you can generate your own APRS packets from another local radio.

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

On 4/16/2020 12:46 PM, Yatharth Verma via groups.io wrote:
Hi,
Thanks for the quick reply! I checked for Igate logs under view logs. There were 2 logs Igate(not) & Igate enabled. The Igate enabled one showed:
WinMain:2020-04-16T14:21:17.539 UZ7HO[AGW] IGating Receive-Only
WinMain:2020-04-16T14:21:17.539 ***** IGate Enabled Receive-Only *****

and the Igate(not) showed this entry:
WinMain:2020-04-16T10:42:53.908 RFtoIS:    !Xmit(APRS-IS)  (RS0ISS>CQ:>ARISS - International Space Station)
I didn't understand what Igate(not) means

Also, I checked the trace log of Packets which I suppose should show all the packets displayed in the scroller and it showed:
2020-04-16T10:42:53.908 RF[UZ7HO][1200] RS0ISS>CQ:>ARISS - International Space Station

So does it mean that the packet was Igated?

Regarding aprs.fi - till the time I received this packet from ISS I was using the callsign VU3NUF but I tweaked the settings a little bit today and added a suffix VU3NUF-10, but it was hours after receiving the packet.

Best regards,
Yatharth
VU3NUF

On Thursday, April 16, 2020, 08:43:00 PM GMT+5:30, Lynn Deffenbaugh <kj4erj@...> wrote:


Look under Enables / View Log for any IGate* logs.  Bring each of those up and enable it.  One of them should tell you whether or not packets are being gated to the APRS-IS.

However, those are not "CQ" packets from the ISS.  That's actually the ToCall or UnProto piece.  The packet is from RS0ISS (the first part before the >) with a destination (ToCall/UnProto) of CQ (the part after the > until either a comma or colon).  It has an empty path (colon immediately follows ToCall with no commas) and is actually a status packet (the > after the colon).  Therefore it has no location (the ISS never actually says where it is), so it will show up on your map at 0,0 or at the Null Island.

But one of the IGate* trace logs should be able to answer your question.

Well, sort of.  Your question was whether the packet is "reaching aprs.fi", but that is not under APRSIS32's direct control.  APRSIS32 is only responsible for delivering gated packets to your immediate upstream (directly connected) APRS-IS server.  Whether your packet actually gets distributed, and how far, through the APRS-IS is dependent on timing and the duplicate suppression rules of the APRS-IS servers.

A quick check at https://aprs.fi/?c=raw&call=RS0ISS&limit=1000&view=normal doesn't show anything from VU3NUF, which I assume (possibly incorrectly) is the callsign under which you are running APRSIS32?

Remember, aprs.fi is simply (albeit quite complex actually) a database capturing and displaying data from the APRS-IS as well as several other sources.  It is NOT the APRS-IS network.

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

On 4/16/2020 10:55 AM, Yatharth Verma via groups.io wrote:
Greetings..from India!

I have just started using APRSIS32 again after a hiatus of 2 years, therefore there is something which I need to seek help for.

First of all, about my installation:

1. Intel i5 CPU with 4 GB RAM
2. Windows 8.1 operating system
3. RTL-SDR radio dongle for RX with UZ&HO sound modem (working correctly)
4. Homebrewed QFH antenna

Now my problem:
I am receiving APRS CQ packets from an ISS pass correctly. I say correctly since it gets displayed on the sound modem screen (text pasted below):

1:Fm RS0ISS To CQ <UI R Pid=F0 Len=36> [16:12:53R] [+++]
>ARISS - International Space Station

This also reaches APRSIS32 in the log of the sound modem port:
Port(UZ7HO):2020-04-16T10:42:53.908 AGW:AX.25[0] RS0ISS>CQ:>ARISS - International Space Station

But I am unable to verify (rather I don't know how to verify), whether this packet is being Igated or not. Please help me find out this. And also whether it is reaching aprs.fi or not?

I shall be grateful for any help.

Best regards,
Yatharth
VU3NUF


Re: Nickname File Transfer

Fred Hillhouse
 

I don’t believe there is a direct way to transfer them. However, You may be able to copy them from your .xml and paste them in the others.

 

Be sure to back up your xml files first. It might take several tries. Of course any modification will have to be done while APRSIS32 is NOT running.

 

Fred N7FMH

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Bob KE6GYD
Sent: Saturday, April 18, 2020 7:11 PM
To: APRSISCE@groups.io
Subject: [APRSISCE] Nickname File Transfer

 

Our group has over 100 nicknames set up on my computer.  Is there a file containing those nicknames that can be transferred to other members computers so they don't have to recreate them all?
73
Bob
KE6GYD  




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com