Keyboard Shortcuts
Likes
Search
Beacon and Status message timing
开云体育Hi Andrew ? I have my yaac beta 156 working well transmitting on the local rf network.? The aprs-is port is disabled.? However I seem to have a problem with the timing of beacon and status messages.? In my configuration I have set the beacon message with a slow repeat rate of 900 seconds and the status message with 1500.? I also monitor aprs.fi and findu.com to see how both are being received.? ?I am attaching a file with output since midnight tonight.? You can see that the beacons and status messages received from aprs.fi are very oddly spaced and, particularly at the end of the extract, there are 8 status messages in a row with no beacons in between.? Since only beacons have location information, findu.com does not record the status messages as valid and does not update its records.? Findu.com currently reports the last report received over 7 hours ago. ?My hope is that my beacon and status message timing can be set so that they would roughly alternate so that both aprs.fi and findu.com are synchronized. ? I would point out that when I set yaac instead to transmit directly to the aprs-is network via the internet and disable the rf network, aprs.fi? and findu.com are perfectly synchronized. ? I hope I have explained clearly what my issue is and that there is some solution.? Thanks in advance and for a wonderful program that you are constantly improving and expanding.? You are a great service to the amateur community, Andrew.? Please let me know if you have any questions. ? Joe VA3JLF ? |
|
Hi, Joseph.
That's very strange behavior of the I-gates in your area, keeping your status messages and discarding your positions. What exactly are the settings for your position beacon? Mic-E or standard or compressed text position format? Do you have a free-text comment appended to the beacon? What are the initial and slow rates for your beacon and your status? How many different beacons do you have (only the default one, or additional ones)? The other question is, how many transmit-only beacons are in your area (as in, jamming your position packets)? Are you using time-slotting (not recommended unless you're on a non-standard frequency and your time slots are coordinated with all other stations on the frequency)? Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Friday, July 31, 2020 2:03 PM To: [email protected] Subject: [yaac-users] Beacon and Status message timing Hi Andrew I have my yaac beta 156 working well transmitting on the local rf network. The aprs-is port is disabled. However I seem to have a problem with the timing of beacon and status messages. In my configuration I have set the beacon message with a slow repeat rate of 900 seconds and the status message with 1500. I also monitor aprs.fi and findu.com to see how both are being received. I am attaching a file with output since midnight tonight. You can see that the beacons and status messages received from aprs.fi are very oddly spaced and, particularly at the end of the extract, there are 8 status messages in a row with no beacons in between. Since only beacons have location information, findu.com does not record the status messages as valid and does not update its records. Findu.com currently reports the last report received over 7 hours ago. My hope is that my beacon and status message timing can be set so that they would roughly alternate so that both aprs.fi and findu.com are synchronized. I would point out that when I set yaac instead to transmit directly to the aprs-is network via the internet and disable the rf network, aprs.fi and findu.com are perfectly synchronized. I hope I have explained clearly what my issue is and that there is some solution. Thanks in advance and for a wonderful program that you are constantly improving and expanding. You are a great service to the amateur community, Andrew. Please let me know if you have any questions. Joe VA3JLF |
开云体育Hi Andrew ? My setup is very simple.? I have one beacon that I keep the default name for (default).? The position is manually entered (no gps).? Beacon type is Position.? I have free text.? The initial rate is 60, decay ratio 2 and slow repeat rate 1800.? The selected digipeat paths in proportional path order are WIDE2-1 first and WIDE2-2 second, so I assume WIDE2-1 would be the first priority followed by WIDE2-2.? (Now that I think of it, should this only be WIDE2-2?)? The status beacon is set up the same way with WIDE2-1 in the first position followed by WIDE2-2.? The inital repeat rate is 60, decay ratio 2 and stable repeat rate 1500. ? There is not a lot of radio traffic in my area.? There are very few and I am not using time slotting.? I guess I’ll try using WIDE2-2 for both beacons and see if it makes any difference. ? Joe ? Sent from for Windows 10 ? From: Andrew P.
Sent: July 31, 2020 7:24 PM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing ? Hi, Joseph. ? That's very strange behavior of the I-gates in your area, keeping your status messages and discarding your positions. What exactly are the settings for your position beacon? Mic-E or standard or compressed text position format? Do you have a free-text comment appended to the beacon? What are the initial and slow rates for your beacon and your status? How many different beacons do you have (only the default one, or additional ones)? ? The other question is, how many transmit-only beacons are in your area (as in, jamming your position packets)? Are you using time-slotting (not recommended unless you're on a non-standard frequency and your time slots are coordinated with all other stations on the frequency)? ? Andrew, KA2DDO author of YAAC ? ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Friday, July 31, 2020 2:03 PM Subject: [yaac-users] Beacon and Status message timing ? Hi Andrew ? I have my yaac beta 156 working well transmitting on the local rf network.? The aprs-is port is disabled.? However I seem to have a problem with the timing of beacon and status messages.? In my configuration I have set the beacon message with a slow repeat rate of 900 seconds and the status message with 1500.? I also monitor aprs.fi and findu.com to see how both are being received.?? I am attaching a file with output since midnight tonight.? You can see that the beacons and status messages received from aprs.fi are very oddly spaced and, particularly at the end of the extract, there are 8 status messages in a row with no beacons in between.? Since only beacons have location information, findu.com does not record the status messages as valid and does not update its records.? Findu.com currently reports the last report received over 7 hours ago.? My hope is that my beacon and status message timing can be set so that they would roughly alternate so that both aprs.fi and findu.com are synchronized. ? I would point out that when I set yaac instead to transmit directly to the aprs-is network via the internet and disable the rf network, aprs.fi? and findu.com are perfectly synchronized. ? I hope I have explained clearly what my issue is and that there is some solution.? Thanks in advance and for a wonderful program that you are constantly improving and expanding.? You are a great service to the amateur community, Andrew.? Please let me know if you have any questions. ? Joe VA3JLF ? ? ? ? ? |
|
That's an interesting observation. What are the digipeater specifications for your beacon versus your status? If you can't reach an I-gate without being digipeated, then beacon transmissions without sufficient digipeat aliases (such as WIDE2-2) might not ever get digipeated, whereas if your status only uses WIDE2-2, it would be digipeated all the time.
What are your beacon and status settings, especially regarding digipeat aliases (possibly using proportional pathing)? Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Monday, August 3, 2020 5:11 PM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing Hi Andrew Do you have further thoughts on this? Are my settings correct? The issue seems to be that the status messages get digipeated more than the beacon.because yaac is indeed making the transmissions as far as I can see. Joe VA3JLF |
开云体育Hi Andrew ? The digi specs are as follows: ? Status message????? ???WIDE2-2 with a text of FN13kw CumulusMX on a Raspberry Pi 3 Beacon???????????????? ????????? WIDE2-2 with a text of 21 Fennell Crescent, Cherry Valley WX Station ? Would you suggest changing one to WIDE2-1?? ? Thanks for your help. ? Joe VA3JLF ? ? Sent from for Windows 10 ? From: Andrew P.
Sent: August 3, 2020 5:18 PM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing ? That's an interesting observation. What are the digipeater specifications for your beacon versus your status? If you can't reach an I-gate without being digipeated, then beacon transmissions without sufficient digipeat aliases (such as WIDE2-2) might not ever get digipeated, whereas if your status only uses WIDE2-2, it would be digipeated all the time. ? What are your beacon and status settings, especially regarding digipeat aliases (possibly using proportional pathing)? ? Andrew, KA2DDO author of YAAC ? ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Monday, August 3, 2020 5:11 PM Subject: Re: [yaac-users] Beacon and Status message timing ? Hi Andrew ? Do you have further thoughts on this?? Are my settings correct?? The issue seems to be that the status messages get digipeated more than the beacon.because yaac is indeed making the transmissions as far as I can see. ? Joe VA3JLF ? ? ? ? |
|
No, my concern is that your beacon was using the proportional pathing of
-- direct -- WIDE1-1, WIDE1-1,WIDE2-1 which, if your nearest I-gate still required a digipeat hop, would cause all the -- direct -- (no digpeat aliases) beacon packets to not make it to the I-gate. Similarly, if there are no WIDE1-1 fill-in digis, the packets could have been dropped if the local WIDE2 digis wouldn't also accept WIDE1. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Monday, August 3, 2020 7:33 PM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing Hi Andrew The digi specs are as follows: Status message WIDE2-2 with a text of FN13kw CumulusMX on a Raspberry Pi 3 Beacon WIDE2-2 with a text of 21 Fennell Crescent, Cherry Valley WX Station Would you suggest changing one to WIDE2-1?? Thanks for your help. Joe VA3JLF Sent from Mail<> for Windows 10 From: Andrew P.<mailto:andrewemt@...> Sent: August 3, 2020 5:18 PM To: [email protected]<mailto:[email protected]> Subject: Re: [yaac-users] Beacon and Status message timing That's an interesting observation. What are the digipeater specifications for your beacon versus your status? If you can't reach an I-gate without being digipeated, then beacon transmissions without sufficient digipeat aliases (such as WIDE2-2) might not ever get digipeated, whereas if your status only uses WIDE2-2, it would be digipeated all the time. What are your beacon and status settings, especially regarding digipeat aliases (possibly using proportional pathing)? Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Monday, August 3, 2020 5:11 PM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing Hi Andrew Do you have further thoughts on this? Are my settings correct? The issue seems to be that the status messages get digipeated more than the beacon.because yaac is indeed making the transmissions as far as I can see. Joe VA3JLF |
开云体育Hi Andrew ? Maybe I have some settings wrong.? On the digipeat tab I have WIDE2-2 checked in aliases for digipeating and WIDE2-2 as selected digipeat path.? Under Beacon I have WIDE2-2 as selected digipeat path and the same thing under the Status tab.? Under the Ports tab I have WIDE 2-2? enable checked.? Do these settings sound right or do I have to change something?? I think WIDE2-2 is the best digipeat path to use. ? Joe VA3JLF ? ? ? Sent from for Windows 10 ? From: Andrew P.
Sent: August 3, 2020 10:05 PM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing ? No, my concern is that your beacon was using the proportional pathing of ? -- direct -- ? WIDE1-1, ? WIDE1-1,WIDE2-1 which, if your nearest I-gate still required a digipeat hop, would cause all the -- direct -- (no digpeat aliases)? beacon packets to not make it to the I-gate. ? Similarly, if there are no WIDE1-1 fill-in digis, the packets could have been dropped if the local WIDE2 digis wouldn't also accept WIDE1. ? Andrew, KA2DDO author of YAAC ? ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Monday, August 3, 2020 7:33 PM Subject: Re: [yaac-users] Beacon and Status message timing ? Hi Andrew ? The digi specs are as follows: ? Status message???????? WIDE2-2 with a text of FN13kw CumulusMX on a Raspberry Pi 3 Beacon?????????????????????????? WIDE2-2 with a text of 21 Fennell Crescent, Cherry Valley WX Station ? Would you suggest changing one to WIDE2-1?? ? Thanks for your help. ? Joe VA3JLF ? ? Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 ? From: Andrew P.<mailto:andrewemt@...> Sent: August 3, 2020 5:18 PM To: [email protected]<mailto:[email protected]> Subject: Re: [yaac-users] Beacon and Status message timing ? That's an interesting observation. What are the digipeater specifications for your beacon versus your status? If you can't reach an I-gate without being digipeated, then beacon transmissions without sufficient digipeat aliases (such as WIDE2-2) might not ever get digipeated, whereas if your status only uses WIDE2-2, it would be digipeated all the time. ? What are your beacon and status settings, especially regarding digipeat aliases (possibly using proportional pathing)? ? Andrew, KA2DDO author of YAAC ? ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Monday, August 3, 2020 5:11 PM Subject: Re: [yaac-users] Beacon and Status message timing ? Hi Andrew ? Do you have further thoughts on this?? Are my settings correct?? The issue seems to be that the status messages get digipeated more than the beacon.because yaac is indeed making the transmissions as far as I can see. ? Joe VA3JLF ? ? ? ? ? ? ? ? |
|
You don't need to check WIDE2 (or any other digipeat alias) on any port unless you are planning to operate as a digipeater through that port. All we are talking about here are the requests in your beacon and status packets as an end-user station to get digipeating service from other stations.
________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Tuesday, August 4, 2020 9:17 AM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing Hi Andrew Maybe I have some settings wrong. On the digipeat tab I have WIDE2-2 checked in aliases for digipeating and WIDE2-2 as selected digipeat path. Under Beacon I have WIDE2-2 as selected digipeat path and the same thing under the Status tab. Under the Ports tab I have WIDE 2-2 enable checked. Do these settings sound right or do I have to change something? I think WIDE2-2 is the best digipeat path to use. Joe VA3JLF Sent from Mail<> for Windows 10 From: Andrew P.<mailto:andrewemt@...> Sent: August 3, 2020 10:05 PM To: [email protected]<mailto:[email protected]> Subject: Re: [yaac-users] Beacon and Status message timing No, my concern is that your beacon was using the proportional pathing of -- direct -- WIDE1-1, WIDE1-1,WIDE2-1 which, if your nearest I-gate still required a digipeat hop, would cause all the -- direct -- (no digpeat aliases) beacon packets to not make it to the I-gate. Similarly, if there are no WIDE1-1 fill-in digis, the packets could have been dropped if the local WIDE2 digis wouldn't also accept WIDE1. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Monday, August 3, 2020 7:33 PM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing Hi Andrew The digi specs are as follows: Status message WIDE2-2 with a text of FN13kw CumulusMX on a Raspberry Pi 3 Beacon WIDE2-2 with a text of 21 Fennell Crescent, Cherry Valley WX Station Would you suggest changing one to WIDE2-1?? Thanks for your help. Joe VA3JLF Sent from Mail<> for Windows 10 From: Andrew P.<mailto:andrewemt@...> Sent: August 3, 2020 5:18 PM To: [email protected]<mailto:[email protected]> Subject: Re: [yaac-users] Beacon and Status message timing That's an interesting observation. What are the digipeater specifications for your beacon versus your status? If you can't reach an I-gate without being digipeated, then beacon transmissions without sufficient digipeat aliases (such as WIDE2-2) might not ever get digipeated, whereas if your status only uses WIDE2-2, it would be digipeated all the time. What are your beacon and status settings, especially regarding digipeat aliases (possibly using proportional pathing)? Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...> Sent: Monday, August 3, 2020 5:11 PM To: [email protected] Subject: Re: [yaac-users] Beacon and Status message timing Hi Andrew Do you have further thoughts on this? Are my settings correct? The issue seems to be that the status messages get digipeated more than the beacon.because yaac is indeed making the transmissions as far as I can see. Joe VA3JLF |
|
Andrew
I have been looking at various settings of mine and I still cannot understand why my status message beacons more often than my weather beacon.? Is there a setting that I am missing?? Look at this output from aprs.fi.? It shows 2 weather beacons followed by 8 status messages.? ?According to my settings in the config, the weather beacon should be going out more often. Thanks Andrew. Joe VA3JLF 2020-08-05 09:27:06 EDT:?>APJYC1,,WIDE2*,qAR,:@132702h4356.06N/07709.62W_232/000g003t069r000p012P000h67b10154?/A=295??21?Fennell?Crescent?Cherry?Valley?Wx?Station 2020-08-05 09:27:06 EDT:?>APJYC1,,WIDE2*,qAR,:@132702h4356.06N/07709.62W_232/000g003t069r000p012P000h67b10154?/A=295??21?Fennell?Crescent?Cherry?Valley?Wx?Station? 2020-08-05 09:28:38 EDT:?>APJYC1,,WIDE2*,qAR,:>FN13kw?CumulusMX?on?a?Raspberry?Pi3 2020-08-05 09:43:39 EDT:?>APJYC1,,WIDE2*,qAR,:>FN13kw?CumulusMX?on?a?Raspberry?Pi3 2020-08-05 09:58:38 EDT:?>APJYC1,,WIDE2*,qAR,:>FN13kw?CumulusMX?on?a?Raspberry?Pi3 2020-08-05 10:13:38 EDT:?>APJYC1,,WIDE2*,qAR,:>FN13kw?CumulusMX?on?a?Raspberry?Pi3 2020-08-05 10:28:39 EDT:?>APJYC1,,WIDE2*,qAR,:>FN13kw?CumulusMX?on?a?Raspberry?Pi3 2020-08-05 10:43:39 EDT:?>APJYC1,,WIDE2*,qAR,:>FN13kw?CumulusMX?on?a?Raspberry?Pi3 2020-08-05 10:52:21 EDT:?>APJYC1,WIDE2-1,qAR,:>FN13kw?CumulusMX?on?a?Raspberry?Pi3 2020-08-05 10:55:22 EDT:?>APJYC1,,WIDE2*,qAR,:>FN13kw?CumulusMX?on?a?Raspberry?Pi3? |
|
If you want to know what your station is doing, watch the RF network. relies on the APRS-IS network for all of its information. The APRS-IS network is designed to delete all of the packets that contain duplicate payload information within a specified window of time. This removes a majority of the information that is available on the RF network. Much of the information that is deleted contains a great deal of evidence of how the local network is functioning.? The APRS-IS network only sees the packets ?that are successfully decoded by the i-gates in the local area. Packet collisions can destroy local reception at the i-gate, which may have been able to be copied locally.? Look to the local RF network for the truth.? James VE6SRV On Wed, Aug 5, 2020 at 9:08 AM Joseph LaFerla <joe@...> wrote: Andrew --
James VE6SRV |
|
Thanks for this James.? I think my problem lies elsewhere, if I do have a problem.? When yaac sends out my status message and weather beacons, both ultimately get to an igate as you can see in the snippet I provided but the status message repeats more often than the weather.? I confirmed this by looking at the AX25xmit files that Andrew asked me to look at.? Ideally I would like the two message types to roughly alternate and I thought that my timings provided for that.
WE have a very small RF network with not too many radios. Joe VA3JLF |