[aprssig] Re: Unreasonable xmission delay

[Bruce W. Martin, KQ4TV]

I received the following information today.
NT4UX-2 is a UIdigi v1.93 using N8DEU's reccomended settings.
KQ4TV-1 is a javAPRSSrvr 3.11b03 Igate.

Can anyone shed light on what can be done to eliminate 5 minutes of  
delay for 100 miles of 3 hops.

Bruce, KQ4TV


On Jul 14, 2006, at 1:57 PM, Case, Coe wrote:

> Bruce:
>
> Please evaluate the following raw data from FINDU.
>
> 20060714122325,K4COE>S4TS1V,WIDE1-1,WIDE2-1,qAo,N8DEU-4:`rAf!hW>/]"3r}
> 20060714122427,K4COE>S4TR9X,WIDE1-1,WIDE2-1,qAo,N8DEU-4:`rB 
> \nsF>/]"3r}CERT,SkyWarn,RACES,ARES
> ....
> 20060714122815,K4COE>S4TS1V,W4GPS-7,WIDE1,NT4UX-2,WIDE2*,qAR,KQ4TV-1:` 
> rAf!hW>/]"3r}
> 20060714122941,K4COE>S4TR9X,W4GPS-7,WIDE1,NT4UX-2,WIDE2*,qAR,KQ4TV-1:` 
> rB\nsF>/]"3r}CERT,SkyWarn,RACES,ARES
> It appears there is a 5 minute delay in nt4ux-2 and kq4tv-1  
> retransmission and igate posting to the internet.  It is causing  
> FINDU to overwrite current data with data and locations that are 5  
> minutes old.  Two hops should be a worst case 20 sec delay, not 5  
> minutes.
>
> If you are working/Tracking vehicle to vehicle (not via the  
> internet), then getting to the first i-gate means nothing, you  
> still need to wideN to get to the other vehicle's mobile APRS.   
> Besides, as you can see from my track displays over the last 3  
> weeks, I travel through area's that even three hops do not get to  
> any digi/igate.  (Colorado, South Carolina, Louisianna as endpoints)
>
> Thanks,
>
> K4coe