开云体育

next beta build#187 of YAAC ("Yet Another APRS Client"), created 2023-Sep-17 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/p/yetanotheraprsc changes and updates include: 1. fix plugin loading logic so dependencies between plugins will be properly resolved and first windows provided by plugins can be used again (this was broken in build#185). 2. allow creating alternate map windows centered on a specific station or object. This was intended to be a convenience in tracking multiple individual mobile stations (such as SAGs in a bicycle event). 3. fix the ?YDBG qury handler to not report the map center and zoom if the queried station does not have any map windows. 4. resolve a few more "bugs" about inner classes that could be static. 5. fix popping forward of text message table window so self-addressed text messages don't cause the pop-forward to occur. This became necessary when YAAC could start originating telemetry messages with the associated self-addressed text messages labeling the telemetry fields. 6. fix individual station history table to decode free-text comments as UTF-8 (same as the main Raw packets table), not ISO-8859-1. 7. fix table popup menu choices to pan the map to a station or object to not cause a failure if YAAC is running without a map window. 8. fix expert-mode configuration panels so they don't fail to be created if YAAC doesn't have a map window open. 9. fix plugin "store" to work with revised plugin loading logic. Newly installed plugins that have other pre-existing plugins dependent on them may not work correctly, but at least it will try, and the issue wil be fixed when YAAC is restarted. 10. fix APRS-IS port drivers to automatically send comments to backbone server if the YAAC instance hasn't sent a packet to the backbone for the timeout check interval, so the backbone won't keep disconnecting YAAC instances operating in listen-only mode. 11. fix sendable packet logic to prevent extra duplicate packet from being transmitted. 12. for Mic-E packets, fix model type code for Anytone D878UV, add type codes for new Yaesu FTM-300D, FT5D, and FTM-500D. 13. upgrade version of SLF4J logging library used by YAAC to 2.0.7. 14. harden SmallScreen plugin to better handle circular plugin dependencies. 15. add first draft of new RV Telemetry plugin, which allows YAAC to collect and recompute telemetry data from its environment (using the Pi4J library to access GPIO data on Raspberry Pi computers) and subsequently transmit APRS Telemetry messages of the collected data, with a new directed query option ?TELEM to ask the station to send its telemetry now instead of waiting for the next configured reporting time.

Hello, I’m a new YAAC user and as I’m delving into Linux, I would like an APRS client there. I have YAAC working fairly well, however there is one aspect I have not been able to figure out despite searching this group, Googling, and reviewing the https://www.ka2ddo.org/ka2ddo/YAAC.html pages. I seem to only be able to see spots on the map for a small radius based on my lat./long. I’m only using one APRS-IS port for now, set to noam.aprs2.net. I have tried both with a GPS (with the port added) and without (manually set lat./long.). I have tried this on well-appointed machines; one Intel i9 (Windows 10 Pro, 16 Core, 65GB RAM, 2TB HD) and one AMD (Linux Mint 21.2, 8 Core, 32GB RAM, 1TB HD), so I’m not thinking it’s a machine performance or resource issues. I start YAAC with -Xms2048m -Xmx8192m (and I have tried other combination). I have 1GB ethernet down for my internet connection. With the Windows based APRSIS32, I can see spots on its map for the entire country. The answer is probably out there somewhere, but I could use your collective guidance on the following: I am only seeing messages within a few miles of me (maybe 50 miles). I can change my location (via the right clink on map and “Move Home Here”) and new/updated spots (raw packets) from the old location still show up on the Raw packet monitor and map but no other new ones for my updated location. I have tried setting the “Monitoring Radius” to 150 statute miles and setting the Range Limit filter to 150 statute miles, but no additional spots show up on the map. I have also tried restarting YAAC after changes are made and double-checking the settings. Can anyone offer some guidance on this topic? I’m guessing I am missing something (probably obvious), but I just haven’t been able to figure out what it might be yet. I am befuddled. Regards, Michael KD8GIJ

This newbie is successful at figuring out how to send a beacon out on 144.390. But how to I configure the digipeter settings to ping the ISS on 144.825. Also, to I set to "beacon", or "aprs"? I can find no tutorials, aside from the internal help menu. But it is beyond my understanding. Thanks.

Here we go again. I hate my terrible memory. I'm building a new APRS station on a Quadra computer running armbian out of the box. I've got other APRS machines, one on a Mint desktop and one on a RaspberryPi that autostart on boot without issue. The problem is, I do not recall how I set it up. There is no service, no .bashrc, no init.d, no autostart folders, no crontabs, none of the usual suspects. They just do it. Now I'm trying to get direwolf and YAAC to autostart on this new box and it just isn't happening. I've found multiple options in previous messages, but nothing seems to work for me on this box. Ideas appreciated. -- 73, Michael WA7SKG "Any day you do not learn one new thing is a wasted day."

So I have YAAC now running on the Quadra. So far, I just have one port configured for APRS-IS. Now, I am getting a random pop-up box that says "Failure on port#1:APRS-IS noam.aprs2.net EOF" I click OK and the box goes away. Several hours later, it is back. All the data still seems to be on the screen. Is this just a network hiccup, or something I need to worry about or fix? -- 73, Michael WA7SKG "Any day you do not learn one new thing is a wasted day."

Has anybody set up YAAC on one of these little Quadra computers? I understand they are very similar to a RaspberryPi, but there are some differences. I will need to use a software modem as I do not have an available TNC. -- 73, Michael WA7SKG "Any day you do not learn one new thing is a wasted day."

Looking for help on how to configure Digipeater settings to ping ISS on 145.825.. Thanks

Seems the upgrade logic was broken on Raspberry Pis and a few other sysystem where an operating-system-provided copy of the JSSC library was being used. Since that library wouldn't be writeable by normal users (to protect it from Trojan Horses and related malware "features"), YAAC thought that YAAC itself couldn't be upgraded. This code is now fixed so that only files in the YAAC installation directory are checked for writeability by the requesting user when you invoke the Help->Check For Updates menu choice. If you managed to get build#185 installed, you may have to manually overwrite it with build#186 (or later) to get around this problem. Sorry about the inconvenience. Andrew, KA2DDO author of YAAC ---------------------------------------------------------------------- next beta build#186 of YAAC ("Yet Another APRS Client"), created 2023-Aug-26 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/p/yetanotheraprsc changes and updates include: 1. fix upgrading bug where use of an operating-system-supplied copy of the JSSC library makes YAAC think it can't be upgraded. 2. fix broken hyperlinks in built-in help files.

The OpenStreetMap map data has also been updated to the August 14th snapshot of the OSM database. -------------------------------- next beta build#185 of YAAC ("Yet Another APRS Client"), created 2023-Aug-26 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/p/yetanotheraprsc changes and updates include: 1. fix incorrect map clearing of regions bounded by a Shoreline Way. 2. make position message parsing more tolerant of text-format latitude and longitude of exactly zero that alsdo use "0" instead of the hemisphere indicator ("N", "S", "W", "E"), and extract signpost comments better. 3. generalize access to per-user YAAC data directory to ensure consistency, 4. improve error reporting when YAAC tries to use a plugin requiring a newer version of the Java runtime environment, so that the user will know what version they need to use the plugin. 5. clarify some debug logging messages. 6. add the ability for plugins to selectively force logging of received APRS packets, even if the user configuration specifies not logging received traffic. 7. re-order the default entries on the View menu to make YAAC still usable if using the GtkLookAndFeel (which doesn't support scrolling or multi-columning menus that are longer than the screen height). Also allow using the swing.defaultlaf property to override the default look-and-feel for the Java UI. 8. fix Help->About dialog to not expand to ridiculous size if a large number of plugins are installed. 9. fix per-station history table to refresh automatically as new packets are received from the station or about the object. 10. fix NullPointerException and ClassCastException from improper initialization of JSpinners. 11. clean up more old code style issues causing spurious compiler and IDE warnings. 12. fix NullPointerException upon starting a mouse drag across the map from outside the map boundaries. 13. fix LineEditor control for table cells allowing the user to select a line style for rendering polylines upon the map. 14. fix node domain name processing in AREDN plugin. 15. fix plugins with inconsistent text on the About dialog. 16. fix timestamping of dynamic objects so they move and render correctly. 17. fix PBBS plugin so configuration panel doesn't fail on initial configuration. 18. add Extreme Temperature alert conditions to weather alert plugin. 17. fix NullPointerException in weatheralert plugin's configuration panel.

Hello all. I bought a Kenwood TM-D7A (G) in good shape. I'm wanting to connect it directly to a Pi or PC and use the TNC for YAAC. I have the serial cable and I plan to use a USB GPS on the computer side to let YAAC port position data. Where do I go in the configuration to tell it about this TNC? Any other hints or knowledge on this radio is welcome! This was one of those unicorn radios that came up cheap and I think it is still useful. Thanks! Ronny K4RJJ

HI I am not sure when this started but I am no longer able to see the menu bar on Y. It seems to be covered up with something and I cannot figure it out. I tried minimising and maximising the image. Anyone have any idea what is going on. I have the latest beta 183 I think. Thanks. Joe VA3TV Sent from Mail for Windows

Greetings, Does YAAC check for the existence of hardware even if the Serial_TNC port is unchecked? Likewise, does it also check if something like Dire Wolf is running even if the AGWPE port is unchecked? If I recall correctly, YAAC appears check for inactive ports. I find it handy to keep them configured, but unused, if the associated device is unplugged and/or the software (as in Dire Wolf) is not running. This way I can switch devices and simply click/unclick the appropriate ports depending on what hardware I've got connected. Is this expected behavior? I don't normally switch devices that much and will now delete inactive ports. If it makes any difference, I'm running YAAC with three profiles as well. Thanks! 73, KD0KZE / Paul

I'm hosting YAAC on a Pi4 running Ubuntu, and after seeing the update email this morning I've manually run the "Check for Updates" from the Help menu. The response is a Check for Updates window that states: "The YAAC application and1 plugins need upgrading but you do not have permission to overwrite them." I'd be grateful of a steer on where to look for a fix. 73 Ciemon G0TRT

Hello Andrew, I know how you feel when you lose a friend and radio amateur, I also want to offer you my heartfelt condolences. Unfortunately, I have lost many companions in recent years. No matter where you live in this world ..... losing a friend is always bad! Greetings from the sunny south of Germany Wolfgang

This build is a tribute to my friend, the late "Jedi" Jim Fisher AD3DI (SK), who supported the APRS radio operations for the Multiple Sclerosis Society's City-to-Shore 150 bike ride in southern New Jersey. Several of these changes are to support comm ops for the ride. Others are followups to the fixes in the last build, including fixing some mapping issues. Enjoy! Andrew, KA2DDO --------------------------------------------------------- next beta build#184 of YAAC ("Yet Another APRS Client"), created 2023-Aug-10 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/p/yetanotheraprsc changes and updates include: 1. fix user-reported bugs in connected-mode AX.25 stack. 2. clean up source code Javadocs. 3. more repairs on Mac OS X specific operation of YAAC. 4. make Kenwood display message list scrollable with keyboard arrow keys, implement Tune button if repeaterfinder plugin is available and current message is a repeater specification. 5. on map, fix sizing of symbol overlay character, background status and Mic-E status circles when symbol icon is enlarged so they aren't hodden by the larger icon. 6. fix "active operator" overlay configuration control to not conflict with symbol choices that would prevent using the "active operator" overlay. 7. fix OSM rendering so areas of map would not be blanked incorrectly and that water bodies surrounding an island would not be reported in OSM popup dialog if the island was clicked. 8. fix more bugs in WayAnalyzer debug utility. 9. fix bugs in rendering GeoTIFF raster images that use angular coordinates instead of linear (distance) coordinates. 10. fix errors in processing KISS output stream escapes. 11. fix OSM map importing and rendering of wetlands and islands, and Ways that barely cross tile boundaries. 12. Updates to support using extra column providers on the local objects table, not just the station/object list. This is a service enabled by the bikestats plugin. 12. update dynamic objects plugin to allow manually correcting a dynamic object's position by specifying a OSM or APRS object or station where the dynamic object should be now (ex.: lead bicycle object just passed a staffed route checkpoint). 13. update the repeater finder plugin to expose its tuning capabilities through the TuneIfc now used by the Kenwood radio view dialog. These capabilities are specific to the radio being controlled by the plugin. Also add tuning support for Icom IC-2730A, IC-9700, and IC-705.

Hey Folks, Apologies but I was able to figure it out when configuring the TNC I was using Raw AX.25 protocol, therefore beacon, digi, and PBBS functions worked. Once I switched and enabled APRS protocol messaging started to work. Thanks, Rocco WQ1Q

Hi Everyone, I'm a relatively new YAAC user I am having an issue with getting APRS messaging working from YAAC itself. It seems I can create messages but they do not Xmit. Beaconing is working, digipeating works, in addition connecting to a PBBS also works. I can also rx messages say from another HT, but I am unable to xmit a reply. All the previous mentioned functions puts out RF. For some reason any kind of messaging i.e. station chat, direct messaging, winlink email will not put a transmission out on the wire. I am running a linux system with YAAC and using a d-74 in kiss mode connected via usb. Given the other functions work and I have used this setup successfully in xastir I am reasonably confident it's a configuration issue on my end. Thoughts?

Hello, I installed YAAC on a, I believe a Windows 10 machine. The radio is a new FTM-500 and the idea was to display a map of APRS traffic around the location. I could see raw packets on messages but no stations on the map. I am curious why I can see the raw packaets and not see anying on the map. On a new install on a PC is there a filter or something you have to change to get YAAC to see stations on the map? In other installations on linux machines I alwasy see stations on the map if I am getitng raw packets. Since I do not run on windows any thoughts from the those that do use windows. Tim KM4ESU