[wxsig] Awfully quiet

[Gerry Creager]

The data are timestamped as soon as they hit FindU.  More likely, you 
are seeing a digi-induced delay.  Last time I looked, we were not seeing 
much latency on the APRS-IS side.

As Mountain digis do seem to see a lot of traffic, I suspect that's a 
real problem for you.

gerry n5jxs
first.aprs.net

John Koster wrote:
> On Fri, 11 Aug 2006,  Dave wrote:
> 
>> Well I think I was the last one to post some problems, and we have it 
>> working much more reliable now, it did seem to be a heat issue with the 
>> regulator.  We are having some issues with long update delays, I don't think 
>> it is an RF issue, I think it is more an internet issue.  Sometimes in 
>> findu.com it will show a multi-hour delay, but on aprswest it will show a 
>> much shorter gap, and vice versa, any ideas?
>>
> 
> If you get real time data monitoring your own signal, then you don't have 
> much control over how long it takes to propagate through digipeaters and 
> the internet.  The time does seem out of reason, but I have zero 
> experience in that department.  If you have more than one digi that you 
> can hit, you might try a beam pointed towards one or the other and see if 
> that makes a difference.  One of them might have a better path to the 
> igate.
> 
> Another issue might be how flooded the server is with data and how long it 
> takes to crunch things.  I wouldn't expect the delays you're talking about 
> however.  
> 
> In either case I don't think you have much control over it.  After all, 
> it's a broadcast protocol.
> 

-- 
Gerry Creager -- gerry.creager at tamu.edu
Texas Mesonet -- AATLT, Texas A&M University	
Cell: 979.229.5301 Office: 979.458.4020  FAX 979.862.3983
MAIL:  AATLT, 3139 TAMU
Physical: 1700 Research Parkway, Suite 160,
College Station, TX 77843-3139