[aprssig] IGate to APRS-IS data transfer delays

[Tim Cunningham]

At any given time I can see this type of delay. KG4PID-15 has been connected 
to "third.aprs.net" core server for 05h32m51.457s, so it is not a dial on 
demand system.

Are there IGates that dial on demand?


Here is a current snapshot of current data that shows the delay:

20060718221851,W4GPS-7>APZWX,AL2-2,qAo,N8DEU-4:!!000000B303B81F0027A00403015D----00C6051D00000000
20060718222108,W4GPS-7>APZWX,AL2-1,qAo,KG4PID-15:!!000000B303B81F0027A00403015D----00C6051D00000000
2min 17sec delay with 1 hop

20060718222150,W4GPS-7>APZWX,AL2-2,qAo,N8DEU-4:!!000000B303B81F0027A104030169----00C6052000000000
20060718222338,W4GPS-7>APZWX,AL2-2,qAo,KG4PID-15:!!000000B303B81F0027A104030169----00C6052000000000
1min 48sec delay direct

20060718222450,W4GPS-7>APZWX,AL2-2,qAo,N8DEU-4:!!000000B303B61F00279F04050165----00C6052300000000
20060718222742,W4GPS-7>APZWX,AL2-2,qAo,KG4PID-15:!!000000B303B61F00279F04050165----00C6052300000000
2min 52sec delay direct

20060718222738,W4GPS-7>APZ19,qAo,N8DEU-4:!3438.07NS08630.74W#PHG5630/W3,ALn 
Huntsville Alabama
20060718222958,W4GPS-7>APZ19,qAo,KG4PID-15:!3438.07NS08630.74W#PHG5630/W3,ALn 
Huntsville Alabama
2min 20sec delay direct

20060718222750,W4GPS-7>APZWX,AL2-2,qAo,N8DEU-4:!!000000B303B61F00279F04060163----00C6052600000000
20060718223020,W4GPS-7>APZWX,AL2-2,qAo,KG4PID-15:!!000000B303B61F00279F04060163----00C6052600000000
2min 30sec delay direct


The weather packets are easy to identify as the same packet. Clearly we see 
some variable delay between the same packets heard direct by two IGates. 
N8DEU-4 (APRS+SA) was connected to "first.aprs.net" port 14580 using the 
filter "r/34/-86/200 t/n" and KG4PID-15 (UI-View32 V2.03) was connected to 
"third.aprs.net" port 14580 using the filter "m/100". Depending on the CPU 
speed and the I/O connection speed the range parameter on the filter may 
need to be reduced further to gain more responsive transfer to the APRS-IS. 
Just a thought.



73's,
Tim - N8DEU
Huntsville, Alabama






----- Original Message ----- 
From: "Ben Jackson" <ben at ben.com>
To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org>
Sent: Tuesday, July 18, 2006 5:16 PM
Subject: Re: [aprssig] IGate to APRS-IS data transfer delays


> On Tue, Jul 18, 2006 at 04:57:58PM -0500, Tim Cunningham wrote:
>>
>> 20060715003528,W4GPS-7>APZ19,WIDE2-2,qAo,N8DEU-4:!3438.07NS08630.74W#PHG5630/W3,ALn
>> Huntsville Alabama
>> 20060715003639,W4GPS-7>APZ19,WIDE2-2,qAo,KG4PID-15:!3438.07NS08630.74W#PHG5630/W3,ALn
>> Huntsville Alabama
>>
>> In the above example 2 IGates hear the same packet from W4GPS-7. They are
>> N8DEU-4 and KG4PID-15.
>
> Did you look for other packets heard by KG4PID-15 (or both Igates) right
> before that packet?  Was it gating timely right up until that packet?  Or
> was there some inactivity?  I'm wondering if you could see this kind of
> result with a demand-dial internet connection.
>
> -- 
> Ben Jackson AD7GD
> <ben at ben.com>
> http://www.ben.com/
>
> _______________________________________________