Date   

No APRS.FI after creating an AGW port

jabrams2
 

I finally got around to re-setting up my APRS gateway.  I notice that if you download the software using IE, the maps do not load.  Using Chrome solved that problem.  I set up APRSIS and saw both my location on the computer and APRS.FI.  After I reinstalled AGWPE with a sound card port, I am getting that APRS-IS and the name of the sound port is working, however my location disappeared from APRS.FI.  I did use the 127.0.0.1 TCP/IP port, and was receiving stations on the computer even before I reinstalled AGWPE (ham version).  Since I want to only IGATE (RF to IS, the transmitter is disabled because the antenna  is going to be used as a remote input link to our repeater system.  In APRS-IS I did not see any IGATE symbol (diamond with an I ort R), as I scrolled the available images from 30 to 150.  I previously had an IGATE symbol.

Jerry WB2ZEX (Brooklyn)


KI5SS

Don Hamrick
 

DOWNLOAD APRS


Re: NMEA logging findings - just interesting info

Rob Giuliano
 

I'll be honest, the only thing I thought odd was that the logging continued while disabled.
My comments on message related to what many (if not most) newer GPS units send by default.  I am not so sure the $GA message are that important.  They were not being sent by default.  I had to change settings to get them to show.  Same with $GB (BeiDou).  I was just curious and noticed the $GB messages were decoded.


LOG with time enabled and disabled:
WinMain:2020-12-28T18:33:58.062 Logging Disabled
WinMain:2020-12-28T18:33:58.062 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:33:58.062 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:33:58.062 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:33:59.060 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:33:59.060 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:33:59.060 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:33:59.060 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:33:59.061 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:00.060 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:00.060 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:00.060 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:00.060 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:00.060 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:01.142 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:01.142 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:01.143 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:01.143 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:01.143 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:01.530 Logging Enabled
Port(NMEA):2020-12-28T18:34:01.552 Processing[74]:$GNGGA,183401.00,4209.35129,N,08346.26423,W,1,11,0.81,233.5,M,-34.6,M,,*76
Port(NMEA):2020-12-28T18:34:01.610 Processing[56]:$GNGSA,A,3,32,31,25,16,29,22,26,03,,,,,1.59,0.81,1.37*12
Port(NMEA):2020-12-28T18:34:01.660 Processing[46]:$GNGSA,A,3,72,74,66,,,,,,,,,,1.59,0.81,1.37*1B
Port(NMEA):2020-12-28T18:34:01.735 Processing[66]:$GPGSV,4,1,13,01,06,251,,03,42,299,16,04,19,300,17,16,22,188,17*76
Port(NMEA):2020-12-28T18:34:01.735 Clearing SatellitesInView for 1/4
Port(NMEA):2020-12-28T18:34:01.801 Processing[68]:$GPGSV,4,2,13,22,51,264,22,25,21,043,27,26,54,169,22,29,11,081,28*7C
Port(NMEA):2020-12-28T18:34:01.877 Processing[64]:$GPGSV,4,3,13,31,68,038,28,32,34,110,34,44,31,224,,46,23,236,*72
Port(NMEA):2020-12-28T18:34:01.902 Processing[27]:$GPGSV,4,4,13,51,36,213,*4A
Port(NMEA):2020-12-28T18:34:01.902 Remembering 13 SatellitesInView at 4/4 (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:01.971 Processing[64]:$GLGSV,3,1,09,65,82,330,,66,16,324,16,71,02,142,,72,49,140,21*6F
Port(NMEA):2020-12-28T18:34:02.035 Processing[62]:$GLGSV,3,2,09,74,41,035,27,75,77,248,,76,23,223,,82,03,344,*6D
WinMain:2020-12-28T18:34:02.060 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:02.060 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:02.061 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:02.061 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:02.061 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:02.068 Processing[27]:$GLGSV,3,3,09,83,02,026,*51
Port(NMEA):2020-12-28T18:34:02.129 Processing[50]:$GNGLL,4209.35129,N,08346.26423,W,183401.00,A,A*61
Port(NMEA):2020-12-28T18:34:02.160 Processing[36]:$GNGST,183401.00,44,,,,4.7,5.9,11*67
Port(NMEA):2020-12-28T18:34:02.160 Unsupported($GNGST)
Port(NMEA):2020-12-28T18:34:02.201 Processing[36]:$GNZDA,183401.00,28,12,2020,00,00*7E
Port(NMEA):2020-12-28T18:34:02.201 $GPZDA Local Zone Hours=00 Minute=00
Port(NMEA):2020-12-28T18:34:02.444 Processing[66]:$GNRMC,183402.00,A,4209.35126,N,08346.26449,W,0.494,,281220,,,A*7A
Port(NMEA):2020-12-28T18:34:02.477 Processing[33]:$GNVTG,,T,,M,0.494,N,0.916,K,A*3A
Port(NMEA):2020-12-28T18:34:02.560 Processing[74]:$GNGGA,183402.00,4209.35126,N,08346.26449,W,1,11,0.86,233.1,M,-34.6,M,,*75
Port(NMEA):2020-12-28T18:34:02.619 Processing[56]:$GNGSA,A,3,32,31,25,16,29,22,26,03,,,,,1.63,0.86,1.38*13
Port(NMEA):2020-12-28T18:34:02.669 Processing[46]:$GNGSA,A,3,72,74,66,,,,,,,,,,1.63,0.86,1.38*1A
Port(NMEA):2020-12-28T18:34:02.744 Processing[66]:$GPGSV,4,1,13,01,06,251,,03,42,299,16,04,19,300,16,16,22,188,17*77
Port(NMEA):2020-12-28T18:34:02.744 Clearing SatellitesInView for 1/4
Port(NMEA):2020-12-28T18:34:02.810 Processing[68]:$GPGSV,4,2,13,22,51,264,22,25,21,043,27,26,54,169,22,29,11,081,28*7C
Port(NMEA):2020-12-28T18:34:02.885 Processing[64]:$GPGSV,4,3,13,31,68,038,28,32,34,110,34,44,31,224,,46,23,236,*72
Port(NMEA):2020-12-28T18:34:02.910 Processing[27]:$GPGSV,4,4,13,51,36,213,*4A
Port(NMEA):2020-12-28T18:34:02.910 Remembering 13 SatellitesInView at 4/4 (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:02.977 Processing[64]:$GLGSV,3,1,09,65,82,330,,66,16,324,17,71,02,142,,72,49,140,20*6F
Port(NMEA):2020-12-28T18:34:03.043 Processing[62]:$GLGSV,3,2,09,74,41,035,27,75,77,248,,76,23,223,,82,03,344,*6D
WinMain:2020-12-28T18:34:03.061 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:03.061 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:03.061 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:03.061 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:03.061 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:03.077 Processing[27]:$GLGSV,3,3,09,83,02,026,*51
Port(NMEA):2020-12-28T18:34:03.138 Processing[50]:$GNGLL,4209.35126,N,08346.26449,W,183402.00,A,A*61
Port(NMEA):2020-12-28T18:34:03.168 Processing[36]:$GNGST,183402.00,41,,,,4.7,5.9,11*61
Port(NMEA):2020-12-28T18:34:03.169 Unsupported($GNGST)
Port(NMEA):2020-12-28T18:34:03.210 Processing[36]:$GNZDA,183402.00,28,12,2020,00,00*7D
Port(NMEA):2020-12-28T18:34:03.210 $GPZDA Local Zone Hours=00 Minute=00
Port(NMEA):2020-12-28T18:34:03.435 Processing[66]:$GNRMC,183403.00,A,4209.35126,N,08346.26467,W,0.790,,281220,,,A*70
Port(NMEA):2020-12-28T18:34:03.470 Processing[33]:$GNVTG,,T,,M,0.790,N,1.464,K,A*34
Port(NMEA):2020-12-28T18:34:03.551 Processing[74]:$GNGGA,183403.00,4209.35126,N,08346.26467,W,1,11,0.86,232.8,M,-34.6,M,,*70
Port(NMEA):2020-12-28T18:34:03.610 Processing[56]:$GNGSA,A,3,32,31,25,16,29,22,26,03,,,,,1.63,0.86,1.38*13
Port(NMEA):2020-12-28T18:34:03.659 Processing[46]:$GNGSA,A,3,72,74,66,,,,,,,,,,1.63,0.86,1.38*1A
Port(NMEA):2020-12-28T18:34:03.735 Processing[66]:$GPGSV,4,1,13,01,06,251,,03,42,299,19,04,19,300,15,16,22,188,17*7B
Port(NMEA):2020-12-28T18:34:03.735 Clearing SatellitesInView for 1/4
Port(NMEA):2020-12-28T18:34:03.801 Processing[68]:$GPGSV,4,2,13,22,51,264,21,25,21,043,27,26,54,169,22,29,11,081,28*7F
Port(NMEA):2020-12-28T18:34:03.876 Processing[64]:$GPGSV,4,3,13,31,68,038,28,32,34,110,34,44,31,224,,46,23,236,*72
Port(NMEA):2020-12-28T18:34:03.901 Processing[27]:$GPGSV,4,4,13,51,36,213,*4A
Port(NMEA):2020-12-28T18:34:03.901 Remembering 13 SatellitesInView at 4/4 (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:03.970 Processing[64]:$GLGSV,3,1,09,65,82,330,,66,16,324,16,71,02,142,,72,49,140,21*6F
Port(NMEA):2020-12-28T18:34:04.034 Processing[62]:$GLGSV,3,2,09,74,41,035,27,75,77,248,,76,23,223,,82,03,344,*6D
WinMain:2020-12-28T18:34:04.060 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:04.060 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:04.060 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:04.060 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:04.060 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:04.067 Processing[27]:$GLGSV,3,3,09,83,02,026,*51
Port(NMEA):2020-12-28T18:34:04.129 Processing[50]:$GNGLL,4209.35126,N,08346.26467,W,183403.00,A,A*6C
Port(NMEA):2020-12-28T18:34:04.159 Processing[36]:$GNGST,183403.00,42,,,,4.7,6.0,11*69
Port(NMEA):2020-12-28T18:34:04.159 Unsupported($GNGST)
Port(NMEA):2020-12-28T18:34:04.201 Processing[36]:$GNZDA,183403.00,28,12,2020,00,00*7C
Port(NMEA):2020-12-28T18:34:04.201 $GPZDA Local Zone Hours=00 Minute=00
Port(NMEA):2020-12-28T18:34:04.424 Processing[66]:$GNRMC,183404.00,A,4209.35124,N,08346.26482,W,0.740,,281220,,,A*73
Port(NMEA):2020-12-28T18:34:04.457 Processing[33]:$GNVTG,,T,,M,0.740,N,1.371,K,A*3A
Port(NMEA):2020-12-28T18:34:04.541 Processing[74]:$GNGGA,183404.00,4209.35124,N,08346.26482,W,1,11,0.86,232.7,M,-34.6,M,,*71
Port(NMEA):2020-12-28T18:34:04.599 Processing[56]:$GNGSA,A,3,32,31,25,16,29,22,26,03,,,,,1.63,0.86,1.38*13
Port(NMEA):2020-12-28T18:34:04.649 Processing[46]:$GNGSA,A,3,72,74,66,,,,,,,,,,1.63,0.86,1.38*1A
Port(NMEA):2020-12-28T18:34:04.724 Processing[66]:$GPGSV,4,1,13,01,06,251,,03,42,299,20,04,19,300,15,16,22,188,18*7E
Port(NMEA):2020-12-28T18:34:04.724 Clearing SatellitesInView for 1/4
Port(NMEA):2020-12-28T18:34:04.790 Processing[68]:$GPGSV,4,2,13,22,51,264,22,25,21,043,26,26,54,169,22,29,11,081,28*7D
Port(NMEA):2020-12-28T18:34:04.865 Processing[64]:$GPGSV,4,3,13,31,68,038,28,32,34,110,34,44,31,224,,46,23,236,*72
Port(NMEA):2020-12-28T18:34:04.890 Processing[27]:$GPGSV,4,4,13,51,36,213,*4A
Port(NMEA):2020-12-28T18:34:04.891 Remembering 13 SatellitesInView at 4/4 (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:04.957 Processing[64]:$GLGSV,3,1,09,65,82,330,,66,16,324,17,71,02,142,,72,49,140,20*6F
Port(NMEA):2020-12-28T18:34:05.024 Processing[62]:$GLGSV,3,2,09,74,41,035,27,75,77,248,,76,23,223,,82,03,344,*6D
Port(NMEA):2020-12-28T18:34:05.057 Processing[27]:$GLGSV,3,3,09,83,02,026,*51
WinMain:2020-12-28T18:34:05.061 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:05.062 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:05.062 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:05.062 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:05.062 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:05.118 Processing[50]:$GNGLL,4209.35124,N,08346.26482,W,183404.00,A,A*62
Port(NMEA):2020-12-28T18:34:05.148 Processing[36]:$GNGST,183404.00,41,,,,4.7,6.1,11*6C
Port(NMEA):2020-12-28T18:34:05.149 Unsupported($GNGST)
Port(NMEA):2020-12-28T18:34:05.190 Processing[36]:$GNZDA,183404.00,28,12,2020,00,00*7B
Port(NMEA):2020-12-28T18:34:05.190 $GPZDA Local Zone Hours=00 Minute=00
Port(NMEA):2020-12-28T18:34:05.429 Processing[66]:$GNRMC,183405.00,A,4209.35121,N,08346.26482,W,0.674,,281220,,,A*71
Port(NMEA):2020-12-28T18:34:05.462 Processing[33]:$GNVTG,,T,,M,0.674,N,1.249,K,A*36
Port(NMEA):2020-12-28T18:34:05.545 Processing[74]:$GNGGA,183405.00,4209.35121,N,08346.26482,W,1,11,0.86,232.8,M,-34.6,M,,*7A
Port(NMEA):2020-12-28T18:34:05.604 Processing[56]:$GNGSA,A,3,32,31,25,16,29,22,26,03,,,,,1.63,0.86,1.38*13
Port(NMEA):2020-12-28T18:34:05.654 Processing[46]:$GNGSA,A,3,72,74,66,,,,,,,,,,1.63,0.86,1.38*1A
Port(NMEA):2020-12-28T18:34:05.728 Processing[68]:$GPGSV,4,1,13,01,06,251,12,03,42,299,20,04,19,300,14,16,22,188,18*7C
Port(NMEA):2020-12-28T18:34:05.728 Clearing SatellitesInView for 1/4
Port(NMEA):2020-12-28T18:34:05.803 Processing[68]:$GPGSV,4,2,13,22,51,264,23,25,21,043,26,26,54,169,20,29,11,081,28*7E
Port(NMEA):2020-12-28T18:34:05.870 Processing[64]:$GPGSV,4,3,13,31,68,038,28,32,34,110,33,44,31,224,,46,23,236,*75
Port(NMEA):2020-12-28T18:34:05.895 Processing[27]:$GPGSV,4,4,13,51,36,213,*4A
Port(NMEA):2020-12-28T18:34:05.895 Remembering 13 SatellitesInView at 4/4 (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:05.970 Processing[64]:$GLGSV,3,1,09,65,82,330,,66,16,324,17,71,02,142,,72,49,140,20*6F
Port(NMEA):2020-12-28T18:34:06.037 Processing[62]:$GLGSV,3,2,09,74,41,035,26,75,77,248,,76,23,223,,82,03,344,*6C
WinMain:2020-12-28T18:34:06.060 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:06.061 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:06.061 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:06.061 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:06.061 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
Port(NMEA):2020-12-28T18:34:06.062 Processing[27]:$GLGSV,3,3,09,83,02,026,*51
Port(NMEA):2020-12-28T18:34:06.123 Processing[50]:$GNGLL,4209.35121,N,08346.26482,W,183405.00,A,A*66
Port(NMEA):2020-12-28T18:34:06.162 Processing[36]:$GNGST,183405.00,41,,,,4.7,6.1,11*6D
Port(NMEA):2020-12-28T18:34:06.162 Unsupported($GNGST)
Port(NMEA):2020-12-28T18:34:06.197 Processing[36]:$GNZDA,183405.00,28,12,2020,00,00*7A
Port(NMEA):2020-12-28T18:34:06.198 $GPZDA Local Zone Hours=00 Minute=00
Port(NMEA):2020-12-28T18:34:06.433 Processing[66]:$GNRMC,183406.00,A,4209.35122,N,08346.26459,W,0.554,,281220,,,A*76
Port(NMEA):2020-12-28T18:34:06.469 Processing[33]:$GNVTG,,T,,M,0.554,N,1.026,K,A*3C
WinMain:2020-12-28T18:34:06.527 Logging Disabled
WinMain:2020-12-28T18:34:07.060 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:07.060 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:07.060 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:07.060 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:07.060 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:08.061 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:08.061 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:08.061 Failed To Find PRN 73 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:08.061 Failed To Find PRN 80 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:08.061 Failed To Find PRN 87 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:09.061 Failed To Find PRN 70 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )
WinMain:2020-12-28T18:34:09.061 Failed To Find PRN 71 in 13 in view (1 3 4 16 22 25 26 29 31 32 44 46 51 )

Sample $GA messages
18:38:15  $GPGGA,183815.00,4209.34878,N,08346.26034,W,1,12,0.74,253.0,M,-34.6,M,,*65
18:38:54  $GAGGA,183854.00,4209.34753,N,08346.26507,W,1,12,0.74,241.8,M,-34.6,M,,*79

18:38:15  $GPGSA,A,3,32,31,25,16,29,22,26,03,,,,,1.54,0.74,1.35*09
18:38:54  $GAGSA,A,3,32,31,25,16,29,22,26,03,,,,,1.55,0.74,1.36*1A

18:38:15  $GPGLL,4209.34878,N,08346.26034,W,183815.00,A,A*78
18:38:54  $GAGLL,4209.34753,N,08346.26507,W,183854.00,A,A*6F

18:38:15  $GPGST,183815.00,39,,,,4.4,5.2,13*70
18:38:54  $GAGST,183854.00,38,,,,3.5,4.2,9.2*45

18:38:15  $GPZDA,183815.00,28,12,2020,00,00*69
18:38:54  $GAZDA,183854.00,28,12,2020,00,00*7D

18:38:16  $GPRMC,183816.00,A,4209.34865,N,08346.26059,W,0.110,,281220,,,A*6E
18:38:55  $GARMC,183855.00,A,4209.34763,N,08346.26503,W,0.225,,281220,,,A*7E

18:38:16  $GPVTG,,T,,M,0.110,N,0.204,K,A*25
18:38:55  $GAVTG,,T,,M,0.225,N,0.416,K,A*34

Looks like the $GA message formats match.

Robert Giuliano
KB8RCO



On Monday, December 28, 2020, 12:41:26 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 70 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )
This error is when APRSIS32 attempts to match up the satellites in view by PRN # to put the Configure / Screen / Satellites numbers inside the circle based on azimuth and elevation.  I'll double-check that the sentences would probably pick that up.  If you could turn on logging for a short bit when you're getting the errors, it might help.  The errors SHOULD be there regardless of the Enable setting.

I'll also take a look at what talkers are supported and add $GA if you can confirm that the remainder of the sentence format matches the other talkers.

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


On 12/28/2020 11:17 AM, Rob Giuliano via groups.io wrote:
<snip>


Re: NMEA logging findings - just interesting info

Lynn Deffenbaugh
 

WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 70 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )
This error is when APRSIS32 attempts to match up the satellites in view by PRN # to put the Configure / Screen / Satellites numbers inside the circle based on azimuth and elevation.  I'll double-check that the sentences would probably pick that up.  If you could turn on logging for a short bit when you're getting the errors, it might help.  The errors SHOULD be there regardless of the Enable setting.

I'll also take a look at what talkers are supported and add $GA if you can confirm that the remainder of the sentence format matches the other talkers.

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


On 12/28/2020 11:17 AM, Rob Giuliano via groups.io wrote:
I am running APRSIS32 2020-10-27 1838 (Development Version) and noticed something different about NMEA logging.

I am running the same uBlox M8 modules I use at work with a different configuration. 
On all units the port I am using sends only NMEA strings (no ubx or RTCM#).
When I use a work GPS with APRSIS32, I get errors in the log, but only when logging is disabled?

Port(NMEA):2020-12-28T15:08:36.452 Processing[66]:$GNRMC,150836.00,A,4209.35008,N,08346.26937,W,0.356,,281220,,,A*7F
WinMain:2020-12-28T15:08:36.477 Logging Disabled
WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 70 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )
WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 71 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )
WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 73 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )
WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 80 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )

Digging a little deeper, I find the configuration differences between errors and no errors are:
Key settings with Errors
Numbering used bfor SVs not supported by NMEA:    Strict(no output)
                                                              Main Talker ID:    System dependent
                                                               GSV Talker ID:    GNSS Specific (or Use main Talker ID)

FIX: To fix it, I change the Main Talker ID to GPS(GPS) and GVS Talker ID 'must be' Use main Talker ID to stop reporting errors.

After that, I can change Numbering ... NMEA or  Main Talker ID without errors, until GVS Talker ID gets changed to GNSS Specific, then the erros return and both settings (Main & GSV) must be as specified above to reset it.

Interesting, the GPS information appears to update properly the entire time. 

I am happy to report that APRSIS32 does not restrict decode to $GPxxx strings, but seems to accept $GLxxx, $GNxxx, and $GBxxx.  It goesn't seem to like the Galileo ($GAxxx) strings for the same message types (RMC, GGA, GLL, etc.). 

Thanks for supporting multiple formats as most modern GPS units now seem to send the combined ($GNxxx) messages by default.

Robert Giuliano
KB8RCO


NMEA logging findings - just interesting info

Rob Giuliano
 

I am running APRSIS32 2020-10-27 1838 (Development Version) and noticed something different about NMEA logging.

I am running the same uBlox M8 modules I use at work with a different configuration. 
On all units the port I am using sends only NMEA strings (no ubx or RTCM#).
When I use a work GPS with APRSIS32, I get errors in the log, but only when logging is disabled?

Port(NMEA):2020-12-28T15:08:36.452 Processing[66]:$GNRMC,150836.00,A,4209.35008,N,08346.26937,W,0.356,,281220,,,A*7F
WinMain:2020-12-28T15:08:36.477 Logging Disabled
WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 70 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )
WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 71 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )
WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 73 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )
WinMain:2020-12-28T15:08:37.060 Failed To Find PRN 80 in 16 in view (1 8 10 12 15 18 20 21 23 24 25 31 32 44 46 51 )

Digging a little deeper, I find the configuration differences between errors and no errors are:
Key settings with Errors
Numbering used bfor SVs not supported by NMEA:    Strict(no output)
                                                              Main Talker ID:    System dependent
                                                               GSV Talker ID:    GNSS Specific (or Use main Talker ID)

FIX: To fix it, I change the Main Talker ID to GPS(GPS) and GVS Talker ID 'must be' Use main Talker ID to stop reporting errors.

After that, I can change Numbering ... NMEA or  Main Talker ID without errors, until GVS Talker ID gets changed to GNSS Specific, then the erros return and both settings (Main & GSV) must be as specified above to reset it.

Interesting, the GPS information appears to update properly the entire time. 

I am happy to report that APRSIS32 does not restrict decode to $GPxxx strings, but seems to accept $GLxxx, $GNxxx, and $GBxxx.  It goesn't seem to like the Galileo ($GAxxx) strings for the same message types (RMC, GGA, GLL, etc.). 

Thanks for supporting multiple formats as most modern GPS units now seem to send the combined ($GNxxx) messages by default.

Robert Giuliano
KB8RCO


Re: Newbie question...

Lynn Deffenbaugh
 

If it were just a display name, that would have happened a long time ago.  But there is no "display" name.  The name in the drop-down is the actual port type that is stored directly in the XML configuration file and is used to switch to the proper section of code to support the port.

So, changing the "name" would invalidate all of the port configurations that currently ask for "KISS".

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


On 12/17/2020 8:14 PM, Arnold Harding. - KQ6DI wrote:
Can't the displayed name just be changed to KISS (Kenwood)?  So the only change is what the user sees when selecting KISS.
 
That's my thought, but it's never just that simple.
Arnold, KQ6DI
On 12/17/2020 4:12 PM Lynn Deffenbaugh <kj4erj@...> wrote:
 
 

Yeah, and hindsight is always 20/20.  I did the KISS when it was the only mode supported and Kenwood is all I had access to.  And since then, I haven't figured out how to change it without breaking all of the installations out there that are using a KISS-type port.  Eventually I'll get an inspiration.

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


On 12/17/2020 7:03 PM, James Ewen wrote:
I would suggest not naming the Kenwood specific configuration as KISS for a start. Most implementations that have a KISS mode configuration have it set to work in KISS mode. Something for a specific hardware configuration like the Kenwood radio would probably be better labelled Kenwood KISS. 
 
Clarity is a wonderful thing to strive for. 
 
Hoping everyone stays safe, healthy and sane this non-traditional holiday season. 
 
James
VE6SRV 
 
On Thu, Dec 17, 2020 at 4:56 PM Lynn Deffenbaugh < kj4erj@...> wrote:

Good to know that was it.  I really need to figure out how to document the legacy "KISS" mode better somewhere.

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


On 12/17/2020 4:35 PM, W9PFD wrote:
Thanks for the info and explanation on "COM4 OK"

You were correct that I had selected KISS rather than Simply(KISS).  Created a new port using Simply(KISS),  [and deleted the old one]  and PERMed  INTFACE KISS  into the KPC2.  Appears to be working on RF channel as well as Internet now.

A lot to learn in switching software.

Thanks for your help and your work on this.

Dave - W9PFD
--
James
VE6SRV


Re: Newbie question...

Arnold Harding - KQ6DI
 

Can't the displayed name just be changed to KISS (Kenwood)?  So the only change is what the user sees when selecting KISS.
 
That's my thought, but it's never just that simple.
Arnold, KQ6DI

On 12/17/2020 4:12 PM Lynn Deffenbaugh <kj4erj@...> wrote:
 
 

Yeah, and hindsight is always 20/20.  I did the KISS when it was the only mode supported and Kenwood is all I had access to.  And since then, I haven't figured out how to change it without breaking all of the installations out there that are using a KISS-type port.  Eventually I'll get an inspiration.

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


On 12/17/2020 7:03 PM, James Ewen wrote:
I would suggest not naming the Kenwood specific configuration as KISS for a start. Most implementations that have a KISS mode configuration have it set to work in KISS mode. Something for a specific hardware configuration like the Kenwood radio would probably be better labelled Kenwood KISS. 
 
Clarity is a wonderful thing to strive for. 
 
Hoping everyone stays safe, healthy and sane this non-traditional holiday season. 
 
James
VE6SRV 
 
On Thu, Dec 17, 2020 at 4:56 PM Lynn Deffenbaugh < kj4erj@...> wrote:

Good to know that was it.  I really need to figure out how to document the legacy "KISS" mode better somewhere.

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


On 12/17/2020 4:35 PM, W9PFD wrote:
Thanks for the info and explanation on "COM4 OK"

You were correct that I had selected KISS rather than Simply(KISS).  Created a new port using Simply(KISS),  [and deleted the old one]  and PERMed  INTFACE KISS  into the KPC2.  Appears to be working on RF channel as well as Internet now.

A lot to learn in switching software.

Thanks for your help and your work on this.

Dave - W9PFD
--
James
VE6SRV


Re: Newbie question...

Lynn Deffenbaugh
 

Yeah, and hindsight is always 20/20.  I did the KISS when it was the only mode supported and Kenwood is all I had access to.  And since then, I haven't figured out how to change it without breaking all of the installations out there that are using a KISS-type port.  Eventually I'll get an inspiration.

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


On 12/17/2020 7:03 PM, James Ewen wrote:
I would suggest not naming the Kenwood specific configuration as KISS for a start. Most implementations that have a KISS mode configuration have it set to work in KISS mode. Something for a specific hardware configuration like the Kenwood radio would probably be better labelled Kenwood KISS. 

Clarity is a wonderful thing to strive for. 

Hoping everyone stays safe, healthy and sane this non-traditional holiday season. 

James
VE6SRV 

On Thu, Dec 17, 2020 at 4:56 PM Lynn Deffenbaugh <kj4erj@...> wrote:

Good to know that was it.  I really need to figure out how to document the legacy "KISS" mode better somewhere.

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


On 12/17/2020 4:35 PM, W9PFD wrote:
Thanks for the info and explanation on "COM4 OK"

You were correct that I had selected KISS rather than Simply(KISS).  Created a new port using Simply(KISS),  [and deleted the old one]  and PERMed  INTFACE KISS  into the KPC2.  Appears to be working on RF channel as well as Internet now.

A lot to learn in switching software.

Thanks for your help and your work on this.

Dave - W9PFD
--
James
VE6SRV


Re: Newbie question...

James Ewen
 

I would suggest not naming the Kenwood specific configuration as KISS for a start. Most implementations that have a KISS mode configuration have it set to work in KISS mode. Something for a specific hardware configuration like the Kenwood radio would probably be better labelled Kenwood KISS. 

Clarity is a wonderful thing to strive for. 

Hoping everyone stays safe, healthy and sane this non-traditional holiday season. 

James
VE6SRV 

On Thu, Dec 17, 2020 at 4:56 PM Lynn Deffenbaugh <kj4erj@...> wrote:

Good to know that was it.  I really need to figure out how to document the legacy "KISS" mode better somewhere.

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


On 12/17/2020 4:35 PM, W9PFD wrote:
Thanks for the info and explanation on "COM4 OK"

You were correct that I had selected KISS rather than Simply(KISS).  Created a new port using Simply(KISS),  [and deleted the old one]  and PERMed  INTFACE KISS  into the KPC2.  Appears to be working on RF channel as well as Internet now.

A lot to learn in switching software.

Thanks for your help and your work on this.

Dave - W9PFD

--
James
VE6SRV


Re: Newbie question...

Lynn Deffenbaugh
 

Good to know that was it.  I really need to figure out how to document the legacy "KISS" mode better somewhere.

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


On 12/17/2020 4:35 PM, W9PFD wrote:
Thanks for the info and explanation on "COM4 OK"

You were correct that I had selected KISS rather than Simply(KISS).  Created a new port using Simply(KISS),  [and deleted the old one]  and PERMed  INTFACE KISS  into the KPC2.  Appears to be working on RF channel as well as Internet now.

A lot to learn in switching software.

Thanks for your help and your work on this.

Dave - W9PFD


Re: Newbie question...

W9PFD
 

Thanks for the info and explanation on "COM4 OK"

You were correct that I had selected KISS rather than Simply(KISS).  Created a new port using Simply(KISS),  [and deleted the old one]  and PERMed  INTFACE KISS  into the KPC2.  Appears to be working on RF channel as well as Internet now.

A lot to learn in switching software.

Thanks for your help and your work on this.

Dave - W9PFD


Re: Newbie question...

Lynn Deffenbaugh
 

What port type did you tell APRSIS32 to use when you configured the RF port?  It doesn't have any port type that sets up a KPC2 and should be set to Simply(KISS) which will cause it to expect the TNC to already be locked into KISS mode before it connects.

I suspect you have selected a KISS type port which is actually specific to the Kenwood APRS radio TNCs, not KPCs.

The "COM4 OK" simply means that the communications port was opened successfully.  It does not indicate any sort of actual communications with the TNC.

APRSIS32 doesn't want any flow control on the port.

If you open Enables / View Logs / Port(COM4) and enable that window, you might learn more about what's going on.

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


On 12/17/2020 11:33 AM, W9PFD wrote:
Hello:

I am new to APRSISCE/32.  I have followed the setup instructions and all works well on the Internet connections, but the radio port does not want to transmit, and I do not see from the logs that it is receiving either.  I have checked all the steps in the article  "Why won't APRSISCE/32 Transmit?"  and they are all correct.  The TNC and the radio all work fine using a terminal program.  [And worked with a previous APRS program...]  Message at top of screen indicates  "APRS-IS OK"  and  "COM4 OK".  The OS on the computer is Vista, and the TNC is a KPC2 connected via a hardware COM port.

When the program starts and is putting the TNC into KISS mode, what flow control type does APRSISCE/32 expect to see?

Any other suggestions?

TNX + 73,

Dave, W9PFD



  
 


Newbie question...

W9PFD
 

Hello:

I am new to APRSISCE/32.  I have followed the setup instructions and all works well on the Internet connections, but the radio port does not want to transmit, and I do not see from the logs that it is receiving either.  I have checked all the steps in the article  "Why won't APRSISCE/32 Transmit?"  and they are all correct.  The TNC and the radio all work fine using a terminal program.  [And worked with a previous APRS program...]  Message at top of screen indicates  "APRS-IS OK"  and  "COM4 OK".  The OS on the computer is Vista, and the TNC is a KPC2 connected via a hardware COM port.

When the program starts and is putting the TNC into KISS mode, what flow control type does APRSISCE/32 expect to see?

Any other suggestions?

TNX + 73,

Dave, W9PFD



  
 


Re: RF but not APRS.FI

Mike Cooper
 

Problem is solved. TNC's were switched and it all began working ok. The original TNC was reset and a backup configuration file uploaded and it was put back on the air and it is working fine. That "0x1b" was not readily apparent when looking at the BT string.  It is interesting that both AGWTracker and APRSIS32 would read and accurately position the Beacon information. Thanks to everyone for help in figuring this one out.

Mike W7OSG


Re: RF but not APRS.FI

Greg D
 

I believe 0x1b is the "ESC" key.  Control-[ also generates the same code on some keyboards, so perhaps it's a problem with fat-fingers.

Greg  KO6TH


Lynn Deffenbaugh wrote:

It's an invalid symbol code.  <0x1b> is not a valid symbol.

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

PS.  Here's Hessu's answer:

On Wed, 16 Dec 2020, Lynn W Deffenbaugh (Mr) wrote:

Hessu,

Do you know if aprs.fi's APRS parser is case sensitive on the N/S and E/W in an uncompressed
position packet?  Consider:

2020-12-16 15:47:53EST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [I
nvalid uncompressed location]

No, it's case insensitive for that, but it wouldn't accept it due to the invalid symbol code character (0x1B hex).

https://github.com/hessu/perl-aprs-fap/blob/master/FAP.pm#L1512

  - Hessu



On 12/16/2020 3:54 PM, Lynn Deffenbaugh wrote:

I'll ask Hessu on aprs.fi, but I suspect you are correct.  Didn't even think to go to the raw packets when I saw the map date was from back in November!

These were gated by KG7KMV, not W7OSG, but that has nothing to do with why they're not showing at aprs.fi.

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


On 12/16/2020 3:50 PM, Mike Heskett WB5QLD wrote:

N7DJX has invalid position, Is it because of n & w instead of N & W

 

2020-12-16 13:47:53 CST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [Invalid uncompressed location]
2020-12-16 14:10:05 CST: N7DJX>ID,WAREAG,qAR,KG7KMV:N7DJX/R WIDE2-2/D N7DJX-1/B
2020-12-16 14:17:53 CST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [Invalid uncompressed location]
2020-12-16 14:30:31 CST: N7DJX>ID,WAREAG,qAR,KG7KMV:N7DJX/R WIDE2-2/D N7DJX-1/B

 

Michael Heskett

WB5QLD

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Wednesday, December 16, 2020 2:47 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] RF but not APRS.FI

 

First, it appears that your APRS-IS port is down. That would explain your station not igating anyone.  In the upper right corner, do you see it alternating between your port status and shows that APRS-IS is down?

Enables / View Logs / Port(APRS-IS) and enable that log and you might see what is going on with your APRS-IS port.

But I do see that you are copying N7DJX directly, a total of 5 packets in the past 2 hours.

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

On 12/16/2020 3:16 PM, Michael wrote:

Not me, but N7DJX


Mike W7OSG



Re: RF but not APRS.FI

Lynn Deffenbaugh
 

It's an invalid symbol code.  <0x1b> is not a valid symbol.

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

PS.  Here's Hessu's answer:

On Wed, 16 Dec 2020, Lynn W Deffenbaugh (Mr) wrote:

Hessu,

Do you know if aprs.fi's APRS parser is case sensitive on the N/S and E/W in an uncompressed
position packet?  Consider:

2020-12-16 15:47:53EST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [I
nvalid uncompressed location]

No, it's case insensitive for that, but it wouldn't accept it due to the invalid symbol code character (0x1B hex).

https://github.com/hessu/perl-aprs-fap/blob/master/FAP.pm#L1512

  - Hessu



On 12/16/2020 3:54 PM, Lynn Deffenbaugh wrote:

I'll ask Hessu on aprs.fi, but I suspect you are correct.  Didn't even think to go to the raw packets when I saw the map date was from back in November!

These were gated by KG7KMV, not W7OSG, but that has nothing to do with why they're not showing at aprs.fi.

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


On 12/16/2020 3:50 PM, Mike Heskett WB5QLD wrote:

N7DJX has invalid position, Is it because of n & w instead of N & W

 

2020-12-16 13:47:53 CST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [Invalid uncompressed location]
2020-12-16 14:10:05 CST: N7DJX>ID,WAREAG,qAR,KG7KMV:N7DJX/R WIDE2-2/D N7DJX-1/B
2020-12-16 14:17:53 CST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [Invalid uncompressed location]
2020-12-16 14:30:31 CST: N7DJX>ID,WAREAG,qAR,KG7KMV:N7DJX/R WIDE2-2/D N7DJX-1/B

 

Michael Heskett

WB5QLD

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Wednesday, December 16, 2020 2:47 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] RF but not APRS.FI

 

First, it appears that your APRS-IS port is down. That would explain your station not igating anyone.  In the upper right corner, do you see it alternating between your port status and shows that APRS-IS is down?

Enables / View Logs / Port(APRS-IS) and enable that log and you might see what is going on with your APRS-IS port.

But I do see that you are copying N7DJX directly, a total of 5 packets in the past 2 hours.

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

On 12/16/2020 3:16 PM, Michael wrote:

Not me, but N7DJX


Mike W7OSG


Re: RF but not APRS.FI

Lynn Deffenbaugh
 

Don't need to for this test.  I believe Mike, WB5QLD nailed the issue with N7DJX.

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


On 12/16/2020 3:54 PM, Michael wrote:
Yes, it is down on purpose, my experimenting. I will turn it back on

Mike W7OSG


Re: RF but not APRS.FI

Lynn Deffenbaugh
 

I'll ask Hessu on aprs.fi, but I suspect you are correct.  Didn't even think to go to the raw packets when I saw the map date was from back in November!

These were gated by KG7KMV, not W7OSG, but that has nothing to do with why they're not showing at aprs.fi.

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


On 12/16/2020 3:50 PM, Mike Heskett WB5QLD wrote:

N7DJX has invalid position, Is it because of n & w instead of N & W

 

2020-12-16 13:47:53 CST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [Invalid uncompressed location]
2020-12-16 14:10:05 CST: N7DJX>ID,WAREAG,qAR,KG7KMV:N7DJX/R WIDE2-2/D N7DJX-1/B
2020-12-16 14:17:53 CST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [Invalid uncompressed location]
2020-12-16 14:30:31 CST: N7DJX>ID,WAREAG,qAR,KG7KMV:N7DJX/R WIDE2-2/D N7DJX-1/B

 

Michael Heskett

WB5QLD

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Wednesday, December 16, 2020 2:47 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] RF but not APRS.FI

 

First, it appears that your APRS-IS port is down. That would explain your station not igating anyone.  In the upper right corner, do you see it alternating between your port status and shows that APRS-IS is down?

Enables / View Logs / Port(APRS-IS) and enable that log and you might see what is going on with your APRS-IS port.

But I do see that you are copying N7DJX directly, a total of 5 packets in the past 2 hours.

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

On 12/16/2020 3:16 PM, Michael wrote:

Not me, but N7DJX


Mike W7OSG


Re: RF but not APRS.FI

Michael
 

Yes, it is down on purpose, my experimenting. I will turn it back on

Mike W7OSG


Re: RF but not APRS.FI

Mike Heskett WB5QLD
 

N7DJX has invalid position, Is it because of n & w instead of N & W

 

2020-12-16 13:47:53 CST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [Invalid uncompressed location]
2020-12-16 14:10:05 CST: N7DJX>ID,WAREAG,qAR,KG7KMV:N7DJX/R WIDE2-2/D N7DJX-1/B
2020-12-16 14:17:53 CST: N7DJX>BEACON,WAREAG,qAR,KG7KMV:!4334.26n/11619.11w<0x1b>w-Hara war Eagle 147.04 pl 123 [Invalid uncompressed location]
2020-12-16 14:30:31 CST: N7DJX>ID,WAREAG,qAR,KG7KMV:N7DJX/R WIDE2-2/D N7DJX-1/B

 

Michael Heskett

WB5QLD

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Wednesday, December 16, 2020 2:47 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] RF but not APRS.FI

 

First, it appears that your APRS-IS port is down. That would explain your station not igating anyone.  In the upper right corner, do you see it alternating between your port status and shows that APRS-IS is down?

Enables / View Logs / Port(APRS-IS) and enable that log and you might see what is going on with your APRS-IS port.

But I do see that you are copying N7DJX directly, a total of 5 packets in the past 2 hours.

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

On 12/16/2020 3:16 PM, Michael wrote:

Not me, but N7DJX


Mike W7OSG

921 - 940 of 35992