Keyboard Shortcuts
Likes
- Yaac-Users
- Messages
Search
Re: No Beacon tab in expert mode
Frank, I received your private email with the log, and found an interesting "feature". Did you rebuild your Raspberry PI (I can see the operating system type elsewhere in the YAAC.out file), and forget to set the the locale to the United States (instead of defaulting to Great Britain)? The peculiar reason YAAC is failing to show the Beacon tab is because you configured your beacon to display your listening frequency on the 70cm band, on an amateur frequency that is legal in the United States, but not in England. I also see that you imported your configuration from a save file, rather than entering it manually, which is how the "illegal" frequency managed to get in (because the configuration importer assumes that the configuration must have been legal to be there to be exported).
Anyway, because the beacon's monitoring frequency is out-of-band for your Pi's locale, the Beacon tab won't come up. I will fix this in the next build. In the meantime, use "raspi-config" to set your locale correctly to "en_US", and the problem will go away. I've seen this problem before when users wanted to pick a reported frequency in the range 440-450MHz, and couldn't do it because the British locale doesn't allow it. You're the first one to figure out a way around the restriction. Congratulations. :-) Hope this helps. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Andrew P. via groups.io <andrewemt@...> Sent: Sunday, November 10, 2024 2:20 PM To: [email protected] Subject: Re: [yaac-users] No Beacon tab in expert mode This probably means that somehow your saved beacon doesn't work with changes since build 201, and is causing the initialization of the Beacon tab to fail. Please repeat opening the expert-mode Configuration dialog, then copy the YAAC.out file (in your configured logs directory) and email it to me. This will contain the recent progress of YAAC, including the error message of why the Beacon tab couldn't be created. From that file, I can figure out what went wrong and make a fix for it. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Frank Bobro - N3FB via groups.io <fbobro@...> Sent: Sunday, November 10, 2024 1:47 PM To: [email protected] Subject: [yaac-users] No Beacon tab in expert mode Running version 204. I had upgraded from 201. Upgrade process did not work automatically, I did a fresh install and reloaded my saved xml file. I am not seeing a beacon tab in the expert mode, that tab appears to be missing. Tabs that I do see in order are: General Transmit Digipeat Ports Status Preferences Behavior Callsign DB It is beaconing correctly, just wanted to look at the settings after the upgrade. Thanks for any help! Frank Bobro - N3FB 443.650 + PL of 131.8 Transmitting from Canonsburg, PA |
Re: No Beacon tab in expert mode
This probably means that somehow your saved beacon doesn't work with changes since build 201, and is causing the initialization of the Beacon tab to fail.
Please repeat opening the expert-mode Configuration dialog, then copy the YAAC.out file (in your configured logs directory) and email it to me. This will contain the recent progress of YAAC, including the error message of why the Beacon tab couldn't be created. From that file, I can figure out what went wrong and make a fix for it. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Frank Bobro - N3FB via groups.io <fbobro@...> Sent: Sunday, November 10, 2024 1:47 PM To: [email protected] Subject: [yaac-users] No Beacon tab in expert mode Running version 204. I had upgraded from 201. Upgrade process did not work automatically, I did a fresh install and reloaded my saved xml file. I am not seeing a beacon tab in the expert mode, that tab appears to be missing. Tabs that I do see in order are: General Transmit Digipeat Ports Status Preferences Behavior Callsign DB It is beaconing correctly, just wanted to look at the settings after the upgrade. Thanks for any help! Frank Bobro - N3FB 443.650 + PL of 131.8 Transmitting from Canonsburg, PA |
No Beacon tab in expert mode
Running version 204. I had upgraded from 201. Upgrade process did not work automatically, I did a fresh install and reloaded my saved xml file.? I am not seeing a beacon tab in the expert mode, that tab appears to be missing. Tabs that I do see in order are:? General Transmit Digipeat Ports Status Preferences Behavior Callsign DB It is beaconing correctly, just wanted to look at the settings after the upgrade.? Thanks for any help! Frank Bobro - N3FB 443.650 + PL of 131.8 Transmitting from Canonsburg, PA |
Re: APRS Tactical Messages
Alex Pinheiro Machado
Thank you very?much, Andrew! I did know yaac yet, but I will learn about it. I came here to ask apologies about my issues and learn more about. I started my aprs station in 99' with bob bruninga but stayed about 23 years without aprs station and now I am discovering more aprs clients.? 73! Alex, PT2VHF Em ter., 22 de out. de 2024 às 19:11, Andrew P. via <andrewemt=[email protected]> escreveu:
|
Re: APRS Tactical Messages
开云体育Hi, Alex.
I'm Andrew, KA2DDO, the author of YAAC ("Yet Another APRS Client"). This mailing list may not be able to give you the best advice regarding SARTrack configuration, so you may want to email Bart ZL4FOX (the author of SARTrack) at
support@... and see if he can help you. I don't know if Bart has a mailing list.
Another good mailing list is [email protected] which is a general list for all things APRS.
The website https://how.aprs.works has good fundamental information about APRS, so you can be a good netizen on the APRS net.
Also, I wrote up a somewhat long article on basic concepts of APRS that you might find useful to read now that you are on the YAAC mailing list. You can find it here:
/g/yaac-users/message/102
Welcome to the APRS party, and take your time figuring things out and adding new features.
Andrew, KA2DDO From:[email protected] <[email protected]> on behalf of Alex Pinheiro Machado <alexpmr@...>
Sent:?Tuesday, October 22, 2024 4:53:30 PM To:?Jamie Hughes <wa7jh@...> Cc:[email protected] <[email protected]> Subject:?Re: [yaac-users] APRS Tactical Messages ?
Hi Jamie! Sure, I need your suggestions?to fix it and use the best configuration and, of course, do not disturb the network. Could you help?me with this?
Thanks,?
Alex
Em ter., 22 de out. de 2024 às 17:10, Jamie Hughes <wa7jh@...> escreveu:
|
Re: APRS Tactical Messages
Alex Pinheiro Machado
Jamie, I just uninstalled SARTrack to learn before (VHF-3) and checked?VHF-1 that is running?esp32igate, with this configuration below: VHF-1 is digi and igate. For DIGI, which path is better? WIDE-2-2? And what about the beacon interval? Is it fine? Em ter., 22 de out. de 2024 às 18:17, Jamie Hughes <wa7jh@...> escreveu:
|
Re: APRS Tactical Messages
开云体育Alex, ? Thank you for such a quick reply. I use SmartBeaconing so it is kind of complicated but not. ? In short,
The goal here is not to beacon so frequently that I never stop beaconing. Right now, your 15 second beacon is likely just constantly sending data and never listening if it’s connected to RF.
? I like to error on the more frequent beacon but understand that it defeats the system if I beacon too much. ? The SmartBeacon adds a little logic? which I have set like this: I am 5 miles or 5 minutes which ever comes first, when not moving 30 minutes. ? Hope that helps, ? 73, ? Jamie Hughes WA7JH (360) 340-8886 ? From: Alex Rodrigues <alexpmr@...>
Sent: Tuesday, October 22, 2024 1:56 PM To: Jamie Hughes <wa7jh@...> Cc: [email protected] Subject: Re: APRS Tactical Messages ? My Whatsapp number is?+55 61 98402 3634.? Again, my apologies for the trouble I caused!.? ? Alex, PT2VHF ? Em ter., 22 de out. de 2024 às 17:10, Jamie Hughes <wa7jh@...> escreveu:
|
Re: APRS Tactical Messages
Alex Pinheiro Machado
Hi Jamie! Sure, I need your suggestions?to fix it and use the best configuration and, of course, do not disturb the network. Could you help?me with this? Thanks,? Alex Em ter., 22 de out. de 2024 às 17:10, Jamie Hughes <wa7jh@...> escreveu:
|
Re: Tactical Messages from PT2VHF
Alex Pinheiro Machado
Hello! I'm Alex, PT2VHF. A friend of mine told me about this problem. I am trying to figure out all the issues and fix them. I am testing SARTrack and I don?t know why, sometimes the software insists on filling the field "Tactical Name" with my name without my intervention. I will uninstall, clear the configuration and try again. My apologies regarding the confusion.? Best?regards,? Alex, PT2VHF Em ter., 22 de out. de 2024 às 17:19, Jamie H via <wa7jh=[email protected]> escreveu:
|
APRS Tactical Messages
开云体育Good day Alex, ? In the last few weeks, I (we) have noticed lots of APRS tactical messages from you. ? It appears that you are sending your digipeater beacon every minute as well as SARTrack with a beacon every 15 seconds. ? Remember that APRS relies on multiple radios and systems to rebroadcast your data. This means that your beacons are flooding the network with little to no real ability to be propagated with other traffic. ? Would you be willing to adjust your settings to fall in line with a best practice APRS configuration. Your tactical messages are being received worldwide. ? Thank in advance for your consideration, ? Jamie Hughes WA7JH (360) 340-8886 ? |
Fw: [APRS] [yaac-users] Tactical Messages from PT2VHF
________________________________________
From: [email protected] <[email protected]> on behalf of Lynn Deffenbaugh <kj4erj@...> Sent: Tuesday, October 22, 2024 2:15 PM To: [email protected] Subject: Re: [APRS] [yaac-users] Tactical Messages from PT2VHF Thankfully you only need to learn a few things at a time, but you're correct, there's a LOT to APRS (and we haven't even mentioned direction-finding/fox-hunting support objects recent). But two dots just connected in my brain, so circling back to the original question about filtering out Tactical messages, it should be possible to eliminate these coming from the APRS-IS with the following filter term: -g/TACTICAL The minus is a negative or "don't include these" as mentioned by Pete recently and the g/ is a "group message" filter removing all messages directed to TACTICAL. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 10/22/2024 12:35 PM, Luzemario PR7LDR wrote: On Tue, Oct 22, 2024 at 08:55 AM, Lynn Deffenbaugh wrote: (SAR)#Tactical_Callsigns Guys, thank you very much for your answers. It sounds like a trap for novices like me... ;-) This reminds me of John WB2OSZ talking about various APRS extensions in his docs. Those like me who have never done packet radio or APRS before, have a steep learning curve. |
Re: Tactical Messages from PT2VHF
Regarding this station that is flooding the world with TACTICAL message:
I've done some looking at this station, and he is rather abusive of the network. He has a digipeater PT2VHF-1 sending its beacon every minute (not that the digipeater is moving anywhere), so when is anyone else going to get a moment to get a packet in to be digipeated? :-( His digipeater is apparently also an I-gate, because it is feeding the beacons directly to APRS-IS, using a tocall of APE32I. Anybody recognize that software/firmware type? He also has (apparently) a copy of SARtrack running at his home PT2VHF-3 transmitting both its beacon and the TACTICAL message every 15 seconds (!), no position change. Since he is directly connected to the APRS-IS backbone, the T2BRAZIL backbone server isn't throttling his excessive transmission rate the way a digipeater would. I wonder if he is transmitting the same rate on RF; we would never see it since he is sending direct to APRS-IS so no other I-gate could possibly get it in faster than he does. Of course, we don't know if any of this is actually about that station; it could be a fraudulent false identity trying to jam the APRS-IS. Any Brazilian operators on these mailing lists who know this operator? Since he is not sending anything useful, I would recommend using YAAC's blacklist feature to block his callsign-SSIDs (disabling at least QUERY operations for his callsign-SSID). Blacklisting is persisted, so you won't have to keep setting it up. Jamie, hope this helps. I'm still going to make some of the other fixes I proposed to make this sort of thing less likely to happen by accident. Bart ZL4FOX, is there a mode in SARTrack that could let a user do this sort of network abuse? And to the keepers of the APRS-IS backbone, should Tx I-gates provide the same sort of duplicate throttling that New-N digipeaters do (no more than one identical packet in 30 seconds)? I want to check my code to ensure I'm throttling like that on a Tx I-gate configuration. Andrew, KA2DDO author of YAAC ("Yet Another APRS Client") ________________________________________ From: [email protected] <[email protected]> on behalf of Andrew P. <andrewemt@...> Sent: Monday, October 21, 2024 8:23 AM To: [email protected] Subject: Re: [yaac-users] Tactical Messages from PT2VHF Whenever the dialog announcing tactical messages from that user comes up, click the "Never" button. That will remember that decision as long as YAAC remains up. Considering how annoying these messages can be, I'm thinking about making some changes to this: 1. Persist a "Never" or "Always" decision for a specific sending callsign over YAAC restarts. However, then there would have to be a way to delete the persisted settings if they were no longer wanted. 2. Ignore TACTICAL messages to get your local tactical aliases entirely if you don't have any defined, so the annoying dialog won't come up if you have nothing to send to the requestor. 3. Fix YAAC's sending of TACTICAL messages to be RFONLY,NOGATE so that it won't go to the APRS-IS unless someone specifically changes the configuration to enable it. Since TACTICAL names are supposed to be local (not global), those messages really shouldn't be going over the Internet. The menu choices to send and get tacticals isn't even enabled in YAAC unless you have an open RF port, but any station set up as an I-gate would presently allow the messages to be sent to APRS-IS as well as RF. I need to check how many of those annoyances are coming from YAAC (as opposed to some other program like Xastir), and see if the present default behavior of YAAC is contributing to noise. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Jamie H <wa7jh@...> Sent: Sunday, October 20, 2024 8:02 PM To: [email protected] Subject: [yaac-users] Tactical Messages from PT2VHF I keep getting tactical messages from this call, can I turn that shit off? Jamie Hughes WA7JH (360) 340-8886 |
Re: Tactical Messages from PT2VHF
开云体育Alas, the filtering won't stop the automatic recognition of query text messages.?
The comments in my previous message discuss handling these issues.
Andrew, KA2DDO
author of YAAC
Powered by Cricket Wireless Get From: [email protected] <[email protected]> on behalf of Andrew W5AWS via groups.io <awds@...>
Sent: Sunday, October 20, 2024 8:20:28 PM To: [email protected] <[email protected]> Subject: Re: [yaac-users] Tactical Messages from PT2VHF ?
My guess is that you can filter messages.
Look under 'Contents' of the 'Help' menu then in the 'Table of Contents': 'Menus' then click on 'Filter'. As a new user just started, I can't be more specific until I finish working my way through the Help system. Andrew, W5AWS. -=-=-=- |
Re: Tactical Messages from PT2VHF
Whenever the dialog announcing tactical messages from that user comes up, click the "Never" button. That will remember that decision as long as YAAC remains up.
Considering how annoying these messages can be, I'm thinking about making some changes to this: 1. Persist a "Never" or "Always" decision for a specific sending callsign over YAAC restarts. However, then there would have to be a way to delete the persisted settings if they were no longer wanted. 2. Ignore TACTICAL messages to get your local tactical aliases entirely if you don't have any defined, so the annoying dialog won't come up if you have nothing to send to the requestor. 3. Fix YAAC's sending of TACTICAL messages to be RFONLY,NOGATE so that it won't go to the APRS-IS unless someone specifically changes the configuration to enable it. Since TACTICAL names are supposed to be local (not global), those messages really shouldn't be going over the Internet. The menu choices to send and get tacticals isn't even enabled in YAAC unless you have an open RF port, but any station set up as an I-gate would presently allow the messages to be sent to APRS-IS as well as RF. I need to check how many of those annoyances are coming from YAAC (as opposed to some other program like Xastir), and see if the present default behavior of YAAC is contributing to noise. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Jamie H <wa7jh@...> Sent: Sunday, October 20, 2024 8:02 PM To: [email protected] Subject: [yaac-users] Tactical Messages from PT2VHF I keep getting tactical messages from this call, can I turn that shit off? Jamie Hughes WA7JH (360) 340-8886 |
Re: Tactical Messages from PT2VHF
My guess is that you can filter messages.
Look under 'Contents' of the 'Help' menu then in the 'Table of Contents': 'Menus' then click on 'Filter'. As a new user just started, I can't be more specific until I finish working my way through the Help system. Andrew, W5AWS. -=-=-=- |
Tactical Messages from PT2VHF
开云体育I keep getting tactical messages from this call, can I turn that shit off? ? Jamie Hughes WA7JH (360) 340-8886 ? |
next beta build#204 of YAAC, created 2024-Oct-16
next beta build#204 of YAAC ("Yet Another APRS Client"), re-created 2024-Oct-16
downloadable from or changes and updates include: 1. account for day and month wrap issues for timestamped position and Object reports. 2. support compressed-mode position reports for weather stations where the compressed-mode position includes the wind direction and speed. 3. speed up YAAC startup by optimizing initialization code. 4. properly identify private Objects as Objects when they will never have any messages. 5. add ability to draw "heat map" of station position density across time (for moving station coverage). 6. add optional capability to send an Object kill message when a locally originated Object is deleted from the local system. 7. harden packet log import code to survive cases when logged packets were corrupted. 8. add the ability to mark selected stations with higher or lower importance for purposes of sorting stations. 9. fix cases where certain popup menu choices were not allowed on the map view when they should have been. 10. remove some duplicate GUI layout code. 11. fix bug introduced in digipeat path editing panel. 12. widen timestamp columns in table views so the time isn't truncated by default. 13. fix Object editor when updating an Object using an alternate symbol table overlay code. 14. first pass at trying to fix Station/Object list when the list is restricted to only Stations or only Objects. 15. first pass at trying to fix map refresh logic when timed values need updating. 16. fix rendering of overlay character when using double-sized or quad-sized icons. 17. add indicator on map window toolbar to report that filtering is being used, so the user doesn't have to open the Edit->Filter dialog to check for the presence of filtering. 18. fix inactivity timing in APRS-IS port driver to prevent spurious disconnects when traffic is light. 19. make the "pool ball" icons stop rotating on the map. 20. fix ADSB plugin to refresh the map when aircraft data is updated. 21. make it possible to clear old history from the vessels table in the AisDecoder plugin. 22. fix pseudo-APRS-IS server plugin to send cached state of known stations to newly connected clients so they don't have to wait to get current on network status. 23. update demo and smallscreen plugins to work with new screen feature added to support a previous build's update to the dynamic objects plugin. 24. add ability in dynamic objects plugin to locate the position of a distance along a route. 25. tweak the MS150CueTranslator utility to match the identifiers used for this year's rest stops. 26. add more icons for amenity types on the OpenStreetMap rendering. |