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 for Windows ? From: James Ewen
Sent: March 13, 2024 6:18 PM To: [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 ? ? On Wed, Mar 13, 2024 at 4:02?PM Andrew P. <andrewemt@...> wrote:
? |
|
On Thu, Mar 14, 2024 at 2:28?PM Joseph LaFerla <joe@...> wrote: >? I understand your explanation of the different paths and so on but why is my station VA3JLF-1 not suffering the same fate as his?? You might want to define what the "same fate" means. Are you not seeing your own weather?data, or are you talking about not being digipeated?by local digipeaters? Have the two of you ever looked at the raw data collected by for your stations? If you look at the raw data, there's a lot of information available. There's a lot of information available for you to dig into what is happening with your packets. Specifically this part: ?>APJYC1,,,WIDE2,qAR,: The outgoing path being used by this station is WIDE2-2, which is asking for 2 digipeater hops. You can see that VA3PEC handled the first hop, and VE3UEL handled the second hop, and then WN8Z-4 heard the packet being digipeated?by VE3UEL and gated it to the APRS-IS. If WN8Z-4 was busy hearing local packets in New York, and missed the initial transmission, then a digi local to VE3EP-1 (VA3PEC) repeated the packet. WN8Z-4 missed the digipeat?possibly due to more local traffic or collisions, and then finally heard the second digipeat?of the packet via VA3UEL and gated that to the APRS-IS, as evidenced by the used path elements included in the packet. But you can also see this: >APX210,WIDE2-2,qAR,: In this case, WN8Z-4 heard the packet directly from VE3EP-1, and gated it to the APRS-IS. While all the timing inside computers and components of a digipeater that Andrew pointed out is accurate, this is a much simpler reason for it looking like no one digipeated?the signal. WN8Z-4 heard the initial transmission, and gated the packet. Multiple digipeaters probably heard and digipeated?the packet all over the place, but only the first packet to be gated is shown at . If you look at the info page for VE3EP-1, you can see a table that lists all of the stations that heard VE3EP-1 directly (again, filtered to only the first packets that made it to the APRS-IS). There's a lot more information available at than just the map image. You can also try hovering your cursor over stations. The site will draw a line showing the path the packet took to get from the originating station to the i-gate that put the packet on the APRS-IS.? But the most important thing to remember?is that and site that shows data from the APRS-IS stream is only showing you one possible path that you packet took when in reality on RF, your packet probably travelled many different paths through multiple digipeaters to multiple i-gates, but you only see the one that made it to the APRS-IS first. All the rest of the copies are supressed. James VE6SRV? |
|
Good stuff. I also use & search for your call.
___
Sent from my two-way wrist watch
73 de W3AB/George
On Mar 14, 2024, at 15:13, James Ewen <ve6srv@...> wrote:
|
GEO BADGER