开云体育

Ah, you have fallen into the misguided and incorrect assumption that you can use aprs.fi for propagation analysis. You cannot do this, because the APRS-IS explicitly does not report _every_ packet delivered by I-gates to the APRS-IS backbone, but only the _first_ _instance_ of each packet. So only the fastest I-gate on the lowest RF delay path will get credit for forwarding your packets to APRS-IS.

Let us make an entirely hypothetical example, since I don't know all the stations in your vicinity.

Let us assume that an I-gate near VE3UEL is using DireWolf, a software TNC with built-in I-gating capability. As soon as the packet is finished demodulating, DireWolf has the packet on its way to APRS-IS (it doesn't have to send the packet anywhere else first).

Let us also assume that the I-gate near VA3PEC is using a hardware TNC, so after it demodulates the packet, it has to send the packet in KISS mode at 9600 baud (bulked out by asynchronous start and stop bits and framing) to the computer running the I-gate software. Assuming your packets are 70 bytes of address header and payload body (a reasonable size with 2 digipeat aliases, plain ASCII encoding of latitude and longitude and no timestamp, and at least 5 fields of weather parameters), that takes 75 milliseconds just to get the packet out of the TNC and into the attached computer so the I-gate software can start processing it.

By that time, the DireWolf instance has already delivered its copy of the packet to its APRS-IS server.

So the TNC I-gate loses and will not be reported on aprs.fi as sending the packet, even though it heard the packet at the same time as the DireWolf instance did (and that's assuming both digipeaters are retransmitting the packet at the same time, rather than one waiting for another local station to shut up, or one improperly configured to do random delay of packet transmission instead of as soon as the channel is clear).

The only way you can tell if a digipeater has digipeated your packet is to listen to the digipeater's RF transmissions on RF. And you can't tell if a digipeater sent it if another digipeater collides with its transmission, causing the packet to be lost in interference.

Hope this helps.

Andrew, KA2DDO
author of YAAC (a very _slow_ I-gate)
________________________________________
From: [email protected] <[email protected]> on behalf of Ian Morrison <Ianm3920@...>
Sent: Thursday, March 14, 2024 11:32 AM
To: [email protected]
Subject: Re: [yaac-users] Missing Weather on Local Map

Well, the my last 34 beacons were digipeated by ve3uel according to aprs.fi, which is approx. 50 kms from here and one from ve3pec which is approx.. 10 kms away. Va3pec is not a particularly busy digipeater. So my conclusion is that I am being “Ignored”.
Interestingly though I can see both va3pec and ve3uel in the raw packets list in YAAC., plus many other stations being didipeated by both repeaters but only mine nine along with others by ve3uel

Ian
VE3EP

BTW if you want to have a look, the calls are ve3ep-1 and ve3ep-9 for the mobile.

Sent from Mail<> for Windows

From: James Ewen<mailto:ve6srv@...>
Sent: March 13, 2024 6:18 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [yaac-users] Missing Weather on Local Map

The first question I would ask is "How do you know the nearest digipeater is ignoring your signal?"

What evidence do you have to support that statement?

James
VE6SRV


On Wed, Mar 13, 2024 at 4:02?PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
That's peculiar. Why would the local digipeaters be ignoring your packets? Wrong digipeat path? Non-standard frequency? Or did they blacklist you for some reason?

And you can't hear the distant digipeater?

________________________________________
From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Ian Morrison <Ianm3920@...<mailto:Ianm3920@...>>
Sent: Wednesday, March 13, 2024 5:59 PM

Thanks for the reply Andrew.
RF only. The nearest digipeater ignores my signal but a distant one picks it up and sends it to an igate. Actually there are three digis quite close and they all ignore me.
Ian
VE3EP


From: Andrew P.<mailto:andrewemt@...<mailto:andrewemt@...>>
Sent: March 13, 2024 5:47 PM

Are you using RF on your station or just an Internet connection? Bear in mind that YAAC only reports _received_ station information, and APRS-IS never sends your own station's packets back to your own station, whereas local digipeaters will bounce back RF packets your station has transmitted.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Ian Morrison <Ianm3920@...<mailto:Ianm3920@...>>
Sent: Wednesday, March 13, 2024 5:44 PM

YAAC version 0-beta 196 (17 Feb 24) on a RPI 3
All is well in the outside world. Station and weather seen on YAAC map of my near neighbour. APRS.FI<> is also correct.
My local map is showing all the stations reporting weather in my vicinity except my own. Just the weather symbol. The beacon doesn’t update it.

Anyone see a similar problem

Ian Morrison
VE3EP