I am new to APRS and working on configuring YAAC. I have a simple entry in my beacon free text field.
"Wolverine Lake, Michigan"
When the system beacons, I see the following when checked from another APRS system or looking at the raw packets view. This can also be easily see on aprs.fi.
,/W2 Wolverine Lake, Michigan
What is the ./W2 in the beacon?
Thanks,
Craig N8PWM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The /W2 is indicating that you have configured your station as a WIDE2-2 digipeater. If you had regional digipeat aliases as well (ex.: MI2-2 for Michigan), they would also appear here, in the format "/W2, MI2".
If you have not actually configured your station as a digipeater, please let me know, as this would then be a bug needing to be fixed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Uh, how did you manage to specify RF digipeat aliases for an APRS-IS port? There's no option for that on the APRS-IS and SSL-APRS-IS port configuration editor panels. I-gates generally don't use digipeat aliases on their Internet-to-RF transmissions, so only RF local stations can hear the I-gate's relays from the Internet.
The rest of it sounds mostly correct if you intend to be operating a WIDE2-2 RF digipeater; your beacon shouldn't be saying WIDE1-1,WIDE2-2 in a single path choice (or are these separate proportional-pathing lines?) unless you intend it to go three hops (through the WIDE1-1 fill-in digi and then twice on the WIDE2-2 wide-range digipeaters). Even if you intend them for proportional pathing, you should either have lines of WIDE1-1 and WIDE1-1,WIDE2-1 or lines of WIDE2-1 and WIDE2-2 (depending on whether you need to relay through a WIDE1-1 fill-in digi to get to the WIDE2-n digipeaters). And this shouldn't be changing on a regular basis, since digipeaters aren't generally installed on mobile stations (ignoring the special-case TEMP1-1 digi feature).
In any case, YAAC automatically provides the information that your station is functioning as a WIDE2-2 digipeater in your beacon message. It is reasonable for a digipeater supporting WIDE2-2 to also support WIDE1-1 to deal with the common case of a mobile end-node station specifying the WIDE1-1,WIDE2-1 path (in case their only reachable digipeater was a WIDE1-1 fill-in digi), especially if the WIDE2-2 digipeater doesn't support the still-non-standard ability to skip ahead in digipeat aliases in the path (forgot the term used to describe this ability; in any case, YAAC doesn't have this feature).
Andrew, KA2DDO
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry that was my mistake. I only have the digi paths on the RF side. I have confirmed the settings as suggested. I have aliases as WIDE1-1 and WIDE2-2 but the digi path is WIDE1-1, WIDE2-1.
Thank you for your help. I think I have a better understanding of the settings.
Excellent product!
Thanks,
Craig N8PWM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi all,
I am new to APRS and working on configuring YAAC. I have a simple entry in my beacon free text field.
"Wolverine Lake, Michigan"
When the system beacons, I see the following when checked from another APRS system or looking at the raw packets view. This can also be easily see on aprs.fi.
,/W2 Wolverine Lake, Michigan
What is the ./W2 in the beacon?
Thanks,
Craig N8PWM
The /W2 is indicating that you have configured your station as a WIDE2-2 digipeater. If you had regional digipeat aliases as well (ex.: MI2-2 for Michigan), they would also appear here, in the format "/W2, MI2".
If you have not actually configured your station as a digipeater, please let me know, as this would then be a bug needing to be fixed.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Andrew,
I am setup as a digi. I have wide1-1, wide2-2 setup on the digipeat tab under aliases and wide1-1, wide2-1 under the digi path.
I have wide1-1 and wide2-2 setup for the aprs-is and tnc aliases.
This does not seem right to me. Do you have suggestions on my setup?
Thank you for your response.
Thanks,
Craig N8PWM
Uh, how did you manage to specify RF digipeat aliases for an APRS-IS port? There's no option for that on the APRS-IS and SSL-APRS-IS port configuration editor panels. I-gates generally don't use digipeat aliases on their Internet-to-RF transmissions, so only RF local stations can hear the I-gate's relays from the Internet.
The rest of it sounds mostly correct if you intend to be operating a WIDE2-2 RF digipeater; your beacon shouldn't be saying WIDE1-1,WIDE2-2 in a single path choice (or are these separate proportional-pathing lines?) unless you intend it to go three hops (through the WIDE1-1 fill-in digi and then twice on the WIDE2-2 wide-range digipeaters). Even if you intend them for proportional pathing, you should either have lines of WIDE1-1 and WIDE1-1,WIDE2-1 or lines of WIDE2-1 and WIDE2-2 (depending on whether you need to relay through a WIDE1-1 fill-in digi to get to the WIDE2-n digipeaters). And this shouldn't be changing on a regular basis, since digipeaters aren't generally installed on mobile stations (ignoring the special-case TEMP1-1 digi feature).
In any case, YAAC automatically provides the information that your station is functioning as a WIDE2-2 digipeater in your beacon message. It is reasonable for a digipeater supporting WIDE2-2 to also support WIDE1-1 to deal with the common case of a mobile end-node station specifying the WIDE1-1,WIDE2-1 path (in case their only reachable digipeater was a WIDE1-1 fill-in digi), especially if the WIDE2-2 digipeater doesn't support the still-non-standard ability to skip ahead in digipeat aliases in the path (forgot the term used to describe this ability; in any case, YAAC doesn't have this feature).
Andrew, KA2DDO
Sorry that was my mistake. I only have the digi paths on the RF side. I have confirmed the settings as suggested. I have aliases as WIDE1-1 and WIDE2-2 but the digi path is WIDE1-1, WIDE2-1.
Thank you for your help. I think I have a better understanding of the settings.
Excellent product!
Thanks,
Craig N8PWM