¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. APRSISCE
  2. Messages
Single Messages Topics Expanded Polls

Re: APRS iGate stopped working!

Lynn Deffenbaugh
 

¿ªÔÆÌåÓý

Those look correct.?? Based on the log captures and aprs.fi's raw packet view, it definitely appears that you are having intermittent RF reception (or at least, getting the packets into APRSIS32) and either your instance is not running 24x7 or it is also having APRS-IS connectivity issues.?? The first bit comes from the RF packet capture logs as well as the >IGATE packets from aprs.fi's raw view.?? The last part is inferred by the lack of even beacon packets in aprs.fi's raw packet views for AB9NN-48.

For instance, on the 2nd bit, the gap in beacon timestamps at 

2024-04-28 20:21:09 EDT:?>APWW11,TCPIP*,qAC,T2YANTAI:>290025zAPRS?iGate?in?Beulah,?Michigan?-?NW?Lower?Michigan
2024-04-29 08:13:44 EDT:?>APWW11,TCPIP*,qAC,T2CSNGRAD:@121811h4437.84N/08604.35W-!INSERVICE!
And then the length of time before the >IGATE status actually reflected RF-received stations:

2024-04-29 08:13:44 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:@121811h4437.84N/08604.35W-!INSERVICE!
2024-04-29 09:07:59 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=1*W8TVI-9(9km@16<0xb0>)
2024-04-29 10:07:59 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=2,DX=1*W8TVI-9(9km@16<0xb0>)
2024-04-29 11:07:59 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=3,DIR_CNT=1,RF_CNT=5,DX=1*KD9VQI-10(103km@292<0xb0>)
2024-04-29 12:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=1,DIR_CNT=1,RF_CNT=1
2024-04-29 13:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=1*KD9VQI-10(103km@292<0xb0>)
2024-04-29 14:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=1*KD9VQI-10(103km@292<0xb0>)
2024-04-29 15:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=2,DIR_CNT=1,RF_CNT=2,DX=1*KD9VQI-10(103km@292<0xb0>)
2024-04-29 16:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=2,DIR_CNT=0,RF_CNT=2,DX=1*KD9VQI-10(103km@292<0xb0>)
And finally, the hourly packet counts I just got in response to a ?APRSS query.? These are the same hourly packet counts you can view locally by double-clicking on the upper left corner of the main APRSIS32 window.

17:00:21  New Chat Between KJ4ERJ and AB9NN-48 on 2024-04-29
17:00:23> ?igate
17:00:24< IGate[1/2] LOC_CNT=10 DIR_CNT=1 RF_CNT=21 (*2-17:00:24)
        < IGate[2/2] FT857d[Simply(KISS)] Bi-Directional+ (*2-17:00:24)
        < DX=3*KD9VQI-10(103km@292¡ã) (*2-17:00:24)
17:00:31> ?aprss
17:00:32< Ports[1/2] 04-29 08:18:10 APRS-IS OK 492 482 523 534 561 603 713+ (*2-17:00:32)
        < 634 /hr (*2-17:00:32)
        < Ports[2/2] 04-29 08:10:27 FT857d OK 48 38 8 0 0 31 68 24 /hr+ (*2-17:00:32)
First, your machine doesn't seem to know what time it is given that here at 17:00 east coast time it showed me 08:10 where you are in Michigan.

Second, those two zeros in the middle tell me that 3 and 4 hours ago, you received zero packets from the RF port that you called FT857d.?? And 2 hours ago appears incomplete because it only shows 8 packets in that hour.?? So I really think you need to look at the RF reception and decoding for your IGate as the numbers and logs seem to indicate that's where the problem is.

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



On 4/29/2024 8:56 AM, AB9NN - Jon Kreski wrote:
Here are the two screen shots requested!
Join [email protected] to automatically receive all group messages.